From: Lars Ingebrigtsen <larsi@gnus.org>
To: miha@kamnitnik.top
Cc: 3735@debbugs.gnu.org, dsb@smart.net, Chong Yidong <cyd@gnu.org>,
18135@debbugs.gnu.org, Don Hopkins <don@donhopkins.com>
Subject: bug#18135: bug#3735: shell-mode editing, movement, and command entry broken by prompt/output changes
Date: Sun, 05 Dec 2021 20:27:16 +0100 [thread overview]
Message-ID: <8735n6svhn.fsf@gnus.org> (raw)
In-Reply-To: <87bl1v3u99.fsf@miha-pc> (miha@kamnitnik.top's message of "Sun, 05 Dec 2021 17:13:06 +0100")
miha@kamnitnik.top writes:
> Reproducer:
>
> - copy " -la" into kill ring
> - type "echo ls" into M-x shell
> - (Shell gives output line "ls".)
> - Go up to output line "ls" (C-p).
> - yank " -la"
> - press C-b
> - the line now "ls -la" with point after "l"
> - press RET
>
> Only " -la" is sent to the process instead of "ls -la"
Thanks; with that I'm also able to reproduce the problem.
> I am willing to write up a patch to fix this. I'm thinking of having
> comint-mode register a function in after-change-functions to mark text
> inserted in the 'output' field as 'output'. Would this be okay or are
> there any obvious flaws with this approach?
I think that sounds like a promising approach, but I wonder whether
something could be done with rear-nonsticky here. `field' isn't
rear-sticky here for probably good reasons, but perhaps something could
be tweaked there? (I haven't actually tried, though.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-05 19:27 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 [this message]
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
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=8735n6svhn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=18135@debbugs.gnu.org \
--cc=3735@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=don@donhopkins.com \
--cc=dsb@smart.net \
--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).