I've had a very strange issue, and I have a workaround (hack) to get around it. I don't really have the time to figure out exactly what is going on, but figure I'll leave this issue for anyone else who might come along.
When running helm-fasd(-*) I get the error:
helm-get-candidates: Candidates function ‘#[128 \302\300\303\301""\207 [helm-fasd-init (fasd -R -l -s ) apply append] 6
(fn &rest ARGS2)]’ should run a process
Now... that doesn't seem right, since if you look at helm-fasd-init it's clearly starting a process right there.
I got lazy and swapped the helm-log lines to message (I know, I should be setting some debug var to control this, but :man_shrugging: ). This meant that I now had the line (message "Starting helm-fasd process") in helm-fasd-init. This stopped the error occurring and made allowed me to use the package as normal.
I really don't feel like investigating what exactly is causing a tool to start working when I'm adding debug lines right now, so I'm leaving this here for anyone braver than me (if anyone else hits this issue).
I've had a very strange issue, and I have a workaround (hack) to get around it. I don't really have the time to figure out exactly what is going on, but figure I'll leave this issue for anyone else who might come along.
When running
helm-fasd(-*) I get the error:Now... that doesn't seem right, since if you look at
helm-fasd-initit's clearly starting a process right there.I got lazy and swapped the
helm-loglines tomessage(I know, I should be setting some debug var to control this, but :man_shrugging: ). This meant that I now had the line(message "Starting helm-fasd process")inhelm-fasd-init. This stopped the error occurring and made allowed me to use the package as normal.I really don't feel like investigating what exactly is causing a tool to start working when I'm adding debug lines right now, so I'm leaving this here for anyone braver than me (if anyone else hits this issue).