GNU bug report logs - #35739
[w32] Bad signature from GNU ELPA for archive-contents

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: rcopley <at> gmail.com, 35739 <at> debbugs.gnu.org, npostavs <at> gmail.com
Subject: bug#35739: Bad signature from GNU ELPA
Date: Sat, 25 May 2019 10:36:36 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: rcopley <at> gmail.com,  35739 <at> debbugs.gnu.org,  npostavs <at> gmail.com
> Date: Fri, 24 May 2019 15:51:28 -0400
> 
> > I'm okay with documenting what that produces somewhere
> 
> That would be a big help,

Where would you like this to be documented?

Btw, in two different messages in this thread you mentioned two
different situations.  One is this:

> document what it means to insert decoded text into a unibyte buffer

The other is this:

> I don't know what decoding text into a unibyte buffer will do

The former seems to imply the following:

  (with-current-buffer BUFFER
    (set-buffer-multibyte nil)
    (insert (decode-coding-string STRING CODING-SYSTEM)))

while the latter implies this:

  (with-current-buffer BUFFER
    (set-buffer-multibyte nil))
  (decode-coding-string STRING CODING-SYSTEM nil BUFFER)

The results of these 2 use cases are not the same.

So I don't yet have a clear idea what exactly you want to be
documented.  In particular, what 'insert' does in the 1st use case
seems to be documented in its doc string, but maybe that is not
enough?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.