From: Sebastian Rose <sebastian_rose@gmx.de>
To: Kyle Sexton <ks@mocker.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: :link-up, :link-home
Date: Mon, 06 Jul 2009 18:03:28 +0200 [thread overview]
Message-ID: <87hbxpaje7.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <a6b4a2050907060741y94c7e37peb90c9e36f356e3b@mail.gmail.com> (Kyle Sexton's message of "Mon, 6 Jul 2009 09:41:12 -0500")
Kyle Sexton <ks@mocker.org> writes:
> The way I would like to use the link-up and link-home feature is to have
> those links point back to my main org index.html that is automatically
> generated. I can then have a list of all my notes and when someone clicks
> in the note they aren't "trapped" in that note. Very similar to how it's
> accomplished in infojs with the 'showall' option.
>
> I'm doing all this with a pre and post amble that load a long header and
> footer, so I don't think infojs will work. In fact, when trying to include
> infojs with the heater and footer it looked like it was disabled.
Yes, org-info.js depends on a certain structure and on the table of
contents.
Currently, the search for org-export contents is started, is
<div id="content">
... All exported standard stuff here ...
</div>
But we could use something like
org_html_manager.set("B", "#idOfTheElement");
to change it (`B' is the internal name of that container after the
call to `make').
I think it will work with some additional changes.
Sebastian
next prev parent reply other threads:[~2009-07-06 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 19:52 :link-up, :link-home Kyle Sexton
2009-07-06 10:08 ` Carsten Dominik
2009-07-06 11:58 ` Sebastian Rose
2009-07-06 11:56 ` Carsten Dominik
2009-07-06 14:41 ` Kyle Sexton
2009-07-06 16:03 ` Sebastian Rose [this message]
2009-07-07 11:57 ` Carsten Dominik
2009-07-06 11:16 ` 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:
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=87hbxpaje7.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ks@mocker.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).