unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 62300@debbugs.gnu.org
Subject: bug#62300: 29.0.60; No hyperlinks for some symbols in *Help* buffers
Date: Tue, 21 Mar 2023 15:11:42 +0200	[thread overview]
Message-ID: <83lejq6ygh.fsf@gnu.org> (raw)
In-Reply-To: <jwvsfdzglj8.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 20 Mar 2023 17:55:40 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 62300@debbugs.gnu.org
> Date: Mon, 20 Mar 2023 17:55:40 -0400
> 
> >>   emacs -Q
> >>   C-h f global-text-scale-adjust RET
> >> 
> >> Observe that in the *Help* buffer the variable
> >> global-text-scale-adjust-resizes-frames does not have the link
> >> appearance.  This is because:
> >> 
> >>   (boundp 'global-text-scale-adjust-resizes-frames) => nil
> 
> `help-definition-prefixes` and friends
> (`help-enable-completion-autoload`, ...) are the result of a tradeoff:
> we offer to autoload files "on demand" but the "demand" is often
> vague/implicit, so we have to judge when the demand is clear enough to
> justify loading a file and when it's not.
> 
> If we're too trigger happy, we can end up auto-loading all the .el files
> in sight, making Emacs unnecessarily bigger&slower (and increasing the
> risk that we bump into a file that breaks the convention, such as
> `c-ts-mode`).
> 
> In this case, `global-text-scale-adjust` has an explicit autoload in
> `loaddefs.el` so we already have the docstring needed to display
> `C-h f global-text-scale-adjust RET` without having to load
> `face-remap.el`, so `help-enable-completion-autoload` doesn't load
> `face-remap.el`.

So you are saying that the only way of having
global-text-scale-adjust-resizes-frames decorated as a link is to
autoload it?  Even though autoloading defcustoms is frowned upon?  Or
is there a better way?





  reply	other threads:[~2023-03-21 13:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 18:34 bug#62300: 29.0.60; No hyperlinks for some symbols in *Help* buffers Eli Zaretskii
2023-03-20 18:52 ` Eli Zaretskii
2023-03-20 21:55   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 13:11     ` Eli Zaretskii [this message]
2023-03-21 14:19       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 17:26         ` Eli Zaretskii
2023-03-21 17:59           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 18:23             ` Eli Zaretskii
2023-03-21 19:09               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 19:54                 ` Eli Zaretskii
2023-03-22  1:48                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-22 15:52                     ` 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=83lejq6ygh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62300@debbugs.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.
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).