From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: make `occur' use word at point as default
Date: Mon, 29 Aug 2005 12:33:32 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGECGCMAA.drew.adams@oracle.com> (raw)
In-Reply-To: <2gpsrwr6b6.fsf@tiscali.de>
> The command `occur' currently uses the last item in the regexp
> history as the default value.
> Please do not change that. Peopel are accustomed to just typing RET
> to search for the same thing again.
That's a good point.
But the problem remains: too often I have to first mark a word
or symbol, copy the region, start a command..., paste it, press
<enter>. That's three keystrokes too many. How do other people
accomplish this?
I think something like isearch's "C-w" and friends extended to other
commands which read from the minibuffer would be useful.
Opinions?
FWIW (since you asked), here is my (singleton, heretical) opinion (again):
1. I prefer to access previous values ("search for the same thing again")
via the history list - only. That's not what the default value is for, IMO.
I agree with Emilio that the default value in the `occur' case should
reflect the current word/symbol, not the last-used value. It's not hard to
hit `M-p' to "search again".
2. I prefer to have the default value placed in the minibuffer
automatically, as input - that is, as INIT-VALUE. Yes, that means that I
must empty the minibuffer (one keystroke), if the default value is not
something I want to use. More often than not, however, I do use it, perhaps
modifying it first.
3. I also cycle among the other `completing-read' "default" values, using
the arrow keys, treating them the same way as the default value (possibly
editing, re-completing, etc.). I use a library that lets me cycle, match,
and complete such values either by prefix (normal completion) or by regexp.
next prev parent reply other threads:[~2005-08-29 19:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 12:37 make `occur' use word at point as default Emilio Lopes
2005-08-29 8:39 ` Richard M. Stallman
2005-08-29 17:39 ` Emilio Lopes
2005-08-29 19:33 ` Drew Adams [this message]
2005-08-29 20:07 ` David Kastrup
2005-08-30 7:57 ` Mathias Dahl
2005-08-30 13:43 ` Kai Großjohann
2005-08-31 14:35 ` Richard M. Stallman
2005-08-31 16:03 ` Drew Adams
2005-09-01 15:52 ` Richard M. Stallman
2005-09-01 17:09 ` Drew Adams
2005-09-01 19:29 ` Juri Linkov
2005-09-01 23:59 ` Drew Adams
2005-09-03 1:41 ` Richard M. Stallman
2005-09-03 2:01 ` Drew Adams
2005-09-03 2:04 ` Drew Adams
2005-09-03 13:33 ` Benjamin Riefenstahl
2005-09-04 0:58 ` Richard M. Stallman
2005-09-06 15:19 ` Drew Adams
2005-09-07 5:05 ` Richard M. Stallman
2005-09-07 5:25 ` Drew Adams
2005-09-07 5:46 ` Juri Linkov
2005-09-08 2:41 ` Richard M. Stallman
2005-09-07 5:27 ` Juri Linkov
2005-09-01 5:47 ` Juri Linkov
2005-09-01 13:08 ` Stefan Monnier
2005-09-01 19:29 ` Juri Linkov
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=DNEMKBNJBGPAOPIJOOICGECGCMAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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).