emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Eros Zaupa <eroszaupa@gmail.com>
Cc: 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: Thu, 28 Apr 2022 22:40:44 +0800	[thread overview]
Message-ID: <87wnf96zkj.fsf@localhost> (raw)
In-Reply-To: <CAFEsDey-Lqtbsq6fdcaKgy1LHfg4_jsMKudn2s67wJ+wmVKang@mail.gmail.com>

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.

Though I am not 100% sure.

Org is indeed ignoring top-level property drawer when parsing

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?

Dear Eros Zaupa,

> ***main.org***
>     #+SETUPFILE: test.org
>     #+begin_src sh
>     echo ${A}
>     #+end_src
>     #+RESULTS:
> ***test.org***
>     :header-args:sh: :var A="this is a"
>     :END:

To work around your issue, you can use keyword property syntax:


#+PROPERTY: header-args:sh :var A="this is a"


  reply	other threads:[~2022-04-28 14:41 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 [this message]
2022-04-29 15:51   ` Cook, Malcolm
2022-05-02 18:59   ` Nick Dokos

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:

  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=87wnf96zkj.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eroszaupa@gmail.com \


* 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


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).