unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 43322@debbugs.gnu.org
Subject: bug#43322: Confusing menu entry for cua-mode
Date: Sat, 24 Oct 2020 11:05:33 +0300	[thread overview]
Message-ID: <83zh4cgib6.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkzYU9wyLHmG8m9uiWYH75z55HthHAcmJ3KXq7cpERHuw@mail.gmail.com> (message from Stefan Kangas on Fri, 23 Oct 2020 21:17:42 +0000)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 23 Oct 2020 21:17:42 +0000
> Cc: 43322@debbugs.gnu.org
> 
> We should probably replace "Shift movement mark region" with something
> else.  But it's not clear to me how to best describe it; its other
> features don't really lend themselves to a short one line description.
> 
> I see two options:
> 
> 1. Change "Shift movement mark region" to "CUA Mode (without
>    C-x/C-c/C-v)" with tooltip "Enable CUA Mode without setting
>    C-x/C-c/C-v keys".  Perhaps we could even add on to the tooltip the
>    explanatory text " (`cua-enable-cua-keys' is non-nil)".
> 
> 2. If we can make the assumption that a user who has set
>    `cua-enable-cua-keys' at least vaguely knows what they are doing,
>    perhaps we could get away with just not doing anything special in
>    that case.  In that case, we can get rid of the special handling and
>    just show the default menu entry under all circumstances.
> 
> WDYT?  Any other ideas?

I think we should do 1, but how do we name that item? what does CUA
mode do nowadays when CUA keys are disabled?





  reply	other threads:[~2020-10-24  8:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  0:41 bug#43322: Confusing menu entry for cua-mode Stefan Kangas
2020-09-11  6:54 ` Eli Zaretskii
2020-09-11 19:30   ` Stefan Kangas
2020-09-11 19:40     ` Eli Zaretskii
2020-10-23  0:37       ` Stefan Kangas
2020-10-23 19:57         ` Eli Zaretskii
2020-10-23 21:17           ` Stefan Kangas
2020-10-24  8:05             ` Eli Zaretskii [this message]
2020-10-29  1:05               ` Stefan Kangas
2020-10-29 14:21                 ` Eli Zaretskii
2020-10-29 15:01                   ` Stefan Kangas
     [not found] <<CADwFkm=PZtb-wu05YvxoSfop7N9d2fi2CUiWEr6YU4vCCq44Pg@mail.gmail.com>
     [not found] ` <<83wo10hkgg.fsf@gnu.org>
     [not found]   ` <<CADwFkm=_G=yb+u1E7qoA=S6kn1HAw=ZKaeFXn1yPXL6vNUjM1A@mail.gmail.com>
     [not found]     ` <<83363of6fs.fsf@gnu.org>
     [not found]       ` <<CADwFkmkqnSvJnf9qjMkNXYHiZ6bzh6v0XvmhHj5GR5LZ3CD3nA@mail.gmail.com>
     [not found]         ` <<83d018iul1.fsf@gnu.org>
     [not found]           ` <<CADwFkmkzYU9wyLHmG8m9uiWYH75z55HthHAcmJ3KXq7cpERHuw@mail.gmail.com>
     [not found]             ` <<83zh4cgib6.fsf@gnu.org>
     [not found]               ` <<CADwFkmkPnY5JrmCP9NpjhQ4j8=yaUaAf326XGcZeAmBbu93TgA@mail.gmail.com>
     [not found]                 ` <<83wnz9aza1.fsf@gnu.org>
2020-10-29 16:51                   ` Drew Adams
2020-10-29 17:09                     ` Eli Zaretskii
     [not found] <<<CADwFkm=PZtb-wu05YvxoSfop7N9d2fi2CUiWEr6YU4vCCq44Pg@mail.gmail.com>
     [not found] ` <<<83wo10hkgg.fsf@gnu.org>
     [not found]   ` <<<CADwFkm=_G=yb+u1E7qoA=S6kn1HAw=ZKaeFXn1yPXL6vNUjM1A@mail.gmail.com>
     [not found]     ` <<<83363of6fs.fsf@gnu.org>
     [not found]       ` <<<CADwFkmkqnSvJnf9qjMkNXYHiZ6bzh6v0XvmhHj5GR5LZ3CD3nA@mail.gmail.com>
     [not found]         ` <<<83d018iul1.fsf@gnu.org>
     [not found]           ` <<<CADwFkmkzYU9wyLHmG8m9uiWYH75z55HthHAcmJ3KXq7cpERHuw@mail.gmail.com>
     [not found]             ` <<<83zh4cgib6.fsf@gnu.org>
     [not found]               ` <<<CADwFkmkPnY5JrmCP9NpjhQ4j8=yaUaAf326XGcZeAmBbu93TgA@mail.gmail.com>
     [not found]                 ` <<<83wnz9aza1.fsf@gnu.org>
     [not found]                   ` <<0421a811-2ed3-4e1d-a2e0-bd12accf73ef@default>
     [not found]                     ` <<83pn51arih.fsf@gnu.org>
2020-10-29 17:54                       ` Drew Adams
2020-10-29 18:15                         ` 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=83zh4cgib6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=43322@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).