From: Eli Zaretskii <eliz@gnu.org>
To: Dan Hitt <dan.hitt@gmail.com>
Cc: tomasn@posteo.net, 46507-done@debbugs.gnu.org
Subject: bug#46507: 26.1; bold attribute copied into enriched-mode text is not saved
Date: Sun, 14 Mar 2021 09:50:47 +0200 [thread overview]
Message-ID: <83blbmgomg.fsf@gnu.org> (raw)
In-Reply-To: <CAOphiz+OZ5XC8+x2pF+sFv-P5Wh+P7tCBxvSxLST33KG8OVCUw@mail.gmail.com> (message from Dan Hitt on Sat, 13 Mar 2021 23:32:51 -0800)
> From: Dan Hitt <dan.hitt@gmail.com>
> Date: Sat, 13 Mar 2021 23:32:51 -0800
> Cc: Tomas Nordin <tomasn@posteo.net>, 46507@debbugs.gnu.org
>
> For the sake of anybody who stumbles across this thread, i tested it by uncompressing
> /usr/share/emacs/26.3/lisp/textmodes/enriched.el.gz into a new empty directory.
>
> Then i hand-patched in the diffs (i.e., i patched it by cut-and-paste, using emacs, not using any program that
> understands diffs).
>
> Then i ran 'emacs -Q', and did M-x load-file to load in the modified enriched.el file.
>
> Then i did the test: copying in chunks of text from eshell and shell, setting the mode to enriched, saving,
> closing, and reopening, and it worked in all cases.
>
> Presumably what will happen next is that this fix eventually gets pushed out and adopted by debian and
> ubuntu and whoever else is downstream, but in the meantime i can just the modified enriched.el.
>
> Thanks again for figuring out how to fix it.
Thanks for testing, I'm therefore closing this bug report.
prev parent reply other threads:[~2021-03-14 7:50 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
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 [this message]
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=83blbmgomg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46507-done@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).