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 file with NvimTree when LeetCode is open. #166

Open
shaojunjie0912 opened this issue Feb 25, 2025 · 2 comments
Open

Can't open file with NvimTree when LeetCode is open. #166

shaojunjie0912 opened this issue Feb 25, 2025 · 2 comments

Comments

@shaojunjie0912
Copy link

Hello, thank you for your contribution to this project. While using the leetcode plugin, I may have encountered an issue related to opening files. The specific situation is as follows:

First, I entered nvim leetcode.nvim in the terminal to open the LeetCode plugin page.

Image

Then, I used Ctrl+n (which is the shortcut I configured to open the NvimTree plugin) to open the NvimTree panel on the left.

Image

However, when I selected a file and pressed Enter, nothing happened, and the cursor automatically jumped to the LeetCode main page on the right. Could you please help me understand why this is happening?

Image

@New9c
Copy link
Contributor

New9c commented Mar 12, 2025

Not the main guy who made this, but I can make a guess:
I have a plugin called oil.nvim (it's like NvimTree but better XD)
If I do Space+o I get this:

Image

If you fork the repo, you can try git grep winfixbuf:

Image
I believe the creators don't want you to switch buffers, and since Leetcode questions are all individual problems, there isn't a good reason for switching to another file out of the blue.

If you want to continue doing say problem 2, you can go to Menu > Problems > List, then type 2.
Hope this helps!

@shaojunjie0912
Copy link
Author

Thanks for your reply. I will have a try!

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