From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: :link-up, :link-home
Date: Mon, 6 Jul 2009 13:56:23 +0200 [thread overview]
Message-ID: <DB8741DE-AA51-4BAF-A6AF-703647FA4D78@gmail.com> (raw)
In-Reply-To: <878wj2aur2.fsf@kassiopeya.MSHEIMNETZ>
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
next prev parent reply other threads:[~2009-07-06 11:56 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 [this message]
2009-07-06 14:41 ` Kyle Sexton
2009-07-06 16:03 ` Sebastian Rose
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB8741DE-AA51-4BAF-A6AF-703647FA4D78@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.