run bash sessions without config files

run bash sessions without config files

[Tyler Smith]

Hi,

I use shell-mode a lot, and have a very complex prompt, coloured with
escape codes and lots of bells and whistles. This appears to confuse
org-babel when I'm running code blocks in a session, similar to what's
described here:

https://emacs.stackexchange.com/questions/19735/emacs-freezes-with-any-org-babel-snippet-using-session

Is it possible to configure org-babel to ignore any customization files,
such as .emacs.d/init_bash.el and .bashrc?

As a workaround, I redefine PS1 and PS2 at the top of my org buffer,
which fixes the problem temporarily. I'd like a permanent fix if
possible.

Best,

Tyler

-- 
plantarum.ca

Re: run bash sessions without config files

[Tyler Smith]

On Wed, Aug 2, 2017, at 11:53 AM, Tyler Smith wrote:
> 
> Is it possible to configure org-babel to ignore any customization files,
> such as .emacs.d/init_bash.el and .bashrc?
> 

After some digging around, it looks like this isn't possible.
~org-babel~ starts shell sessions via the standard function ~(shell)~.
Loading ~init_bash.el~ is hard-coded into this function, so there's no
user-visible way to direct Emacs not to read it for org-mode code
blocks, while still using it in other contexts. 

Best,

Tyler

Re: run bash sessions without config files

[Adam Porter]

Tyler Smith <tyler@plantarum.ca> writes:

> On Wed, Aug 2, 2017, at 11:53 AM, Tyler Smith wrote:
>> 
>> Is it possible to configure org-babel to ignore any customization files,
>> such as .emacs.d/init_bash.el and .bashrc?
>> 
> After some digging around, it looks like this isn't possible.
> ~org-babel~ starts shell sessions via the standard function ~(shell)~.
> Loading ~init_bash.el~ is hard-coded into this function, so there's no
> user-visible way to direct Emacs not to read it for org-mode code
> blocks, while still using it in other contexts. 

Could you run the code in the source block within "bash --noprofile
--norc"?  You could use "-c" to pass the rest of the commands as a
string, or "-s" to pass to STDIN with a heredoc.  I don't know if it
will work, but it might...