summaryrefslogtreecommitdiff
path: root/plugin
diff options
context:
space:
mode:
authorKoichi Murase <myoga.murase@gmail.com>2025-06-04 13:11:00 +0900
committerJunegunn Choi <junegunn.c@gmail.com>2025-06-08 00:00:17 +0900
commit09194c24f275d9387b31e50b38cf7f3a94b1f0fa (patch)
treeb4a1502f35c6e919e48e8f6680cdcfa284dc372e /plugin
parentec521e47aa9d8ee0b28801d11d737bf91c46bc43 (diff)
downloadfzf-09194c24f275d9387b31e50b38cf7f3a94b1f0fa.tar.gz
[bash,zsh] Work around a quirk of macOS awk
macOS awk is a variant of nawk, but it contains a unique patch for the UTF-8 support. However, this patch causes the problem. If the input contains any non-UTF-8 data, macOS awk stops processing and does not do anything, instead of ignoring the unrecognized data and continue the processing. However, the contents of the ssh configuration and /etc/hosts is not under the control of fzf, so we cannot fix the input when those files contain non-UTF-8 data. To work around this behavior, one can set the locale to LC_ALL=C to treat the input data with the plain 8-bit encoding.
Diffstat (limited to 'plugin')
0 files changed, 0 insertions, 0 deletions