| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
Problem: Undefined behavior when using backslash after empty line.
Solution: Check for an empty line. (Dominique Pelle, closes vim/vim#1631)
https://github.com/vim/vim/commit/478af67dd6a9adc456464c3736bda328ae3a28cb
|
|
|
|
|
|
|
| |
Problem: Using :change in between :function and :endfunction fails.
Solution: Recognize :change inside a function. (ichizok, closes vim/vim#1374)
https://github.com/vim/vim/commit/70bcd7336f9f19304f32c52a86ed5b4b3de852c2
|
|
|
|
|
|
|
| |
Problem: Tests use assert_true(0) and assert_false(1) to report errors.
Solution: Use assert_report().
https://github.com/vim/vim/commit/37175409d766ce67f2548dffa6d73451379b5737
|
|
|
|
|
|
|
| |
Problem: The client-server test may hang when failing.
Solution: Set a timer. Add assert_report()
https://github.com/vim/vim/commit/42205551b140bee8b419b24abe210f56bb80b35e
|
|
|
|
|
|
|
| |
Problem: Sometimes VimL is used, which is confusing.
Solution: Consistently use "Vim script". (Hirohito Higashi)
https://github.com/vim/vim/commit/b544f3c81f1e6a50322855681ac266ffaa8e313c
|
|
|
|
|
|
|
| |
Problem: Still some float functionality is not covered by tests.
Solution: Add more tests. (Dominique Pelle, closes vim/vim#1364)
https://github.com/vim/vim/commit/872004132f25cabe59352912889e042d6c7e6b4e
|
|
|
|
|
|
|
|
| |
Problem: str2nr() and str2float() do not always work with negative values.
Solution: Be more flexible about handling signs. (LemonBoy, closes vim/vim#1332)
Add more tests.
https://github.com/vim/vim/commit/08243d26d22ad44a857d02c90071578577b8a55d
|
|
|
|
|
|
|
|
|
| |
Problem: On MS-Windows some float functions return a different value when
passed unusual values. strtod() doesn't work for "inf" and "nan".
Solution: Accept both results. Fix str2float() for MS-Windows. Also
reorder assert function arguments.
https://github.com/vim/vim/commit/6247361101dcccc0c877e90ad67cd0cc83df7c68
|
|
|
|
|
|
|
| |
Problem: Several float functions are not covered by tests.
Solution: Add float tests. (Dominique Pelle)
https://github.com/vim/vim/commit/453b576ee5d32e9b8e6876712748ae01f9be68dd
|
| |
|
| |
|
|\
| |
| | |
[RFC] lint: check indentation of FUNC_ATTR lines
|
| | |
|
|/ |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
The error case is already handled and an appropriate error message is
already printed.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Also:
Add ru to shada tests with all keys
Add test for unset unnamed and register 0
|
| | |
|
| |
| |
| |
| |
| | |
shada_write was too long (over 500 lines) and caused a linting error.
Register initialization was moved to its own function in order to save lines.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Ref #4645
|
| |
| |
| |
| |
| |
| | |
LuaRocks 2.3 and onwards changed the /P option to no longer include the
version number which made newer releases of LuaRocks fail when compiling
on Windows.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reverts commit 337b6179df852350b52409fd3806e4b47ab2875b
Closes #6716 at the expense of not being able to use a
multi-key 'pastetoggle' manually.
Multi-key 'pastetoggle' can still be used when inserting the entire
option into the typebuffer at once (though the use here is
questionable).
Also remove those tests to do with waiting for the completion of
'pastetoggle' and mention in the documentation that 'pastetoggle'
doesn't wait for timeout.
|
|\ \
| | |
| | | |
if_cscope: Fix truncation of formated output
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
snprintf() has to truncate the string written to buffer buf for maximal
size_t value.
Increase buffer size to fix this.
|
|\ \ \
| | | |
| | | | |
connect to socket (RPC only for the moment)
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
Helped-By: oni-link <knil.ino@gmail.com>
|
|\ \ \
| | | |
| | | | |
Use uv_getaddrinfo() for servers
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Although in_port_t is a typedef for uint16_t, GCC in Ubuntu 12.04
complains about potential loss of data due to converting int to
uint16_t. Since we know this isn't possible, silence the warning to
avoid breaking QB until it gets upgraded to a newer Ubuntu.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In the process of setting up the socket watcher, the address may be
changed (e.g., adding the OS-selected port).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When using serverstart("ip.ad.d.r:") to listen on a random port, we need
to abide by getaddrinfo()'s API and pass in a NULL service, rather than
an empty string.
When given an empty string, getaddrinfo() is free to search for a
service by the given name (since the string isn't a number) which will
fail. At least FreeBSD does perform this lookup.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change implicitly adds IPv6 support.
If the address contains ":", we try to use a TCP socket instead of a Unix domain
socket. Everything in front of the last occurrence of ":" is the hostname and
everything after it the port.
If the hostname lookup fails, we fall back to using a Unix domain socket.
If the port is empty ("localhost:"), a random port will be assigned.
Examples:
NVIM_LISTEN_ADDRESS=localhost:12345 -> TCP (IPv4 or IPv6), port: 12345
NVIM_LISTEN_ADDRESS=localhost: -> TCP (IPv4 or IPv6), port: random (> 1024)
NVIM_LISTEN_ADDRESS=localhost:0 -> TCP (IPv4 or IPv6), port: random (> 1024)
NVIM_LISTEN_ADDRESS=localhost -> Unix domain socket "localhost" in current dir
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: The buffer that quickfix caches for performance may become
invalid. (Daniel Hahler)
Solution: Reset qf_last_bufref in qf_init_ext(). (Daniel Hahler,
closes vim/vim#1728, closes vim/vim#1676)
https://github.com/vim/vim/commit/6dd4a53502fb4ec1b66104eab1805e7254ad9e41
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
https://svnweb.freebsd.org/ports/head/editors/neovim/Makefile?revision=428479&view=markup#l28
Closes #6771
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
From FreeBSD ports patch:
https://svnweb.freebsd.org/ports/head/editors/neovim/files/patch-src_nvim_os_pty__process__unix.c?revision=425833&view=markup
References https://github.com/neovim/neovim/issues/6771#issuecomment-302921368
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
From FreeBSD ports patch:
https://svnweb.freebsd.org/ports/head/editors/neovim/files/patch-CMakeLists.txt?revision=425833&view=markup
References #4363
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Showing the 'number' column in terminal buffers is a bit silly because
of 'scrollback'. But it's mostly harmless and technically works as
expected.
The least surprising thing is to leave the user's settings alone. Since
there are tradeoffs in both cases, we choose inertia.
We still disable 'relativenumber' in *terminal-mode* (as opposed to
normal-mode) because it is totally broken: the Nvim cursor (not terminal
cursor) is always on the last line.
|