Hi,
> Hi Eric,
>
> Sébastien Vauban wrote:
> > "Eric Schulte" wrote:
> >>
> >> [...] The following works for me without any hang.
> >> The only difference I can see between our setups is a matching prompt
> >> regexp.
> >
> > That was it. Fixing my PS1 prompt to be like yours (temporarily keeping
Sébastien Vauban writes:
> Hi Eric,
>
> Sébastien Vauban wrote:
>> "Eric Schulte" wrote:
>>>
>>> [...] The following works for me without any hang.
>>> The only difference I can see between our setups is a matching prompt
>>> regexp.
>>
>> That was it. Fixing my PS1 prompt to be like yours (tempo
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> Sébastien Vauban writes:
>
> #+begin_src sh :session "ecm"
> ls *.org
> #+end_src
>
> Nothing to do with the problem, but better to write `:session ecm' than
> `:session "ecm"', no?
>
Correct, it will be interprete
Hi Sébastien,
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
[...]
>> Yes, I agree that this should be implemented, patches are welcome :)
>
> I can imagine. My skills are still maybe a bit low to be productive in that
> area. But I really would like to help. Second problem is -
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> Sébastien Vauban writes:
>>>
>>> What's the impact of specifying "sh" or "bash" for the snippet?
>>
>> While "sh" blocks should work "bash" blocks will not be recognized. In
>> org-babel "sh" doesn't explicitly mean the "sh" comman
Hi Sébastien,
Sébastien Vauban writes:
> Hi Eric,
>
> FYI, I just re-did a git pull && make clean && make, before writing this post
> (5 min ago). I also launched a new Emacs.
>
> "Eric Schulte" wrote:
>> Sébastien Vauban writes:
>>>
>>> Let's assume the following Org file:
>>>
>>> #+begin_src
Nick Dokos writes:
>
> There are two methods that I use that I think are much more effective
> than sprinkling message calls all over the place:
>
> o edebug-defun: (in emacs-lisp mode, C-u C-M-x) will mark the
> function so that when it is called, the interpreter stops and you can
> t
Eric Schulte wrote:
> Hi S=C3=A9bastien,
>
> S=C3=A9bastien Vauban writes:
>
> [...]
> >
> > Just for my information (maybe being able to be more accurate next time, =
> or
> > even finding a solution myself), how do you debug such a problem?
> >
> > With which debugger, with tracing/stepping?
Hi Sébastien,
Sébastien Vauban writes:
[...]
>
> Just for my information (maybe being able to be more accurate next time, or
> even finding a solution myself), how do you debug such a problem?
>
> With which debugger, with tracing/stepping? With stack trace?
>
I'm almost embarrassed to admit t
Sébastien Vauban writes:
> Hi Torsten,
>
> Torsten Wagner wrote:
>> I just tried quickly. I use org-babel with python, up to now never with
>> shell scripting.
>>
>>> --8<---cut here---start->8---
>>> * Prerequisites
>>>
>>> #+begin_src sh :session ecm
>>>
Sébastien Vauban writes:
>
> It stops working only when I add `:session "whatever"' after the `sh'
> specification.
>
> That's the only difference between when it works and when it doesn't.
>
Hi Sébastien,
You discovered a tricky bug in the session-based evaluation of shell
blocks. I've just p
At Fri, 27 Nov 2009 10:15:41 +0100,
Sébastien Vauban wrote:
>
> Hi,
>
> Can I bump up this thread?
>
>
> > I'm trying to execute code through babel, for the first time -- I did use it
> > for small examples of LP, but not yet for enhanced work.
> >
> > This is my first file:
> >
> > * Prerequis
12 matches
Mail list logo
