On Tue, May 09, 2023 at 01:26:45PM -0700, mark_at_yahoo wrote: > AddToFunc StartFunction > + I ImagePath > $[HOME]/.local/share/icons/hicolor/48x48:$[HOME]/.local/share/icons/hicolor/64x64:$[HOME]/.local/share/icons/hicolor/72x72:+
Setting ImagePath here is a little counter-intuitive. It's a global command that should be set at the top of your file. See: https://www.fvwm.org/Wiki/Tips/FvwmStartup/ > From reading the documentation I've always assumed that FVWM searches > the ":"-separated paths (including the default indicated by "+") for an > appropriate image file with some "NAME" plus a supported suffix such as > ".xpm", ".svg", ".png", depending on how the fvwm binary was compiled. I > recently discovered the following post, which clarified that the "NAME" > is derived from the X11 window class property: Hmm. No. Unless you set IconOverride, the preference is to the application-provided icon. > Q: Is my understanding of FVWM's ImagePath correct? See above. > Q: How can I list the compiled-in default "+" ImagePath, maybe > with some command in an FvwmConsole? You can't easily. > Q: Where is the mystery small icon be coming from? MiniIcon. Same principle as above. > #0 0x00007f1e0696190c __pthread_kill_implementation (libc.so.6 + 0x8f90c) > #1 0x00007f1e06910196 raise (libc.so.6 + 0x3e196) > #2 0x00007f1e068f8897 abort (libc.so.6 + 0x26897) > #3 0x00007f1e068f87ab __assert_fail_base.cold (libc.so.6 + 0x267ab) > #4 0x00007f1e069084b6 __assert_fail (libc.so.6 + 0x364b6) > #5 0x00007f1e078b4c03 _XAllocID (libX11.so.6 + 0x42c03) Try the fvwm2 version from git. Kindly, Thomas
