Re: FVWM: problem installing fvwm
--- Ayan Mahalanobis <[EMAIL PROTECTED]> a écrit > The amazing thing! After installing FVWM from the web site you > mentioned > with fvwm-themes, it works fine from run level 3. I switched > back to run > level 5 and it pushed me back to GNOME. What could be the > reson. The > .xinitrc file is the same and of course it doesn't read it ar > is getting > over written by some thing. Does that mean that I got to stay > in run > level 3. > > Ayan > Usually in runlevel 5 (X) .xinitrc file from home directory is ignored (at least that's the behaviour on my machine) and instead the contents of .xsession is executed. The .xsession file _must_ be executable So: -- create a file .xsession echo fvwm2 >$HOME/.xsession -- make it executable chmod 755 $HOME/.xsession And it should work.(Works for me :-)) If it doesn't work you must figure out the X startup sequence in runlevel 5 (see files in /etc/X11/xdm) which is not an easy task _or_ keep looking for an answer to your problem _or_ enjoy runlevel 3 :-) Bye Calin = -- A mouse is a device used to point at the xterm you want to type in. Kim Alm on a.s.r. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: Open look applications
--- Dan Espen <[EMAIL PROTECTED]> a écrit : > szonyi calin <[EMAIL PROTECTED]> writes: > > Hi > > > > I have a problem. > > I have focus follow mouse and OpenLook application don't get > > focus > > when the mouse pointer enters the window. > > Actually they get the focus but window decorations don't > change. > > (The window looks unfocused but actually has focus). > > > > Do i need a specia command in my fvwm2rc for this > applications > > to behave correctly ? > > > > fvwm version 2.4.11 > > Style * Lenience > > See this section of the man page for details: > > OPEN LOOK and XVIEW COMPATIBILITY > Thanks Calin > -- > Dan Espen E-mail: [EMAIL PROTECTED] = -- A mouse is a device used to point at the xterm you want to type in. Kim Alm on a.s.r. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: Open look applications
Hi I have a problem. I have focus follow mouse and OpenLook application don't get focus when the mouse pointer enters the window. Actually they get the focus but window decorations don't change. (The window looks unfocused but actually has focus). Do i need a specia command in my fvwm2rc for this applications to behave correctly ? fvwm version 2.4.11 Thanks Bye Calin = -- A mouse is a device used to point at the xterm you want to type in. Kim Alm on a.s.r. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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?
--- Imre Vida <[EMAIL PROTECTED]> a écrit : > On Mon, Aug 26, 2002 at 05:28:28PM +0200, szonyi > calin wrote: > > Welcome to *nix > > Well, thanks for the nice welcome. > :-) > > > I think the man page should remain as it is. > > The man page format is standard. > > Man page _is_ a reference. Man page _is not_ a > > tutorial. Will never be. > > I was making a benevolent suggestion, what i > thought would/could > help some people. > It was not about any kind of tutorial, but only > about putting > a piece of information (that is already in the > manual) somewhere > at the begining, where people reading the man the > first time can > easily spot it. That's the problem with man pages: the references are at the end, usually :-) There was a good manual viewer (X11 based) which was acting like a browser (i.e. you had a TOC at the beginning and when you pressed the word on that TOC the program took you right to the place where it was in the manual.) but it seems it's not on the net anymore. > I was also not suggesting to change the (holy) > Format either. > But i can't fail to note here, that the standard > does not seem to be > that very strictly defined - see man of man: > > " A manual page consists of several parts. > They may be labelled NAME, SYNOPSIS, DESCRIPTION, > OPTIONS, FILES, >SEE ALSO, BUGS, and AUTHOR." > > Please note: MAY be labelled. > Sorry. Next time i'll double check before saying something > > So i don't really understand your rather harsh tone. > Could you explain? > I saw some man pages which were written some kind backwards: Name , Synopsys, Description (very long -literature), Options (command options), real description of options (after a couple of pages). I don't want to read man pages where the options of command are after ten pages of scrolling. A tutorial has many literature (by literature underestanding the part that tells to users what's a pager, what's a taskbar and other similar things.) > > > If you are impatient and newbie in the same time > > the chances of screwing things up are big > > The "To the Impatient" was meant to have a pinch of > irony/humor. Well, it seems i could not bring it > through - sorry about that. > Sorry, i misunderestood that one :-( My apologies. > > > best > > imre Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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?
--- Len Philpot <[EMAIL PROTECTED]> a écrit : > On Mon, Aug 26, 2002 at 05:28:28PM +0200, szonyi > calin wrote: > > > > Welcome to *nix > > It was hard to write, therefore it should be hard to > learn, right? ;-) > This kind of attitude worked for a long time when > there weren't > alternatives (at least perceived if not in reality). > However, in today's > market, as much as we (I?) sometimes dislike it, the > customer deserves > some consideration. Even in free software it helps. > Sorry. I didn't know that people with *nix experience didn't discovered fvwm yet. > > > I think the man page should remain as it is. > > The man page format is standard. > > I wish KDE / Gnome and others would include (more) > man pages instead of > all the (*?%$ HTML documentation. > They try to emulate windoze (with some success :-) ) > > > Man page _is_ a reference. Man page _is not_ a > > tutorial. Will never be. > > I agree - However some explantory text/refernce > material might be in > order here and there, whether in the man page or as > a separate document. > I think a separate document will be better. As someone wrote on this list, the man page is too big allready. > > > If you are impatient and newbie in the same time > > the chances of screwing things up are big, so > > my advice is to start with a configuration file > > that _works_ and modify it to suit your needs, > > Well, since I started this thread let me say that I > am not new to > computers, nor am I totally new to *nix -- I use and > administer Solaris > every day at work in a decent sized production > environment and have done > so for almost 4 years. I'm certainly not a guru (I > learn every day), but > not a Unix newbie either... an fvwm newbie, > certainly, though! > Sorry again. :-) Many new users which come from windows don't read documentation so I thought you are one of those. My apologies, but i'm became sick of seeing windoze lusers who can't configure their pc saying that *nix is hard to learn, when the only thing they have read in their life was the label from the OK button in a dialog box. > > > I think somebody wrote a tutorial for fvwm. > > Use it. > > The only one I've found is a bit thin. What's there > is useful enough, > but it's not much (as the author freely admits). > I found the examples distributed with the source a good start. Maybe I'll try to write an extensive tutorial. I'm not an expert but with some help I think I can do it. The main problem are the differences between versions of fvwm Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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?
--- Imre Vida <[EMAIL PROTECTED]> a écrit : > 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 K&M 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). > Welcome to *nix I think the man page should remain as it is. The man page format is standard. Man page _is_ a reference. Man page _is not_ a tutorial. Will never be. If you are impatient and newbie in the same time the chances of screwing things up are big, so my advice is to start with a configuration file that _works_ and modify it to suit your needs, I think somebody wrote a tutorial for fvwm. Use it. Good luck > > > imre > Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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
--- Ionel Mugurel Ciobica <[EMAIL PROTECTED]> a écrit : > În data de 21-08-2002, la 11h 06'39", Mikhael > Goikhman (migo) scria cãtre fvwm, despre "Re: FVWM: > i can't run fvwm 2.4": > > > I have the same problem with fvwm 2.4.x. Every time > I install a new > package with dselect or with apt-get the fvwm get > updated to 2.4.x. > and then I can't login, the error is the same with > the fixed font. > I have to manually downgrade fvwm to 2.2.4 > (hopefully I still have a > *.deb for that). > Try to compile fvwm manually > In my case: > > 1. I did not compile fvwm myself. I use the *.deb > file from woody. > 2. I use locale ro_RO.ISO-8859-16. I use export LC_ALL=ro_RO export LANG=ro in .xinitrc no problems I think the locale for Romania should be ro_RO.ISO-8859-2. Is there any reason for using ro_RO.ISO-8859-16 ? > 3. fvwm exits immediately. > What errors are printed ? Try to redirect stderr from fvwm to a file. > I also have compatibilities problems because I use > fvwm 2.2.4-2 > instead of 2.4.6-2. fvwm recommends fvwm-common, > xlibs conflicts with > fvwm-common. I think I need an older xlibs (I have > 4.1.0-17). > But I can't find, for instance 4.1.0-14. I never can > exit from the > dselect menu. I have to make a full upgrade and then > "dpkg -i > fvwm_2.2.4-2.deb". > Packages problems :-) If you compile it manually maybe you can fool debian that you have what he wants while still running your favourite version of fvwm. > Thank you, > Ionel Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: FVWM2 OpenLook theme
--- "Michel, Philipp" <[EMAIL PROTECTED]> a écrit : > Hello all, > > > I am desperately looking for some way to make my > fvwm desktop look as much > like Sun's OpenLook / ol(v)wm as possible, so as to > ease long-time openlook > users moving to a new desktop. I was wondering > whether anyone has done an > openlook theme in the past or if there's any > floating around. If I have to > do it myself (by taking lots of screenshots), I > would really appreciate some > pointers on how to quickly get at least the window > borders and menu to look > somewhat like openlook. > > I hope this is not too strange of a query... > AddToFunction RestartFunction + "Behave like OLVWM" Restart olvwm :-)) > Thanks a lot for your time, > > -Philipp > It seems it's the only way :-) Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: Scroll Lock mode
--- Remko Troncon <[EMAIL PROTECTED]> a écrit : > > Oh dear! You've lived with the most frequently > encountered > > problem for a year without knowing that the > solution is written in > > big friendly letters right at the front of the > fvwm FAQ. ;-) > > Oops. Didn't see that one :( Then again, it took me > a year to find out > that it was due to the modifiers that things stopped > working. I > still don't understand why these modifiers get > turned on from time to > time. > Thanks for the tip ! > On my keyboard pressing CTRL+s activates ScrollLock Pressing it again doesn't deactivate it so i have to press the real ScrollLock key. :-( Calin = -- The UNIX Hierarchy - Beginner - insecure with the concept of a terminal - has yet to learn the basics of "vi" - has not figured out how to get a directory - still has trouble with typing after each line of input ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: fvwm2 dropped from Red Hat Linux!
--- Jukka Lehti <[EMAIL PROTECTED]> a écrit : > Hi, > > I just noticed Red Hat has dropped fvwm2 package > from > their latest beta! I think this is outrageous and we > should make an official protest against this > unjustified decision! > You must be joking, right ? Why do you think the new computers have huge amounts of ram ? To run fvwm ? No You need something to take advantage of your ram. Something like Gnome or KDE. That's why they are dropping fvwm. In terms of memory usage it is not well suited for the new millenium. Programs these days consume more and more memory only fvwm decided: "Hey I can do a lot of things without consuming much memory". This is a very conservative aproach and is not well suited for times we are living in :-)) Fvwm has bad habbits. I mean why a program should free memory when you have so much at your disposal ? :-)) > I'm going to fill in a bug report to Red Hat's > bugzilla RSN. > And they will say it's a hardware problem :-)) Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: Problem with FvwmTheme
--- Dominik Vogt a écrit : > On Mon, Apr 22, 2002 at 01:12:12PM +0530, Rahul > > in the new version, I get the message FvwmTheme is > obsolete, please > > refer to colorsets section of fvwm(1) man page. As > a result, No > > gradients are rendered at all. > > > > My query is that if FvwmTheme is obsolete, how can > i define new > > colorsets. Please help me. > > Just keep cool :-) We're currently integrating > FvwmTheme into the > fvwm core. Please keep in mind that the odd version > numbers > (second digit) are development versions and may not > work as > expected. When we're done rewriting the code, > everything will > work like it did before, without changing the config > file. Well, the features i did't like when switching from fvwm 2.2 to fvwm 2.4 were errors and warnings about my config (obsolete commands etc. ) So i had to change my old fvwm 2.2 config file to make fvwm 2.4 happy. :-( Is this a feature ? Will it hapen again when fvwm 2.6 wil be released ? > Another problem you might fall for is that the fvwm2 > executable > was renamed to fvwm. If you do not use "make > install" you might > run an old executable with the new FvwmTheme version > (in other > words: without FvwmTheme). "make install" creates a > symbolic link > from fvwm2 to fvwm. > which s a good thing if you have an old fvwm 1 version on your disk :-) > Bye > > Dominik ^_^ ^_^ > Bye Calin > -- > Dominik Vogt, email: [EMAIL PROTECTED] > LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 > Tuebingen > fon: ++49 (0) 7071/7965-0, fax: ++49 (0) > 7071/7965-20 ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: X program options
--- Victor Eijkhout <[EMAIL PROTECTED]> a écrit : > Not really an fvwm Q, but ... > > In .Xdefaults I can specify > xterm*geometry: > > Where do I specify default options for colours, such > as "-bg gray"? I tried > xterm*bg: grey > in .Xdefaults, but that has no effect. should be xterm*background: grey > -- > Victor Eijkhout <[EMAIL PROTECTED]> > tel: 865 974 9308 (W), 865 673 6998 (H), 865 974 > 8296 (F) > http://www.cs.utk.edu/~eijkhout/ = ,-. ," ^ ^ ", | @ @ | --- ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: fvwm2.4.6 freeze
--- Mikhael Goikhman <[EMAIL PROTECTED]> a écrit : > On 10 Apr 2002 13:13:55 +0200, szonyi calin wrote: > > > > if you have in fvwm2rc lines like this > > +"text"Exec program > > instead of > > + "text" Exec exec program > > this could be the cause > > > > Fvwm is waiting for a comand to finnish and it is > > busy until that command finishes > > No, this is not correct. Exec is always done in a > forked process that is > not waited. Exec is asynchronous. PipeRead is > synchronous. > > "Exec" and "Exec exec" have exactly the same effect > from the window > manager point of view. Some shells (say, GNU bash) > even add "exec" > themselves if needed, so program is executed with no > additional fork. > Other shells fork, so there are 2 processes, shell > and program. > > Regards, > Mikhael. >From my experience they are not similar. I had problems in the past with this (Fvwm waiting for the command to finish and having to kill X) Maybe with newer versions of fvwm they are the same but in older versions i am sure that you should specify either +"Label" Exec program & or +"Label" Exec exec program Anyway, I haven't try +"Label" Exec program from some time because I had a slow computer and killing X wasn't a nice thing to do (on that old computer). :-) Bye Calin = ,-. ," ^ ^ ", | @ @ | --- ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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: fvwm2.4.6 freeze
--- Frank Liu <[EMAIL PROTECTED]> a écrit : > > any thoughts on what further debugging/testing I can > do to > find out the root cause? > > thanks! > frank > if you have in fvwm2rc lines like this +"text"Exec program instead of + "text" Exec exec program this could be the cause Fvwm is waiting for a comand to finnish and it is busy until that command finishes Maybe you have a module which is waiting for some sort of I/O. (FvwmEvent ?) Posting your config will help Bye Calin = ,-. ," ^ ^ ", | @ @ | --- ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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 + restart
--- Perry Hutchison <[EMAIL PROTECTED]> a écrit : > > Hey, I was thinking about something as I was > rewriting part of > > my configuration, and I thought it would be neat > if there were > > an option in fvwm2 where you can have fvwm2 > automatically reload > > when you change the .fvwm2rc. If no option like > that exists, > > what do you think about it? > > There a couple of practical concerns. > > * In order to do this, fvwm2 would have to > periodically "stat" the > .fvwm2rc file and check for the date and/or size > having changed. If > the stat were done only occasionally, there would > be a delay between > updating the file and the auto-restart. If done > frequently, it > would become a significant overhead in its own > right. > > * How would you avoid a race condition, wherein > fvwm2 sees the changed > file and decides to restart halfway through a > rewrite? Most text > editors don't lock files while writing them. Well, as far as i know there is one wm which does it and does it well -- olvwm (olwm). I don't know what method it uses but it's not slow. Of course olvwm doesn't have the complexity of fvwm2 :-) And in .olvwm you don't have pixmaps and fonts which will slow things down. Maybe using the style of olvmw to specify fonts and pixmaps will help (i.e. through X resource mechanism) One of the annoing things of doing restart is that fvwm allways seem to start on the firs page of the desk and you have to change the desk (page) to get back where you were before restart. = ,-. ," ^ ^ ", | @ @ | --- ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at 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]
