| Commit message (Collapse) | Author | Age |
... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
It wasn't even hooked up to anything... must have been removed when
term.c was replaced.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added: TermOpen autocmd
Added: terminal mode (un)map commands
Options and commands not available in neovim ('cp' and variants, termcap
options, :shell, :fixdel) are highlighted as errors. Previously deleted
entries were restored.
Co-authored-by: Felipe Morales <hel.sheep@gmail.com>
|
|/ / /
| | |
| | |
| | |
| | | |
DecodeHook isn't needed since neovim/python-client#53
rpc methods won't pass bytes anymore, ref neovim/python-client#129
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'guioptions' is mentioned in the "Option Defaults" section of vim_diff,
and while its default did indeed change, it was only because the 't'
flag was removed. To make that clear, move its reference to the
"Removed Features" section instead.
Remove stray instance of 't' flag from GO_ALL. Most if not all of the
GO_* #defines are unused, but lets keep them for now as it's not clear
whether they won't be used by Nvim GUIs.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This also removes the 't' flag from 'guioptions'.
Side effect: :term[inal] -> :te[rminal]
Closes #3003.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
```
updated for version 7.4.668
Problem: Can't use a glob pattern as a regexp pattern.
Solution: Add glob2regpat(). (Christian Brabandt)
```
https://code.google.com/p/vim/source/detail?r=v7-4-668
|
| |/
|/|
| |
| |
| | |
This makes it possible to register a lazy loaded host in a plugin/ file.
Previously this caused an error on restart after :UpdateRemotePlugins
|
| |
| |
| |
| |
| |
| | |
Nvim has no direct integration with X.
Helped-by: Florian Walch <florian@fwalch.com>
|
| |
| |
| |
| |
| | |
This is primarily low-hanging fruit; there are still many references to
things such as MS-DOS throughout (see os_dos.txt).
|
| |
| |
| |
| | |
Nvim hasn't ever had X11 integration, so this has was never needed.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Presumably due to tarruda's unifdefing, it was already a no-op at the
time of nvim's first commit.
It's probably better to be clear that it doesn't exist, as opposed to
users thinking `:set guipty` is doing something when it isn't.
|
| |
| |
| |
| | |
We've never had an X11 GUI.
|
| | |
|
| |
| |
| |
| |
| | |
Using e.g. a Linux distribution's package manager should be preferred
over installing the `neovim` Python modules with `pip`.
|
| | |
|
|/
|
|
|
| |
Because of recent work on defaults (see
https://github.com/neovim/neovim/issues/2676)
|
| |
|
|
|
|
|
|
|
| |
Re: compatibility issues with users doing `:so
$VIMRUNTIME/macros/matchit.vim`
Fixes #2918
|
|
|
|
|
| |
- It's severely outdated
- We already have (up to date) installation instructions on the wiki
|
|
|
|
|
|
| |
Fixes #2712
Helped-By: Michael Reed <m.reed@mykolab.com>
|
|
|
|
| |
Helped-By: Justin M. Keyes <justinkz@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
refs #2895
Helped-by: Bohr Shaw <pubohr@gmail.com>
Helped-by: Justin M. Keyes <justinkz@gmail.com>
[ci skip]
|
|
|
|
|
|
| |
In general, attempt to make things more concise.
Reviewed-by: Michael Reed <m.reed@mykolab.com>
|
| |
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
| |
|
|
|
|
|
|
| |
Also update the documentation regarding the option.
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
|
|
| |
This also updates the documentation about 'incsearch'.
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
|
|
| |
"i" could slow down the completion.
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
Also, some documentation changes.
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The executable 'python' can refer to either Python 2 or Python 3. Add a
check to only accept Python 2 interpreters as providers for +python.
Also improve the error messages.
Resolves #2734.
|
|
|
|
| |
Ref: https://github.com/blueyed/neovim/commit/9b653ce0#commitcomment-11195449
|
|
|
|
|
|
|
|
| |
I could not find a reference to NVIM_PYTHON_PYTHON_LOG anywhere, and
python-client looks for NVIM_PYTHON_LOG_FILE.
~/.nvimlog appears to be hardcoded and enabled by default. This would
need to be adjusted when this changes.
|