Thread: [CEDET-devel] Org-mode
Brought to you by:
zappo
From: Konrad S. <sco...@gm...> - 2010-10-30 07:45:48
|
Hey! Is anybody working on Org-mode? My main interest is to build a parser to manipulate the nodes of the resulting tree and save them back. Tips on how to get started are also welcome. Cheers, -- "O conservadorismo expressa a resistência natural, geral e espontânea da alma humana a deixar-se usar como instrumento a serviço de promessas irrealizáveis sob o guiamento de líderes pretensamente iluminados." -OdeC |
From: Eric M. L. <er...@si...> - 2010-11-03 12:15:54
|
On 10/30/2010 03:45 AM, Konrad Scorciapino wrote: > Hey! > > Is anybody working on Org-mode? My main interest is to build a parser to > manipulate the nodes of the resulting tree and save them back. Tips on > how to get started are also welcome. > I know of no one doing that. I don't know what org-mode's code structure is like, but I'd assume it already has a parser, and you could adapt the output to Semantic tag format. The HTML parser also handles arbitrary text so you could look in semantic-html to see what sort of things that does. Eric |
From: Lennart B. <len...@gm...> - 2010-11-03 12:34:36
|
On Wed, Nov 3, 2010 at 1:15 PM, Eric M. Ludlam <er...@si...> wrote: > On 10/30/2010 03:45 AM, Konrad Scorciapino wrote: >> Hey! >> >> Is anybody working on Org-mode? My main interest is to build a parser to >> manipulate the nodes of the resulting tree and save them back. Tips on >> how to get started are also welcome. >> > > I know of no one doing that. I don't know what org-mode's code > structure is like, but I'd assume it already has a parser, and you could > adapt the output to Semantic tag format. > > The HTML parser also handles arbitrary text so you could look in > semantic-html to see what sort of things that does. There are different exporters for org-mode. Currently we are trying to make an exporter to ODT files. I think a parser would come in handy. |
From: David E. <de...@ra...> - 2010-11-03 12:45:45
|
Eric M. Ludlam writes: > On 10/30/2010 03:45 AM, Konrad Scorciapino wrote: >> Hey! >> >> Is anybody working on Org-mode? My main interest is to build a parser to >> manipulate the nodes of the resulting tree and save them back. Tips on >> how to get started are also welcome. >> > > I know of no one doing that. I don't know what org-mode's code > structure is like, but I'd assume it already has a parser, and you could > adapt the output to Semantic tag format. org uses outline-mode, and I don't think there's something like a 'global parser', since the outline structure can be nicely parsed locally in the current context. I think a good starting point would be the various export functions from org-mode. For example, org-latex.el has the function org-export-latex-parse-global. -David |
From: Eric M. L. <er...@si...> - 2010-11-03 14:08:05
|
On 11/03/2010 08:32 AM, David Engster wrote: > Eric M. Ludlam writes: >> On 10/30/2010 03:45 AM, Konrad Scorciapino wrote: >>> Hey! >>> >>> Is anybody working on Org-mode? My main interest is to build a parser to >>> manipulate the nodes of the resulting tree and save them back. Tips on >>> how to get started are also welcome. >>> >> >> I know of no one doing that. I don't know what org-mode's code >> structure is like, but I'd assume it already has a parser, and you could >> adapt the output to Semantic tag format. > > org uses outline-mode, and I don't think there's something like a > 'global parser', since the outline structure can be nicely parsed > locally in the current context. I think a good starting point would be > the various export functions from org-mode. For example, org-latex.el > has the function org-export-latex-parse-global. Perhaps a generic parser that deals with outline mode would make it possible to tagify any outlined buffer, including org-mode. ie- it would identify the outline features, and parse based on those regexps. That would be kind of neat, and lead to a wide range of possible new tools for structured text that isn't code beyond the simple stuff enabled by html and texinfo parsers. Eric |
From: Lennart B. <len...@gm...> - 2010-11-04 15:45:59
|
On Thu, Nov 4, 2010 at 3:37 PM, Carsten Dominik <car...@gm...> wrote: > > On Nov 3, 2010, at 1:34 PM, Lennart Borgman wrote: > >> On Wed, Nov 3, 2010 at 1:15 PM, Eric M. Ludlam <er...@si...> >> wrote: >>> >>> On 10/30/2010 03:45 AM, Konrad Scorciapino wrote: >>>> >>>> Hey! >>>> >>>> Is anybody working on Org-mode? My main interest is to build a parser to >>>> manipulate the nodes of the resulting tree and save them back. Tips on >>>> how to get started are also welcome. >>>> >>> >>> I know of no one doing that. I don't know what org-mode's code >>> structure is like, but I'd assume it already has a parser, and you could >>> adapt the output to Semantic tag format. >>> >>> The HTML parser also handles arbitrary text so you could look in >>> semantic-html to see what sort of things that does. >> >> There are different exporters for org-mode. >> >> Currently we are trying to make an exporter to ODT files. I think a >> parser would come in handy. > > > org-html.el is probably the best starting point to make a complete parser. > It does a very detailed analysis of the text. > > We should have built all the exporters on the same parser - unfortunately we > did not. One of the hard to correct mistakes we made in early development. Then perhaps the best we can do now is starting by breaking up org-hml.el in the parser and a callback function for writing the export. After that we can add new exports by adding new callback functions. |
From: Lennart B. <len...@gm...> - 2010-11-04 18:45:08
|
On Thu, Nov 4, 2010 at 7:04 PM, Jambunathan K <kja...@gm...> wrote: >> >> Then perhaps the best we can do now is starting by breaking up >> org-hml.el in the parser and a callback function for writing the >> export. After that we can add new exports by adding new callback >> functions. > > The suggested refactoring could be a side-effect of org-odt.el that is > shaping up from org-html.el. Note that the refactoring happens or > atleast is visible in org-odt.el (which I control) and *not* in > org-html.el (which is in the field) > > The main challenge with breaking up org-html.el first and then say > plugging in org-odt.el to that later is: > > 1. Code-churn that it would create in org-html.el > 2. Proving that *nothing* in HTML export actually breaks. I am playing a bit with refactoring. A main issue might be how refined the callback function should be. Not sure what I think yet, but I will come back with an example. |