Nathan Fritz
Nathan Fritz
@harlantwood the ipfs link isn't loading -- just hangs.
I was able to reproduce this on Windows, but not on other platforms.
The `%PATH%` is generated correctly for each script. The `%CD%` is correct for each script. `\node_modules\jest\package.json` is `26.x.x` `\jest-26\node_modules\jest\package.json` is `28.x.x` But when executing `\node_modules\.bin\jest.cmd` from any other path other...
Having a method that accesses that would be a good way to go about it.
Now that I'm actively using neovim, I'll start maintaining this. Sorry about that.
@nokolay AFAIK, @bear is just doing housekeeping on sleekxmpp rather than adding features. If you'd like to make a pull request for 301, I'm sure he'd be happy to look.
We've discussed changing some of the xmlstream reading/rewriting functions to load/install different versions depending on which version of Python you're using. This may not be enough, and needs a bit...
I could see that argument. I'm not sure if it's a bug or a feature request. I'm curious as to your use case. You could always run `tar -tvf package.tgz`...
Just a side comment... should we be using `--fixup`, `--amend`, or `refactor:` for feedback commits? I'm thinking usually an amend/fixup, but a refactor if it is significant.
A reproducible version of this issue is in #5046 with a helpful discussion.