Re: Fw: Re: FVWM: Beginners how to

2007-10-02 Thread Chris G
On Mon, Oct 01, 2007 at 10:21:20PM +0100, Thomas Adam wrote:
 On Mon, Oct 01, 2007 at 10:10:18PM +0100, Chris G wrote:
  On Mon, Oct 01, 2007 at 10:47:19PM +0200, Jes?s Guerrero wrote:
   On Mon, 1 Oct 2007 22:41:56 +0200
   Jes?s Guerrero [EMAIL PROTECTED] wrote:
   
exec $HOME/.xsession.$DISPLAY
   
   Ok, forget my comment about that exec line. It is a redirector. I didn't 
   even read
   it, it was my fault. Still, the rest of things I said are valid. Your 
   xinitrc is
   strange.
   
  Not to mention that if the system is set to run at run level 5 (which
  tends to be the default nowadays) it won't even look at .initrc.
 
 Umm, this depends entirely on the distribution.  Debian, for instance
 doesn't distinguish between what's started in runlevels 2-5 inclusive,
 they're essentially all the same.
 
OK, it's the scripts 'underneath' xdm/kdm/wdm/gdm.  The distributions
I have played with have all ignored the .xinitrc when at run level 5.

Whatever, depending on distribution, there's a fair chance that
.xinitrc isn't being looked at.

-- 
Chris Green



Re: Fw: Re: FVWM: Beginners how to

2007-10-02 Thread Thomas Adam
On 02/10/2007, Chris G [EMAIL PROTECTED] wrote:
 On Mon, Oct 01, 2007 at 10:21:20PM +0100, Thomas Adam wrote:
  On Mon, Oct 01, 2007 at 10:10:18PM +0100, Chris G wrote:
   On Mon, Oct 01, 2007 at 10:47:19PM +0200, Jes?s Guerrero wrote:
On Mon, 1 Oct 2007 22:41:56 +0200
Jes?s Guerrero [EMAIL PROTECTED] wrote:
   
 exec $HOME/.xsession.$DISPLAY
   
Ok, forget my comment about that exec line. It is a redirector. I 
didn't even read
it, it was my fault. Still, the rest of things I said are valid. Your 
xinitrc is
strange.
   
   Not to mention that if the system is set to run at run level 5 (which
   tends to be the default nowadays) it won't even look at .initrc.
 
  Umm, this depends entirely on the distribution.  Debian, for instance
  doesn't distinguish between what's started in runlevels 2-5 inclusive,
  they're essentially all the same.
 
 OK, it's the scripts 'underneath' xdm/kdm/wdm/gdm.  The distributions
 I have played with have all ignored the .xinitrc when at run level 5.

 Whatever, depending on distribution, there's a fair chance that
 .xinitrc isn't being looked at.

http://fvwmwiki.bu-web.de/HashFvwmIrcFaq?highlight=%28CategoryIRC%29#head-5fd61e65135d57c37be671b7cf0970711e6cb591

-- Thomas Adam



Re: Fw: Re: FVWM: Beginners how to

2007-10-02 Thread Lucio Chiappetti
On Tue, 2 Oct 2007, Chris G wrote:

 Whatever, depending on distribution, there's a fair chance that
 .xinitrc isn't being looked at.

Sorry, I've not archived the beginning of the thread, but if I remember 
correctly the original poster was asking something about using fvwm 
remotely under VNC.

That's nothing to do with .xinitrc or alike.

All what you have to do is to provide in the directory ~/.vnc a file 
called xstartup. A minimal version of such file could just be 

#!/bin/sh
xsetroot -solid blue
fvwm 

and then do all your desktop configuration in ~/.fvwm/.fvwmrc

I arranged this for a retired colleague which uses VNC from a remote site 
to have a desktop running here so that he can read journals from our 
server.

If one wishes one can put other applications in xstartup, but I find 
easier and more elegant to let fvwm do it itself.

-- 
---
Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy)
For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html
---
()  ascii ribbon campaign - against html mail 
/\  http://arc.pasp.de/



Re: FVWM: Adding a screen w feature

2007-10-02 Thread Dominik Vogt
On Mon, Oct 01, 2007 at 01:39:12PM -0700, Gautam Iyer wrote:
 I was wondering if it would be possible to add a screen w feature to
 the Xinearama support.
 
 Quite often, I decide I want to move the current window to the center of
 the screen (or just place it again using MinOverlap... features).
 Unfortunately when fvwm does this it always does this according to a
 global screen number, or the current screen (i.e. screen containing the
 mouse pointer). It would be nice if Fvwm could do this based on the
 screen the window is currently in! Thus my suggestion of screen w to
 move arguments.
 
 Any chance of this happening?

Actually, that should have worked out of the box but didn't.  I
have fixed it in CVS.

Ciao

Dominik ^_^  ^_^

 --
Dominik Vogt


signature.asc
Description: Digital signature


Re: FVWM: Beginners how to

2007-10-02 Thread Michelle Konzack
Am 2007-10-01 11:39:49, schrieb Billy N. Patton:
 I've searched the FAQ and cannot find what I'm loking for.
 
 I run fvwm2 in my vnc connection just fine.  When I come to work and set at 
 my desk my Linux box is running kde.
 here is my .xinitrc  This doesn't start fvwm.
 #!/bin/sh
 
 exec $HOME/.xsession.$DISPLAY 21
 
 if [ -f $HOME/.bashrc ]
 then
   . $HOME/.bashrc
 fi
 
 #xrdb $HOME/.Xdefaults  # Load X11 resource database
 #exec $HOME/local/kde1.1/bin/startkde
 #exec /usr/bin/startkde
 #exec /home/cjitlal/bin/startkde3.1.1
 
 #xterm  -geometry 80x24-0-0 
 /usr/local/bin/icewm
 
- END OF REPLIED MESSAGE -

Normaly if you try to start icewm

But anyway, why do you execute your $HOME/.xsession.$DISPLAY?
They sould be sourced if called from a shell script.

And ofcourse, $HOME/.bashrc should be sourced before the xsession file.

And at all, all exec are not needed in the shell script.

Thanks, Greetings and nice Day
Michelle Konzack
Tamay Dogan Network


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSN LinuxMichi
0033/6/6192519367100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Re: FVWM: Beginners how to

2007-10-02 Thread Matthias Schroeder
Hi, 

Am Tue, 2 Oct 2007 16:28:49 +0200
schrieb Michelle Konzack [EMAIL PROTECTED]:

 Am 2007-10-01 11:39:49, schrieb Billy N. Patton:

  #!/bin/sh
  
  exec $HOME/.xsession.$DISPLAY 21
  

 But anyway, why do you execute your $HOME/.xsession.$DISPLAY?
 They sould be sourced if called from a shell script.
 

exec with redirect and no other command redirects all further output of
the script - often handy for logging and stuff like this - so
$HOME/.xsession.$DISPLAY is his logfile...

 And at all, all exec are not needed in the shell script.
 

uhm, not sure - but you can save some processes if your script
starts a long running process as last command - like .xsession and the
windowmanager. Without an exec your bash .xsession appears also in
the processlist... 

 Thanks, Greetings and nice Day
 Michelle Konzack
 Tamay Dogan Network
 

Regards,

Matthias 



Re: FVWM: Adding a screen w feature

2007-10-02 Thread Gautam Iyer
On Tue, Oct 02, 2007 at 01:17:31PM +0200, Dominik Vogt wrote:

  I was wondering if it would be possible to add a screen w feature to
  the Xinearama support.
  
  Quite often, I decide I want to move the current window to the center of
  the screen (or just place it again using MinOverlap... features).
  Unfortunately when fvwm does this it always does this according to a
  global screen number, or the current screen (i.e. screen containing the
  mouse pointer). It would be nice if Fvwm could do this based on the
  screen the window is currently in! Thus my suggestion of screen w to
  move arguments.
  
  Any chance of this happening?
 
 Actually, that should have worked out of the box but didn't.  I
 have fixed it in CVS.

Hmm. Don't follow: You mean in CVS Move screen c 50-50w 50-50w will
move the window to the center of the screen it is in (regardless of the
screen the pointer is in, or the primary screen number etc).

Thanks

GI

PS: Also perhaps useful would be to expand the $[screen] variable in
window context. Or add a $[w.screen] variable if the above might
cause confusion.

-- 
'Programmer' -- Someone who fixes a problem you didn't know you had in a
way you don't understand.



Re: FVWM: Beginners how to

2007-10-02 Thread Tim Hanson
On Monday 01 October 2007 09:39, Billy N. Patton wrote:
 I've searched the FAQ and cannot find what I'm loking for.

 I run fvwm2 in my vnc connection just fine.  When I come to work and set at
 my desk my Linux box is running kde.
 here is my .xinitrc  This doesn't start fvwm.
 #!/bin/sh

 exec $HOME/.xsession.$DISPLAY 21

 if [ -f $HOME/.bashrc ]
 then
. $HOME/.bashrc
 fi

 #xrdb $HOME/.Xdefaults  # Load X11 resource database
 #exec $HOME/local/kde1.1/bin/startkde
 #exec /usr/bin/startkde
 #exec /home/cjitlal/bin/startkde3.1.1

 #xterm  -geometry 80x24-0-0 
 /usr/local/bin/icewm

This is for tightvnc:

On the host, go to ~/.vnc and find xstartup

Mine looks like this:

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
fvwm2 

-- 
If you don't want your dog to have bad breath, do what I do:  Pour a little
Lavoris in the toilet.
-- Jay Leno