unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* `shell-command-on-region' behaviour changed
@ 2010-04-06 13:50 Leo
  0 siblings, 0 replies; only message in thread
From: Leo @ 2010-04-06 13:50 UTC (permalink / raw)
  To: emacs-devel

Hello all,

I have noticed blank *Shell Command Output* buffer appears frequently
for quite a while. I keep deleting it since it appears in almost every
buffer switching in ido.

This is due to shell-command-on-region no longer respects its
well-documented and established behaviour of deleting that output buffer
when there's no output. The document still says so by the way.

I think the documented behaviour is better.

`shell-command-on-region' and `shell-command' have more noninteractive
uses than interactive ones. Many emacs packages authors rely on this
behaviour by ignoring the output-buffer arg to shell-command. Due to
this change packages like dired (its dired-do-shell-command) starts
leaving a blank buffer. And the doc string already says *Shell Command
Output* is shared if output buffer is unspecified.

I am unclear about what use case the changed behaviour tries to cover.
But the change will be better if it only affects non-programming use of
shell-command/shell-command-on-region, i.e. by using a different
output-buffer for interactive use.

I only use M-! or M-| for simple shell scripting and I am only
interested in the output for that moment at least for 99% of the cases.

Leo





^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-04-06 13:50 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-06 13:50 `shell-command-on-region' behaviour changed Leo

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