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

Previous Next

Package: emacs;

Reported by: Philip Kaludercic <philipk <at> posteo.net>

Date: Mon, 3 Jan 2022 08:38:02 UTC

Severity: normal

Tags: patch

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Philip Kaludercic <philipk <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: larsi <at> gnus.org, 52973 <at> debbugs.gnu.org, Juri Linkov <juri <at> linkov.net>
Subject: bug#52973: Adding a few context-menu-mode commands
Date: Sat, 08 Jan 2022 19:01:46 +0000
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Juri Linkov <juri <at> linkov.net>
>> Cc: Philip Kaludercic <philipk <at> posteo.net>,  larsi <at> gnus.org,
>>   52973 <at> debbugs.gnu.org
>> Date: Sat, 08 Jan 2022 20:30:06 +0200
>> 
>> None of the proposed functions is specific to a mode.
>
> The way I see it, the functions in man.el are for Man-mode, and those
> in hi-lock.el are for hi-lock-mode.

No, the Man functions can be used anywhere you want to read a man page.
It checks if the user clicked on something like "emacs(1)", then inserts
a entry into the context menu to open the man page at point.

The hi-lock functions can be used to highlight a symbol, just like with
`M-s h .'.  Requiring hi-lock-mode to be enabled beforehand would be
counterproductive.

>> When the global value of context-menu-functions
>> contains one of the proposed functions, right-clicking anywhere
>> will autoload every package where such context functions are defined.
>
> This is over-engineered, IMO.  There should be no need for such
> complexity.

What would you suggest to simplify this?

-- 
	Philip Kaludercic




This bug report was last modified 3 years and 115 days ago.

Previous Next


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