Dan Espen <des...@verizon.net> writes: > Thomas Adam <tho...@fvwm.org> writes: > >> On Thu, Jun 21, 2012 at 11:41:10AM -0400, Dan Espen wrote: >>> Thomas Funk <t.funk...@googlemail.com> writes: >>> >>> >> Hmm. I am not sure I agree with this at all. The spec defines >>> >> XDG_MENU_PREFIX which we can carry on using, seeing as its use defines >>> >> more >>> >> than just menus for us -- it's also compliant with other applications >>> >> generating menus; they too look at the value of this. >>> > It changes only the local variable not the ENV >>> > >>> >> Also, why the change of $root_menu to $xdg_menu? That's noise for no >>> >> reason. >>> > because it is more correct - it's not a root menu, it's an application >>> > menu based on the xdg menu ... but can be changed back. >>> >>> I have a rewrite of fvwm-menu-desktop that I've been using for a while >>> now. >>> >>> One of the reasons I haven't released it is because of this distinction. >>> >>> It looks to me like xdg does not include the concept of one root menu. >> >> Well don't let this be a reason to hold you back, Dan. :) I sure as hell >> don't want Thomas to waste his time (and what is infinitely worse through >> this, my time as well) on flogging a dead horse. > > Thomas, > > I have no clue about the automake implications of adding python. > I see how our configure.ac does the perl checking but I'm not clear > on how to do something similar for python. > > I can check in with the #! hard coded to /usr/bin/python. > Can you clean this up after I do that?
Backed up mail finally came through. Obviously past this point... -- Dan Espen
