From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50851@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#50851: 28.0.50; flyspell-mode overrides context-menu-mode
Date: Fri, 02 Sep 2022 12:32:21 +0000 [thread overview]
Message-ID: <87v8q6are2.fsf@posteo.net> (raw)
In-Reply-To: <87edwuvwyh.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 02 Sep 2022 13:26:30 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Not necessarily, a word might appear to be a typo (but is actually just
>> not in the dictionary) but I would still like to search the buffer using
>> occur to see where else it appears. If context-menu-mode is enabled, I
>> think it would be right for the same context menu to appear consistently
>> (which is still not the case), and have spell-checking be a submenu
>> instead of taking over.
>
> So you'd prefer to have the flyspell menu appear as a sub-menu to the
> normal (mode-specific) context menu?
>
> I'm not sure whether that's how the context menu was envisioned -- I
> thought it was to be, well, context aware, so it'd change based on
> what's under point.
Isn't the context in this case a (possible) typo?
next prev parent reply other threads:[~2022-09-02 12:32 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
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 [this message]
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=87v8q6are2.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=50851@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
/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).