schulte.e...@gmail.com writes:
> Alan Schmitt writes:
>
>> Hi Eric,
>>
>> schulte.e...@gmail.com writes:
>>
I see that "hello subtree" is tangled. Does it mean that to comment a
whole tree I need to comment every subtree (recursively)?
Thanks,
Alan
>>>
>>> I just pus
Alan Schmitt writes:
> Hi Eric,
>
> schulte.e...@gmail.com writes:
>
>>> I see that "hello subtree" is tangled. Does it mean that to comment a
>>> whole tree I need to comment every subtree (recursively)?
>>>
>>> Thanks,
>>>
>>> Alan
>>
>> I just pushed up a fix, thanks for catching this bug.
>
>
Hi Eric,
schulte.e...@gmail.com writes:
>> I see that "hello subtree" is tangled. Does it mean that to comment a
>> whole tree I need to comment every subtree (recursively)?
>>
>> Thanks,
>>
>> Alan
>
> I just pushed up a fix, thanks for catching this bug.
I'm sorry, but I think there is a bug w
Alan Schmitt writes:
> schulte.e...@gmail.com writes:
>
>>> I just tried it with my init file and it did not work. Here is a
>>> minimal example. Save this as "test.org":
>>>
>>> --8<---cut here---start->8---
>>> * Testing
>>>
>>> #+BEGIN_SRC emacs-lisp
>>> (me
schulte.e...@gmail.com writes:
>> I just tried it with my init file and it did not work. Here is a
>> minimal example. Save this as "test.org":
>>
>> --8<---cut here---start->8---
>> * Testing
>>
>> #+BEGIN_SRC emacs-lisp
>> (message "hello world")
>> #+END_SRC
Alan Schmitt writes:
> Hello,
>
> Sorry to resurrect this old thread, but I cannot make this work.
>
> b...@altern.org writes:
>
>> Rainer M Krug writes:
>>
>>> I agree - COMMENTing a subtree should automatically disable tangling of
>>> code blocks in the
>>> subtree. Would this something which
Hello,
Sorry to resurrect this old thread, but I cannot make this work.
b...@altern.org writes:
> Rainer M Krug writes:
>
>> I agree - COMMENTing a subtree should automatically disable tangling of code
>> blocks in the
>> subtree. Would this something which could be introduced easily, as it se
Hi Charles,
Charles Berry writes:
> Why not use the new exporter, rather than org-babel-tangle?
A very nice example on how the new exporter can be useful!
Thanks for sharing this,
--
Bastien
Bastien altern.org> writes:
>
> Hi Rainer,
>
> Rainer M Krug gmail.com> writes:
>
> > Follow up: would it be possible to have the same mechanism for tangling,
i.e. a tag :notangle:?
> > functioning would be equivalent to property tangle: no but more visible and
consistent with the
> > :noexpo
Hi Rainer,
Rainer M Krug writes:
> Follow up: would it be possible to have the same mechanism for tangling, i.e.
> a tag :notangle:?
> functioning would be equivalent to property tangle: no but more visible and
> consistent with the
> :noexport:? One could also define properties to be tangled
Bastien writes:
> Rainer M Krug writes:
>
>> I agree - COMMENTing a subtree should automatically disable tangling of code
>> blocks in the
>> subtree. Would this something which could be introduced easily, as it seems
>> there are quite a few
>> who assumed that it would be doing it?
>
> This
"Sebastien Vauban"
writes:
> Bastien wrote:
>> Rainer M Krug writes:
>>
>>> I agree - COMMENTing a subtree should automatically disable tangling of
>>> code blocks in the subtree. Would this something which could be introduced
>>> easily, as it seems there are quite a few who assumed that it w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/02/13 10:47, Sebastien Vauban wrote:
> Hi Rainer,
>
> Rainer M Krug wrote:
>> On 28/02/13 10:30, Sebastien Vauban wrote:
>>> Bastien wrote:
Rainer M Krug writes:
> I agree - COMMENTing a subtree should automatically disable tangl
Hi Rasmus,
Rasmus writes:
> Does this ONLY affect tangling or also other code?
Only tangling.
HTH,
--
Bastien
Bastien writes:> Rainer M Krug writes:
>
>> I agree - COMMENTing a subtree should automatically disable tangling of code
>> blocks in the
>> subtree. Would this something which could be introduced easily, as it seems
>> there are quite a few
>> who assumed that it would be doing it?
>
> This is
Hi Rainer,
Rainer M Krug wrote:
> On 28/02/13 10:30, Sebastien Vauban wrote:
>> Bastien wrote:
>>> Rainer M Krug writes:
>>>
I agree - COMMENTing a subtree should automatically disable tangling of
code blocks in the subtree. Would this something which could be
introduced easily, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/02/13 10:30, Sebastien Vauban wrote:
> Bastien,
>
> Bastien wrote:
>> Rainer M Krug writes:
>>
>>> I agree - COMMENTing a subtree should automatically disable tangling of
>>> code blocks in the
>>> subtree. Would this something which could b
Bastien,
Bastien wrote:
> Rainer M Krug writes:
>
>> I agree - COMMENTing a subtree should automatically disable tangling of
>> code blocks in the subtree. Would this something which could be introduced
>> easily, as it seems there are quite a few who assumed that it would be
>> doing it?
>
> Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/02/13 10:25, Bastien wrote:
> Rainer M Krug writes:
>
>> I agree - COMMENTing a subtree should automatically disable tangling of code
>> blocks in the
>> subtree. Would this something which could be introduced easily, as it seems
>> there ar
Rainer M Krug writes:
> I agree - COMMENTing a subtree should automatically disable tangling of code
> blocks in the
> subtree. Would this something which could be introduced easily, as it seems
> there are quite a few
> who assumed that it would be doing it?
This is now the case in master:
ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/02/13 00:33, Darlan Cavalcante Moreira wrote:
>
> I also converted my Emacs configuration to an org-mode file a long time ago
> and I hit the same
> spot you did. As you, I initially assumed (wished) that the COMMENT marker
> would disable
> t
I also converted my Emacs configuration to an org-mode file a long time ago
and I hit the same spot you did. As you, I initially assumed (wished) that
the COMMENT marker would disable tangling of blocks in that subtree. After
that I found out the tangle property, which solves the problem but has n
Alan L Tyree writes:
[...]
> G'day Eric,
>
> If I understand your problem correctly, doesn't the property :tangle: do
> what you want?
Yes, thanks; Aaron Ecay has also pointed out to me. It works and does
exactly what I said I needed. And you have both been very polite :-)
--
: Eric S Fraga
Eric S Fraga writes:
> Hello,
>
> I finally bit the bullet and converted by rather convoluted and long
> emacs startup code to an org file with emacs-lisp code blocks. I then
> tangle these into the actual code which is loaded by emacs at
> startup. So far, so good, and it does make it easier f
Aaron Ecay writes:
> You should be able to set the “tangle” property of the headline to “no”
> to achieve this effect: see the following section of the manual:
> (org) Header arguments in Org mode properties
>
> It isn’t as easy to manipulate as a tag, perhaps.
Thanks. This does work and is rel
You should be able to set the “tangle” property of the headline to “no”
to achieve this effect: see the following section of the manual:
(org) Header arguments in Org mode properties
It isn’t as easy to manipulate as a tag, perhaps.
--
Aaron Ecay
Hello,
I finally bit the bullet and converted by rather convoluted and long
emacs startup code to an org file with emacs-lisp code blocks. I then
tangle these into the actual code which is loaded by emacs at
startup. So far, so good, and it does make it easier for me to navigate
around my custom
27 matches
Mail list logo
