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

feat: GH-44 lock marks when saving #53

Merged
merged 3 commits into from
Apr 25, 2024

Conversation

primeapple
Copy link
Collaborator

Use lockmarks in write command to keep [ and ] marks after saving.

Thanks @simonmandlik

@primeapple primeapple self-assigned this Apr 19, 2024
@okuuva
Copy link
Owner

okuuva commented Apr 23, 2024

This is a great addition, but I think it should be a configuration option which defaults to false. My reasoning being that a manual save doesn't lock marks either by default.

@primeapple primeapple changed the title fix: GH-44 lock marks when saving feat: GH-44 lock marks when saving Apr 24, 2024
@primeapple
Copy link
Collaborator Author

I changed it accordingly and made it an options. Thanks for the feedback.
I wonder at which point do we let the user to specify the save command themselves... :D

Copy link
Owner

@okuuva okuuva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one suggestion on the wording in the documentation. I don't have strong feelings about it though so feel free to ignore if you feel like the original was better. Other than that LGTM!

README.md Outdated Show resolved Hide resolved
lua/auto-save/config.lua Outdated Show resolved Hide resolved
@primeapple primeapple merged commit fddbf38 into main Apr 25, 2024
2 checks passed
@primeapple primeapple deleted the fix-GH-44-keep-marks-when-saving branch April 25, 2024 06:34
@okuuva okuuva mentioned this pull request Apr 25, 2024
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 this pull request may close these issues.

2 participants