-
Notifications
You must be signed in to change notification settings - Fork 40
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
Refactor code: Update minimum requirements to nvim 0.7 #151
Conversation
f8c8585
to
988a8c6
Compare
@saccarosium can you create a separate PR for the function encode issue? So we can merge that now, and merge the breaking stuff later. |
988a8c6
to
81f239f
Compare
@savq I've added some of the commits I've been working on my other branch. I felt that this changes made this PR more solid putting it in a better shape. |
Instead of having of having a separate key to evaluate if the directory is installed or not I've made the following changes to status enum: - INSTALLED: equivalent to the old exists key - LISTED: a package is in the paq list but it isn't yet been installed - CLONED: equivalent to what installed used to mean, a package was recently cloned (aka installed) on the machine. Also to simplify the filtering of packaging based on the status I've made a new table called 'filters' that help filter packages both in 'vim.tbl_filter' and regular if statements.
4db6cb4
to
9b65baf
Compare
Instead of saving the state on the function 'exe_op' I save the state on every individual function that alter the state. I find this to be more reliable.
@savq I think we need to merge our PRs into a separate branch for now and test there the changes there. |
Yes. I'll merge this to |
This PR does the following:
.editorconfig
: for better style consistency (supported natively in neovim 0.9)paq
methodfilter
table to make it more easy filter packages