From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 58843@debbugs.gnu.org
Subject: bug#58843: Print "decrypted" rot13 text is buffer is read-only
Date: Sat, 29 Oct 2022 08:51:49 +0300 [thread overview]
Message-ID: <835yg3jhxm.fsf@gnu.org> (raw)
In-Reply-To: <87zgdf20zr.fsf@posteo.net> (message from Philip Kaludercic on Fri, 28 Oct 2022 19:37:28 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: 58843@debbugs.gnu.org
> Date: Fri, 28 Oct 2022 19:37:28 +0000
>
> >> When someone sends you rot13'ed text but the buffer is read-only, it
> >> seems the next best thing one can do is to print the decrypted text. I
> >> don't think it makes sense in general for `translate-region' to do the
> >> same, so I just modified the code in rot13.el.
> >
> > Thanks, but I see no patch in your message. I see a complete rot13.el
> > file.
>
> Oops, I must have selected the wrong file.
Showing the result in the echo-area is a good idea, but echo-area is
not really suitable for displaying arbitrarily long text. How about
popping a window with a temporary buffer instead?
This also needs a NEWS entry, I think.
next prev parent reply other threads:[~2022-10-29 5:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 18:24 bug#58843: Print "decrypted" rot13 text is buffer is read-only Philip Kaludercic
2022-10-28 19:18 ` Eli Zaretskii
2022-10-28 19:37 ` Philip Kaludercic
2022-10-29 5:51 ` Eli Zaretskii [this message]
2022-10-29 6:28 ` Philip Kaludercic
2022-10-29 7:08 ` Eli Zaretskii
2022-10-29 15:32 ` Philip Kaludercic
2022-10-29 15:50 ` Eli Zaretskii
2022-10-29 16:03 ` Philip Kaludercic
2022-10-29 16:12 ` Eli Zaretskii
2022-10-29 16:25 ` Philip Kaludercic
2022-10-29 16:45 ` Eli Zaretskii
2022-10-30 14:17 ` Philip Kaludercic
2022-11-04 23:09 ` Philip Kaludercic
2022-10-30 14:44 ` Stefan Kangas
2022-10-30 14:52 ` Philip Kaludercic
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=835yg3jhxm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58843@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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).