FVWM + ( Re: startx + ~/.xsession and no ~/.xinitrc, or .xsessionrc )
On Sat, Dec 14, 2013 at 08:25:56PM +0000, Brian wrote:
>
> Put
>
> exec fvwm
>
> after the xterm command in .xsession. This command does not complete and
> .xsession doesn't close. You've summoned X, give it a chance to show off
> what it can do :).
>
> EXERCISE: You decide 'exec fvwm' is a splendid idea but decide to keep
> your .xsessionrc and put the extra line in it. Discuss the consequences.
:)
renamed .xsessionrc to .xsession and added exec fvwm as last line.
All good now, cheers!
For some reason I thought the 'exec fvwm' command was no longer
necessary, but as someone has already mentioned I could ditch the
.xsession* file(s) completely. This would mean moving the background
handling into the .fvwm/config file, which would be the 'cleaner'
solution.
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X
Reply to:
- References:
- startx + ~/.xsession and no ~/.xinitrc, results in reduced functionality (xfce4, sid)
- From: Zenaan Harkness <zen@freedbms.net>
- Re: startx + ~/.xsession and no ~/.xinitrc, results in reduced functionality (xfce4, sid)
- From: Bob Proulx <bob@proulx.com>
- Re: startx + ~/.xsession and no ~/.xinitrc, results in reduced functionality (xfce4, sid)
- From: Charlie <ariestao@skymesh.com.au>
- Re: startx + ~/.xsession and no ~/.xinitrc, results in reduced functionality (xfce4, sid)
- From: Bob Proulx <bob@proulx.com>
- Re: startx + ~/.xsession and no ~/.xinitrc, results in reduced functionality (xfce4, sid)
- From: Brian <ad44@cityscape.co.uk>
- Re: startx + ~/.xsession and no ~/.xinitrc, results in reduced functionality (xfce4, sid)
- From: Chris Bannister <cbannister@slingshot.co.nz>
- Re: startx + ~/.xsession and no ~/.xinitrc, results in reduced functionality (xfce4, sid)
- From: Brian <ad44@cityscape.co.uk>