Open janvanveldhuizen opened 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
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.
Hmm... going back to v2.0. Plain v3.0 without any customization gives errors too. For example, when opening a file from the treeview
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...
@janvanveldhuizen show your custom config, also after v3.0 you must do lazy sync duh!
seems like you wrote wrong theme name :/
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.
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>