thanks. that also works for me.
Samuel Wales writes:
> i always put inactive timestamps in headlines, and sort both the
> outline and agenda using them. for example:
>
> * CONVERSATION [2015-08-31 Mon 14:41] john
> * CONVERSATION [2015-09-01 Tue 15:02] rms
>
> or newest first. they are
and here is my get function, likewise documented only for me and
written a long time ago but works well for me:
(defun alpha-org-entry-get (property &optional sg inherit)
"Return the value of PROPERTY, whether you are in the outline
or the agenda, by calling `org-entry-get'.
SG \(string given\)
hi john,
documented for myself only:
(defun alpha-org-timestamp-score (&optional sg)
"Return unix minutes as a floating point number.
;;;for 0..1
;;;Beware adding this to a much larger number (around 100); you will
;;;lose resolution. Multiply first by a number with a lot of
;;;zeroes. Then
i always put inactive timestamps in headlines, and sort both the
outline and agenda using them. for example:
* CONVERSATION [2015-08-31 Mon 14:41] john
* CONVERSATION [2015-09-01 Tue 15:02] rms
or newest first. they are visible and binary-searchable.
works perfectly for me.
Hi,
I am making a historical list of seminar speakers in an org-file. I am
trying to figure out the best way to store the dates so I can do
something later like find speakers from 2010, or to sort the speakers by
date etc...
Here is an example of my current thoughts. My questions are:
1. are org