Please do not CC me on Emacs bug threads. If there's an issue in Flycheck
please take it to our issue tracker at
https://github.com/flycheck/flycheck/issues where we can keep track of it.
2013/9/30 Rasmus :
> Hi Sebastian,
>
> Sebastian Wiesner writes:
>
>> can I limit a subtree to be exported with specific backends only?
>> I.e. only to HTML, but not Texinfo or LaTeX?
>>
>> Background: I am trying to simplify the documentation of one of my
2013/9/30 Sebastien Vauban :
> A partly manual solution would be to use tags for which sections to export in
> which backend, make a sparse tree with the backend you're interested to
> export,
> and export what's visible?
I am by far not an Org mode expert, and have never used sparse trees.
Would
content on the website that should
not appear in the manual and vice versa.
So long,
Sebastian Wiesner
2013/7/3 Bastien :
> Sebastian Wiesner writes:
>
>> Is there a single assignment for just one specific patch? I am not
>> going to assign the FSF copyright for any and every future change to
>> Emacs I might create.
>
> The FSF policy is that you cannot assign your
2013/7/3 Bastien :
> Sebastian Wiesner writes:
>
>> 2013/7/3 Bastien :
>>> Well, that's too much work for me now. Hopefully someone who needs
>>> this can help too.
>>
>> I'll probably give it a shot, depending on how much free time I can
2013/7/3 Bastien :
> Well, that's too much work for me now. Hopefully someone who needs
> this can help too.
I'll probably give it a shot, depending on how much free time I can
find in the next weeks.
You said, you might incorporate such an extension into Org, but isn't
Org covered by Copyright
2013/7/3 Bastien :
> Sebastian Wiesner writes:
>
>> Ideally the HTML exporter would consult this database when exporting
>> info links, to find out where the corresponding HTML manual is
>> published.
>
> I see, thanks. Is it safe to assume that htmlxref.cnf wi
2013/7/3 Bastien :
> Hi Sebastian,
>
> Sebastian Wiesner writes:
>
>> I'll put Org mode migration of said manual on hold, for I currently
>> lack the time to write a proper link exporter myself.
>
> I gave this a closer look: one problem is that info links are
2013/7/3 Bastien :
> Hi Sebastian,
>
> Sebastian Wiesner writes:
>
>> Hardly the answer I hoped to get.
>
> Please let us know the answer you hoped to get, it will
> surely help us giving it :)
Uh, I hoped for a “easy, just toggle that customize setting” sort of
answ
2013/6/30 Bastien :
> Hi Sebastian,
>
> Sebastian Wiesner writes:
>
>> how can I customize "info:" links in HTML output?
>
> Look at org-info.el in the source code.
>
> You can extend
>
> (org-add-link-type "info" 'org-info-open)
>
many "info:"
links, but each of these is important and must be rendered properly in
both, Texinfo and HTML output.
Greetings,
Sebastian Wiesner
2013/2/24 Mike McLean :
>
> On Feb 24, 2013, at 11:03 AM, Sebastian Wiesner wrote:
>
>> Hello,
>>
>> how is the online manual of Org mode [1] rendered? Especially, how is
>> the awesome table of contents on the right sight created?
>
> It is done through C
13 matches
Mail list logo
