-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Type check commands #67
Comments
We've added the support to do this and have laid in the groundwork for more, so going ahead and closing this |
elferherrera
pushed a commit
to elferherrera/nushell
that referenced
this issue
Feb 7, 2022
Revert "improve table for lists"
Hofer-Julian
pushed a commit
to Hofer-Julian/nushell
that referenced
this issue
Jan 27, 2023
Replace splitting tag in git log
amtoine
added a commit
to amtoine/nushell
that referenced
this issue
Apr 6, 2023
Command used ```bash [.github/**/* **/*.rs **/*.nu] | each {|target| sd 'crates/nu-utils/standard_library' 'crates/standard_library' $target } ``` i used this complex command because of ```bash >_ sd 'crates/nu-utils/standard_library' 'crates/standard_library' **/* Error: nu::shell::external_command × External command failed ╭─[entry nushell#67:1:1] 1 │ sd 'crates/nu-utils/standard_library' 'crates/standard_library' **/* · ─┬ · ╰── can't run executable ╰──── help: Argument list too long (os error 7) ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have enough information about the commands and the piped chain of commands that we could do some simple typechecking on it before we run it.
Some examples:
The text was updated successfully, but these errors were encountered: