[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Patch] ob-tangle.el: New value 'ascii' for the header argument ':co
From: |
Ihor Radchenko |
Subject: |
Re: [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments' |
Date: |
Tue, 14 Jun 2022 19:55:56 +0800 |
Juan Manuel Macías <maciaschain@posteo.net> writes:
> On the other hand, I have a curiosity. I understand that the behavior of
> the `:comments org' option should be left intact to ensure backwards
> compatibility. But I've always wondered if there is any use case where
> this value, as it behaves, might be practical. I don't quite understand
> how useful all the Org metadata in the comments of the tangled file can
> be. The expectation with `:comments org' is that only the content of the
> Org document will be rendered (as comments), but not its metadata, that
> all they do is unnecessarily fatten up the source file. I'm thinking,
> for example, of headers with lots of properties. or comment blocks,
> which would be visible in the tangled source file:
The original proposal by Eric Schulte:
https://list.orgmode.org/4BFFEE4F.5010608@ccbr.umn.edu/
>>> Maybe we should allow either exporting just the headlines of the
>>> org-mode file or exporting the entire org-mode file -- possibly after an
>>> ASCII export -- this would have the effect of prefixing every line in
>>> the org-mode file behind a comment *except* for the tangled source-code
>>> blocks.
Clearly, the "possible after an ASCII export" dropped somewhere in the
middle.
Best,
Ihor
Re: [Patch] ob-tangle.el: New value 'ascii' for the header argument ':comments', Rudolf Adamkovič, 2022/06/12