From: Leo <sdl.web@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: C-c C-j
Date: Thu, 05 Apr 2007 15:08:08 +0100 [thread overview]
Message-ID: <m2k5wqkj7b.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: m2slbekjhk.fsf_-_@sl392.st-edmunds.cam.ac.uk
On 2007-04-05, Leo said:
> I also found C-c C-j convenient. However, it is quite weak when
> navigating through a big file with various levels of subtrees. I
> wonder would it be useful to add the support of navigating subtrees on
> the same level?
I know C-c C-b and C-c C-f navigate on the same level. I was thinking
of making M-<up/down> navigate on the same level after hitting C-c
C-j.
--
Leo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)
next prev parent reply other threads:[~2007-04-05 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 19:09 (unknown) Jost Burkardt
2007-04-05 0:26 ` Jason F. McBrayer
2007-04-05 14:01 ` C-c C-j (was: ) Leo
2007-04-05 14:08 ` Leo [this message]
2007-04-05 16:46 ` Re: C-c C-j Carsten Dominik
2007-04-05 18:25 ` Leo
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=m2k5wqkj7b.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
--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).