emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Simon Thum <simon.thum@gmx.de>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: new (iCalendar) exporter problem
Date: Thu, 09 May 2013 16:33:44 +0200	[thread overview]
Message-ID: <518BB3C8.2050900@gmx.de> (raw)
In-Reply-To: <877gjb83j2.fsf@bzg.ath.cx>

On 05/07/2013 12:22 PM, Bastien wrote:
> Hi Simon,
>
> Simon Thum <simon.thum@gmx.de> writes:
>
>> You mean inherited tags (coming from filetags in this case) do not
>> contribute to exclude tag filtering?
>
> More precisely, filetag-inherited tags do not contribute to excluding
> subtrees during export.
>
>> If yes, why? I seems inconsistent.
>
> Inherited-exclude-tags contribute to excluding subtrees not because
> they are inherited, but because the whole exclude-tagged subtree is
> excluded.

I guessed that but there is a difference in modelled vs. observable 
behaviour.

>
> We may support filetags for excluding, but it seems simple enough to
> exclude the entire file instead IMHO.
>
Well, probably.

I eventually figured that

(let ((org-agenda-files (remove-if (lambda (a) (string-match "extern" 
a)) org-agenda-files)))
   (org-agenda-files)
   )

is going to get me roughly where I want, but since I rely a lot on tags 
it's not going to scale nicely.

So in case it comes up elsewhere please consider this.

Thank you,

Simon

     prev parent reply	other threads:[~2013-05-09 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 20:02 new (iCalendar) exporter problem Simon Thum
2013-05-05 20:14 ` Nicolas Goaziou
2013-05-05 20:24   ` Simon Thum
2013-05-05 20:37     ` Nicolas Goaziou
2013-05-05 20:42       ` Simon Thum
2013-05-05 21:01         ` Nicolas Goaziou
2013-05-05 21:31           ` Simon Thum
2013-05-06 18:06           ` Simon Thum
2013-05-07 10:22             ` Bastien
2013-05-09 14:33               ` Simon Thum [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=518BB3C8.2050900@gmx.de \
    --to=simon.thum@gmx.de \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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

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).