From: Philipp Kiefer <phil.kiefer@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, emacs-orgmode@gnu.org
Subject: Re: Suggestion to increase usefulness of TAB key / 'org-cycle' function
Date: Mon, 1 May 2023 22:31:54 +0200 [thread overview]
Message-ID: <1fdb079f-be89-b3c0-3380-fd56ac274eca@gmail.com> (raw)
In-Reply-To: <87ildbhow0.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
I see. Thank you for your very helpful reply!
On 01.05.2023 20:45, Ihor Radchenko wrote:
> Philipp Kiefer<phil.kiefer@gmail.com> writes:
>
>>> Do I understand you correctly that you mean tab should cycle visibility
>>> in this case?
>>>
>>> * headline
>>> some text
>>> CURSOR IS HERE
>>> - a list
>> Yes, I suggested that in those cases, org-cycle should fold the subtree
>> point is in, i. e. fold up to the next parent heading above.
> To get this, just customize `org-cycle-emulate-tab' to nil.
>
>> Hm, for me, TAB does not currently seem to do any indenting anywhere in
>> an Org file.
> It just means that <TAB> is not configured to do anything in your Emacs.
> By default, the Org's fallback is `org-cycle-emulate-tab' or whatever
> global <TAB> is bound to.
>
>> If people use tab for indentation in Org out of the box when not on
>> headings (which it has never done for me, I think), my suggestion would
>> indeed be moot.
> <TAB> does a lot of staff. Just read through `org-cycle' docstring.
>
[-- Attachment #2: Type: text/html, Size: 2018 bytes --]
prev parent reply other threads:[~2023-05-01 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 8:49 Suggestion to increase usefulness of TAB key / 'org-cycle' function Philipp Kiefer
2023-04-28 9:45 ` Fraga, Eric
2023-04-28 15:17 ` Philipp Kiefer
2023-04-28 17:41 ` Dr. Arne Babenhauserheide
2023-04-28 22:28 ` Esteban Ordóñez
2023-04-28 23:19 ` Dr. Arne Babenhauserheide
2023-04-30 17:17 ` Philipp Kiefer
2023-05-01 18:45 ` Ihor Radchenko
2023-05-01 20:31 ` Philipp Kiefer [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1fdb079f-be89-b3c0-3380-fd56ac274eca@gmail.com \
--to=phil.kiefer@gmail.com \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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/org-mode.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).