From: Nathanael Schweers <NSchweers@mailbox.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Referencing variables beginning with an asterisk in docstrings broken?
Date: Mon, 29 Aug 2016 01:32:41 +0200 [thread overview]
Message-ID: <87shtoeag6.fsf@reisefreund.localdomain> (raw)
In-Reply-To: <jwvy43hpsja.fsf-monnier+gmane.emacs.help@gnu.org> (Stefan Monnier's message of "Sat, 27 Aug 2016 21:55:25 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I’d like to adhere to the Common Lisp convention of naming special
>> variables in my elisp code, yet if I do so, I cannot seem to reference
>> them in docstrings.
>> Is this behaviour a bug?
>
> Probably a bug, but do note that Elisp is not Common-Lisp, so I strongly
> recommend you follow the Elisp convention of using a "<pkg>-" prefix
> instead of using asterisks for global variables.
>
>
> Stefan
>
>
I did both. I also filed a bug, but it seems that this is because of
some heuristic to prevent too many false positives. I guess I’ll either
change my naming, or just live with it. Currently I use
*prefix/public-var*, but I guess prefix/*public-var* might be even
better.
Nathanael
--
next prev parent reply other threads:[~2016-08-28 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 14:54 Referencing variables beginning with an asterisk in docstrings broken? Nathanael Schweers
2016-08-28 1:55 ` Stefan Monnier
2016-08-28 15:18 ` GDB GUD Variable Buffer Augusto Fraga Giachero
2016-08-28 15:53 ` Eli Zaretskii
2016-08-28 16:35 ` Augusto Fraga Giachero
2016-08-28 16:54 ` Eli Zaretskii
2016-08-28 23:32 ` Nathanael Schweers [this message]
2016-08-29 0:32 ` Referencing variables beginning with an asterisk in docstrings broken? Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2016-08-25 13:56 Nathanael Schweers
2016-08-25 20:19 ` 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
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=87shtoeag6.fsf@reisefreund.localdomain \
--to=nschweers@mailbox.org \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).