emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Simon Thum <simon.thum@gmx.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: new (iCalendar) exporter problem
Date: Sun, 05 May 2013 23:31:54 +0200	[thread overview]
Message-ID: <5186CFCA.2080506@gmx.de> (raw)
In-Reply-To: <871u9lf8ek.fsf@gmail.com>

On 05/05/2013 11:01 PM, Nicolas Goaziou wrote:
> Simon Thum <simon.thum@gmx.de> writes:
>
>> I guess we have it then.
>>
>> Your example leads to icalendar without content.
>
> What is the value of `org-icalendar-with-timestamps'?

org-icalendar-with-timestamps: active

But see below.

>
> I don't see any difference between my "* Test 2" headline and your "*
> Test" below.

Yes, I copied only the first of your headlines. That lead to the 
confusing statement of mine. But the behaviour is consistent: a 
#filetags: tag cannot prevent export of the file's headlines. IMO this 
is a bug.

My use case is to prevent duplicates that come from me importing outside 
iCals into org (using ical2org). When exporting, I do not want these to 
be re-exported. I could remove the files from the agenda altogether, but 
tags offer a more logical path for me.

Cheers,

Simon


>
>> However I have:
>>
>> #+filetags: drawnin
>> #+icalendar_exclude_tags: drawnin noexport
>> #+bind: org-icalendar-categories (all-tags)
>>
>> * Test (no tag here ->
>>
>>     <2013-05-05 Sun>
>>
>>     Desc
>>
>>
>> That one indeed exports, but IMO shouldn't.
>
> exclude tags are not inherited.
>
>
> Regards,
>

  reply	other threads:[~2013-05-05 21:31 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 [this message]
2013-05-06 18:06           ` Simon Thum
2013-05-07 10:22             ` Bastien
2013-05-09 14:33               ` Simon Thum

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=5186CFCA.2080506@gmx.de \
    --to=simon.thum@gmx.de \
    --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
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).