Qi Xiao
Qi Xiao
A log module with a runtime-configurable destination and style is definitely a reasonable building block, and it does make the need for separate stderr-writing commands obsolete. The API is orthogonal...
Weirdly I couldn't find dedicated docs for namespaced keywords on Clojure's website, but a Google search seems to give some relevant results.
I think bitwise operations should work for all exact integers (`int` and `big.Int`).
As for naming... I would opt for more boring and verbose names in a new `bitwise:` module: `bitwise:and`, `bitwise:or` and so on.
The `jump-to` command could then be implemented like: ```elvish fn jump-to {|filter| cd (edit:location:filtered-dirs $filter | take 1)} ```
"Command not found" error when running a batch script with space in path with an argument with space
This is a Windows thing 😞 I'm actually a bit surprised that it took so long for someone to file an issue :) The gist of the issue is that:...
"Command not found" error when running a batch script with space in path with an argument with space
Hmm OK, this is more complicated than I thought actually. When you pass an argument with spaces to `code`, the error message is actually complaining that the *command* could not...
"Command not found" error when running a batch script with space in path with an argument with space
Hmm, I believe the error comes before the `... %*` line in the bat file. It happens as Windows is trying to execute the bat file and *if both the...
"Command not found" error when running a batch script with space in path with an argument with space
Hmm OK, it's https://github.com/golang/go/issues/17149
"Command not found" error when running a batch script with space in path with an argument with space
The issue is a bit long, here's my summary of what's relevant for Elvish: - The root of the issue is that when you call `StartProcess` on Windows to run...