FastFold VS vim-rooter

Just be aware that the marker based folding can be annoying to collaborators if you are working on documents with other authors. With a plugin like FastFold [0] you should be able to have fast folding with the expr foldtype.

[0]: https://github.com/Konfekt/FastFold

If you don't get great results, try changing 'foldmethod' (syntax is usually best but indent often works well). If vim doesn't have syntax support for your language, find a plugin that offers it. Even better if it defines 'foldtext' so your methods collapse down into an easy to read outline. I use vim-ficklefold to manage folds and FastFold to prevent syntax folds from making vim slow.

FastFold

Could be foldmethod=syntax that's slow, try FastFold.

FastFold, fauxClip, syntaxMarkerFold

I have have the same problem. I found this plugin FastFold that seems to be what we are looking for but I haven't had the chance to test it yet. The general idea is to stop autofolding under most circumstances except when it makes sense.

Check out FastFold plugin

Because in this case the way this plugin works causes folds to recomputed. Fold methods syntax and expr are slow, cause those are written in Vim script instead directly in C. Plugin FastFold lets you change this behaviour and update folds only on demand.

Some of those rules can be quite heavy on large files, so FastFold really helps here. It also prevents uncontrolled folds opening when editing, so just added bonus. Another plus are temporary manual folds.

This or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.

maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim

The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:

It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.

An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter

I just use rooter and avoid thinking about it...

There's vim-rooter, which is great.

No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.