From: Dan Nicolaescu <dann@ics.uci.edu>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: Mode line changes
Date: Wed, 05 Mar 2008 16:27:30 -0800 [thread overview]
Message-ID: <200803060027.m260RUuM022608@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <18383.13776.783993.199319@kahikatea.snap.net.nz> (Nick Roberts's message of "Thu, 6 Mar 2008 13:07:44 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> > > That's why I said "where possible". Mouse-3 is tied up with other menus
> > > on the major and minor modes. Whereas mouse-3 currently on the line
> > > number mode does nothing so I don't see the point in breaking the
> > > convention when there is no need.
> >
> > So you are arguing that for popping a menu one would have to use mouse-1
> > for the major-mode, vc-mode, and minor-modes and then when moving one
> > entry to the left use mouse-3 for the line-number/column-number menu ?
> > That's completely inconsistent. Adding a binding to mouse-3 would make
> > more sense if that's considered necessary.
>
> I'm saying that the major and minor modes already use mouse-3 for pull down
> menus and that mouse-3 is generally used elsewhere for pull down menus, but you
> can twist it if you want.
No twisting involved, I was talking about the major-mode and minor-mode
menus, not some other menus. mouse-3 does not pop any menu for vc-mode.
> Incidentally vc-mode doesn't say what mouse-2 and mouse-3 do in the tooltip.
Just an oversight.
next prev parent reply other threads:[~2008-03-06 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 20:46 Mode line changes Nick Roberts
2008-03-05 21:40 ` Dan Nicolaescu
2008-03-05 23:20 ` Nick Roberts
2008-03-05 23:44 ` Dan Nicolaescu
2008-03-06 0:07 ` Nick Roberts
2008-03-06 0:27 ` Dan Nicolaescu [this message]
2008-03-06 0:20 ` Miles Bader
2008-03-07 3:39 ` Richard Stallman
2008-03-05 22:04 ` Stefan Monnier
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=200803060027.m260RUuM022608@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).