From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benoit Bidoggia Subject: Re: Problem with org-agenda-clockreport-mode and tag-filtered view in agenda Date: Wed, 26 Nov 2014 20:10:51 +0100 Message-ID: References: <86mw7egxhz.fsf@example.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c372b070378e0508c7ca46 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40399) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xthzh-0004KP-KW for emacs-orgmode@gnu.org; Wed, 26 Nov 2014 14:11:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xthzc-0007oi-Tz for emacs-orgmode@gnu.org; Wed, 26 Nov 2014 14:11:17 -0500 Received: from mail-la0-x22c.google.com ([2a00:1450:4010:c03::22c]:47889) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xthzc-0007oN-H1 for emacs-orgmode@gnu.org; Wed, 26 Nov 2014 14:11:12 -0500 Received: by mail-la0-f44.google.com with SMTP id ge10so3035488lab.3 for ; Wed, 26 Nov 2014 11:11:11 -0800 (PST) In-Reply-To: <86mw7egxhz.fsf@example.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Sebastien Vauban Cc: emacs-orgmode@gnu.org --001a11c372b070378e0508c7ca46 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear Seb, Thanks for the piece of advice. I'll do that asap. I first need though to configure for the git version (now I'm using the emacs package version). I'll post on the list again when I find the problematic commit. Thanks again, best regads. Beno=C3=AEt On Wed, Nov 26, 2014 at 9:46 AM, Sebastien Vauban wrote: > Dear Benoit, > > > PROBLEM: Agenda clock report mode does not take into consideration > filtered > > view anymore (C-u R in agenda view). > > > > It's behavior changed somewhere between version 8.2.4 (for which it > works) > > and version 8.2.10 (for which it doesn't work anymore). > > Is it a bug or is it intentional? > > > > I intensively use clock report with filtered views, so it has become > quite > > problematic for me. > > IMHO, the best way you can help to try and get the problem fixed is to > find the problematic commit. > > In order to do, use the Git version of org-mode, and play a couple of > minutes with `git bisect': > > #+begin_src sh > git bisect start BAD-COMMIT GOOD-COMMIT > #+end_src > > Test... > > If good: > > #+begin_src sh > git bisect good > #+end_src > > If bad: > > #+begin_src sh > git bisect bad > #+end_src > > And after a few more steps like that, "git bisect" will eventually find > a first bad commit: > > #+begin_src sh > git bisect bad > 2ddcca36c8bcfa251724fe342c8327451988be0d is the first bad commit > #+end_src > > Send it to the list (and put the author of the commit in Cc). > > Then use "git bisect reset" to go back to the branch we were in before > we started bisecting: > > #+begin_src sh > git bisect reset > #+end_src > > Best regards, > Seb > > -- > Sebastien Vauban > > > --001a11c372b070378e0508c7ca46 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear Seb,

Thanks for the piece of advic= e. I'll do that asap.
I first need though to configure for th= e git version (now I'm using the emacs package version).
I= 9;ll post on the list again when I find the problematic commit.
<= br>
Thanks again, best regads.
Beno=C3=AEt

On = Wed, Nov 26, 2014 at 9:46 AM, Sebastien Vauban <sva-news@mygooglest.= com> wrote:
Dear Benoit,
> PROBLEM: Agenda clock report mode does not take into consideration fil= tered
> view anymore (C-u R in agenda view).
>
> It's behavior changed somewhere between version 8.2.4 (for which i= t works)
> and version 8.2.10 (for which it doesn't work anymore).
> Is it a bug or is it intentional?
>
> I intensively use clock report with filtered views, so it has become q= uite
> problematic for me.

IMHO, the best way you can help to try and get the problem fixed is = to
find the problematic commit.

In order to do, use the Git version of org-mode, and play a couple of
minutes with `git bisect':

#+begin_src sh
git bisect start BAD-COMMIT GOOD-COMMIT
#+end_src

Test...

If good:

#+begin_src sh
git bisect good
#+end_src

If bad:

#+begin_src sh
git bisect bad
#+end_src

And after a few more steps like that, "git bisect" will eventuall= y find
a first bad commit:

#+begin_src sh
git bisect bad
2ddcca36c8bcfa251724fe342c8327451988be0d is the first bad commit
#+end_src

Send it to the list (and put the author of the commit in Cc).

Then use "git bisect reset" to go back to the branch we were in b= efore
we started bisecting:

#+begin_src sh
git bisect reset
#+end_src

Best regards,
=C2=A0 Seb

--
Sebastien Vauban



--001a11c372b070378e0508c7ca46--