aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | | | 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
| * | | tui: eliminate scrolling region data structureBjörn Linse2018-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The scrolling region is always local to a single grid_scroll event, use local variables and parameters instead. The invocation of reset_scroll_region in grid_resize is cargo-culted to use margin reset under exactly the same circumstances, not sure if it is necessary though.
| * | | tui: eliminate grid->attrs, use indexed cell->attrBjörn Linse2018-09-26
| | | | | | | | | | | | | | | | remove dead ugrid_put
* | | | Merge #9060 from janlazo/vim-8.1.0120Justin M. Keyes2018-09-27
|\ \ \ \
| * | | | lintJan Edmund Lazo2018-09-27
| | | | |
| * | | | vim-patch:8.1.0120: buffer 'modified' set even when :sort has no changesJan Edmund Lazo2018-09-26
| |/ / / | | | | | | | | | | | | | | | | | | | | Problem: Buffer 'modified' set even when :sort has no changes. Solution: Only set 'modified' when lines are moved. (Jason Franklin) https://github.com/vim/vim/commit/dc9e955fb07f410d5d3e981ce18d895dd2847c85
* | | | vim-patch:8.1.0435: cursorline highlight not removed in some situation (#9059)Justin M. Keyes2018-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cursorline highlight not removed in some situation. (Vitaly Yashin) Solution: Reset last_cursorline when resetting 'cursorline'. (Christian Brabandt, closes vim/vim#3481) https://github.com/vim/vim/commit/8c63e0ec314ba07d54b881dc629fe19e6eda1fb8
* | | | man.vim: Start at the top #9023Justin M. Keyes2018-09-27
|/ / / | | | | | | | | | fixes #9057
* | | Merge #9053 from janlazo/vim-8.1.0433Justin M. Keyes2018-09-26
|\ \ \
| * | | vim-patch:8.1.0436: can get the text of inputsecret() with getcmdline()Jan Edmund Lazo2018-09-25
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Can get the text of inputsecret() with getcmdline(). (Tommy Allen) Solution: Don't return the text. https://github.com/vim/vim/commit/ee91c33570008aefd2d62b8f88b22db751acacbe
| * | | vim-patch:8.1.0433: mapping can obtain text from inputsecret()Jan Edmund Lazo2018-09-25
|/ / / | | | | | | | | | | | | | | | Problem: Mapping can obtain text from inputsecret(). (Tommy Allen) Solution: Disallow CTRL-R = and CTRL-\ e when using inputsecret(). https://github.com/vim/vim/commit/31cbadf74bccc2a5cd8233bc31bbcfe466b00021
* | | terminal: Redraw statusline on title change #8973Josh Triplett2018-09-25
| | | | | | | | | | | | | | | | | | | | | | | | The statusline may incorporate b:term_title, so redraw it when that title changes. Introduce a new function status_redraw_buf to redraw windows associated with the current buffer.
* | | Merge #9047 from jamessan/log-crashJustin M. Keyes2018-09-25
|\ \ \
| * | | log: Assert that we haven't started freeing memory before loggingJames McCoy2018-09-24
| | | | | | | | | | | | | | | | | | | | This is to catch situations like the previous commit, which somehow avoided detection by any of the CI builds.
| * | | os_unix: Log exit code before freeing all memoryJames McCoy2018-09-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When building with -DEXITFREE, the ILOG call would result in a crash trying to access VV_PROGPATH, which had already been released: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007f8f761082f1 in __GI_abort () at abort.c:79 #2 0x00007f8f760ffa8a in __assert_fail_base (fmt=0x7f8f76253ec8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x1c74280 <.str.8> " ,\t\n", file=file@entry=0x1c73fe2 "256]'", line=line@entry=610, function=function@entry=0x1c742e0 <.str.9+32> "") at assert.c:92 #3 0x00007f8f760ffb02 in __GI___assert_fail (assertion=0x1c74280 <.str.8> " ,\t\n", file=0x1c73fe2 "256]'", line=610, function=0x1c742e0 <.str.9+32> "") at assert.c:101 #4 0x00000000012d87c1 in vim_getenv (name=0x2f5a460 <get_special_key_name.string+64> "NVIM_LOG_FILE") at ../src/nvim/os/env.c:608 #5 0x00000000012d6538 in expand_env_esc (srcp=0x1c2f4e0 <.str.10+32> "", dst=0x2f5a460 <get_special_key_name.string+64> "NVIM_LOG_FILE", dstlen=4095, esc=false, one=false, prefix=0x0) at ../src/nvim/os/env.c:351 #6 0x00000000012d85af in expand_env_esc (srcp=0x625000000100 "\004", dst=0x7ffeed88cf40 "", dstlen=32766, esc=237, one=136, prefix=0x60200401c8b4 <error: Cannot access memory at address 0x60200401c8b4>) at ../src/nvim/os/env.c:472 #7 0x0000000000eb4274 in do_log_to_file (log_file=0x0, log_level=0, context=0x0, func_name=0x0, line_num=0, eol=false, fmt=0x0) at ../src/nvim/log.c:254 #8 0x0000000000eb305b in open_log_file () at ../src/nvim/log.c:164 #9 0x0000000000eb2cc6 in logmsg (log_level=<error reading variable: Cannot access memory at address 0x268>, context=<error reading variable: Cannot access memory at address 0x260>, func_name=<error reading variable: Cannot access memory at address 0x258>, line_num=<error reading variable: Cannot access memory at address 0x254>, eol=<error reading variable: Cannot access memory at address 0x253>, fmt=<error reading variable: Cannot access memory at address 0x248>) at ../src/nvim/log.c:109 #10 0x00000000013022c7 in mch_free_acl (aclent=0x4f59100) at ../src/nvim/os_unix.c:132 #11 0x0000000000efddac in getout (exitval=0) at ../src/nvim/main.c:681 #12 0x0000000000c1bb3e in ex_quit (eap=0x7ffeed88cd00) at ../src/nvim/ex_docmd.c:6067 #13 0x0000000000bab781 in do_one_cmd (cmdlinep=0x7ffeed88f180, flags=10, cstack=0x7ffeed88f1a0, fgetline=0x0, cookie=0x0) at ../src/nvim/ex_docmd.c:2228 #14 0x0000000000b8de6d in do_cmdline (cmdline=0x7ffeed891ae2 "quit", fgetline=0x0, cookie=0x0, flags=10) at ../src/nvim/ex_docmd.c:592 #15 0x0000000000b94036 in do_cmdline_cmd (cmd=0x7ffeed891ae2 "quit") at ../src/nvim/ex_docmd.c:268 #16 0x0000000000efb900 in exe_commands (parmp=0x7ffeed890900) at ../src/nvim/main.c:1699 #17 0x0000000000ee96b2 in main (argc=11, argv=0x7ffeed890fa8) at ../src/nvim/main.c:524
* | | | TUI: Alacritty supports DECSCUSR (#9048)Christian Duerr2018-09-25
|/ / / | | | | | | Alacritty may set TERM to"alacritty" or "alacritty-direct" if it finds its terminfo.
* | | deps: revert to jemalloc 4.5.0 (#9035)Justin M. Keyes2018-09-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Since the jemalloc upgrade to 5.1.0, I'm seeing weird behavior such as infinite loops inside jemalloc routines. - VimR maintainer reported major performance regression correlated with jemalloc 5.1.0. ref https://github.com/neovim/neovim/pull/7808 reverts 765515010f8e60596ec67eb7cdfbe7f5e4e60c7d
* | | build: Unify USE_BUNDLED, USE_BUNDLED_DEPS (#9046)Justin M. Keyes2018-09-24
| | | | | | | | | It's confusing that the Makefile uses a different name than CMake.
* | | vim-patch:8.1.0428: the :suspend command is not tested (#9043)Jan Edmund Lazo2018-09-24
| | | | | | | | | | | | | | | Problem: The :suspend command is not tested. Solution: Add a test. (Dominique Pelle, closes vim/vim#3472) https://github.com/vim/vim/commit/3b30168f04b8a2a2f1bbaa2f90be546550463146
* | | vim-patch:8.1.0429: no test for :lcd with 'shellslash' (#9041)Daniel Hahler2018-09-23
| | | | | | | | | | | | | | | | | | | | | | | | Problem: No test for :lcd with 'shellslash'. Solution: Add a test. (Daniel Hahler, closes vim/vim#3475) https://github.com/vim/vim/commit/c75878c923034b883090aef3f08f565513d98f4d Related NA patch: vim-patch:8.1.0343
* | | Merge pull request #9039 from blueyed/undercurlBjörn Linse2018-09-23
|\ \ \ | | | | | | | | tui: code consistency in update_attrs
| * | | minor: tui: update_attrs: code consistencyDaniel Hahler2018-09-23
|/ / /
* | | Merge #9034 'swapfile: always show dialog'Justin M. Keyes2018-09-23
|\ \ \
| * | | test: Do not load entire log-file into memoryJustin M. Keyes2018-09-23
| | | | | | | | | | | | | | | | With DEBUG-level logging, after `make test`, log file could be 1+ GB.
| * | | swapfile: Always show swap dialog (E325)Justin M. Keyes2018-09-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If swapfile dialog prompts for input, it must be displayed to the user. fix #8840 fix #9027
| * | | shortmess+=F: Hide :bnext, :bprev fileinfo messagesJustin M. Keyes2018-09-23
| |/ /
* / / vim-patch:8.0.1557: printf() does not work with only one argument (#9038)Daniel Hahler2018-09-23
|/ / | | | | | | | | Problem: printf() does not work with only one argument. (Daniel Hahler) Solution: Allow using just the format. (Ken Takata, closes vim/vim#2687) https://github.com/vim/vim/commit/c71807db9c1821baf86796cd76952df36ff1a29a
* | vim-patch:8.1.0389: :behave command is not tested (#9030)Jan Edmund Lazo2018-09-23
| | | | | | | | | | Problem: :behave command is not tested. Solution: Add a test. (Dominique Pelle, closes vim/vim#3429) https://github.com/vim/vim/commit/da1f71d75f0bf5d5ef876a09aa08fb19f6f24b3b
* | Merge #9031 from janlazo/vim-8.1.0414Justin M. Keyes2018-09-23
|\ \
| * | vim-patch:8.0.0370: invalid memory access when setting wildchar emptyJan Edmund Lazo2018-09-23
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Invalid memory access when setting wildchar empty. Solution: Avoid going over the end of the option value. (Dominique Pelle, closes vim/vim#1509) Make option test check all number options with empty value. https://github.com/vim/vim/commit/a12e40351d1357687e8b5dc3122fffef705bdc08
| * | vim-patch:8.0.0368: not all options are tested with a range of valuesJan Edmund Lazo2018-09-22
| | | | | | | | | | | | | | | | | | Problem: Not all options are tested with a range of values. Solution: Generate a test script from the source code. https://github.com/vim/vim/commit/2f5463df014a406a2b780068e341ef30a99c9b98
| * | vim-patch:8.1.0414: v:option_old is cleared when using :set in OptionSet autocmdJan Edmund Lazo2018-09-22
| | | | | | | | | | | | | | | | | | | | | Problem: v:option_old and v:option_new are cleared when using :set in OptionSet autocmd. (Gary Johnson) Solution: Don't trigger OptionSet recursively. https://github.com/vim/vim/commit/3f3fb0b14734272e7c817020c847aaa0fba5cea5
* | | func_attr.h: FUNC_ATTR_PRINTFMichael Hoffmann2018-09-23
|/ /
* | Merge #8898 from justinmk/vim-8.1.0310Justin M. Keyes2018-09-22
|\ \ | | | | | | vim-patch:8.1.0310: file info msg with 'F' in 'shortmess'
| * | test/old: test_options: Accommodate Nvim defaultJustin M. Keyes2018-09-21
| | |
| * | vim-patch:8.1.0310: file info msg with 'F' in 'shortmess'Justin M. Keyes2018-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: File info message not always suppressed with 'F' in 'shortmess'. (Asheq Imran) Solution: Save and restore msg_silent. (Christian Brabandt, closes vim/vim#3221) https://github.com/vim/vim/commit/2f0f871159b2cba862fcd41edab65b17da75c422 ref #8840 ref #9027
generated by cgit (git 2.34.1) at 2025-07-02 20:31:04 +0000