Re: wmaker through x2go

2016-01-05 Thread richard lucassen
On Tue, 5 Jan 2016 10:10:20 -0500
"Carlos R. Mafra"  wrote:

> > Is there a way to start wmaker with its own screenconfig? I know I
> > can script to switch the GNUstep dir, but is there a more elegant
> > way to handle this?
> 
> I don't think there is an elegant way to do this. 
> 
> You can also try to use 'xrandr' to set the resolution. If wmaker
> was compiled with --enable-randr then the screen would be
> automatically updated for the new resolution.

With Debian packages it is not compiled in. But setting the right size
is not the problem when using fullscreen, it's the size of the programs
that are started automagically. Anyway, for the moment I'll script
around it, I simply switch between two GNUstep/Default directories by
symlinking one of the two. For future googlers:

The script called "~/scripts/x2go" that is called by x2go client through
the option "custom desktop":

#
#!/bin/dash

# if lockfile: exit
test -f /tmp/wmaker.lock && exit 1
# set lock to prevent from running two sessions:
touch /tmp/wmaker.lock
cd ~/GNUstep/
rm -f Defaults
ln -s Defaults.x2go/ Defaults
cd
exec /usr/bin/ssh-agent /usr/bin/wmaker
#

The local version called "/usr/local/bin/xx":

#
#!/bin/dash

# set lock to prevent from running two sessions:
if test -f /tmp/wmaker.lock ; then
  echo "\n[ERROR] lockfile found: /tmp/wmaker.lock\n"
  exit 1
fi
touch /tmp/wmaker.lock
cd ~/GNUstep/
rm -f Defaults
ln -s Defaults.local/ Defaults
cd
exec /usr/bin/ssh-agent /usr/bin/startx /usr/bin/wmaker
#

The lockfile is removed by the exit script:

$ cat ~/GNUstep/Library/WindowMaker/exitscript
#!/bin/dash

test -f /tmp/wmaker.lock && rm -f /tmp/wmaker.lock

R.

-- 
richard lucassen
http://contact.xaq.nl/


-- 
To unsubscribe, send mail to [email protected].


Re: wmaker through x2go

2016-01-05 Thread Carlos R. Mafra
On Tue,  5 Jan 2016 at 14:04:05 +0100, richard lucassen wrote:
> Hello list,
> 
> I have a systemdless workstation with a 1920x1440 monitor. I start
> wmaker from prompt:
> 
> /usr/bin/ssh-agent /usr/bin/startx /usr/bin/wmaker
> 
> No problem. I close using "save workspace state". So far, so good.
> 
> When I start wmaker through an x2go session on a laptop with a smaller
> screen, I get a fullscreen (because I want to have fullscreen) but with
> the workspace state of the big one (many objects are too big)
> 
> Is there a way to start wmaker with its own screenconfig? I know I can
> script to switch the GNUstep dir, but is there a more elegant way to
> handle this?

I don't think there is an elegant way to do this. 

You can also try to use 'xrandr' to set the resolution. If wmaker
was compiled with --enable-randr then the screen would be automatically
updated for the new resolution.


-- 
To unsubscribe, send mail to [email protected].


wmaker through x2go

2016-01-05 Thread richard lucassen
Hello list,

I have a systemdless workstation with a 1920x1440 monitor. I start
wmaker from prompt:

/usr/bin/ssh-agent /usr/bin/startx /usr/bin/wmaker

No problem. I close using "save workspace state". So far, so good.

When I start wmaker through an x2go session on a laptop with a smaller
screen, I get a fullscreen (because I want to have fullscreen) but with
the workspace state of the big one (many objects are too big)

Is there a way to start wmaker with its own screenconfig? I know I can
script to switch the GNUstep dir, but is there a more elegant way to
handle this?

R.

-- 
richard lucassen
http://contact.xaq.nl/


-- 
To unsubscribe, send mail to [email protected].