[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13649: boobytrapped dired-do-async-shell-command question
From: |
Juri Linkov |
Subject: |
bug#13649: boobytrapped dired-do-async-shell-command question |
Date: |
Sun, 10 Feb 2013 12:10:56 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu) |
>> A command is running in the default buffer. What to do? (k/c/r/h)
Or rather to model the prompt after `save-some-buffers-action-alist'
that asks "Save file? (y, n, !, ., q, C-r, d or C-h)" and ask:
A command is running. Kill it? (y, n, c, r, or C-h)
where the key `y' would mean to kill the running process, `c' - create
a new buffer, `r' - rename the buffer with the running process, and
`C-h' - help with the explanation of these options including `C-g':
C-g to quit (cancel the whole command);
> BTW, one more useful option would be "run it when the current command
> finishes".
IIUC, this will require adding a queue of postponed commands, and also UI
to handle them (e.g. to remove a submitted command from the queue, etc.)
bug#13649: boobytrapped dired-do-async-shell-command question, Stefan Monnier, 2013/02/08
bug#13649: boobytrapped dired-do-async-shell-command question, jidanni, 2013/02/08
bug#13649: boobytrapped dired-do-async-shell-command question, jidanni, 2013/02/10
bug#13649: boobytrapped dired-do-async-shell-command question, jidanni, 2013/02/10
bug#13649: boobytrapped dired-do-async-shell-command question, jidanni, 2013/02/10