From: Eli Barzilay <eli@barzilay.org>
To: 21737@debbugs.gnu.org
Cc: Chong Yidong <cyd@gnu.org>, Le Wang <l26wang@gmail.com>
Subject: bug#21737: 24.5; Minor feature request: `comint-previous-matching-input-from-input' and point
Date: Thu, 22 Oct 2015 16:29:15 -0400 [thread overview]
Message-ID: <22057.18203.537000.988338@gargle.gargle.HOWL> (raw)
`comint-previous-matching-input-from-input' used to insert a match and
leave the point at the end of the line. I found that behavior much
better than zsh and bash since when recalling old commands I edit the
last part of the command much more often. (In fact, I think that
comint used to leave the point where it was years ago, since I
remember having to tweak emacs to put it at the end.)
A few years ago, there was a bug & a patch reported by Le Wang about
keeping the point at the same place -- something that I find really
annoying... The problem with this patch is that it has no option to
leave the point at the end, forcing me to duplicate the whole function
if I want that behavior.
So, this is a feature request to add such an option with a new custom
variable.
--
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next reply other threads:[~2015-10-22 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 20:29 Eli Barzilay [this message]
[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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22057.18203.537000.988338@gargle.gargle.HOWL \
--to=eli@barzilay.org \
--cc=21737@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=l26wang@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 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.