unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Peter Dean <laszlomail@protonmail.com>
Cc: 46702@debbugs.gnu.org
Subject: bug#46702: Link symbol name in Help
Date: Mon, 22 Feb 2021 16:01:35 +0100	[thread overview]
Message-ID: <874ki4kuy8.fsf@gnus.org> (raw)
In-Reply-To: <HodoNB8z2mwNTAHcXZq4pyTFlxvDzJjDAJAASw4RMe9k5vrs34HDSudkDXyI03TMIS5IVxHDV5vtO-9kPoA_psYSsYtJrqNr3a7ryYy9l-w=@protonmail.com> (Peter Dean's message of "Mon, 22 Feb 2021 06:05:09 +0000")

Peter Dean <laszlomail@protonmail.com> writes:

> Demonstrated here with the scratch buffer, showing that
> lisp-interaction-mode is not linked in the second line:
>
>    https://i.imgur.com/KIWQE60.png

This is due to this code:

(defun help-make-xrefs (&optional buffer)
[...]
      (goto-char (point-min))
      ;; Skip the header-type info, though it might be useful to parse
      ;; it at some stage (e.g. "function in `library'").
      (forward-paragraph)

Anybody know what the rationale behind this is?  I in complex values,
there may be false positives, but...  I tried just removing that bit and
looking at a couple of variables, and it fixes the problem described
here, and I didn't see any regressions.

Complex variable values aren't displayed here (but at the end of the
buffer), so that shouldn't be a problem.

Any opinions?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2021-02-22 15:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  6:05 bug#46702: Link symbol name in Help Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22  8:21 ` Andreas Schwab
2021-02-22  8:26   ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22  8:38     ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 15:01 ` Lars Ingebrigtsen [this message]
2021-02-22 15:55   ` Eli Zaretskii
2021-02-22 21:34     ` Lars Ingebrigtsen
2021-02-22 21:52       ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 21:58         ` Lars Ingebrigtsen
2021-02-22 22:08           ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-23  3:28         ` Eli Zaretskii
2021-02-23  7:09           ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-23 15:31             ` Eli Zaretskii
2021-02-24 16:09               ` Lars Ingebrigtsen
2021-02-24 16:29                 ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-24 16:38                   ` Eli Zaretskii
2021-02-24 16:59                     ` Lars Ingebrigtsen
2021-02-24 17:05                       ` Eli Zaretskii
2021-02-25 15:15                         ` Lars Ingebrigtsen
2021-02-25 15:29                           ` 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

  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=874ki4kuy8.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46702@debbugs.gnu.org \
    --cc=laszlomail@protonmail.com \
    /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).