GNU bug report logs -
#380
previous-matching-history-element beef up
Previous Next
Reported by: jidanni <at> jidanni.org
Date: Mon, 9 Jun 2008 18:15:03 UTC
Severity: wishlist
Tags: fixed
Fixed in version 27.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 380 in the body.
You can then email your comments to 380 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#380
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
jidanni <at> jidanni.org
:
New bug report received and forwarded. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):
Let's examine today the docstring for
M-r (translated from <escape> r) runs the command previous-matching-history-element
which is an interactive compiled Lisp function in `simple.el'.
It is bound to M-r.
(previous-matching-history-element REGEXP N)
Find the previous history element that matches REGEXP.
(Previous history elements refer to earlier actions.)
With prefix argument N, search for Nth previous match.
If N is negative, find the next or Nth next match.
Normally, history elements are matched case-insensitively if
`case-fold-search' is non-nil, but an uppercase letter in REGEXP
makes the search case-sensitive.
See also `minibuffer-history-case-insensitive-variables'.
OK, but what about when you want to search further back again: mention that you
just hit a second M-r RET...
And when one does hit that second M-r, it would be nice if the prompt
would show what the current default search string is. All it ever says is
"Previous element matching (regexp): " though indeed it remembers a
default all the time at least after first use.
Indeed it might even also say "found on history item 432" or "found at
18% of history" upon finding something, but maybe that's too verbose.
Also some of us would like C-r to "bust through" into previous lines,
so we don't have to use the less familiar M-r (ESC r for us old dogs
who never learned new ALT tricks). Maybe make a variable to allow
that.
All the above also applies to M-s.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#380
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Stefan Monnier <monnier <at> iro.umontreal.ca>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #10 received at 380 <at> emacsbugs.donarmstrong.com (full text, mbox):
tag 380 +wishlist
thanks
> And when one does hit that second M-r, it would be nice if the prompt
> would show what the current default search string is. All it ever says is
> "Previous element matching (regexp): " though indeed it remembers a
> default all the time at least after first use.
Indeed, it should probably use the " (default <foo>)" convention.
But maybe that would be impractical because the prompt would then be
too long.
> Also some of us would like C-r to "bust through" into previous lines,
> so we don't have to use the less familiar M-r (ESC r for us old dogs
> who never learned new ALT tricks). Maybe make a variable to allow
> that.
I don't know what you mean by "bust through", but in Emacs-23, C-s and
C-r (i.e. isearch) will automatically jump through the history to find
the next match. Maybe that's what you meant.
Stefan
Severity set to `wishlist' from `normal'
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> emacsbugs.donarmstrong.com
.
(Sat, 28 Jun 2008 01:10:05 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#380
; Package
emacs
.
(Sun, 13 Oct 2019 05:16:02 GMT)
Full text and
rfc822 format available.
Message #15 received at 380 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>> And when one does hit that second M-r, it would be nice if the prompt
>> would show what the current default search string is. All it ever says is
>> "Previous element matching (regexp): " though indeed it remembers a
>> default all the time at least after first use.
>
> Indeed, it should probably use the " (default <foo>)" convention.
> But maybe that would be impractical because the prompt would then be
> too long.
It's a bit on the long side, but I think it helps usability a lot, so
I've made this change on the trunk now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) fixed.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sun, 13 Oct 2019 05:16:02 GMT)
Full text and
rfc822 format available.
bug marked as fixed in version 27.1, send any further explanations to
380 <at> debbugs.gnu.org and jidanni <at> jidanni.org
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sun, 13 Oct 2019 05:16:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 10 Nov 2019 12:24:17 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 140 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.