[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org f

From: Nicolas Goaziou
Subject: Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)
Date: Thu, 21 Jan 2016 10:47:02 +0100


Derek Feichtinger <address@hidden> writes:

> The thing which made it hard for me to identify the initial problem was
> that the test CLOCK lines I had in the testing file where placed there
> without a heading. When later in the day I wanted to clock in to my tasks,
>  I then just ended up with a "outline-back-to-heading: before first
> heading" error, but with no indicator which of my ~60 open org files was
> the culprit. Maybe one could insert the file location in that error
> message?

Actually, that is the very point of `org-back-to-heading' but... it
wasn't used. I fixed it. Thank you.

> Since org is so extremely useful, and I almost spend 80% of my day in org
> files (also some of my collaborators are beginning to use it... it is
> viral), I often have >50 files with all kinds of purposes open: agenda,
> various notes, beamer, html-exports, wiki-authoring, project-organization,
> bookkeeping... the thing is just too useful. So, I think clashes between
> the many uses of org files probably are natural.
> This being emacs  :-) I just decided to advise org-resolve-clocks.

Exactly. Thanks to Emacs, you can bend any part of Org to your needs.


Nicolas Goaziou

reply via email to

[Prev in Thread] Current Thread [Next in Thread]