Philip Waritschlager
Philip Waritschlager
no, you're right, and it makes sense to add some custom scoping like you did imo!
haven't looked into this. I guess for now the workaround would be to add a `send {RButton up}` manually
Broke with recent update, I've already fixed it in the commits. Nope, no highlighting, I think there's been an issue for that somewhere already too. But otherwise it should have...
implemented recently, it's now a checkbox, there's highlighting, and also more search options for file contents etc., and the selected type is remembered across restarts
They are currently calculated based on the hash of the branch name, so always stable. They are picked from a set of pre-defined colors. These aren't super great though, some...
Jup, both good ideas!
the default logic hasn't changed, but you can now fully configure branch coloring with new config settings `branch-colors`, `branch-color-strategy`, and `branch-color-custom-mapping`.
good ideas here, and the quick tip area info text thingy is just the output of cli `git status` that I put there because frankly I didn't know what else...
#715
Facing the same issue, except we also get error output: ``` client-shared.js:2058 TypeError: Cannot read properties of undefined (reading 'useState') at useLottie2 (lottie1.js:166:27) at Lottie3 (lottie1.js:484:22) at Nh (vendor.js:12852:8) ```...