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
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: Debian Unstable now has FVWM 2.6.5
Vincent W. Chen wrote: On Wed, Jan 23, 2013 at 5:53 AM, Thomas Adam tho...@fvwm.org 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. Enjoy. -- Thomas Adam As the currently maintainer, I'd like to ask those who have the time to test out the new package and file bugs at the Debian bug tracker if possible. I tried to keep most of the files in the same places, despite the fairly big changes made. I'd also like to hear from those who upgrade from the old 2.5.30 package whether there's any (new) problems introduced. My thanks goes to John Paul Adrian Glaubitz for sponsoring the package and Thomas Adam for answering the questions I've had. Regards, Vincent Chen Thank you very much for bringing FVWM and Debian together. Both worlds are great and just belong together. - Michael -
Re: FVWM: Debian Unstable now has FVWM 2.6.5
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. Enjoy. -- Thomas Adam Yay! Good news! But anyway, I downloaded FVWM 2.6.5 in July 2012 for my Squeeze installations und plan to use this instead of the built-in FVWM version. - Michael -
Re: FVWM: Debian Unstable now has FVWM 2.6.5
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 Wed, Jan 23, 2013 at 5:53 AM, Thomas Adam tho...@fvwm.org 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. Enjoy. -- Thomas Adam As the currently maintainer, I'd like to ask those who have the time to test out the new package and file bugs at the Debian bug tracker if possible. I tried to keep most of the files in the same places, despite the fairly big changes made. I'd also like to hear from those who upgrade from the old 2.5.30 package whether there's any (new) problems introduced. My thanks goes to John Paul Adrian Glaubitz for sponsoring the package and Thomas Adam for answering the questions I've had. Regards, Vincent Chen
