Eric Abrahamsen e...@ericabrahamsen.net writes:
Okay, thanks. Since this is part of a function, I guess I should assume
the (progn... behavior above, assume `org-element-at-point' is going to
return a paragraph, and then work up from there to see if I'm in a
log-list. Is that right?
That's
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Right now it looks like the central cond statement in
`org-add-log-setup' is as close as we've got to a canonical definition
of where a heading's log list is to be found. Should I just write my own
version of this, or would you be open
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Right now it looks like the central cond statement in
`org-add-log-setup' is as close as we've got to a canonical definition
of where a heading's log list is to be found. Should I just
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Right now it looks like the central cond statement in
`org-add-log-setup' is as close as we've got to a canonical definition
of where a heading's log list is to be found. Should I just
Eric Abrahamsen e...@ericabrahamsen.net writes:
I was just fooling with this a bit, and am noticing some odd (to me)
behavior. If I start with emacs -Q, then (goto-char (org-log-beginning))
takes me to the start of a :LOGBOOK: drawer, and (org-element-at-point)
returns the drawer. That works
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Eric Abrahamsen e...@ericabrahamsen.net writes:
I was just fooling with this a bit, and am noticing some odd (to me)
behavior. If I start with emacs -Q, then (goto-char (org-log-beginning))
takes me to the start of a :LOGBOOK: drawer, and
Pete Ley peteley11...@gmail.com writes:
All I've got now are a function that finds the logbook, and another that
parses the log items and normalizes them: extracts the TODO
states/timestamps/key-values and sets them as properties on the items
themselves. Then you've got a pretty good basis
All I've got now are a function that finds the logbook, and another that
parses the log items and normalizes them: extracts the TODO
states/timestamps/key-values and sets them as properties on the items
themselves. Then you've got a pretty good basis from which to do
reporting.
Hooking into
Hi,
Eric Abrahamsen e...@ericabrahamsen.net writes:
I've been (very gradually) working on something I'm calling org-log, for
just this sort of situation -- a library that would possibly go
underneath org-habit and maybe even org-clock. It would look like:
* Read book
:LOGBOOK:
- Note
Hi Daya
On Mon, Oct 20, 2014 at 4:33 PM, Daya Atapattu atapat...@gmail.com wrote:
I like to schedule studying a book: It would be scheduled as Read pages
100-125. Then the next day it should read Read pages 126-150. The
description of the habit varies; org-mode picks that up sequentially
Samuel Loury konubi...@gmail.com writes:
Hi,
Eric Abrahamsen e...@ericabrahamsen.net writes:
I've been (very gradually) working on something I'm calling org-log, for
just this sort of situation -- a library that would possibly go
underneath org-habit and maybe even org-clock. It would look
Is there a way to create a habit that picks-up the description from a list?
I like to schedule studying a book: It would be scheduled as Read pages
100-125. Then the next day it should read Read pages 126-150. The
description of the habit varies; org-mode picks that up sequentially from a
Hi Daya,
Daya Atapattu atapat...@gmail.com writes:
Is there a way to create a habit that picks-up the description from a
list?
I like to schedule studying a book: It would be scheduled as Read
pages 100-125. Then the next day it should read Read pages
126-150. The description of the
Thanks for the response, Bastien.
I guess, short of writing some elisp code, I will have to reschedule each
evening for next day.I can't schedule in advance, because I miss some
days.
- Daya
On Mon, Oct 20, 2014 at 10:52 AM, Bastien b...@gnu.org wrote:
Hi Daya,
Daya Atapattu
Daya Atapattu writes:
Is there a way to create a habit that picks-up the description
from a list?
I like to schedule studying a book: It would be scheduled as
Read pages 100-125. Then the next day it should read Read
pages 126-150. The description of the habit varies; org-mode
picks that
As Bastien said, this doesn't really fit the idea of a habit, but I
think there is a reasonable non-elisp way of tweaking it to fit. Maybe
it would help.
What if you had something like this:
* Read book
:LOGBOOK:
- Note taken on [2014-10-20 Mon 10:33] \\
151-300
- Note taken on
Why don't you set your habit as a read 25 pages and use a piece of
paper or some card as a bookmark to remember where you finished? E-book
readers provide the functionality of remembering where you stopped last
time as I know. The title of the book is written on the book itself and
e-book readers
Daya Atapattu atapat...@gmail.com writes:
Is there a way to create a habit that picks-up the description from a
list?
I like to schedule studying a book: It would be scheduled as Read
pages 100-125. Then the next day it should read Read pages 126-150.
The description of the habit varies;
Pete Ley peteley11...@gmail.com writes:
As Bastien said, this doesn't really fit the idea of a habit, but I
think there is a reasonable non-elisp way of tweaking it to fit. Maybe
it would help.
What if you had something like this:
* Read book
:LOGBOOK:
- Note taken on [2014-10-20 Mon
19 matches
Mail list logo
