emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: emacs-orgmode@gnu.org
Subject: Re: Replace Org's C-TAB with C-M-TAB - objection?
Date: Sun, 24 May 2020 14:31:47 +0200	[thread overview]
Message-ID: <87ftbpo6oc.fsf@fastmail.fm> (raw)
In-Reply-To: <87y2ph4mq0.fsf@gmail.com>

On Sun, May 24 2020, stardiviner wrote:
> Bastien <bzg@gnu.org> writes:
>> C-TAB in Org is bound to `org-force-cycle-archived' to allow to 
>> cycle
>> through archived subtrees.
>> In the Emacs tab-bar mode, it is now bound to `tab-next', which 
>> needs
>> to work globally.
>> So Org's binding and tab-bar's one are in conflict, as reported 
>> here:
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41325
>> I suggest binding `org-force-cycle-archived' to C-M-TAB: any 
>> objection?
>> Thanks,
> I object this change. Emacs tab-bar is not enabled by default. 
> When conflict,
> user can customize keybinding. I don't think it's very necessary 
> to change.

I would support the change, since both Org mode and tab-bar-mode 
are part of core Emacs and I doubt it'll be clear to new users 
coming to Emacs why these conflicting key bindings exist. Instead, 
they'll be annoyed that they cannot C-TAB out of the Org buffer 
and their impression of Emacs (not just Org mode or tab-bar-mode) 
will suffer. Ever more so because it's probably not immediately 
obvious to new users how C-TAB is different from just TAB: they 
both open the subtree at point.

I've been using C-TAB for a long time to switch buffers (albeit 
not with tab-bar-mode), and it's always annoying when some mode 
usurps (from my perspective) this keybinding. Now, I'm familiar 
with Emacs and the relative independence and freedom that 
individual packages have, plus C-TAB is a personal keybinding, so 
I know this sort of thing may happen and I know how to resolve it. 
For a new user, that won't be so obvious. For them, this will 
simply look like a badly designed UI.

So I think the general argument for habit-breaking UI changes 
applies: it creates a more consistent UI, which means it's easier 
on new users and more in line with what they expect. For existing 
users that want the old behaviour back, it's a simple 
configuration in their init.el.

Joost Kremers
Life has its moments

  reply	other threads:[~2020-05-24 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24  8:55 Replace Org's C-TAB with C-M-TAB - objection? Bastien
2020-05-24 11:05 ` stardiviner
2020-05-24 12:31   ` Joost Kremers [this message]
2020-06-01 12:44 ` Bind `org-force-cycle-archived' to C-c C-TAB instead of C-TAB Bastien
2020-06-01 13:03 ` Replace Org's C-TAB with C-M-TAB - objection? Bastien
  -- strict thread matches above, loose matches on Subject: below --
2020-05-27  4:36 Vladimir Nikishkin

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftbpo6oc.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=emacs-orgmode@gnu.org \


* 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


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).