Stefan Haller

> That's an interesting use case for `CATCH_CONFIG_FALLBACK_STRINGIFIER`, but one that I am not convinced should be supported. It has saved us so many times that I wouldn't want to...

I'd be interested in suggestions how to work around the issue (apart from "don't abuse `CATCH_CONFIG_FALLBACK_STRINGIFIER` like this" -- we definitely want to keep the behavior of getting compilation failures...

Thanks for looking into this! We solved our problem a while ago by actually implementing all the missing stringifiers for all the types we use in GENERATE statements, so it's...

Yes, this is my only remaining big feature wish too. However, the way I understand it, it first needs support from VS Code, see https://github.com/microsoft/vscode/issues/134941. While it might also be...

@jesseduffield We can make it a lot simpler than [your suggestion above](https://github.com/jesseduffield/lazygit/issues/1062#issuecomment-1301620948). We don't need a per-repo or even per-branch config for what the base branch is. Fortunately, `git merge-base`...

I made a draft PR if anybody wants to play with it: #2619. I use option 2. above in the first commit, but added a second commit that uses a...

Closing as obsolete, now that we have #3173.

It would be great to have a (hacky) patch to try these out, would that be possible easily?

Thanks. It's really tricky to find a good balance between it being discernible (at a glance) and still looking elegant. I feel we could do without the `┴` and `┬`...

> All we need to do is change it so that it can be one character long at minimum, Are you expecting me to do that? I wouldn't be angry...