From: Bernt Hansen <firstname.lastname@example.org> To: Litvinov Sergey <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH] narrowing in agenda file Date: Wed, 01 Feb 2012 21:15:17 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Litvinov Sergey's message of "Wed, 01 Feb 2012 16:18:55 +0100") Litvinov Sergey <email@example.com> writes: > Bernt Hansen <firstname.lastname@example.org> 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 >> task >> - Visiting a task with RET or SPC goes to the task when outside the >> narrowed region >> - Remote editing of a task outside the narrowed region changes the >> target task and not something in your narrowed region instead > >> I tried this patch today and clock reports in the agenda no longer >> display for me. Could you take a look at it please? > > Hi Bernt, > > thank you for the recommendations and for testing the patch. I am working > on ERT tests for the items you listed above. Also I found that > =org-agenda-add-note= does not work with narrowed agenda file. > > Meanwhile I can share another patch to fix the problem with clock > reports (please see the second code block in > testing/examples/org-agenda-test.org ) Hi, I can't get this patch to apply. Can you resend something I can apply to origin/master so I can help with the testing? Thanks, Bernt
next prev parent reply other threads:[~2012-02-02 2:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-23 14:41 Litvinov Sergey 2012-01-23 18:04 ` Bernt Hansen 2012-02-01 14:11 ` Bernt Hansen 2012-02-01 15:18 ` Litvinov Sergey 2012-02-02 2:15 ` Bernt Hansen [this message] 2012-02-02 7:33 ` Litvinov Sergey 2012-02-12 21:27 ` Bernt Hansen
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] narrowing in agenda file' \ /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
Code repositories for project(s) associated with this 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).