4 ms·
I have almost all of this in both emacs and vim and it only took me 5 years to get it just right.
by base698 10y ago
I have almost all of this in both emacs and vim and it only took me 5 years to get it just right.
- Asooka 10y agoCan you elaborate on how you handle the project thing? I really miss having the concept of "solution" and "project" in Vim from VS. Not just to have my files grouped logically in a $Project/{source,include}/blah.{h,cpp} tree, but also to be able to apply per-project settings like clang-complete options, etc. Right now I don't see a way to have e.g. three different projects that all build from the same files, but use different build options (mainly third-party sdk versions) and thus should give me different completions and code navigation.
- base698 10y agoPart of why I switched to emacs was something called helm: https://tuhdo.github.io/helm-intro.html https://tuhdo.github.io/helm-intro.html It fuzzy matches almost anything: files, function names, or commands Project grouping in the traditional sense can be done with projectile and NeoTree. http://projectile.readthedocs.io/en/latest/ http://projectile.readthedocs.io/en/latest/ https://github.com/jaypei/emacs-neotree/blob/dev/README.md https://github.com/jaypei/emacs-neotree/blob/dev/README.md I think what you are describing in the second half can be handled with company mode and triggering a major/minor mode off a file extension. https://www.gnu.org/software/emacs/manual/html_node/emacs/Major-Modes.html https://www.gnu.org/software/emacs/manual/html_node/emacs/Ma... http://company-mode.github.io http://company-mode.github.io If that's not it it's possible Googling will find exactly what you describe. People tend to port anything useful from any editor to emacs.