| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace long_i with plain long.
long_i was just plain long, adding marker __w64, to be used by
Microsoft's compilers only, as an aid when transitioning from 32 bits to
64 bits. Purpose of this marker was, in fact, to make a 32 bit compiler
emit the same warnings that a 64 bit compiler would.
This __w64 marker is nowadays deprecated by said compilers, and use of a
real 64 bit compiler is recommended instead. See
http://msdn.microsoft.com/en-us/library/s04b5w00.aspx for details.
So, there's no reason to maintain this anymore, and thus is removed.
Refactoring long into int64_t is not attempted, as doing that in a bulk
way is too much complicated. That is left to be done later, on a
file-by-file basis, probably intermixed with file-by-file -Wconversion
activation.
Requested in #459.
|
|
|
|
|
|
|
|
|
| |
- Replace int_u with uint32_t (same size, should give no problems).
In fact, only usage found seems to be dead code (some functions in
ui.h seem not to be used anymore).
- Remove int_u typedef.
Requested in #459.
|
|
|
|
|
|
|
|
|
| |
- Replace short_u with uint16_t (same size, should give no problems).
- When possible, remove explicit downcasts so that they are found when
flag -Wconversion enabled.
- Remove short_u typedef.
Requested in #459.
|
|
|
|
|
| |
The old version required to change the range given to :w for each new
test. Now a new buffer is used instead.
|
| |
|
| |
|
| |
|
|
|
|
| |
ref #572
|
|
|
|
| |
They were only defined for MSDOS which is now unsupported.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Files changed: charset.c, buffer.c, diff.c, edit.c,
ex_cmds.c, ex_cmds2.c and ex_docmd.c.
The remaining alloc's in these files require more careful attention to
remove.
|
|
|
|
|
|
|
| |
reverting broad cosmetic/style change because:
- increases merge-conflicts
- increases overhead of merging upstream Vim patches
- reasons for change are ambiguous, so default to no change
|
|
|
| |
If this backslash is here and USE_VALGRIND is defined, valgrind complains that "else" is not a command.
|
|
|
|
|
|
|
|
| |
Problem: Using just "$" does not cause an error message.
Solution: Check for empty environment variable name.
(Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=00228400629e28384f7f52556c3c119ba0d0a44d
|
| |
|
|
|
|
|
|
|
|
|
| |
Problem: Using exists() on a funcref for a script-local function
does not work.
Solution: Translate <SNR> to the special byte sequence.
Add a test.
https://code.google.com/p/vim/source/detail?r=1a5ed2626b26a982e307a206572121a557adf709
|
| |
|
|
|
|
|
|
|
|
| |
Problem: CTRL-U in Insert mode does not work after using a cursor key.
(Pine Wu)
Solution: Use the original insert start position. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=81c26975e8f9dc7435353581346542409403f296
|
|
|
|
|
|
|
| |
Problem: Test 62 fails.
Solution: Set the language to C. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=8f84e906d454a95d3167678a745dde9de442b604
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Remove unnecessary else
* Move variable declaration nearer to point of use
* Add missing curly brackets
* Comment style
|
|
|
|
| |
Clean up the use of rettv_list_alloc and remove error checks.
|
|
|
|
| |
Clean up the use of list_append_tv and remove error checks.
|
|
|
|
| |
Clean up the use of list_append_number and remove error checks.
|
| |
|
|
|
|
|
|
|
| |
Problem: Duplicate code in regexec().
Solution: Add line_lbr flag to regexec_nl().
https://code.google.com/p/vim/source/detail?r=0ea551fa607dc443b97c2fba97dc0c9cb0bcf303
|
|
|
|
|
|
|
| |
The following functions are affected:
- ga_remove_duplicate_strings
- ga_append
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've checked all uses of ga_concat in the codebase:
- ex_cmds2.c
- ex_getln.c
- eval.c
- message.c
- regexp-nfa.c
- term.c
- spell.c
None of them concats the garray with itself. This makes it safe to use the
faster memcpy() instead of memmove(). This change was also documented.
|
| |
|
|
|
|
|
| |
A generalized version of ga_concat_strings that can handle any separator.
Reimplement ga_concat_strings on top of it.
|
|
|
|
|
|
|
| |
Less useless strlen(), stpcpy() is a more natural fit for this task.
ga_concat_strings() still has too much strlen() but that would be ugly to
remove for a function that's not used very often (just once in the current
codebase).
|
|
|
|
|
| |
Both are implemented to POSIX 2008 spec, though I'm not sure I'm happy about
stpncpy's behaviour.
|
|
|
|
|
|
|
| |
- xrealloc will call xmalloc if the input pointer is NULL, no need to check
twice.
- use the early-quit idiom to decrease the indentation, which enhances
readability.
|
|
|
|
|
| |
Rename `shorten_fname` -> `path_shorten_fname`
Rename `shorten_fname1` -> `path_shorten_fname_if_possible`
|
| |
|
| |
|
|
|
|
|
|
|
| |
The function prototypes use garray_T* arguments, but the header is not
included in path.h. Technically we could also get away with a forward
declaration since we're just using the pointer, but I don't see the urgent
need for that.
|
|
|
|
|
|
|
|
| |
Problem: The string returned by submatch() does not distinguish between a
NL from a line break and a NL that stands for a NUL character.
Solution: Add a second argument to return a list. (ZyX)
https://code.google.com/p/vim/source/detail?r=a63d0cd691dc925283815d17d62f4e948d723a59
|
|
|
|
|
|
|
| |
Problem: Can't call a global function with "g:" in an expression.
Solution: Skip the "g:" when looking up the function.
https://code.google.com/p/vim/source/detail?r=8ec9d2196bee0c5108f2d2c196a660a7f4e5f29f
|
|
|
|
|
|
|
|
|
| |
Problem: Can't define a function starting with "g:". Can't assign a
funcref to a buffer-local variable.
Solution: Skip "g:" at the start of a function name.
Don't check for colons when assigning to a variable.
https://code.google.com/p/vim/source/detail?r=00acac0af680c2d8c82db5258474b121a5908926
|
|
|
|
|
| |
At some places, printf-like function's arguments styling could be
improved to enhance readability.
|
|
|
|
|
|
|
|
|
| |
Though correct (to my understanding), some of the casts introduced in
previous commits could lead to confusion, by casting only the first
expression component instead of the whole expression.
This fixes that, parenthesizing casted expressions, except where
operator precedence rules make it unneccesary.
|
| |
|