From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 71728@debbugs.gnu.org
Subject: bug#71728: previous-line-or-history-element should put cursor at end, like comint-previous-input
Date: Sun, 23 Jun 2024 16:50:04 +0300 [thread overview]
Message-ID: <86a5jbepkj.fsf@gnu.org> (raw)
In-Reply-To: <87bk3raieo.3.fsf@jidanni.org> (message from Dan Jacobson on Sun, 23 Jun 2024 21:38:23 +0800)
> From: Dan Jacobson <jidanni@jidanni.org>
> Cc: 71728@debbugs.gnu.org
> Date: Sun, 23 Jun 2024 21:38:23 +0800
>
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> >> From: Dan Jacobson <jidanni@jidanni.org>
> >> ! ;; dired-do-shell-command
> >> l ;; self-insert-command
> >> s ;; self-insert-command
> >> <return> ;; exit-minibuffer
> >> ! ;; dired-do-shell-command
> >> <up> ;; previous-line-or-history-element
> >> C-e ;; move-end-of-line
> >> SPC ;; self-insert-command
> >> - ;; self-insert-command
> >> a ;; self-insert-command
> >> <return> ;; exit-minibuffer
> >> ! ;; dired-do-shell-command
> >> <up> ;; previous-line-or-history-element
> >> C-e ;; move-end-of-line
> >> l ;; self-insert-command
> >> <return> ;; exit-minibuffer
>
> EZ> If you don't like the current heuristics, use M-p instead of the <UP> arrow.
>
> Alas, in my above example, M-p behaves exactly the same as <up>.
So you are complaining about the usual Emacs behavior of vertical
motion, which keeps the column? Why should Emacs go to EOL in this
particular case when it doesn't do that in any other buffer/window?
next prev parent reply other threads:[~2024-06-23 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 23:16 bug#71728: previous-line-or-history-element should put cursor at end, like comint-previous-input Dan Jacobson
2024-06-23 5:37 ` Eli Zaretskii
2024-06-23 13:38 ` Dan Jacobson
2024-06-23 13:50 ` Eli Zaretskii [this message]
2024-06-23 14:05 ` Dan Jacobson
2024-06-23 14:09 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a5jbepkj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71728@debbugs.gnu.org \
--cc=jidanni@jidanni.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.