From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, rpluim@gmail.com, 33855@debbugs.gnu.org
Subject: bug#33855: 27.0.50; Can't see markup in HELLO
Date: Fri, 20 May 2022 10:24:12 -0400 [thread overview]
Message-ID: <jwvleuw2siw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83v8u09wep.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 May 2022 16:16:30 +0300")
>> Cc: Robert Pluim <rpluim@gmail.com>, 33855@debbugs.gnu.org
>> Date: Fri, 20 May 2022 08:33:43 -0400
>> From: Stefan Monnier via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Currently, doing something like:
>>
>> C-x C-f .../HELLO # Open an enriched-mode file
>> M-x enriched-mode # Disable enriched-mode
>> foobar # Insert arbitrary text
>> C-x C-s # Save
>>
>> throws away all the annotations without any warning.
>>
>> WDYT?
>
> What other method would you suggest for removing the annotations?
Maybe a more explicit one, like `C-x h M-x write-region`?
I can't see any part of my above recipe which says that the user (me in
this case, I was just trying things out, tho admittedly I disabled
`enriched-mode` via the menu on the "Enriched" word in the mode line
instead of via `M-x enriched-mode`) intended to remove the annotations.
Stefan
next prev parent reply other threads:[~2022-05-20 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 22:15 bug#33855: 27.0.50; Can't see markup in HELLO Stefan Monnier
2022-05-18 13:07 ` Lars Ingebrigtsen
2022-05-18 14:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-18 14:53 ` Robert Pluim
2022-05-19 23:18 ` Lars Ingebrigtsen
2022-05-20 12:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 13:16 ` Eli Zaretskii
2022-05-20 14:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-20 15:49 ` Eli Zaretskii
2022-05-20 18:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 19:07 ` Eli Zaretskii
2022-05-20 20:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-21 5:34 ` Eli Zaretskii
2022-05-21 11:58 ` Lars Ingebrigtsen
2022-05-21 12:42 ` Eli Zaretskii
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=jwvleuw2siw.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=33855@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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).