Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Fri, Oct 28, 2011 at 10:34:13AM +0200, Michael Großer wrote: > Thomas Adam wrote: > > On Fri, Oct 28, 2011 at 09:50:06AM +0200, Michael Großer wrote: > >> Michelle Konzack wrote: > >> > Hello ro...@cloudcabin.org, > >> >> I have quite a large config with some whistles and bells and maybe a > >> >> couple dirty hacks in it and I use Archlinux (which means bleeding edge, > >> >> constant updates and such), I think the first version I tried was > >> >> 2.5.27, > >> >> and not a single feature was broken with an update. > >> > > >> > I have strted using Fvwm2 in March 1999 and the config works up to NOW. > >> > >> Last year, I came back to fvwm after 10 years and started to learn > >> how to configure it. I started with version 2.5.26 (Debian Lenny). > >> > >> 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". > > > > So you swapped around the Key binding lines after the function definitions? > > This simply just isn't true -- they both work the same. > > > > -- Thomas Adam > > I also couldn't believe this. Maybe, the 2.5.30 has a bug that is fixed > in later releases? No, this won't be true either. > Whatever! I just leave this order now to be able to use all versions > of FVWM, even the buggy ones. > No, it's never just "Whatever!". If you've found a problem, I want to know about it. All I can tell you with absolute certainty is it has nothing to do with you reordering lines in your config. So put your config somewhere with it still exhibiting the problem for you, and I'll take a look. -- Thomas Adam
Re: FVWM: fvwm-menu-desktop again
On Fri, Oct 28, 2011 at 11:32:46AM +0200, Jesús J. Guerrero Botella wrote: > Hello. > > I am having more problems with this script. Using 2.6.3 (and I get the > same with latest CVS) on a non-kde machine now. So, there's no > kde-config (nor kde4-config). Of course, > /etc/xdg/menus/gnome-applications.menu do exist and it is a valid menu > file. This is the verbose output: > > == > $ XDG_MENU_PREFFIX=/etc/xdg/menus/gnome- bin/fvwm-menu-desktop --verbose | > xsel Spell PREFIX correctly and it will work. -- Thomas Adam
Re: FVWM: fvwm-menu-desktop again
Nevermind, there was a typo on my var definition. Good for me. I get nervous all the time about this script for some reason. I should have checked better before spamming the list. Please, just ignore these two mails. Regards. -- Jesús Guerrero Botella
FVWM: fvwm-menu-desktop again
Hello. I am having more problems with this script. Using 2.6.3 (and I get the same with latest CVS) on a non-kde machine now. So, there's no kde-config (nor kde4-config). Of course, /etc/xdg/menus/gnome-applications.menu do exist and it is a valid menu file. This is the verbose output: == $ XDG_MENU_PREFFIX=/etc/xdg/menus/gnome- bin/fvwm-menu-desktop --verbose | xsel DEBUG: foreach fvwm_app. INTERMEDIATE icons to use fvwm_title -> folder.xpm. INTERMEDIATE icons to use fvwm_app -> mini/mini-x.xpm. INTERMEDIATE icons to use fvwm_folder -> folder.xpm. INTERMEDIATE icons to use fvwm_toptitle -> mini-k.xpm. icons to use fvwm_title -> folder.xpm. icons to use fvwm_app -> . icons to use fvwm_folder -> folder.xpm. icons to use fvwm_toptitle -> mini-k.xpm. DEBUG: foreach fvwm_folder. INTERMEDIATE icons to use fvwm_title -> folder.xpm. INTERMEDIATE icons to use fvwm_app -> . INTERMEDIATE icons to use fvwm_folder -> mini/folder.xpm. INTERMEDIATE icons to use fvwm_toptitle -> mini-k.xpm. icons to use fvwm_title -> folder.xpm. icons to use fvwm_app -> . icons to use fvwm_folder -> . icons to use fvwm_toptitle -> mini-k.xpm. DEBUG: foreach fvwm_title. INTERMEDIATE icons to use fvwm_title -> mini/folder.xpm. INTERMEDIATE icons to use fvwm_app -> . INTERMEDIATE icons to use fvwm_folder -> . INTERMEDIATE icons to use fvwm_toptitle -> mini-k.xpm. icons to use fvwm_title -> . icons to use fvwm_app -> . icons to use fvwm_folder -> . icons to use fvwm_toptitle -> mini-k.xpm. DEBUG: foreach fvwm_toptitle. INTERMEDIATE icons to use fvwm_title -> . INTERMEDIATE icons to use fvwm_app -> . INTERMEDIATE icons to use fvwm_folder -> . INTERMEDIATE icons to use fvwm_toptitle -> mini/mini-k.xpm. icons to use fvwm_title -> . icons to use fvwm_app -> . icons to use fvwm_folder -> . icons to use fvwm_toptitle -> . desktop dirs /usr/share/desktop-directories KDE legacy dirs Use of uninitialized value $root_cmd in concatenation (.) or string at bin/fvwm-menu-desktop line 215. DEBUG: root menu is DEBUG: charset is UTF-8. DEBUG: language is es_ES.utf8. DEBUG: root-cmd is . at bin/fvwm-menu-desktop line 215. ERROR: Can't find root menu file. -- Jesús Guerrero Botella
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Thomas Adam wrote: > On Fri, Oct 28, 2011 at 09:50:06AM +0200, Michael Großer wrote: >> Michelle Konzack wrote: >> > Hello ro...@cloudcabin.org, >> >> I have quite a large config with some whistles and bells and maybe a >> >> couple dirty hacks in it and I use Archlinux (which means bleeding edge, >> >> constant updates and such), I think the first version I tried was 2.5.27, >> >> and not a single feature was broken with an update. >> > >> > I have strted using Fvwm2 in March 1999 and the config works up to NOW. >> >> Last year, I came back to fvwm after 10 years and started to learn >> how to configure it. I started with version 2.5.26 (Debian Lenny). >> >> 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". > > So you swapped around the Key binding lines after the function definitions? > This simply just isn't true -- they both work the same. > > -- Thomas Adam I also couldn't believe this. Maybe, the 2.5.30 has a bug that is fixed in later releases? Whatever! I just leave this order now to be able to use all versions of FVWM, even the buggy ones.
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Fri, Oct 28, 2011 at 09:50:06AM +0200, Michael Großer wrote: > Michelle Konzack wrote: > > Hello ro...@cloudcabin.org, > >> I have quite a large config with some whistles and bells and maybe a > >> couple dirty hacks in it and I use Archlinux (which means bleeding edge, > >> constant updates and such), I think the first version I tried was 2.5.27, > >> and not a single feature was broken with an update. > > > > I have strted using Fvwm2 in March 1999 and the config works up to NOW. > > Last year, I came back to fvwm after 10 years and started to learn > how to configure it. I started with version 2.5.26 (Debian Lenny). > > 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". So you swapped around the Key binding lines after the function definitions? This simply just isn't true -- they both work the same. -- Thomas Adam
reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Michelle Konzack wrote: > Hello ro...@cloudcabin.org, >> I have quite a large config with some whistles and bells and maybe a >> couple dirty hacks in it and I use Archlinux (which means bleeding edge, >> constant updates and such), I think the first version I tried was 2.5.27, >> and not a single feature was broken with an update. > > I have strted using Fvwm2 in March 1999 and the config works up to NOW. Last year, I came back to fvwm after 10 years and started to learn how to configure it. I started with version 2.5.26 (Debian Lenny). 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
