From: Tyler Smith <tyler@plantarum.ca>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Emacs Org-Mode Help <emacs-orgmode@gnu.org>
Subject: Re: org alters output of bash code blocks when run with :session
Date: Tue, 13 Mar 2018 13:24:50 -0400 [thread overview]
Message-ID: <1520961890.1938027.1301766872.58CEC7F1@webmail.messagingengine.com> (raw)
In-Reply-To: <87bmgcyrjp.fsf@nicolasgoaziou.fr>
On Mon, Feb 26, 2018, at 6:27 AM, Nicolas Goaziou wrote:
> Tyler Smith <tyler@plantarum.ca> writes:
> >
> > How do I force the babel session to leave the output alone, and print
> > it verbatim into the org file?
>
> It may be related to other problems related to prompt in shell sessions.
> See for example
> <http://lists.gnu.org/r/emacs-orgmode/2018-02/msg00081.html>,
> <http://lists.gnu.org/r/emacs-orgmode/2018-01/msg00415.html>, and for
> step forward a solution
> <http://lists.gnu.org/archive/html/emacs-orgmode/2017-04/msg00147.html>.
>
> Patches welcome!
It looks like ob-shell sets up sessions just by calling `shell`, which means all the user's customizations for shell-mode are automatically applied. This includes setting the prompt (e.g., from .emacs.d/init_bash.sh), as well as the value of `comint-prompt-regexp`.
I can't see any straightforward way to modify ob-shell sessions without also changing regular shell-mode. So I wonder if the easiest way to address this would be to create a new mode derived from shell-mode, ('ob-shell-mode')? That would give us a way to modify the prompt code inside babel without interfering with shell-mode.
If that sounds sensible I can put together a patch for ob-shell.el. Let me know what you think.
Best,
Tyler
next prev parent reply other threads:[~2018-03-13 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 22:10 org alters output of bash code blocks when run with :session Tyler Smith
2018-02-26 10:27 ` Nicolas Goaziou
2018-03-13 17:24 ` Tyler Smith [this message]
2018-03-14 13:51 ` Nicolas Goaziou
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=1520961890.1938027.1301766872.58CEC7F1@webmail.messagingengine.com \
--to=tyler@plantarum.ca \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).