You don't need that following the window manager. It can even prevent a
window manager from working. Try that with window maker and you'll be bombed
straight to the console.
Coronya
Debianized for now 37 days
On Thu, 25 Jan 2001, Pollywog wrote:
On Thu, 25 Jan 2001 10:22:51 -0800 (PST),
To quote Xucaen [EMAIL PROTECTED],
# I created ~/.xsession and added the line
Try 'chmod +x ~/.xsession'.
Hi all..
here's what's happening:
I created ~/.xsession and it causes X to restart
immediately upon login (I type my password, hit
return(enter) and poof! the screen flickers and
I'm
--- Pascal Hos [EMAIL PROTECTED] wrote:
here's what's happening:
I created ~/.xsession and it causes X to
restart
immediately upon login (I type my password,
hit
return(enter) and poof! the screen flickers
and
I'm prompted again for user name and
password)
I've tried about 5
To quote Xucaen [EMAIL PROTECTED],
# Hi all..
# here's what's happening:
# I created ~/.xsession and it causes X to restart
# immediately upon login (I type my password, hit
# return(enter) and poof! the screen flickers and
# I'm prompted again for user name and password)
#
# I've tried about 5
Hi all..
thanks foir all your help, because of you I
figured it out.
for some reason, fvwm starts automatically (I
haven't figured out why)
and when I created my .xsession, fvwm no longer
loaded, so I had to load it myself from my
.xsession script.
so now my last line of my .xsession is:
exec
On Thu, 25 Jan 2001 10:22:51 -0800 (PST), Xucaen said:
does anyone know why creating .xsession causes
fvwm to NOT load anymore? I'd really like to know
why
I don't think you need the following your window manager.
--
Andrew
Xucaen wrote:
Hi all..
thanks foir all your help, because of you I
figured it out.
for some reason, fvwm starts automatically (I
haven't figured out why)
and when I created my .xsession, fvwm no longer
loaded, so I had to load it myself from my
.xsession script.
so now my last line of
To quote Xucaen [EMAIL PROTECTED],
# Hi all..
# thanks foir all your help, because of you I
# figured it out.
#
# for some reason, fvwm starts automatically (I
# haven't figured out why)
# and when I created my .xsession, fvwm no longer
# loaded, so I had to load it myself from my
# .xsession
Lo, on Thursday, January 25, Pollywog did write:
On Thu, 25 Jan 2001 10:22:51 -0800 (PST), Xucaen said:
does anyone know why creating .xsession causes
fvwm to NOT load anymore? I'd really like to know
why
I don't think you need the following your window manager.
True,
exec
On Thu, Jan 25, 2001 at 01:20:54PM -0500, David B. Harris wrote:
You know, it *might* be useful to include your .xsession.
Just a bit. :)
The fact that you have one means that it overrides any system default, no?
Are you exec'ing a WM?
Mike
--
Michael P. Soulier [EMAIL
--- Michael P. Soulier [EMAIL PROTECTED]
wrote:
On Thu, Jan 25, 2001 at 01:20:54PM -0500, David
B. Harris wrote:
You know, it *might* be useful to include
your .xsession.
Just a bit. :)
The fact that you have one means that it
overrides any system default, no?
Are you
11 matches
Mail list logo