You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be convenient for scripts if glide novendor could print paths separated by "\n". That will make tools like sed and grep easier to use for processing its output. I encountered this in an old project that sets its own GOPATH and was forced to put glide.yaml in a strange location.
On *nix systems I'm familiar with the command go test $(glide novendor) will work the same regardless of newline bytes in the output of glide novendor. If backwards compatibility is a big concern a flag could control the delimiter and default to a white space byte.
I'd be willing to write the pull request if desired. I'm sure its fairly straight forward. But I wanted to bring up the issue before coding.
The text was updated successfully, but these errors were encountered:
It would be convenient for scripts if
glide novendor
could print paths separated by"\n"
. That will make tools likesed
andgrep
easier to use for processing its output. I encountered this in an old project that sets its ownGOPATH
and was forced to putglide.yaml
in a strange location.On *nix systems I'm familiar with the command
go test $(glide novendor)
will work the same regardless of newline bytes in the output ofglide novendor
. If backwards compatibility is a big concern a flag could control the delimiter and default to a white space byte.I'd be willing to write the pull request if desired. I'm sure its fairly straight forward. But I wanted to bring up the issue before coding.
The text was updated successfully, but these errors were encountered: