Re: [ANN] lisp/ob-tangle-sync.el

[Mehmet Tekman]

>> Ihor Radchenko <yantar92@posteo.net> writes:
>>
>> May it be better to make :tangle header argument compound?
>> Like ":tangle "file" export". Similar to :results header argument. See
>> "16.6 Results of Evaluation" section of Org manual.
>>
>
> Mehmet Tekman <mtekman89@gmail.com> writes:
>
> That's a great idea I had not considered, and would definitely reduce
> the header bloat, especially since `:tangle-sync' *requires* the
>`:tangle' header to be there.

On closer inspection it might actually be unpractical to have the sync
action within the `:tangle' syntax, the main reason being that people
might define the tangle target in the document header for ease of use.

e.g.

#+begin_example

#+TITLE: Sync Many Blocks
#+PROPERTY: header-args  :tangle /tmp/default_tangle.txt :comments yes

** File Contents
 
*** Free Head

#+begin_src conf
  This is some text that can be synced both ways by default
#+end_src

*** Import

#+begin_src conf :tangle-sync import
  This is text that can only be imported from the remote, but it still
  refers to the default tangle argument
#+end_src

#+end_example

If we instead encode the sync action in the `:tangle' syntax then users
will have to explicitly type out the tangle file in each block.

Also, tangle-sync wouldn't be the only extra tangle-related property in
a block, since tangle-mode is also a thing.

Is it okay to leave `:tangle-sync' as it is?