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 09:11:59 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Bernt Hansen's message of "Mon, 23 Jan 2012 13:04:20 -0500") Bernt Hansen <email@example.com> writes: > Litvinov Sergey <firstname.lastname@example.org> 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 well but there are other issues that crop up when you > keep the narrowed region. > > Please make sure that at least the following work as expected with your > patch: > > - 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'm hoping your patch works since I also want this desired behaviour but > so far my attempts to achieve this failed miserably :( > > Regards, > Bernt Hi Litvinov, I tried this patch today and clock reports in the agenda no longer display for me. Could you take a look at it please? Thanks, Bernt
next prev parent reply other threads:[~2012-02-01 14:12 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 [this message] 2012-02-01 15:18 ` Litvinov Sergey 2012-02-02 2:15 ` Bernt Hansen 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).