Specifying absolute path to fzf in `fzf/executable' results in "Wrong type argument: processp, nil"

bling / fzf.el

A front-end for fzf

GNU General Public License v3.0

360 stars 50 forks source link

Closed JohnC32 closed 1 year ago

JohnC32 commented 1 year ago

If fzf is not on the path and you specify fzf/executable as the full path to the executable, running M-x fzf will result in error:

 Wrong type argument: processp, nil
 Back to top level
 Error in post-command-hook (term-goto-process-mark-maybe): (wrong-type-argument processp nil)

This is on Debian 11, using Emacs 27 with fzf.el from Jan 13, 2023, 1d80e76.

pierre-rouleau commented 1 year ago

I concur. There's a problem there. I'm looking at it.

pierre-rouleau commented 1 year ago

@JohnC32 Thanks for reporting this. It'd be great if you could try the fix in my PR https://github.com/bling/fzf.el/pull/106 and confirm it works for you.

JohnC32 commented 1 year ago

Thanks for the quick fix. The fix works.

pierre-rouleau commented 1 year ago

I just happened to look at my messages last night. Thanks for confirming. I Just asked @bling to integrate it.