Hi everyone. Gee, stay away for a while, and everything’s different.
Yeah, I know this is a bit of a duplicate, but I figured the specific title might help others find it better. Plus, I hope more info.
I’m on Ubuntu 20, so Fvwm 2.6.8 and more importantly, pyxdg 0.26. The pyxdg bug has already been mentioned, but the short version is the fvwm-menu-desktop duplication problem is in the pyxdg library, and it’s been fixed.
That’s all nice, but Ubuntu hasn’t made a newer pyxdg available in updates. (No, I’m not going to do a dist-upgrade - I have my reasons. )
So, I’m hoping to figure out a fix. I’m hesitant to try to just overwrite the system pyxdg with a newer version from git or wherever, but before I try that, I wonder whether I can do a local install of it, and have Fvwm use it. It’d be something like what I remember from years ago, using $LD_LIBRARY_PATH to run beta software for testing. I’m certainly not a Python coder, but I think it has something similar. (IIRC, so does Perl.) If I could stick pyxdg in $HOME/local/python3 (or wherever) and use an ENV to use it for fvwm-menu-desktop somehow, might that be an option? If so, I’d appreciate some details.
ETA: I messed with this some, and this, so far, seems to work. Comments appreciated.
pip install --user --upgrade pyxdg PYTHON_PATH=~/.local/lib/python3.8/site-packages/xdg/ fvwm-menu-desktop > foo.menu
It threw a lot of errors, but seemed to work OK.
Maybe, if I export the PYTHON_PATH in my .bashrc, it’ll stick for invocations of FvwmForm-XDGMenu-Config. Would it be better to just do SetEnv?