Aaron Jensen

Here's an example `.tool-versions`: ``` nodejs 12.15.0 ruby 2.7.0 ``` Is that good or do you need an actual repo with that in it?

Yeah, it was running QMK. It woke fine for a couple years. Thanks for the link to the issue. Feel free to close this one since it’s tracked upstream.

There must be specific sleep states where it can wake. This morning, it woke for me: ``` 2022-08-29 09:05:52 -0400 Assertions PID 327(powerd) Created UserIsActive "com.apple.powermanagement.kernel.useractive AppleUserHIDEventDriver:sleepDisplayTickle kIOMessageSystemWillS" 00:00:00 id:0x0x900009129...

That’s great, thanks.

Is there a way to revert it manually upon leaving? For example, I'd just want to return it to a box on leaving. I tried delete-frame-hook but that didn't work.

For now I added a cursor reset to my prompt. Something like this: ```bash if [ -n "$TMUX" ]; then local _reset_cursor=$'\e[0 q' else local _reset_cursor=$'\e[2 q' fi PROMPT='%{${_reset_cursor}%}...' ```

@starenka with respect, your initial comment included a suggestion to "revert back to this commit", which is not the same as reverting a commit. Instead, it implies resetting to that...

Great, thanks!

This looks like it could be the cause: https://github.com/rubygems/rubygems/pull/5256

@deivid-rodriguez that is very unfortunate. It essentially makes these versions of bundler unusable for us. We delete Gemfile.lock every time we install and do not pin unless we must. In...