Aram Drevekenin

Yeah, it's also not even a crash: https://github.com/zellij-org/zellij/blob/6cf795a7df6c83b65a4535b6af0338b4a0b1742f/zellij-client/src/input_handler.rs#L83 I guess these are both symptoms of something else unhandled

I think it's fine to keep this open as a reported issue, even if we don't yet have enough info how to solve it.

Hey @abatkin - first, thank you for your patience in waiting for a review and even rebasing the code to the latest changes. While I'm generally happy to add this...

@marianomarciello - respectfully, I disagree with both points. 1. Every application on our machine relies on lots and lots of external dependencies. This is extra visible with rust projects since...

Not sure why this was closed? It's still not implemented...

All good - I want this to be implemented, but I hope you can be patient - it might take time.

This means that one has a configuration file from a newer Zellij version and is running an older Zellij version. I guess this likely happened to OP because they installed...

> I'm seeing the same thing after launching zellij for the first time since last week on my Intel Thinkpad. I've changed nothing in the config. I'm running zellij 0.42.2-1...

I hear you, but honestly... how would you suggest this be implemented? Given that by definition an older version has no knowledge of the config of the newer version?

> It doesn't have to have knowledge of any specific properties, just that it's found unknown property. This is what we do now, except we use the word "Unsupported" rather...