From: Eli Zaretskii <eliz@gnu.org>
To: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
Cc: 44411@debbugs.gnu.org
Subject: bug#44411: 28.0.50; uudecode-decode-region-internal is broken
Date: Tue, 03 Nov 2020 17:36:28 +0200 [thread overview]
Message-ID: <83d00ucv0j.fsf@gnu.org> (raw)
In-Reply-To: <86y2ji6e0y.wl--xmue@d1.dion.ne.jp> (message from Kazuhiro Ito on Tue, 03 Nov 2020 17:27:41 +0900)
> Date: Tue, 03 Nov 2020 17:27:41 +0900
> From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
>
> When I call uudecode-decode-region-internal in multibyte buffer, it
> fails to decode eight-bit characters.
What do you mean by "decode eight-bit characters"? There's no such
thing in the "real world", it is entirely an Emacs invention. How
could such "characters" appear in uuencoded email message?
Can you describe the real-life use case where this happened?
> Additionally, concat and char-to-string functions are called so
> frequently that deocder is very slow for large data.
Please show only the changes to fix what you think is a bug. let's
leave the optimization alone for a moment, so that it doesn't muddy
the waters.
Thanks.
next prev parent reply other threads:[~2020-11-03 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 8:27 bug#44411: 28.0.50; uudecode-decode-region-internal is broken Kazuhiro Ito
2020-11-03 15:09 ` Lars Ingebrigtsen
2020-11-03 15:36 ` Eli Zaretskii [this message]
2020-11-04 8:26 ` Kazuhiro Ito
2020-11-04 15:26 ` Eli Zaretskii
2020-11-05 10:48 ` Kazuhiro Ito
2020-11-05 13:48 ` Eli Zaretskii
2020-11-07 9:42 ` Eli Zaretskii
2020-11-09 15:47 ` Kazuhiro Ito
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d00ucv0j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44411@debbugs.gnu.org \
--cc=kzhr@d1.dion.ne.jp \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).