hdansou / logseq-alfred

Alfred Workflow for logseq
MIT License
75 stars 5 forks source link

Searching files (lqf) works, but searching content (lqs) apparently not #16

Open Sekibutsu opened 1 year ago

Sekibutsu commented 1 year ago

Hi,

I did installations per the instructions, and "lqf" finds and opens files, but "lqs" does not find anything. Any ideas? Is it supposed to search from within all files with any keyword, similarly than to Logseq cmnd+K function? Hope to get this work if so.

My best, Oskari

huhinka commented 9 months ago

I have the same problem. In my case, Alfred did not find the Python2 executable after macOS 12.3 which removed it.

And my workaround is using External Script to point to Python3 instead of /usr/bin/python.

The steps of this can be found here: Calling non-standard runtimes from Alfred.

When configuring a Run Script or Script Filter, Alfred provides a Language dropdown listing the runtimes which have historically been included with macOS. But what if you want to run a script from another language which you have installed on your system? Be it Node.js, Lua, or something else, it’s dead-simple to call them. Either:

  • Save your script with a proper shebang (examples: #!/usr/bin/env node; #!/usr/bin/env lua) and use External Script as the Language, pointing to your script.
  • Use /bin/zsh (or /bin/bash) as the Language and tell the runtime to call your script (examples: node MY_SCRIPT.js; lua MY_SCRIPT.lua).