From mboxrd@z Thu Jan  1 00:00:00 1970
From: Derek Feichtinger <dfeich@gmail.com>
Subject: 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: Tue, 19 Jan 2016 21:22:48 +0100
Message-ID: <CALGTQTaDP4R5PW=2rtQj4OdaCb=fThO0+Xirq7x0N+cLDpUkgA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary=089e013a0c1e1126890529b5a2b1
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33461)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dfeich@gmail.com>) id 1aLcni-0007H7-9R
	for emacs-orgmode@gnu.org; Tue, 19 Jan 2016 15:22:51 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dfeich@gmail.com>) id 1aLcnh-0001ce-GT
	for emacs-orgmode@gnu.org; Tue, 19 Jan 2016 15:22:50 -0500
Received: from mail-ig0-x22d.google.com ([2607:f8b0:4001:c05::22d]:34124)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dfeich@gmail.com>) id 1aLcnh-0001cY-BZ
	for emacs-orgmode@gnu.org; Tue, 19 Jan 2016 15:22:49 -0500
Received: by mail-ig0-x22d.google.com with SMTP id ik10so85599269igb.1
	for <emacs-orgmode@gnu.org>; Tue, 19 Jan 2016 12:22:48 -0800 (PST)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

--089e013a0c1e1126890529b5a2b1
Content-Type: text/plain; charset=UTF-8

Hi

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.

Best regards,
Derek

--089e013a0c1e1126890529b5a2b1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><div><br></div><div>org-resolve-clock loops o=
ver all open org buffers for detecting open</div><div>clocks (using functio=
n org-files-list). Is this really intended? I think</div><div>it should jus=
t loop over the org-agenda-files.</div><div><br></div><div>I was working on=
 an extension for clocking and was recording my testing results</div><div>i=
nto a separate org file. I also had put there examples of</div><div>various=
 clock lines to test regexps against. The example clock lines</div><div>eff=
ectively prevented me from clocking in to a task from my normal</div><div>a=
genda files.</div><div><br></div><div>Since org has so many usages, I think=
 it should not be assumed that each</div><div>org buffer is related to the =
agenda functionality.</div><div><br></div><div>Best regards,</div><div>Dere=
k=C2=A0</div><div><br></div></div>

--089e013a0c1e1126890529b5a2b1--