From: Eli Zaretskii <eliz@gnu.org>
To: dan.hitt@gmail.com, tomasn@posteo.net
Cc: 46507@debbugs.gnu.org
Subject: bug#46507: 26.1; bold attribute copied into enriched-mode text is not saved
Date: Sat, 13 Mar 2021 12:28:58 +0200 [thread overview]
Message-ID: <83y2eribyt.fsf@gnu.org> (raw)
In-Reply-To: <83sg55ss4o.fsf@gnu.org> (message from Eli Zaretskii on Mon, 08 Mar 2021 15:16:07 +0200)
> Date: Mon, 08 Mar 2021 15:16:07 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: tomasn@posteo.net, 46507@debbugs.gnu.org
>
> > I went through the exercise with eshell, to make sure that nothing changed, and it doesn't seem to have:
> > colors get saved, but not boldness.
>
> So if the problem is with the font-lock-face vs face property, why is
> it that enriched-mode does preserve the color attribute, but not the
> both attribute? They both come from the same font-lock-face property,
> no?
>
> > Eli: Maybe it is wrong for me to say "needs" :) :). It would be very convenient though, and i could tweak some
> > variables in my start up (for testing with 'emacs -Q' though i would have to finagle it somehow i guess?).
>
> I don't think there's argument that enriched-mode should support this
> use case.
I've now attempted to extend enriched.el on the master branch to
support this use case. Please test.
next prev parent reply other threads:[~2021-03-13 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 2:01 bug#46507: 26.1; bold attribute copied into enriched-mode text is not saved Dan Hitt
2021-03-07 12:46 ` Tomas Nordin
2021-03-07 16:51 ` Dan Hitt
2021-03-07 19:23 ` Tomas Nordin
2021-03-07 19:29 ` Eli Zaretskii
2021-03-07 20:18 ` Dan Hitt
2021-03-08 13:16 ` Eli Zaretskii
2021-03-13 10:28 ` Eli Zaretskii [this message]
2021-03-13 18:47 ` Dan Hitt
2021-03-13 19:22 ` Eli Zaretskii
2021-03-14 7:32 ` Dan Hitt
2021-03-14 7:50 ` 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=83y2eribyt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46507@debbugs.gnu.org \
--cc=dan.hitt@gmail.com \
--cc=tomasn@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 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).