On Tue 18 Sep 2018 at 09:26:29 (+1000), Zenaan Harkness wrote: > On Mon, Sep 17, 2018 at 08:44:10PM +0000, Kleene, Steven (kleenesj) wrote: > > On Mon Sep 10 08:47:39 EDT 2018, I wrote: > > > > >> I can't figure out where fvwm is getting the xpm icon for an xterm. > > >> ... > > >> I have this in ~/.fvwm/config: > > >> Style "XTerm" Icon null.xpm, SloppyFocus, IconBox 200x200-1+8 > > >> where null.xpm is intended to call /usr/share/pixmaps/fvwm/null.xpm, a > > >> zero-byte file I created. > > > > On Monday, September 17, 2018 9:41 AM, Thomas Schmitt replied: > > > > > Maybe fvwm is not happy with the zero size. > > > What happens if you put a file with a picture there ? > > > > If I put ANY other xpm there, I still see an icon that matches > > /usr/share/pixmaps/mini.xterm_48x48.xpm or a live window screenshot. > > If any xterm is open - or in fact if any other program has that file > "locked and loaded", then the effect of replacing that file on disk > will not be seen until the file gets unlocked and reloaded - logging > out of X and back in should do it (as would rebooting of course). > > There ought be a more elegant "reload this icon" method rather than > logout/in - perhaps someone else knows what it is?
I don't see why you should need to involve X: it should be enough to restart fvwm because the decision as to which icon to use should be being held within fvwm, not X. BTW if you really dislike the active icon (the one that just keeps running xterm in miniature), you should be able to disable the feature with the xterm -ai commandline option. Cheers, David.
