| Commit message (Collapse) | Author | Age |
| ... | |
| |/
|
|
|
|
|
| |
The latest version works around a libuv bug that can leave zombie nvim processes
despite the event loop being properly cleaned up. This can lead to functional
tests being aborted depending on the maximum number of child processes
configured for a platform.
|
| |\
| |
| |
| | |
stricter highlight tests'
|
| | | |
|
| |/ |
|
| |\
| |
| | |
doc: "halfway a line" is a very confusing phrase
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
If you Google for this phrase found in the Vim documentation you'll find
almost exclusively hits from the Vim documentation. I think changing
"halfway a line" to "halfway through a line" makes more sense.
There seems to be an pervasive odd use of the word 'halfway' in the
original docs which I'm updating everywhere.
|
| |\ \
| | |
| | | |
vim-patch:7.4.500 and fix in vim-patch:7.4.406
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| | |
Problem: Test 72 still fails once in a while.
Solution: Don't set 'fileformat' to unix, reset it. (Ken Takata)
https://code.google.com/p/vim/source/detail?r=v7-4-500
|
| |\ \
| | |
| | | |
Fix CID #102150
|
| | |/
| |
| |
| |
| |
| |
| | |
Don't attempt to write an error message to a channel that may have been
closed and freed.
[CID #102150](https://scan8.coverity.com/reports.htm#v22612/p10672/fileInstanceId=3625286&defectInstanceId=1525721&mergedDefectId=102150)
|
| |\ \
| | |
| | | |
vim-patch: Mark patches as NA.
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | | |
- shortmess+=I: Remove intro screen
- background=light: Disregard COLORFGBG environment variable
|
| | | |
| | |
| | |
| | | |
Replace the hexadecimal escape sequences, which are only supported by luajit
|
| |/ / |
|
| |\ \
| |/
|/| |
vim-patch:bd18da9 (runtime update)
|
| |/
|
|
|
|
| |
Update runtime files.
https://code.google.com/p/vim/source/detail?r=bd18da914be9d43a70713f6af02770a0d3280159
|
| |\
| |
| | |
Remove "easy" mode.
|
| | | |
|
| |\ \
| | |
| | | |
vim-patch:7.4.462
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Setting the local value of 'backupcopy' empty gives an error.
(Peter Mattern)
Solution: When using an empty value set the flags to zero. (Hirohito
Higashi)
https://code.google.com/p/vim/source/detail?r=v7-4-462
|
| |\ \ \
| |/ /
|/| | |
vim-patch:7.4.446
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: In some situations, when setting up an environment to trigger an
autocommand, the environment is not properly restored.
Solution: Check the return value of switch_win() and call restore_win()
always. (Daniel Hahler)
https://code.google.com/p/vim/source/detail?r=v7-4-446
|
| |\ \
| | |
| | | |
vim-patch:47b1887 (runtime update)
|
| |/ /
| |
| |
| |
| |
| | |
Updated runtime files.
https://code.google.com/p/vim/source/detail?r=47b1887483da0bc33d26a3e8d89973d76c9f39ef
|
| |\ \
| | |
| | | |
coverity/102151: initialize `our_paren_pos`
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This hoists the initialization of `our_paren_pos` outside a conditional
so it can be safely referenced further down in this function.
Originally broken in:
https://code.google.com/p/vim/source/diff?spec=svndc8197342755fda6ca4d6619dac228406867a7ce&old=01583c79d5f4d3f29d4c33dd10dd29efd349cad0&r=dc8197342755fda6ca4d6619dac228406867a7ce&format=unidiff&path=%2Fsrc%2Fmisc1.c
This fixes CID #102151
https://scan8.coverity.com/reports.htm#v22612/p10672/fileInstanceId=3625174&defectInstanceId=1525719&mergedDefectId=102151
|
| |\ \ \
| | | |
| | | | |
vim-patch:7.4.492
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: In Insert mode, after inserting a newline that inserts a comment
leader, CTRL-O moves to the right. (ZyX) Issue 57.
Solution: Correct the condition for moving the cursor back to the NUL.
(Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-492
|
| |\ \ \
| | | |
| | | | |
Remove project-specific integer types: long_u. (5)
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | | |
CommandDefinition.cmd_argt: long_u --> uint32_t.
|
| |\ \ \
| | | |
| | | | |
vim-patch:7.4.490
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Cannot specify the buffer to use for "do" and "dp", making them
useless for three-way diff.
Solution: Use the count as the buffer number. (James McCoy)
https://code.google.com/p/vim/source/detail?r=v7-4-490
|
| |\ \ \ \
| |_|/ /
|/| | | |
vim-patch.sh: Add option to list missing Vim changesets.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
job.c: Prevent early return from job_wait().
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
A blocking call job_wait(job, -1) can only return after job is finished
and all handles of job are closed. But hitting CTRL-C makes job_wait()
return early while handles can still be open. This can lead to problems
with the job/handle callbacks if the caller (of job_wait()) already
freed the memory that is used in the job callbacks.
To fix this, only return after all handles of the job are closed.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
test: Correct lfs.attributes() call, and allow unit tests to run with gcc on OSX
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The primitive C canonicalizer we use to strip out duplicate header
declarations and keep luajit's ffi happy, didn't work properly in this case.
What happened is this (in /usr/include/ctype.h):
__DARWIN_CTYPE_TOP_inline int
isspecial(int _c)
{
return (__istype(_c, _CTYPE_T));
}
Gets preprocessed to something like:
__inline int
isspecial(int _c)
{
return (__istype(_c, _CTYPE_T));
}
On OSX/gcc. The formatter wasn't recognizing this entire function as
something to put on a single line because it naively just checks for
"static" or "inline" for that, but not "__inline".
This error doesn't occur on OSX/clang. Without looking further into it, I
guess that __DARWIN_CTYPE_TOP_inline gets defined to inline on clang, but
__inline on gcc, for some reason.
This helps issue #1572 along.
|