Skip to content

fix(setup): explicitly specify path to hijack when possible #1718

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

Merged
merged 1 commit into from
Mar 9, 2025

Conversation

pynappo
Copy link
Collaborator

@pynappo pynappo commented Mar 9, 2025

Closes #1717

@pynappo pynappo changed the title fix(hijack): explicitly specify path to hijack when possible fix(setup): explicitly specify path to hijack when possible Mar 9, 2025
@pynappo pynappo force-pushed the fix-lazy-hijacking branch from 67b002d to 9be66db Compare March 9, 2025 02:23
@pynappo pynappo force-pushed the fix-lazy-hijacking branch from 9be66db to 9332d2e Compare March 9, 2025 02:23
@pynappo pynappo merged commit 40dd577 into nvim-neo-tree:main Mar 9, 2025
8 checks passed
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

Successfully merging this pull request may close these issues.

BUG: Neo-tree doesn't hijack the first :e command on lazy-load
1 participant