Re: How to add entries to an org file, not diary

[Darlan Cavalcante Moreira <darcamo@gmail.com>]

Perfect, thanks!

- Darlan
At Tue, 10 Nov 2009 08:23:50 +0100,
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> 
> 
> On Nov 10, 2009, at 2:57 AM, Darlan Cavalcante Moreira wrote:
> 
> >
> > This is really nice.
> > Thanks Carsten!
> >
> > I currently use a subtree in my main org file to put dates for
> > appointments, birthdays, etc.. Having a native way to do that will
> > save time and I my approach could became to cluttered in the future.
> >
> > I only miss an easy way to change the date of an appointment, for
> > example. The usual refiling is not very efficient here, since the
> > diary file will have a lot of headings and one may need to refile it
> > to a heading that doesn't exist yet. Maybe org-refile could test if
> > this is the diary file and if it is, offer an interface similar to the
> > usual time stamp insertion.
> 
> Hi Darlan,
> 
> the simple answer is:  Don't be religious about where
> in the date three the entry is located.  Placing all these
> entries into a tree is a convenience, but it has no significance
> for the interpretation of the entries when the agenda is constructed.
> Each entry still contains a time stamp, and changing the appointment
> rescheduling means that this time stamp is changed.
> The entry will still be located under the day where it initially
> belonged, but so what?
> 
> The longer answer would be to write a function that cleans up
> the tree and moves all entries to the right date.  Not too hard
> to write.  In fact, I have just added it:
> 
> M-x org-datetree-cleanup RET
> 
> If your date tree is part of a larger buffer,
> you might want to narrow the buffer to the date tree
> before running this command.
> 
> - Carsten
> 
> >
> > But this is something minor.
> > Again, thanks for this and org-mode.
> >
> >
> > At Mon, 9 Nov 2009 22:09:23 +0100,
> > Carsten Dominik <carsten.dominik@gmail.com> wrote:
> >>
> >> Hi Stephen,
> >>
> >> On Nov 6, 2009, at 4:16 PM, Stephen Eglen wrote:
> >>
> >>> Dear all,
> >>> If I'm visting an agenda (C-c a a) buffer, and want to add a diary
> >>> entry
> >>> for a particular day, I can use org-agenda-diary-entry, bound to  
> >>> 'i'.
> >>> This inserts an entry in my diary file.
> >>>
> >>> What I'd like to do is add the entry instead to an org file,
> >>> e.g. 'agenda.org' where I currently store all diary-like entries.   
> >>> Is
> >>> that functionality available?  (Am trying to wean myself off diary
> >>> files, after many years of using it...)
> >>
> >> If you get the latest Org version from the git server, you can
> >> configure the variable `org-agenda-diary-file' to point to your
> >> "diary.org" file or any other Org-mode file.  This should be a
> >> file dedicated for general appointments, anniversaries
> >> etc.
> >>
> >> Then `i' in the agenda will create new entries in that file.
> >> Simple entries (day and block) will be placed into an outline
> >> tree that is based on dates:  Top-level years, level 2 months,
> >> level 3 days[1].  I have always wanted to have something
> >> like this, so that it will be easy to archive old stuff!  So thanks
> >> for giving me a reason to finally make it.
> >>
> >> Right now I have implemented
> >>
> >> i d   for day entries,
> >> i b   for blocks,
> >> i a   for anniversaries (which will be collected under a special
> >>       heading "Anniversaries" in your `diary.org'
> >> i j   To jump to the cursor date in the date tree
> >>
> >> What else would be useful?
> >>
> >> The same command will also be bound to the `i' key in the
> >> calendar (calendar restart required), so you can make the same
> >> kind of entries from the calendar - very convenient at times,
> >> in particular for long blocks.
> >>
> >> The basics of these new commands seem to work OK, but it
> >> is quite possible that I have not yet thought this through
> >> fully.  Let me know what I am missing, so that we can tweak it.
> >>
> >> - Carsten
> >>
> >> [1] If there is any entry in this file with a DATE_TREE property set,
> >> the tree will be build under that entry.
> >>
> >>
> >> _______________________________________________
> >> Emacs-orgmode mailing list
> >> Remember: use `Reply All' to send replies to the list.
> >> Emacs-orgmode@gnu.org
> >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 
> - Carsten
> 
> 
>