From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 33855@debbugs.gnu.org
Subject: bug#33855: 27.0.50; Can't see markup in HELLO
Date: Wed, 18 May 2022 15:07:59 +0200 [thread overview]
Message-ID: <87czgbc7kg.fsf@gnus.org> (raw)
In-Reply-To: <jwv36qn7uua.fsf@iro.umontreal.ca> (Stefan Monnier's message of "Sun, 23 Dec 2018 17:15:57 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> I can't seem to figure out how to conveniently edit the markup.
> In modes like image-mode, postscript-mode, doc-view-mode, ..., we can
> choose between the "edit source" and "view rendering", but for
> enriched-mode buffers, all I find is find-file-literally which not only
> makes the markup explicit but also shows me the bytes rather than the
> chars, which is not what I want.
>
> I think we should add a way to see (and edit) the markup.
> Maybe the corresponding command can be `enriched-mode` (tho currently
> that command doesn't do this).
> And maybe it can be bound to C-c C-c.
This doesn't seem like it should be that difficult to implement.
Round-tripping with
(enriched-encode (point-min) (point-max) (current-buffer))
and
(enriched-decode (point-min) (point-max))
seems to work fine (well, with some post-processing after the first to
get rid of colours, so they're not doubly encoded).
I'm not quite sure that having the `C-c C-c' command be `enriched-mode'
would be all that helpful, though -- was there any particular reason for
that in the feature spec?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-18 13:07 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 [this message]
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
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=87czgbc7kg.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=33855@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).