From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: van.ly@sdf.org, 53158@debbugs.gnu.org
Subject: bug#53158: 28.0.90; TAB, RET key behave differently for Git-Log-View, Outline View mode
Date: Mon, 10 Jan 2022 22:18:40 +0200 [thread overview]
Message-ID: <86k0f7wdi7.fsf@mail.linkov.net> (raw)
In-Reply-To: <83fspv8if0.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Jan 2022 22:06:27 +0200")
>> Then you can choose: when point is at the beginning of the outline heading,
>> TAB can expand and collapse outlines, when point is not at the line beginning,
>> TAB moves to the next hunk.
>
> FWIW, I consider this not a good UI. Having point one column to the
> left or to the right of where you want to be is quite frequent, so
> making a key sequence produce a very different effect depending on
> that is far from being the best idea, IMO.
Of course, it's not a good UI - it's a trade-off.
> To me, this tells that these two modes, and the user expectations and
> habits to go with them, are simply incompatible, and we shouldn't try
> mixing them. If someone wants a diff-mode-like outline mode, let's
> make such a mode, and leave the original diff-mode alone.
This problem is not specific to diff-mode.
next prev parent reply other threads:[~2022-01-10 20:18 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 [this message]
2022-01-10 20:22 ` Eli Zaretskii
2022-01-13 9:05 ` Lars Ingebrigtsen
2022-01-13 9:32 ` Van Ly
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=86k0f7wdi7.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=53158@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=van.ly@sdf.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).