From: Howard Melman <hmelman@gmail.com>
To: 41129@debbugs.gnu.org
Subject: bug#41129: outline-mode: New keybindings for demote/promote/move-subtree
Date: Sat, 30 Jan 2021 13:48:38 -0500 [thread overview]
Message-ID: <lytuqyp8ft.fsf@Lumet2.home> (raw)
In-Reply-To: <CADwFkmmQAHgGJPdccKQLWzFwGXbFUEyoAw19tT1OL1pKUb5BAw@mail.gmail.com>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Howard Melman <hmelman@gmail.com>
>> Date: Sat, 30 Jan 2021 12:39:52 -0500
>>
>> the command right-word, which is only useful when editing
>> bidirectional
>
> This assertion is incorrect. The real goal of right-word is to
> provide a command that works as users expect in both left-to-right and
> right-to-left contexts. The alternative would be to request that the
> user should decide whether to use M-f or M-b to go in a particular
> direction, and that's a non-starter.
I stand corrected. I'm a left-to-right only user and I
won't make the case that that is more important, merely that
I'm unfamiliar with the specifics of other users.
>> is so important it needs TWO very similar default key bindings
>> (M-right and C-right)
>
> This command has two bindings not because of its importance, but
> because other programs out there use those bindings. Emacs is
> following the expectations of the users here.
Ok, but in emacs they expect and need both? How do they
adjust in org mode? Or is this a complaint that users of
right-word have in org-mode? Would users of
outline-minor-mode adjust similarly?
Does outline-mode support right-to-left oriented outlines?
Does org? I'm guessing not because then these arrow key
bindings would want to adjust demote/promote behavior
accordingly. Should they?
Maybe these bindings could be in another minor-mode that
could be enabled by those users that want them?
outline-use-org-bindings-minor-mode.
--
Howard
next prev parent reply other threads:[~2021-01-30 18:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 20:49 bug#41129: outline-mode: New keybindings for demote/promote/move-subtree Stefan Kangas
2020-05-08 17:56 ` Stefan Kangas
2021-01-28 6:28 ` Lars Ingebrigtsen
2021-01-28 9:39 ` Pankaj Jangid
2021-01-28 15:07 ` Stefan Kangas
2021-01-29 4:49 ` Lars Ingebrigtsen
2021-01-29 20:06 ` Howard Melman
2021-01-29 22:01 ` bug#41129: [External] : " Drew Adams
2021-01-30 6:23 ` Lars Ingebrigtsen
2021-01-30 17:39 ` Howard Melman
2021-01-30 18:00 ` Eli Zaretskii
2021-01-30 18:48 ` Howard Melman [this message]
2021-01-30 19:22 ` Eli Zaretskii
2021-01-30 19:40 ` Howard Melman
2021-01-30 19:55 ` Eli Zaretskii
2021-03-03 19:10 ` Juri Linkov
2022-05-09 10:38 ` Lars Ingebrigtsen
2022-05-09 14:31 ` Howard Melman
2022-05-10 2:03 ` Lars Ingebrigtsen
2022-05-11 7:10 ` Juri Linkov
2022-05-11 10:37 ` Visuwesh
2022-05-11 11:56 ` Lars Ingebrigtsen
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=lytuqyp8ft.fsf@Lumet2.home \
--to=hmelman@gmail.com \
--cc=41129@debbugs.gnu.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).