emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: emacs-orgmode@gnu.org
Subject: Re: PROPOSAL: Bind `org-fold-hide-subtree' by default in Org Mode.
Date: Fri, 24 Feb 2023 18:13:14 -0600	[thread overview]
Message-ID: <87cz5y7gbp.fsf@red-bean.com> (raw)
In-Reply-To: <tt6je4$1nt$2@ciao.gmane.io> (Max Nikulin's message of "Thu, 23 Feb 2023 09:35:46 +0700")
In-Reply-To: <87mt54tdc8.fsf@red-bean.com>

Okay, today I did some research and found that every "C-c 
C-<letter>" binding is used in Org Mode except for "C-c C-g". 
While that one is technically reserved for the mode's use, I 
suspect the reason it's unbound is that people are accustomed to 
using C-g as a quit command (and they get that effect if they 
accidentally type C-c, because then they type C-g and it's just an 
undefined key -- i.e., it quits, which is what the user wanted).

Note that while "C-c C-h" does not appear to be bound, it actually 
is: it gets you a help buffer about the Org Mode keybindings 
(which then, ironically, does not list "C-c C-h" as one of the 

(It's not clear to me whether Emacs's conventions consider "C-c 
C-i" to be a letter or whether they treat "C-i" as "TAB" and 
consider it special; based on the previous evidence in this 
thread, maybe the latter, so we shouldn't consider "C-c C-i" to be 

I think what this is telling me is that Org Mode keybinding real 
estate is quite valuable :-), and that unless there are other 
people who feel as strongly as I do that `org-fold-hide-subtree' 
is amazingly useful, we probably won't decide to bind it by 
default in Org Mode.  So I should just continue to bind it to a 
custom key myself and continue to live a glorious life all alone 
in my private keymap splendour.

Best regards,

I wrote:
>On 23 Feb 2023, Max Nikulin wrote:
>>On 23/02/2023 00:01, Karl Fogel wrote:
>>>  =C2=A0(when (not (keymap-lookup nil "C-<tab>"))
>>>  =C2=A0=C2=A0 (keymap-local-set "C-<tab>" 
>>>  'org-fold-hide-subtree))
>>> So FWIW C-<tab> is not bound in Org Mode buffers for me, in=20
>>> Emacs
>>> 30.x (i.e., recent development builds).
>>lisp/tab-bar.el:130:  (unless (global-key-binding [(control=20
>>lisp/tab-bar.el:131:    (global-set-key [(control tab)]=20
>>Minibuffer file cache completion should not be relevant to 
>Ah, I don't use tab-bar at all (at least not as far as I know), 
>I'm not 100% sure what the above is saying.
>Are you saying that the only current default binding for 
>in Emacs is that one in tab-bar.el, and therefore we should 
>free to rebind it in Org Mode?  If so, we should still be=20
>cautious, since Emacs has policies for maintaining the 
>space.  Generally, the space "C-c C-<LETTER>" is reserved for=20
>major modes, so ideally we should find something in there if 
>can -- although Org Mode has used up a lot of that space 
>:-), so I'm not sure what's left, unless we decide to swap out=20
>some existing binding in favor of this one.
>(I realize this contradicts what I said in my inital post.  I 
>forgotten that C-<tab> was not part of the mode-reserved space.)

  reply	other threads:[~2023-02-25  0:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  7:29 PROPOSAL: Bind `org-fold-hide-subtree' by default in Org Mode Karl Fogel
2023-02-22 15:57 ` Max Nikulin
2023-02-22 17:01   ` Karl Fogel
2023-02-23  2:35     ` Max Nikulin
2023-02-23  4:48       ` Samuel Wales
2023-02-25  8:01         ` Key binding in help (was: Re: PROPOSAL: Bind `org-fold-hide-subtree' by default in Org Mode.) Max Nikulin
2023-02-25 23:32           ` Samuel Wales
2023-03-08 15:27             ` Max Nikulin
2023-02-23 19:02       ` PROPOSAL: Bind `org-fold-hide-subtree' by default in Org Mode Karl Fogel
2023-02-25  0:13         ` Karl Fogel [this message]
2023-02-25 11:26           ` Max Nikulin
2023-02-25 17:33             ` Karl Fogel

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=87cz5y7gbp.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --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).