fix(filesystem): follow_current_file logic error#2053
Merged
Conversation
pynappo
approved these changes
Jun 27, 2026
pynappo
left a comment
Collaborator
There was a problem hiding this comment.
i'll merge b/c obviously the logic i wrote there was wrong, but for future reference can you write the reproduction steps needed to reproduce the issue? would be nice to have a test case to cover any future regressions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Neotree did not
follow_current_filein my neovim setup anymore, same thing happening to a colleague using Neotree.I let a LLM investigate and apparently the bug is that "not" is stronger binding than comparison, so the line
The suggested fix solved the problem for me.