bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#9054: [External] : bug#9054: 24.0.50; show source in other window


From: Drew Adams
Subject: bug#9054: [External] : bug#9054: 24.0.50; show source in other window
Date: Mon, 20 Sep 2021 14:11:38 +0000

>  > How about
>  >    Describe symbol at mouse click
>  > etc.?
> 
> I would try to avoid the term "symbol" in context menus.  Beginners
> might not associate "symbol" with some sort of plain code they see.
> Juri meanwhile uses "function" and "variable" instead but I'm still
> convinced that explicitly writing out the symbol in the menu entry is
> the best choice here.

Your point is reasonable.  On the other hand,
it's not difficult to find out what's meant, I
think.  The first attempt to use such a menu
choice shows users what's meant, by concrete
example.  And that teaches users about the
Emacs notion of "symbol", which is not a bad
thing.
___

I already showed the Thing At Pointer submenu
used in my mouse-3 context menu when there's
no nonempty active region.

My code for menu-bar Help menu similarly has
these items in its Describe submenu.  (It has
others too, but these are things that can be
picked up as a thing-at-point.)

 Command
 Function
 Option
 Variable
 Face
 Key
 File

And even the vanilla Help > Describe has key,
function, variable, and face.
___

FWIW, I don't think writing out the name of
the symbol (or face or whatever) is needed.

In the case of symbols, the symbol name is
being pointed at.  Yes, in the case of a
face or some other thing that's not showing
its name, the name might help, but just
trying the menu item shows a user what's
involved right away.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]