FVWM: money donations to the fvwm project
hi, is it possible to supply money, a donation, to the fvwm project? if i did this, where would it go, to what purpose? would i be allowed to say where it went? Harry
Re: FVWM: money donations to the fvwm project
On Mon, Jan 23, 2012 at 08:53:05PM +, Harry portobello wrote: hi, is it possible to supply money, a donation, to the fvwm project? Once upon a time it used to be so, but that was mostly an initiative of Dominik Vogt, as far as I know. Because FVWM is not an organisation and has no structure per-se, there is no one to manage such finances. As such, any one person cannot manage nor benefit from such donations, nor are the developers of FVWM plentiful to make donations useful. We do not have anything pressing or in progress where monetary aid is important or even welcome. If anything, bug-reports and users' gratification is often enough. I would personally also like to think that any one developer of FVWM is in this for the fun and not the personal gain of money through ad-hoc, if well received donations. I know for myself, I do this because I like to. So I thank you for your offer, but would say: No. if i did this, where would it go, to what purpose? would i be allowed to say where it went? -- Thomas Adam -- Deep in my heart I wish I was wrong. But deep in my heart I know I am not. -- Morrissey (Girl Least Likely To -- off of Viva Hate.)
Re: [Solved and learned something] Re: FVWM: How to bring FvwmIdent onto layer 6 [Was: FvwmIdent disappears very often]
Thomas Adam wrote: On Fri, Jan 20, 2012 at 10:42:41PM +0100, Michael Großer wrote: # Bind some decors to the buttons at the left side ButtonStyle 1 - Clear MwmDecorMenu ButtonStyle 3 - Clear MwmDecorStick ButtonStyle 5 - Clear MwmDecorLayer 6 ButtonStyle 7 - Clear MwmDecorLayer 4 ButtonStyle 9 - Clear MwmDecorLayer 2 # Bind some decors to the buttons at the right side ButtonStyle 2 - Clear ButtonStyle 4 - Clear MwmDecorMax ButtonStyle 6 - Clear MwmDecorMin ButtonStyle 8 - Clear MwmDecorShade I made a screenshot to show them in real live. Button 5, 7 and 9 show me the layer of a respective window (and I can change the layer by klicking one of the buttons). Right. Can you provide a more minimal configuration for this including any mouse bindings and style lines affecting how the decor is rendered. I note here you're not using a decor which might explain some of your problems. But again I can't reproduce this. Is this config minimal enough for you? http://www.jumping-blue-turtle.com/fvwm/will_disappear_on_random_date_2012-05-12/8998_bugdemo_002.tar.bz2 I tested it on FVWM version 2.5.26. Press Win+x to get an xterm. Press Win+n to get an nedit window. Press Win+f to get a firefox. Other shortcuts are in 0005_general_shortcuts. At the bottom of the screen, you should find an FvwmIconMan. Rightclick with your mouse on an entry there. An FvwmIdent appears with button 7 pointed out: A continuous line indicates that FvwmIdent is in layer 4, but this is not true, because FvwmIdent is in layer 6. Move your mouse. As soon as another window gets focus, something at FvwmIdent will change: Now, button 5 will be pointed out: A continuous line indicates that FvwmIdent is in layer 6, which indeed is true. The bug is that FvwmIdent does not immediately indicate that it is in layer 6. The file 0001_window_decorations contains the code that draws the buttons to the windows and colorizes the window decorations. I made the second and the third line of 0012_FvwmIdent inactive. Normally, I need them active to fix some problems of FvwmIdent. When they are active, FvwmIdent always indicates the truth (the right layer). If you can reproduce this bug only with an older version of FVWM but not with a current version, then the case should be closed. If a current version also has this bug, then you can do something if you want. You also can wait some weeks until I test it against a current version by myself :-)
Re: FVWM: Why is Debian behind schedule regarding recent FVWM versions so much?
Thomas Adam wrote: On Fri, Jan 13, 2012 at 12:17:29PM +0100, michael.gros...@gmx.de wrote: But, the idea of a distribution like Debian is to get stable software onto the computer by typing apt-get install something. Each exception I have to make erodes the whole idea of a ready-to-use Linux distribution. Use a different distro? No way. Does anybody know why even Sid is behind schedule that much? The maintainer often goes AWOL; this is not news, and anyone who's really wanting to use FVWM via apt-get just build their own .deb file. Either way, go pester Manoj about this, as I have done so many times already, but I care not to discuss such things here as they're off-topic. I see now that it does not make sense to pester Manoj myself. He didn't answer my request too. My decision is for sure now that I will show my readers a way how to download a current FVWM version, compile it and install it on Debian systems. I even will deliberately commit a language inconsistency by describing the FVWM related topics in English (and not in German) and try to encapsulate it a little bit from the rest of my how-tos in order to show German and non-German readers a way how to use Debian Linux *AND* FVWM together. Then, nobody will need Manoj anymore :-)
Re: FVWM: Why is Debian behind schedule regarding recent FVWM versions so much?
Original-Nachricht Datum: Tue, 24 Jan 2012 00:41:03 +0100 (CET) Von: Thomas Funk t.f...@web.de An: Michael Großer michael.gros...@gmx.de, fvwm@fvwm.org Betreff: Aw: Re: FVWM: Why is Debian behind schedule regarding recent FVWM versions so much? Hi Michael, My decision is for sure now that I will show my readers a way how to download a current FVWM version, compile it and install it on Debian systems. You can build a Debian package very easily with the following commands: ./configure --prefix=/usr make deb-inplace This is implemented in Fvwm since ages (thanks to Thomas for that hint ;) ) Thomas -- What is the exact difference between a 'terminal', a 'shell', a 'tty' and a 'console'? A terminal is at the end of an electric wire, a shell is the home of a turtle, tty is a strange abbreviation and a console is a kind of cabinet. -- Gilles Hm. I remember when I did it last time that it was a lg odyssey finding out which libraries were needed, finding the libraries, finding other libraries from which the libraries depend and so on. For newbies, this was definitely not an acceptable way. The reason why I write and publish my own howtos is exactly this: The experts throw one-liners like ./configure --prefix=/usr make deb-inplace around and say how easy all is, and then you sit there and nothing works, because the experts forgot to say that there are concepts like dependencies. Thank you for your hint. I will test this line next time: ./configure --prefix=/usr make deb-inplace But even if this one line will work, I will have to document it, because some kind of knowledge is not easy to find in the Internet. Michael -- michael.gros...@gmx.de 030/76 21 88 28 0177/578 5 578
Re: FVWM: Why is Debian behind schedule regarding recent FVWM versions so much?
Hm. I remember when I did it last time that it was a lg odyssey finding out which libraries were needed, finding the libraries, finding other libraries from which the libraries depend and so on. For newbies, this was definitely not an acceptable way. The reason why I write and publish my own howtos is exactly this: The experts throw one-liners like ./configure --prefix=/usr make deb-inplace around and say how easy all is, and then you sit there and nothing works, because the experts forgot to say that there are concepts like dependencies. Thank you for your hint. I will test this line next time: ./configure --prefix=/usr make deb-inplace But even if this one line will work, I will have to document it, because some kind of knowledge is not easy to find in the Internet. I've been compiling my own fvwm debian packages for some time and here are some additional hints. For dependencies the ones in Manjo's package are somewhat sane (as in they will work unless you care enough to limit some of them, you can install them all wth a single apt-get command) you can just type apt-get build-dep fvwm You may need/want to install build-essential as well. as for using 'make deb-inplace', it makes a .deb file just fine and it should install on your system (Works here for me on debian sid). This is old and outdated and a newer debian/ dir should be used to be more in line with the newer debian specification and I belive thomas did some work on this and has a newer debian/ on his git server, though I never have gotten around to trying it to compile a debian package. The last note is the debian package for some reason (I am still unsure why Manjo did this) has an epoch version and the package you made will not. Because of this epoch version the version in the debian repos 1:2.5.30 is considered greater than the version you compiled 2.6.3 for instance, and if you upgrade/dist-upgrade you system it will install the version from the debian repo effectivally downgrading your fvwm package. To prevent this you need to put the fvwm package on hold echo fvwm hold | dpkg --set-selections For those other fvwm debain users out there I hope this is of some help jaimos
Re: FVWM: Why is Debian behind schedule regarding recent FVWM versions so much?
On Monday, 23 January 2012 at 18:05, Jaimos Skriletz wrote: The last note is the debian package for some reason (I am still unsure why Manjo did this) has an epoch version and the package you made will not. Because of this epoch version the version in the debian repos 1:2.5.30 is considered greater than the version you compiled 2.6.3 for instance, and if you upgrade/dist-upgrade you system it will install the version from the debian repo effectivally downgrading your fvwm package. To prevent this you need to put the fvwm package on hold Looks like a typo in 2005 was the cause: fvwm (2.5.130.CVS.2005.07.19.01-1) unstable; urgency=low fvwm (1:2.5.13-0.CVS.2005.08.08.01-1) unstable; urgency=low So to have apt recognize the 2.5.13 package as larger than 2.5.130, the epoch was necessary. Solution: set the epoch of dpkg scripts in the source distribution to something like 10, then it'll take a while until the repo package overrides the custom one (assuming that someone who compiles a custom package doesn't want it autoupgraded to a repo package at some random point in time).
