all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-mode #+SETUPFILE not working with properties [9.5.2 (release_9.5.2-378-g98588e @ /home/eros/src/org-mode/lisp/)]
Date: Mon, 02 May 2022 14:59:26 -0400	[thread overview]
Message-ID: <87zgjzbw1d.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87wnf96zkj.fsf@localhost

Ihor Radchenko <yantar92@gmail.com> writes:

> Eros Zaupa <eroszaupa@gmail.com> writes:
>
>> I would like to move the properties drawer to a separate file and import it
>> into the main one. To do so I'm using the `#SETUPFILE` property suggested
>> [here][1], but this doesn't seem to work.
>
> Confirmed.
> Though I am not 100% sure.
>
> Org is indeed ignoring top-level property drawer when parsing
> #+SETUPFILE.
>
> Dear All,
> I think that parsing top-level property drawer is simply an omission
> from the time we introduced top-level property drawers into syntax.
>
> We may either implement this support or leave things as is and document
> the current behaviour.
>
> I would be in favour of implementing top-level drawer support in
> SETUPFILE, but there might be alternative opinions. WDYT?

FWIW, I agree that it is a bug and it should be fixed.

-- 
Nick

"There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler



      parent reply	other threads:[~2022-05-02 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 15:19 [BUG] org-mode #+SETUPFILE not working with properties [9.5.2 (release_9.5.2-378-g98588e @ /home/eros/src/org-mode/lisp/)] Eros Zaupa
2022-04-28 14:40 ` Ihor Radchenko
2022-04-29 15:51   ` Cook, Malcolm
2022-05-02 18:59   ` Nick Dokos [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgjzbw1d.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.