Thomas Adam

Hi @slazav That's part of it. But this is also a lot of work. It's not as simple as just removing the option for `-s`. Internally, `fvwm3` is tracking the...

Hi @slazav, How are you getting on with this? Is there anything I can do to help?

Hi @slazav, I understand completely about being busy! Please do open a PR your work and I'll pick up the remaining bits soon.

Can you provide me with a backtrace, please? I've tried to reproduce this, but cannot.

> And, of all the possible stack traces, which one would be the most useful? If it's vim which is crashing, that'll definitely help me. Any/all strack traces which are...

Perfect. Thank you -- I'll try and get round to looking at this soon. I'm moving this to the `fvwm3` repository so I don't lose it -- any fixes I...

Seems to work OK for me:  If you're still seeing crashes, you'll need to get me a stacktrace from a corefile.

Yeah, that's no good to me -- not only is the formatting abysmal, but also you'll need to ensure you build fvwm3 with debug symbols: adding `-ggdb -O0` to CFLAGS.

Thanks for the testing. The patch isn't quite right, but I'll work with @topcat001 to get something which is, next week.

Hi @Zirias I think this patch is correct -- in most cases where `fscreen_scr_arg arg` is used, it's doing so not based directly on the screen name. Please can you...