From: Don Hopkins <don@donhopkins.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 3735@debbugs.gnu.org, dsb@smart.net, Chong Yidong <cyd@gnu.org>,
18135@debbugs.gnu.org, miha@kamnitnik.top
Subject: bug#18135: bug#3735: shell-mode editing, movement, and command entry broken by prompt/output changes
Date: Wed, 8 Dec 2021 01:20:46 +0100 [thread overview]
Message-ID: <819B1602-3EAA-48A7-8E83-52D16F1F6769@donhopkins.com> (raw)
In-Reply-To: <87ee6of9w4.fsf@gnus.org>
Thank you! I’m looking forward to upgrading to emacs 29.
-Don
> On Dec 7, 2021, at 21:16, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> <miha@kamnitnik.top> writes:
>
>> Yeah I thought about that too. However, commands such as 'yank' or
>> 'just-one-space' use insert rather than insert-and-inherit and thus
>> always bypass inheritance of surrounding text properties regardless of
>> it's stickiness. That is why I settled for using the
>> 'insert-in-front-hooks' text property, patch attached.
>
> Thanks; works well here, too, so I've pushed this to Emacs 29 now.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-12-08 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 12:52 bug#18135: Emacs bug # 3735 definitely not fixed (5 years later) Don Hopkins
2017-05-06 14:46 ` Chong Yidong
2021-12-04 21:15 ` bug#18135: bug#3735: shell-mode editing, movement, and command entry broken by prompt/output changes Lars Ingebrigtsen
2021-12-04 22:18 ` Don Hopkins
2021-12-05 16:13 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 19:27 ` Lars Ingebrigtsen
2021-12-07 16:57 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 20:16 ` bug#3735: " Lars Ingebrigtsen
2021-12-08 0:20 ` Don Hopkins [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=819B1602-3EAA-48A7-8E83-52D16F1F6769@donhopkins.com \
--to=don@donhopkins.com \
--cc=18135@debbugs.gnu.org \
--cc=3735@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=dsb@smart.net \
--cc=larsi@gnus.org \
--cc=miha@kamnitnik.top \
/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).