| Commit message (Collapse) | Author | Age |
|
|
|
| |
We use libuv for high resolution time now so this note is irrelevant.
|
|
|
|
|
|
| |
Among other things, this includes:
- lies about command.com
- references to pcterm
|
|\
| |
| | |
vim-patch:f3c2afb
|
|/
|
|
|
|
| |
Update a few runtime files.
https://github.com/vim/vim/commit/f3c2afb77f8b1f2591337fcaa90ba0fb45365cbc
|
|
|
|
|
|
| |
It helps clarify intent for those unaware of root's UID.
see https://github.com/neovim/neovim/pull/4015#discussion_r49822371
|
|\
| |
| | |
[RFC] test: sys/fcntl.h -> fcntl.h
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
POSIX.1-2008[1] says that the latter should be used, and all of our
supported platforms would seem to support this scheme, apparently even
Windows[2].
[1]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/fcntl.h.html
[2]: https://msdn.microsoft.com/en-us/library/z0kc8e3z.aspx
|
|\ \
| | |
| | | |
[RFC] Misc. macro cleanup
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- 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.
|
|\ \
| |/
|/| |
vim-patch:2b8388b
|
| |
| |
| |
| |
| |
| | |
Updated runtime files.
https://github.com/vim/vim/commit/2b8388bd0175835eb751e6c58cd0b0b69465f0d9
|
| |
| |
| |
| | |
We don't support it.
|
|\ \
| | |
| | | |
[RFC] Windows: Undefine the Windows RGB macro
|
|/ /
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| |/
|/| |
[RFC] Remove references to GTK GUI support + some no-ops
|
|/
|
|
| |
We don't support it.
|
|\
| |
| | |
[RFC] MinGW: don't use -fstack-protector
|
|/
|
|
|
| |
Mingw-w64 fails to link when using -fstack-protector flags, disabled the
flag check for non Unix system.
|
|\
| |
| | |
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
|
|\ \
| |/
|/| |
Vim 7.4.721
|
|/
|
|
|
|
|
|
| |
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
|
|\
| |
| | |
[RFC] shada.c: Fix HAVE_BE64TOH check
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ \
| |/
|/| |
Fix build output paths for Visual Studio generator
|
| |
| |
| |
| |
| |
| |
| | |
The Visual Studio cmake generator creates subdirectories inside
the build path for different build configuration. But this breaks some of our
cmake scripts, like the help tags installer, that assume the targets are
built in that location. Updated CMakeLists.txt to remove extra paths.
|
|\ \
| | |
| | | |
[RFC] config: Cleanup unused identifiers.
|
|/ /
| |
| |
| |
| |
| | |
HAVE_CRT_EXTERNS_H is unused since a3ec68c.
SIZEOF_OFF_T is unused since f916cf0.
HAVE_LIBGEN_H was never used.
|
|\ \
| | |
| | | |
[RFC] Stop using <stropts.h>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | | |
[RDY] os/*_defs.h: MAXNAMLEN cleanup
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \ \
| | | |
| | | | |
Remove redundant functions to replace for the general has_event function
|
| |/ / |
|
|/ /
| |
| |
| | |
We don't support it.
|
|\ \
| | |
| | | |
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
|