Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open a terminal #58

Open
opa-jan opened this issue Oct 2, 2023 · 7 comments
Open

Can't open a terminal #58

opa-jan opened this issue Oct 2, 2023 · 7 comments

Comments

@opa-jan
Copy link

opa-jan commented Oct 2, 2023

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
Copy link
Collaborator

siduck commented Oct 3, 2023

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

@opa-jan
Copy link
Author

opa-jan commented Oct 4, 2023

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

@opa-jan
Copy link
Author

opa-jan commented Oct 4, 2023

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

@opa-jan
Copy link
Author

opa-jan commented Oct 4, 2023

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
Copy link
Collaborator

siduck commented Oct 5, 2023

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

@siduck
Copy link
Collaborator

siduck commented Oct 5, 2023

seems like you wrote wrong theme name :/

@opa-jan
Copy link
Author

opa-jan commented Oct 5, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants