unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: 10598@debbugs.gnu.org
Subject: bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually
Date: Fri, 13 Jul 2012 04:28:43 -0500	[thread overview]
Message-ID: <20479.59979.797807.988643@gargle.gargle.HOWL> (raw)
In-Reply-To: <871ukg9i6m.fsf@mail.jurta.org>

On Fri Jul 13 2012 Juri Linkov wrote:
> At least with a variable the users can do something like
> 
> (define-key dired-mode-map ";"
>   (lambda ()
>     (interactive)
>     (let ((dired-async-each nil))
>       (call-interactively 'dired-do-async-shell-command))))

Would it make sense to provide such a command for everyone? If
dired-async-each is not even intended to be customizable, I cannot
think of too many other options to use this variable in a meaningful
way. Anyway, in real life I expect that according to Murphy's Law
whatever customization a user chooses for this variable, next time
he or she needs to run dired-do-async-shell-command, the customized
value will be the wrong one.





  reply	other threads:[~2012-07-13  9:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 10:17 bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually Roland Winkler
2012-01-25 11:14 ` Juri Linkov
2012-01-25 11:47   ` Roland Winkler
2012-07-12  9:01     ` Juri Linkov
2012-07-12 10:26       ` Roland Winkler
2012-07-13  8:30         ` Juri Linkov
2012-07-13  9:28           ` Roland Winkler [this message]
2012-07-14  9:31             ` Juri Linkov
2012-07-15  7:51               ` Roland Winkler
2012-07-15  8:29                 ` Juri Linkov
2012-07-17  7:17                   ` Roland Winkler
2012-07-17 18:41                     ` Juri Linkov
2012-01-25 22:48 ` Jérémy Compostella

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=20479.59979.797807.988643@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=10598@debbugs.gnu.org \
    --cc=juri@jurta.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).