Re: FVWM: Focus back to parent
On Tue, Aug 27, 2002 at 11:49:33AM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 11:35:00AM +0200, Imre Vida wrote: if i start an application and quit it (immediatelly - e.g. briefly looking at an image, etc) the focus is not returned to the parent window, the focus seems to be undefined (i.e. no window selected). I use ClickToFocus and GrabFocus. Which version or snapshot are you using? This works fine with 2.5.3. it is the snapshot form 28.08 imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Focus back to parent
On Tue, Aug 27, 2002 at 02:16:07PM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 01:32:51PM +0200, Imre Vida wrote: On Tue, Aug 27, 2002 at 11:49:33AM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 11:35:00AM +0200, Imre Vida wrote: if i start an application and quit it (immediatelly - e.g. briefly looking at an image, etc) the focus is not returned to the parent window, the focus seems to be undefined (i.e. no window selected). I use ClickToFocus and GrabFocus. Which version or snapshot are you using? This works fine with 2.5.3. it is the snapshot form 28.08 Er, this snapshot will be built tomorrow. :-) sorry, i meant 20.08 imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: .fvwm2rc syntax guide?
On Sun, Aug 25, 2002 at 08:29:50PM -0400, Dan Espen wrote: Are you aware that you can start fvwm with no config file at all, press F1 or any mouse button on the root window and fvwm will offer to create a few different configurations for you? yes, it is mentioned in the man but it appears at line 365 in a very modest 2 line sentence (context: .fvwm2rc). it is repeated in a somewhat more extended version at ~1100 (Built in KM Bindings). while I agree that structurally these are apropriate locations, i believe not many newbies can spot and pick up the message (i personally missed them when first read/ scanned through the manual. mind you it is 8000+ lines of heavy text). I think it would be helpful to - to put a To the Impatient setion at the very begining of the man with this info - mention this also in one of the INSTALL and/or README files (e.g. README.sysrc). imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: i can't run fvwm 2.4
On Sat, Aug 24, 2002 at 09:14:54AM +, Mikhael Goikhman wrote: On 23 Aug 2002 23:32:02 +0200, Imre Vida wrote: This also suggests that the maintainers are aware of (at least some) problems on this front. This is to put it very softly, as John did it earlier a bit naughty against all those stupid users like me. Well, the multibyte support is marked experimental in 2.4.x and disabled by default. Sorry it caused you any problems. sorry, the criticism was not directed against you. I was just somewhat puzzled by what you said. To have an experimetal feature is fine, but to have it enabled in a stable distribution (Debian and RH) is not - especially when it is not documented for the user. But again this should be directed to a different forum. imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: i can't run fvwm 2.4
On Fri, Aug 23, 2002 at 06:33:59PM +, Mikhael Goikhman wrote: Is there any reason for using ro_RO.ISO-8859-16 ? It includes the euro sign and some other small changes AFAIK. I suppose fvwm-2.4.x exits when it does not find fixed *-iso8859-16 font. By the way these patches to replace searching for strictly fixed font were demanded by the Debian maintainer, I think he included these or similar patches before creating debs anyway. Sorry, but i don't understand this: If such a patch was requested and applied why does the program exit after not finding one set of fixed fonts? ((There is only one errormsg /to be precise - one msg twice/, and also it is misleading as it does not specify that it is looking for /in my case/ *-iso8859-15 fonts.)) This also suggests that the maintainers are aware of (at least some) problems on this front. This is to put it very softly, as John did it earlier a bit naughty against all those stupid users like me. Imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: i can't run fvwm 2.4
Hi, i run my machine under Debian woody. When i tried to switch to fvwm i had problems running fvwm (offical deb package v2.4.8). First i could not get it started with xdm but was still able to launch it from an xterm. Later on, however, i was not able to launch it at all what ever i tried. Finally i decided to down load the source and compile it myself, First i downloaded v.2.5.2 and it was running fine but later on i thought it would be may be safer to have the stable version. And now that i compiled and tried to run v2.4.9 i have exactly the same problem. There are two error messeges about fvwm not being able to find a fontset: [FVWM][GetFontSetOrFixed]: WARNING -- can't get fontset 'fixed', trying '-*-fixed-medium-r-normal-*-14-*-*-*-*-*-*-*' [FVWM][GetFontSetOrFixed]: ERROR -- can't get fontset '-*-fixed-medium-r-normal-*-14-*-*-*-*-*-*-*' The xserver /xfontsel/ does know about these fonts so they are definitely not missing (and the fontsever is running). Originally i had xdm setup to start up the window manager. In this case, after a blank window i got back to the login window (while any other window man e.g. icewm, sawfish or even gnome-session can be started without probs). xdm.log says: X connection to :0.0 broken (explicit kill or server shutdown). warning: process set to nice value 0 instead of -10 as requested (but i believe this is not about fvwm) I also tried to start fvwm from an xterm only xsession: i got the above errormsg about the fontset and nothing else hapens interestingly before the restart this worked despite the errormsgs. I tried this also as root - no difference. And run strace: i find the same erromsgs but nothing else that would give me a cue what is going on. I hope some of you do have an idea what could the problem imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: an idea to Maximization
Hi, i'm new to fvwm and like it a lot however, i was somewhat puzzled by the way Maximization works: wanted to define some hotkeys to maximize/grow windows horizontally/verticaly or even left/right/up/down and by combining these actions to get the best size and location (very often i end up with hundreds of windows open and then try to get the best out of them ;-) these combinations however do not work: the window switches back to it's 'normal' size after the second hotkey and only after repeating it, does it do the sec type of maximization (and of course only that one this time) so obviously, any of these actions is considered as a Maximization and any following action of the same type will be taken as a request to Unmaximize the window (toggle). of course, one could use True to force the maximizations but then the unmaximization toggle will not work with the same hotkey if there is already the possibility to do vert. and hor. maximizations separately, wouldn't it be nicer/more logical to also handle them separately (ie. assign two booleans instead of one single)? best imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
