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 19:45:20 +0300 [thread overview]
Message-ID: <83h6zmh93z.fsf@gnu.org> (raw)
In-Reply-To: <87eduqppgc.fsf@posteo.net> (message from Philip Kaludercic on Sat, 29 Oct 2022 16:25:07 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: 58843@debbugs.gnu.org
> Date: Sat, 29 Oct 2022 16:25:07 +0000
>
> > No, this is described in the "Rmail Rot13" node.
>
> Ah yes. How does this look like:
OK, with two nits:
> +@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
^^^^^^^^
"in-place"
> +display the plain text in the echo area. If the text is too long, a
> +separate buffer will be used.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Passive voice alert! Suggest to rephrase
If the text is too long for the echo area, the command will pop up a
temporary buffer with the decrypted text.
Btw, is it "decrypted" or "encrypted/decrypted"?
Thanks.
next prev parent reply other threads:[~2022-10-29 16:45 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h6zmh93z.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 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.