Ryan Lue

That's originally how I had wanted to do it, but 1) JS is not my main language, and 2) I didn't want to spend the time figuring it out if...

No, I agree; it does feel weird this way. Here's another idea: we could create a new file at `plugin/fold_rspec.vim` that looks like this: ```viml if exists("g:loaded_fold_rspec") finish endif let...

Alternately, we could just simplify the existing `if` clause to: ```viml if !exists('g:fold_rspec_enhanced_foldtext') || g:fold_rspec_enhanced_foldtext ```

> [raising exceptions in queries] breaks the pattern of query methods returning a boolean. I just discovered that 973b63b (relatively recent—just six months old) builds on (established?) this pattern of...

> Generating error messages should be handled at the presentation layer. Can you elaborate? Applications with no presentation layer at all (_e.g.,_ CLI apps) raise errors and set messages on...

> The library should be able to send a failure reason or an error message and leave the decision about how error messages are displayed to the application. 100% agree,...

Interesting! I assume you actually meant the following: ```ruby def foo? return :no_user unless user return :archived if record.archived? true end ``` because without `return`, the symbols are invoked in...

I am on an M1 Mac Mini. I have confirmed that `powerMonitor.getSystemIdleTime()` works in Electron (and so the `upstream` tag can be removed from this issue, and/or this issue may...

This is an interesting problem. Here are the solutions, as I see them: 1. The easiest fix would be if there were a way to run `system()` commands asynchronously. Your...

So pleased to hear it. :) As with #3, I see the value but I'm too lazy to make concrete decisions about how this should be done. If one more...