| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
patch 7.4.713
Problem: Wrong condition for #ifdef.
Solution: Change USR_EXRC_FILE2 to USR_VIMRC_FILE2. (Mikael Fourrier)
https://code.google.com/p/vim/source/detail?r=v7-4-713
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These patches are not applicable (NA):
.611 (if_python3.c)
.627 (term.c)
.666 (X on *nix)
.678 (--remote)
.683 (vimtutor)
.687 (terminal)
.691 (mzscheme)
.692 (Solaris)
.730 (crypto)
.731 (GUI)
.738 (compiling w/o syntax highlighting)
.644 applied in an unsupported platform (Stratus VOS)
|
| |
|
|
|
|
|
| |
Helped-By: David Bürgin <676c7473@gmail.com>
Helped-By: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
|
|
|
|
|
| |
When ml_add_stack() needs to increase the size of the empty stack,
buf->b_ml.ml_stack is NULL and is used as argument in memmove().
This is undefined behaviour. Declaration of memmove() in string.h:
extern void *memmove (void *__dest, const void *__src, size_t __n)
__THROW __nonnull ((1, 2));
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backported from vim_dev:
https://groups.google.com/forum/#!searchin/vim_dev/completeopt/vim_dev/tVsk0pdOGvs/fCzBbPkA4w0J
Use case:
https://github.com/Shougo/neocomplcache.vim/issues/426
Reviewed-by: Felipe Morales <hel.sheep@gmail.com>
Reviewed-by: Scott Prager <splinterofchaos@gmail.com>
Reviewed-by: Michael Reed <m.reed@mykolab.com>
|
|
|
|
|
|
|
|
|
|
| |
When splitting the window (win_split_ins), function win_new_width is
already called before the height has been set. This calls
terminal_resize, which passes a height of 0 on to libvterm, which
doesn't handle a height of 0 properly.
A fix is already in place in terminal.c for not passing on the height,
but strictly speaking, it doesn't make sense for window to call
terminal_resize when it isn't initialized completely yet.
|
| |
|
|
|
|
| |
We don't link to any X11 libs, so this is most likely unneeded.
|
|
|
|
|
|
|
|
|
|
| |
Error messages in general should be namespaced, especially in the
context of a shell. Given the possibility of a backgrounded job printing
messages to standard output/error, namespacing these messages should
avoid any confusion as to where the message came from.
Helped-by: Scott Prager <splinterofchaos@gmail.com>
Helped-by: oni-link <knil.ino@gmail.com>
|
|
|
|
|
|
|
|
| |
This removes the need for preprocessor defines as array indices, and
brings error handling more in line with other files, which for the most
most part to use constant strings (also, see `globals.h`).
Helped-By: Nicolas Hillegeer <nicolas@hillegeer.com>
|
|
|
|
|
|
| |
Making an environment variable empty can be a way of unsetting it for
platforms that don't support unsetenv(). In most cases, we treat empty
variables as having been unset. For all others, use os_env_exists().
|
|
|
|
|
|
|
|
|
|
| |
<C-A> over "07" should increment to "08" by default.
Re: https://github.com/neovim/neovim/issues/1664
Reviewed-by: Justin M. Keyes <justinkz@gmail.com>
Reviewed-by: Scott Prager <splinterofchaos@gmail.com>
Reviewed-by: Michael Reed <m.reed@mykolab.com>
|
|
|
|
| |
Helped-By: David Bürgin <676c7473@gmail.com>
|
|
|
|
|
| |
Helped-By: David Bürgin <676c7473@gmail.com>
Helped-By: Shougo Matsushita <Shougo.Matsu@gmail.com>
|
| |
|
| |
|
|
|
|
| |
Helped-By: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
| |
Closes #2745
|
|
|
|
|
| |
- "stdin" is misleading because it may read from stdout or stderr
- also remove some unused includes
|
|
|
|
|
|
|
|
|
| |
- Create a private libuv loop instead of re-using uv_default_loop(), to
avoid conflict[1] with existing watcher(s) on the fd.
- Expose the global "input" fd as a getter instead of a mutable global.
[1] .deps/build/src/libuv/src/unix/core.c:833:
uv__io_stop: Assertion `loop->watchers[w->fd] == w' failed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If stdin is non-blocking, many tools (e.g. cat(1), read(1)) which assume
that stdin is blocking, will break in odd ways:
read: read error: 0: Resource temporarily unavailable
cat: -: Resource temporarily unavailable
rm: error closing file
libuv puts stdin in nonblocking mode, and leaves it that way at exit
(this is apparently by design). So, before this commit, this always
works (because the shell clobbers O_NONBLOCK):
$ nvim --cmd q
$ read
...but these forms do _not_ work:
$ nvim --cmd q && read
$ echo foo | nvim --cmd q && read
$ nvim && read
After this commit, all of the above forms work.
Background:
https://github.com/fish-shell/fish-shell/commit/437b4397b9cf273922ce7b414bf6626845f15ad0#diff-41f4d294430cd8c36538999d62681ae2
https://github.com/fish-shell/fish-shell/issues/176#issuecomment-15800155
- bash (and other shells: zsh, tcsh, fish), upon returning to the
foreground, always sets fd 0 back to blocking mode. This practice only
applies to stdin, _not_ stdout or stderr (in practice these fds may be
affected anyways).
- bash/zsh/tcsh/fish do _not_ restore the non-blocking status of stdin
when _resuming a job_.
- We do _not_ save/restore the original flags visible to
fcntl(F_[SG]ETFL), because (counterintuitively) that isn't expected.
Helped-by: oni-link <knil.ino@gmail.com>
Closes #2086
Closes #2377
---
Note: The following implementation of stream_set_blocking() was
discarded, because it resulted in a failed libuv assertion[1]:
int stream_set_blocking(int fd, bool blocking)
{
uv_pipe_t stream;
uv_pipe_init(uv_default_loop(), &stream, 0);
uv_pipe_open(&stream, fd);
int retval = uv_stream_set_blocking((uv_stream_t *)&stream, blocking);
uv_close((uv_handle_t *)&stream, NULL);
return retval;
}
[1] .deps/build/src/libuv/src/unix/core.c:833: uv__io_stop: Assertion `loop->watchers[w->fd] == w' failed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Can't match "%>80v" properly. (Axel Bender)
Solution: Correctly handle ">". (Christian Brabandt)
https://github.com/vim/vim/commit/v7-4-582
See https://groups.google.com/d/msg/vim_dev/n-02i4FnOcw/P3Yyx1OLeXgJ
Slightly adapted due to the long_u refactoring in
2ceb1c74d591a07183ee02baf6ff1e205c87c6b8.
Reviewed-by: Florian Walch <florian@fwalch.com>
Fixes #2726
|
|
|
|
|
|
|
|
|
| |
Problem: Wrong cursor positioning when 'linebreak' is set and lines wrap.
Solution: (Christian Brabandt)
https://github.com/vim/vim/commit/v7-4-579
See https://groups.google.com/d/msg/vim_dev/Eh3N9L68Ajw/4dB5x1RTQJQJ
|
| |
|
| |
|
|
|
|
|
|
|
| |
When maximizing the window, often only lines would be detected properly
with the `try_resize` handler being called immediately.
Fixes https://github.com/neovim/neovim/issues/2322.
|
| |
|
|
|
|
|
|
|
| |
Reviewed-by: Michael Reed <m.reed@mykolab.com>
Reviewed-by: Luke Andrew <luke.github@la.id.au>
Reviewed-by: Justin M. Keyes <justinkz@gmail.com>
Reviewed-by: Florian Walch <florian@fwalch.com>
|
|
|
|
|
| |
- In Windows eof is a function, renamed the eof var in input.c
to input_eof
|
|
|
|
|
| |
The sys/wait.h include was moved after the vim.h include, since the include
guards are defined in config.h the guards cannot be used earlier.
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed-by: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
|
|
| |
Also remove some references to emacs tags from the docs.
References https://github.com/neovim/neovim/issues/1664
|
| |
|
|
|
|
|
|
|
| |
It didn't actually do anything after
3baba1e7bc6698e6bc9f1d37fce88b30d6274bc9
Helped-by: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
|
| |
Removed in 3baba1e7bc6698e6bc9f1d37fce88b30d6274bc9, but the docs
weren't updated.
|
|
|
|
|
|
| |
Because of 3baba1e7bc6698e6bc9f1d37fce88b30d6274bc9, it's dead code.
Helped-by: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regarding debugger.txt (which was Spotted by @Hettomei):
The third section was empty, and the second section is very outdated.
Nvim doesn't have things like Balloon Evalutation and Sun Visual
workshop integration, so just remove the section.
Regarding everything else:
- term.[ch] and term_defs.h don't exist anymore, so remove refs to them
- Add ttybuiltin to vim_diff.txt. It should have been done before, but
vim_diff.txt didn't exist when ttybuiltin was removed (done in
3baba1e7bc6698e6bc9f1d37fce88b30d6274bc9,)
Helped-by: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
|
|
|
|
| |
Resolves #2632. This is done so C helper modules don't generate unexpected
coverage output.
Reviewed-by: Justin M. Keyes <justinkz@gmail.com>
Reviewed-by: Florian Walch <florian@fwalch.com>
|
|
|
|
| |
#2677
|
|
|
|
|
|
|
|
|
| |
Problem: Cannot change the result of systemlist().
Solution: Initialize v_lock. (Yukihiro Nakadaira)
https://github.com/vim/vim/commit/v7-4-597
See https://groups.google.com/d/msg/vim_dev/WXCfHMeqjfk/n2PjNwZ2bzIJ
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These changes cannot apply because they
a) fix compiler warning
b) modify removed GUI related code
c) modify removed build files
mark the following patch as NA:
* 7.4.728, https://github.com/vim/vim/commit/v7-4-728
* 7.4.727, https://github.com/vim/vim/commit/v7-4-727
* 7.4.726, https://github.com/vim/vim/commit/v7-4-726
* 7.4.724, https://github.com/vim/vim/commit/v7-4-724
* 7.4.720, https://github.com/vim/vim/commit/v7-4-720
* 7.4.705, https://github.com/vim/vim/commit/v7-4-705
* 7.4.681, https://github.com/vim/vim/commit/v7-4-681
* 7.4.679, https://github.com/vim/vim/commit/v7-4-679
* 7.4.677, https://github.com/vim/vim/commit/v7-4-677
* 7.4.676, https://github.com/vim/vim/commit/v7-4-676
* 7.4.674, https://github.com/vim/vim/commit/v7-4-674
* 7.4.669, https://github.com/vim/vim/commit/v7-4-669
* 7.4.663, https://github.com/vim/vim/commit/v7-4-663
* 7.4.657, https://github.com/vim/vim/commit/v7-4-657
Reviewed-by: David Bürgin <676c7473@gmail.com>
Reviewed-by: Michael Reed <m.reed@mykolab.com>
Reviewed-by: oni-link <knil.ino@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
For now, only install man pages matching "nvim*.1": we don't want to
install xxd.1 as it might conflict with that of a user's Vim
installation.
closes #1826
Reviewed-by: Florian Walch <florian@fwalch.com>
Helped-by: John Szakmeister <john@szakmeister.net>
|
|
|
|
|
|
|
| |
Remove related dead code and references in the docs.
Helped-By: Michael Reed <m.reed@mykolab.com>
Helped-By: Shougo Matsushita <Shougo.Matsu@gmail.com>
|
| |
|