unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: ashton@wiersdorfmail.net, 74230@debbugs.gnu.org
Subject: bug#74230: 30.0.92; eshell-emit-prompt clobbers text properties
Date: Thu, 14 Nov 2024 10:52:21 +0200	[thread overview]
Message-ID: <86v7wqjiyi.fsf@gnu.org> (raw)
In-Reply-To: <42bd1d73-8faf-b12b-e3c3-06c814d395a4@gmail.com> (message from Jim Porter on Thu, 7 Nov 2024 10:16:16 -0800)

> Date: Thu, 7 Nov 2024 10:16:16 -0800
> Cc: eliz@gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
> 
> On 11/6/2024 10:21 AM, Ashton Wiersdorf wrote:
> > In Emacs 29.4, the function did *not* overwrite the text properties of
> > the prompt `rear-nonsticky (read-only)`. The new version overwrites the
> > rear-nonsticky property so that it is only `(field)`.
> 
> Thanks for noticing this.
> 
> > If I set `eshell-highlight-prompt' to `t', then I get the read-only
> > behavior that I want, but now I cannot get the pleasant component
> > highlighting that `fancy-shell' is meant to provide.
> 
> If you set the 'face' attribute instead of the 'font-lock-face' 
> attribute, you should get the highlighting you want (that's what I do) 
> while 'eshell-highlight-prompt' is non-nil.
> 
> Here's a patch to fix this though so that we're more careful about not 
> clobbering stickiness properties. Eli, what do you think about this 
> patch? It fixes a regression from Emacs 29, but the diff is fairly large 
> for so late in the Emacs 30 cycle. Unfortunately, I can't think of a 
> better solution that doesn't just shuffle the bug around to a different 
> spot. On the plus side, this code already has regression tests, and it 
> was easy to add a new one for this case.
> 
> Personally, I'd be ok with having this be a known bug (there's a 
> workaround for Emacs 30) and fixing it on master. But if you think this 
> change is ok for the release branch, I'd also be ok with installing 
> there; then people don't need to deal with the workaround.

I agree, let's fix this on master.

Thanks.





  reply	other threads:[~2024-11-14  8:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 18:21 bug#74230: 30.0.92; eshell-emit-prompt clobbers text properties Ashton Wiersdorf
2024-11-07 18:16 ` Jim Porter
2024-11-14  8:52   ` Eli Zaretskii [this message]
2024-11-14 18:33     ` Jim Porter

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=86v7wqjiyi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74230@debbugs.gnu.org \
    --cc=ashton@wiersdorfmail.net \
    --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).