| Commit message (Collapse) | Author | Age |
|\
| |
| | |
vim-patch:7.4.{1893,1895}
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Cannot use a window ID where a window number is expected.
Solution: Add LOWEST_WIN_ID, so that the window ID can be used where a
number is expected.
https://github.com/vim/vim/commit/888ccac8902cee186fbd47e971881f6d9b19c068
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Cannot easily get the window ID for a buffer.
Solution: Add bufwinid().
https://github.com/vim/vim/commit/b3619a90eae2702553ff9494ecc4c9b20c13c224
|
|\ \
| | |
| | | |
vim-patch: 7.4.2158, 2162, 2205
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: 'wildignore' always applies to getcompletion().
Solution: Add an option to use 'wildignore' or not. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/e9d58a6459687a1228b5aa85bd7b31f8f1e528a8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Result of getcompletion('', 'sign') depends on previous
completion.
Solution: Call set_context_in_sign_cmd(). (Dominique Pelle)
https://github.com/vim/vim/commit/7522f6982197f83a5c0f6e9af07fb713934f824a
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Result of getcompletion('', 'cscope') depends on previous
completion. (Christian Brabandt)
Solution: Call set_context_in_cscope_cmd().
https://github.com/vim/vim/commit/b650b9878e9f0ac6bb1b61230095ad9ab3850a33
|
|\ \ \
| | | |
| | | | |
vim-patch: 7.4.1765, 7.4.1714
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Undo options are not together in the options window.
Solution: Put them together. (Gary Johnson)
https://github.com/vim/vim/commit/4694a17d1ec08382f996990a7fac1ac60197ec81
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Non-GUI specific settings in the gvimrc_example file.
Solution: Move some settings to the vimrc_example file. Remove setting
'hlsearch' again. (suggested by Hirohito Higashi)
https://github.com/vim/vim/commit/54f1b7abf8c48b1dd997202258d1d0673ed4bd29
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Check `exists('b:term_title')` to avoid the BufReadCmd for already-initialized
:terminal buffers.
Move the test for `:argadd`.
Add a test for `:edit<CR>`.
Tweak comments and code style.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Closes #4784
|
| | | | |
| | | | |
| | | | | |
yuck
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Command line completion on "find **/filename" drops sub-directory.
Solution: Handle this case separately. (Harm te Hennepe, closes vim/vim#932, closes
vim/vim#939)
https://github.com/vim/vim/commit/73d4e4c8922f6f4d256f910a18f47c0c3a48c28b
|
| | | | |
| | | | |
| | | | |
| | | | | |
Followup for #5461
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | | |
ui: Fix the call to utf_ambiguous_width
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`utf_ambiguous_width` expects the Unicode character, but in 9e1c6596 I
just passed the first UTF-8 byte to the function. This led to various
display problems because now many multi-cell characters weren't falling
into that part of the branch.
Also, to better align with the existing Vim code, remove the forced
cursor update. Setting the flag will cause it to happen in the next
UI_CALL.
Thanks to qvacua for all the help investigating the issue!
Closes #5448
|
|\ \ \ \ \
| | | | | |
| | | | | | |
build: prevent in-tree builds for the time being, as it's not supported
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix generated files for in-tree build.
|
| |/ / / / / |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
term_write(): Skip writes if stream was closed.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If the backing stream for a :terminal was closed (e.g. if the shell exits
unexpectedly) there may be pending input on the loop which will be processed
before the terminal close event (which is queued on the same loop).
terminal_send checks term->closed but this does not reflect the state of the
underlying streams. The terminal.c module in fact has no knowledge of the
streams (this seems intentional: it is abstracted as TerminalOption.write_cb).
The SIGCHLD handler (pty_process_unix.c) is executed immediately, and it
triggers a stream teardown so Stream.closed=false (TerminalJobData.in.closed).
When the pending writes are handled by eval.c:term_write, wstream_write() aborts
because it sees the closed Stream.
To avoid that, this commit checks Stream.closed in eval:term_write() before writing
to the WStream. (As hinted above, we cannot do this in terminal:terminal_send()
because that module cannot inspect the underlying streams.)
References #5445
https://github.com/neovim/neovim/pull/5445#issuecomment-252529766
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
References #5445
See https://github.com/neovim/neovim/pull/5445#issuecomment-252529766
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
window: Fix cmd_with_count's formatting when sizeof(long) != 8
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On architectures where `sizeof(long)` != 8, "%" PRId64 will read junk from
memory. This was seen on various Debian builds where
test/functional/legacy/close_count_spec.lua would fail due to `1<C-w>c`
emitting an error like `E488: Trailing characters: close-87944975647104`.
Changing the `Prenum` parameter to int64_t ensures it is safe to use
`"%" PRId64`, and make another small step towards removal of the use of
`long`.
|
|\ \ \ \
| | | | |
| | | | | |
vim-patch:7.4.1549
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Test for syntax attributes fails in Win32 GUI.
Solution: Use an existing font name.
https://github.com/vim/vim/commit/c835293d54c223627c7d4516ee273c21a3506fa1
|
|\ \ \ \
| | | | |
| | | | | |
Makefile: add PREFIX variable
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We use a Makefile which in turn uses cmake. If we wanted to set the install
prefix for cmake, we had to do this so far:
make CMAKE_FLAGS="-DCMAKE_INSTALL_PREFIX=/tmp/nvim"
That's long and hard to remember. Following the conventions of other Makefiles,
this now works as well and is equivalent:
make PREFIX=/tmp/nvim
|
|\ \ \ \ \
| | | | | |
| | | | | | |
config: Allow setting USERNAME/HOSTNAME from the environment
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Allowing this to be controlled externally improves reproducibility, as
well as provides a more useful address to report for "Compiled by". For
example, I intend to set it to the packaging list when building the
Debian package.
Signed-off-by: James McCoy <jamessan@jamessan.com>
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
updated runtime files. Add avra syntax.
https://github.com/vim/vim/commit/0c1ff16b5467f97ce08134fdbc8198127bbe492a
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Updated runtime files.
https://github.com/vim/vim/commit/939a1abe935a539f2d4c90a56cb0682cbaf3bbb0
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
Add missing test file.
https://github.com/vim/vim/commit/8067a64852d6d134b493c5674e404225ed4bbe7d
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If multiple versions of a package are installed, the provider health check could
choose a wrong path:
/usr/local/lib/python3.5/site-packages/neovim-0.1.10-py3.5.egg-info/PKG-INFO
/usr/local/lib/python3.5/site-packages/neovim-0.1.9-py3.5.egg-info/PKG-INFO
Prior to this change :CheckHealth could falsely show 0.1.9 as the installed
version, since glob() doesn't enforce any predictable order.
Now we sort all potential paths numerically in descending order and just look at
the first path instead.
|
| | | | |
|
| |_|/
|/| | |
|
|\ \ \
| | | |
| | | | |
Fix Python 2/3 health checks
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
It's the same as the declaration above it, but hardcoded to use python3
and does not redirect stderr.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
unibi_format() calls out() multiple times for a given format string.
When data->buf fills up during this process, flush_buf() gets called,
which possibly calls unibi_out() again to toggle the cursor visibility.
However, if we were halfway through outputting an escape sequence, doing
this will clobber it, resulting in junk being displayed.
Fix this by not toggling the cursor visibility when draining a full
buffer in out().
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
NA list:
1653: matchit packadd
1750: channel
1770: termguicolors
1794: GUI Win32
1805: Makefile
1804, 1945: manpager.vim
1811: channel
2115, 2232, 2278, 2319: defaults.vim
included:
1763: spell
|
| | | |
|