From: Xin Shi <shixin111@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Problem with org-info.js?
Date: Thu, 25 Jun 2009 14:56:31 -0400 [thread overview]
Message-ID: <5236d6f90906251156o2942bb33ta6372482b9326b2c@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 932 bytes --]
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.
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.
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.
Thanks!
Xin
[-- Attachment #1.2: Type: text/html, Size: 1105 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
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
next reply other threads:[~2009-06-25 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 18:56 Xin Shi [this message]
2009-06-25 21:26 ` Problem with org-info.js? Sebastian Rose
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=5236d6f90906251156o2942bb33ta6372482b9326b2c@mail.gmail.com \
--to=shixin111@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).