From: Mark Elston <email@example.com> To: Manish <firstname.lastname@example.org> Cc: Org Mode List <email@example.com> Subject: Re: Automatic Update of Org files Date: Fri, 06 Feb 2009 11:55:03 -0800 [thread overview] Message-ID: <498C9597.firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Manish, I actually have it printed out and am going through it. One of the reasons I would prefer to keep notes *with* the entries I generate is that I would like to eventually export both the entries and notes to a file I can print out and take with me to meetings. Either LaTeX export or text export would work. In any case, I thought it would be simpler if everything were in one place. Both the org-registry and the org-annotate-file put notes separate from the entries. While this is OK for online work it is more problematic when you want to create a set of notes to take to a meeting. At least it seems so to me. Mark * Manish wrote (on 2/6/2009 11:34 AM): > On Sat, Feb 7, 2009 at 12:24 AM, Mark Elston wrote: > [...] >> My biggest concern is keeping any notes I add to items I have >> extracted from these various sources during an update process. >> >> I tried the org-registry package mentioned by Samuel but it didn't >> load and initialize. > > I haven't had a chance to use it but you could take a look at > contrib/lisp/org-annotate-file.el as well. It seems to do something > similar. >
next prev parent reply other threads:[~2009-02-06 19:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-05 22:03 Mark Elston 2009-02-05 22:40 ` Samuel Wales 2009-02-05 23:13 ` Mark Elston 2009-02-06 15:19 ` David Thole 2009-02-06 18:54 ` Mark Elston 2009-02-06 19:34 ` Manish 2009-02-06 19:55 ` Mark Elston [this message] 2009-02-07 5:37 ` William Henney
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=498C9597.firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Automatic Update of Org files' \ /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
Code repositories for project(s) associated with this 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).