From: Van Ly <van.ly@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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 20:59:00 +0000 (UTC) [thread overview]
Message-ID: <24ff80-a2f2-955b-4ff3-6d5b20a4b5f@SDF.ORG> (raw)
In-Reply-To: <83h7ab8iql.fsf@gnu.org>
On Mon, 10 Jan 2022, Eli Zaretskii wrote:
>> Date: Mon, 10 Jan 2022 19:36:43 +0000 (UTC)
>> From: Van Ly <van.ly@sdf.org>
>> cc: 53158@debbugs.gnu.org
>>
>>> There's absolute no guarantee in Emacs that a key behaves the same in
>>> tow different modes. Even if those two modes can be argued to be
>>> similar in some sense.
>>>
>>
>> Yes, I know. Emacs unboxes with unpleasant defaults.
>
> Is that some new way of convincing the maintainers to be more amenable
> to your opinions and suggestions? If so, it isn't working.
>
A pearl comes from an irritant in the shell.
>
> A TAB as a means to cycle visibility could be a natural thing in
> outline modes, but log-view-mode is not an outline mode, it's derived
> from different parents.
>
Having the same keybinding function on the aster at position one on
the line to unroll/rollup the headline/detail is an opportunity
for improving the UI intuitivity across these two modes. From an
enduser perspective.
--
vl
next prev parent reply other threads:[~2022-01-10 20:59 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
2022-01-14 15:36 ` Howard Melman
2022-01-10 19:59 ` Eli Zaretskii
2022-01-10 20:59 ` Van Ly [this message]
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=24ff80-a2f2-955b-4ff3-6d5b20a4b5f@SDF.ORG \
--to=van.ly@sdf.org \
--cc=53158@debbugs.gnu.org \
--cc=eliz@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).