From: Leo Butler <leo.butler@umanitoba.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: saving/restoring text and overlays
Date: Mon, 30 Mar 2020 15:14:19 -0500 [thread overview]
Message-ID: <867dz1fvms.fsf@x201.butler.org> (raw)
In-Reply-To: <83imim4lzs.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Mar 2020 05:25:43 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> ********************************************************
> Caution: This message was sent from outside the University of Manitoba.
> ********************************************************
>
>> From: Leo Butler <leo.butler@umanitoba.ca>
>> Date: Sun, 29 Mar 2020 15:21:39 -0500
>> Cc: help-gnu-emacs@gnu.org
>>
>> So it appears that enriched text mode did do what I want, but the way
>> Emacs handles display properties is too permissive...
>>
>> This leads me to ask why the feature was nuked rather than handling it
>> like file variables
>> (https://www.gnu.org/software/emacs/manual/html_node/emacs/File-Variables.html).
>
> It wasn't nuked, you are reading too much into that NEWS entry. Only
> the dangerous part was disabled, and even that can be enabled if you
> trust the source of the file.
You are right.
After more investigation, I find that Emacs 25.2.2 on Ubuntu 18.04
is not saving the x-display properties while Emacs 26.1 on Debian
testing does.
Inspection of enriched.el on each system shows that on Ubuntu
enriched-translations is missing the portions
(FUNCTION (enriched-decode-foreground "x-color")
(enriched-decode-background "x-bg-color")
(enriched-decode-display-prop "x-display"))
(display (nil enriched-handle-display-prop))
Sigh.
Apologies, I should have looked more carefully.
Leo
prev parent reply other threads:[~2020-03-30 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 4:14 saving/restoring text and overlays Leo Butler
2020-03-26 22:23 ` Michael Heerdegen
2020-03-29 20:21 ` Leo Butler
2020-03-30 0:14 ` Michael Heerdegen
2020-03-30 0:23 ` Michael Heerdegen
2020-03-30 1:23 ` Noam Postavsky
2020-03-30 2:25 ` Eli Zaretskii
2020-03-30 20:14 ` Leo Butler [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=867dz1fvms.fsf@x201.butler.org \
--to=leo.butler@umanitoba.ca \
--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).