From: Mark Elston <firstname.lastname@example.org> To: Samuel Wales <email@example.com> Cc: Org Mode List <firstname.lastname@example.org> Subject: Re: Automatic Update of Org files Date: Thu, 05 Feb 2009 15:13:37 -0800 [thread overview] Message-ID: <498B72A1.email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Samuel, Thanks for the info. I will have to digest this and see if it fits. One concern I have with this approach (and I may not have fully grasped what you intended) is that the original source files have the current information like deadlines, etc that I want used when creating my agenda for the week. If I want more information about the agenda item I will navigate to it and hit <Return> which takes me to the generated Org file. Once there, I would like to be able to add notes as necessary. Alternatively, I suppose I could navigate to the notes if there is a simple mechanism for this. I don't really understand all you described below but I will try playing with it and see what comes out. Mark * Samuel Wales wrote (on 2/5/2009 2:40 PM): > IIUC, source is not under your complete control. You need it orgified > but also annotated. There are various annotation mechanisms. My > comments on the remember redesign might be relevant. > > You could consider going backward. Have your org file contain links > to the read-only stuff. Put entry IDs in the read-only stuff. > > Dunno if this helps. > > Here is something I had lying around: > > Another feature is to have org-registry show on the mode > line when a link points to the current buffer's object (w3m > page, file, dired, etc.). You click on it to go to the org > file link. See my remember suggestions in a previous thred > for more re annotations, bookmarks, and registry. > > I proposed this before: > > === snip > > Extension #2 to the bookmark idea. > > My idea is to always have annotations available for > emacs-w3m, dired, files, like org-annotate-file, just with > more modes. > > You can see in the mode line that whatever buffer you are in > has an annotation, and you can make an annotation. You can > also go to the annotation. > > The annotations are stored in an org file anywhere in the > hierarchy. Thus, if you want, annotations on a doctor's web > site can be stored in the entry for that doctor that is in > your org file. If you visit that web site from any source, > even Google, the mode line says that it is annotated. Then > you can pull up that entry with a command. > > Likewise with files or dired or whatever. For example, you > can comment org.el or /etc/passwd without having to modify > them. > > Remember code seems a plausible place to arrange for > choosing a location and putting a note into it. Annotations > are like bookmarks with text that also go the other > direction. It's natural to combine the idea of a bookmark > and the idea of an annotation. > > You might want the mode line to say "there is bookmark to > this (web page, file, etc.)" as one character and "there is > a text note about this" as another character. Thus, if you > have annotated a file and the file is unmodified, you will > see "-u:--!!" and if you have merely bookmarked the location > without commenting on it, then you will see "-u:--!-". > === snip > >
next prev parent reply other threads:[~2009-02-05 23:13 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 [this message] 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 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=498B72A1.email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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).