Re: fvwm2 -> fvwm3 (War: FVWM: Resizing)
Am Do den 11. Mai 2023 um 21:27 schrieb Thomas Adam: > > - FvwmProxy gone > > Correct. Is there any replacement? I was using FvwmProxy quite often as I often have many windows one upon the other and need to find a specific window. It is also helpful to find windows that some cracy applikation set to 1x1 pixel without border. (Don't laugh! I had that several times.) Ah, yes, the focus policy seems to be changed. Especially with SloppyFocus. When my button menu closes it takes the focus from different window. I also found out that the config must not have BOMB marking. (I usually have all files in utf8 encoding with bomb as my vim setup open non-BOMB-files as latin1.) I also found that restart of fvwm3 does iconize some (not all) windows. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Re: fvwm2 -> fvwm3 (War: FVWM: Resizing)
tl;dnr ... many thanks to all, but I'm still struggling with the syntax. Can anyone provide me with a config line which does: "For all windows, search the current IconPath for a file .png and use it if found." and, optionally: "... and if not found, use the application-provided icon, or if none, no icon at all" but I'd be happy with anything (except a crash ;) ) in the "not-found" case. (I've had some partial success with "Style ** Icon terminal.png" but I don't want that on all windows, nor to have to add explicit "Style FooApp Icon foo_app.png" lines for everything I use.) On 5/11/23 12:20 PM, Klaus Ethgen wrote: > It might be that the application brings its own icons. Search for > _NET_WM_ICON in the xprop output. Yes, that's what's happening. `xprop` even provides a low-res colored-ascii-block renditoin of the icon. Thanks for clearing up this mystery. > I myself do not use the icons as I use a custom iconize function to > replace the icons with a small snapshot of the content. This sets the > following styles: `WindowStyle IconOverride, Icon > $[FVWM_USERDIR]/icon.tmp.$[w.id].png, StaysOnBottom` That's really cool (and something that, somehow, xterms do on my system), but I'd actually prefer a static icon (as long as it's of my own choosing). > So, the IconOverride here is the key. Again as per the "tl;dnr" above, any help appreciated. On Thu, 11 May 2023 14:38:59 -0700, Thomas Adam wrote: > Setting ImagePath here is a little counter-intuitive. It's a > global command that should be set at the top of your file. See: Thanks for the full documentation. Makes perfect sense, and I'd already made the change at Klaus's suggestion. > Hmm. No. Unless you set IconOverride, the preference is to the > application-provided icon. Again, thanks for clearing up what's been a mystery to me for years. Even before my current spate of problems I've never understood why I get one style of icon for my terminal windows (mate-terminal, KDE konsole, etc) but a different one after a "FvwmCommand restart" (and seemingly sometimes at random, without). > > Q: How can I list the compiled-in default "+" ImagePath, maybe > >with some command in an FvwmConsole? > > You can't easily. Sad, but understandable since I'm probably the first person who's needed it in the 30 year history of Fvwm. > Try the fvwm2 version from git. I think the crash is only happening due to my current problems, and only happens if I forget to un-iconify all windows before doing "restart". (That didn't crash on my previous openSUSE versions, but also didn't work correctly.) If that's the case I'll probably punt and get back to what I'm supposed to be working on instead of fighting these install teething pains. But, yes, my next step was to build 2.x and/or 3.x from source (openSUSE Tumbleweed doesn't provide 3.x despite being a rolling release which claims to track the latest from all projects). If nothing else, I was going to compile the source to add some debug output to print ImagePath.
Re: fvwm2 -> fvwm3 (War: FVWM: Resizing)
On Tue, May 09, 2023 at 08:51:00PM +0100, Klaus Ethgen wrote: > Am Mo den 8. Mai 2023 um 19:24 schrieb Thomas Adam: > > In fvwm3, randr support supports this without a restart, but it needs more > > testing. > > That brings me to the topic I did long postponed. > > How to best move from fvwm2 to fvwm3? Use: fvwm-convert-2.6 Along with release notes: https://github.com/fvwmorg/fvwm3/releases I also recall cks writing a blog post about this: https://utcc.utoronto.ca/~cks/space/blog/unix/Fvwm2ToFvwm3 > I just gave it a try and found several incompatibilities. You will do -- this is now a feature, and not a bug. > First I notice that fvwm3 does log nothing to .xsession-errors by > itself. I have to start it with `-v -o -`. It will log some things to stderr, but given how some display managers now redirect this, it was becoming more and more inconsistent. So yes, if you want to see output from fvwm3, you can use: fvwm3 -v pkill -HUP fvwm3 The signal will toggle the logging. BTW, the default log file location is $FVWM_USERDIR/fvwm3-output.log > The next is that there is somewhere default config that overwrite or > replace parts of my config. No -- no more than fvwm already has. > I just put my current and growed config to [0]. > > - Xinerama (Line 8/9) does not work anymore, what is the correct > replacement? There isn't. You now need to use xrandr(1) or some other tool to represent your monitors, and fvwm3 will automatically use that. > - The Colorset styles seems to be broken that way > - HilightBack and HilightFore style not supported > - Color style not supported Correct. Use colorsets for everything now. > - FvwmProxy gone Correct. > - The title line is completely different now. I use to have blue for > activated window and grey for inactive. Now it is the opposite (Have > to do with HilightFore and HilightBack) Again, use colorsets. > - How to have a config file for both versions with some > in-config-switches to choose between incompatible options? You could use: Test (Version ), but I would suggest converting your config file across. fvwm2 isn't being maintained any more. And fvwm3 was never guaranteed to be backwards compatible with fvwm2 -- it tries to be in that those areas which haven't changed will still work, but at some point things will diverge. Kindly, Thomas
