Difference between revisions of "Neovim"
Jump to navigation
Jump to search
(Created page with "Category:SoftwareCategory:editorCategory:textCategory:ideCategory:vim {|<!--CONFIGURATION: REQUIRED--> |{{#vardefine:app|neovim}} |{{#vardefine:url|https:/...") |
Moskalenko (talk | contribs) m (Text replacement - "#uppercase" to "uc") |
||
| Line 24: | Line 24: | ||
Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application. | Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application. | ||
==System Variables== | ==System Variables== | ||
| − | * HPC_{{ | + | * HPC_{{uc:{{#var:app}}}}_DIR - installation directory |
<!--Configuration--> | <!--Configuration--> | ||
{{#if: {{#var: conf}}|==Configuration== | {{#if: {{#var: conf}}|==Configuration== | ||
Revision as of 21:23, 6 December 2019
Description
Neovim is literally the future of Vim. Neovim is an extension of Vim: feature-parity and backwards-compatibility are high priorities. If you already use Vim, see :help nvim-from-vim to learn about the differences. GUIs can nvim --embed or communicate via named pipe using the discoverable msgpack API. The msgpack API enables structured communication to and from any programming language. Remote plugins run as co-processes that communicate with Neovim safely and asynchronously.
Environment Modules
Run module spider neovim to find out what environment modules are available for this application.
System Variables
- HPC_NEOVIM_DIR - installation directory