unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>, Juri Linkov <juri@linkov.net>
Cc: l26wang@gmail.com, 11680@debbugs.gnu.org
Subject: bug#11680: flyspell should use mouse-3 instead of mouse-2
Date: Mon, 17 Aug 2020 14:01:37 +0000	[thread overview]
Message-ID: <CADwFkm=D7d2XuXh2EBke17TJ+Zu2HZhV5oF6qTJUkOETLa=cLg@mail.gmail.com> (raw)
In-Reply-To: <356faca3-1387-4477-8e81-27580b76374d@default>

Drew Adams <drew.adams@oracle.com> writes:

>> In the future, a more general option would be preferable
>> that would enable using the right mouse button to pop up
>> context menus in more places in Emacs like most other apps do
>> nowadays, i.e. something like cua-emulation mode but for mouse-3.

Agreed, that would be very useful.

> (Caveat: I haven't followed this thread, at all.)
>
> But if `mouse-3' behavior that allows for context-specific
> popup menus is what's sought, then `mouse3.el' fulfills
> that need, and with a great deal of flexibility.  This has
> been the case since 2010.
>
> Not only does it provide for context menus, but it does so
> without sacrificing the other useful vanilla `mouse-3'
> behaviors, which are also useful.  It adds to, instead of
> replaces, existing `mouse-3' behavior.  It's compatible
> with what Emacs users expect in general for `mouse-3'.
>
> https://www.emacswiki.org/emacs/Mouse3
>
> https://www.emacswiki.org/emacs/download/mouse3.el

Thanks, I didn't know about this library but will look into it in
detail.  Is there anything stopping us from incuding this library in
Emacs?  Would it be suitable for general use?

Best regards,
Stefan Kangas





  reply	other threads:[~2020-08-17 14:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 12:23 bug#11680: flyspell should use mouse-3 instead of mouse-2 Le Wang
2019-11-01 18:21 ` Stefan Kangas
2019-11-01 19:07   ` Eli Zaretskii
2019-11-02  0:25     ` Stefan Kangas
2019-11-02  7:51       ` Eli Zaretskii
2020-01-16  1:50         ` Stefan Kangas
2020-01-16 14:46           ` Eli Zaretskii
2020-08-13  6:10             ` Stefan Kangas
2020-08-13 13:07               ` Eli Zaretskii
2020-08-15  1:08                 ` Stefan Kangas
2020-08-15 17:53                   ` Eli Zaretskii
2020-08-16 17:53                     ` Stefan Kangas
2020-08-17  0:38                   ` Juri Linkov
2020-08-17  2:38                     ` Drew Adams
2020-08-17 14:01                       ` Stefan Kangas [this message]
2020-08-17 15:12                         ` Drew Adams
2020-08-19  1:07                   ` Juri Linkov
2020-08-19 10:00                     ` Stefan Kangas
2020-08-27  5:14                       ` Stefan Kangas

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='CADwFkm=D7d2XuXh2EBke17TJ+Zu2HZhV5oF6qTJUkOETLa=cLg@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=11680@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=juri@linkov.net \
    --cc=l26wang@gmail.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 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).