From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58843@debbugs.gnu.org
Subject: bug#58843: Print "decrypted" rot13 text is buffer is read-only
Date: Sat, 29 Oct 2022 16:25:07 +0000 [thread overview]
Message-ID: <87eduqppgc.fsf@posteo.net> (raw)
In-Reply-To: <83ilk2halz.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 Oct 2022 19:12:56 +0300")
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: 58843@debbugs.gnu.org
>> Date: Sat, 29 Oct 2022 16:03:39 +0000
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > LGTM, but what about the suitable change to the user manual?
>>
>> I can't appear to find anything in the manual mentioning rot13. Are you
>> suggesting creating a new node?
>
> No, this is described in the "Rmail Rot13" node.
Ah yes. How does this look like:
[-- Attachment #2: Type: text/plain, Size: 718 bytes --]
diff --git a/doc/emacs/rmail.texi b/doc/emacs/rmail.texi
index e38bde036a..4939f5597c 100644
--- a/doc/emacs/rmail.texi
+++ b/doc/emacs/rmail.texi
@@ -1409,6 +1409,13 @@ Rmail Rot13
rot13-other-window}. This displays the current buffer in another window
which applies the code when displaying the text.
+@findex rot13-region
+ If you are only interested in a region, the command @kbd{M-x
+rot13-region} might be preferable. This will decrypt the active
+region in place. If the buffer is read-only, it will attempt to
+display the plain text in the echo area. If the text is too long, a
+separate buffer will be used.
+
@node Movemail
@section @command{movemail} program
@cindex @command{movemail} program
next prev parent reply other threads:[~2022-10-29 16:25 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
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 [this message]
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=87eduqppgc.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=58843@debbugs.gnu.org \
--cc=eliz@gnu.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 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).