From: Ihor Radchenko <yantar92@posteo.net>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: heading structure ramblie
Date: Wed, 20 Mar 2024 13:04:51 +0000 [thread overview]
Message-ID: <87v85hrr4c.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8v9rXTDY1KDJTjdi1ktA62HUp96oinkSHN8EdX3GYOW0g@mail.gmail.com>
Samuel Wales <samologist@gmail.com> writes:
> i sometimes need to know when a folded heading has children,
> and also possibly go to them. maybe it swallowed a heading
> without my intention. creating new headings with c-c *
> seems to create children, when i want a sibling. (so maybe i need a
> command like c-c * that creates a sibling. but i also want to show and
> navigate heading structure.)
Children are created when you use C-c * on a list.
When used on non-list, with C-u C-u prefix argument, siblings will be
created.
> i'd also like to know without linting the whole file if
> anything is awry locally, such as twice or more indented
> (*******) or half-indented (****), when org-odd-levels-only
> t.
>
> ...
> this could be solved by showing a view similar to canonical
> visibility, but only headings perhaps as an org-cycle state.
>
> i THINK this is supposed to be possible with c-u:
What about `org-shifttab'?
> or perhaps simpler, is there a command that will go to the
> next heading even if it is invisible, and unfold? there
> seems to be no org-next-heading, but there is one for
> visible headings.
Try C-c C-r (org-reveal). With one or two prefix arguments depending on
your needs.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-03-20 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 7:02 heading structure ramblie Samuel Wales
2024-03-20 13:04 ` Ihor Radchenko [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=87v85hrr4c.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).