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

Feature Request: Emit autocmd event on tag updates #73

Closed
Subjective opened this issue Jul 6, 2023 · 1 comment
Closed

Feature Request: Emit autocmd event on tag updates #73

Subjective opened this issue Jul 6, 2023 · 1 comment

Comments

@Subjective
Copy link
Contributor

Hi, thanks for the great plugin! As others have already mentioned, I've been enjoying using grapple for file navigation as it seems quite polished for purpose, compared to its counterpart harpoon which has a lot of extras I don't use.

While I'm mostly satisfied with the experience, I was wondering if it would it be possible to emit an autocmd event every time tags are added/deleted/toggled/reset? It would be really helpful for integrating grapple into a statusline plugin like heirline, which updates based on events rather than a time interval.

Thanks again, and have a nice day :)

@cbochs
Copy link
Owner

cbochs commented Feb 26, 2024

@Subjective Thanks for the suggestion and all the PRs! Apologies, I haven't had time to work on this project for a while.

I've been working on a rewrite. It will include an event like this. For now, I'm happy to merge your PR. However, I would suggest using the name GrappleUpdate.

Also, feel free to try out the branch rewrite, if you're interested! 🙂 Please note, there are breaking changes in the file format so your previous tags won't be loaded (not deleted, however). Also, the user command has been updated:

GrappleTag -> Grapple tag
GrappleUntag -> Grapple untag
GrappleToggle -> Grapple toggle
GrapplePopup tags -> Grapple open_tags

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 a pull request may close this issue.

2 participants