From: Ihor Radchenko <yantar92@gmail.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: emacs-devel@gnu.org
Subject: Re: Cycling first N heading levels in outline
Date: Sun, 23 May 2021 18:21:35 +0800 [thread overview]
Message-ID: <87r1hxu4wg.fsf@localhost> (raw)
In-Reply-To: <trinity-82fb005c-1ca3-4262-8e43-f5f4d391a366-1621763631518@3c-app-mailcom-bs09>
Christopher Dimech <dimech@gmx.com> writes:
>> Hmm. Have you tried org-shifttab (bound to S-<TAB>)? It operates
>> globally across the buffer.
>
> I rather keep things to outline-minor-mode than apply org functionality. Originally,
> Was using org-mode as the major buffer but that removed programming highlighting.
> Outline should take care of such things itself rather than workarounds with org
> functionality.
Sorry, I actually mixed this message with org mailing list because of
the contents. I initially though that you referred to org.
As for highlighting issue, please report is as a bug if you think that
Org does something wrongly.
>> Also, there is outline-hide-sublevels. When called with prefix argument,
>> it will display sublevels from level 1 up until the level equal to the
>> prefix argument.
>
> But LEVELS defaults to the level of the *current heading* or to 1 if the
> *current line is not a heading*. This means I got to go to a heading.
>
> The problem occurs for long files, because I am forces to navigate the file.
> If the heading level is deep, it is difficult to search through.
Yet, with *numeric* prefix argument it will forcefully show all the
levels between 1 and number passed as prefix argument.
Best,
Ihor
next prev parent reply other threads:[~2021-05-23 10:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 16:16 Cycling first N heading levels in outline Christopher Dimech
2021-05-23 4:48 ` Ihor Radchenko
2021-05-23 8:58 ` Christopher Dimech
2021-05-23 9:46 ` Ihor Radchenko
2021-05-23 9:53 ` Christopher Dimech
2021-05-23 10:21 ` Ihor Radchenko [this message]
2021-05-23 10:23 ` Ihor Radchenko
2021-05-23 13:10 ` Christopher Dimech
2021-05-23 14:14 ` Ihor Radchenko
2021-05-23 14:14 ` Jean Louis
2021-05-23 14:34 ` Christopher Dimech
2021-05-23 14:37 ` Jean Louis
2021-05-23 14:12 ` Jean Louis
2021-05-23 14:35 ` Ihor Radchenko
2021-05-23 17:57 ` Jean Louis
2021-05-23 18:55 ` Christopher Dimech
2021-05-23 19:06 ` Tassilo Horn
2021-05-23 19:55 ` Stefan Monnier
2021-05-24 10:34 ` Christopher Dimech
2021-05-24 10:57 ` Kévin Le Gouguec
2021-05-24 11:23 ` Christopher Dimech
2021-05-25 17:41 ` Christopher Dimech
2021-05-24 10:39 ` Christopher Dimech
2021-05-24 16:27 ` Stefan Monnier
2021-05-24 17:43 ` Christopher Dimech
2021-05-26 13:57 ` Ihor Radchenko
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=87r1hxu4wg.fsf@localhost \
--to=yantar92@gmail.com \
--cc=dimech@gmx.com \
--cc=emacs-devel@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).