From: Ken Mankoff <mankoff@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Tangling based on file level #+PROPERTY
Date: Sat, 7 Oct 2017 18:05:30 +0200 [thread overview]
Message-ID: <CAFdBzEr1jicuNpi=3F_jqAytqV10LUELY+F+qA3vUBcVT=kGGw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY2qzQKHzq914vgmTzfLQzu4V2i9F2H+zYzoJWeW84Cs_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
Strange, and nevermind. Restarting emacs fixed it. It must have been
something to do with stale files and the upgrade.
-k.
On Sat, Oct 7, 2017 at 3:44 PM, Kaushal Modi <kaushal.modi@gmail.com> wrote:
> On Sat, Oct 7, 2017, 7:10 AM Ken Mankoff <mankoff@gmail.com> wrote:
>
>> Hi Org List,
>>
>> I just upgraded to 9.1.2.
>>
>
> What version did you upgrade from?
>
> I have a file with this at the top:
>>
>> #+PROPERTY: header-args :tangle filename
>>
>> And a lot of SRC blocks with this header:
>>
>> #+BEGIN_SRC emacs-lisp
>> #+END_SRC
>>
>> In the past, when I tangled the file, I got ~100 blocks exported. Now I
>> get 5, because only 5 have explicit ":tangle" arguments in the header.
>>
>> I just checked the NEWS file and did not see mention of this change. Has
>> something changed with the header-arg properties? Babel?
>>
>
> It impossible to tell what's wrong with just that information. Can you
> share a minimum working example that demonstrates this? (something that
> should probably tangle 3 files but is instead tangling just 1?)
>
> My best guess is you have this style of incompatible properties?
>
> *** Old Babel header properties are no longer supported
>
> Using header arguments as property names is no longer possible. As
> such, the following
>
> #+BEGIN_EXAMPLE
> ,* Headline
> :PROPERTIES:
> :exports: code
> :var: a=1 b=2
> :var+: c=3
> :END:
> #+END_EXAMPLE
>
> should be written instead
>
> #+BEGIN_EXAMPLE
> ,* Headline
> :PROPERTIES:
> :header-args: :exports code
> :header-args+: :var a=1 b=2
> :header-args+: :var c=3
> :END:
> #+END_EXAMPLE
>
> Please note that, however, old properties were defined at the source
> block definition. Current ones are defined where the block is called.
>
> --
>
> Kaushal Modi
>
[-- Attachment #2: Type: text/html, Size: 3230 bytes --]
prev parent reply other threads:[~2017-10-07 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 11:08 Tangling based on file level #+PROPERTY Ken Mankoff
2017-10-07 13:44 ` Kaushal Modi
2017-10-07 16:05 ` Ken Mankoff [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='CAFdBzEr1jicuNpi=3F_jqAytqV10LUELY+F+qA3vUBcVT=kGGw@mail.gmail.com' \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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).