From: Kyle Meyer <kyle@kyleam.com>
To: Bastien <bzg@gnu.org>
Cc: George Sokolsky <sokolgeo@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: Org-agenda ignores archive tag set by "#+FILETAGS: ARCHIVE"
Date: Sun, 24 May 2020 17:06:11 +0000 [thread overview]
Message-ID: <87v9kls1oc.fsf@kyleam.com> (raw)
In-Reply-To: <87h7w5wqfe.fsf@gnu.org>
Bastien writes:
> George Sokolsky <sokolgeo@posteo.net> writes:
>
>> I have .org files with "#+FILETAGS: ARCHIVE" headers.
>
> Shouldn't it be "#+FILETAGS: :ARCHIVE:" instead?
>
> (Note the columns.)
Despite being the documented form, org-set-regexps-and-options will
handle entries "tag1 [tag2 ...]" as well:
(cl-mapcan (lambda (value)
(cl-mapcan
(lambda (k) (org-split-string k ":"))
(split-string value)))
(cdr (assoc "FILETAGS" alist)))
>> I want items from these .org files to be hidden by default from results
>> of "org-agenda" -> "s Search for keywords" by default.
>>
>> This is not the case, unfortunately.
>
> Can you be so kind as to test with latest Org from maint or master?
Earlier this week I applied the patch from a sibling message of this
thread (5e2490bdf), so maint and master no longer behave as initially
reported (hopefully :>).
next prev parent reply other threads:[~2020-05-24 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 10:53 Org-agenda ignores archive tag set by "#+FILETAGS: ARCHIVE" George Sokolsky
2020-05-17 5:33 ` [PATCH] agenda: Consider FILETAGS for archive skipping Kyle Meyer
2020-05-17 8:54 ` Dauer, Michael
2020-05-18 9:34 ` George Sokolsky
2020-05-18 9:52 ` Bastien
2020-05-18 10:09 ` George Sokolsky
2020-05-18 11:48 ` Bastien
2020-05-18 12:17 ` George Sokolsky
2020-05-19 0:43 ` Kyle Meyer
2020-05-21 3:05 ` Kyle Meyer
2020-05-21 7:16 ` George Sokolsky
2020-05-24 10:57 ` Org-agenda ignores archive tag set by "#+FILETAGS: ARCHIVE" Bastien
2020-05-24 17:06 ` Kyle Meyer [this message]
2020-05-25 8:28 ` George Sokolsky
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=87v9kls1oc.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=sokolgeo@posteo.net \
/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).