feat: emit YaziRenamedOrMoved event when files are renamed or moved #495
Conversation
This file contains 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
Problem ======= When files are renamed or moved in yazi, there is no way for other plugins to know about this. If the user uses yazi.nvim along with other plugins that need to react to files being renamed or moved, it cannot be done. This means that other plugins that depend on yazi cannot react to these changes. Currently yazi.nvim can only react to LSP delete/rename events, but plugins that operate outside of the LSP protocol are not supported. Solution ======== Add a new Neovim autocmd/event called `YaziRenamedOrMoved` that is emitted when files are renamed or moved. This event will contain a table of the paths that were renamed or moved. Previously we were already emitting a Neovim event for `YaziDDSHover` - now we have two custom events. Closes #494
This was referenced Jan 23, 2025
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.
Problem
When files are renamed or moved in yazi, there is no way for other plugins to know about this. If the user uses yazi.nvim along with other plugins that need to react to files being renamed or moved, it cannot be done. This means that other plugins that depend on yazi cannot react to these changes.
Currently yazi.nvim can only react to LSP delete/rename events, but plugins that operate outside of the LSP protocol are not supported.
Solution
Add a new Neovim autocmd/event called
YaziRenamedOrMovedthat is emitted when files are renamed or moved. This event will contain a table of the paths that were renamed or moved.Previously we were already emitting a Neovim event for
YaziDDSHover- now we have two custom events.Closes #494