Closed LATBauerdick closed 4 years ago
There seem to be more general problems with "special characters" in ID and filenames.
Try a filename/title/ID like "R&D Goals"!
for the problem with neuron search -e
the effect is similar to the difference of, e.g.
nvim $(fzf)
vs
nvim "$(fzf)"
the first can't deal with "special" file names, the latter seems to work fine -- although I'm not sure it will deal with all possible cases.
I think this is because we are piping the filename output unquoted to the editor: https://github.com/srid/neuron/blob/a33ccad0b84bef9dc1c06ccd913f0e5d4724881c/neuron/src/app/Neuron/CLI/Search.hs#L36-L37
Changing the above to use xargs
as indicated here might be one fix.
This is working in current master
(probably due to #445?), so I'll close.
at least not if
$EDITOR
is set tonvim
. It looks like that the file name returned from fzf needs to escape the blank characters.e.g. if the search result returns the file name
one two.md
, the editor opens two files, with the filenames ofone
andtwo.md
.