Hi,
Nathan Koch wrote:
##GNUStep
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh &
gdnc &
gpbs &
make_services
##
Still to no avail. Was wondering the proper way of starting it?
You only need to source the script:
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh
(no ampersand is needed, the script will terminate and you need it
execution before other things start)
gdnc and gpbs do not need to be started manually since a long time
anymore. You can do it though, no harm and speeds you the first app start.
make_services is also not strictly needed. You need to execute it only
after an application is installed so that the database of types is
updated. If you install GS apps through packages and they are done
conveniently, it will done during the install script (I am not sure
OpenBSDs one are done that way).
then you can start any gnustep app from terminal.
GNUstep does not provide a windowmanager, you probably want WindowMaker.
If you do this in your xinitrc, as Lars suggests:
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh
wmaker &
exec GWorkspace
GWorkspace will manage the session and exiting / logging our GWorkspace
will work as expected, but you need GWorkspace
If you have an issue with with GWorkspace and need to restart it or it
crashes, it will kill your session (*)
if you instead have:
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh
exec wmaker
wmaker "drives" your session, so you can strictly speaking not run
GNUstep apps yet, but any app you want, including GNUstep apps, from the
window maker menu. You can also run GWorkspace that way. If an app needs
GWorkspace it will also start for you.
Sum up:
First method is the "clean" way to have sort of full GNUstep workspace,
GWorkspace+WindowMaker
The latter method is less pure, but more versatile and with two clicks
ens with the same stuff open, but allows also e.g. just run X11 with an
xterm if needed (e.g. on a low-spec machine or if you are on a hurry)
(*) certain people report in certain setups mysterious crashes or
abnormous CPU usage after days or certain conditions, which cannot be
reproduced and so debugged.