[-- Attachment #1.1: Type: text/plain, Size: 579 bytes --] What is the proper format for those variables? I've tried to set them several different ways: http://www.sitename.com index.html "http://www.sitename.com" "<a href='index.html'></a>" But nothing seems to change in my exported files. I've also tried setting them through the org file's local customisations (#+LINK_UP, etc..) The variable description that I found in emacs help says: Documentation: Where should the "UP" link of exported HTML pages lead? Is there another help section I can use that would give me an example of proper formatting? Thanks! -- Kyle Sexton [-- Attachment #1.2: Type: text/html, Size: 785 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
Hi Kyle,
currently :link-up and :link-home only show up when you use
org-info.js Javascript to display the file.
I would even say this is a bug. Any proposals on how these
links should be included in "normal" HTML output? Sebastian,
I am of course looking at you here :-)
- Carsten
On Jul 5, 2009, at 9:52 PM, Kyle Sexton wrote:
> What is the proper format for those variables? I've tried to set
> them several different ways:
>
> http://www.sitename.com
> index.html
> "http://www.sitename.com"
> "<a href='index.html'></a>"
>
> But nothing seems to change in my exported files. I've also tried
> setting them through the org file's local customisations (#+LINK_UP,
> etc..)
>
> The variable description that I found in emacs help says:
>
> Documentation:
> Where should the "UP" link of exported HTML pages lead?
>
> Is there another help section I can use that would give me an
> example of proper formatting?
>
> Thanks!
>
> --
> Kyle Sexton
> _______________________________________________
> 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
Kyle Sexton <ks@mocker.org> writes:
> What is the proper format for those variables? I've tried to set them
> several different ways:
>
> http://www.sitename.com
> index.html
> "http://www.sitename.com"
> "<a href='index.html'></a>"
#+INFOJS_OPT: up:index.html home:/index.html
Sebastian
On Jul 6, 2009, at 1:58 PM, Sebastian Rose wrote: > Carsten Dominik <carsten.dominik@gmail.com> writes: >> Hi Kyle, >> >> currently :link-up and :link-home only show up when you use >> org-info.js Javascript to display the file. >> >> I would even say this is a bug. Any proposals on how these >> links should be included in "normal" HTML output? Sebastian, >> I am of course looking at you here :-) > > > This is hard to tell. I'd place them somewhere above the title or to > the > very right next to the title. > > But then again, we'd need an option to exclude those links for people > that use a menu anyway. We could only insert this part if the links are defined, and org-info could swallow this part....? - Carsten > > Things like this make me think of the old idea we've been talking > about > from time to time: > > Have a somewhat template based export (doesn't generic export work a > little bit like that?) and just transform everything to HTML ( `&' => > `&', export blocks, resolve internal links...). > > > > Simple solution (links above title in this case): > > <div style="text-align:right;font-size:70%;white-space:nowrap;"> > <a accesskey="h" href="./link_up.html"> UP </a> > | > <a accesskey="H" href="../link_home.html"> HOME </a> > </div> > <h1 id="title"> THE TITLE </h1> > > > > What do the others think? > > > > Sebastian
Carsten Dominik <carsten.dominik@gmail.com> writes:
> Hi Kyle,
>
> currently :link-up and :link-home only show up when you use
> org-info.js Javascript to display the file.
>
> I would even say this is a bug. Any proposals on how these
> links should be included in "normal" HTML output? Sebastian,
> I am of course looking at you here :-)
This is hard to tell. I'd place them somewhere above the title or to the
very right next to the title.
But then again, we'd need an option to exclude those links for people
that use a menu anyway.
Things like this make me think of the old idea we've been talking about
from time to time:
Have a somewhat template based export (doesn't generic export work a
little bit like that?) and just transform everything to HTML ( `&' =>
`&', export blocks, resolve internal links...).
Simple solution (links above title in this case):
<div style="text-align:right;font-size:70%;white-space:nowrap;">
<a accesskey="h" href="./link_up.html"> UP </a>
|
<a accesskey="H" href="../link_home.html"> HOME </a>
</div>
<h1 id="title"> THE TITLE </h1>
What do the others think?
Sebastian
[-- Attachment #1.1: Type: text/plain, Size: 1217 bytes --] On Mon, Jul 6, 2009 at 5:08 AM, Carsten Dominik <carsten.dominik@gmail.com>wrote: > Hi Kyle, > > currently :link-up and :link-home only show up when you use > org-info.js Javascript to display the file. > > I would even say this is a bug. Any proposals on how these > links should be included in "normal" HTML output? Sebastian, > I am of course looking at you here :-) > > - Carsten > > Glad to know it's a potential bug and not me going crazy. :) Perhaps as a short term fix the variable documentation for things dependent on infojs could have that as a note. 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. I'm trying to move my entire website to being generated from org-mode. :P -- Kyle Sexton [-- Attachment #1.2: Type: text/html, Size: 1661 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
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
THis is now fixed. if link-up or link-home are defined, also normal
HTML export will list them.
- Carsten
On Jul 6, 2009, at 4:41 PM, Kyle Sexton wrote:
>
>
> On Mon, Jul 6, 2009 at 5:08 AM, Carsten Dominik <carsten.dominik@gmail.com
> > wrote:
> Hi Kyle,
>
> currently :link-up and :link-home only show up when you use
> org-info.js Javascript to display the file.
>
> I would even say this is a bug. Any proposals on how these
> links should be included in "normal" HTML output? Sebastian,
> I am of course looking at you here :-)
>
> - Carsten
>
>
> Glad to know it's a potential bug and not me going crazy. :)
> Perhaps as a short term fix the variable documentation for things
> dependent on infojs could have that as a note.
>
> 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. I'm trying to move my entire website to being generated
> from org-mode. :P
>
> --
> Kyle Sexton