aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* 'keymap' now uses :lmap instead of :lnoremapMatthew Malcomson2018-03-14
| | | | | | | This means that the major way that :lmap mappings are applied works as one would expect with macros. This also means that having a translation with 'keymap' does not preclude using mappings in insert mode with :imap.
* Ensure :lmap mappings take preferenceMatthew Malcomson2018-03-14
| | | | | | If the mental model of :lmap mappings is a translation between your keyboard and vim proper, then they should take preference over :imap (and other) mappings. This patch makes that happen.
* Record :lmap transformed keys in gotchars()Matthew Malcomson2018-03-14
| | | | | | | The mental model of :lmap and 'keymap' is of a transformation done before anything else. Hence when recording a macro, or writing to a scriptfile, the transformed keys should be recorded instead of the keys before the transformation.
* vim-patch:8.0.0316: :help z? does not work (#8134)KunMing Xie2018-03-14
| | | | | Problem: ":help z?" does not work. (Pavol Juhas) Solution: Remove exception for z?. https://github.com/vim/vim/commit/dad7309dd22f0c6b5de0b031acd7f54d3aa94326
* Add missing PVS headers to new filesJames McCoy2018-03-11
|
* vim-patch:8.0.0262,8.0.0263 (#8123)KunMing Xie2018-03-11
| | | | | | | | | | | | | vim-patch:8.0.0262: Farsi support is barely tested Problem: Farsi support is barely tested. Solution: Add more tests for Farsi. Clean up the code. https://github.com/vim/vim/commit/ddf662a1c86ef0b4bd0c55c5f0aa192ebd6d9a5e vim-patch:8.0.0263: Farsi support is not tested enough Problem: Farsi support is not tested enough. Solution: Add more tests for Farsi. Clean up the code. https://github.com/vim/vim/commit/80627cf51fd4274320875193a43ce11cee58c96e
* Merge #8084 'build/win: support MSVC'Justin M. Keyes2018-03-08
|\
| * build/msvc: Remove confusing commentb-r-o-c-k2018-03-04
| |
| * build/msvc: Workaround for compiler optimization bugb-r-o-c-k2018-03-04
| |
| * build/msvc: Fix errors caused by compiler intrinsicsb-r-o-c-k2018-03-04
| |
| * build/msvc: Add missing WIN32 macrob-r-o-c-k2018-03-04
| | | | | | | | MSVC predefines `_WIN32`, but not `WIN32`. Also, some unnecessary includes have been removed.
| * Merge branch 'master' into msvc-compatb-r-o-c-k2018-03-01
| |\
| * | build/msvc: Remove unnecessary header includeb-r-o-c-k2018-02-28
| | |
| * | build/msvc: Fix standard IO file number definitionsb-r-o-c-k2018-02-28
| | | | | | | | | | | | With MSVC, STDOUT_FILENO and STDERR_FILENO are defined as function calls instead of constants, meaning they can't be assigned to enum values. The enum was only used in one file, so it has been removed. A definition for STDIN_FILENO has been added that is consistent with the other two definitions.
| * | build/msvc: Fix missing restrict keywordb-r-o-c-k2018-02-28
| | | | | | | | | | | | MSVC has the __restrict keyword and a marco is defined for it in `win_defs.h`.
| * | build/msvc: Move include into unix_defs.hb-r-o-c-k2018-02-28
| | |
| * | build/msvc: Add mode_t typedef to win_defs.hb-r-o-c-k2018-02-28
| | |
| * | build/msvc: Fix preprocessor parsingb-r-o-c-k2018-02-28
| | | | | | | | | | | | Preprocessor directives on the first line of the file were not being parsed.
* | | version.c: update [ci skip] (#7999)Marvim the Paranoid Android2018-03-08
| | | | | | | | | | | | | | | NA: vim-patch:8.0.0207: leaking file descriptor when system() fails vim-patch:8.0.1434: GTK: :promtfind does not put focus on text input
* | | vim-patch:8.0.0513: fix getting name of cleared highlight group (#8103)KunMing Xie2018-03-08
| | | | | | | | | | | | | | | | | | | | | Problem: Getting name of cleared highlight group is wrong. (Matt Wozniski) Solution: Only skip over cleared names for completion. (closes vim/vim#1592) Also fix that a cleared group causes duplicate completions. https://github.com/vim/vim/commit/c96272e30e2b81e5e0c8418f09d9db4e2fcd5d73
* | | vim-patch:8.0.0220: highlight completion misses some values #8013ckelsel2018-03-04
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Completion for :match does not show "none" and other missing highlight names. Solution: Skip over cleared entries before checking the index to be at the end. https://github.com/vim/vim/commit/15eedf1d621d980cb40f50cc6a78a09ab94388c7
* | | vim-patch:8.0.0234,8.0.0236,8.0.0225 (#8052)KunMing Xie2018-03-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vim-patch:8.0.0234: crash when using put in Visual mode Problem: When several lines are visually selected and one of them is short, using put may cause a crash. (Axel Bender) Solution: Check for a short line. (Christian Brabandt) https://github.com/vim/vim/commit/941c12da3c087fd04aa6c120a76bf28f19349d96 vim-patch:8.0.0236: gcc complains about uninitialized variable Problem: Gcc complains that a variable may be used uninitialized. Confusion between variable and label name. (John Marriott) Solution: Initialize it. Rename end to end_lnum. https://github.com/vim/vim/commit/6a717f17ec6b09634be1c29e0ac4c35213f7b32d vim-patch:8.0.0225: put in Visual block mode terminates early Problem: When a block is visually selected and put is used on the end of the selection only one line is changed. Solution: Check for the end properly. (Christian Brabandt, neovim issue 5781) https://github.com/vim/vim/commit/9957a10d0f0c34d8083af6ed66e198e4796038e0
* | | message: don't output unprintable chars to screenBjörn Linse2018-03-04
| | | | | | | | | | | | fixes #7586 #8070
* | | vim-patch:8.0.1561: crash with rust syntax highligting (#8095)James McCoy2018-03-03
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Crash with rust syntax highligting. (Edd Barrett) Solution: Avoid going past the end of an empty line. https://github.com/vim/vim/commit/069dafc1ded60d9ee0fee4bcecce78ac8a235d87 Closes #6248
* | | api: nvim_list_uis #8004geekodour2018-03-03
| | | | | | | | | | | | | | | ref #7438 closes #4842
* | | Merge #8072 from mhinz/vim-8.0.1439Justin M. Keyes2018-03-03
|\ \ \ | |_|/ |/| | vim-patch: 8.0.1439, 8.0.1442
| * | vim-patch:8.0.1442: using pointer before it is setMarco Hinz2018-02-26
| | | | | | | | | | | | | | | | | | | | | Problem: Using pointer before it is set. Solution: Search in whole buffer instead of next token. https://github.com/vim/vim/commit/a172b63ab8661019dba61285a738c8b6b55a33aa
| * | vim-patch:8.0.1439: if cscope fails a search Vim may hangMarco Hinz2018-02-26
| |/ | | | | | | | | | | | | | | Problem: If cscope fails a search Vim may hang. Solution: Bail out when a search error is encountered. (Safouane Baroudi, closes vim/vim#2598) https://github.com/vim/vim/commit/1274d33493efb6250470a37b9f4432bb31e87d64
* / cscope: ignore EINTR while reading the prompt (#8079)Marco Hinz2018-02-28
|/ | | | | | | | | | | | | | | | | | | | The following code.. au VimEnter,DirChanged * if filereadable('.git/cscope.out') | \ exe 'cs add .git/cscope.out' | endif ..would lead to this issue: Error detected while processing VimEnter Auto commands for "*": cs_read_prompt EOF: Interrupted system call Error detected while processing VimEnter Auto commands for "*": E262: error reading cscope connection 0 A signal, in this case SIGCHLD, during a system call leads to errno being set to EINTR. Ignore it. This is merely a workaround for the time being. We don't block SIGCHLD signals, since they're needed by libuv. The proper fix would be to rewrite if_cscope.c to use libuv for handling processes.
* shada: fix typo (#8066)Daniel Hahler2018-02-25
|
* screen.c: make negative 'writedelay' show all redrawsBjörn Linse2018-02-24
| | | | | | | | | | | | | | | | | | | | Currently writedelay shows the sequence of characters that are sent to the UI/TUI module. Here nvim has already applied an optimization: when attempting to put a char in a screen cell, if the same char already was there with the same attributes, UI output is disabled. When debugging redrawing it it sometimes more useful to inspect the redraw stream one step earlier, what region of the screen nvim actually is recomputing from buffer contents (win_line) and from evaluating statusline expressions. Take the popupmenu as an example. When closing the popupmenu (in the TUI), currently 'writedelay' looks like vim only is redrawing the region which the pum covered. This is not what happens internally: vim redraws the entire screen, even if only outputs the changed region. This commit allows negative values of 'writedelay', which causes a delay for all redrawn characters, even if the character already was displayed by the UI before.
* 'fillchars': fix defaults logic; handle ambiwidth=double #7986Matthieu Coudron2018-02-23
| | | | Update tests.
* defaults: 'fillchars'Justin M. Keyes2018-02-23
| | | | | | | | | | | Most fonts should have these by now. Both are a significant visual improvement. - Vertical connecting bar `│` is used by tmux, pstree, Windows 7 cmd.exe and nvim-qt.exe. - Middle dot `·` works on Windows 7 cmd.exe, nvim-qt.exe. For reference: tmux uses these chars to draw lines: │ ├ ─
* ui_bridge: make sure TUI receives no more UI events after "stop" eventBjörn Linse2018-02-22
|
* vim-patch:8.0.0225: put in Visual block mode terminates early (#8040)UTkarsh Maheshwari2018-02-21
| | | | | | | Problem: When a block is visually selected and put is used on the end of the selection only one line is changed. Solution: Check for the end properly. (Christian Brabandt, neovim issue 5781) https://github.com/vim/vim/commit/9957a10d0f0c34d8083af6ed66e198e4796038e0
* screen: win_del_lines/win_ins_lines cleanupBjörn Linse2018-02-21
|
* screen: remove dead code emulating terminals without scroll regionsBjörn Linse2018-02-21
| | | | This logic is now in tui/tui.c
* vim-patch:8.0.0222: blockwise put on multi-byte char (#8030)KunMing Xie2018-02-20
| | | | | | | | | Note: code change was covered by c2a18216114bae75b6d6a2c7f1a68db04578abce Problem: When a multi-byte character ends in a zero byte, putting blockwise text puts it before the character instead of after it. Solution: Use int instead of char for the character under the cursor. (Luchr, closes vim/vim#1403) Add a test. https://github.com/vim/vim/commit/c81299684b2b9045e56525d3da3f45e8440fbf0d
* Merge pull request #8031 from bfredl/gotintstatusBjörn Linse2018-02-20
|\ | | | | jobwait: return -2 on interrupt even with timeout
| * jobwait: return -2 on interrupt also with timeoutBjörn Linse2018-02-20
| |
* | vim-patch:8.0.0214 (#8010)KunMing Xie2018-02-19
| | | | | | | | | | | | | | | | | | vim-patch:8.0.0214: leaking memory when syntax cluster id is unknown Problem: Leaking memory when syntax cluster id is unknown. (Coverity) Solution: Free the memory. https://github.com/vim/vim/commit/d7a96151e0c86e8d4f9162c919cf3ff400a893b6
* | build/gcc: disable -Warray-bounds entirely #7923Justin M. Keyes2018-02-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to disable -Warray-bounds locally for kbtree.h, but we can't because _Pragma("GCC diagnostic pop") is broken in GCC 5.x+. So this commit disables -Warray-bounds entirely (for GCC only). GCC bug: "_Pragma diagnostic 'ignored' in macro with strict-overflow not suppressing warning fully with -Werror" https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66099 ref https://github.com/neovim/neovim/pull/7083#issuecomment-326323599 closes #7921
* | vim-patch:8.0.1493: completion items cannot be annotated (#8003)Shougo2018-02-18
| | | | | | | | | | | | | | Problem: Completion items cannot be annotated. Solution: Add a "user_data" entry to the completion item. (Ben Jackson, coses vim/vim#2608, closes vim/vim#2508) https://github.com/vim/vim/commit/9b56a57cdae31f7a2c85d440392bf63d3253a158
* | vim-patch:8.0.0212: buffer for key name may be too small (#8009)KunMing Xie2018-02-18
| | | | | | | | | | | | | | | | | | Problem: The buffer used to store a key name theoreticaly could be too small. (Coverity) Solution: Count all possible modifier characters. Add a check for the length just in case. https://github.com/vim/vim/commit/423977d3cebac2be1158b1d11da60fe96db4b750
* | vim-patch-8.0.0649 and vim-patch-8.0.0650: autocmd open help 2 timesNimit Bhardwaj2018-02-17
|/
* vim-patch:8.0.0323: one second pause when running cmdline test (#8015)Danish Prakash2018-02-16
| | | | | | Problem: When running the command line tests there is a one second wait. Solution: Change an Esc to Ctrl-C. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/31eb139b8877439d06db0ca57692dfe35fec3f0c
* Merge pull request #8008 from bfredl/arrayfreeBjörn Linse2018-02-14
|\ | | | | ex_getln: clear cmdline_block after it's freed
| * ex_getln: clear cmdline_block after it's freedBjörn Linse2018-02-14
| |
* | ui: refactor ui optionsBjörn Linse2018-02-13
|/
* Merge #8001 from justinmk/vimpatchesJustin M. Keyes2018-02-12
|\
generated by cgit (git 2.34.1) at 2025-08-13 04:12:21 +0000