emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: BUG: in beamer export non-beamer tags exported as part of header
Date: Tue, 24 May 2016 23:02:44 +0200	[thread overview]
Message-ID: <87bn3v88zv.fsf@gmx.us> (raw)
In-Reply-To: 87fut79ozi.fsf@saiph.selenimh

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> But in my document, I have
>>
>> #+SELECT_TAGS: export presentation
>>
>> in which case, I would have expected, that the tags defined here are not
>> exported?
>
> It's arguably better. 
>
> OTOH, it is easier to remove them with a filter (or globally with
> tags:nil) than to add them back if we automatically delete them. So,
> I tend to think we shouldn't remove them automatically.
>
> WDYT?

FWIW I agree with not being clever here.  It becomes a too convoluted
definition of tags.  Aside, I can’t think of single case where I would
*export* tags (but that’s another story).

-- 
When in doubt, do it!

  reply	other threads:[~2016-05-24 21:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 10:48 BUG: in beamer export non-beamer tags exported as part of header Rainer M Krug
2016-05-24 12:08 ` Rasmus
2016-05-24 12:27   ` Rainer M Krug
2016-05-24 20:32     ` Nicolas Goaziou
2016-05-24 21:02       ` Rasmus [this message]
2016-05-25  7:39         ` Rainer M Krug
2016-05-25  7:37       ` Rainer M Krug
2016-05-25 20:29         ` Nicolas Goaziou
2016-05-27  9:01           ` Rainer M Krug
2016-05-27 11:58             ` Nicolas Goaziou
2016-05-27 16:15               ` Rainer M Krug
2016-05-31 19:53                 ` Nicolas Goaziou
2016-06-01  8:06                   ` Rainer M Krug
2016-06-01 11:08                     ` Nicolas Goaziou
2016-06-01 12:21                       ` Rasmus
2016-06-01 13:23                         ` Rainer M Krug
2016-06-01 17:40                           ` Nicolas Goaziou
2016-05-31 20:07                 ` John Hendy
2016-06-01  8:12                   ` Rainer M Krug

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=87bn3v88zv.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).