unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 조성빈 <pcr910303@icloud.com>, "Van L" <van@scratch.space>
Cc: help-gnu-emacs@gnu.org
Subject: context-sensitive mouse-3 [was: Is Elisp really that slow?]
Date: Sun, 19 May 2019 14:44:35 +0000 (UTC)	[thread overview]
Message-ID: <d199254c-90ef-431d-96da-0b79fd94aa82@default> (raw)

> Saying about discoverability, I would like a context-sensitive right-click
> mouse menu, something like Microsoft Office. Most newcomers are familiar with
> finding functionality with the mouse;

Library `mouse3.el' gives you a context-sensitive menu
on `mouse-3'.  And yet it still also gives you the
normal Emacs `mouse-3' behavior.

You or your code can customize what the menu shows in
different contexts.

https://www.emacswiki.org/emacs/Mouse3


> how should I find new functions...?

I'm guessing you mean functions (in particular,
commands) that are new to you, and not necessarily
new to Emacs.

Icicles can help with discoverability in a few ways:

 * See what you can do at any moment:
   . See which possible inputs are expected by a
     command that reads input
   . See which key sequences are currently available,
     which of them are general vs which are local,
     and what each of them does
 * See individual descriptions of the possible inputs,
   that is, help on completion candidates
 * Find menu items more easily
 * Find commands more easily
 * Find help in the doc
 * Learn how to use regexps

https://www.emacswiki.org/emacs/EmacsNewbieWithIcicles

Menus in general, and La Carte in particular, can also
help with discoverability, and even more so when combined
with substring or regexp completion (e.g. Icicles).

https://www.emacswiki.org/emacs/LaCarte



             reply	other threads:[~2019-05-19 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-19 14:44 Drew Adams [this message]
2019-05-19 15:12 ` context-sensitive mouse-3 [was: Is Elisp really that slow?] 조성빈
2019-05-19 15:22   ` Drew Adams

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=d199254c-90ef-431d-96da-0b79fd94aa82@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=pcr910303@icloud.com \
    --cc=van@scratch.space \
    /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.
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).