From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rcopley@gmail.com, 35739@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#35739: Bad signature from GNU ELPA
Date: Sat, 25 May 2019 10:36:36 +0300 [thread overview]
Message-ID: <83imtz3rzv.fsf@gnu.org> (raw)
In-Reply-To: <jwvh89jzl68.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 24 May 2019 15:51:28 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: rcopley@gmail.com, 35739@debbugs.gnu.org, npostavs@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?
next prev parent reply other threads:[~2019-05-25 7:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 21:25 bug#35739: Bad signature from GNU ELPA Richard Copley
2019-05-14 21:37 ` bug#35739: Acknowledgement (Bad signature from GNU ELPA) Richard Copley
2019-05-14 22:04 ` bug#35739: Bad signature from GNU ELPA Noam Postavsky
2019-05-14 22:26 ` Richard Copley
2019-05-14 22:42 ` Richard Copley
2019-05-15 2:42 ` Eli Zaretskii
2019-05-15 7:13 ` Richard Copley
2019-05-15 14:03 ` Stefan Monnier
2019-05-15 15:03 ` Eli Zaretskii
2019-05-18 22:36 ` Stefan Monnier
2019-05-22 5:19 ` Eli Zaretskii
2019-05-22 16:20 ` Stefan Monnier
2019-05-22 17:09 ` Eli Zaretskii
2019-05-22 19:40 ` Stefan Monnier
2019-05-23 3:50 ` Eli Zaretskii
2019-05-23 4:06 ` Stefan Monnier
2019-05-23 4:52 ` Eli Zaretskii
2019-05-23 12:10 ` Stefan Monnier
2019-05-23 14:15 ` Eli Zaretskii
2019-05-24 14:22 ` Stefan Monnier
2019-05-24 15:00 ` Eli Zaretskii
2019-05-24 19:31 ` Stefan Monnier
2019-05-24 19:43 ` Eli Zaretskii
2019-05-24 19:51 ` Stefan Monnier
2019-05-25 7:36 ` Eli Zaretskii [this message]
2019-05-25 18:38 ` Stefan Monnier
2019-05-25 19:13 ` Eli Zaretskii
2019-05-15 2:41 ` Eli Zaretskii
2019-05-15 6:46 ` Richard Copley
2019-05-15 14:40 ` Eli Zaretskii
2019-05-15 15:12 ` Richard Copley
2019-05-29 18:45 ` Stefan Monnier
2019-05-29 19:11 ` Richard Copley
2019-05-29 20:07 ` Stefan Monnier
2019-05-29 20:50 ` Noam Postavsky
2019-05-30 2:35 ` Eli Zaretskii
2019-05-31 4:54 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83imtz3rzv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35739@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=rcopley@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.