CVS domivogt: * Retry write() on pipe if it returns EINTR.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt03/07/29 10:39:43 Modified files: . : ChangeLog fvwm : module_interface.c Log message: * Retry write() on pipe if it returns EINTR. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Even better fix ;-)
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt03/07/29 10:42:01 Modified files: fvwm : module_interface.c Log message: * Even better fix ;-) -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Wiki for fvwm?
Hi there, On 28 Jul 2003 at 22:26:27 +0200, Felix E. Klee wrote: On Thursday 24 July 2003 10:39, Mario Domgörgen wrote: Wouldn't it be great if fvwm has its own wiki? Fvwm is customizable and there are so a lot of usefull code snippets, that i would lek the idea of a playce where we can collect such things. In the FAQ are already some great pieces, but there are doubtless a lot more... What do you think of that? I proposed that a couple of month ago as well. Surely it would would be nice to have such a thing but noone seems to have tackled it and I just don't have the time. I am not that sure if it is that appropriate. (see http://wiki.org/wiki.cgi?WhatIsWiki) Allowing everyone to edit site contents requires the pages to be maintained, so that advertising and other unwanted, probably illegal stuff is removed. On the wiki pages at http://c2.com/cgi/wiki?WikiWikiSandbox one can even place pictures which is quite precarios since someone could place illegal ones. Sure, the changer's IP address is stored but it seems a lot of work to trace somebody which can be identified by it's IP address only. Further I don't think that it is that good for storing config parts for fvwm because users will hardly find something, since it will be just to much. I'd rather if we collect config parts, like button setups, titlebar decorations, menu definitions and fvwm scripts, and place them together with a screenshot and description on the web site. Having them fully maintained ensures higher quality and saves the user time (and nerves :-) Regards, Uwe -- 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: window resize in 2.5.7
On Mon, Jul 28, 2003 at 07:37:17PM +0200, Olivier Chapuis wrote: On Mon, Jul 28, 2003 at 04:11:15PM +0200, Dominik Vogt wrote: On Mon, Jul 28, 2003 at 03:52:15PM +0200, Olivier Chapuis wrote: On Wed, Jul 23, 2003 at 02:36:59PM +0200, Dominik Vogt wrote: On Wed, Jul 23, 2003 at 08:07:32AM -0400, Ben Winslow wrote: Since I could reproduce this, I decided to track it down... fvwm is indeed trying to grab the pointer and failing [XBell() at functions.c:992 in execute_complex_function], however, it's not because of anything Jules has done... In ConfigFvwmDefaults, an EWMHActivateWindowFunc function is defined--whenever gkrellm is clicked on to be moved (I think GTK2 is what's actually causing this to happen), EWMHActivateWindowFunc is called, causing this problem. Which gkrellm version? It doesn't happen with 1.2.10. Anyway, this is a gkrellm bug: An application can not expect that the window manager processes any requests (_NEW_WM_ACTIVE_WINDOW client message in this case) while the server/pointer/keyboard is grabbed. This should be fixed in gkrellm. Maybe. But it is not always needed to grab the pointer when we execute a complex function. So, I suggest that when fvwm fail to grab the pointer for executing a complex function we do not abort the function execution. This fix Jules problem (that I can reproduce, and it happens the same thing with the Mozilla resize grip). What do you think? I think it's a bad idea. It is practically impossble to guess whether a function needs to grab the pointer before executing or not, and it depends on what other application do too. For example, if an application warps the pointer while a function is executed, all sorts of strange things can happen. In fact I can reproduce the gkrellm problem only on certain condition: I've a FvwmEvent running which executes a complex function on each module events. fvwm bell and abort a complex function which is run with a raise_window (gkrellm) or a configure_window (Mozilla resizing with grip). Also I've an FvwmEvent which auto shade a FvwmButtons with a delay via leave_window (with the schedule command and a shade complex function). When, I leave the FvwmButtons and popup a menu of an application before auto shade the auto shade complex function xbell and abort. So I really think that by default we should not abort complex functions when we cannot grab the cursor. Maybe a Grab prefix or a Grab function (with automatic ungrab) should be introduced, but I _think_ that the case where we need to grab is exceptional. Do you have a real life example (say in your fvwm config)? The pointer *must* be grabbed during function execution. We have made various attempts to ignore this in the past, and they all ended in disaster. For example, if the user can click in windows (or release a button - quite likely during function execution) she can cause EnterNotify and LeaveNotify events, screwing up scripts that make tricky use of Raise/Lower/Focus. Bye Dominik ^_^ ^_^ -- 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: Wiki for fvwm?
I'd rather if we collect config parts, like button setups, titlebar decorations, menu definitions and fvwm scripts, and place them together with a screenshot and description on the web site. I agree with Uwe. The current approach is a lot easier, much more maintainable, and gives a good overview. The threshold is a little bit higher, because you have to actually send a mail to someone, but maybe that isn't really such a bad thing after all ;-) IMHO, wiki is only suitable for early stages of a work in progress, when things are in a state of flux, and having centralized documents is a lot of overhead on synchronization. But once things stopped moving, the whole wiki hierarchy (which is usually a huge mess by then in which you get lost very quick) should be organized into centrally administered documents. Just my 2 cents. cheers, Remko -- 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: Transparent menus
On 17 Jul 2003 00:04:38 +0300, Mikhael Goikhman wrote: On 16 Jul 2003 12:29:45 +0200, stu wrote: Is it possible to have transparent menus with fvwm 2.5.7? If so, how would I go about doing it? It is possible. You should define a colorset with RootTransparent buffer (buffer is optional, read FvwmTheme man page) and set a root image using either Esetroot or fvwm-root -r. I want to have a transparent menu with the root image given by xsetroot: xsetroot -mod 4 4 -bg rgb:10/18/20 -fg rgb:30/38/40 I do this by using gimp to grab xsetroot -mod 4 4 -bg rgb:10/18/20 -fg rgb:30/ 38/40 to a image file. Is there a simple way ? Regards, Benoit -- 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: Wiki for fvwm?
Remko Troncon [EMAIL PROTECTED] writes: I agree with Uwe. The current approach is a lot easier, much more maintainable, and gives a good overview. The threshold is a little bit higher, because you have to actually send a mail to someone, but maybe that isn't really such a bad thing after all ;-) If the maintainer of the homepage agree with that, i will be happy ... :) IMHO, wiki is only suitable for early stages of a work in progress, when things are in a state of flux, and having centralized documents is a lot of overhead on synchronization. But once things stopped moving, the whole wiki hierarchy (which is usually a huge mess by then in which you get lost very quick) should be organized into centrally administered documents. It could be very hard to get a centralized document of configuration scripts. But there will be a dozen differant ways to make a panel with FVWMButtons for example. How do you want to deal with that in a centralized document? I think you talk about a manual but i want seomthing for configuration. In the moment all of these things are put in the faq. Okay for the moment ... but a faq could become very unreadable if add a dozen alternatives for every problem on it ... Mario -- Chaos reigns within. Reflect, repent, and reboot. Order shall return. -- 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: Wiki for fvwm?
Felix E. Klee [EMAIL PROTECTED] writes: I proposed that a couple of month ago as well. Surely it would would be nice to have such a thing but noone seems to have tackled it and I just don't have the time. Maybe you could do it? I'm sure the FVWM web site maintainers will provide you with the neccessary web space. If there is webspace and a rough consens that we want something like that, i would do that although i never have started a public wiki But couldn't be that hard and maybe someone could help me... :) Mario -- Out of memory. We wish to hold the whole sky, But we never will. -- 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: Wiki for fvwm?
Hallo Mario, Mario Domgörgen schrieb am Dienstag, den 29. Juli 2003: Every site need to be maintained, only that on a wiki that's collective work of a lot of people. Wikis work with the expectation that there are more good that bad users and that the bad users will not stay very long when their try to destroy the work of other people will silently removed. And it's really more work to add illegal material than to remove it. Besides, i have never heard or seen anything like that on linuxwiki.de or emacswiki.org. I got the idea of wiki, but I see not that big difference to the current mailing list procedure. Everyone is free to post ideas, scripts, shots... to the fvwm-mailing list. If the posted is good we will put it on the web site. Having them fully maintained ensures higher quality and saves the user time (and nerves :-) But you need therefor seomone who mantain the site ... it's easier just to add two pages on a wiki, then sending a maintainer the work and wait till he transfer it. Emacswiki is really a great example how usefull it can be to collect configuration scripts on a wiki. Nobody hinder you to add a screenshot and a description to you button config on a wiki... At the moment mainly I keep the web site up to date. I just commit my changes via cvs. A couple of months ago I remade the fvwm web site using php. At the moment I am working on a concept making the screenshot and maybe download pages generic, so that it will be easier to add new shots, scripts, pics and information. Users won't be allowed to do changes but it will be much easier for the maintainer to add resources to the web site. Since my time is quite limited (full-time work and one-year old son :-) progress is quite poor. If you would like to do some work on the web site you might get cvs access, but I am not the one to be asked for that. How is it? Has somebody free webspace for a wiki or does the maintainer of the hompage want us all to send our scripts with descriptions and images to him? If it is small you could send it to the fvwm-mailing list, if it is bigger please provide a link were we can download it. Regards, Uwe -- 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: Wiki for fvwm?
Uwe Pross [EMAIL PROTECTED] writes: Every site need to be maintained, only that on a wiki that's collective work of a lot of people. Wikis work with the expectation that there are more good that bad users and that the bad users will not stay very long when their try to destroy the work of other people will silently removed. And it's really more work to add illegal material than to remove it. Besides, i have never heard or seen anything like that on linuxwiki.de or emacswiki.org. I got the idea of wiki, but I see not that big difference to the current mailing list procedure. Everyone is free to post ideas, scripts, shots... to the fvwm-mailing list. If the posted is good we will put it on the web site. Mailing-lists,irc and wiki have many things in common. I prefer wikis before lists because the information is sorted and easier to find than searching for subjects in a archive of a list. I had always the feeling that here are a lot of god hints that are never getting on the site... Transparent menus are one thing for example (a bad one, okay, as this should be really easy to find searching the archive but neverless), the question hit the mailing list every month or so, but it is not in the faq ... i'm sure could find some other examples But you need therefor seomone who mantain the site ... it's easier just to add two pages on a wiki, then sending a maintainer the work and wait till he transfer it. Emacswiki is really a great example how usefull it can be to collect configuration scripts on a wiki. Nobody hinder you to add a screenshot and a description to you button config on a wiki... If you would like to do some work on the web site you might get cvs access, but I am not the one to be asked for that. I never really got used to things like xml,html or php ... Me would be a very bad choice to help maintaining a homepage... :) How is it? Has somebody free webspace for a wiki or does the maintainer of the hompage want us all to send our scripts with descriptions and images to him? If it is small you could send it to the fvwm-mailing list, if it is bigger please provide a link were we can download it. When for example a configuration of a panel is suitable for the homepage i will :) Mario -- The Tao that is seen Is not the true Tao, until You bring fresh toner. -- 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: Wiki for fvwm?
Hi there, On 29 Jul 2003 at 16:20:34 +0200, Mario Domgörgen wrote: Mailing-lists,irc and wiki have many things in common. I prefer wikis before lists because the information is sorted and easier to find than searching for subjects in a archive of a list. I had always the feeling that here are a lot of god hints that are never getting on the site... Transparent menus are one thing for example (a bad one, okay, as this should be really easy to find searching the archive but neverless), the question hit the mailing list every month or so, but it is not in the faq ... i'm sure could find some other examples You are right, currently the web page does not provide good configs and setups. As I said I am going to change that. But it may take some time. When for example a configuration of a panel is suitable for the homepage i will :) Certainly, I think we should provide all kinds of configs like for FvwmButtons, FvwmWindowList, Pager, Menus and so on. It may just take some time until this this kind of resource pool has been set up. If your are going to provide a FvwmButton-setup, please ensure that it runs as you expect by Reading this config file using Read FvwmButtonrc So it is easier for other users to use your config. Please provide pixmaps for the buttons, links to the programs to be swallowed, a screenshot of the button bar and a short description. Regards, Uwe -- 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: Wiki for fvwm?
On Tuesday 29 July 2003 08:11, Uwe Pross wrote: I am not that sure if it is that appropriate. (see http://wiki.org/wiki.cgi?WhatIsWiki) Allowing everyone to edit site contents requires the pages to be maintained, so that advertising and other unwanted, probably illegal stuff is removed. On the wiki pages at http://c2.com/cgi/wiki?WikiWikiSandbox one can even place pictures which is quite precarios since someone could place illegal ones. Sure, the changer's IP address is stored but it seems a lot of work to trace somebody which can be identified by it's IP address only. Hm, other Wikis that I've used word fine (e.g. WikiPedia or the EMACS Wiki). But maybe that really involves some good administration. So, why not try it out? Maybe it works, maybe not. Further I don't think that it is that good for storing config parts for fvwm because users will hardly find something, since it will be just to much. I see the advantages of a Wiki in it being an intermediate thing between the FAQ (which is very slow to update and possibly can't cover as much content) and the mailing lists (which are there for discussion and not to find ready made solutions). I'd rather if we collect config parts, like button setups, titlebar decorations, menu definitions and fvwm scripts, and place them together with a screenshot and description on the web site. Hm, then I would have a couple of things to contribute. Among other things 1. a setup of a simple clock running in an rxvt that can be swallowed in the panel, 2. a setup of a simple tool to watch log files (again running in an rxvt) including the neccessary FVWM menu setup, 3. a setup for geometric arrangement and management of desktops (i.e. they are navigatable by keyboard shortcuts, and are not arranged in a linear fashion), 4. a method to include menus for CodeWeavers CXOffice and CXPlugin. All these things took me quite some time to set up and are of general interest. In addition I would for example like to see other people's small one-liners for clocks, dial up utilities, etc.. Would you really add this to the FAQ? Would I post it to the mailing list? No, because I don't want to waste my time to dig it out, add some explanatory text and just see it vanishing in the archives. Having them fully maintained ensures higher quality and saves the user time (and nerves :-) Higher quality? - maybe. Users time and nerves? - probably not. Let's not forget what costs really time and nerves: browsing the mailing list archives and trying to forge things by oneself. Felix (just wondering why there is so much of a discussion trying to prevent someone from contributing something that might come in handy) -- To contact me in private don't reply but send mail to felix DOT klee AT inka DOT de -- 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: Wiki for fvwm?
On Tue, Jul 29, 2003 at 08:11:19AM +0200, Uwe Pross wrote: I am not that sure if it is that appropriate. (see http://wiki.org/wiki.cgi?WhatIsWiki) Allowing everyone to edit site contents requires the pages to be maintained, so that advertising and other unwanted, probably illegal stuff is removed. well. actually everybody who puts up example configuration and other information on the wiki is also able to remove illegal and unwanted stuff. so the wiki is maintained by the wiki users itself. the work needed to maintain the wiki is divided up between its users and saves a lot of time to everybody. maintaining such a huge information pool would be a fulltime job for a single person. Further I don't think that it is that good for storing config parts for fvwm because users will hardly find something, since it will be just to much. at least a wiki would be more organized than mailinglist archives ;) ... you can have many categories instead of sorting by thread or date. and then, there is a search function for most wikis. Having them fully maintained ensures higher quality and saves the user time (and nerves :-) this would mean, as i said, a lot of effort and time for a maintainer, while the wiki is maintained by its users itself. RvB (Rene van Bevern) [EMAIL PROTECTED] FVWM IRC Channel at irc.freenode.net #fvwm pgpsgkbrA7jXt.pgp Description: PGP signature
Re: FVWM: Wiki for fvwm?
Felix E. Klee [EMAIL PROTECTED] writes: Hm, other Wikis that I've used word fine (e.g. WikiPedia or the EMACS Wiki). But maybe that really involves some good administration. So, why not try it out? Maybe it works, maybe not. Higher quality? - maybe. Users time and nerves? - probably not. Let's not forget what costs really time and nerves: browsing the mailing list archives and trying to forge things by oneself. Felix (just wondering why there is so much of a discussion trying to prevent someone from contributing something that might come in handy) We talked about that all today on the channel on freenode and decided to just start away and see how it works. Maybe discussion on the channel is more straight forwarded, so we would be happy if you join us there, but naturally that should be also discussed on the list! We made quick and dirty list of thinks we want to see on the wiki: we need: - easy, pastable pre for code snippets and config stuff - anchors - css - search function with regexp (hopefully Perl-like) - subpages - file uploading - possibly images - diffs - diff changes, comment changes, show which user made changes don't need: - colors Webspace can be provided by Rene van Bevern (RvB) ... Hope some people here like our idea and are willing to make the wiki a important part of the fvwm-family! Greetings! Mario -- Windoze not found: (C)heer, (P)arty or (D)ance? -- 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: Wiki for fvwm?
%% Felix E. Klee [EMAIL PROTECTED] writes: fek 4. a method to include menus for CodeWeavers CXOffice and CXPlugin. Ooh, I'd be interested in that. -- --- Paul D. Smith [EMAIL PROTECTED] HASMAT--HA Software Mthds Tools Please remain calm...I may be mad, but I am a professional. --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them. -- 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: Wiki is running - Building up (was: Wiki for fvwm?)
On Tue, Jul 29, 2003 at 10:31:26PM +0200, Mario Domgörgen wrote: We made quick and dirty list of thinks we want to see on the wiki: [...] the list mentioned is completely fulfilled by MoinMoin, a phyton wiki clone. Webspace can be provided by Rene van Bevern (RvB) ... so i did. i put up a configured MoinMoin Wiki on http://rvb.dyndns.org/FvwmWiki with an fvwm css style and a basic front page. the next task is finding a suitable structure to sort the data. don't forget: wiki is teamwork. you are all invited giving ideas on that topic. for now i will base a template table of contents from the category of the FAQ. Maintaining is done by some people from the fvwm freenode channel, because discussion there is faster than on mailinglists. Namely these are: Rene van Bevern (RvB) Stephan Beyer (sbeyer, who is not even on this list) Mario Domgörgen (Kanaldrache) of course others are invited to help us. you could put a link on the fvwm page where it is well visible. bye RvB (Rene van Bevern) [EMAIL PROTECTED] pgpiLX6kKsSdf.pgp Description: PGP signature
