Skip to content

pull#1

Open
sducomman wants to merge 256 commits into
sducomman:masterfrom
jdhao:main
Open

pull#1
sducomman wants to merge 256 commits into
sducomman:masterfrom
jdhao:main

Conversation

@sducomman

Copy link
Copy Markdown
Owner

No description provided.

jdhao added 30 commits August 2, 2024 06:23
- rearrange a few components
- add and remove a few components
In lazy.nvim, the `build` parameter accept value in different format.
If the value is
1. a string and starts with `:`, it will be treated as vim command
2. a string and starts without `:`, it will be treated as shell command
3. a function. Lazy.nvim will run this function

I compared closely between case 1 and case 3. In case 1, when lazy.nvim
runs the viml command, the runtimepath is already populated with the
current plugin we are trying to build.
However in case 3, the runtimepath is not populated with the plugin
path, which means that any command you run by this plugin is not
available.

So I did it in a hacky way to add the plugin path to runtimepath
manually, and source it manually using `:runtime` command. The `:
runtime` command is needed because in the init process, adding the
plugin path to runtimepath does not ensure that the script under this
plugin is sourced immediately. So if we want to use the command/function
immediately, we need to source it manually, see also neovim/neovim#29957.
The settings are copied from kevinhwang91/nvim-ufo#4 (comment),
with some modification.
1. For python and lua, rely on LSP for folding
2. show fold signs on the right of the number column
Only show fold signs for fold level below a certain level to avoid
clutter the left side columns with a lot of folding signs
`<cmd> `mapping must end with `<CR>`
The removed settings are already set by lazydev.nvim.
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.

6 participants