From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65980-done@debbugs.gnu.org
Subject: bug#65980: 30.0.50; C-e behaves surprisingly in minibuffer
Date: Sat, 16 Sep 2023 14:02:35 +0200 [thread overview]
Message-ID: <878r96iaw4.fsf@gmx.net> (raw)
In-Reply-To: <83v8caimac.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Sep 2023 10:56:27 +0300")
On Sat, 16 Sep 2023 10:56:27 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: 65980@debbugs.gnu.org
>> Date: Fri, 15 Sep 2023 14:35:50 +0200
>>
>> > Your patch changes one of the subroutines of next-line and
>> > previous-line. Those by now became very complex creatures, and handle
>> > many different cases of vertical cursor motion (with and without
>> > visual-line-mode, with and without line truncation, with and without
>> > R2L text, etc.) So I hesitate to even consider it for this obscure use
>> > case. I'd be much happier if the change was in move-beginning-of-line
>> > and move-end-of-line instead, so that it wouldn't have any chance of
>> > affecting other commands. Could you try to come up with such a change
>> > instead?
>>
>> Sure. I think the easiest way is simply to take your observation about
>> inhibit-field-text-motion and confine it to the minibuffer:
>
> Thanks, please install your first patch on the emacs-29 branch.
Done in commit 33ff4fed03d and closing the bug. Thanks.
Steve Berman
prev parent reply other threads:[~2023-09-16 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 16:51 bug#65980: 30.0.50; C-e behaves surprisingly in minibuffer Stephen Berman
2023-09-14 17:26 ` Eli Zaretskii
2023-09-14 20:37 ` Stephen Berman
2023-09-15 5:40 ` Eli Zaretskii
2023-09-15 12:35 ` Stephen Berman
2023-09-16 7:56 ` Eli Zaretskii
2023-09-16 12:02 ` Stephen Berman [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=878r96iaw4.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=65980-done@debbugs.gnu.org \
--cc=eliz@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.
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).