all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 22926@debbugs.gnu.org
Subject: bug#22926: 24.5; `shell-command', `shell-command-default-error-buffer'
Date: Sun, 06 Mar 2016 19:40:04 +0200	[thread overview]
Message-ID: <83ziubv72j.fsf@gnu.org> (raw)
In-Reply-To: <97b7c9cf-83fc-4d10-8f2b-836132fcc5ca@default> (message from Drew Adams on Sun, 6 Mar 2016 07:14:47 -0800 (PST))

> Date: Sun, 6 Mar 2016 07:14:47 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> 
> 1. Doc string of `shell-command': Mention that you are prompted for the
>    command.

Done.

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

Not sure it's necessary.

> 3. In general, orient the doc a bit more toward interactive use.

Upon reading the doc string, it already is: the entire first part of
it is specifically about interactive invocations.  If you have more
specific suggestions, let's hear them.

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





  reply	other threads:[~2016-03-06 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 15:14 bug#22926: 24.5; `shell-command', `shell-command-default-error-buffer' Drew Adams
2016-03-06 17:40 ` Eli Zaretskii [this message]
2016-04-30 22:55   ` Lars Ingebrigtsen
     [not found] <<97b7c9cf-83fc-4d10-8f2b-836132fcc5ca@default>
     [not found] ` <<83ziubv72j.fsf@gnu.org>
2016-03-06 21:30   ` Drew Adams
2016-03-07 16:35     ` Eli Zaretskii
     [not found] <<<97b7c9cf-83fc-4d10-8f2b-836132fcc5ca@default>
     [not found] ` <<<83ziubv72j.fsf@gnu.org>
     [not found]   ` <<4e20bee2-3a48-44d1-8501-f19ccc660b0a@default>
     [not found]     ` <<834mciuty3.fsf@gnu.org>
2016-03-07 16:52       ` Drew Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ziubv72j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22926@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.