From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 54486@debbugs.gnu.org
Subject: bug#54486: 29.0.50; Eshell `escaped' string property can "leak" into output
Date: Mon, 21 Mar 2022 22:00:00 +0200 [thread overview]
Message-ID: <83cziff54v.fsf@gnu.org> (raw)
In-Reply-To: <b6e46375-f26d-f0ba-9aa0-ea18e119de19@gmail.com> (message from Jim Porter on Mon, 21 Mar 2022 12:24:09 -0700)
> Cc: 54486@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Mon, 21 Mar 2022 12:24:09 -0700
>
> I didn't know `yank-excluded-properties' existed. I think that would be
> a good thing to use for this.
>
> Besides that, I think it would be best if Eshell didn't show the
> `escaped' property when printing things under normal circumstances. It's
> really just for internal bookkeeping in Eshell, so I think users are
> unlikely to want to see it in most cases. The best way to fix this might
> be to rethink how Eshell (specifically `eshell-stringify') prints lists
> by default. This is mentioned in bug#12689 (though that bug additionally
> describes an unrelated issue with Eshell subcommands that I've since fixed).
Eshell commands that print strings could remove that property.
> Finally, maybe it would be good to change the name of the `escaped'
> property to something like `eshell-escaped'.
Yes, that'd be a good thing. But I'm worried that it could cause
failures in existing code, couldn't it? We could do that as an
experiment and see if anyone complains.
prev parent reply other threads:[~2022-03-21 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 3:52 bug#54486: 29.0.50; Eshell `escaped' string property can "leak" into output Jim Porter
2022-03-21 4:04 ` Jim Porter
2022-03-21 12:19 ` Eli Zaretskii
2022-03-21 19:24 ` Jim Porter
2022-03-21 20:00 ` 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=83cziff54v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54486@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
/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).