#nerdtree — Public Fediverse posts

Installing NERDTree Is Simpler As You Might Think

https://hiddenalpha.ch/slnk/id/1:6185e48

#vi #vim #NERDTree #plugin

Trying out #HelixEditor after years in #Vim / #NeoVIM and I find myself really missing #nerdtree. After doing some digging apparently tree based file pickers are kicking the hornets nest and most suggest using a file browser like #yazi in another #tmux pane or something.

Anybody know a quick way to open a file in a new vsplit or h split in an existing helix session?

Fuzzy pickers are great but sometimes I just need a tree view.

Not sure when it happened, but opening a finder window today felt kinda unfamiliar, as I transitioned to shell, nerdtree and vifm, full time. Strange Realisation.

#macos #finder #filemanager #vifm #nerdtree

Not sure when it happened, but opening a finder window today felt kinda unfamiliar, as I transitioned to shell, nerdtree and vifm, full time. Strange Realisation.

#macos #finder #filemanager #vifm #nerdtree

Today I've disabled #NeoTree and just hacked a #lua #NERDTree configuration. NeoTree came bundled with #LazyVim, but I find its defaults to be such a pain. The uppercase H key should always be "top of buffer", not "show hidden files". It doesn't have a good workflow for moving files. When I open it in a gitignored folder such as node_modules, it refused to show anything by default. The list of grievances is too big. I've tried to configure it to my liking, but I failed.

[1/5]

Here are the #vim / #neovim plugins I currently use. My plugin manager is plugged. I know there are more "modern" ones, but plugged works just fine so why change it.

*WORKING WITH FILES*

ctrlpvim/ctrlp.vim – a fuzzy finder for files, buffers, mru, tags etc. This is how I mostly open and switch files/buffers. (It's so much faster than #nerdtree!)

airblade/vim-rooter - changes the cwd to the project dir of the current file. When I'm not using #ctrlp, I'm using…

[1/5]

Here are the #vim / #neovim plugins I currently use. My plugin manager is plugged. I know there are more "modern" ones, but plugged works just fine so why change it.

*WORKING WITH FILES*

ctrlpvim/ctrlp.vim – a fuzzy finder for files, buffers, mru, tags etc. This is how I mostly open and switch files/buffers. (It's so much faster than #nerdtree!)

airblade/vim-rooter - changes the cwd to the project dir of the current file. When I'm not using #ctrlp, I'm using…

[1/5]

Here are the #vim / #neovim plugins I currently use. My plugin manager is plugged. I know there are more "modern" ones, but plugged works just fine so why change it.

*WORKING WITH FILES*

ctrlpvim/ctrlp.vim – a fuzzy finder for files, buffers, mru, tags etc. This is how I mostly open and switch files/buffers. (It's so much faster than #nerdtree!)

airblade/vim-rooter - changes the cwd to the project dir of the current file. When I'm not using #ctrlp, I'm using…

[1/5]

Here are the #vim / #neovim plugins I currently use. My plugin manager is plugged. I know there are more "modern" ones, but plugged works just fine so why change it.

*WORKING WITH FILES*

ctrlpvim/ctrlp.vim – a fuzzy finder for files, buffers, mru, tags etc. This is how I mostly open and switch files/buffers. (It's so much faster than #nerdtree!)

airblade/vim-rooter - changes the cwd to the project dir of the current file. When I'm not using #ctrlp, I'm using…

[1/5]

Here are the #vim / #neovim plugins I currently use. My plugin manager is plugged. I know there are more "modern" ones, but plugged works just fine so why change it.

*WORKING WITH FILES*

ctrlpvim/ctrlp.vim – a fuzzy finder for files, buffers, mru, tags etc. This is how I mostly open and switch files/buffers. (It's so much faster than #nerdtree!)

airblade/vim-rooter - changes the cwd to the project dir of the current file. When I'm not using #ctrlp, I'm using…

That's an interesting thought: This article suggests that you shouldn't use a file tree sidebar (e.g. #NerdTree) in #Vim (or #Neovim), because it's not really compatible to a multi-window workflow. Because it can be confusing to predict in which window the file will actually open.

Instead, the author suggests that you display the files (or file tree) not in a sidebar, but to replace a window's content with a file picker, and after selecting the file, open it there, too.

http://vimcasts.org/blog/2013/01/oil-and-vinegar-split-windows-and-project-drawer/

Ich hatte gehofft, mir könnte der in #emacs integrierte Dateimanager #dired genügen. Leider nicht, denn jeder Verzeichniswechsel öffnet einen neuen Buffer. Bedeutet, durch 10 Verzeichnisse navigiert und 9 weitere Buffer sind im Hintergrund aktiv. Keine Ahnung, wie man auf die Idee kommt, dies könnte eine gute sein. In meinen Augen Schwachsinn. Muss ich mich doch mit #nerdtree oder ähnliches befassen.

@governa you can also use ranger in #vim #neovim as a replacement for #NERDTree or netrw with the plugin: https://github.com/Mizuchi/vim-ranger.

shitpost aside, using gvim for the day showed me how I often I ^Z back to the shell when using vim to do file stuff, which all would be totally possible to do in vim itself.
So I tweaked my #FZF + #NERDTree-setup a bit and will continue to get more used to it.

NERDTree is a #vim plugin that creates a project browsing tree that is easy to use. For beginners it is the most similar to modern IDE file explorers (vim power users use netrw).

Movement is the same as a regular vim buffer. Files, sym-links, executable files, and directories are highlighted differently and can be bookmarked for quick access.

Checkout ":help NERDTree" for more info or press "?" inside a NERDTree buffer for help.

https://github.com/preservim/nerdtree

Day 6 - #100DaysToOffload

#nerdtree

Acá sigo, actualizando las notas de mi #tesis desde #vim con #nerdtree y algo de tunning personalizado :D