emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: nicholas.dokos@hp.com
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-info.js
Date: Wed, 19 May 2010 10:34:52 -0400	[thread overview]
Message-ID: <8739xoq7sj.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <9853.1274277495@gamaville.dokosmarshall.org> (Nick Dokos's message of "Wed, 19 May 2010 09:58:15 -0400")

Nick Dokos <nicholas.dokos@hp.com> writes:

> Dan Davison <davison@stats.ox.ac.uk> wrote:
>> If I'm viewing the manual with Sebastian's org-info javascript info
>> emulation, and I'm on node 13 of the manual, what key do I press to get
>> to 13.1?
>> I wish I were better with info. My understanding is that I would use
>> space or ] in emacs.
> In emacs info, <SPACE> advances down the imaginary scroll, so it may or
> may not get you to the next (sub)section, depending on the length of the
> current section and the size of your screen. ']' will go to the next
> node in a depth-first traversal, 'n' will get you to the next node in a
> level-traversal (always assuming that the relevant nodes exist).
> Numeric arguments will get you to the relevant subsection (i.e. if you
> are in sec. 13 and press 6, you'll end up in subsection 13.6 - assuming
> that it exists), whereas 'n' and 'p' will get you to the next/previous
> heading at the same level and 'u' will go up a level.
> Now I'm on much shakier ground (iow, I don't necessarily know what I'm
> talking about), but I think `n' does a depth-first traversal, so it will
> go from 13 to 13.1 - the question is how to go from 13 to 14 without
> visiting all the 13.x... in-between:

Actually, no, n goes from 13 to 14 (at least in google-chrome). But I'm
with you -- it seems to behave differently in


There n does the depth-first traversal you describe (and that is the
behaviour I'm looking for).

- how to get the full traversal in the org manual?
- why is there different behaviour between the manual and the worg page?


> I thought I would go UP to the TOC
> and then TAB to or click on the next section, but the UP link does not
> seem to do what I think it should do (go up one level in the hierarchy -
> at least that seems to be the case in the org-info pages:
> http://orgmode.org/worg/code/org-info-js). I'm not saying there is no
> way: I just didn't find one after a few minutes of fooling around.
> HTH,
> Nick
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-05-19 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 13:23 org-info.js Dan Davison
2010-05-19 13:58 ` org-info.js Nick Dokos
2010-05-19 14:34   ` Dan Davison [this message]
2010-05-19 15:37     ` org-info.js Carsten Dominik
  -- strict thread matches above, loose matches on Subject: below --
2015-01-26 19:11 org-info.js Phillip Lord
2015-01-26 19:51 ` org-info.js Achim Gratz
2015-01-27 17:09   ` org-info.js Phillip Lord
2008-03-25 10:17 org-info.js Pete Phillips
2008-03-26 11:42 ` org-info.js Sebastian Rose

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:

  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=8739xoq7sj.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \


* 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


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).