emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>,
	Martin Pohlack <mp26@os.inf.tu-dresden.de>,
	emacs-orgmode@gnu.org
Subject: Re: Re: skip entry with inherited tags
Date: Thu, 22 Jul 2010 09:38:46 +0200	[thread overview]
Message-ID: <A5E331FE-CFF5-4CE0-B90B-C253D33E1C07@gmail.com> (raw)
In-Reply-To: <6694F386-1367-43D6-9587-7F26ECBC9C57@gmail.com>

Hi Martin,

On Jul 21, 2010, at 4:32 PM, Carsten Dominik wrote:

> Hi Martin,
>
> I just looked at your patch.
>
> If I have a normal agenda (i.e. *not* a block agenda), then your
> patch will cause the preset filter *not* to be applied.

OK, that was obviously incorrect, sorry about that.

However, it still does not work correctly, here is the counter example:

-----------------------------------------------------------------------------
* TODO test 1								  :a:
* TODO test 2								  :b:

* at 1									  :a:
   SCHEDULED: <2010-07-22 Thu>
* at 1									  :b:
   SCHEDULED: <2010-07-22 Thu>
------------------------------------------------------------------------------

With this custom command:

(setq org-agenda-custom-commands
       '(("x" "testmartin"
	 ((agenda "" ((org-agenda-filter-preset '("+a"))))
	  (alltodo "" ((org-agenda-filter-preset '("+b")))))
	 nil nil)))

the result is incorrect, both with and without your patch.

The internal logic of the filter and the preset filter is such that
it applies to the entire view, and you should not set in the local
options for a command that is part of a block agenda view.

I have now documented this limitation.

Sorry that this took so long - thank you for your patience.

Best wishes

- Carsten



>
> - Carsten
>
> On Jul 13, 2010, at 10:34 PM, Martin Pohlack wrote:
>
>> Hi Carsten and Matt,
>>
>> On 13.07.2010 20:48, Carsten Dominik wrote:
>>> On Jul 13, 2010, at 7:41 PM, Martin Pohlack wrote:
>>>> Hard to respond to this vague situation :-).
>>>>
>>>> It would be great if you could point me at more specific situations
>>>> that
>>>> might break or if others could test the patch.  I have been using  
>>>> it
>>>> for
>>>> more than a month now without problems.
>>>
>>> The specific one I meant is if you use r or g to rebuild the agenda,
>>> if you do something like a refile command which does an automatic
>>> rebuild,
>>> do you get back the view you expected?
>>
>> Yes, I regularly use 'r'.  It works for me.  Refiling a single  
>> entry did
>> not show a problem.
>>
>>> Also, if you apply other filter commands, either with "/", or  
>>> narrowing
>>> the filter with "/", does that give the expected results while you  
>>> are
>>> in your block agenda?
>>
>> I quickly applied a tag filter using '/' 'tab'.  Only the relevant
>> entries were shown.  Some block agendas become empty as expected.
>> Clearing the filter restores the expected full view.
>>
>> I am not entirely sure that the patch does not have problems though.
>>
>> Matt: could you give the patch a quick test at your end?
>>
>>>>> I will only be able to study this more closely after the release.
>>>>
>>>> Take your time, I will wait for more details to emerge or feedback
>>>> from
>>>> other testers.
>>>>
>>>> One more note here: The current situation for block agendas is a  
>>>> bit
>>>> problematic as their limitations are not documented afaik.
>>>>
>>>> Writing custom agendas is not easy in itself.  If things don't  
>>>> work,
>>>> it
>>>> is really hard to distinguish between driver errors and  
>>>> limitations of
>>>> the block agendas.
>>>
>>> Do you have suggestions on how to improve the situation?
>>
>> * Well, the best thing to do would be to remove the limitations of  
>> the
>> block agendas, obviously :-), which I hope this patch does.
>>
>> * The second best thing is to document them.
>>
>> I am aware of this tag filter limitation, but no others from the  
>> top of
>> my head.  Do others know more?
>>
>> Cheers,
>> Martin
>
> - Carsten
>
>
>

- Carsten

  reply	other threads:[~2010-07-22  7:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  7:42 skip entry with inherited tags Matthias Teege
2010-05-18 11:18 ` Martin Pohlack
2010-05-18 17:25   ` Matt Lundin
2010-06-03 21:44     ` Martin Pohlack
2010-06-04 11:27       ` Carsten Dominik
2010-06-04 12:11         ` Martin Pohlack
2010-07-07  8:49           ` Martin Pohlack
2010-07-13 11:49             ` Carsten Dominik
2010-07-13 17:41               ` Martin Pohlack
2010-07-13 18:48                 ` Carsten Dominik
2010-07-13 20:34                   ` Martin Pohlack
2010-07-21 14:32                     ` Carsten Dominik
2010-07-22  7:38                       ` Carsten Dominik [this message]
2010-08-04 21:38                         ` Martin Pohlack
2010-08-16 12:50                           ` Carsten Dominik
2010-08-16 12:56                             ` Martin Pohlack
2010-08-16 13:10                               ` Carsten Dominik

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=A5E331FE-CFF5-4CE0-B90B-C253D33E1C07@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    --cc=mp26@os.inf.tu-dresden.de \
    /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).