[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43322: Confusing menu entry for cua-mode
From: |
Stefan Kangas |
Subject: |
bug#43322: Confusing menu entry for cua-mode |
Date: |
Fri, 23 Oct 2020 21:17:42 +0000 |
Eli Zaretskii <eliz@gnu.org> writes:
>> AFAICT, cua-mode respects shift-select-mode, which makes the menu entry
>> incorrect.
>
> So what do you propose to do about this bug report?
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?
- bug#43322: Confusing menu entry for cua-mode, Stefan Kangas, 2020/10/22
- bug#43322: Confusing menu entry for cua-mode, Eli Zaretskii, 2020/10/23
- bug#43322: Confusing menu entry for cua-mode,
Stefan Kangas <=
- bug#43322: Confusing menu entry for cua-mode, Eli Zaretskii, 2020/10/24
- bug#43322: Confusing menu entry for cua-mode, Stefan Kangas, 2020/10/28
- bug#43322: Confusing menu entry for cua-mode, Eli Zaretskii, 2020/10/29
- bug#43322: Confusing menu entry for cua-mode, Stefan Kangas, 2020/10/29
- bug#43322: Confusing menu entry for cua-mode, Drew Adams, 2020/10/29
- bug#43322: Confusing menu entry for cua-mode, Eli Zaretskii, 2020/10/29
- bug#43322: Confusing menu entry for cua-mode, Drew Adams, 2020/10/29
- bug#43322: Confusing menu entry for cua-mode, Stefan Kangas, 2020/10/29