unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 25462@debbugs.gnu.org
Subject: bug#25462: Out of date doc string for "`".
Date: Tue, 17 Jan 2017 20:05:39 +0000	[thread overview]
Message-ID: <20170117200539.GB4169@acm.fritz.box> (raw)
In-Reply-To: <CAM-tV-_L4hOe9XV7aSFYRjaQ1xG_ve6KbD26w5C6PZorB0Y26A@mail.gmail.com>

Hello, Noam.

On Mon, Jan 16, 2017 at 04:52:36PM -0500, Noam Postavsky wrote:
> On Mon, Jan 16, 2017 at 4:30 PM, Alan Mackenzie <acm@muc.de> wrote:
> > Hello, Emacs.

> > The doc string for "`" has become partial.

> > It fails to mention that "`" has a radically different meaning when used
> > in certain parts of a `pcase', and probably quite a few other similar
> > macros.

> I don't think that makes sense. Similarly, we don't add a mention of
> `cl-loop's use of `if' in the docstring of `if', because that's not
> part of the `if' special form. It's just a use of `if' as a plain
> symbol.

I don't think `if' inside cl-loop is liable to cause much confusion.
pcase, on the other hand, does cause confusion, as it radically changes
the meaning of symbols contained within it, something that other macros
don't do - with the possible minor exception of cl-loop.

If you can think of any other such examples of context dependence
changing the semantics, I think these should be documented too.

The direction I'm coming from is to make the doc strings help users -
not to make them 100% consistent.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2017-01-17 20:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 21:30 bug#25462: Out of date doc string for "`" Alan Mackenzie
2017-01-16 21:52 ` Noam Postavsky
2017-01-17 20:05   ` Alan Mackenzie [this message]
2017-01-18  2:04     ` npostavs
2017-01-17 21:17   ` John Mastro
2017-01-18 20:55     ` Alan Mackenzie
2017-01-18 22:14       ` Noam Postavsky
2017-01-18 20:40   ` Alan Mackenzie
2021-09-25 16:12 ` Stefan Kangas
2021-09-26  6:46   ` Lars Ingebrigtsen
2021-09-26  7:17     ` Stefan Kangas
2021-09-26 20:31       ` Alan Mackenzie

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=20170117200539.GB4169@acm.fritz.box \
    --to=acm@muc.de \
    --cc=25462@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).