From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Agenda Tag filtering - has the behaviour changed?
Date: Tue, 22 Sep 2015 11:00:04 +0200 [thread overview]
Message-ID: <20150922090004.GE6415@chitra.no-ip.org> (raw)
In-Reply-To: <87pp1hdns0.fsf@norang.ca>
On Thu, Sep 17, 2015 at 12:16:44PM -0400, Bernt Hansen wrote:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
> > Hello,
> >
> > Robert Klein <roklein@roklein.de> writes:
> >
> >> Looking through the commit messages this may come from commit
> >> 6c6ae990c10dbe7f96b24fccf840fe9f6d81a3b8
> >
> > Indeed. It seems related to this NEWS entry
> >
> > *** Minor refactoring of ~org-agenda-filter-by-tag~
> > Now uses the argument arg and optional argument exclude instead of
> > strip and narrow. ARG because the argument has multiple purposes and
> > makes more sense than strip now. The term narrowing is changed to
> > exclude.
> >
> > The main purpose is for the function to make more logical sense when
> > filtering on tags now when tags can be structured in hierarchies.
>
> Thanks both.
>
> So was this an intended usability change? I can probably live with it -
> I just need to retrain my fingers -- but it does take longer to achieve
> the result I want now since I have to clear the agenda tags before
> selecting a new filter and wait for the agenda update each time (my
> agenda has lots of entries).
>
> The old behaviour was faster to use.
>
> I haven't done anything with hierarchical tags yet.
FWIW, I think hierarchical tags should be opt-in. The current behaviour
is a very nice feature, but probably a less common use case than the old
behaviour. Maybe there can be a toggle?
I tried looking at the source, but it looked non-trivial.
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2015-09-22 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:17 Agenda Tag filtering - has the behaviour changed? Bernt Hansen
2015-09-17 6:34 ` Robert Klein
2015-09-17 7:11 ` Nicolas Goaziou
2015-09-17 16:16 ` Bernt Hansen
2015-09-22 9:00 ` Suvayu Ali [this message]
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=20150922090004.GE6415@chitra.no-ip.org \
--to=fatkasuvayu+linux@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).