@@ -9,7 +9,6 @@ CONTENTS *nvim-tree*
99 2. Quickstart | nvim-tree-quickstart |
1010 3. Commands | nvim-tree-commands |
1111 4. Setup/Configuration | nvim-tree-setup |
12- 4.1 Vinegar Style | nvim-tree-vinegar |
1312 5. Api | nvim-tree-api |
1413 6. Mappings | nvim-tree-mappings |
1514 7. Highlight Groups | nvim-tree-highlight |
@@ -1207,47 +1206,6 @@ Configuration for diagnostic logging.
12071206 | nvim-tree.filesystem_watchers | processing, verbose.
12081207 Type: `boolean ` , Default: `false`
12091208
1210- ==============================================================================
1211- 4.1 VINEGAR STYLE *nvim-tree-vinegar*
1212-
1213- | nvim_tree_vinegar | *nvim_tree_vinegar*
1214-
1215- nvim-tree can behave like vinegar. To allow this, you will need to configure
1216- it in a specific way:
1217-
1218- - Use `require" nvim-tree" .open_replacing_current_buffer ()` instead of the
1219- default open command.
1220- You can easily implement a toggle using this too:
1221- >
1222- local function toggle_replace()
1223- local view = require"nvim-tree.view"
1224- local api = require"nvim-tree.api"
1225- if view.is_visible() then
1226- api.tree.close()
1227- else
1228- require"nvim-tree".open_replacing_current_buffer()
1229- end
1230- end
1231- <
1232- - Use the `edit_in_place` action to edit files. It's bound to `<C-e> ` by
1233- default, vinegar uses `<CR> ` . You can override this with:
1234- >
1235- require"nvim-tree".setup {
1236- view = {
1237- mappings = {
1238- list = {
1239- { key = "<CR>", action = "edit_in_place" }
1240- }
1241- }
1242- }
1243- }
1244- <
1245- Going up a dir is bound to `- ` by default in nvim-tree which is identical to
1246- vinegar, no change is needed here.
1247-
1248- You'll also need to set | nvim-tree.hijack_netrw | to `true` during setup.
1249- A good functionality to enable is | nvim-tree.hijack_directories | .
1250-
12511209==============================================================================
12521210 5. API *nvim-tree-api*
12531211
0 commit comments