solution of an old riddle [Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]]
Michael Großer wrote: > Eleven days ago, I migrated an existing (still dirty, but extremly powerful) > configuration to a new Debian Squeeze plattform with "FVWM 2.5.30". > > I had to change the order of some code to make my config work > with "FVWM 2.5.30". > > > > This code only works with "FVWM 2.5.26" >> # set some layers >> Key Plus WTSF123456789 S4 Function "raise-to-top" >> Key Numbersign WTSF123456789 S4 Function "set-to-put" >> Key Minus WTSF123456789 S4 Function "lower-to-bottom" >> >> # define some layer functions >> AddToFunc lower-to-bottom >> + I Layer 0 2 >> + I Lower >> + I Stick >> + I Stick >> >> AddToFunc set-to-put >> + I Layer 0 4 >> + I Stick >> + I Stick >> + I Raise >> >> AddToFunc raise-to-top >> + I Layer 0 6 >> + I Stick >> + I Stick >> + I Raise > > > > This is the way, the code has to look like if I want to > have it work with "FVWM 2.5.30" too: >> # define some layer functions >> AddToFunc lower-to-bottom >> + I Layer 0 2 >> + I Lower >> + I Stick >> + I Stick >> >> AddToFunc set-to-put >> + I Layer 0 4 >> + I Stick >> + I Stick >> + I Raise >> >> AddToFunc raise-to-top >> + I Layer 0 6 >> + I Stick >> + I Stick >> + I Raise >> >> # set some layers >> Key Plus WTSF123456789 S4 Function "raise-to-top" >> Key Numbersign WTSF123456789 S4 Function "set-to-put" >> Key Minus WTSF123456789 S4 Function "lower-to-bottom" > > > > The change is minimal, but not always, you should assume > to have enough luck to take over an FVWM config utterly > untouched. > > > > Just my two cents :-) > Michael I posted this on 2011-10-28 09:50. Now, I know what the problem was. During the last months, I had finally the time to install and configure a Debian Squeeze a very clean way, carefully scrutinizing every little step. Probably, I have the cleanest Debian Squeeze installation in the world now :-P I live in Germany, and my very clean Debian is running with a German keyboard layout. It has a German keyboard layout both in console mode (text mode, thus F1 ... F6) and in X.Org mode. My kind of dirty prototype in the year 2011 had a little misconfiguration with a German keyboard layout in X.Org mode and an English keyboard layout in console mode. So, when I typed in console mode a "y", I got a "z", and when I typed "z", I got a "y". When FVWM started for the first time after reboot, I had a German keyboard layout, but somehow, the keys "Plus", "Numbersign" and "Minus" could not be recognized by FVWM. When I restarted FVWM, it recognized them correctly. The solution of this riddle is that X.Org somehow got confused with the English keyboard layout in console mode. So, this problem was a complex issue, which I solved by taking much time to setup a very clean Linux, where I carefully ensured that I truly understand every installation step. Just wanted to post the real cause of this. - Michael -
Re: FVWM: Debian Unstable now has FVWM 2.6.5
will most likely build it in my cowbuilder setup for squeeze, lenny, wheezy and see what happens... if all goes well, it might end up on backports.debian.org. cheers, christine On 01/23/2013 07:50 PM, Jaimos F Skriletz wrote: > On 01/23/2013 11:29 AM, E Frank Ball III wrote: >> On Wed, Jan 23, 2013 at 01:53:32PM +, Thomas Adam wrote: >> > Hi, >> > >> > Just a quick note to all the Debian users who've long since been >> waiting for >> > Debian to update their version of FVWM, this has finally happened. >> > >> > I've been helping out the new maintainer and talking to the DD who's >> > sponsering the maintainer, and we've finally got FVWM 2.6.5 >> released to >> > Debian Unstable. >> > >> > Someone may well backport this; I don't know. >> >> >> Thank you, thats great. Any chance it will make it into Wheezy? > Wheezy is frozen so most likely not. > > jaimos >
Re: FVWM: Debian Unstable now has FVWM 2.6.5
You will run into the problem that MenuFvwmRoot does not contain "D. Debian Menu" anymore like it used to be in Debian Lenny with FVWM 2.5.26. Squeeze with FVWM 2.5.30 generates such a Debian menu, but only then when the 3876 lines of code of "/etc/X11/fvwm/system.fvwm2rc" are included, with a lot annoying stuff that I don't want to have in my config. If you want, you can solve this problem. If not, I will open a new thread in summer 2013 to address this problem and will work without Debian menu until then. - Michael - pebcak wrote: > will most likely build it in my cowbuilder setup for squeeze, lenny, > wheezy and see what happens... if all goes well, it might end up on > backports.debian.org. > > > cheers, > christine > > On 01/23/2013 07:50 PM, Jaimos F Skriletz wrote: >> On 01/23/2013 11:29 AM, E Frank Ball III wrote: >>> On Wed, Jan 23, 2013 at 01:53:32PM +, Thomas Adam wrote: >>> > Hi, >>> > >>> > Just a quick note to all the Debian users who've long since been >>> waiting for >>> > Debian to update their version of FVWM, this has finally happened. >>> > >>> > I've been helping out the new maintainer and talking to the DD who's >>> > sponsering the maintainer, and we've finally got FVWM 2.6.5 >>> released to >>> > Debian Unstable. >>> > >>> > Someone may well backport this; I don't know. >>> >>> >>> Thank you, thats great. Any chance it will make it into Wheezy? >> Wheezy is frozen so most likely not. >> >> jaimos >> > >
Re: FVWM: Debian Unstable now has FVWM 2.6.5
On Sun, Jan 27, 2013 at 10:53:15AM +0100, Michael Großer wrote: > You will run into the problem that MenuFvwmRoot > does not contain "D. Debian Menu" anymore like > it used to be in Debian Lenny with FVWM 2.5.26. > > Squeeze with FVWM 2.5.30 generates such a Debian > menu, but only then when the 3876 lines of code > of "/etc/X11/fvwm/system.fvwm2rc" are included, > with a lot annoying stuff that I don't want to > have in my config. Just read /etc/X11/fvwm/menudefs.hook into your config. Claude
Re: FVWM: Debian Unstable now has FVWM 2.6.5
Original-Nachricht > Datum: Sun, 27 Jan 2013 09:13:15 -0600 > Von: Claude Rubinson > An: fvwm > Betreff: Re: FVWM: Debian Unstable now has FVWM 2.6.5 > On Sun, Jan 27, 2013 at 10:53:15AM +0100, Michael Großer wrote: > > You will run into the problem that MenuFvwmRoot > > does not contain "D. Debian Menu" anymore like > > it used to be in Debian Lenny with FVWM 2.5.26. > > > > Squeeze with FVWM 2.5.30 generates such a Debian > > menu, but only then when the 3876 lines of code > > of "/etc/X11/fvwm/system.fvwm2rc" are included, > > with a lot of annoying stuff that I don't want to > > have in my config. > > Just read /etc/X11/fvwm/menudefs.hook into your config. > > Claude I tried it. With no luck. It was one of my obvious ideas. Maybe, I did something wrong, but in my case, it didn't work. Perhaps, I should try to include "/etc/X11/fvwm/menudefs.hook" in FVWM "2.6.5", if it contains such a file. I tested both "2.5.30" and "2.6.5" yesterday, bulldozing my two Debian partitions after each test with a fresh and chaste version of Squeeze, but I did different tests with "2.5.30" and "2.6.5". I made more tests with "2.5.30", because it was more Debian affine than "fvwm-2.6.5.tar.bz2". - Michael -
Re: FVWM: Debian Unstable now has FVWM 2.6.5
On Sun, Jan 27, 2013 at 08:49:14PM +0100, michael.gros...@gmx.de wrote: > > > On Sun, Jan 27, 2013 at 10:53:15AM +0100, Michael Großer wrote: > > > You will run into the problem that MenuFvwmRoot > > > does not contain "D. Debian Menu" anymore like > > > it used to be in Debian Lenny with FVWM 2.5.26. > > > > > > > Just read /etc/X11/fvwm/menudefs.hook into your config. > > > > Claude > > I tried it. With no luck. It was one of my obvious ideas. > Maybe, I did something wrong, but in my case, it didn't work. > Perhaps, I should try to include "/etc/X11/fvwm/menudefs.hook" > in FVWM "2.6.5", if it contains such a file. I tested both > "2.5.30" and "2.6.5" yesterday, bulldozing my two Debian > partitions after each test with a fresh and chaste version > of Squeeze, but I did different tests with "2.5.30" and > "2.6.5". I made more tests with "2.5.30", because it was > more Debian affine than "fvwm-2.6.5.tar.bz2". > the menu is created with a debian menu-methods and the output is the /etc/X11/fvwm/menudefs.hook by default on the debian package (I just checked this myself). 'Read /etc/X11/fvwm/menudefs.hook' will just read the debian menu but not add it to your root menu. So that file only contains the info generated by the debian 'menu' package. you should less that file, but the menu name is /Debian and you can get the menu by doing 'popup /Debian' and there is the menu. You can add that to your root menu to get access to the menu from there. Note you will have to 'Read /etc/X11/fvwm/menudefs.hook' each time you add/remove packages to change the menu you will need to reread that file to get the updated menu. But this method ensures that you only add the menu to your current config and not all fo the other stuff from the default debian config file. jaimos
Re: FVWM: Debian Unstable now has FVWM 2.6.5
Jaimos Skriletz wrote: > On Sun, Jan 27, 2013 at 08:49:14PM +0100, michael.gros...@gmx.de wrote: >> >> > On Sun, Jan 27, 2013 at 10:53:15AM +0100, Michael Großer wrote: >> > > You will run into the problem that MenuFvwmRoot >> > > does not contain "D. Debian Menu" anymore like >> > > it used to be in Debian Lenny with FVWM 2.5.26. >> > > >> > >> > Just read /etc/X11/fvwm/menudefs.hook into your config. >> > >> > Claude >> >> I tried it. With no luck. It was one of my obvious ideas. >> Maybe, I did something wrong, but in my case, it didn't work. >> Perhaps, I should try to include "/etc/X11/fvwm/menudefs.hook" >> in FVWM "2.6.5", if it contains such a file. I tested both >> "2.5.30" and "2.6.5" yesterday, bulldozing my two Debian >> partitions after each test with a fresh and chaste version >> of Squeeze, but I did different tests with "2.5.30" and >> "2.6.5". I made more tests with "2.5.30", because it was >> more Debian affine than "fvwm-2.6.5.tar.bz2". >> > > the menu is created with a debian menu-methods and the output is the > /etc/X11/fvwm/menudefs.hook by default on the debian package (I just checked > this myself). > > 'Read /etc/X11/fvwm/menudefs.hook' will just read the debian menu but not add > it to your root menu. So that file only contains the info generated by the > debian 'menu' package. > > you should less that file, but the menu name is /Debian and you can get the > menu by doing 'popup /Debian' and there is the menu. You can add that to your > root menu to get access to the menu from there. > > Note you will have to 'Read /etc/X11/fvwm/menudefs.hook' each time you > add/remove packages to change the menu you will need to reread that file to > get the updated menu. But this method ensures that you only add the menu to > your current config and not all fo the other stuff from the default debian > config file. > > jaimos > > Hi! I can give it a try during the next 6 months. 'popup /Debian' could be an approach that I should indeed pursue. As usual, I will report about my progress when it is time. What do you mean with "you should less that file"? Using the "less" command to do something with that file? And if so, what? > and not all fo the other stuff from > the default debian config file. Yeah, I know. I only need the Debian menu. The other stuff is of no interest. It just interferes with my own config. It could be a good idea to transform a future version of "/etc/X11/fvwm/system.fvwm2rc" into a 2, 3, 4, ... or 9 liner, which includes other files to add features to the default config. One 'read' command reads in menus, one 'read' command reads in a pager, one some window decorations, one a clock, and the user could set a "#" character before each 'read' command whose feature he/she does not like. This could be a very convenient modular approach for picky users like me ;-) - Michael -
Re: FVWM: Debian Unstable now has FVWM 2.6.5
> > > > the menu is created with a debian menu-methods and the output is the > > /etc/X11/fvwm/menudefs.hook by default on the debian package (I just > > checked this myself). > > > > 'Read /etc/X11/fvwm/menudefs.hook' will just read the debian menu but not > > add it to your root menu. So that file only contains the info generated by > > the debian 'menu' package. > > > > you should less that file, but the menu name is /Debian and you can get the > > menu by doing 'popup /Debian' and there is the menu. You can add that to > > your root menu to get access to the menu from there. > > > > Note you will have to 'Read /etc/X11/fvwm/menudefs.hook' each time you > > add/remove packages to change the menu you will need to reread that file to > > get the updated menu. But this method ensures that you only add the menu to > > your current config and not all fo the other stuff from the default debian > > config file. > > > > I can give it a try during the next 6 months. 'popup /Debian' could be > an approach that I should indeed pursue. As usual, I will report > about my progress when it is time. What do you mean with > "you should less that file"? Using the "less" command to do > something with that file? And if so, what? > I mean take a look at what is inside the file. You will see it is nothing more than Menu Definitions for fvwm and the main thing is it tells you the Menu Names so you can refence them in your own config. As I said all you need to do to get the debian menu is 1) Read /etc/X11/fvwm/menudefs.hook That will pull in all the menu defintions, then you need to configure your config to put the menu where you want it once you decide where you want it (submenu, key binding, etc) you can then open the menu with 2) 'Popup /Debian' or 'Menu /Debian' That is all you need to do to get access to the debian menu. You can use FvwmConsole to play with things, but just add it as a submenu to your root menu in your config file and you have the menu. jaimos
Re: FVWM: Debian Unstable now has FVWM 2.6.5
Jaimos Skriletz wrote: >> > >> > the menu is created with a debian menu-methods and the output is the >> > /etc/X11/fvwm/menudefs.hook by default on the debian package (I just >> > checked this myself). >> > >> > 'Read /etc/X11/fvwm/menudefs.hook' will just read the debian menu but not >> > add it to your root menu. So that file only contains the info generated by >> > the debian 'menu' package. >> > >> > you should less that file, but the menu name is /Debian and you can get >> > the menu by doing 'popup /Debian' and there is the menu. You can add that >> > to your root menu to get access to the menu from there. >> > >> > Note you will have to 'Read /etc/X11/fvwm/menudefs.hook' each time you >> > add/remove packages to change the menu you will need to reread that file >> > to get the updated menu. But this method ensures that you only add the >> > menu to your current config and not all fo the other stuff from the >> > default debian config file. >> > >> >> I can give it a try during the next 6 months. 'popup /Debian' could be >> an approach that I should indeed pursue. As usual, I will report >> about my progress when it is time. What do you mean with >> "you should less that file"? Using the "less" command to do >> something with that file? And if so, what? >> > > I mean take a look at what is inside the file. You will see it is nothing > more than Menu Definitions for fvwm and the main thing is it tells you the > Menu Names so you can refence them in your own config. > > As I said all you need to do to get the debian menu is > > 1) Read /etc/X11/fvwm/menudefs.hook > > That will pull in all the menu defintions, then you need to configure your > config to put the menu where you want it > > once you decide where you want it (submenu, key binding, etc) you can then > open the menu with > > 2) 'Popup /Debian' or 'Menu /Debian' > > That is all you need to do to get access to the debian menu. You can use > FvwmConsole to play with things, but just add it as a submenu to your root > menu in your config file and you have the menu. > > jaimos > Sounds very easy now. Thank you. Yet another topic solved for today (at least in theory). :-) *logoff* (it's night in Berlin now) - Michael -
Re: FVWM: why 2 archives for this list?
On Sat, Jan 26, 2013 at 11:23:57AM +0100, Pierre Frenkiel wrote: > hi, > I discovered that there are 2 archives for this list: > >http://www.mail-archive.com/fvwm@fvwm.org/maillist.html > >http://www.mail-archive.com/fvwm@lists.math.uh.edu/ > > the 1st one shows all posts, but in the 2nd one, some posts > are missing. Unfortunatley, the link in http://www.fvwm.org/ leads > to the 2nd one. > > Can anybody explain that? It seems the listmaster is no longer operational. the message I sent to listmas...@fvwm.org on: Date: Thu, 8 Nov 2012 05:58:55 +1300 with subject: FVWM: missing list headers [List CC'd in case anyone else interested.] Hi, I noticed in the headers of a typical post on the fvwm mailing list, a strange thing. There is only the "List-Id:" header¹ missing are the typical: List-Post: List-Help: List-Subscribe: List-Unsubscribe: headers found on other mailing lists which have them. ¹ In fact, it is spelled "List-ID:", which is not even the normal spelling. This could be a clue as to why it is not implemented in the usual manner. was returned with no such address as listmas...@fvwm.org! Also there is no sign of it in the archives!! (maybe because fvwm@fvwm.org was only CC'd?) -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X
