GNU bug report logs - #52973
Adding a few context-menu-mode commands

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: larsi <at> gnus.org, 52973 <at> debbugs.gnu.org, philipk <at> posteo.net
Subject: bug#52973: Adding a few context-menu-mode commands
Date: Thu, 13 Jan 2022 12:06:21 +0200

> From: Juri Linkov <juri <at> linkov.net>
> Cc: larsi <at> gnus.org,  philipk <at> posteo.net,  52973 <at> debbugs.gnu.org
> Date: Thu, 13 Jan 2022 10:39:25 +0200
> 
> >> > When will that load these packages?  When context-menu-mode is turned
> >> > on, when the menu is actually popped up, or something else?
> >>
> >> When the menu is popped up the first time.
> >
> > Then why is that a problem?
> 
> The problem is that irrelevant packages will be loaded by default.

They aren't irrelevant: the user wants to use their context-menu
entries.  How is this different from when the user customizes some
option that belongs to a package, or displays its documentation?

> > We could alternatively only have these items when the corresponding
> > package is loaded, but you rejected that possibility, AFAIU.
> 
> This means there are no hi-lock/man items by default.

The same will happen under your suggestion, won't it?

> Then once the user used `M-x man' or `M-x highlight-regexp',
> these items will surprisingly appear in the global menu.

That's no more surprising that having, e.g.,

  M-: (setq FOO- TAB

complete on variables from the package FOO only after it's loaded.

> This makes no sense, there are no such magic things happened
> on the menu bar.

I guess our notions of what makes sense are very different, because
what doesn't make sense to you does for me, and vice versa.  I'm not
sure how to reconcile such opposite opinions.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.