Re: Why should shell-command-on-region call kill-buffer?
On Sun, Jun 30, 2002 at 08:11:48AM +0200, Hrvoje Niksic wrote:
Olivier Galibert <galibert(a)pobox.com> writes:
> What is the reason for that kill-buffer? I see nothing in the
> documentation telling that the no output case is special...
I can only assume that the idea was that an empty output buffer was
not of much use to anyone and would only get in the way of
completions, etc. That's tenuous, but it's the best I can come up
with. I don't think that kill-buffer is a recent addition.
Did it actually caus problems for you?
It's just making a bug weirder than expected.
package-admin-add-binary-package fails with "Invalid operation:
Selecting deleted or non-existent buffer". What really happens is
that the contents of the output buffer are somehow lost in
call-process-internal, and the kill-buffer kicks in. Of course, the
output should not be lost in the first place.
OG.