all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 35433@debbugs.gnu.org
Subject: bug#35433: 27.0.50; 'function' docstring: tell more about advantages?
Date: Fri, 26 Apr 2019 09:48:51 +0300	[thread overview]
Message-ID: <83h8alxnvw.fsf@gnu.org> (raw)
In-Reply-To: <874l6ll9hh.fsf@web.de> (message from Michael Heerdegen on Fri, 26 Apr 2019 05:40:42 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Fri, 26 Apr 2019 05:40:42 +0200
> 
> I wonder if we should add to the docstring of `function' that when the
> argument is a symbol, several checks are performed: it is checked
> whether the function will be defined at run-time and whether the
> function is obsolete, for example.
> 
> The current docstring doesn't suggest that function-quoting symbols has
> any advantages, but these warnings are also useful for users' init
> files, people that are not always informed what "argument is byte
> compiled" implies.

I think these details belong first and foremost to the ELisp manual.
We could also add a shortened version to the doc string, but I'd like
first to see the full version in the manual.

Thanks.





  reply	other threads:[~2019-04-26  6:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  3:40 bug#35433: 27.0.50; 'function' docstring: tell more about advantages? Michael Heerdegen
2019-04-26  6:48 ` Eli Zaretskii [this message]
2019-04-27  8:30   ` Michael Heerdegen
2019-04-27  8:47     ` Eli Zaretskii
2019-05-22 23:39       ` Michael Heerdegen
2019-05-23  4:43         ` Eli Zaretskii
2019-05-23 16:55           ` Michael Heerdegen
2019-05-23 18:31             ` Eli Zaretskii
2019-05-23 23:18               ` Michael Heerdegen
2019-05-24  6:42                 ` Eli Zaretskii

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=83h8alxnvw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35433@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.