From: Juri Linkov <juri@linkov.net>
To: Stephen Perry <stevoooo@gmail.com>
Cc: John Wiegley <jwiegley@gmail.com>, 21737@debbugs.gnu.org
Subject: bug#21737: Acknowledgement (24.5; Minor feature request: `comint-previous-matching-input-from-input' and point)
Date: Thu, 19 Nov 2015 02:33:32 +0200 [thread overview]
Message-ID: <87fv02keab.fsf@mail.linkov.net> (raw)
In-Reply-To: <8D94ED5A-0304-479A-A1EC-AD5768EA206D@gmail.com> (Stephen Perry's message of "Tue, 17 Nov 2015 13:08:29 +0000")
>> I wonder could we use the logic of 'track-eol' here? This means that going
>> to the previous command lines starting at the end of the command line will
>> keep to the ends of command lines.
>
> It’s a trivial change to make, but I’m not sure if having it do
> the same thing will be annoying for people who don’t want
> track-eol turned on everywhere?
We have it working this way in navigating the minibuffer's history,
so users are already accustomed to this behavior.
next prev parent reply other threads:[~2015-11-19 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 20:29 bug#21737: 24.5; Minor feature request: `comint-previous-matching-input-from-input' and point Eli Barzilay
[not found] ` <handler.21737.B.14455457715661.ack@debbugs.gnu.org>
2015-10-22 20:42 ` bug#21737: Acknowledgement (24.5; Minor feature request: `comint-previous-matching-input-from-input' and point) Eli Barzilay
2015-10-23 6:26 ` bug#21737: 24.5; Minor feature request: `comint-previous-matching-input-from-input' and point Eli Zaretskii
2015-11-13 22:30 ` bug#21737: Acknowledgement (24.5; Minor feature request: `comint-previous-matching-input-from-input' and point) Stephen Perry
2015-11-16 16:50 ` John Wiegley
2015-11-16 18:55 ` Stephen Perry
2015-11-17 0:58 ` Juri Linkov
2015-11-17 13:08 ` Stephen Perry
2015-11-19 0:33 ` Juri Linkov [this message]
2020-09-17 17:42 ` Lars Ingebrigtsen
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=87fv02keab.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=21737@debbugs.gnu.org \
--cc=jwiegley@gmail.com \
--cc=stevoooo@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).