emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-info.js: new navigation history
Date: Thu, 18 Jun 2009 09:21:35 +0200	[thread overview]
Message-ID: <68684FB9-A099-40F3-990A-7E7E0DE6EBA0@gmail.com> (raw)
In-Reply-To: <87skhyv84v.fsf@kassiopeya.MSHEIMNETZ>

Hi Sebastian,

On Jun 17, 2009, at 11:52 PM, Sebastian Rose wrote:

> Hi,
>
>
> just cannot resist posting this here:

Why would you even consider to resist? :-)

this is really great, I missed the possibility to go back to the most  
recent position.

- Carsten


>
> The navigation of org-info.js has been improved quite a bit.
>
>  1.) Navigating a file through org-info.js, either using the mouse or
>      using the keyboard, modifies the location. Thus, once you left
>      the file by following a link somewhere else, your browser's  
> `back'
>      button will bring you back to the point you left the file.
>
>  2.) org-info.js now navigates accross files. If those files both use
>      org-info.js, you can navigate back and forth. Because of the new
>      technique in 1.), both files nearly feel like beeing one and the
>      same file. Thus following links in published files feels like
>      following footnotes and returning to the context.
>
>      Example:
>
>      Once you reach the end of the internal history, repeatedly
>      pressing `B' or `b' takes you forward and back in the browsers
>      history.
>
>      - open one of your published org files.
>      - press `n' until a you reach a section, that has a link to  
> another
>        file in your published tree.
>      - follow the link by clicking on it.
>      - in the other file, navigate using `n' and `p'...
>      - go back in the navigation history using `b'
>      - repeat this, until org-info.js brings you back to the file you
>        opened in step 1. Note, that you see the same section you saw
>        just before leaving the file by following the link.
>      - Now press `B' until org-info.js brings you to the other file
>        again.
>
> One flaw though: the internal history is lost when returning to a
> file.
>
>
>
> Regards
>
>
>   Sebastian
>
>
>
> --
> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449  
> Hannover
> Tel.:  +49 (0)511 - 36 58 472
> Fax:   +49 (0)1805 - 233633 - 11044
> mobil: +49 (0)173 - 83 93 417
> Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
> Http:  www.emma-stil.de
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-06-18  8:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 21:52 org-info.js: new navigation history Sebastian Rose
2009-06-18  7:21 ` Carsten Dominik [this message]
2009-06-18  8:21 ` Carsten Dominik
2009-06-18 14:31 ` Xin Shi
2009-06-18 14:58   ` Sebastian Rose
2009-06-18 20:37     ` Xin Shi
2009-06-18 22:01       ` Sebastian Rose
2009-06-19 14:20         ` Xin Shi
2009-06-19 14:50           ` Sebastian Rose
2009-06-19 15:09           ` Sebastian Rose
2009-06-19 15:28             ` Xin Shi
2009-06-19 16:08               ` Sebastian Rose
2009-06-19 16:50                 ` Xin Shi
2009-06-22 11:46                   ` Sebastian Rose
2009-06-23  1:29                     ` Xin Shi
2009-06-23  2:15                       ` Sebastian Rose
2009-06-23 12:56                         ` Xin Shi

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=68684FB9-A099-40F3-990A-7E7E0DE6EBA0@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian_rose@gmx.de \
    /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).