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

Allow pinning of buffers #44

Open
leath-dub opened this issue Nov 21, 2024 · 3 comments
Open

Allow pinning of buffers #44

leath-dub opened this issue Nov 21, 2024 · 3 comments

Comments

@leath-dub
Copy link
Owner

leath-dub commented Nov 21, 2024

I am thinking about adding a kind of harpoon like feature where you can pin buffers/files and save them after close.

Maybe this list is in a separate menu but you can also set an option to auto open those pinned files so they are accessible in the main menu.

Feel free to add musings/thoughts below.

@omerdn1
Copy link

omerdn1 commented Nov 25, 2024

Love this! I'd like to see an implementation that utilizes the native session API instead of saving the routes to file, which is how harpoon has been doing things, and it proved to be slow at scale.

@leath-dub
Copy link
Owner Author

Love this! I'd like to see an implementation that utilizes the native session API instead of saving the routes to file, which is how harpoon has been doing things, and it proved to be slow at scale.

I have not heard of this ! gonna look into this.

@leath-dub
Copy link
Owner Author

Love this! I'd like to see an implementation that utilizes the native session API instead of saving the routes to file, which is how harpoon has been doing things, and it proved to be slow at scale.

After reading about sessions I think something like the following would be just as efficient at it is dead simple.

We have a .snipe file which we could check for in the current directory or recursively upwards. It holds contents like this:

lua/snipe/menu.lua:0:3
README.md:3:10

Just have to figure out how to save cursor position and output it like this.

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

No branches or pull requests

2 participants