From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Robert Pluim <rpluim@gmail.com>, 33855@debbugs.gnu.org
Subject: bug#33855: 27.0.50; Can't see markup in HELLO
Date: Sat, 21 May 2022 13:58:19 +0200 [thread overview]
Message-ID: <87mtfbyu5g.fsf@gnus.org> (raw)
In-Reply-To: <jwv8rqw4cni.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 20 May 2022 08:33:43 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Looking a bit more into it, I wonder if 'enriched-toggle-markup' should
> be merged with the `enriched-mode` command itself.
>
> 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?
(Then more discussion followed.)
I don't really have much of an opinion here -- I think that
enriched-mode is a weird thing to have as a minor mode. If you switch
it on in a programming mode, and then save the file, you've destroyed
the file -- silently. (You can often undestroyify it by loading it into
Emacs, and then writing out the buffer text to a file, but would a user
know that?)
It's a thing that only makes sense as a major mode, inheriting from text
mode, and it should have its own file ending, like HELLO.enriched.
Fortunately, the only file in existence in the entire universe➀ that uses
this format (and minor mode) is etc/HELLO, so it's not a major issue
(except for the file-destroying bit for unfortunate users, but
fortunately most people don't know about it so they don't try to use
it).
➀ Fact not officially notarized.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-21 11:58 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
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 [this message]
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=87mtfbyu5g.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=33855@debbugs.gnu.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).