Allow for multiline env vars when generating and reading /tmp/ytfzf-env #552
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.
If you want to have a multiline string anywhere in your environment such as
ytfzf
will error withbecause it is trying to
export
--bind
(I realize I could put it all on one line but it looks neater in my zshrc this way and it works with fzf just fine) 😛
This change set tells
env
to delimit variable definitions by the special unix null character, by calling it with-0
. This character is much less likely to be found in an env var as it denotes the end of a string.stuff I searched to come to this solution:
https://www.man7.org/linux/man-pages/man1/env.1.html
https://stackoverflow.com/questions/8677546/reading-null-delimited-strings-through-a-bash-loop