[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files i
From: |
Roland Winkler |
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 |
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.
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Juri Linkov, 2012/07/12
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Roland Winkler, 2012/07/12
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Juri Linkov, 2012/07/13
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually,
Roland Winkler <=
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Juri Linkov, 2012/07/14
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Roland Winkler, 2012/07/15
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Juri Linkov, 2012/07/15
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Roland Winkler, 2012/07/17
- bug#10598: 24.0.92; run dired-do-async-shell-command on multiple files individually, Juri Linkov, 2012/07/17