From: Mark Elston <m.elston@advantest-ard.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Announcing my Python module to read org-mode files
Date: Mon, 16 Mar 2009 18:40:46 -0700 [thread overview]
Message-ID: <49BEFF9E.5050408@advantest-ard.com> (raw)
In-Reply-To: <loom.20090317T011739-354@post.gmane.org>
* Charles Cave wrote (on 3/16/2009 6:22 PM):
> Mark Elston <m.elston <at> advantest-ard.com> writes:
>
>> The only thing better would be a way to use this package to
>> update the nodes and then write them back out. Hmmmmm......
>
> The changes to the package to write the node output out are...
>
> 1. A means of storing the org-mode preamble .. all the lines before
> the first headline. Maybe this could be in a node with level 0
> and headline of null. The bodytext of this object could be
> the preamble lines.
>
> 2. A method to output a node in ord-mode format echoing the
> ** prefix, TODO tag, headline, tags, properties and body text.
>
> 3. The module currently discards lines beginning with #.
> These should now be preserved.
>
> I wouldnt imagine this being a great deal of work.
> I will add this to my (very long list) of things to do!
>
Actually, for my purposes, I think the problem is simpler. As these
files are automatically generated (and, eventually, updated) the
preamble is 'pre-defined' for each file. It could be written out
new each time the file is updated. So #1 and #3 are non-issues as far
as I am concerned.
#2 is, of course, the primary issue. I will probably need to deal with
properties as I get more involved in 'tweaking' my generators so I am
thrilled to see you already support them.
Mark
prev parent reply other threads:[~2009-03-17 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 3:37 Announcing my Python module to read org-mode files Charles Cave
2009-03-15 8:35 ` Ian Barton
2009-03-16 18:28 ` Mark Elston
2009-03-17 1:22 ` Charles Cave
2009-03-17 1:40 ` Mark Elston [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49BEFF9E.5050408@advantest-ard.com \
--to=m.elston@advantest-ard.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).