No User Shell Envir in Emacs via SSH

No User Shell Envir in Emacs via SSH

[Kenneth Jacker]

Sitting at home, I enter this into KDE's "Run Command..." (Kubuntu) to
"map" an X11/Emacs session running on my office machine onto my home
machine's monitor:

      +----------------------------+
      | Command:  ssh office emacs |
      +----------------------------+

The window appears on my home machine as expected and works fine.

The problem, however, is that my office machine's "bash environment"
isn't included/defined within Emacs. Apparently, the only
environmental variables defined are those from a system-wide Bash init
file (e.g. DISPLAY, HOME, LANG, MAIL, PATH, etc.).

Does anyone know what I need to do so that the "exported variables"
(i.e., environment) defined in my ".bashrc" are also present?

Thanks for your ideas!
-- 
Prof Kenneth H Jacker       khj@cs.appstate.edu
Computer Science Dept       www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC  28608  USA        

Re: No User Shell Envir in Emacs via SSH

[Glenn Morris]

Kenneth Jacker wrote:

>       +----------------------------+
>       | Command:  ssh office emacs |
>       +----------------------------+
[...]
> The problem, however, is that my office machine's "bash environment"
> isn't included/defined within Emacs.
[...]
> Does anyone know what I need to do so that the "exported variables"
> (i.e., environment) defined in my ".bashrc" are also present?

That's a ssh/shell question rather than an Emacs question...

AFAIK, the "ssh <host> <command>" syntax starts a non-login shell on
the remote machine, so it should source ~/.bashrc but not
~/.bash_profile. Putting echo statements at the top of my ~/.bashrc
and ~/.bash_profile files and using 'ssh host true' confirms this.

Maybe you actually need ~/.bash_profile to be sourced, in which case
you can always just try:

ssh office 'source ~/.bash_profile; emacs'

Or maybe you can move statements from ~/.bash_profile to ~/.bashrc if
that makes sense.

Or maybe you have something in your ~/.bashrc that causes processing
to be aborted when sourced by ssh. Eg I have:

[ "$PS1" ] || return

part-way through mine, which means ssh only reads the top part of it.

Re: No User Shell Envir in Emacs via SSH

[Eric Hanchrow]

    Sitting at home, I enter this into KDE's "Run Command..."
    (Kubuntu) to "map" an X11/Emacs session running on my office
    machine onto my home machine's monitor:

          +----------------------------+ | Command: ssh office emacs |
          +----------------------------+

    The window appears on my home machine as expected and works fine.

    The problem, however, is that my office machine's "bash
    environment" isn't included/defined within Emacs.  Apparently, the
    only environmental variables defined are those from a system-wide
    Bash init file (e.g.  DISPLAY, HOME, LANG, MAIL, PATH, etc.).

    Does anyone know what I need to do so that the "exported
    variables" (i.e., environment) defined in my ".bashrc" are also
    present?

I've never found a good solution for this.

What I'm using now is an astonishingly ugly Rube Goldberg type hack,
whereby my .bashrc runs a _perl_ program that creates files with
environment variable definitions -- one for the Bourne shell, and one
for emacs -- and then my .bash_profile sources the shell file, and I
have Emacs load the emacs file.

It works, but it makes the Baby Jesus cry.  Details upon request.

-- 
Software is largely a service industry operating under the
persistent but unfounded delusion that it is a manufacturing
industry.
        -- Eric Raymond

Re: No User Shell Envir in Emacs via SSH

[Mathias Megyei]

I have in my .bash_profile

LOGIN_SHELL=true
export LOGIN_SHELL

and in my .bashrc

if [ "x$LOGIN_SHELL" = "x" ]; then
    . .bash_profile
fi

Sa after ssh my .bash_profile is sorced only once.

Mathias

On Thu, 2006-11-30 at 21:31 -0800, Eric Hanchrow wrote:
>     Sitting at home, I enter this into KDE's "Run Command..."
>     (Kubuntu) to "map" an X11/Emacs session running on my office
>     machine onto my home machine's monitor:
> 
>           +----------------------------+ | Command: ssh office emacs |
>           +----------------------------+
> 
>     The window appears on my home machine as expected and works fine.
> 
>     The problem, however, is that my office machine's "bash
>     environment" isn't included/defined within Emacs.  Apparently, the
>     only environmental variables defined are those from a system-wide
>     Bash init file (e.g.  DISPLAY, HOME, LANG, MAIL, PATH, etc.).
> 
>     Does anyone know what I need to do so that the "exported
>     variables" (i.e., environment) defined in my ".bashrc" are also
>     present?
> 
> I've never found a good solution for this.
> 
> What I'm using now is an astonishingly ugly Rube Goldberg type hack,
> whereby my .bashrc runs a _perl_ program that creates files with
> environment variable definitions -- one for the Bourne shell, and one
> for emacs -- and then my .bash_profile sources the shell file, and I
> have Emacs load the emacs file.
> 
> It works, but it makes the Baby Jesus cry.  Details upon request.
>