From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] Executing sh-code
Date: Mon, 30 Nov 2009 08:44:55 -0700 [thread overview]
Message-ID: <yn4skbwyq2w.fsf@gmail.com> (raw)
In-Reply-To: <87638tnivd.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Sun, 29 Nov 2009 22:03:50 +0100")
Hi Sébastien,
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> 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 that I do most of my elisp debugging
with the `message' function. I embed `message' debug statements to
print the values of key variables at key points, and I run through
problems looking at the output.
I'd be interested to hear if anyone can recommend a better elisp
debugging solution.
>
> Let's assume the following Org file:
>
> #+begin_src sh :session "ecm"
> cd ~/Personal
> #+end_src
>
> #+begin_src sh :session "ecm"
> ls *.org
> #+end_src
>
> I C-c C-c the first snippet. Nothing special, except it doesn't hang anymore.
> So, it already looks much better.
>
> Second snippet. C-c C-c. There, it still hangs ;-((
>
> Though, C-x C-b shows me the contents of the "ecm" buffer:
>
> cd ~/Personal
>
> ~ % ~/Personal % ls *.org
> echo 'org_babel_sh_eoe'
> Bookmarks.org Scorpios.org Tickler.org Voice-over-IP.org*
> Home.org* Succession.org Using-startx-for-Remote-Display.org refile.org
> ~/Personal % org_babel_sh_eoe
> ~/Personal %
>
> Looks closer to what it should...
>
> Still a little problem, though, as explained above.
>
So the fix here is to fix the value of the `comint-prompt-regexp'
variable in your shell. Org-babel uses this variable to digest output
from the shell. I have mine set with the following
--8<---------------cut here---------------start------------->8---
(defun schulte/set-shell-prompt-regexp ()
(setq comint-prompt-regexp "^\(.+\)"))
(add-hook 'shell-mode-hook 'schulte/set-shell-prompt-regexp)
--8<---------------cut here---------------end--------------->8---
You'll have to change the regexp ("^\(.+\)" in my example) to match your
prompt. I was unable to create your prompt locally. I find the
`regexp-builder' function to be very handy for these situations. If you
are unable to build a working regexp please send me a string of your
prompt and I'd be happy to return an appropriate regexp.
on a related topic:
I've also noticed that org-babel has difficulty digesting shell output
when it is ansi-colorized. I'm not sure what the best fix here would
be. We could probably start piping all org-babel session results
through something like `ansi-color-filter-region' but that feels a
little bit too heavy. I'd be interested to hear other peoples
thoughts/suggestions.
>
> BTW, 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" command, but rather
means 'run shell' which will default to whatever shell you have
configured.
Thanks -- Eric
>
> Best regards,
> Seb
next prev parent reply other threads:[~2009-11-30 15:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 14:22 [babel] Executing sh-code Sébastien Vauban
2009-11-27 9:15 ` Sébastien Vauban
2009-11-27 10:46 ` Eric S Fraga
2009-11-27 10:00 ` Torsten Wagner
2009-11-27 10:43 ` Sébastien Vauban
2009-11-27 19:32 ` Eric Schulte
2009-11-27 19:46 ` Dan Davison
2009-11-29 21:03 ` Sébastien Vauban
2009-11-30 15:44 ` Eric Schulte [this message]
2009-11-30 16:02 ` Nick Dokos
2009-11-30 16:16 ` Eric Schulte
2009-12-01 8:37 ` Sébastien Vauban
2009-12-01 10:01 ` Sébastien Vauban
2009-12-02 19:09 ` Eric Schulte
2009-12-04 13:25 ` Sébastien Vauban
2009-12-04 14:09 ` Sébastien Vauban
2009-12-04 17:04 ` Eric Schulte
2009-12-07 1:10 ` Torsten Wagner
2009-12-07 9:59 ` Sébastien Vauban
2009-12-04 17:03 ` Eric Schulte
2009-12-02 14:55 ` Sébastien Vauban
2009-12-02 20:16 ` Eric Schulte
2009-12-03 9:27 ` Sébastien Vauban
2009-12-03 16:06 ` Eric Schulte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yn4skbwyq2w.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).