From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: enriched mode loses bold on save, version 26.1, debian 10.3
Date: Sat, 13 Feb 2021 17:31:11 +0300 [thread overview]
Message-ID: <YCfir4gixurkaMXE@protected.rcdrun.com> (raw)
In-Reply-To: <83tuqgccpt.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2021-02-13 16:36]:
> > Date: Sat, 13 Feb 2021 13:10:39 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: help-gnu-emacs@gnu.org
> >
> > > I think this is a bug in enriched-mode, please report it together with
> > > the recipe for reproducing the problem.
> >
> > Let us say I have M-x shell in one window, and my prompt symbol "$" is
> > green color or bold, and in other window file in enriched mode.
> >
> > Then I move to buffer *shell* and copy this:
> >
> > ,----
> > | $ ls
> > `----
> >
> > I can see visually that $ is green in color or bold, and when I insert
> > it into enriched mode file, I can see the same color. When I save it,
> > it is not there, this is because propertized text was copied and
> > pasted.
> >
> > Is enriched mode supposed to understand propertized text and convert
> > such into enriched mode?
>
> Well, it did understand the foreground color in the OP's recipe,
> didn't it?
Now when inspecting that it should save the color I can see it does
save the color, that I did not know.
> it did save the color, but not the bold attribute So then answer
> appears to be YES, and there's something Enriched mode should have
> done but didn't.
That is right and also clarified to me.
> (And there's no reason to "convert to enriched mode", since what
> Enriched mode offers is a mechanism to save and restore text
> properties. It's not like it invents some new text attributes or
> something, they are just text properties.)
Aha. That I did not know.
next prev parent reply other threads:[~2021-02-13 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 2:21 enriched mode loses bold on save, version 26.1, debian 10.3 Dan Hitt
2021-02-13 8:30 ` Jean Louis
2021-02-13 8:37 ` Eli Zaretskii
2021-02-13 10:10 ` Jean Louis
2021-02-13 13:35 ` Eli Zaretskii
2021-02-13 14:31 ` Jean Louis [this message]
2021-02-13 15:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 15:27 ` Jean Louis
2021-02-14 2:09 ` Dan Hitt
2021-02-14 2:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-15 2:15 ` Dan Hitt
2021-03-14 7:43 ` Dan Hitt
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=YCfir4gixurkaMXE@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).