From: Van Ly <van.ly@sdf.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53158@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#53158: 28.0.90; TAB, RET key behave differently for Git-Log-View, Outline View mode
Date: Thu, 13 Jan 2022 09:32:45 +0000 (UTC) [thread overview]
Message-ID: <8730137e-471-daa1-d4a6-db668ee46f0@SDF.ORG> (raw)
In-Reply-To: <87bl0g6m54.fsf@gnus.org>
On Thu, 13 Jan 2022, Lars Ingebrigtsen wrote:
> Juri Linkov <juri@linkov.net> writes:
>
>> We were hit by this unpleasant problem in diff-mode with outline-minor-mode.
>> In diff-mode TAB moves point to the next hunk, because in browsers TAB moves
>> to the next link. But in outline-minor-mode TAB should expand and collapse
>> on the heading because TAB does this in Org mode.
>
> I think it's unfortunate that outline minor mode uses TAB, because it
> crashes with so much else we're using that key for. But I guess
> there's not much we can do about it at this point.
>
I think outline minor mode and org mode should coordinate to work
well with diff-mode TAB moves. Use TAB and S-TAB for moving forward
and backward to points of interest. Use ` immediately above the TAB
for operating on that context. What you can do is have a file for
design language roadmap guidance forward to overtime have
contributors align how the TAB is to be used and phase in new
behavior. Give it 18-months to align and grandfather in old behavior
people have grown callous for and are insensitive to pain point.
--
vl
next prev parent reply other threads:[~2022-01-13 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 14:20 bug#53158: 28.0.90; TAB, RET key behave differently for Git-Log-View, Outline View mode Van Ly
2022-01-10 17:54 ` Eli Zaretskii
2022-01-10 19:36 ` Van Ly
2022-01-10 19:52 ` Juri Linkov
2022-01-10 20:06 ` Eli Zaretskii
2022-01-10 20:18 ` Juri Linkov
2022-01-10 20:22 ` Eli Zaretskii
2022-01-13 9:05 ` Lars Ingebrigtsen
2022-01-13 9:32 ` Van Ly [this message]
2022-01-14 15:36 ` Howard Melman
2022-01-10 19:59 ` Eli Zaretskii
2022-01-10 20:59 ` Van Ly
2022-01-11 3:25 ` Eli Zaretskii
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=8730137e-471-daa1-d4a6-db668ee46f0@SDF.ORG \
--to=van.ly@sdf.org \
--cc=53158@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 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).