From: Eli Zaretskii <eliz@gnu.org>
To: Nathanael Schweers <NSchweers@mailbox.org>
Cc: 24309@debbugs.gnu.org
Subject: bug#24309: 25.1; Problem in variable reference in docstrings.
Date: Fri, 26 Aug 2016 11:55:54 +0300 [thread overview]
Message-ID: <83vayndi3p.fsf@gnu.org> (raw)
In-Reply-To: <87poowfnxh.fsf@reisefreund.localdomain> (message from Nathanael Schweers on Fri, 26 Aug 2016 01:07:06 +0200)
> From: Nathanael Schweers <NSchweers@mailbox.org>
> Date: Fri, 26 Aug 2016 01:07:06 +0200
>
>
> This bug applies to both the version given in the description
> (i.e. 25.1-RC2) and version 24.5 distributed on fedora.
Actually, Emacs has behaved like that since creation of hyper-links to
quoted symbols in doc strings was introduced in Emacs 20.3.
> - Start Emacs with “emacs -Q”.
> - evaluate these forms:
> (defvar var "var" "docstring of var")
> (defvar var* "var*" "docstring of var*")
> (defvar *var "*var" "docstring of *var")
> (defvar *var* "*var*" "docstring of *var*")
>
> (defun fun0 () "see variable ‘var’." var)
> (defun fun1 () "see var*iable ‘var*’." var*)
> (defun fun2 () "see *variable ‘*var’." *var)
> (defun fun3 () "see *var*iable ‘*var*’." *var*)
> - See the docstrings of the defined functions. For fun0 and fun1 the
> reference to the variable is correct, for fun2 and fun3 they are not.
See help-xref-symbol-regexp, it requires that the first character
after the opening quote has the word syntax, not the symbol syntax. I
don't know why is that, perhaps to avoid too many false positives or
something. The comment there says this was done deliberately.
next prev parent reply other threads:[~2016-08-26 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 23:07 bug#24309: 25.1; Problem in variable reference in docstrings Nathanael Schweers
2016-08-26 8:55 ` Eli Zaretskii [this message]
2019-11-08 3:48 ` Stefan Kangas
2020-12-27 19:51 ` Basil L. Contovounesios
2020-12-27 20:01 ` Basil L. Contovounesios
2020-12-27 22:15 ` Lars Ingebrigtsen
2021-01-10 13:50 ` Basil L. Contovounesios
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=83vayndi3p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24309@debbugs.gnu.org \
--cc=NSchweers@mailbox.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).