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: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Monday, 31 October 2011 at 5:42, Michael Großer wrote: If you're using Firefox, there's an addon to show the page title in the status bar. Thanks! I will look for it as soon as I have enough time :-) Seems it's not available anymore, so I'll attach it (modified to support Firefox up to version 40). Needs some kind of status bar enabled, e.g. with the status-4-evar addon. titleinstatusbar@nikolakocic.com.xpi Description: application/xpinstall
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Thomas Adam wrote: So put your config somewhere with it still exhibiting the problem for you, and I'll take a look. Hi! I will do this within the next days. I will need a little bit of time to make two easily compareable configs. I also will use this opportunity to point out another bug (FVWM does not update the window title when the new window title contains a unicode character, which always happens when I use bugzilla). Just wait until I'm back... Michael
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Sat, Oct 29, 2011 at 10:31:52PM +0200, Michael Großer wrote: Thomas Adam wrote: So put your config somewhere with it still exhibiting the problem for you, and I'll take a look. Hi! I will do this within the next days. I will need a little bit of time to make two easily compareable configs. I also will use this opportunity to point out another bug (FVWM does not update the window title when the new window title contains a unicode character, which always happens when I use bugzilla). You do not need to point this out, it's been a known bug for a while. -- 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: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Thomas Adam wrote: On Sat, Oct 29, 2011 at 10:31:52PM +0200, Michael Großer wrote: [...] I also will use this opportunity to point out another bug (FVWM does not update the window title when the new window title contains a unicode character, which always happens when I use bugzilla). You do not need to point this out, it's been a known bug for a while. Oh! When will it be fixed then? I'm confronted with this bug up to hundred times every day, because I always have to use my mouse wheel to scroll to the top of bugzilla pages just because the window title doesn't show me the description of the bug that I'm reading or editing. In my first FVWM days, I loaded an additional KDE3 session into an xnest window, but this contraption is not very stable, and I'm not able to use copy and paste between the inside and the outside of xnest, and KDE3 is dead anyway since from Debian Squeeze on a very horrible and totally unacceptable KDE4 is shipped...
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
Thomas Adam wrote: On Sat, Oct 29, 2011 at 11:29:42PM +0200, Michael Großer wrote: Thomas Adam wrote: On Sat, Oct 29, 2011 at 10:31:52PM +0200, Michael Großer wrote: [...] I also will use this opportunity to point out another bug (FVWM does not update the window title when the new window title contains a unicode character, which always happens when I use bugzilla). You do not need to point this out, it's been a known bug for a while. Oh! When will it be fixed then? I'm confronted with this bug up to hundred When I get round to it. Can you also look in to BugOpts TransliterateUtf8? I've had success in OK. One more item on my mental to-do list. But this is one I will be reminded of every day when I use bugzilla...
Re: reusing old configs in new versions [Re: FVWM: Reviewing FVWM]
On Saturday, 29 October 2011 at 23:29, Michael Großer wrote: Oh! When will it be fixed then? I'm confronted with this bug up to hundred times every day, because I always have to use my mouse wheel to scroll to the top of bugzilla pages just because the window title doesn't show me the description of the bug that I'm reading or editing. If you're using Firefox, there's an addon to show the page title in the status bar.
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
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
