emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Highlighting bug with org-agenda-set-restriction-lock
Date: Fri, 05 Apr 2013 10:46:40 -0400	[thread overview]
Message-ID: <8738v5yqzz.fsf@norang.ca> (raw)
In-Reply-To: <890D099A-90BD-4AA5-AD86-E145AF8429A7@gmail.com> (Carsten Dominik's message of "Fri, 5 Apr 2013 16:23:23 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> I now also see that the patch did not achieve what the purpose of it
> was.  The problem is not the end of the overlay, but the position of
> the org-agenda-restriction-end marker.  Indeed, if you add tasks after
> this marker, they will not be included in the search.  There is not
> good work-around for this I can think of, so it is a problem we will
> have to live with.
>
> - Carsten

I would prefer the original highlighting behaviour as well.
I normally narrow the buffer to the subtree as well when working on it
-- and the entire narrowed buffer is bright gaudy yellow currently :).

My workaround for the adding items to the ends is to remark the subtree
restriction.  I have added speed keys P, F, W, and N in my setup for
narrow to project, narrow to file, widen, and narrow to subtree
respectively.

I normally narrow to project with P (on any task in the project narrows
the current buffer to the project.  In the agenda P sets the restriction
lock on the project -- so if I've added anything new at the end of the
project I can just hit P on any task in the agenda and the restriction
lock is reset appropriately including all of the (new) tasks in the
project.  (My definition of a project is any todo keyword task that has
at least one subtask with a todo keyword.)

Regards,
Bernt

  parent reply	other threads:[~2013-04-05 14:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 13:12 Highlighting bug with org-agenda-set-restriction-lock Bernt Hansen
2013-04-05 13:20 ` Bernt Hansen
2013-04-05 14:12 ` Carsten Dominik
2013-04-05 14:23   ` Carsten Dominik
2013-04-05 14:46     ` Carsten Dominik
2013-04-05 15:48       ` Bernt Hansen
2013-04-06  5:17         ` Carsten Dominik
2013-04-05 14:46     ` Bernt Hansen [this message]
2013-04-05 14:50       ` Carsten Dominik
2013-04-06 20:33       ` Bastien
2013-04-06 21:16         ` Bernt Hansen
2013-04-06 21:25           ` Bastien
2013-04-07  0:29             ` Bernt Hansen
2013-04-07  7:33               ` Bastien
2013-04-07 12:08                 ` Bernt Hansen
2013-04-07 14:05                 ` Christian Moe
2013-04-07 18:43                   ` Bernt Hansen
2013-04-10 22:36                     ` Bastien

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=8738v5yqzz.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=carsten.dominik@gmail.com \
    --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).