| Commit message (Collapse) | Author | Age |
... | |
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: "1gd" may hang.
Solution: Don't get stuck in one position. (Christian Brabandt, closes vim/vim#1643)
https://github.com/vim/vim/commit/60402d68da09997cacdeec71fd22c9344f8f40d5
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Problem: No test for the 8g8 command.
Solution: Add a test. (Dominique Pelle, closes vim/vim#1615)
https://github.com/vim/vim/commit/395b6bab33e5ed9a0377d7f140e98fd3ab682672
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(#8588)
Problem: Swap file exists briefly when opening the command window.
Solution: Set the noswapfile command modifier before splitting the window.
(James McCoy, closes vim/vim#1620)
https://github.com/vim/vim/commit/3bab93998d01a01b7f2a071fa3b8054bb0094625
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
DWIM: avoid empty buffer 1 when stdin was empty. If other files were
specified at startup, we assume that stdin is only accidentally
not-a-TTY: user did not intend to send text from it.
ref #8560
ref #8561
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If stdin is not a TTY we read it into buffer 1, as text. But if the
stdin pipe is empty, Nvim was most likely invoked for some other reason.
DWIM: select buffer 2 (if it exists). Example:
echo file1 | xargs nvim
closes #8560
closes #8561
ref https://github.com/equalsraf/neovim-qt/issues/417
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Illegal memory access with :z and large count.
Solution: Check for number overflow, using long instead of int. (Dominique
Pelle, closes vim/vim#1612)
https://github.com/vim/vim/commit/fa0ad0bb0b4255e64ebcf9269d60a942e0ae7ff9
|
|\ \ \
| |/ /
|/| | |
vim-patch: Replace shell variables in printf with formatted args
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that special characters in the variables are not
interpreted as escapes/format characters in the printf string, as was
seen with upstream patch 8.0.0615.
$ ./scripts/vim-patch.sh -p 8.0.0615
Updating Vim sources: /$HOME/src/neovim/.vim-src
✔ Updated Vim sources.
✔ Found Vim revision 'bf15b8d78b22661db8b19d662b62bb9a061cdd37'.
Creating patch...
Pre-processing patch...
✔ Saved patch to '/$HOME/src/neovim/vim-8.0.0615.patch'.
Fetching 'origin/master'.
✔ From https://github.com/neovim/neovim
* branch master -> FETCH_HEAD
Creating new branch 'vim-8.0.0615' based on 'origin/master'.
✔ Switched to a new branch 'vim-8.0.0615'
Branch 'vim-8.0.0615' set up to track remote branch 'master' from 'origin'.
Creating empty commit with correct commit message.
./scripts/vim-patch.sh: line 40: printf: `w': invalid format character
✔ [vim-8.0.0615 db7fbb016] vim-patch:8.0.0615: using ./scripts/vim-patch.sh: line 44: printf: `w': invalid format character
✘ [vim-8.0.0615 db7fbb016] vim-patch:8.0.0615: using
[ci-skip]
|
| |
| |
| |
| |
| |
| | |
Problem: The mode test may hang in Test_mode(). (Michael Soyka)
Solution: Set 'complete' to only search the current buffer (as suggested by
Michael)
https://github.com/vim/vim/commit/ffea8c99d9658b0b51a848a6f674851851e78fa7
|
| |
| |
| |
| |
| | |
Problem: getpos() can return a negative line number. (haya14busa)
Solution: Handle a zero topline and botline. (closes vim/vim#1613)
https://github.com/vim/vim/commit/a1d5fa65bc7e8a548858e9c295a192b63dcd011b
|
| |
| |
| |
| |
| | |
Problem: Building with gcc 7.1 yields new warnings.
Solution: Initialize result. (John Marriott)
https://github.com/vim/vim/commit/9e0f6ec0762575d229b86798b284ca4876bc3d73
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Extra line break in verbosefile when using ":echomsg". (Ingo
Karkat)
Solution: Don't call msg_start(). (closes vim/vim#1618)
https://github.com/vim/vim/commit/52604f2454e5369f861d3ce34764f74a0999c773
|
| |/
| |
| |
| |
| |
| |
| | |
Problem: Using g< after :for does not show the right output. (Marcin
Szamotulski)
Solution: Call msg_sb_eol() in :echomsg.
https://github.com/vim/vim/commit/57002ad70c4c32f3afefec24994a974cf3eef3ad
|
|\ \
| | |
| | | |
cmake: Check for GNU compiler, not Linux, to set -D_GNU_SOURCE
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
2.8.12 is supported by our main CI targets and [repology] confirms that
this is broadly supported.
[repology]: https://repology.org/metapackage/cmake/information
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's a mix of CXX and C related variables being set/referenced in our
CMake files. Since we only use C, use an explicit language list of "C"
instead of the implicit "C CXX" and replace all uses of CXX variables
with their C counterparts
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Debian hurd-i386 [build] failed (partly) due to -D_GNU_SOURCE not be
defined:
[215/286] /usr/bin/cc -DINCLUDE_GENERATED_DECLARATIONS -Iconfig -I../src -Isrc/nvim/auto -Iinclude -I/usr/include/luajit-2.1 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DDISABLE_LOG -Wdate-time -D_FORTIFY_SOURCE=2 -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -O2 -g -DMIN_LOG_LEVEL=3 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -MD -MT src/nvim/CMakeFiles/nvim.dir/os/pty_process_unix.c.o -MF src/nvim/CMakeFiles/nvim.dir/os/pty_process_unix.c.o.d -o src/nvim/CMakeFiles/nvim.dir/os/pty_process_unix.c.o -c ../src/nvim/os/pty_process_unix.c
../src/nvim/os/pty_process_unix.c: In function 'pty_process_tty_name':
../src/nvim/os/pty_process_unix.c:121:10: warning: implicit declaration of function 'ptsname'; did you mean 'ttyname'? [-Wimplicit-function-declaration]
return ptsname(ptyproc->tty_fd);
Hurd is obviously not Linux, but it is using a GNU compiler and glibc so
it needs -D_GNU_SOURCE for the ptsname() definition to be visible.
[build]: https://buildd.debian.org/status/fetch.php?pkg=neovim&arch=hurd-i386&ver=0.3.0-2&stamp=1528981349&raw=0
|
|/
|
|
| |
wchar_t has better cross-platform support and seems to fix an issue
on MinGW when building with `-std=c99`.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Unnecessary if statement.
Solution: Remove the statement. Fix "it's" vs "its" mistakes. (Dominique
Pelle, closes vim/vim#1568)
https://github.com/vim/vim/commit/aab93b12cb54fbe5efe9e8f6fde1c46802a3031e
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before this change, -E/-Es without `-u NONE` reads stdin as Ex commands.
It should always read stdin as text (into buffer 1), like this:
echo foo | nvim -Es +'%p'
foo
echo foo | nvim -Es -u NORC +'%p'
foo
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes Ex mode (Q, -e) to work like Vim's "improved Ex mode"
(gQ, -E). That brings some small behavior differences, but should not
impact most Ex scripts (unless, for example, they depend on mappings
being disabled--but that can be solved for -e by skipping user config).
Before this change:
* the screen test hangs.
After this change:
* Q acts like gQ.
* -e/-es differs from -E/-Es only in its treatment of stdin.
This moves towards potentially removing getexmodeline().
(HINT: That does NOT mean "removing Ex mode", it means removing the
Vi-compatible Ex mode, which differs from Vim's "improved Ex mode" only
in some minor details (e.g. mappings are disabled).)
ref #1089 :-)~
|
| |
| |
| |
| |
| | |
- "neovim" package may be installed with yarn. Check yarn if npm fails.
- Use filereadable() instead of glob(). closes #8552
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: For some people the hint about quitting is not sufficient.
Solution: Put <Enter> separately. Also use ":qa!" to get out even when
there are changes.
https://github.com/vim/vim/commit/28a8193e3113f676f89fb6312b099d849df881d3
|
| |
| |
| |
| |
| |
| |
| | |
Problem: shellescape() always escapes a newline, which does not work with
some shells. (Harm te Hennepe)
Solution: Only escape a newline when the "special" argument is non-zero.
(Christian Brabandt, closes vim/vim#1590)
https://github.com/vim/vim/commit/206155280def51160a9d81d983aed639015ffb44
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
- Empty "--tags=", "--filter=" prevents TEST_FILE from running.
- Fix another bug: TEST_FILTER overwrote TEST_TAG.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix PVS warnings:
fileio.c:7293 Medium V547 Expression is always true.
fileio.c:7351 Medium V547 Expression 'event == 100' is always false.
event_name2nr returns event_T, so PVS infers that nothing outside of
that range could possibly be returned.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: gF test fails still on MS-Windows.
Solution: Use : before the line number and remove it from 'isfname'.
https://github.com/vim/vim/commit/712598f210570627534246cb5dcbb4f213367997
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: gF test fails on MS-Windows.
Solution: Use @ instead of : before the line number
https://github.com/vim/vim/commit/d7aca7a71c7254501c08f04db1798df479df0e89
|
| |/
| |
| |
| |
| |
| |
| | |
Problem: When gF fails to edit the file the cursor still moves to the found
line number.
Solution: Check the return value of do_ecmd(). (Michael Hwang)
https://github.com/vim/vim/commit/2a79ed293c077ba791db962f0e121cf97ba4f7a7
|
|\ \
| |/
|/| |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Problem: Edit test may fail on some systems.
Solution: If creating a directory with a very long path fails, bail out.
https://github.com/vim/vim/commit/15ecbd6f3d39ff04862999a577962ef9369a9e53
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Test_edit causes older xfce4-terminal to close. (Dominique Pelle)
Solution: Reduce number of columns to 2000. Try to restore the window
position.
https://github.com/vim/vim/commit/ba6ec182973af726ce9b7b7eb3753fc3a7ae7d1b
|
| |
| |
| |
| |
| |
| | |
Problem: Test with long directory name fails on Mac.
Solution: Skip the test on Mac systems.
https://github.com/vim/vim/commit/c77d6757471fa207520586bbdbc1b30af84cf5c8
|
| |
| |
| |
| |
| |
| | |
Problem: Test with long directory name fails on non-unix systems.
Solution: Skip the test on non-unix systems.
https://github.com/vim/vim/commit/9b81079ddd839a666682f6bdbc24890bf4d1a42c
|
|/
|
|
|
|
|
| |
Problem: Buffer overflow when 'columns' is very big. (Nikolai Pavlov)
Solution: Correctly compute where to truncate. Fix translation.
(closes vim/vim#1600)
https://github.com/vim/vim/commit/658a3a2caf5852d071b6b1be92d9d6614a6208dc
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Problem: Warning for uninitialized variable. (John Marriott)
Solution: Initialize "indent".
https://github.com/vim/vim/commit/97db5541a65e4614f8753af27996c204946061a9
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Using freed memory when resetting 'indentexpr' while evaluating
it. (Dominique Pelle)
Solution: Make a copy of 'indentexpr'.
https://github.com/vim/vim/commit/a701b3b6f0f06ac0c9fcc75c6c34a1258fc3b1a2
|