From: Rasmus <rasmus@gmx.us>
To: mankoff@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Tags v. PROPERTIES for noexport and ignoreheadings
Date: Wed, 06 Jan 2016 00:51:25 +0100 [thread overview]
Message-ID: <87r3hvlh4y.fsf@gmx.us> (raw)
In-Reply-To: <m2y4c3k36f.fsf@gmail.com> (Ken Mankoff's message of "Tue, 05 Jan 2016 18:38:16 -0500")
Ken Mankoff <mankoff@gmail.com> writes:
> On 2016-01-05 at 18:29, Rasmus <rasmus@gmx.us> wrote:
>> Ken Mankoff <mankoff@gmail.com> writes:
>>> I'm trying to figure out when I should be using tags and when I
>
>>> should be using properties, for the cases of "noexport" and
>>> "ignoringheading".
>>
>> If you are working on a patch to be submitted to org, you should use a
>> property unless you have good reasons not to (IMO). If you are working
>> on a hack do whatever you want...
>
> I'm asking as an end-user writing a document. I'd rather use an
> official solution than a hack. I've been using the hacked tag solution
> but thought that there was a recent official change.
There’s no consensus. As you mentioned there's noexport tags.
ox-koma-letter relies heavily on tags as well. UNNUMBERED is a
property...
There’s no official way to use ignoreheadings. The closes thing is the
ox-extra in contrib where Aaron curates a couple of hacks (the
ignoreheadings one by was first posted by Eric Schulte, I think when he
wrote about his thesis in Org). That filter also uses a tag ("ignore"),
but it would be trivial to change to a property, if you prefer.
Eventually, it would be nice to add a ignoreheading property and a
"insert-just-before-heading" property (e.g. for @@latex:\clearpage@@) in
ox. We are not there yet.
Rasmus
--
Vote for proprietary math!
prev parent reply other threads:[~2016-01-05 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 23:17 Tags v. PROPERTIES for noexport and ignoreheadings Ken Mankoff
2016-01-05 23:29 ` Rasmus
2016-01-05 23:38 ` Ken Mankoff
2016-01-05 23:51 ` Rasmus [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=87r3hvlh4y.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@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).