emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Xin Shi <shixin111@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Problem with org-info.js?
Date: Thu, 25 Jun 2009 23:26:29 +0200	[thread overview]
Message-ID: <87zlbwhunu.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <5236d6f90906251156o2942bb33ta6372482b9326b2c@mail.gmail.com> (Xin Shi's message of "Thu, 25 Jun 2009 14:56:31 -0400")

Xin Shi <shixin111@gmail.com> writes:
> Hello Experts,
>
> I'm using org-6.28b and the fresh org-info.js (a few minutes ago). I publish
> org file into HTML with #+INFOJS_OPT: view:info. Just like this page:
> http://orgmode.org/Changes.html
>
> However, the internal links (such as [[#tag-name]]) still does not
> work.

Here it does. I wonder if we could finally help you, if you submitted a
simple test file that reproduces the problem.


As I wrote before, I can use custom IDs in the several documented ways
and they all work for me. Please send a test file so we have a chance to
find out where the problem is. I fear without a chance to reproduce the error,
we can not be of great help.


> When I hover the courser on the link, I can see it is correct. Somehow, the
> javascript just does not follow the link. Put it another way, once get into
> that page, all of the movement for the internal links are governed by
> javascript only, only links like javascript:org_html_manager.go(12) works. I
> don't know if it's possible to fix it.


No. Not in info view. The info-view mode (and folding in plain view) is
done by hiding the other sections. To show a section, the script has to
show it again.


> For example, in the same page:
> http://orgmode.org/Changes.html
>
> although it already have "customed_id"s, such as #v6.27, when you click on
> the Version 6.27, the real link get you to there is
> javascript:org_html_manager.go(29). If one put a link on that page:
> [[#v6.27][Go to Version 6.27]], it might not work.

There is a script like that on the page, but the script changes all
those links to ensure that the script gets noticed if the link is
used. How else should the script show and hide sections as needed??

To see that, just click on the [[#v6.27][Go to Version 6.27]] and then
press `U'. Do you see the URL in the link the script shows on top of the
screen? 

It looks like this:

   http://orgmode.org/Changes.html#v6.27

If you now click this link, you will come to that exact section.



   Sebastian

  reply	other threads:[~2009-06-25 21:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 18:56 Problem with org-info.js? Xin Shi
2009-06-25 21:26 ` Sebastian Rose [this message]
2009-06-26 21:14   ` Xin Shi
2009-06-26 23:07     ` Sebastian Rose
2009-06-26 23:21     ` Sebastian Rose
2009-06-27 19:45       ` Xin Shi
2009-06-27 21:49         ` Sebastian Rose
2009-06-28  1:03           ` Xin Shi
2009-06-28  3:37             ` Sebastian Rose
2009-06-28 15:08               ` 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=87zlbwhunu.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=shixin111@gmail.com \
    /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).