From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Derek Feichtinger <dfeich@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: 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: Wed, 20 Jan 2016 14:14:46 +0100 [thread overview]
Message-ID: <87oacggzp5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CALGTQTaDP4R5PW=2rtQj4OdaCb=fThO0+Xirq7x0N+cLDpUkgA@mail.gmail.com> (Derek Feichtinger's message of "Tue, 19 Jan 2016 21:22:48 +0100")
Hello,
Derek Feichtinger <dfeich@gmail.com> writes:
> org-resolve-clock loops over all open org buffers for detecting open
> clocks (using function org-files-list). Is this really intended? I think
> it should just loop over the org-agenda-files.
>
> I was working on an extension for clocking and was recording my testing
> results
> into a separate org file. I also had put there examples of
> various clock lines to test regexps against. The example clock lines
> effectively prevented me from clocking in to a task from my normal
> agenda files.
>
> Since org has so many usages, I think it should not be assumed that each
> org buffer is related to the agenda functionality.
Clocking is not just an agenda functionality. Since every Org document
can contain clocks, it makes sense to use `org-files-list' instead of
`org-agenda-files'.
You could test your extension in a dedicated Emacs process, with
`org-agenda-files' being nil and Org documents opened piece-wise.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-01-20 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 20:22 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/) Derek Feichtinger
2016-01-20 13:14 ` Nicolas Goaziou [this message]
2016-01-21 9:26 ` Derek Feichtinger
2016-01-21 9:47 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oacggzp5.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=dfeich@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).