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:44:22 +0000 [thread overview]
Message-ID: <87o7vyaqu1.fsf@posteo.net> (raw)
In-Reply-To: <878rn2uf97.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 02 Sep 2022 14:34:12 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>>> 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?
>
> Yes... and it pops up a menu to fix that, doesn't it?
Yes, but this is not the context menu that is active everywhere else. I
believe that what I am expecting is intuitive, as browsers behave the
same way. If you have a text field and right-click on any regular word,
you get the "undo", "cut", "paste", etc. options. But if you
right-click on a typo you get spell checking suggestion _in addition_ to
the previous options.
next prev parent reply other threads:[~2022-09-02 12:44 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
2022-09-02 12:34 ` Lars Ingebrigtsen
2022-09-02 12:44 ` Philip Kaludercic [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7vyaqu1.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 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.