Integrated terminal in NVChad doesn't recognize commands (using fish-shell)

[BAD-WOLF]

2024-10-22-00-13-30.mp4

I'm experiencing an issue with the integrated terminal in NVChad. When I open the terminal using :term, it seems to be running an extremely minimal shell. Commands like nodejs, php, and apt are not recognized, and I can only use basic commands like cd, ls, and other default system commands. It appears that the terminal is defaulting to sh instead of using my preferred shell (fish).

I have fish-shell set as my default shell, but NVChad's integrated terminal doesn't seem to recognize this and always loads sh by default. When I manually run fish, it works, but this behavior shouldn't be happening.

Steps to reproduce:

1. Open NVChad.
2. Open the integrated terminal using :term.
3. Try running a command like nodejs, php, or apt.

Expected behavior:
The terminal should recognize fish-shell as the default shell and allow me to run commands like nodejs, php, apt, etc.

Environment:

• NVChad version: 2.5
• Shell: fish-shell
• Operating system: Linux Ubuntu

Any help or guidance would be appreciated!

[siduck]

Open the integrated terminal using :term.

that isnt nvchad's term at all .. Nvchad one has nvchad.term module

[BAD-WOLF]

Thanks for the response! However, the issue seems to be related to NVChad itself, not just the terminal. To clarify, I have the following configuration in my init.lua file:

{
    "mtoohey31/cmp-fish", 
    ft = "fish",  -- Load the plugin only for .fish files
    dependencies = { "hrsh7th/nvim-cmp" },  -- Ensure cmp is available
    config = function()
        local cmp = require('cmp')
        cmp.setup({
            sources = cmp.config.sources({
                { name = 'fish' }
            })
        })
    end
},

However, when trying to use the cmp-fish plugin, I am getting the following error:

Error detected while processing TextChangedI Autocommands for "*":
Error executing lua callback: Vim:E475: Invalid value for argument cmd: 'fish' is not executable

I also tried specifying the path to fish manually with the configuration below:

{ name = 'fish', option = { fish_path = "/usr/bin/fish" } }

But I still get the same error:

Error detected while processing TextChangedI Autocommands for "*":
Error executing lua callback: Vim:E475: Invalid value for argument cmd: '/usr/bin/fish' is not executable

What's strange is that the error also occurs directly in the terminal, as I showed in the video above. So it doesn't seem to be an issue with an additional plugin that I am trying to integrate, but rather with NVChad itself or how it is handling commands and the terminal.

Additional steps to reproduce:

1. Set up NVChad with the cmp-fish plugin.
2. Try using fish as the default shell in the integrated terminal.
3. Observe the error related to the command not being recognized.

Any further guidance would be greatly appreciated, as this issue affects the functionality of the terminal and the shell within NVChad.

[siduck]

those errors dont look nvchad related at all :/

please try your config on a saner OS, like linux

[BAD-WOLF]

Thank you for your suggestion!

I tried the configuration on a full Linux OS (Ubuntu), and it worked as expected. You can see the results in the attached screenshot.

However, I’m still interested in understanding why this setup didn’t work in WSL. Do you have any insight into why the behavior would differ between WSL and a full Linux environment? Any pointers would be greatly appreciated.

Thanks again for your help!

[siduck]

try with nvim --clean and does it work on :term command

[BAD-WOLF]

Thanks for the follow-up!

I tried running nvim --clean and used the :term command as suggested, but I encountered the same issue. Here’s the result:

It seems to be launching into the term://~//11:/bin/sh shell, which I didn’t expect. Do you have any insight on why it might be defaulting to this shell or how to change it to a different one like bash or fish?

It's no use trying to change the path even manually

[siduck]

so not a nvchad issue anymore. please ask in r/neovim

[BAD-WOLF]

Thanks for the suggestion, but I believe it might still be somewhat related to the NvChad configuration, as I just ran Neovim completely clean without any configuration (no init.vim or init.lua loaded), and it worked perfectly on the same WSL environment. Here's the result:

Given that, I would appreciate if you could test on your end using WSL as well, to see if the issue might be specific to that environment combined with NvChad.