andrew blinn

@dm0n3y wondering if we can address this but just not prevent defaulting on unhandled keyboard cases? could try this

that would help mitigate it for sure... remind me of why you're not keen on triggering expansion on move-away instead of space/tab?

my preference here would be to keep the overall UI clean by not having persistent buttons for the rename/add/delete functionality. like instead, maybe they only appear when you hover over...

@cyrus- yeah for sure. I worry there might be two reasons, my recollection is also fuzzy. In any case I think any reasons for the asymmetry are specific to the...

ah probably that. any thoughts about the separate issue?

(a somewhat artificial example but worth changing i think) i feel like the let case should probably have a distinct error message as well since how you address such an...

change made here: https://github.com/hazelgrove/hazel/pull/1111 which was a follow-up to earlier perf work here: https://github.com/hazelgrove/hazel/pull/1079

@cyrus is this still a thing? can't reproduce, unless i'm misunderstanding

Would be addressed by #1351 (pretty sure this is an overlay capture issue)

this one has been bugging me forever but an easy fix eluded me.... would be good practice for anyone who wants to get into the nitty gritty of the code...