You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Details
Bug report: #111
After the transition to initialization through the plugin directory we
essentially made the plugin configuration dependent on initialization
order. Whichever thing happens to call the setup function last
determines the configuration.
This works for plugin managers like lazy.nvim since the plugin directory
is run before the user calls setup, so user settings will override the default.
However this is not the case for vim-plug which runs setup before the plugin
directory. Side not, I believe this is the way neovim is meant to work and
lazy.nvim / other managers change this ordering.
To fix this I have modified the main setup function to pick up the last
non empty configuration.
That way if plugin first runs like with lazy.nvim any later calls to setup
by the user will override the configuration, there is no need to re-initialize
if an empty configuration is supplied.
Now if setup runs first it'll initialize the state and since the plugin
directory provides an empty configuration it will be skipped instead of
overwriting the user supplied configuration.
- Pre-compute concealed data once per parse cycle [fcd908b](https://github.com/MeanderingProgrammer/markdown.nvim/commit/fcd908bafb96e4a30abe7bf8f502790b93ea85ac)
- Improve table parsing performance by storing state [4d046cd](https://github.com/MeanderingProgrammer/markdown.nvim/commit/4d046cdf65393a62c0eb209e01574b39f28bc01b)
30
+
- Improve performance of showing / hiding marks by storing mark id [ef0c921](https://github.com/MeanderingProgrammer/markdown.nvim/commit/ef0c921858cbe079d40304200af60b6ce0c99429)
31
+
- Hide code block background based on language [#110](https://github.com/MeanderingProgrammer/markdown.nvim/issues/110)
0 commit comments