[O] Add "legacy" time tracking as CLOCK entries
Hi, while I've been using org-mode for some time, I'm now working on a project where I've decided to use the time-tracking functions. But I've got some "legacy" time on the project that I would like to incorporate. I.e., I have in my (paper) log book a record of (say) half an hour spent on a certain day, but I don't have a record of the start and end time and I don't want to invent them. I note that I can add an entry that looks like this: CLOCK: => 0:30 and have this contribute to totals. But I would also like to record the date for this entry. Checking the regular expression in org-clock-sum and a bit of trial and error showed that this _doesn't_ work: CLOCK: [2013-12-11 Wed] => 0:30 and nor does: CLOCK: [2013-12-11 Wed]--[2013-12-11 Wed] => 0:30 But this does seem to work: CLOCK: => 0:30 [2013-12-11 Wed] I've figured this out myself on the basis of not finding anything about it in the manual. Nevertheless, is there a "standard" way of doing this that I missed?
Re: [O] Add "legacy" time tracking as CLOCK entries
On 15/01/2014, Sebastien Vauban wrote: > Richard Walker wrote: >> I note that I can add an entry that looks like this: >> >> CLOCK: => 0:30 >> >> and have this contribute to totals. But I would >> also like to record the date for this entry. ... > > Can't you try to convert your lines to: > > CLOCK: [2013-12-11 Wed 0:00]--[2013-12-11 Wed 0:30] => 0:30 > > duration That's just the sort of thing I wanted to avoid. But now I've found that "my" way doesn't show the durations in the Agenda views; yours does. So I have switched all the entries to your way. On some days, I have several of these entries for different tasks, so I get "Clocking overlap" errors in the Day-Agenda view when I use the clockcheck function. OK, the solution to that is to ignore those errors ...
Re: org-datetree-insert-line and org-blank-before-new-entry
On Wed, 26 Oct 2022 at 18:28, Ihor Radchenko wrote: > Richard Walker writes: > ... > > Change (assq 'heading org-blank-before-new-entry) > > to (org--blank-before-heading-p) here? > > You are indeed right. > Fixed on main now. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6bbd08f5aa81bd0b6b2b2f448a858516f388702a Thank you so much. (I did wonder if anyone had seen my report.)
org-datetree-insert-line and org-blank-before-new-entry
A follow-up to the changes made to org-datetree-insert-line in September 2020. The definition now begins: (defun org-datetree-insert-line (year &optional month day text) (delete-region (save-excursion (skip-chars-backward " \t\n") (point)) (point)) (when (assq 'heading org-blank-before-new-entry) (insert "\n")) ... I'm getting blank lines inserted before new entries, and I found a couple of sources of advice for setting org-blank-before-new-entry ( https://emacs.stackexchange.com/questions/51117/org-mode-control-whether-m-ret-inserts-a-newline-or-not-for-plain-lists and https://stackoverflow.com/questions/28351465/emacs-orgmode-do-not-insert-line-between-headers ) that say to do this: (setf org-blank-before-new-entry '((heading . nil) (plain-list-item . nil))) Such a setting seems to be consistent with the help text of org-blank-before-new-entry, and what org--blank-before-heading-p expects to find. But, having made this setting, (when (assq 'heading org-blank-before-new-entry) (insert "\n")) still does the insertion, since (assq 'heading org-blank-before-new-entry) is non-nil. Change (assq 'heading org-blank-before-new-entry) to (org--blank-before-heading-p) here?
