Re: Problems starting emacs with correct environmental settings

[Peter Dyballa]

Am 03.07.2009 um 12:08 schrieb Pascal J. Bourguignon:

> Depending on the shell used by these scripts, you may edit one of the
> file used by these shell to set the environment. Eg. in case of bash,
> you could set your environment in ~/.bash_env or ~/.bash_login or
> ~/.bashrc ; for other Bourne shells, ~/.profile or ~/.login could be
> used.  In the last resort, you can directly edit the X startup scrip
> that is used in your configuration.


Alain send me some answers privately. To me it seems that processes  
created from the menu icons inherit only a small environment, could  
be that of a privileged process. It obviously has some basic  
components in PATH, but not Alain's private parts. And GNU Emacs  
actually is opened via emacsclient, from a shell script, which is  
passed to the launcher as " ~/..." and "~/" does not get expanded to  
something like "/home/<user>/..."

With pstree, observing such a launched process, one might find some  
basic clues. By using a shell script that creates a login shell to  
launch emacsclient from inside it a few problems could be cured…

--
Greetings

  Pete

It's not the valleys in life I dread so much as the dips.
                                – Garfield