-
Notifications
You must be signed in to change notification settings - Fork 198
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
Can't preview string with nul byte #278
Comments
lotabout
added a commit
that referenced
this issue
Mar 1, 2020
Now NUL will be translated back to `\0` when invoking execute or preview command. It may not be expected in all cases, but it is the best we can do for now.
Current fix will translate NUL character to |
lotabout
added a commit
that referenced
this issue
Mar 1, 2020
Now NUL will be translated back to `\0` when invoking execute or preview command. It may not be expected in all cases, but it is the best we can do for now.
lotabout
added a commit
that referenced
this issue
Mar 1, 2020
Now NUL will be translated back to `\0` when invoking execute or preview command. It may not be expected in all cases, but it is the best we can do for now.
lotabout
added a commit
that referenced
this issue
Mar 1, 2020
Fix #278: NUL not working in preview cmd
Another solution is to support eg. fzf --preview='echo "$(<{f})"' <<<$'abc\0abc' |
makovich
pushed a commit
to makovich/skim
that referenced
this issue
May 28, 2020
Now NUL will be translated back to `\0` when invoking execute or preview command. It may not be expected in all cases, but it is the best we can do for now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Got an error:
The text was updated successfully, but these errors were encountered: