-
Notifications
You must be signed in to change notification settings - Fork 86
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
bug: 51a0794
do not respect aerial position
#369
Labels
bug
Something isn't working
Comments
Zeioth
changed the title
bug: 51a07949abf169b4cad30e14c165ac1ec0ce4e6f do not respect aerial position
bug: May 1, 2024
51a07949abf169b4cad30e14c165ac1ec0ce4e6f
do not respect aerial position
Zeioth
changed the title
bug:
bug: 51a0794 do not respect aerial position
May 1, 2024
51a07949abf169b4cad30e14c165ac1ec0ce4e6f
do not respect aerial position
Zeioth
changed the title
bug: 51a0794 do not respect aerial position
bug: May 1, 2024
51a0794
do not respect aerial position
If you have no time to look into this, reverting the commit would be enough to at least prevent users from breaking the UI. The mentioned commit seems to break |
Zeioth
added a commit
to Zeioth/aerial.nvim
that referenced
this issue
May 1, 2024
Zeioth
added a commit
to Zeioth/aerial.nvim
that referenced
this issue
May 1, 2024
Update window.lua → closes stevearc#369
stevearc
added a commit
that referenced
this issue
May 8, 2024
There was an edge case with "ignored" window types that would cause `:AerialOpen` in an ignored window to potentially open a second aerial win.
@stevearc I've tested the latest commit and all looks good thank you so much. I'm closing the issue too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Neovim version (nvim -v)
NVIM v0.9.5 Release
Operating system/version
arch
Output of :AerialInfo
Describe the bug
See post below
What is the severity of this bug?
minor (annoyance)
Steps To Reproduce
:Neotree
:AerialOpen
Expected Behavior
More info
Relevant commit
51a0794
The text was updated successfully, but these errors were encountered: