GNU bug report logs - #6857
shell-command should say where it is talking about

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6857 in the body.
You can then email your comments to 6857 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Subject: shell-command should say where it is talking about
Date: Sun, 15 Aug 2010 01:38:41 +0800

       M-! (translated from <escape> !) runs the command shell-command, which
       is an interactive compiled Lisp function in `simple.el'.

OK, but in its error message,

    (Shell command failed with code 99 and some error output)

you had better tell the user just what buffer to look for that error
output in, lest he have to figure it out himself. Not impossible but not
friendly. emacs-version "24.0.50.1".

Message #8 received at 6857 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: jidanni <at> jidanni.org
Cc: 6857 <at> debbugs.gnu.org
Subject: Re: bug#6857: shell-command should say where it is talking about
Date: Sat, 02 Jul 2011 16:00:09 +0200

jidanni <at> jidanni.org writes:

>        M-! (translated from <escape> !) runs the command shell-command, which
>        is an interactive compiled Lisp function in `simple.el'.
>
> OK, but in its error message,
>
>     (Shell command failed with code 99 and some error output)
>
> you had better tell the user just what buffer to look for that error
> output in, lest he have to figure it out himself. Not impossible but not
> friendly. emacs-version "24.0.50.1".

In what cases do you get an error message saying

   (Shell command failed with code 99 and some error output)

?

I get error messages like:

/bin/bash: lala: command not found

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Message #11 received at 6857 <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: larsi <at> gnus.org
Cc: 6857 <at> debbugs.gnu.org
Subject: Re: bug#6857: shell-command should say where it is talking about
Date: Sun, 03 Jul 2011 04:42:58 +0800

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi <at> gnus.org> writes:
LMI> jidanni <at> jidanni.org writes:

>> M-! (translated from <escape> !) runs the command shell-command, which
>> is an interactive compiled Lisp function in `simple.el'.
>> 
>> OK, but in its error message,
>> 
>> (Shell command failed with code 99 and some error output)
>> 
>> you had better tell the user just what buffer to look for that error
>> output in, lest he have to figure it out himself. Not impossible but not
>> friendly. emacs-version "24.0.50.1".

LMI> In what cases do you get an error message saying

LMI>    (Shell command failed with code 99 and some error output)

LMI> ?

LMI> I get error messages like:

LMI> /bin/bash: lala: command not found
I see. I set
(setq shell-command-default-error-buffer "shell-command-errors")
to avoid stderr and stdout being jumbled.

Therefore code like

	    (let ((output
		   (if (and error-file
			    (< 0 (nth 7 (file-attributes error-file))))
		       "some error output"
		     "no output")))

needs to mention shell-command-default-error-buffer if set, to the user.

Message #18 received at 6857 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: jidanni <at> jidanni.org
Cc: 6857 <at> debbugs.gnu.org
Subject: Re: bug#6857: shell-command should say where it is talking about
Date: Sat, 02 Jul 2011 23:02:13 +0200

jidanni <at> jidanni.org writes:

> Therefore code like
>
> 	    (let ((output
> 		   (if (and error-file
> 			    (< 0 (nth 7 (file-attributes error-file))))
> 		       "some error output"
> 		     "no output")))
>
> needs to mention shell-command-default-error-buffer if set, to the user.

Ok; fixed now.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.