Re: .po files of locale zh_TW
Still not accepted in fvwm 2.6.x here are .po files of the locale zh_TW (Traditional Chinese) for fvwm 2.5.12
Re: .po files of locale zh_TW
Hello, On Mon, Apr 18, 2011 at 03:09:14PM +, Wei-Lun Chao wrote: Still not accepted in fvwm 2.6.x here are .po files of the locale zh_TW (Traditional Chinese) for fvwm 2.5.12 Can you provide more context, please? I have no idea what you're talking about here -- and still not accepted implies someone (not I) was aware of this issue in the past. But this is the first I can recall of it. -- Thomas Adam
fvwm-2.6.0 bug(?)
I am running fvwm 2.6.0 on Slackware64 13.1. When it starts up it (apparently) runs fvwm-menu-desktop, which sends out the following complaints: -- WARNING: '/etc/kde/xdg/menus/applications-kmenuedit.menu' does not exist Unknown 'DefaultLayout': 'HASH(0x139b0c0) 0 Merge ARRAY(0x139b228) 0 Merge ARRAY(0x139b2e8) 0 Separator ARRAY(0x139b360) 0 Menuname ARRAY(0x139b408) 0 ' Unknown 'Layout': 'HASH(0x139b4c8) 0 Merge ARRAY(0x139b630) 0 Menuname ARRAY(0x139b6a8) 0 Merge ARRAY(0x13768d8) 0 ' Unknown 'Layout': 'HASH(0x13d9040) 0 Merge ARRAY(0x13d91a8) 0 Filename ARRAY(0x13d9220) 0 Filename ARRAY(0x13dbba8) 0 Separator ARRAY(0x13dbc98) 0 Filename ARRAY(0x13dbd40) 0 Filename ARRAY(0x13dbe30) 0 Filename ARRAY(0x13dbf20) 0 Merge ARRAY(0x13dc058) 0 Separator ARRAY(0x13dc0d0) 0 Menuname ARRAY(0x13dc178) 0 ' DestroyMenu FvwmMenu AddToMenu FvwmMenu KDE Menu Title -- I don't see anything in my configuration which is asking fvwm to call this program. Should I be getting this without asking for it, or am I doing something wrong. (If the latter, my apologies for the noise.) Thanks. Jim
Re: fvwm-2.6.0 bug(?)
On Mon, Apr 18, 2011 at 02:14:38PM -0300, Jim Diamond wrote: I am running fvwm 2.6.0 on Slackware64 13.1. When it starts up it (apparently) runs fvwm-menu-desktop, which sends out the following complaints: -- WARNING: '/etc/kde/xdg/menus/applications-kmenuedit.menu' does not exist Unknown 'DefaultLayout': 'HASH(0x139b0c0) 0 Merge ARRAY(0x139b228) 0 Merge ARRAY(0x139b2e8) 0 Separator ARRAY(0x139b360) 0 Menuname ARRAY(0x139b408) 0 ' Unknown 'Layout': 'HASH(0x139b4c8) 0 Merge ARRAY(0x139b630) 0 Menuname ARRAY(0x139b6a8) 0 Merge ARRAY(0x13768d8) 0 ' Unknown 'Layout': 'HASH(0x13d9040) 0 Merge ARRAY(0x13d91a8) 0 Filename ARRAY(0x13d9220) 0 Filename ARRAY(0x13dbba8) 0 Separator ARRAY(0x13dbc98) 0 Filename ARRAY(0x13dbd40) 0 Filename ARRAY(0x13dbe30) 0 Filename ARRAY(0x13dbf20) 0 Merge ARRAY(0x13dc058) 0 Separator ARRAY(0x13dc0d0) 0 Menuname ARRAY(0x13dc178) 0 ' DestroyMenu FvwmMenu AddToMenu FvwmMenu KDE Menu Title -- I don't see anything in my configuration which is asking fvwm to call this program. Should I be getting this without asking for it, or am I doing something wrong. (If the latter, my apologies for the noise.) It's coming from fvwm-menu-desktop which is called from fvwm.c in liey of no config found, *or* your config doesn't override the builtin menu. I am not too surprised to see the above, but I don't have the environment installed to reproduce it, as that would mean KDE being installed. The error comes from interpret_menu() -- which it will then spit out the above as a last resort. Probably nothing to worry about, it's just this script is perhaps overly chatty. -- 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: fvwm-2.6.0 bug(?)
Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 02:14:38PM -0300, Jim Diamond wrote: I am running fvwm 2.6.0 on Slackware64 13.1. When it starts up it (apparently) runs fvwm-menu-desktop, which sends out the following complaints: -- WARNING: '/etc/kde/xdg/menus/applications-kmenuedit.menu' does not exist Unknown 'DefaultLayout': ' DestroyMenu FvwmMenu AddToMenu FvwmMenu KDE Menu Title -- I don't see anything in my configuration which is asking fvwm to call this program. Should I be getting this without asking for it, or am I doing something wrong. (If the latter, my apologies for the noise.) It's coming from fvwm-menu-desktop which is called from fvwm.c in liey of no config found, *or* your config doesn't override the builtin menu. There's no way to override the creation of the built in menu. There probably should be. Is there a way to defer creation of the menu until it is invoked? I am not too surprised to see the above, but I don't have the environment installed to reproduce it, as that would mean KDE being installed. The error comes from interpret_menu() -- which it will then spit out the above as a last resort. Probably nothing to worry about, it's just this script is perhaps overly chatty. I think it's a bug in the kde config files. We should probably change the menu generation code to be quiet about it unless a debug or verbose flag is on. I can do that if you like...
Re: fvwm-2.6.0 bug(?)
On Mon, Apr 18, 2011 at 01:46:22PM -0400, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 02:14:38PM -0300, Jim Diamond wrote: I am running fvwm 2.6.0 on Slackware64 13.1. When it starts up it (apparently) runs fvwm-menu-desktop, which sends out the following complaints: -- WARNING: '/etc/kde/xdg/menus/applications-kmenuedit.menu' does not exist Unknown 'DefaultLayout': ' DestroyMenu FvwmMenu AddToMenu FvwmMenu KDE Menu Title -- I don't see anything in my configuration which is asking fvwm to call this program. Should I be getting this without asking for it, or am I doing something wrong. (If the latter, my apologies for the noise.) It's coming from fvwm-menu-desktop which is called from fvwm.c in liey of no config found, *or* your config doesn't override the builtin menu. There's no way to override the creation of the built in menu. There probably should be. I meant in terms of recreating FvwmRootMenu, although that's done after the fact by the time the user's config is read in. Is there a way to defer creation of the menu until it is invoked? Yes -- this is what MissingSubMenuFunction is for. I am not too surprised to see the above, but I don't have the environment installed to reproduce it, as that would mean KDE being installed. The error comes from interpret_menu() -- which it will then spit out the above as a last resort. Probably nothing to worry about, it's just this script is perhaps overly chatty. I think it's a bug in the kde config files. We should probably change the menu generation code to be quiet about it unless a debug or verbose flag is on. I can do that if you like... Yes please. Just umm, not another 2.6.2 release just yet though. :) -- 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: .po files of locale zh_TW
2011/4/18 Thomas Adam tho...@fvwm.org: Hello, On Mon, Apr 18, 2011 at 03:09:14PM +, Wei-Lun Chao wrote: Still not accepted in fvwm 2.6.x here are .po files of the locale zh_TW (Traditional Chinese) for fvwm 2.5.12 Can you provide more context, please? I have no idea what you're talking about here -- and still not accepted implies someone (not I) was aware of this issue in the past. But this is the first I can recall of it. The file was sent directly to me and Dominik at a time where I myself at least was very busy, and I didn't notice it was not directed to fvwm-workers until last year, when I replied and asked for the files to be resent to fvwm-workers. /Viktor
Re: fvwm-2.6.0 bug(?)
On Mon, Apr 18, 2011 at 10:10:19PM +0400, Sergey Vlasov wrote: actual user configuration. But there should not be many existing configs which depend on the builtin FvwmMenu definition (this feature There are -- but it won't affect anyone. was added just before the 2.6.0 release), and adding explicit Yes, I know. :P PipeRead 'fvwm-menu-desktop --enable-mini-icons --fvwm-icons' to a custom ~/.fvwm/config will fix the problem (and will be required anyway if some customization of fvwm-menu-desktop options is desired). It's all moot if the default menu is destroyed, which in most cases it is, and if not, well they get the above menu for free. This change looks OK, although I don't thin we should add --enable-mini-icons --fvwm-icons just because; it wasn't there before, and I see no value of adding it in either, as it fixes nothing. -- 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: fvwm-2.6.0 bug(?)
On Mon, Apr 18, 2011 at 07:36:06PM +0100, Thomas Adam wrote: This change looks OK, although I don't thin we should add --enable-mini-icons --fvwm-icons just because; it wasn't there before, and I see no value of adding it in either, as it fixes nothing. My apologies -- I completely misread the change. :) -- 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: fvwm-2.6.0 bug(?)
Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 01:46:22PM -0400, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 02:14:38PM -0300, Jim Diamond wrote: Is there a way to defer creation of the menu until it is invoked? Yes -- this is what MissingSubMenuFunction is for. Aha! No wonder I couldn't find it. IMO, it's not really documented. All the man page has is examples. That keyword is used in place of a menu-name and triggers a special function. Thanks Hope to get some of this done tonight.
Re: fvwm-2.6.0 bug(?)
Hi, On 19 April 2011 02:50, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 01:46:22PM -0400, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 02:14:38PM -0300, Jim Diamond wrote: Is there a way to defer creation of the menu until it is invoked? Yes -- this is what MissingSubMenuFunction is for. Aha! No wonder I couldn't find it. IMO, it's not really documented. All the man page has is examples. I'll add it to my TODO list. :) That keyword is used in place of a menu-name and triggers a special function. Thanks Hope to get some of this done tonight. There's no rush. :) It's not like we're about to release a stable version or anything. :) -- Thomas ADam
Re: fvwm-2.6.0 bug(?)
Thomas Adam tho...@fvwm.org writes: Hi, On 19 April 2011 02:50, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 01:46:22PM -0400, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 02:14:38PM -0300, Jim Diamond wrote: Is there a way to defer creation of the menu until it is invoked? Yes -- this is what MissingSubMenuFunction is for. Aha! No wonder I couldn't find it. IMO, it's not really documented. All the man page has is examples. I'll add it to my TODO list. :) Didn't mean to put this on you, just seeking comments. That keyword is used in place of a menu-name and triggers a special function. Thanks Hope to get some of this done tonight. There's no rush. :) It's not like we're about to release a stable version or anything. :) stable ≠ perfect :) I'm not seeing email on the fix for delayed menu building. I don't think I'll deal with the warning/error message until tomorrow. Getting late.
