emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Benoit Bidoggia <benoit.bidoggia@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem with org-agenda-clockreport-mode and tag-filtered view in agenda
Date: Wed, 26 Nov 2014 20:10:51 +0100	[thread overview]
Message-ID: <CAGsLRvZYFbHEw2JHr56hGrRcfb=FD9v2fV05idgJaw514ka9Qw@mail.gmail.com> (raw)
In-Reply-To: <86mw7egxhz.fsf@example.com>

[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]

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ît


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
> 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
>
>
>

[-- Attachment #2: Type: text/html, Size: 2409 bytes --]

  reply	other threads:[~2014-11-26 19:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 11:12 Problem with org-agenda-clockreport-mode and tag-filtered view in agenda Benoit Bidoggia
2014-11-25 20:41 ` Benoit Bidoggia
2014-11-26  8:46   ` Sebastien Vauban
2014-11-26 19:10     ` Benoit Bidoggia [this message]
2014-11-26 19:17       ` Sebastien Vauban
2015-05-04 13:27         ` Josh Berdine

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='CAGsLRvZYFbHEw2JHr56hGrRcfb=FD9v2fV05idgJaw514ka9Qw@mail.gmail.com' \
    --to=benoit.bidoggia@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.com \
    /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).