unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: 4987@emacsbugs.donarmstrong.com
Cc: trentbuck@gmail.com
Subject: bug#4987: 23.1; shell-command: optionally include working dir in prompt
Date: Sun, 22 Nov 2009 12:29:20 +0200	[thread overview]
Message-ID: <87vdh33qdj.fsf@mail.jurta.org> (raw)
In-Reply-To: <87bpixt8ja.fsf@mail.jurta.org> (Juri Linkov's message of "Fri, 20 Nov 2009 19:27:21 +0200")

> > At http://namazu.org/~tsuchiya/elisp/shell-command.el is an emacs
> > library that "enables tab-completion for `shell-command'".
> >
> > I noticed recently that Emacs does this internally now.  Yay!  But one
> > thing shell-command.el did that Emacs 23 doesn't appear to do, is to
> > include the working directory in the shell-command and
> > dired-do-shell-command prompts.  It'd be neat if Emacs did that, too.
>
> shell-command.el relies on defadvices to implement this.  I think a clean
> implementation should be designed to work more like minibuf-eldef.el.

On second thought, there is no need to over-complicate this feature.
So we could add a new defcustom to define the prompt format and to
use it in `read-shell-command' to modify the prompt.

-- 
Juri Linkov
http://www.jurta.org/emacs/





  reply	other threads:[~2009-11-22 10:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 12:57 bug#4987: 23.1; shell-command: optionally include working dir in prompt trentbuck
2009-11-20 17:27 ` Juri Linkov
2009-11-22 10:29   ` Juri Linkov [this message]
2009-11-23  4:27     ` Stefan Monnier
2019-10-10 23:20 ` Stefan Kangas
2019-10-11  0:31   ` Trent W. Buck
2019-10-11  8:14   ` Eli Zaretskii
2019-10-11 11:03     ` Stefan Kangas
2019-10-11 12:04       ` Michael Albinus
2019-10-11 13:30         ` Stefan Kangas
2019-10-11 14:26           ` Michael Albinus
2019-10-11 14:35           ` Robert Pluim
2019-10-12  8:12             ` Stefan Kangas
2019-10-14  9:32               ` Robert Pluim
2019-10-17 10:57                 ` Stefan Kangas

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=87vdh33qdj.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=4987@emacsbugs.donarmstrong.com \
    --cc=trentbuck@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).