Thomas Adam wrote:
> On 25 July 2012 18:38, Thomas Funk wrote:
>>> Dan Espen wrote:
>>> Thomas Adam made some comments about using FvwmPerl. Is that resolved?
> No -- and as such, until it starts to use perllib and/or FvwmPerl,
> it's not ready. There is *no* reason why we wouldn't dog-food ou
2012/7/23 Thomas Funk :
> 2012/7/23 Thomas Adam :
>> Don't destroy the same menu you're about to (re)create.
> But if I don't destroy it it will be added again and again to
> the root menu every time I pop it up ...
I've tested it on my VM and you're right! Is this because the
menu will built only
2012/7/23 Thomas Adam :
> Don't destroy the same menu you're about to (re)create.
But if I don't destroy it it will be added again and again to
the root menu every time I pop it up ...
Thomas Adam wrote:
>> package Test;
> Will need better namespacing.
changed it to package MenuConfig;
>> use File::Basename;
>> use strict;
> use warnings;
added
>> my $selected = `fvwm-menu-desktop --get-menus selected`;
> How long do these commands take to run in backticks? If long,
perhaps
Thomas Adam wrote:
> On 19 July 2012 22:11, Dan Espen wrote:
>> I'm guessing the other fvwm developers are okay with going to asciidoc?
> No. I have an attempt at this, but it's not finished. We either use
> groff or nothing, and I don't mean groff backported from some
> conversion tool. If y
2012/7/16 Thomas Adam wrote:
> Isn't this in the XDG spec as to which menus appear where, in
> categories? I'm sure it is.
That's right. The process (the python-xdg lib) which generates the menus
follow this. But fvwm-menu-desktop only calls the methods for each menu
found in the system. The stru
