emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.brand@alumni.ethz.ch>
To: emacs-orgmode@gnu.org
Subject: suggestion: simplify depth stepping of document structure (outline) visibility
Date: Wed, 16 Sep 2009 00:00:15 +0200	[thread overview]
Message-ID: <4AB00E6F.4090501@alumni.ethz.ch> (raw)
In-Reply-To: <4AB0000D.5000004@alumni.ethz.ch>

Hi all,

I would like much more to increase the heading visibility depth step by step like with the following if it would be much easier to type

step 1 to see level  1:    C-u 1 S-Tab
step 2 to see levels 1..2: C-u 2 S-Tab
step 3 to see levels 1..3: C-u 3 S-Tab
step 4 to see levels 1..4: C-u 4 S-Tab
and so on until not repeated any more (no cycling, only as a sequence)

Did I miss some simpler work flow to do something similar (not cycling with Tab or S-Tab)?

Are there others who would like this sequence to be easily stepped through?

Which constantly repeatable key command as convenient as possible like cycling with Tab or S-Tab would be suitable?

I would suggest that any key command different to this new key command would stop stepping the sequence and that the first invoke of this new key command again would reset the visibility to overview again like `C-u 1 S-Tab' does (similar to the nice cycle reset behavior of a first `S-Tab').

The point on e. g. a level 3 heading would be nice to be there again after going through steps 1 to 3 (similar to the nice behavior of e. g. `S-Tab S-Tab S-Tab' when the point was in a body before).

- Michael

       reply	other threads:[~2009-09-15 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AB0000D.5000004@alumni.ethz.ch>
2009-09-15 22:00 ` Michael Brand [this message]
2009-09-16  0:26   ` suggestion: simplify depth stepping of document structure (outline) visibility Bernt Hansen
2009-10-14 12:24     ` Michael Brand
2010-09-01 17:10       ` Michael Brand
2010-09-03  1:26         ` Bastien
2010-09-03  5:01           ` Herbert Sitz
2010-09-03  7:59             ` Michael Brand
2010-09-03  9:05           ` Michael Brand

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=4AB00E6F.4090501@alumni.ethz.ch \
    --to=michael.brand@alumni.ethz.ch \
    --cc=emacs-orgmode@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/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).