Hi all,
Bastien writes:
> the manual would enjoy a subsection in "Hacking" on how to create
> a new exporter, either from scratch or as a derived exporter.
> (Such a subsection can be short enough, thanks to derived backend.)
FWIW, I started a rudimentary one.
This is "Adding export back-end
Hi Waldemar,
Waldemar Quevedo writes:
> By the way, does it exist somewhere a set of examples of Emacs
> org-mode -> html conversion for all org-mode features?
Not really -- and it would be nice to have one, especially for
developers like you who are in charge of an external exporter!
> I am m
On 3/9/13, Waldemar Quevedo wrote:
> By the way, does it exist somewhere a set of examples of Emacs
> org-mode -> html conversion for all org-mode features?
> (How are changes from org-mode -> html converstion from Emacs tested
> during development?)
+1
That would be great. I'd definitely donat
Hi Achim,
Achim Gratz wrote:
> Nicolas Goaziou writes:
>> As discussed a few days ago, here is a document describing the complete
>> Org syntax as read by the parser. I also added some comments. I am going
>> to put the Org file on Worg, so anyone can update it and fix mistakes.
>
> after some pla
Nicolas Goaziou writes:
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, so anyone can update it and fix mistakes.
after some playing with the Org manual in Org that T
Hello,
"Nicolas Richard" writes:
> As you know, "Comment" is also a french word meaning "how", and that
> could very well appear uppercased as the first word of a title. (I'd
> personally recommend against uppercasing titles, but I'd understand if
> someone wanted to customize the word for such
Hello,
Waldemar Quevedo writes:
> By the way, does it exist somewhere a set of examples of Emacs
> org-mode -> html conversion for all org-mode features?
> (How are changes from org-mode -> html converstion from Emacs tested
> during development?)
I don't think something like this exists. Thoug
Jambunathan K. writes:
> Still you haven't answered my "Fudging the mail reply headers" question
> to my satisfaction.
http://www.gnu.org/software/emacs/manual/html_node/message/Mailing-Lists.html
"A mailing list poster can use MFT to express that responses should be
sent to just the list, and no
Eric
Eric S Fraga writes:
> Jambunathan K writes:
>
>> You are a jerk, a BIG JERK.
>
> This is completely uncalled. What satisfaction do you gain from this?
> This is a brilliant, informative and polite mailing list except when it
> comes to your contributions.
>
> Don't bother answering bec
Jambunathan K writes:
> You are a jerk, a BIG JERK.
This is completely uncalled. What satisfaction do you gain from this?
This is a brilliant, informative and polite mailing list except when it
comes to your contributions.
Don't bother answering because I've added you to my spam database. I'
Hello,
orgm...@h-rd.org writes:
> What may help is to document the syntax machine readable and somewhat
> more formal.
I think it's a bit too early for that. The document describes the
current syntax, but also uncovers some ambiguous parts of that syntax,
which may need to be fixed (at least req
Hi,
I obviously did not send and actually lost a message I prepared two days
ago. I'll try again.
>> I suggest adding : The number of stars defines the level of the
>> headline.
>
> Does it belong to the syntax definition? Level is how Org uses syntax
> internally. Also the sentence, although rig
Hi Nicolas,
great work! It's fantastic that orgmode now gets a specification.
What may help is to document the syntax machine readable and somewhat
more formal. This ensures that there are less differences in
interpretation and that the specification can be used to generate an
orgmode pa
Hello
On 10 March 2013 13:12, Achim Gratz wrote:
> Jambunathan K writes:
> > Emacs lisp has a manual of it's own. I don't see how Org export
> > reference *cannot* end in Emacs.
>
> I said that I'm expecting these references to become part of the
> manual(s). I still expect that and will try t
Jambunathan K writes:
> Emacs lisp has a manual of it's own. I don't see how Org export
> reference *cannot* end in Emacs.
I said that I'm expecting these references to become part of the
manual(s). I still expect that and will try to help it along, but it
doesn't necessarily need to take the
Achim Gratz writes:
> Bastien writes:
>> No, the documents can go into the distribution with contributions from
>> anyone, because they won't be in Emacs. FSF assignment is needed only
>> for things that go into Emacs.
>
> I understood that these or substantial parts of it will end up in the
> O
Bastien writes:
> No, the documents can go into the distribution with contributions from
> anyone, because they won't be in Emacs. FSF assignment is needed only
> for things that go into Emacs.
I understood that these or substantial parts of it will end up in the
Org manual, which is in Emacs. I
Bastien
> But both reference documents don't fit into the manual IMO.
You are a jerk, a BIG JERK.
Jambunathan K.
--
Achim Gratz writes:
> Bastien writes:
>> That said, we can also bundle both documents into Org's distribution,
>> as .org files in the doc/ directory. And have a make rule to convert
>> them to .pdf and info docs.
>
> I don't want to be the party pooper, but if these documents should go
> into t
Bastien writes:
> That said, we can also bundle both documents into Org's distribution,
> as .org files in the doc/ directory. And have a make rule to convert
> them to .pdf and info docs.
I don't want to be the party pooper, but if these documents should go
into the distribution, then we must in
Bastien writes:
> But both reference documents don't fit into the manual IMO. They
> are great resources for developers, not for users. The footnotes
> are enough for advanced users who want to go beyond the manual.
That said, we can also bundle both documents into Org's distribution,
as .org
Hi Nicolas,
the manual would enjoy a subsection in "Hacking" on how to create
a new exporter, either from scratch or as a derived exporter.
(Such a subsection can be short enough, thanks to derived backend.)
>From this section, we can throw links to the exporter reference
document and the Org syn
Hello,
Jambunathan K writes:
> Please consider adding the Org spec (and also the exporter reference)
> document to the Org manual.
>
> This will be a good excuse for exercising the TexInfo exporter and see
> where it leads.
>
> Committing to Org or Worg has same load cycle. I feel there is more
Nicolas
>> Do you mind if I fix some obvious typos directly on Worg or do you'd
>> rather want patches?
>
> Please go ahead. This is on Worg so anyone can improve it.
Please consider adding the Org spec (and also the exporter reference)
document to the Org manual.
This will be a good excuse for
Hello,
Achim Gratz writes:
> Do you mind if I fix some obvious typos directly on Worg or do you'd
> rather want patches?
Please go ahead. This is on Worg so anyone can improve it.
> Nicolas Goaziou writes:
>> A core concept in this syntax is that only headlines and sections are
>> context-free
Hi Nicolas,
here are my first comments. I'm still trying to wrap my head around some
things, so if I'm off the map on something, please be patient.
Do you mind if I fix some obvious typos directly on Worg or do you'd
rather want patches?
Nicolas Goaziou writes:
> A core concept in this syntax i
On 9.3.2013, at 15:42, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> On 9.3.2013, at 11:52, Waldemar Quevedo wrote:
>>
>>> Hey Nicolas, this looks very detailed and I think it could be useful
>>> for people trying to write other parsers implementations for org-mode.
>>> T
Hello,
Carsten Dominik writes:
> On 9.3.2013, at 11:52, Waldemar Quevedo wrote:
>
>> Hey Nicolas, this looks very detailed and I think it could be useful
>> for people trying to write other parsers implementations for org-mode.
>> Thanks for sharing!
>
> Maybe someone knowledgeable can turn Nic
On 9.3.2013, at 11:52, Waldemar Quevedo wrote:
> Hey Nicolas, this looks very detailed and I think it could be useful
> for people trying to write other parsers implementations for org-mode.
> Thanks for sharing!
Maybe someone knowledgeable can turn Nicola's description into a formal parser
de
Hey Nicolas, this looks very detailed and I think it could be useful
for people trying to write other parsers implementations for org-mode.
Thanks for sharing!
By the way, does it exist somewhere a set of examples of Emacs
org-mode -> html conversion for all org-mode features?
(How are changes fro
Hello,
"Nicolas Richard" writes:
> Nicolas Goaziou writes:
>> As discussed a few days ago, here is a document describing the complete
>> Org syntax as read by the parser. I also added some comments. I am going
>> to put the Org file on Worg, so anyone can update it and fix mistakes.
>
> [for th
Nicolas Goaziou writes:
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, so anyone can update it and fix mistakes.
[for the record, the org file mentionned by Nicolas
Nicolas Goaziou writes:
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser.
Fantastique! :-) I'm preciously saving this!
François
Nicolas Goaziou writes:
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, so anyone can update it and fix mistakes.
Thanks Nicolas -- yep, that's really *great*!
--
Nicolas Goaziou writes:
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, so anyone can update it and fix mistakes.
Wonderful. This will be really useful!
Regards,
A
woow, this is awesome Nicolas, thank you!
- Carsten
On 7.3.2013, at 21:37, Nicolas Goaziou wrote:
> Hello,
>
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, s
Hello,
As discussed a few days ago, here is a document describing the complete
Org syntax as read by the parser. I also added some comments. I am going
to put the Org file on Worg, so anyone can update it and fix mistakes.
37 matches
Mail list logo
