unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: enriched mode loses bold on save, version 26.1, debian 10.3
Date: Sat, 13 Feb 2021 10:37:05 +0200	[thread overview]
Message-ID: <83blcoe53i.fsf@gnu.org> (raw)
In-Reply-To: <CAOphizKqe9iRNJ6A0jgCgTK61-zADqRU1_LT-sPa150g3RHBzg@mail.gmail.com> (message from Dan Hitt on Fri, 12 Feb 2021 18:21:29 -0800)

> From: Dan Hitt <dan.hitt@gmail.com>
> Date: Fri, 12 Feb 2021 18:21:29 -0800
> 
> I can copy text that has colors and some words bolded into a buffer showing
> an enriched-text file.
> 
> For example, i can open an eshell, and do ls: the command prompt is bold
> and orange, while the files i list that are directories come out bold and
> blue, with black unbold text for regular files.
> 
> When i paste this text into an enriched-text file, all of the colors and
> bolding show up.
> 
> When i close the file, and reopen it, the colors are still there, but the
> bolding is gone.
> 
> This is in emacs version 26.1, on debian 10.3.
> 
> What i would like is for the bolding to be saved as well  --- if
> enriched-text is not suitable for this, is there another mode anybody can
> recommend?

I think this is a bug in enriched-mode, please report it together with
the recipe for reproducing the problem.



  parent reply	other threads:[~2021-02-13  8:37 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 [this message]
2021-02-13 10:10   ` Jean Louis
2021-02-13 13:35     ` Eli Zaretskii
2021-02-13 14:31       ` Jean Louis
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=83blcoe53i.fsf@gnu.org \
    --to=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).