Skip pre/post exec events for empty commands (#4829) #7085
Closed
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
In the same vein as #4926, firing
fish_preexec
andfish_postexec
for empty commands is inconsistent with the way$status
,history
and$CMD_DURATION
treat empty commands.fish_postexec
, for example, receives an incorrect value for$CMD_DURATION
when an empty command is processed.As suggested in #4829, this patch skips firing of these events for empty commands altogether.
Fixes issue #4829
TODOs: