I'm coming a little late to this thread so apologies!
Most of the previous thread has focused on analysing the various pros
and cons of the various documentation methods, INFOText/html/org, to
produce the final documentation.
I would like to suggest that whatever method is used that
it also suppo
Nicolas Goaziou writes:
> Hello,
>
> Jonathan Leech-Pepin writes:
>
>> I’m trying to remember why I didn’t implement indexes as properties
>> (it may well have been because I simply didn’t consider it). Assuming
>> there’s nothing in the exporter to prevent converting properties to
>> text after
Hello,
Jonathan Leech-Pepin writes:
> I’m trying to remember why I didn’t implement indexes as properties
> (it may well have been because I simply didn’t consider it). Assuming
> there’s nothing in the exporter to prevent converting properties to
> text after headlines it could work. Treat comm
Hi,
On May 18, 2016 5:21:06 AM EDT, Rasmus wrote:
>Hi,
>
>Nick Dokos writes:
>
>> I believe the main obstacle is that the emacs policy requires a
>texinfo
>> manual for all its component parts.
>
>What is the "component parts"? I couldn't find the definition.
>
>> If that can be generated auto
Hi,
Nick Dokos writes:
> I believe the main obstacle is that the emacs policy requires a texinfo
> manual for all its component parts.
What is the "component parts"? I couldn't find the definition.
> If that can be generated automatically from the org document, then any
> objections probably
On Tue, 17 May 2016, Thomas S. Dye wrote:
Aloha Nicolas,
Nicolas Goaziou writes:
"Thomas S. Dye" writes:
Nicolas Goaziou writes:
Once the manual is up-to-date, we might consider moving it to doc/ in
main distribution.
IIRC, Bastien doesn't like this idea.
Really? I admit I would be s
"Thomas S. Dye" writes:
> Aloha Nicolas,
>
> Nicolas Goaziou writes:
>
>> "Thomas S. Dye" writes:
>>
>>> Nicolas Goaziou writes:
Once the manual is up-to-date, we might consider moving it to doc/ in
main distribution.
>>>
>>> IIRC, Bastien doesn't like this idea.
>>
>> Really? I a
Aloha Nicolas,
Nicolas Goaziou writes:
> "Thomas S. Dye" writes:
>
>> Nicolas Goaziou writes:
>>>
>>> Once the manual is up-to-date, we might consider moving it to doc/ in
>>> main distribution.
>>
>> IIRC, Bastien doesn't like this idea.
>
> Really? I admit I would be surprised. Do you recall w
"Thomas S. Dye" writes:
> Nicolas Goaziou writes:
>>
>> Once the manual is up-to-date, we might consider moving it to doc/ in
>> main distribution.
>
> IIRC, Bastien doesn't like this idea.
Really? I admit I would be surprised. Do you recall why so, or do you
have any reference about it?
Regard
Aloha Nicolas,
Nicolas Goaziou writes:
>
> Once the manual is up-to-date, we might consider moving it to doc/ in
> main distribution.
IIRC, Bastien doesn't like this idea.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Eric Abrahamsen writes:
> "Thomas S. Dye" writes:
>
>> Aloha Eric,
>>
>> Eric Abrahamsen writes:
>>
>>> "Thomas S. Dye" writes:
>>>
Rasmus writes:
> Once upon a time Tom ported the Org manual. It's on his github, probably
> under tsdye.
https://github.com/tsdye/orgm
Rasmus writes:
> Eric Abrahamsen writes:
>
>> What might be nice to have in contrib is an exporter derived from the
>> current texinfo exporter, but specifically set up for Gnu project
>> manuals: so it does the copyright header, and index macros, and maybe
>> even the proper DIR integration (?)
Eric Abrahamsen writes:
> What might be nice to have in contrib is an exporter derived from the
> current texinfo exporter, but specifically set up for Gnu project
> manuals: so it does the copyright header, and index macros, and maybe
> even the proper DIR integration (?).
Maybe a "GNU template
Hello,
"Thomas S. Dye" writes:
> I'm happy if someone moves it to contrib/.
Done.
> Is there anything for me to do before/after that happens?
Not really. Of course, feel free to help keeping (making) it up-to-date
if your spare time allows it.
Once the manual is up-to-date, we might consider
"Thomas S. Dye" writes:
> Aloha Eric,
>
> Eric Abrahamsen writes:
>
>> "Thomas S. Dye" writes:
>>
>>> Rasmus writes:
>>>
Once upon a time Tom ported the Org manual. It's on his github, probably
under tsdye.
>>>
>>> https://github.com/tsdye/orgmanual
>>
>> Hey, that's perfect! Dunno if
Aloha Eric,
Eric Abrahamsen writes:
> "Thomas S. Dye" writes:
>
>> Rasmus writes:
>>
>>> Once upon a time Tom ported the Org manual. It's on his github, probably
>>> under tsdye.
>>
>> https://github.com/tsdye/orgmanual
>
> Hey, that's perfect! Dunno if that's what I was remembering, but that's
"Thomas S. Dye" writes:
> Rasmus writes:
>
>> Once upon a time Tom ported the Org manual. It's on his github, probably
>> under tsdye.
>
> https://github.com/tsdye/orgmanual
Hey, that's perfect! Dunno if that's what I was remembering, but that's
exactly what I was after. Even better if it ends
Aloha Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> "Thomas S. Dye" writes:
>
>> Rasmus writes:
>>
>>> Once upon a time Tom ported the Org manual. It's on his github, probably
>>> under tsdye.
>>
>> https://github.com/tsdye/orgmanual
>
> What about moving it to "contrib/"? It could help keeping
Hello,
"Thomas S. Dye" writes:
> Rasmus writes:
>
>> Once upon a time Tom ported the Org manual. It's on his github, probably
>> under tsdye.
>
> https://github.com/tsdye/orgmanual
What about moving it to "contrib/"? It could help keeping it up-to-date.
Regards,
--
Nicolas Goaziou
Rasmus writes:
> Once upon a time Tom ported the Org manual. It's on his github, probably
> under tsdye.
https://github.com/tsdye/orgmanual
--
Thomas S. Dye
http://www.tsdye.com
I don't recall it, but these look along similar lines?
-
https://www.reddit.com/r/emacs/comments/2bummt/changing_emacs_documentation_system_from_texinfo/
- https://lwn.net/Articles/625072/
John
On Sat, May 14, 2016 at 2:21 AM, Eric Abrahamsen
wrote:
> I remember a while ago there was a discuss
Eric Abrahamsen writes:
> I remember a while ago there was a discussion (on emacs.devel? I can't
> remember) about the format for Emacs manuals, and Org came into it, and
> at some point someone (Rasmus? Achim Gratz? I can't remember this
> either) posted a template for doing Emacs manuals in Org
Copying Oleh as I believe he uses org to generate Info manual for his ivy
package.
--
--
Kaushal Modi
I remember a while ago there was a discussion (on emacs.devel? I can't
remember) about the format for Emacs manuals, and Org came into it, and
at some point someone (Rasmus? Achim Gratz? I can't remember this
either) posted a template for doing Emacs manuals in Org. It was
particularly useful becau
24 matches
Mail list logo