all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "Roland Winkler" <winkler@gnu.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 11:30:10 +0300	[thread overview]
Message-ID: <871ukg9i6m.fsf@mail.jurta.org> (raw)
In-Reply-To: <20478.42579.593253.620476@lukas.physics.niu.edu> (Roland Winkler's message of "Thu, 12 Jul 2012 05:26:27 -0500")

>> +(defvar dired-async-each t
>
> Should this possibly be defcustom? I'd consider this a user option.

I can't imagine anyone wanting to customize it on a permanent basis
because the desirable behavior depends on the type of executed command:
non-interactive programs are better to run sequentially,
but programs with GUI are better to run in parallel.

Ideally this preference should be expressed by syntax
on the command line like using special symbols `*' and `?',
but at the moment I have no idea for such a syntax.

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))))





  reply	other threads:[~2012-07-13  8:30 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 [this message]
2012-07-13  9:28           ` Roland Winkler
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871ukg9i6m.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=10598@debbugs.gnu.org \
    --cc=winkler@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.