| Commit message (Collapse) | Author | Age | 
| | 
| 
| 
| 
| 
|  | 
Among other things, this includes:
- lies about command.com
- references to pcterm
 | 
| | 
| 
| 
| 
| 
|  | 
It helps clarify intent for those unaware of root's UID.
see https://github.com/neovim/neovim/pull/4015#discussion_r49822371
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
- ROOT_UID's comment is misleading, as it's always defined to 0.
- SEEK_{SET,END} & O_NOFOLLOW should already be defined on Unix-like
  systems in <stdio.h> and <fcntl.h>, respectively.  In any case,
  neither of those #ifdef blocks should be in the middle of source files.
- The S_IS{LNK,DIR,...} macros should only be undefined on Windows.
 | 
| | 
| 
| 
| 
| 
| 
|  | 
Windows provides a RGB macro but we have our own in macros.h.
Undefine the Windows one before including macros.h.
See: https://msdn.microsoft.com/en-us/library/dd162937%28v=vs.85%29.aspx
 | 
| |\  
| | 
| |  | 
[RFC] Remove 'swapsync'
 | 
| | | 
| | 
| | 
| |  | 
It's complete overkill.
 | 
| |/  
|   
|   
|    | 
We don't support it.
 | 
| |\  
| | 
| |  | 
vim-patch:7.4.614
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    There is no test for what patch 7.4.601 fixes.
Solution:   Add a test. (Christian Brabandt)
https://github.com/vim/vim/commit/d7ce7a9ad2d9311f7ec3368eeddec8fce6d8e890
 | 
| |/  
|   
|   
|   
|   
|   
|   
|   
|    | 
Problem:    When using the 'c' flag of ":substitute" and selecting "a" or "l"
            at the prompt the flags are not remembered for ":&&". (Ingo
            Karkat)
Solution:   Save the flag values and restore them. (Hirohito Higashi)
https://github.com/vim/vim/commit/cad2fc9935b3a3d9564b4f8d20890b13f14c7d32
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
Problem:    Invalid memory access when there are illegal bytes.
Solution:   Get the length from the text, not from the character. (Dominique
            Pelle)
https://github.com/vim/vim/commit/2186ffa2c7d8a9e2cb09316a7ac9e4ade3957c2f
 | 
| |\  
| | 
| |  | 
Vim 7.4.714
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    Illegal memory access when there are illegal bytes.
Solution:   Check the byte length of the character. (Dominique Pelle)
https://github.com/vim/vim/commit/069dd08d8dbbbadc4e6780d5c881a24bce79a4f7
 | 
| |/  
|   
|   
|   
|   
|   
|   
|    | 
Problem:    When 'list' is set Visual mode does not highlight anything in
            empty lines. (mgaleski)
Solution:   Check the value of lcs_eol in another place. (Christian Brabandt)
https://github.com/vim/vim/commit/d59c099120919d2d77b431308e390f86c594c825
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Mentioned here:
  https://github.com/neovim/neovim/pull/3985#issuecomment-170663426
HAVE_BE64TOH is defined in `config/config.h', which is included by
`vim.h'.  Since the HAVE_BE64TOH check in `shada.c' is evaluated before
`vim.h' is included, it always evaluates to false, meaning that
be64toh() in shada.c is always used instead of the one in <endian.h>.
Moving the HAVE_BE64TOH block to after where `vim.h' is included seems
to fix the issue.
 | 
| |\  
| | 
| |  | 
vim-patch:7.4.569, 7.4.573
 | 
| | | 
| | 
| | 
| | 
| |  | 
process_interrupts() checks get_real_state() so we can avoid some
housekeeping of mapped_ctrl_c in terminal-mode.
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
vim-patch:7.4.569
vim-patch:7.4.573
Helped-by: @glts https://github.com/neovim/neovim/pull/2621
Problem:    Having CTRL-C interrupt or not does not check the mode of the
            mapping. (Ingo Karkat)
Solution:   Use a bitmask with the map mode. (Christian Brabandt)
https://github.com/vim/vim/commit/651863c94a882a97aec7968fc87a638ff78e56ff
Problem:    Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat)
Solution:   Call get_real_state() instead of using State directly.
https://github.com/vim/vim/commit/5000869712f799d9ca25c0e45dc21d332edae5f4
 | 
| |/  
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|   
|    | 
Helped by @Shougo.
vim-patch:7.4.955
vim-patch:7.4.974
vim-patch:7.4.975
vim-patch:7.4.989
Port upstream vim patches 955, 974, 975 and 989. Mark patches
964, 968, 970, and 971, and 982 as NA. Update patch list to 1022.
patch 7.4.955
Problem:    Vim doesn't recognize .pl6 and .pod6 files.
Solution:   Recognize them as perl6 and pod6. (Mike Eve)
patch 7.4.974
Problem:    When using :diffsplit the cursor jumps to the first line.
Solution:   Put the cursor on the line related to where the cursor was before
            the split.
patch 7.4.975
Problem:    Using ":sort" on a very big file sometimes causes text to be
            corrupted. (John Beckett)
Solution:   Copy the line into a buffer before calling ml_append().
patch 7.4.989
Problem:    Leaking memory when hash_add() fails. Coverity error 99126.
Solution:   When hash_add() fails free the memory.
778 marked as not NA as it will be needed once vim patch 754 is merged
Marked as NA:
964 test 87 was deleted
968 tests 86/87 were deleted
970 guarded by: `# if defined(FEAT_GUI_GTK) || defined(PROTO`
    and is inside a function that no longer exists
971 function table already sorted correctly
982 marked as NA because Neovim tests are only specified in exactly one location
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
In Vim, at least the constant `I_PUSH` is used from <stropts.h>, but
Neovim doesn't seem to use anything from said header.
Besides that, POSIX.1-2008[1] marks this header as obsolescent, and
there don't seem to be many platforms that even have it.
[1]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/stropts.h.html#tag_13_52_11
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
For non-Windows systems, we assume that NAME_MAX is in <limits.h>, as
specified in POSIX.1-2008[1]. For Windows, which doesn't have NAME_MAX,
just define it ourselves to _MAX_PATH[2].
Also, remove two (now unused) HAVE_*_H checks.
[1]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
[2]: https://msdn.microsoft.com/en-us/library/930f87yf.aspx
Helped-by: Seth Jackson
 | 
| |\  
| | 
| |  | 
Windows: use ';' as env $PATH separator
 | 
| | | 
| | 
| | 
| | 
| | 
| |  | 
In Windows the separator character in the PATH environment is ';' instead
of ':'. Add a new define ENV_SEPCHAR to be used instead of hardcoding
the character literal.
 | 
| |/   | 
 | 
| |\  
| | 
| |  | 
input: Do not set high-bit. Preserve META modifier.
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Background: Vim internally prefers to represent ALT/META chords as
single-byte keys, by setting the high bit of the key byte.
extract_modifiers() _discards_ the meta/alt modifier, but we need it for
libvterm and libtermkey.
Closes #2440
Closes #3727
Closes #2017
References #2277
References #2254
https://github.com/neovim/neovim/issues/2017#issuecomment-140423557
> We [not libtermkey] are setting the high bit for some reason
https://github.com/neovim/neovim/issues/176#issuecomment-77834715
> libvtermkey requires the leading esc to parse alt/meta
https://github.com/neovim/neovim/pull/3246#issuecomment-136328450
> A program could do better than the current logic on some terminals, by
> asking for pure 8bit mode (S8C1T) and then immediately querying the
> mode again. If the result comes back as an 8bit single-byte CSI, then
> it can presume the mode setting was successful, and now the ESC prefix
> byte won't be seen in multibyte sequences; only as an Alt- prefix or
> a real Escape key. On such a terminal, it could therefore avoid
> needing to use that waiting timeout.
 | 
| |\ \  
| | | 
| | |  | 
shell: Unquote &shell* options before using them
 | 
| | | |  | 
 | 
| | |/  
|/|   
| |   
| |   
| |    | 
MAXNAMLEN can be defined using _MAX_PATH from stdlib.h
which will fix the BASENAMELEN definition too.
 | 
| |/  
|   
|   
|   
|    | 
PRId64 format expects int64_t.
Regression from c6e481cba559d35891f20ef4ac9ca6a41bdcdbd3.
 | 
| |\  
| | 
| |  | 
cmake: Pass MIN_LOG_LEVEL as compiler definition
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| |  | 
- Check if MIN_LOG_LEVEL value is a number 0-3, default to
  INFO (1) or ignore it in Release mode
- When TRAVIS_CI_BUILD is ON the default is DEBUG (0)
- Add local.mk.example
 | 
| | | 
| | 
| | 
| | 
| | 
| |  | 
The block is only compiled if the system is NOT WIN32, but the closing
parenthesis for the statement opened outside the block is closed inside
the block.
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    Running "make newtests" in src/testdir has no output.
Solution:   List the messages file when a test fails. (Christian Brabandt)
            Update the list of tests.
https://github.com/vim/vim/commit/e7893a4088d6ea796bcab6195d232cb26c12c317
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    message from assert_false() does not look nice.
Solution:   Handle missing sourcing_name. Use right number of spaces. (Watiko)
            Don't use line number if it's zero.
https://github.com/vim/vim/commit/cbfe32953aea09d35d9ac7e5865c915b14e310c1
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    When a test script navigates to another buffer the .res file is
            created with the wrong name.
Solution:   Use the "testname" for the .res file. (Damien)
https://github.com/vim/vim/commit/de0ad40cb3c1bc691a754698ed16a5b6cdb4086b
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    v:errors is not initialized.
Solution:   Initialze it to an empty list. (Thinca)
https://github.com/vim/vim/commit/4649ded2877508fe343cbcf6f7e7fd277be0aab3
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    Missing changes in source file.
Solution:   Include changes to the eval.c file.
https://github.com/vim/vim/commit/bbfbaf9741deebb9f1ed790885bd571c4cbce17a
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Problem:    New style testing is incomplete.
Solution:   Add the runtest script to the list of distributed files.
            Add the new functions to the function overview.
            Rename the functions to match Vim function style.
            Move undolevels testing into a new style test script.
https://github.com/vim/vim/commit/683fa185a4b4ed7595e5942901548b8239ed5cdb
 | 
| |/  
|   
|   
|   
|   
|   
|   
|   
|    | 
Problem:    Writing tests for Vim script is hard.
Solution:   Add assertEqual(), assertFalse() and assertTrue() functions.  Add
            the v:errors variable.  Add the runtest script. Add a first new
            style test script.
https://github.com/vim/vim/commit/43345546ae63710441f066648b8485fb545b3801
 | 
| | 
| 
| 
| 
| 
| 
|  | 
The relevant code was never actually in Neovim, most likely due to being
unifdef(1)'d out during the initial import.
see `:h hidden-options'
 | 
| |\  
| | 
| |  | 
eval: Use better error messages when failing to dump values
 | 
| | |  | 
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Examples:
    let g:SR = [[]]
    call add(g:SR[0], g:SR)
    wshada
    " E952: Unable to dump variable g:SR: container references itself in index 0, index 0
    let g:F = {'_TYPE': v:msgpack_types.map, '_VAL': [[{'abc': 1}, function("tr")]]}
    wshada
    " E951: Error while dumping variable g:F, key {'abc': 1} at index 0 from special map, key '': attempt to dump function reference
    " (no msgpack#string available)
    " E951: Error while dumping variable g:F, key {="abc": 1} at index 0 from special map, key '': attempt to dump function reference
    " (msgpack#string available)
    let g:F = {'_TYPE': v:msgpack_types.map, '_VAL': [[g:SR, function("tr")]]}
    wshada
    " E951: Error while dumping variable g:F, key [[[[{E724@0}]]]] at index 0 from special map, index 1: attempt to dump function reference
    call msgpackdump([g:SR])
    " E952: Unable to dump msgpackdump() argument, index 0: container references itself in index 0, index 0
Not tested yet.
 | 
| | | 
| | 
| | 
| |  | 
This was forgotten in 10b2a0e52980aba2d1efc072368fcaf1f33e7512
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| |  | 
The nested line was the else-branch of an if-then-else block that dealt
with cryptography, but after commit
85338fe1d5a56f82546e16c305c2048c081771e0 (Remove cryptography) removed
the if-then part, the indentation of this line was not adjusted.
 |