From: Carsten Dominik <carsten.dominik@gmail.com>
To: Martin Pohlack <mp26@os.inf.tu-dresden.de>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode@gnu.org
Subject: Re: Re: skip entry with inherited tags
Date: Tue, 13 Jul 2010 20:48:54 +0200 [thread overview]
Message-ID: <3BFF4D35-CD16-4A41-B0A4-383538586592@gmail.com> (raw)
In-Reply-To: <4C3CA546.3060000@os.inf.tu-dresden.de>
On Jul 13, 2010, at 7:41 PM, Martin Pohlack wrote:
> Hi Carsten,
>
> On 13.07.2010 13:49, Carsten Dominik wrote:
>> Sorry for taking so much time for this.
>> I am still holding the patch because I have an almost unconscious
>> itch
>> that something is wrong with it. I cannot say what exactly it is
>> (if anything). The logic of what needs to be done when in
>> block agendas has some reason. One of the things I can say already
>> it that with such a local filter, I am afraid that updating the
>> agenda, or modifying the filter might fail or lead to strange
>> results.
>> This is actually something you might want to work on testing.
>
> 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?
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 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?
- Carsten
next prev parent reply other threads:[~2010-07-13 18:49 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 [this message]
2010-07-13 20:34 ` Martin Pohlack
2010-07-21 14:32 ` Carsten Dominik
2010-07-22 7:38 ` Carsten Dominik
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=3BFF4D35-CD16-4A41-B0A4-383538586592@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).