docs: update zsh integration instructions #3794
Merged
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.
Problem
In #3736 the
alias
expansion was only tested for the old way of sourcing the*.zsh
shell files.However, when attempting to use
eval
, it doesn't disablealias expansion
, leading to the same issue as seen in #3731.Proposal
The
eval
command affects the setup established in issue #1944. However, the following syntax appears to work effectively:Alternative Solution
To resolve this, we could prepend
command
to the commands, such asawk
,cat
,sed
, etc.Other Projects
For comparison, consider how
kubectl
is set up on macOS:Pinging @romkatv for your valuable input: we're trying to understand why
eval "$(fzf --zsh)"
has issues with alias expansion, whilesource <(fzf --zsh)
seems to work well. Could you help us see if there are any potential problems with using the latter for sourcing the*.zsh
files? Your expertise would be incredibly helpful.