Re: [O] [PATCH] narrowing in agenda file

2012-02-12 Thread Bernt Hansen
Hi Sergey, I've applied this patch but I still can't generate agenda log reports using 'R' in the agenda with this patch applied. The clock reports seem to be generated and inserted directly in my org files (corrupting data a bit) instead of being inserted in my agenda. I've dropped this patch

Re: [O] [PATCH] narrowing in agenda file

2012-02-01 Thread Bernt Hansen
Bernt Hansen be...@norang.ca writes: Litvinov Sergey slitvi...@gmail.com writes: Narrowing in the agenda file does not survive agenda redo. Please see an example in the first patch. I think the second patch fixes this problem. Hi Sergey, I haven't had a chance to try your patch yet but I

Re: [O] [PATCH] narrowing in agenda file

2012-02-01 Thread Litvinov Sergey
Bernt Hansen be...@norang.ca writes: - org agenda clock reports are correct - You don't have the LOGBOOK drawer aligned with tags when clocking in from the agenda (this was with emacs -q (no org-indent-mode) - Column view in the agenda shows correct clocking amounts for each

Re: [O] [PATCH] narrowing in agenda file

2012-02-01 Thread Bernt Hansen
Litvinov Sergey slitvi...@gmail.com writes: Bernt Hansen be...@norang.ca writes: - org agenda clock reports are correct - You don't have the LOGBOOK drawer aligned with tags when clocking in from the agenda (this was with emacs -q (no org-indent-mode) - Column view in the agenda

Re: [O] [PATCH] narrowing in agenda file

2012-02-01 Thread Litvinov Sergey
This must be a cumulative patch against master. From f95e9e89b47b35d5198ecaff7ee20ffb3e63b066 Mon Sep 17 00:00:00 2001 From: Litvinov Sergey slitvi...@gmail.com Date: Thu, 2 Feb 2012 08:15:56 +0100 Subject: [PATCH] Make narrowing of the agenda file survive (org-agenda-redo) * lisp/org.el

Re: [O] [PATCH] narrowing in agenda file

2012-01-23 Thread Bernt Hansen
Litvinov Sergey slitvi...@gmail.com writes: Narrowing in the agenda file does not survive agenda redo. Please see an example in the first patch. I think the second patch fixes this problem. Hi Sergey, I haven't had a chance to try your patch yet but I recently tried to fix this behaviour as