all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>, 19932@debbugs.gnu.org
Subject: bug#19932: 25.0.50; doc string of `elisp--eval-last-sexp'
Date: Tue, 24 Feb 2015 13:26:23 -0800 (PST)	[thread overview]
Message-ID: <a8ea75d4-f924-44d9-89ca-bce74a30dd20@default> (raw)
In-Reply-To: <54ECE6C3.3000602@yandex.ru>

> > .. should not mention the prefix arg.  This is not a command, and the
> > function code does not access `current-prefix-arg'.
> 
> Maybe it should just be undocumented. It's a private function, and it
> duplicates the docstring of its only caller.

Maybe it should be documented properly.  Emacs is the self-documenting
editor.  Maybe developers should drop the bad habit of thinking of
documentation as only a chore and as only for others.

There is nothing "private" in Emacs Lisp - this is not Java or C++.
And even Emacs "internal" developers deserve to take advantage of
the self-documentation Emacs is intended to provide.

The duplication of its caller's docstring is the bug - it should
have its own documentation.





  reply	other threads:[~2015-02-24 21:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 21:20 bug#19932: 25.0.50; doc string of `elisp--eval-last-sexp' Drew Adams
2015-02-24 21:01 ` Dmitry Gutov
2015-02-24 21:26   ` Drew Adams [this message]
2015-02-25  4:06   ` Stefan Monnier
2015-02-25 10:52   ` Nicolas Richard
2015-02-25 11:17     ` Dmitry Gutov
2015-02-25 12:12       ` Nicolas Richard
2015-02-25 12:44         ` Dmitry Gutov
2015-02-25 15:18           ` Nicolas Richard
2015-02-25 16:39         ` Drew Adams
2015-02-25 16:36     ` Drew Adams
2015-02-25 16:39       ` Dmitry Gutov
2015-02-25 16:45         ` Drew Adams
2015-02-25 16:49       ` Nicolas Richard
2015-02-25 17:05         ` 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=a8ea75d4-f924-44d9-89ca-bce74a30dd20@default \
    --to=drew.adams@oracle.com \
    --cc=19932@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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.