From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 58843@debbugs.gnu.org
Subject: bug#58843: Print "decrypted" rot13 text is buffer is read-only
Date: Sun, 30 Oct 2022 14:52:35 +0000 [thread overview]
Message-ID: <871qqpbbyk.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmn--eWiKLpotLVjDVPGrgVWt+a+qy3fpvD9vSp=dW4=PQ@mail.gmail.com> (Stefan Kangas's message of "Sun, 30 Oct 2022 07:44:08 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>>> No, this is described in the "Rmail Rot13" node.
>>
>> Ah yes. How does this look like:
>
> Do people use rot13 very much these days? I've not seen it used in
> practice in 20 years, but that's just anecdotal of course.
The reason I am proposing this patch is because I have been using it for
the last few weeks as I am taking a cryptography course, and the
exercise hints are "encrypted" in rot13.
> Would it make sense to exclude the `(emacs) Rmail Rot13' section from
> the printed manual? I don't know how frequently we do that, and maybe
> the practice is frowned upon.
I have no opinion on this.
prev parent reply other threads:[~2022-10-30 14:52 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
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 [this message]
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=871qqpbbyk.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=58843@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefankangas@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 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).