OK. An updated version of org-info.js in now available on github as
well, as in worg.git.
NOTE: you MUST UPDATE ORG-INFO.JS, if you use the current git version.
The changes to org-info.js are backward compatible.
Hence you don't need to re-export everything.
Regards,
Sebastian
Carsten Domi
Thanks.
- Carsten
On Mar 3, 2009, at 11:14 AM, Sebastian Rose wrote:
Carsten Dominik writes:
I have now added a "content" container around all of body.
- Carsten
OK, I'll go and adjust org-info.js as needed now.
Best,
Sebastian
On Mar 3, 2009, at 2:16 AM, Richard Riley wrote:
Seb
Carsten Dominik writes:
> I have now added a "content" container around all of body.
>
> - Carsten
OK, I'll go and adjust org-info.js as needed now.
Best,
Sebastian
>
> On Mar 3, 2009, at 2:16 AM, Richard Riley wrote:
>
>> Sebastian Rose writes:
>>
>>> Richard Riley writes:
Sebastian
I have now added a "content" container around all of body.
- Carsten
On Mar 3, 2009, at 2:16 AM, Richard Riley wrote:
Sebastian Rose writes:
Richard Riley writes:
Sebastian Rose writes:
Richard Riley writes:
I really dont see the plethora of sec-id# that are currently
generated
bein
Sebastian Rose writes:
> Richard Riley writes:
>> Sebastian Rose writes:
>>
>>> Richard Riley writes:
I really dont see the plethora of sec-id# that are currently generated
being really useful since they change on each export if new stuff is
entered. This make existing CSS redun
Richard Riley writes:
> Sebastian Rose writes:
>
>> Richard Riley writes:
>>> I really dont see the plethora of sec-id# that are currently generated
>>> being really useful since they change on each export if new stuff is
>>> entered. This make existing CSS redundant unfortunately.
>>
>> The IDs
Sebastian Rose writes:
> Richard Riley writes:
>> I really dont see the plethora of sec-id# that are currently generated
>> being really useful since they change on each export if new stuff is
>> entered. This make existing CSS redundant unfortunately.
>
> The IDs in the section headings are not
Sebastian Rose writes:
>> So one that wraps everything in body. OK, let's call it "content".
>>
>> And then one that does contains the sections and footnotes, but
>> not the title, preamble, and postamble? Am I understanding this
>> correctly?
>
>
> Just the outer one then. As long as noone uses
Richard Riley writes:
> I really dont see the plethora of sec-id# that are currently generated
> being really useful since they change on each export if new stuff is
> entered. This make existing CSS redundant unfortunately.
Forgot to say: the ID's are, what the links in the TOC jump to. Also,
t
Richard Riley writes:
> I really dont see the plethora of sec-id# that are currently generated
> being really useful since they change on each export if new stuff is
> entered. This make existing CSS redundant unfortunately.
The IDs in the section headings are not meant for CSS styling. That's
wh
Carsten Dominik writes:
> On Mar 2, 2009, at 5:00 PM, Sebastian Rose wrote:
>
>>
>> OK - I failed badly :-(
>>
>> I think we can skip the extra element around the TOC.
>>
>> Here's why:
>>
>> As it looks now, the problem with the fixed TOC does not go away. My
>> old trick seems to work only
Carsten Dominik writes:
> On Mar 2, 2009, at 5:00 PM, Sebastian Rose wrote:
>
>>
>> OK - I failed badly :-(
>>
>> I think we can skip the extra element around the TOC.
>>
>> Here's why:
>>
>> As it looks now, the problem with the fixed TOC does not go away. My
>> old trick seems to work only f
On Mar 2, 2009, at 5:00 PM, Sebastian Rose wrote:
OK - I failed badly :-(
I think we can skip the extra element around the TOC.
Here's why:
As it looks now, the problem with the fixed TOC does not go away. My
old trick seems to work only for HTML doctype and/or tables...
Should
have
Richard Riley writes:
> Sebastian Rose writes:
>
>> Richard Riley writes:
>>> Sebastian Rose writes:
>>>
Richard Riley writes:
> It's been a while since I've looked at my org set up. One thing that
> always struck me as a bit hacky was my use of
>
> :preamble "
>
>
OK - I failed badly :-(
I think we can skip the extra element around the TOC.
Here's why:
As it looks now, the problem with the fixed TOC does not go away. My
old trick seems to work only for HTML doctype and/or tables... Should
have tested that one before...
So until now it's not g
Sebastian Rose writes:
> Richard Riley writes:
>> Sebastian Rose writes:
>>
>>> Richard Riley writes:
It's been a while since I've looked at my org set up. One thing that
always struck me as a bit hacky was my use of
:preamble "
and the corresponding postamble to
OK, so I will wait with making changes until you have
done some experimentation, maybe put that up somewhere,
so that others can have a look?
- Carsten
On Mar 2, 2009, at 12:58 PM, Sebastian Rose wrote:
Carsten Dominik writes:
Hi Sebastian,
On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote
Carsten Dominik writes:
> Hi Sebastian,
>
>
> On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:
>>
>> * Suggestions for names
>>
>> `wrap' is, what they use in typolight and some other CMSs. But
>> `content' sounds good to me too.
>>
>>
>>
>>
>>
>>
>> ...
>>
Hi Sebastian,
On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:
* Suggestions for names
`wrap' is, what they use in typolight and some other CMSs. But
`content' sounds good to me too.
...
2
Konfiguration
Richard Riley writes:
> Sebastian Rose writes:
>
>> Richard Riley writes:
>>> It's been a while since I've looked at my org set up. One thing that
>>> always struck me as a bit hacky was my use of
>>>
>>> :preamble "
>>>
>>> and the corresponding postamble to enclose the exported web pages into
Sebastian Rose writes:
> Richard Riley writes:
>> It's been a while since I've looked at my org set up. One thing that
>> always struck me as a bit hacky was my use of
>>
>> :preamble "
>>
>> and the corresponding postamble to enclose the exported web pages into a
>> "container" div. Is there a
Carsten Dominik writes:
> Hi Sebastian,
>
> I could do this. Would this mean that org-info.js would become
> backward not compatible with older pages? I believe quite a few people
> actually
> pull org-info.js from orgmode.org.
I'd have to rework it a bit. But I think it's worth it, since i
Hi Sebastian,
I could do this. Would this mean that org-info.js would become
backward not compatible with older pages? I believe quite a few
people actually
pull org-info.js from orgmode.org.
- Carsten
On Feb 28, 2009, at 12:37 PM, Sebastian Rose wrote:
Richard Riley writes:
It's been
Richard Riley writes:
> It's been a while since I've looked at my org set up. One thing that
> always struck me as a bit hacky was my use of
>
> :preamble "
>
> and the corresponding postamble to enclose the exported web pages into a
> "container" div. Is there a better way to do this? I would thi
It's been a while since I've looked at my org set up. One thing that
always struck me as a bit hacky was my use of
:preamble "
and the corresponding postamble to enclose the exported web pages into a
"container" div. Is there a better way to do this? I would think it
would be a common enough nee
25 matches
Mail list logo
