unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 19116@debbugs.gnu.org
Subject: bug#19116: 25.0.50; doc string of `eval-expression'
Date: Sat, 30 Apr 2016 10:38:11 -0800 (GMT-08:00)	[thread overview]
Message-ID: <6465d7ce-bec6-4be6-9408-e1a0c8abcb64@default> (raw)
In-Reply-To: <<83eg9nneco.fsf@gnu.org>>

> > The first doc-string line should say what the command does
> > interactively:
> >
> >   Read a Lisp expression, evaluate it, and print the value in the echo area.
> >   ^^^^                    ^^^^             ^^^^^
> 
> That's exactly what it says, just in fewer words.

Nope.  2 out of 3.

It does not tell you that you are asked to input
an expression to evaluate.

I'm not inventing anything here, and it seems like you are
just being defensive about this.  This is the way we document
commands, as I'm sure you know.  We tell users that they will
be prompted for this and that, and we tell them what the
command does with what they enter.

I'm done with this.





      parent reply	other threads:[~2016-04-30 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  3:06 bug#19116: 25.0.50; doc string of `eval-expression' Drew Adams
2016-04-30 15:19 ` Lars Ingebrigtsen
2016-04-30 17:04   ` Drew Adams
2016-04-30 17:22     ` Eli Zaretskii
     [not found]   ` <<b30dc17d-8538-4aef-aa01-11b68cb8f845@default>
     [not found]     ` <<83lh3vnh8z.fsf@gnu.org>
2016-04-30 17:55       ` Drew Adams
2016-04-30 18:25         ` Eli Zaretskii
     [not found]   ` <<<b30dc17d-8538-4aef-aa01-11b68cb8f845@default>
     [not found]     ` <<<83lh3vnh8z.fsf@gnu.org>
     [not found]       ` <<f8488fbe-4e7b-4bab-b91d-7751acf610ab@default>
     [not found]         ` <<83eg9nneco.fsf@gnu.org>
2016-04-30 18:38           ` Drew Adams [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=6465d7ce-bec6-4be6-9408-e1a0c8abcb64@default \
    --to=drew.adams@oracle.com \
    --cc=19116@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    /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 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).