emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Honour existing restrictions if possible when visiting tasks from the agenda
Date: Sat, 31 Dec 2011 09:11:12 +0100	[thread overview]
Message-ID: <C9520BD2-553A-4949-9775-46FBCAF8E108@gmail.com> (raw)
In-Reply-To: <1325242149-22487-1-git-send-email-bernt@norang.ca>

Applied, thanks.

- Carsten

On 30.12.2011, at 11:49, Bernt Hansen wrote:

> The following short patch series fixes org file restriction
> handling for me.  I'm regularly narrowing to subtrees for a
> project from the agenda and then using the agenda to visit tasks
> in the subtree.  Each time I visit a task, clock in, or
> regenerate the agenda my restriction is removed in the org file.
> The following patch series fixes this behaviour.
> 

  parent reply	other threads:[~2011-12-31  8:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30 10:49 Honour existing restrictions if possible when visiting tasks from the agenda Bernt Hansen
2011-12-30 10:49 ` [PATCH 1/3] Honour existing restrictions when regenerating " Bernt Hansen
2011-12-30 10:49 ` [PATCH 2/3] Honour existing restrictions when clocking in from " Bernt Hansen
2012-01-19 13:43   ` Matt Lundin
2012-01-19 14:51     ` Bernt Hansen
2012-01-19 15:22       ` Bastien
2012-01-19 15:44       ` Bernt Hansen
2012-01-19 15:47       ` Sebastien Vauban
2012-01-19 16:11         ` Bastien
2012-01-19 18:05         ` Bernt Hansen
2011-12-30 10:49 ` [PATCH 3/3] Honour existing restrictions when visiting tasks " Bernt Hansen
2011-12-31  8:11 ` Carsten Dominik [this message]
2011-12-31 14:12   ` Honour existing restrictions if possible " 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 \
    --in-reply-to=C9520BD2-553A-4949-9775-46FBCAF8E108@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    /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).