From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Bindings on the mode-line
Date: Wed, 14 Sep 2005 09:34:44 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICCEIOCMAA.drew.adams@oracle.com> (raw)
In-Reply-To: <20050914.230534.42650714.jet@gyve.org>
I support this proposal. Emacs doesn't have convention for the usage of
mouse-[1-3]. It is good time to define a convention like C-x for global
binding prefix and C-c for major mode prefix.
I don't know if this is a good time for that - I doubt it. It will likely be
another wrestling match, with everyone having a different, strong opinion.
UI matters always seem to bring that out. After the release is a better
time.
I hope mouse-3 is reserved for context menus.
I generally agree, with the proviso that "reserved" here be interpreted
rather softly. Mouse-3 is already used for such things as extending the
region, so such a reservation could not anyway be strict. IOW, it is
generally a good convention to use mouse-3, or mouse-3 with some modifier,
for context menus, but we shouldn't change important existing functionality
just to respect such a convention (IMO).
Also, it is sometimes useful to have different context menus available at
the same time. We already have C-mouse-3 (mode) and C-mouse-2 (Text
Properties), for instance. An additional (soft) convention could hold that
in such cases, the mouse-3 menu would be more directly related to the mode
(as is the case with C-mouse-3).
In addition a key is needed for popping up a context menu under point.
Yes, that would be useful. When there is more than one such menu, the user
could choose (e.g. in the minibuffer).
next prev parent reply other threads:[~2005-09-14 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 9:57 Bindings on the mode-line Nick Roberts
2005-09-14 14:05 ` Masatake YAMATO
2005-09-14 16:34 ` Drew Adams [this message]
2005-09-15 2:41 ` Richard M. Stallman
2005-09-15 4:22 ` Nick Roberts
2005-09-16 1:01 ` Richard M. Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DNEMKBNJBGPAOPIJOOICCEIOCMAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.