> I *think*, although I'm not entirely certain, that a gdm login will end
> up reading .xsession. It's been a long time since I've used gdm, so I'm
> a little unclear on the details.
I think that gnome will read a .gnomeprofile if it exists but only if
it is executable, which is counterintuitive.
Dave Carrigan wrote:
[snip]
> It depends on what kind of session you choose to launch with gdm. It
> won't evaluate .environment.
> However, if you launch the `Xsession' session, then it will launch
> .xsession. Take a look at the session scripts in /etc/gdm/Sessions,
> which should tell you wh
Stefan Bellon <[EMAIL PROTECTED]> writes:
> I know very little of the login process. Does gdm evaluate the
> ~/.environment file? Or the ~/.xsession file? If neither, then the
> above solution doesn't give me any advantage. If it does evaluate one,
> then yes, this is clearly the way to go.
It de
Lo, on Wednesday, May 22, Stefan Bellon did write:
> Dave Carrigan wrote:
> > Stefan Bellon <[EMAIL PROTECTED]> writes:
>
> [snip]
>
> > > gdm, but without the rest of GNOME, only gdm.
>
> > gdm won't evaluate your .bashrc to set the environment variables. The
> > idomatic solution is to create
Dave Carrigan wrote:
> Stefan Bellon <[EMAIL PROTECTED]> writes:
[snip]
> > gdm, but without the rest of GNOME, only gdm.
> gdm won't evaluate your .bashrc to set the environment variables. The
> idomatic solution is to create a ~/.environment file where you set all
> of your environment variabl
Stefan Bellon <[EMAIL PROTECTED]> writes:
> > I would think that you'd want the environment variables to be visible
> > to your entire X session, including FVWM and all of the programs it
> > starts.
>
> Hm, haven't thought of that yet.
>
> > How are you starting X? Are you running one of the d
Richard Cobbe wrote:
[snip]
> I would think that you'd want the environment variables to be visible
> to your entire X session, including FVWM and all of the programs it
> starts.
Hm, haven't thought of that yet.
> How are you starting X? Are you running one of the display managers
> like xdm,
Lo, on Wednesday, May 22, Tom Cook did write:
> On 0, Stefan Bellon <[EMAIL PROTECTED]> wrote:
> > Felix Natter wrote:
> > > Stefan Bellon <[EMAIL PROTECTED]> writes:
> >
> > > > When using Emacs to start a compilation (e.g. with C-c C-c from C++
> > > > mode) you get "make -k" as default. The p
On 0, Stefan Bellon <[EMAIL PROTECTED]> wrote:
> Felix Natter wrote:
> > Stefan Bellon <[EMAIL PROTECTED]> writes:
>
> > > When using Emacs to start a compilation (e.g. with C-c C-c from C++
> > > mode) you get "make -k" as default. The problem I'm experiencing
> > > is, that I need some shell va
Stefan Bellon <[EMAIL PROTECTED]> writes:
> The variables *are* already in ~/.bashrc (and they're exported there).
> But Emacs only knows about them if I start Emacs from a bash. If I
> however use a function key I have defined with fvwm, then Emacs doesn't
> start with the shell as parent and the
Felix Natter wrote:
> Stefan Bellon <[EMAIL PROTECTED]> writes:
> > When using Emacs to start a compilation (e.g. with C-c C-c from C++
> > mode) you get "make -k" as default. The problem I'm experiencing
> > is, that I need some shell variables set in the Makefile. I've set
> > them in my ~/.bash
Stefan Bellon <[EMAIL PROTECTED]> writes:
> Hi!
>
> When using Emacs to start a compilation (e.g. with C-c C-c from C++
> mode) you get "make -k" as default. The problem I'm experiencing is,
> that I need some shell variables set in the Makefile. I've set them in
> my ~/.bashrc and it works fine
Hi!
When using Emacs to start a compilation (e.g. with C-c C-c from C++
mode) you get "make -k" as default. The problem I'm experiencing is,
that I need some shell variables set in the Makefile. I've set them in
my ~/.bashrc and it works fine if I start Emacs from an xterm which has
this variable
13 matches
Mail list logo
