From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Tyler Smith <tyler@plantarum.ca>
Cc: Emacs Org-Mode Help <emacs-orgmode@gnu.org>
Subject: Re: org alters output of bash code blocks when run with :session
Date: Wed, 14 Mar 2018 14:51:19 +0100 [thread overview]
Message-ID: <871sgmn4tk.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1520961890.1938027.1301766872.58CEC7F1@webmail.messagingengine.com> (Tyler Smith's message of "Tue, 13 Mar 2018 13:24:50 -0400")
Hello,
Tyler Smith <tyler@plantarum.ca> writes:
> 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.
Creating a new mode doesn't sound like the easiest way.
What about the following suggestion, from a link I posted in this
thread:
Thanks for the examples. Anything goes, of course, but I'm hoping for a
tighter integration. Maybe a :prompt param to sh source blocks, which
sets the prompt in a session, and which also manipulates
`comint-prompt-regexp' or `shell-prompt-pattern' local in the session buffer.
Or a mechanism like in Tramp, where the shell prompt is set to a random
string not expected in the shell (see `tramp-end-of-output'), and
`comint-prompt-regexp' or `shell-prompt-pattern' are adapted
automatically local in the session buffer.
Regards,
--
Nicolas Goaziou 0x80A93738
prev parent reply other threads:[~2018-03-14 13:51 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
2018-03-14 13:51 ` Nicolas Goaziou [this message]
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=871sgmn4tk.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=tyler@plantarum.ca \
/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).