Subject: RE: bug#22926: 24.5; `shell-command', `shell-command-default-error-buffer'

From: Drew Adams <[email-masked]>
Date: Sun, 6 Mar 2016 13:30:59 -0800 (PST)

> > 1. Doc string of `shell-command': Mention that you are prompted
> >    for the command.
> 
> Done.

Thx.

> > 2. `shell-command-default-error-buffer': Make it a user option.
> 
> Not sure it's necessary.

Why should it be an internal variable?  Did you check how it is used?

> > 4. Also, some lines in the doc string are too long (but not by
> >    much: 74 chars max instead of 70).
> 
> I don't see how this can be helped, as those lines generally
> reference symbols with long names.

Huh?  This is the longest line (but the mailer will perhaps wrap it):

 `start-process' directly, since it offers more control and does not impose

This is the second longest:

 In an interactive call, the variable `shell-command-default-error-buffer'

This the third longest:

 insert output in current buffer.  (This cannot be done asynchronously.)

None of those involves a symbol whose name is 68 or more chars.
They can all be shortened to 70 chars or less.

(All the other lines are 70 chars or less.)