Add --full-reparse/-f to run command#18339
Merged
Merged
Conversation
fdncred
commented
Jun 4, 2026
nidara-duo
pushed a commit
to nidara-duo/nushell
that referenced
this pull request
Jun 5, 2026
## Description
This PR fixes 2 bugs in the `run` command.
1. It allows for a user to use `run` in non-caching mode by specifying
`run --full-reparse/-f`. This is good for situations like this `watch .
-g *.nu | where path ends-with test.nu | each -f { run -f test.nu }`
when a user is editing `test.nu` over and over again. However, one
should be careful because `test.nu` could be looked up from other viable
locations. It's better to use something like `./test.nu`. I actually ran
into this while testing.
2. It fixes a bug where the decl lookup wasn't correct so `nu -n` and
then `run toolkit.nu` would only work once when you should be able to
`run toolkit.nu` many times in the repl.
## User-facing changes (Release notes)
Bug fixes
- `watch . -g *.nu | where path ends-with test.nu | each -f { run -f
./test.nu }` now works.
- `nu -n` then `run toolkit.nu` then `run toolkit.nu` now works,
previously it didn't allow running it more than once due to a bug in
caching.
## Additional notes
<!--
Optional.
Examples:
- fixes nushell#123
- closes nushell#456
- related nushell#789
Anything else reviewers should know.
Remove this section if not needed.
-->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes 2 bugs in the
runcommand.runin non-caching mode by specifyingrun --full-reparse/-f. This is good for situations like thiswatch . -g *.nu | where path ends-with test.nu | each -f { run -f test.nu }when a user is editingtest.nuover and over again. However, one should be careful becausetest.nucould be looked up from other viable locations. It's better to use something like./test.nu. I actually ran into this while testing.nu -nand thenrun toolkit.nuwould only work once when you should be able torun toolkit.numany times in the repl.User-facing changes (Release notes)
Bug fixes
watch . -g *.nu | where path ends-with test.nu | each -f { run -f ./test.nu }now works.nu -nthenrun toolkit.nuthenrun toolkit.nunow works, previously it didn't allow running it more than once due to a bug in caching.Additional notes