unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Tom <adatgyujto@gmail.com>, emacs-devel@gnu.org
Subject: RE: A smarter command history
Date: Sun, 26 Jan 2014 10:53:04 -0800 (PST)	[thread overview]
Message-ID: <8cbefaa1-b801-4274-b279-ea75ee8bcd30@default> (raw)
In-Reply-To: <loom.20140126T175121-200@post.gmane.org>

> > > For example, in grep's case the command history would look
> > > like this after the fix:
> > >   (let ((default-directory "/home/me/projx"))
> > >     (grep "grep -n -i test"))
> >
> > That could also be problematic if the user wants to run the same
> > grep in various directory.
> 
> Deleting things is easy and in my experience in most of the
> cases I want to run the same grep query in the same directory.

Sounds like a reason _not_ to implement what you asked for:
YAGNI, if you typically run the same grep query in the same dir.

Your reason for the request was that it is a nuisance to change
directory:

>> This is useful to repeat a previous grep command later,
>> but you have to switch to the directory first if you want
>> to run grep in the same directory as previously.

FWIW, I'd suggest that Emacs command `cd' provide a reasonable
minibuffer history list: the directory names previously entered
from the minibuffer.  That is not the case currently - all
entered file and directory names are in the history.

(To change to a subdir, `cd' completion is quick.)



  reply	other threads:[~2014-01-26 18:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25 16:53 A smarter command history Tom
2014-01-25 21:55 ` Stefan Monnier
2014-01-26 16:53   ` Tom
2014-01-26 18:53     ` Drew Adams [this message]
2014-01-26 19:13       ` Tom

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=8cbefaa1-b801-4274-b279-ea75ee8bcd30@default \
    --to=drew.adams@oracle.com \
    --cc=adatgyujto@gmail.com \
    --cc=emacs-devel@gnu.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 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).