It would appear that in the thread [missing keyboard shortcut in mc...]
on Jan 23, Constantinos Maltezos did say:
> On Thursday 22 January 2009 10:48:21 pm Joe(theWordy)Philbrook wrote:
> > Would you happen to know of another WM that invests in the keyboard as a
> > primary input device??
> Sadly, no. Although it's very possible that there's a window manager
> with which you can edit its keyboard shortcuts through an rc file. I
> just don't remember off the top of my head. But maybe FVWM does. I do
> recall that FVWM has pretty good keyboard support.
In Kubuntu 8.10 I did an:
apt-get install fvwm
But I'm at a loss as to how to start an fvwm session.
I don't know if it's significant but I boot to runlevel 3 without kdm...
one of the very first things I do to a kubuntu install is
update-rc.d -f kdm remove
Which I would have done via a virtual console without ever trying to
login via the gui... which might be why when I tried to restore kdm
to find out if fvwm would be listed if I clicked on the session type
icon I wound up with an unusable boot prompt that didn't listen to
either the mouse or keyboard until I did <ctrl>+<alt>+<F1> and
logged into a console where I could at least do another:
update-rc.d -f kdm remove
And return to using startx... (but that's a separate issue that I'll
never care about unless I somehow NEED kdm running to boot fvwm...)
But as it is I poked around the output of man fvwm and it seemed to
suggest the default place for a system configuration file would be:
Which directory didn't exist. Though there was a directory with a
sample config file in:
So I created a symbolic link to /usr/share/fvwm in /usr/local/share.
In this sample config there was some helpful comments which included:
# The suggested way to install this configuration file is to (re)move
# any .fvwm2rc file you have in ~/.fvwm or ~ and run fvwm without any
# startup file.
# Then, run the "Setup 95 Script" from the root menu.
What I got from that was that it should be possible to boot a basic
default fvwm session without having configured a startup file.
However, when I try to run fvwm from a console command-line, it's unable
to "open display" And when I learned from "fvwm -h" that there was an
option [-r] to "replace running window manager" I tried running
startx then attempted that from inside a kde konsole: And got 86 lines
of error messages and warnings and a messed up kde session...
It was still running kde, but <ctrl>+<tab> no longer switched between
the 4 configured desktops, <alt>+<tab> popped up a list of the open
windows from all 4 desktops, And if I selected an open window from
another desktop it would change to that desktop...
It occurs to me that Intrepid uses kde4 and for some reason it
doesn't appear to keep it's configuration settings in:
I know this because that file contains zero bytes. But it wouldn't
surprise me if fvwm needs an xorg.conf to learn how to do things like
"open display" But I'm not sure how to get a correctly configured
xorg.conf... I could copy the one from my Hardy installation which the
installer configured for this same pc. But I'm not sure how Intrepid
would react to that. Is there a way to get Intrepid to generate an
xorg.conf that matches the settings it's using (where ever the heck
I've included snippage of the error messages I got when I tried to
start fvwm below...
Could somebody give me a clue how to start an fvwm session in Kubuntu???