From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Teemu Likonen <tlikonen@iki.fi>, 1598@debbugs.gnu.org
Subject: bug#1598: Please add easy key bindings for outline-(minor-)mode
Date: Mon, 19 Jul 2021 17:55:27 +0200 [thread overview]
Message-ID: <87im165mds.fsf@gmail.com> (raw)
In-Reply-To: <87sg0amjkm.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 19 Jul 2021 17:04:09 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Teemu Likonen <tlikonen@iki.fi> writes:
>
>> The default key bindings for outline-mode and outline-minor-mode are
>> difficult to remember and slow to use. I think the main reason is that
>> there are way too many different key-bindings to operate with outlining.
>>
>> I suggest that you make keys like M-<left> and M-<right> to act modally
>> so that they open and close one outline level at the time depending on
>> which levels and bodies are currently visible. In addition to that, and
>> to make outline navigating easy, M-<up> and M-<down> could move the
>> cursor to previous and next visible outline header.
>
> (I'm going through old bug reports that unfortunately wasn't resolved at
> the time.)
>
> I agree that the outline commands are pretty awkward... but outline
> minor mode is used in a large number of major modes, and has to be
> consistent throughout all those modes. So M-<arrows> can't really be
> used for this, I think.
Also, FWIW, Emacs 28 now makes it possible to use TAB and S-TAB in
outline-minor-mode by setting outline-minor-mode-cycle. That doesn't
address navigation, but at least it brings outline-minor-mode on par
with Org in terms of ergonomy for cycling levels.
prev parent reply other threads:[~2021-07-19 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 9:57 bug#1598: Please add easy key bindings for outline-(minor-)mode Teemu Likonen
2008-12-17 16:20 ` Stefan Monnier
2008-12-17 16:30 ` Processed: " Emacs bug Tracking System
2008-12-17 16:49 ` Teemu Likonen
2021-07-19 15:04 ` Lars Ingebrigtsen
2021-07-19 15:33 ` Christopher Dimech
2021-07-19 15:34 ` Juri Linkov
2021-07-19 15:55 ` Kévin Le Gouguec [this message]
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=87im165mds.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=1598@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=tlikonen@iki.fi \
/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).