aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | | vim-patch:8.1.0466: autocmd test failsJan Edmund Lazo2018-10-08
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Autocmd test fails. Solution: Do call inchar() when flushing typeahead. https://github.com/vim/vim/commit/6a2633b00bb00bcf0d994f08d1c54ace2c221b58
| * | | vim-patch:8.1.0463: "simalt ~x" in .vimrc blocks swap file promptJan Edmund Lazo2018-10-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: "simalt ~x" in .vimrc blocks swap file prompt. Solution: Flush buffers before prompting. (Yasuhiro Matsumoto, closes vim/vim#3518, closes vim/vim#2192) https://github.com/vim/vim/commit/798184cc67036285a24b38c0bf6668d4d1525548
| * | | vim-patch:8.1.0459: Test_executable fails when there is a dog in the systemJan Edmund Lazo2018-10-08
|/ / / | | | | | | | | | | | | | | | Problem: Test_executable fails when there is a dog in the system. Solution: Rename the dog. (Hirohito Higashi) https://github.com/vim/vim/commit/a05a0d325c7615439f4a42f00682b2ebad43c8d9
* | | Merge #9092 from janlazo/vim-8.0.1807Justin M. Keyes2018-10-08
|\ \ \
| * | | oldtests: win: fix executable() assertionsJan Edmund Lazo2018-10-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Windows has "Read and execute" permission via ACL but nvim and libuv do not support ACL. Windows does not support the executable bit in chmod-style permissions but it is safe to assume that if the file exists and is readable, then it is most likely executable. This means that win.ini and shell32.dll are "executable" because they exist, are readable, and are in PATH. PATHEXT does not affect the executable permission of a file; it exists to run files on the shell while omitting the file extension. Assume that PATHEXT is intended for cmd.exe only because powershell can execute powershell files (ie. *.ps1) without changing PATHEXT or related cmd.exe environment variable. In the future, nvim should check the outputs of 'assoc' and 'ftype', cmd.exe internal commands, or check the registry. Powershell can be used for ACL if C++/C# API is too difficult to use.
| * | | vim-patch:8.1.0453: MS-Windows: executable() is not reliableJan Edmund Lazo2018-10-07
| | | | | | | | | | | | | | | | | | | | | | | | Problem: MS-Windows: executable() is not reliable. Solution: Use $PATHEXT properly. (Yasuhiro Matsumoto, closes vim/vim#3412) https://github.com/vim/vim/commit/8295666dc2c65e42135b91d5c61e2a140d002333
| * | | vim-patch:8.1.0454: resolve() was not tested with a symlink cycleJan Edmund Lazo2018-10-06
| | | | | | | | | | | | | | | | | | | | | | | | Problem: resolve() was not tested with a symlink cycle. Solution: Add a test. (Dominique Pelle, closes vim/vim#3513) https://github.com/vim/vim/commit/261099070940fb64d4633a766ae3510fffe4171d
| * | | vim-patch:8.0.1807: function to set terminal name is too longJan Edmund Lazo2018-10-06
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Function to set terminal name is too long. Solution: Refactor the function. Fix typo in test. https://github.com/vim/vim/commit/69e056915c4145b7b64c60963797692a5b293561
* | | | Merge #9036 'func_attr_printf'Justin M. Keyes2018-10-07
|\ \ \ \ | |_|_|/ |/| | |
| * | | src/nvim/eval.cMichaHoffmann2018-10-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | src/nvim/eval/typval.c src/nvim/fileio.c src/nvim/main.c src/nvim/regexp_nfa.c src/nvim/spellfile.c changed some EMSG[..] Macros to emsgf
| * | | fixed lint errorsMichaHoffmann2018-09-24
| | | |
| * | | src/nvim/eval.c: printf errorMichaHoffmann2018-09-24
| | | |
| * | | add func_attr_printf in :MichaHoffmann2018-09-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | log.c message.c strings.c fixed some printf warnings in: src/nvim/undo.c src/nvim/eval.c src/nvim/eval/encode.c src/nvim/eval/typval.c src/nvim/ex_getln.c src/nvim/fileio.c src/nvim/lua/executor.c src/nvim/main.c src/nvim/regexp_nfa.c src/nvim/shada.c src/nvim/spellfile.c src/nvim/tui/terminfo.c src/nvim/garray.h
* | | | build: adjust some messages (#9087)Justin M. Keyes2018-10-06
| |/ / |/| |
* | | Merge #9090 'clint.py: --stdin-filename'Justin M. Keyes2018-10-06
|\ \ \ | |_|/ |/| |
| * | clint: add support for --stdin-filenameDaniel Hahler2018-10-05
| | |
| * | clint: use fileinput for stdinDaniel Hahler2018-10-05
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes handing of "-" on Python 3: Traceback (most recent call last): File "…/Vcs/neovim/src/clint.py", line 3625, in <module> main() File "…/Vcs/neovim/src/clint.py", line 3618, in main ProcessFile(filename, _cpplint_state.verbose_level) File "…/Vcs/neovim/src/clint.py", line 3464, in ProcessFile 'replace').read().split('\n') File "/usr/lib/python3.7/codecs.py", line 701, in read return self.reader.read(size) File "/usr/lib/python3.7/codecs.py", line 500, in read data = self.bytebuffer + newdata TypeError: can't concat str to bytes
* | TUI: check libvte version for undercurl support #9088Daniel Hahler2018-10-05
| | | | | | | | | | Support was added in https://github.com/GNOME/vte/commit/efaf8f3c. Fixes #9083
* | vim-patch.sh: Skip Vim screen-dump filesJustin M. Keyes2018-10-05
| |
* | vim-patch:8.1.0440: remove() with a range not sufficiently tested (#9076)Jan Edmund Lazo2018-10-04
| | | | | | | | | | Problem: remove() with a range not sufficiently tested. Solution: Add a test. (Dominique Pelle, closes vim/vim#3497) https://github.com/vim/vim/commit/2bfddfc508bcc8dcee108f098eb75844a228fa44
* | Merge #9078 from janlazo/vim-8.0.1832Justin M. Keyes2018-10-04
|\ \
| * | vim-patch:8.1.0047: no completion for :unlet $VARJan Edmund Lazo2018-10-02
| | | | | | | | | | | | | | | | | | Problem: No completion for :unlet $VAR. Solution: Add completion. (Jason Franklin) https://github.com/vim/vim/commit/19834010889fc5bfa0f88b3ba83133dae6c0a35d
| * | vim-patch:8.0.1832: cannot use :unlet for an environment variableJan Edmund Lazo2018-10-02
| | | | | | | | | | | | | | | | | | | | | Problem: Cannot use :unlet for an environment variable. Solution: Make it work. Use unsetenv() if available. (Yasuhiro Matsumoto, closes vim/vim#2855) https://github.com/vim/vim/commit/137374fd6538cf9dee0cb22907728d8fdecb5832
* | | Merge pull request #9081 from jamessan/embed-crashJames McCoy2018-10-03
|\ \ \ | |/ / |/| | Fix crash if --embed is used more than once
| * | Fix crash if --embed is used more than onceJames McCoy2018-10-03
|/ /
* | TUI: fix support for undercurl/underline color #9080Daniel Hahler2018-10-03
| |
* | Merge pull request #9052 from blueyed/undercurlBjörn Linse2018-10-02
|\ \ | | | | | | tui: add support for undercurl and colored underline
| * | tui: add support for undercurl and underline colorDaniel Hahler2018-10-01
| | | | | | | | | | | | Fixes https://github.com/neovim/neovim/issues/7479.
* | | Merge pull request #9064 from bfredl/uidocBjörn Linse2018-10-02
|\ \ \ | | | | | | | | UI: rename ext_newgrid to ext_linegrid and add --embed UI startup recommendations
| * | | ui: reserve the right to split a screen redraw into multiple batches.Björn Linse2018-10-02
| | | |
| * | | ui: rename ext_newgrid to ext_linegridBjörn Linse2018-10-01
| | | |
| * | | ui: update docs for safe startup procedureBjörn Linse2018-10-01
|/ / /
* | | Revert "TUI: terminfo_start: use unibi_from_term directly"Justin M. Keyes2018-10-01
| | | | | | | | | | | | | | | | | | | | | If $TERM is not defined then unibi_from_term() would crash. Reverts 3bdc34d0657d223599afdf0ce9b072fafa3d5648. ref #9072
* | | Merge pull request #9073 from blueyed/vim-patch-ffJames McCoy2018-09-30
|\ \ \ | | | | | | | | vim-patch.sh: use --ff with git-pull
| * | | vim-patch.sh: use --ff with git-pullDaniel Hahler2018-09-30
|/ / / | | | | | | | | | | | | | | | | | | | | | I have `merge.ff = no` in my Git config to not use fast-forward merges by default, but when updating the Vim sources it should not cause a merge commit. [ci skip]
* / / TUI: terminfo_start: use unibi_from_term directly (#9072)Daniel Hahler2018-09-30
|/ / | | | | | | | | Avoids redundant call to `getenv("TERM")`. Ref: https://github.com/mauke/unibilium/blob/e3b16d6219ca1cb92d98b1d9cc416b49a3ac468e/uniutil.c#L203-L211
* | man.vim: set $MANWIDTH=999Justin M. Keyes2018-09-30
| | | | | | | | | | | | | | | | On some systems, mandoc disallows $MANWIDTH greater than 1000. E.g. FreeBSD: https://github.com/freebsd/freebsd/blob/b7d613ae8a2fc1530d33aff53a1a678d284bfeec/contrib/mandoc/manpath.c#L312 closes #9065
* | undo: Fix infinite loop if undo_read_byte returns EOF #2880ssteinbach2018-09-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Corrupt(?) persistent undofile leads to an infinite loop. Solution: Break out of loop if undo_read_byte returns EOF (cf. u_read_undo() which does this too). backtrace from lldb (@ a743297be2b3): Process 70700 stopped * thread 1: tid = 0x147d2d1, 0x00007fff8c8facd7 libsystem_pthread.dylib`__mtx_droplock + 209, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP frame 0: 0x00007fff8c8facd7 libsystem_pthread.dylib`__mtx_droplock + 209 libsystem_pthread.dylib`__mtx_droplock + 209: -> 0x7fff8c8facd7: movq %rcx, -0x50(%rbp) 0x7fff8c8facdb: movq %r8, -0x58(%rbp) 0x7fff8c8facdf: movq %rdx, -0x68(%rbp) 0x7fff8c8face3: movq %r14, -0x60(%rbp) (lldb) bt * thread 1: tid = 0x147d2d1, 0x00007fff8c8facd7 libsystem_pthread.dylib`__mtx_droplock + 209, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP * frame 0: 0x00007fff8c8facd7 libsystem_pthread.dylib`__mtx_droplock + 209 frame 1: 0x00007fff8c8fab4e libsystem_pthread.dylib`pthread_mutex_unlock + 63 frame 2: 0x00007fff915da2a4 libsystem_c.dylib`getc + 63 frame 3: 0x000000010e6194b9 nvim`undo_read_byte(bi=0x00007fff5181a838) + 25 at undo.c:1553 frame 4: 0x000000010e619685 nvim`unserialize_uhp(bi=0x00007fff5181a838, file_name=0x000000000f2e8060) + 421 at undo.c:840 frame 5: 0x000000010e618abb nvim`u_read_undo(name=0x0000000000000000, hash=0x00007fff5181af80, orig_name=0x000000000f370dd0) + 1579 at undo.c:1363 frame 6: 0x000000010e4a8db9 nvim`readfile(fname=0x000000000f370dd0, sfname=0x000000000f370dd0, from=0, lines_to_skip=0, lines_to_read=2147483647, eap=0x00007fff5181b6a0, flags=1) + 21017 at fileio.c: 1961 frame 7: 0x000000010e3ecc8b nvim`open_buffer(read_stdin=0, eap=0x00007fff5181b6a0, flags=0) + 603 at buffer.c:153 ... closes #2879 closes #2880
* | editorconfig: Fix charset name #9070Matěj Cepl2018-09-30
| | | | | | | | | | | | | | | | According to https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties the possible values of the charset property are "latin1", "utf-8", "utf-16be", "utf-16le", or "utf-8-bom" (case insensitive), not "utf_8" It breaks https://github.com/sgur/vim-editorconfig/ for example.
* | dialog_changed: Remove mistaken assert #9069Daniel Hahler2018-09-30
| | | | | | | | | | | | | | | | | | | | | | It fails with `nvim -u NONE -c 'set modified' -c 'confirm q'`. Introduced in 3dffc842f (vim-patch:8.0.0983), but the Vim patch [1] does not have this assertion. NULL gets handled in `dialog_msg` [2]. 1: https://github.com/vim/vim/commit/3f9a1ff141412e9e85f7dff47d02946cb9be9228 2: https://github.com/neovim/neovim/blob/c6d36b97bac0df86c1120af323db1b577dc90629/src/nvim/ex_docmd.c#L9704-L9705
* | Merge #9067 from janlazo/vim-8.0.1485Justin M. Keyes2018-09-30
|\ \
| * | vim-patch:8.1.0067: syntax highlighting not working when re-entering a bufferJan Edmund Lazo2018-09-30
| | | | | | | | | | | | | | | | | | Problem: Syntax highlighting not working when re-entering a buffer. Solution: Do force executing autocommands when not called recursively. https://github.com/vim/vim/commit/a5616b0136cea2104a475d143a1685d71e9b2d3d
| * | vim-patch:8.1.0066: nasty autocommand causes using freed memoryJan Edmund Lazo2018-09-30
| | | | | | | | | | | | | | | | | | | | | Problem: Nasty autocommand causes using freed memory. (Dominique Pelle) Solution: Do not force executing autocommands if the value of 'syntax' or 'filetype' did not change. https://github.com/vim/vim/commit/c3ffc9b8d3015dc5280b297b4e3deb4f34944bd4
| * | vim-patch:8.1.0068: nasty autocommands can still cause using freed memoryJan Edmund Lazo2018-09-30
| | | | | | | | | | | | | | | | | | Problem: Nasty autocommands can still cause using freed memory. Solution: Disallow using setloclist() and setqflist() recursively. https://github.com/vim/vim/commit/2f82ca7d79148ae931bf28a747ede06ba8a65de8
| * | lintJan Edmund Lazo2018-09-29
| | |
| * | globals: arg_had_last is boolJan Edmund Lazo2018-09-29
| | |
| * | vim-patch:8.0.1485: weird autocmd may cause arglist to be changed recursivelyJan Edmund Lazo2018-09-29
|/ / | | | | | | | | | | | | Problem: Weird autocmd may cause arglist to be changed recursively. Solution: Prevent recursively changing the argument list. (Christian Brabandt, closes vim/vim#2472) https://github.com/vim/vim/commit/9e33efd1523b85a70533930dd43a26925a2b648c
* | test: check_cores(): Fix tmp dir exclusion (#9061)Justin M. Keyes2018-09-28
| | | | | | | | | | | | | | | | | | | | | | | | | | tmpdir_get() may be an absolute path, but we invoke glob() with a relative `initial_path`. That can lead to this error: [ ERROR ] test/functional/helpers.lua @ 752: after_each test/helpers.lua:95: cannot open ./Xtest-tmpdir/nvim8jKCjR: No such file or directory stack traceback: test/helpers.lua:95: in function 'glob' test/helpers.lua:273: in function 'check_cores' test/functional/helpers.lua:757: in function <test/functional/helpers.lua:752>
* | vim-patch:8.1.0416: sort doesn't report deleted lines (#9062)Jan Edmund Lazo2018-09-28
| | | | | | | | | | Problem: Sort doesn't report deleted lines. Solution: Call msgmore(). (Christian Brabandt, closes vim/vim#3454) https://github.com/vim/vim/commit/b0e982bf05feb27eddb5f809b052c1137f4d4add
* | Merge pull request #9056 from bfredl/tui_reprBjörn Linse2018-09-27
|\ \ | | | | | | TUI code simplification and dead code elimination
generated by cgit (git 2.34.1) at 2025-08-08 06:58:56 +0000