zbirenbaum / nvterm

NvChad's Official Terminal Plugin ( Unmaintained but still usable and stable), wait for v3.0
GNU General Public License v3.0
178 stars 21 forks source link

Can't open a terminal #58

Open janvanveldhuizen opened 11 months ago

janvanveldhuizen commented 11 months ago

As soon as I use Space-H, this error message is displayed:

E5108: Error executing lua: ...an/.local/share/nvim/lazy/nvterm/lua/nvterm/termutil.lua:2 2: attempt to index field 'type_opts' (a nil value)
stack traceback:
...an/.local/share/nvim/lazy/nvterm/lua/nvterm/termutil.lua:22: in function 'exec ute_type_cmd'
...an/.local/share/nvim/lazy/nvterm/lua/nvterm/terminal.lua:46: in function 'crea te_term_window'
...an/.local/share/nvim/lazy/nvterm/lua/nvterm/terminal.lua:116: in function 'new '
/home/jan/.config/nvim/lua/core/mappings.lua:355: in function </home/jan/.config/ nvim/lua/core/mappings.lua:354>

siduck commented 11 months ago

hi @janvanveldhuizen i'm no longer maintaining nvterm as i didnt write any code of it, hence it became hard to maintain for me.

Can you use nvchad v3.0 branch? its using a custom term module which i recently made

janvanveldhuizen commented 11 months ago

Took the v3.0 branch. Terminal worked fine, until I restored my custom lua's. So I have to sort out what I did wrong there. Never mind, I'll try to figure this out myself.

image

janvanveldhuizen commented 11 months ago

Hmm... going back to v2.0. Plain v3.0 without any customization gives errors too. For example, when opening a file from the treeview image

janvanveldhuizen commented 11 months ago

I think I found where the problem starts. All my custom stuff runs fine, until I try to add a custom highlights. So I forget about that. It's not worth spending so much time on just the color of a comment line...

siduck commented 11 months ago

@janvanveldhuizen show your custom config, also after v3.0 you must do lazy sync duh!

siduck commented 11 months ago

seems like you wrote wrong theme name :/

janvanveldhuizen commented 11 months ago

I discovered that the error can be solved by changing the theme using Space-th and back. In the weekend I'll try to write down how exactly to reproduce the issue.