From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: schwab@linux-m68k.org, 38587@debbugs.gnu.org
Subject: bug#38587: base64-decode-region breaks encoding
Date: Tue, 24 Dec 2019 17:13:45 +0100 [thread overview]
Message-ID: <87a77hem6e.fsf@gnus.org> (raw)
In-Reply-To: <87r20tenv8.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 24 Dec 2019 16:37:15 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Something equivalent to what the manual has to say about it would be
> nice.
I've now added a slightly vague version what the manual says here to the
doc strings, but I think it should be factually correct.
I also noticed that the encode-coding-region/decode-coding-region doc
strings do not actually say the most important thing -- whether
"encoding" goes from bytes to text or the other way around, so I've now
made this extremely explicit, because I think there's a lot of confusion
in the area, and "encode" and "decode" in themselves don't actually mean
anything.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-12-24 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 23:55 bug#38587: base64-decode-region breaks encoding Juri Linkov
2019-12-13 2:52 ` Lars Ingebrigtsen
2019-12-13 7:12 ` Eli Zaretskii
2019-12-14 23:31 ` Juri Linkov
2019-12-15 8:56 ` Andreas Schwab
2019-12-15 22:40 ` Juri Linkov
2019-12-16 15:58 ` Eli Zaretskii
2019-12-16 21:51 ` Juri Linkov
2019-12-17 16:04 ` Eli Zaretskii
2019-12-17 23:10 ` Juri Linkov
2019-12-24 15:37 ` Lars Ingebrigtsen
2019-12-24 16:13 ` Lars Ingebrigtsen [this message]
2019-12-16 16:18 ` Andreas Schwab
2019-12-17 16:27 ` Lars Ingebrigtsen
2019-12-15 15:26 ` Eli Zaretskii
2019-12-15 22:41 ` Juri Linkov
2019-12-16 3:28 ` Eli Zaretskii
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=87a77hem6e.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38587@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=schwab@linux-m68k.org \
/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.