Am 07.02.2013 22:53, schrieb Myles English:
Hi Andreas,
Andreas Röhler writes:
Am 06.02.2013 16:17, schrieb John Kitchin:
Thanks for the -Q reminder. I get the same output if I run with emacs -Q
(although I do have to add :results output to each block. I had that set as
a default in my init
Hi Andreas,
Andreas Röhler writes:
> Am 06.02.2013 16:17, schrieb John Kitchin:
>> Thanks for the -Q reminder. I get the same output if I run with emacs -Q
>> (although I do have to add :results output to each block. I had that set as
>> a default in my init files).
>>
>> I had the problem descr
Am 06.02.2013 16:17, schrieb John Kitchin:
Thanks for the -Q reminder. I get the same output if I run with emacs -Q
(although I do have to add :results output to each block. I had that set as
a default in my init files).
I had the problem described in the footnote you listed, and that is why I
a
Thanks for the -Q reminder. I get the same output if I run with emacs -Q
(although I do have to add :results output to each block. I had that set as
a default in my init files).
I had the problem described in the footnote you listed, and that is why I
am using python-mode 5.2, which doesn't have t
Hi John,
John Kitchin writes:
> I have been trying to use the :session feature of babel for python code
> blocks. I have noticed a few things that might be areas for
> improvement. Some issues are related to what I think might be a need for
> sanitizing the code blocks and the output.
>
> I am u
