[NUMI] ... Querying Numi CLI doesn't work about extensions HOT 14 CLOSED

Thank you for opening this issue!

🔔 @AndresMorelos @pernielsentikaer @viandwi24 you might want to have a look.

from extensions.

I just tested this and downloaded it from brew too, no errors. What does which numi-cli in the terminal gives you?

from extensions.

I just tested this and downloaded it from brew too, no errors. What does which numi-cli in the terminal gives you?

That is weird. Here you go:

from extensions.

BTW, does it matter that Numi itself is installed? Could that somehow impact the numi-cli? I tried uninstalling Numi the application too, but still getting the error.

from extensions.

No that should be more than fine, do you know how to debug an extension by forking it? If so I'd like to check it with you 🙂

from extensions.

Unfortunately not. Are there instructions how to do that somewhere? Also, could it be a permissions problem of some kind maybe?

from extensions.

If you know just a little bit of coding, then you can use the Fork action like this

That will guide you a bit, let me know if that files, then you can open the forked extension and add console.logs to the code and run the code with npm run dev

from extensions.

I did this, but when I execute npm run dev, I get a ray: command not found error.

from extensions.

OK, I figured it out. I ran the extension from Raycast, and it worked like that. It turns out there was an error in my .bashrc file which was causing the problem. Actually, it wasn't an error, it was the initialization of the Startship prompt. After commenting that out, it started working fine. You might want to look into that.

from extensions.

@alexbet could you please share a minimal .bashrc to replicate it? I also have Starship prompt but with ZSH, and, it works without issues.

Probably, it's related to starship/starship#5816

from extensions.

BTW, I see here (#10986 (comment)) that you use ZSH too

Why not use a .zshrc file instead of .bashrc and add

eval "$(starship init zsh)"

from extensions.

The code use is:

eval "$(starship init bash)"

I have no idea why this would be a problem. Anyway, switched to ZSH instead.

from extensions.

The code use is:

eval "$(starship init bash)"

I have no idea why this would be a problem. Anyway, switched to ZSH instead.

I'm not sure why this happened, but it also with the VSCode integrated terminal when it tried to source the .bashrc file, probably something related to the starship prompt for the bash environment.

Now that you switched to ZSH, is all working as expected?

Let me know to close this issue.

@alexbet

from extensions.

@alexbet I'll close this issue, feel free to reopen if the issue persists

@raycastbot close this issue

from extensions.