Bug in PlaceAgain
I think I found a bug. I used the following command to arrange icons (taken from the man-page): All (CurrentPage Iconic) PlaceAgain Icon I first iconified 3 windows (have IconFill left bottom set), then I moved the 2 rightmost icons from their positions. Then a applyied the above command. Now the labels of the 2 moved icons moved back to their original positions but the the pixmaps stayed at the same positions. I use a CVS version from Nov 1. //Marcus -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: M_NEW_PAGE changes
On 14 Nov 2002 19:36:59 -0500, Peter McAlpine wrote: On Thu, Nov 14, 2002 at 05:50:56AM +, Mikhael Goikhman wrote: --snip-- vp_width (viewport size in pixels; is page_width a better name?) vp_height total_pages_x (DesktopSize; is desktop_size_x a better name?) total_pages_y --snip-- Any comments before I do this. yes, aren't there lots of possible desktops... because I can set my viewport to look at anywhere I want within my desktop (ex- overlooking two pages). I don't think that it's very consistent with the other information being sent with M_NEW_PAGE. I could recieve: vp_width/height == probably screen resolution vp_x/y COULD == (123,321)... in which case: total_pages_x/y == nothing useful what-so-ever. total_pages_x/y may be not useful for FvwmWindowLister, but useful for FvwmPager. If you ask me: M_NEW_PAGE should contain ONLY vp_x/y M_CONFIG_INFO should contain vp_width/height, and either max_possible_x/y OR DesktopSize (which I think it already does). Currently when DesktopSize command is issued _or_ a page is switched a single M_NEW_PAGE is sent carrying all changes. I don't want to change this, because it seems to be convenient for all modules, not just a pager. Of course, a more static info (that is mostly not changed) may be moved to M_CONFIG_INFO, but M_NEW_PAGE is sent rarely, so it is not very important. This may be done later when all packets are redesigned, I don't like, for example, that M_CONFIG_INFO unites module configuration lines and global constants instead of having 2 different packets. I don't like M_NEW_DESK. As I said, if you will use the PageInfo tracker, you will not need to know whether it internally listens to M_NEW_PAGE, M_NEW_DESK or M_CONFIG_INFO. It seems a little like fvwm sits on the fence regarding whether consider pages as something that can overlap or not. I would say that a viewport could have any possible top-left x/y... and that pages are viewports that do not overlap each other. I use this terminology, viewport is something more general than a page. Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * libstroke compile fixes.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/11/15 03:17:05 Modified files: . : ChangeLog libs : Bindings.c Log message: * libstroke compile fixes. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: compiler warning/bug in FvwmScript/script.y
On Thu, Nov 14, 2002 at 06:50:47PM -0500, Paul Smith wrote: %% Cameron Simpson [EMAIL PROTECTED] writes: | Sorry, I somehow missed that paragraph. I just can't operate info | :-/ cs You may want my man script, which presents info as one of the cs choices for manual pages. More to the point, it parses info files cs and turns them into a single flat text document, which of course cs you browse with your pager as with ordinary manual entries. Yes, please! That's exactly what I need! Info is quite accessible if you spend a few minutes learning the command set--there are only about 10 keys :). I have spent five years and can not get the hang of it. In particular, the s (search) and i (index lookup) are critically important to know. Once you know these you can do more with Info that you can do with either man pages or HTML. I really don't want to rant about the interface of info here. Let it suffice to say that I absolutely *hate* hierarchical documents. And info operates a bit like vi, a bit like lynx and a bit like emacs, but not quite. That totally confuses me. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Problems building snap-20021114
S. Anderson wrote: Bindings.c: In function `__compare_binding': Bindings.c:500: parse error before `)' Bindings.c:505: warning: control reaches end of non-void function Bindings.c: In function `MatchBindingExactly': Bindings.c:585: parse error before `)' Bindings.c:590: warning: control reaches end of non-void function make[2]: *** [Bindings.o] Error 1 make[2]: Leaving directory `/home/sa/src/fvwm/libs' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/sa/src/fvwm' make: *** [all-recursive-am] Error 2 if I comment out the if statments at line 500 and 585 it compiles fine. also it works without modifications on another system with libstroke. On my new redhat 8.0 system I got exactly the same errors (from current cvs) until I installed the libstroke package from tarball source, then it compiles fine! I suspect there's only a problem if you don't have libstroke. Alex -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS olicha: * Fixed update of the RootTransparent colorset in fvwm
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: olicha 02/11/15 03:38:34 Modified files: . : ChangeLog fvwm : builtins.c builtins.h colorset.c modules: ChangeLog modules/FvwmForm: FvwmForm.c Log message: * Fixed update of the RootTransparent colorset in fvwm * Fixed colorset update in Form -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Idea: Improved Window List Menu
On 12 Nov 2002 21:22:21 -0500, Richard Lister wrote: Mikhael Goikhman [EMAIL PROTECTED] wrote on Sat, 9 Nov 2002 09:44:44 +: I will also reformat it to be more like FvwmPerl. Fine. At least here I guessed your answer correctly. :) I just downloaded the cvs snapshot and found you switched to 8-space tab indentation, which was the worst thing I could have imagined :-) Ah well, I suppose indentation styles are a bit of a religious war ... This is not really correct. I don't use 8-spaces, I use one tab. Unlike our C code that requires TAB to be 8 spaces, our perl code is properly structured to allow any TAB size. Use 4 spaces for TAB if you like this, I use 3 or 8. Just please remember to write a properly structured code (no spaces for indentation, no tabs in the middle of line) not to break this TAB size freedom. I know, it is difficult with emacs... Ok, I did a lot of small changes, every change has its reason, take a look. I think you broke the drawminiicon option, but I don't know this idiom: $foo = 0 + !!$1; It only veryfies that $foo ends up to be a number (you compare this with numbers later, right?). But I forgot this is not a boolean (may be 2 as well). I will fix this. Otherwise, I like all the changes you made. The module still misses some configurability like sorting, automatical grouping, submenus, configurable format, class/resource/name resolution). But it is a good start to test future trackers. I've added title/icon/class/resource matching with a syntax like: *FvwmWindowLister: Show resource = Galeon|Navigator|mozilla-bin You can get the new version at: http://cns.georgetown.edu/~ric/software/fvwm/FvwmWindowLister I even added emacs mode settings for your indentation style :-) I don't think these are the right settings, they insert 4 spaces. In fact, I think the only way to configure emacs to do anything useful is to disable auto-indentation and insert real tabs on tab press. Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Problems building snap-20021114
On Thu, Nov 14, 2002 at 08:32:16PM -0700, S. Anderson wrote: On Thu, Nov 14, 2002 at 02:05:48PM +0100, Dominik Vogt wrote: On Thu, Nov 14, 2002 at 06:32:58AM -0600, Jason L Tibbitts III wrote: /home/tibbs/fvwm/fvwm/session.c:232: the use of `tempnam' is dangerous, better use `mkstemp' events.o: In function `__handle_key_event': /home/tibbs/fvwm/fvwm/events.c:1960: undefined reference to `CheckTwoBindings' /home/tibbs/fvwm/fvwm/events.c:1966: undefined reference to `MyXGrabKey' /home/tibbs/fvwm/fvwm/events.c:1976: undefined reference to `CheckTwoBindings' /home/tibbs/fvwm/fvwm/events.c:2000: undefined reference to `MyXUngrabKey' bindings.o: In function `activate_binding': /home/tibbs/fvwm/fvwm/bindings.c:113: undefined reference to `MyXUngrabKey' collect2: ld returned 1 exit status That works in CVS. I guess that tarball was built while I was checking in my changes. I just checked out fvwm-cvs at Thu Nov 14 20:19:49 MST 2002 and it dies here: Bindings.c: In function `__compare_binding': Bindings.c:500: parse error before `)' Bindings.c:505: warning: control reaches end of non-void function Bindings.c: In function `MatchBindingExactly': Bindings.c:585: parse error before `)' Bindings.c:590: warning: control reaches end of non-void function Fixed. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS migo: * FvwmWindowLister: improvements by Richard Lister with minor changes
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo02/11/15 04:27:19 Modified files: modules: ChangeLog modules/FvwmWindowLister: FvwmWindowLister.in FvwmWindowLister.1 Log message: * FvwmWindowLister: improvements by Richard Lister with minor changes _ new options ItemFormat and Function, changed Show/DontShow -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS olicha: * New MinHeight option to TitleStyle
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: olicha 02/11/15 04:46:24 Modified files: . : ChangeLog NEWS fvwm : builtins.c fvwm.1.in geometry.c screen.h libs : Bindings.c Log message: * New MinHeight option to TitleStyle * compile fixes if STROKE -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Shaping/Joining within fvwm
On 15 Nov 2002 10:34:57 +0100, Olivier Chapuis wrote: On Tue, Nov 12, 2002 at 02:44:15PM -0800, Nadim Shaikli wrote: Hi Guys, sorry to pick on the both of you, but since you championed the inclusion of Bidi (fribidi) into fvwm I thought I'd approach ya first. As promised (awhile back), I've finally included shaping/joining code to fvwm (needed for most Bidi languages such as Arabic, Farsi and all of the Syriacs). Without this code, those language are simply not usable and so I'm trying to remedy that issue. Here is my dilemma, I'm including a patch which works on the simple strings (1, 2 words in titles), but seems to fail on more complex ones without any indicators to why. I'm unable to reproduce those problems without running fvwm (ie. I can't get the code to fail outside of its inclusion into fvwm). I'm also unfamiliar with Xnest and how to go about setting that whole thing up, etc. Which leads me to my humble request. As noted I'm including the patch against CVS snapshot 2002 (and fribidi-0.10.4) and I'm also including a simple xterm call with an Arabic/utf-8 title. If you were to chmod 777 that xterm call and invoke it, fvwm fails and core dumps - the traceback doesn't really reveal much to me (as I'm not too familiar with the fvwm code). So I'm asking for help. Mikhael, do you have the time to add the patch? I will try. Hopefully it does not require fribidi detection changes. If it core dumps on me as reported above, I will #ifdef it. Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: CVS olicha: * New MinHeight option to TitleStyle
On Fri, Nov 15, 2002 at 04:46:24AM -0600, fvwm-workers wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: olicha 02/11/15 04:46:24 Modified files: . : ChangeLog NEWS fvwm : builtins.c fvwm.1.in geometry.c screen.h libs : Bindings.c Log message: * New MinHeight option to TitleStyle What exactly is the difference to TitleHeight? I thought that it works exactly like what I expect from MinHeight. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Global key bindings fix (with unwanted Next/Prev interaction).
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/11/15 05:15:03 Modified files: . : ChangeLog fvwm : events.c libs : Bindings.h Log message: * Global key bindings fix (with unwanted Next/Prev interaction). -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: CVS olicha: * New MinHeight option to TitleStyle
On 15 Nov 2002 12:12:41 +0100, Dominik Vogt wrote: Log message: * New MinHeight option to TitleStyle What exactly is the difference to TitleHeight? I thought that it works exactly like what I expect from MinHeight. Try it, Height dictates the title height. I suppose MinHeight does not dictate. TitleStyle Height 10 Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Added description of Icon option for PlaceAgain command.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/11/15 06:27:07 Modified files: . : ChangeLog fvwm : fvwm.1.in modules/FvwmTheme: FvwmTheme.1 Log message: * Added description of Icon option for PlaceAgain command. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: CVS olicha: * New MinHeight option to TitleStyle
On Fri, Nov 15, 2002 at 12:12:41PM +0100, Dominik Vogt wrote: On Fri, Nov 15, 2002 at 04:46:24AM -0600, fvwm-workers wrote: CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: olicha 02/11/15 04:46:24 Modified files: . : ChangeLog NEWS fvwm : builtins.c fvwm.1.in geometry.c screen.h libs : Bindings.c Log message: * New MinHeight option to TitleStyle What exactly is the difference to TitleHeight? I thought that it works exactly like what I expect from MinHeight. As explained Mikhael the MinHeight does not dictate the height of the title bar's. Rational: if you use XxX Pixmap buttons you can set MinHeight to X+something to be sure that your buttons will be not truncated with any font. If you use Height X+something you may have pbs with your title with big font. Olivier -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
menu - paint triangles in the same color as the foreground color
as shown in the screen shot (22 kB, fvwm 2.5.4) below... http://www103.pair.com/parv/tmp/shot-fvwm-2.5.4-menu.png ...triangles are painted either in Background or HilightBack colors, not in Foreground or ActiveFore. following is what produced the menu style... MenuStyle * TrianglesSolid MenuStyle * Foreground white, Background red4, Greyed rgb:f0/0/0 MenuStyle * ActiveFore black, HilightBack grey75 MenuStyle * MenuFace HGradient 512 5 rgb:60/0/0 20 rgb:80/0/0 40 rgb:a0/0/0 20 rgb:80/0/0 10 rgb:60/0/0 10 black MenuStyle * Hilight3DThickness -2 ...i had to use gradient otherwise red (triangle) on red (background) is rather hard to see. could it be possible either to paint the triangles w/ the Foreground ActiveFore colors as appropriate, or to provide means to specify color(s) for triangle? otherwise, indication of a sub menu is easily missed. below is the screen shot (52 kB, fvwm 2.4.4) showing triangles painted in foreground colors... http://www103.pair.com/parv/comp/graphic.comp/shot-fvwm2-4-4-colors.png ...and from configuration file... http://www103.pair.com/parv/comp/unix/cf/fvwm/fvwm-2.cf--old ...menu style is similar to above... MenuStyle * Foreground white, Background red4 MenuStyle * ActiveFore black, HilightBack white, Greyed red MenuStyle * TrianglesSolid, Hilight3DThick - parv -- -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Idea: Improved Window List Menu
Mikhael Goikhman [EMAIL PROTECTED] wrote on Fri, 15 Nov 2002 09:45:20 +: This is not really correct. I don't use 8-spaces, I use one tab. Unlike our C code that requires TAB to be 8 spaces, our perl code is properly structured to allow any TAB size. Use 4 spaces for TAB if you like this, I use 3 or 8. Just please remember to write a properly structured code (no spaces for indentation, no tabs in the middle of line) not to break this TAB size freedom. I know, it is difficult with emacs... OK, I think I understand what you mean. Use one tab for indentation, then the programmer can choose to have their editor display tabs as equivalent to whatever number of spaces they prefer. I agree this is good and will switch to using this. I think it ought to be straightforward with emacs once I figure it out. It only veryfies that $foo ends up to be a number (you compare this with numbers later, right?). But I forgot this is not a boolean (may be 2 as well). I will fix this. Don't worry, that option has gone away, replaced by the choice of %M or %m in ItemFormat. I even added emacs mode settings for your indentation style :-) I don't think these are the right settings, they insert 4 spaces. In fact, I think the only way to configure emacs to do anything useful is to disable auto-indentation and insert real tabs on tab press. I'm confused as to what is happening. I screwed up the mode settings, but they should have made emacs display the tabs as equivalent to 8 spaces not 4. The file I put up definitely has single tabs for indentation. Could it have got corrupted somewhere? Anyway, I've got some more changes to add after the weekend. I'll send those as a patch against CVS and it will hopefully be right this time. Thanks for the help. Ric Richard J Lister Dept of Neuroscience Georgetown University Medical Center http://cns.georgetown.edu/~ric/ -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS dane: * FvwmTheme/FvwmTheme.1: Language check, general edits,
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane02/11/15 15:21:33 Modified files: modules: ChangeLog modules/FvwmTheme: FvwmTheme.1 Log message: * FvwmTheme/FvwmTheme.1: Language check, general edits, spell checks. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Style IconSize and application supplied icon windows
On Fri, 15 Nov 2002, Steve Talley wrote: Good point. A little harder to implement, but might be worth considering in the future. Yep. I looked a little at the code. MWM does someting like this, clipping the window into a frame. And I guess since you work at Sun you have some familiarty with dtwm. Pardon if I made some spellingmistakes (after 2 litres of beer :-) ) Steve Marcus Lundblad wrote: On Thu, 14 Nov 2002, Steve Talley wrote: Application-provided icon windows are purposely not resized by IconSize because the application may need the window to be a certain size. The window could provide more than just an icon, so resizing may adversely affect the application's functionality. Wouldn't it be possible to use the same technique as with swallowed windows in FvwmButtons? Just a thought. (Those icons break the nice symmetry :-) ) //Marcus -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: compiler warning/bug in FvwmScript/script.y
On 10:00 15 Nov 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | On Thu, Nov 14, 2002 at 06:50:47PM -0500, Paul Smith wrote: | %% Cameron Simpson [EMAIL PROTECTED] writes: || Sorry, I somehow missed that paragraph. I just can't operate info || :-/ |cs You may want my man script, which presents info as one of the |cs choices for manual pages. More to the point, it parses info files |cs and turns them into a single flat text document, which of course |cs you browse with your pager as with ordinary manual entries. | | Yes, please! That's exactly what I need! Start here: http://www.zip.com.au/~cs/css/index.html#s-text-info2x and get the info2man.tar.gz file and also fetch: http://www.zip.com.au/~cs/scripts/man which is the script itself. You then add the info dirs to your $MANPATH and go. It may have a few dependencies on my environment which I'd be happy to iron out, so let me know if it gives you trouble. In particular it expects the envvar $OS to be linux on linux systems (well, actually groff-based systems). Hmm, I see there's now an nroff on my redhat box, so maybe you won't need the groff incantation at all. [...] | In particular, the s (search) and i (index lookup) are critically | important to know. Once you know these you can do more with Info that | you can do with either man pages or HTML. | | I really don't want to rant about the interface of info here. Let | it suffice to say that I absolutely *hate* hierarchical documents. | And info operates a bit like vi, a bit like lynx and a bit like | emacs, but not quite. That totally confuses me. I would second that hierachical remark - I also really hate limping through HOWTO web documents which are typically presented in pieces :-( And I generally want a big document in the pager my fingers know. Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ ... that, in a few years, all great physical constants will have been approximately estimated, and that the only occupation which will be left to men of science will be to carry these measurements to another place of decimals. - James Clerk Maxwell (1813-1879) Scientific Papers 2, 244, October 1871 -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS jpweber: Fixed FvwmProxy Next to really ignore windows on other desks;
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: jpweber 02/11/15 22:54:50 Modified files: modules/FvwmProxy: FvwmProxy.c Log message: Fixed FvwmProxy Next to really ignore windows on other desks; Added temp fix to use XFillRectangle vs. XClearWindow since the latter wasn't using the proper select colorset background color; Added .fvwm2rc configs for Width, Height, Separation, EnterSelect, ProxyMove -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
