From: Philip Kaludercic <philipk@posteo.net>
To: Juri Linkov <juri@linkov.net>
Cc: 50851@debbugs.gnu.org
Subject: bug#50851: 28.0.50; flyspell-mode overrides context-menu-mode
Date: Tue, 28 Sep 2021 19:57:15 +0000 [thread overview]
Message-ID: <87bl4cv5gk.fsf@posteo.net> (raw)
In-Reply-To: <877df0le34.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 28 Sep 2021 22:01:03 +0300")
Juri Linkov <juri@linkov.net> writes:
>> When clicking on a misspelled word while context-menu-mode is active,
>> I'd expect the context menu to appear, but it seems like flyspell
>> prevents this.
>
> It was a bug caused by recent changes that is fixed now.
What should have fixed this? I just rebuilt the master branch and it
still seems to open the wrong menu.
>> Asides from preventing this inconsistency, it seems like it would be
>> better to integrate flyspell into context-menu, to suggest corrections.
>
> Adapting flyspell.el to context-menu is a welcome change that requires
> refactoring `flyspell-correct-word' and related functions to return
> a keymap menu where every menu item is bound to a lambda that calls
> `flyspell-do-correct' with an argument that is a correct word.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-09-28 19:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 15:45 bug#50851: 28.0.50; flyspell-mode overrides context-menu-mode Philip Kaludercic
2021-09-28 19:01 ` Juri Linkov
2021-09-28 19:57 ` Philip Kaludercic [this message]
2021-12-02 17:49 ` Juri Linkov
2022-09-02 11:15 ` Lars Ingebrigtsen
2022-09-02 11:23 ` Philip Kaludercic
2022-09-02 11:26 ` Lars Ingebrigtsen
2022-09-02 12:32 ` Philip Kaludercic
2022-09-02 12:34 ` Lars Ingebrigtsen
2022-09-02 12:44 ` Philip Kaludercic
2022-09-02 13:03 ` Lars Ingebrigtsen
2022-09-03 2:34 ` Jim Porter
2022-09-03 19:44 ` Juri Linkov
2021-12-03 13:56 ` Tor Kringeland
2021-12-04 19:54 ` Juri Linkov
2022-09-02 11:17 ` Lars Ingebrigtsen
2022-09-03 19:40 ` Juri Linkov
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=87bl4cv5gk.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=50851@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).