mirror of
https://github.com/neovim/neovim.git
synced 2025-02-25 18:55:25 -06:00
doc
This commit is contained in:
parent
f3056988ed
commit
a5358688bc
@ -124,8 +124,14 @@ include the kitchen sink... but you can use it for plumbing."
|
|||||||
==============================================================================
|
==============================================================================
|
||||||
2. Design decisions *design-decisions*
|
2. Design decisions *design-decisions*
|
||||||
|
|
||||||
Window
|
Jargon *dev-jargon*
|
||||||
|
|
||||||
|
Host ~
|
||||||
|
A plugin "host" is both a client (of the Nvim API) and a server (of an
|
||||||
|
external platform, e.g. python). It is a remote plugin that hosts other
|
||||||
|
plugins.
|
||||||
|
|
||||||
|
Window ~
|
||||||
The word "window" is commonly used for several things: A window on the screen,
|
The word "window" is commonly used for several things: A window on the screen,
|
||||||
the xterm window, a window inside Vim to view a buffer.
|
the xterm window, a window inside Vim to view a buffer.
|
||||||
To avoid confusion, other items that are sometimes called window have been
|
To avoid confusion, other items that are sometimes called window have been
|
||||||
@ -139,7 +145,6 @@ window View on a buffer. There can be several windows in Vim,
|
|||||||
together with the command line, menubar, toolbar, etc. they
|
together with the command line, menubar, toolbar, etc. they
|
||||||
fit in the shell.
|
fit in the shell.
|
||||||
|
|
||||||
|
|
||||||
Providers *dev-provider*
|
Providers *dev-provider*
|
||||||
|
|
||||||
A goal of Nvim is to allow extension of the editor without special knowledge
|
A goal of Nvim is to allow extension of the editor without special knowledge
|
||||||
|
@ -33,9 +33,15 @@ There are 3 ways to create a terminal buffer:
|
|||||||
- By editing a file with a name matching `term://(.{-}//(\d+:)?)?\zs.*`.
|
- By editing a file with a name matching `term://(.{-}//(\d+:)?)?\zs.*`.
|
||||||
For example:
|
For example:
|
||||||
>
|
>
|
||||||
:e term://bash
|
:edit term://bash
|
||||||
:vsp term://top
|
:vsplit term://top
|
||||||
<
|
<
|
||||||
|
Note: The "term://" pattern is handled by a BufReadCmd handler, so the
|
||||||
|
|autocmd-nested| modifier is required to use it in an autocmd. >
|
||||||
|
autocmd VimEnter * nested split term://sh
|
||||||
|
< This is only mentioned for reference; you should use the |:terminal|
|
||||||
|
command instead.
|
||||||
|
|
||||||
When the terminal spawns the program, the buffer will start to mirror the
|
When the terminal spawns the program, the buffer will start to mirror the
|
||||||
terminal display and change its name to `term://$CWD//$PID:$COMMAND`.
|
terminal display and change its name to `term://$CWD//$PID:$COMMAND`.
|
||||||
Note that |:mksession| will "save" the terminal buffers by restarting all
|
Note that |:mksession| will "save" the terminal buffers by restarting all
|
||||||
|
Loading…
Reference in New Issue
Block a user