From mboxrd@z Thu Jan 1 00:00:00 1970 From: "sgeorgii ." Subject: Re: [RFC] [PATCH] Changes to Tag groups - allow nesting and regexps Date: Wed, 25 Nov 2015 14:05:01 +0300 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54770) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1Xsq-0005Mj-AF for emacs-orgmode@gnu.org; Wed, 25 Nov 2015 06:05:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1Xsk-0003pm-Ey for emacs-orgmode@gnu.org; Wed, 25 Nov 2015 06:05:08 -0500 Received: from mail-wm0-x22f.google.com ([2a00:1450:400c:c09::22f]:37625) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1Xsk-0003pa-9t for emacs-orgmode@gnu.org; Wed, 25 Nov 2015 06:05:02 -0500 Received: by wmww144 with SMTP id w144so64266905wmw.0 for ; Wed, 25 Nov 2015 03:05:01 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?UTF-8?Q?Gustav_Wikstr=C3=B6m?= Cc: "emacs-orgmode@gnu.org" , "mail@nicolasgoaziou.fr" Indeed, the {.*} works. Thank you! If we could still use the empty parameter when filtering by "no tags" it would be really sweet :) On 25 November 2015 at 13:26, Gustav Wikstr=C3=B6m wrote: > Hi! > > Indeed, I do get the same error as you. I'll look into it a bit. Not sure= if the behavior is documented though. > > As a workaround for you sgeorgii (and for everyone else with this problem= I suppose :-) ), you can exclude tags instead of filtering. The behavior i= s similar except instead of only showing the rows with the provided tag, it= excludes all rows with the provided tag. If you provide a regular expressi= on, eg. {.*}, then all rows with tags are hidden from the agenda-view. > > So, to recreate with commands, what I just tried to describe with words: > M-x org-agenda > \ (exclude) (alternatively use the combination of / (filter) - (exclude) = ) > (exclude by tag) > {.*} > > > Voila! > > Best regards > Gustav > >> -----Original Message----- >> From: sgeorgii . [mailto:sgeorgii@gmail.com] >> Sent: Wednesday, November 25, 2015 08:51 >> To: gustav.erik@gmail.com; mail@nicolasgoaziou.fr; emacs- >> orgmode@gnu.org >> Subject: [O] [RFC] [PATCH] Changes to Tag groups - allow nesting and reg= exps >> >> Dear Gustav, Eric, >> >> >> I was referred to your subject discussion in respect to my problem: >> >> With new version of org-mode I am now unable to filter agenda to show on= ly >> non-tagged items: >> >> >> > "sgeorgii ." writes: >> > >> >> Hello! >> >> >> >> Having installed latest org 8.3.2 I am now having the subject problem= : >> >> >> >> M-x org-agenda >> >> >> >> When in agenda: >> >> >> >> / (filter) >> >> >> >> TAB (filter by tag) >> >> >> >> (without entering any tags for "Tag:" question) >> >> >> >> Before this gave me agenda view filtered to show only non-tagged item= s. >> >> I believe this was right and just fine. >> >> >> >> Now I have error: >> >> >> >> Debugger entered--Lisp error: (args-out-of-range "" 0 1) >> >> org-agenda-filter-make-matcher-tag-exp(("+") 43) >> >> org-agenda-filter-make-matcher(("+") tag t) >> >> org-agenda-filter-apply(("+") tag t) >> >> org-agenda-filter-by-tag(nil) >> >> call-interactively(org-agenda-filter-by-tag nil nil) >> >> command-execute(org-agenda-filter-by-tag) >> >> > >> > I believe 6c6ae99 (org-agenda: Filtering in the agenda on grouptags, >> > 2015-01-24) changed this behavior. The discussion about these changes >> > is here (sorry, the gmane web interface is down for me): >> > https://lists.gnu.org/archive/html/emacs-orgmode/2015-01/msg00618.html >> > >> > org-agenda-filter-by-tag should be fixed to handle the empty tag case >> > that causes the error above, either by behaving as before or by giving >> > a clear error. I haven't looked closely enough at the changes or the >> > discussion to guess whether that commit intended to preserve the empty >> > tag behavior you were relying on. Is that behavior documented anywher= e? >> > >> > -- >> > Kyle >> >> >> Any help?