From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>, emacs-devel@gnu.org
Subject: Re: Info viewer: Links to symbol documentation
Date: Sat, 25 Apr 2020 12:15:05 +0100 [thread overview]
Message-ID: <87eesbhl52.fsf@tcd.ie> (raw)
In-Reply-To: <837dy398fs.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Apr 2020 13:16:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm)
>> Date: Tue, 21 Apr 2020 22:38:53 +0200
>>
>> I think that info documentation would be even better if there were links
>> to the function and variable documentation along the line of
>> help-mode.el. As a proof of concept I extended info.el so that Emacs'
>> Info viewer exhibits links to most symbol definitions (when they are
>> `quoted' in the documentation).
>>
>> When looking at a few Elisp and Emacs pages the verbosity and redundancy
>> of these automatic links seems not to be disturbing or too distracting.
>>
>> Maybe this draft can be extended so that references to customisation
>> buffers are working as well (as is asked for in the TODO file)...
>>
>> What are your ideas?
>
> I think this could be a useful feature, thanks1.
>
> What do others think?
+1 from me. Perhaps some users will want a toggle.
--
Basil
next prev parent reply other threads:[~2020-04-25 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 20:38 Info viewer: Links to symbol documentation H. Dieter Wilhelm
2020-04-25 10:16 ` Eli Zaretskii
2020-04-25 10:53 ` H. Dieter Wilhelm
2020-04-25 11:15 ` Basil L. Contovounesios [this message]
2020-04-25 16:04 ` Drew Adams
2020-04-25 17:22 ` H. Dieter Wilhelm
2020-04-25 17:34 ` Drew Adams
2020-04-25 12:03 ` Stefan Monnier
2020-04-25 12:22 ` Stefan Kangas
2020-04-25 13:02 ` Stefan Monnier
2020-05-03 10:51 ` H. Dieter Wilhelm
2020-05-03 14:46 ` Stefan Monnier
2020-05-03 16:02 ` H. Dieter Wilhelm
2020-04-25 13:21 ` H. Dieter Wilhelm
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=87eesbhl52.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=dieter@duenenhof-wilhelm.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 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.