emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Properties Drawer versus tags
Date: Fri, 20 Dec 2019 10:35:18 -0600	[thread overview]
Message-ID: <CAFAhFSXhrR4dGX=OGLqBx8He69vizaShPb7Aq7Rxtqw7Q40KPw@mail.gmail.com> (raw)
In-Reply-To: <877e2ryqip.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

I might add that a properties/drawer is a sort of "official heading
metadata repo," while tags not so much. It would be nice to see (lots of)
examples.

On Fri, Dec 20, 2019 at 9:18 AM Ken Mankoff <mankoff@gmail.com> wrote:

>
> On 2019-12-19 at 22:24 -08, Lawrence Bottorff <borgauf@gmail.com>
> wrote...
> > Very simple, largely philosophical question: When/why use a properties
> > drawer below a heading versus just using tags on the heading? What are
> > the advantages, disadvantages of both?
>
> Tags are binary. They are there or not.
>
> Property drawers allow you to assign values to variables.
>
> I've never fully understood why some property drawers are set to binary.
> For controlling LaTeX export I have both a property ":clearpage: t" and a
> tag ":ignore:", and the tag makes more sense to me. Some of those may only
> exist in my personal config.
>
>   -k.
>

[-- Attachment #2: Type: text/html, Size: 1299 bytes --]

  reply	other threads:[~2019-12-20 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  6:24 Properties Drawer versus tags Lawrence Bottorff
     [not found] ` <CACv55yT8Lg+Z=gR0hyUhQ-08bFqn9xMtLn6JP=EZQzQMf_SXqg@mail.gmail.com>
2019-12-20  6:46   ` David R
2019-12-20  6:47   ` Fwd: " David R
2019-12-20 11:54 ` Allen Li
2019-12-20 15:18 ` Ken Mankoff
2019-12-20 16:35   ` Lawrence Bottorff [this message]
2019-12-20 17:17 ` Adam Porter

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='CAFAhFSXhrR4dGX=OGLqBx8He69vizaShPb7Aq7Rxtqw7Q40KPw@mail.gmail.com' \
    --to=borgauf@gmail.com \
    --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).