| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Illegal memory access.
Solution: Check for missing pattern. (Dominique Pelle)
|
|
Problem: Illegal memory access with weird syntax command. (Dominique Pelle)
Solution: Check for column past end of line.
|
|
Problem: Only terminals with up to 256 colors work properly.
Solution: Use the 256 color behavior for all terminals with 256 or more
colors. (Robert de Bath, closes #504)
|
|
Problem: Crash when using "syn keyword x c". (Dominique Pelle)
Solution: Initialize the keyword tabble. (Raymond Ko, PR 397)
|
|
Problem: Invalid memory access for ":syn keyword x a[".
Solution: Do not skip over the NUL. (Dominique Pelle)
|
|
Problem: More problems reported by coverity.
Solution: Avoid the warnings. (Christian Brabandt)
|
|
Problem: Illegal memory access with "sy match a fold".
Solution: Check for empty string. (Dominique Pelle)
|
|
Problem: Spelling mistakes are not displayed after ":syn spell".
Solution: Force a redraw after ":syn spell" command. (Christian Brabandt)
|
|
Problem: The first syntax entry gets sequence number zero, which doesn't
work. (Clinton McKay)
Solution: Start at number one. (Bjorn Linse)
|
|
Problem: Using freed memory when g:colors_name is changed in the colors
script. (oni-link)
Solution: Make a copy of the variable value.
|
|
Problem: Some function headers may be missing from generated .pro files.
Solution: Add PROTO to the #ifdef.
|
|
Problem: When using ":ownsyntax" spell checking is messed up. (Issue 78)
Solution: Use the window-local option values. (Christian Brabandt)
|
|
Problem: Crash when using syntax highlighting.
Solution: When regprog is freed and replaced, store the result.
|
|
Problem: Check for whether a highlight group has settings ignores fg and bg
color settings.
Solution: Also check cterm and GUI color settings. (Christian Brabandt)
|
|
Problem: Now that the +visual feature is always enabled the #ifdefs for it
are not useful.
Solution: Remove the checks for FEAT_VISUAL.
|
|
Problem: ColorScheme autocommand matches with the current buffer name.
Solution: Match with the colorscheme name. (Christian Brabandt)
|
|
Problem: New regexp engine: Matching plain text could be faster.
Solution: Detect a plain text match and handle it specifically. Add
vim_regfree().
|
|
Problem: No command line completion for ":syntime".
Solution: Implement the completion. (Dominique Pelle)
|
|
Problem: Memory leak in ":syntime report".
Solution: Clear the grow array. (Dominique Pelle)
|
|
Problem: Compiler warning for unused argument.
Solution: Add UNUSED.
|
|
Problem: Can't build with anything but huge features.
Solution: Check for FEAT_PROFILE. (Yasuhiro Matsumoto)
|
|
Problem: Can't see what pattern in syntax highlighting is slow.
Solution: Add the ":syntime" command.
|
|
Problem: Typos in source files.
Solution: Fix the typos. (Ken Takata)
|
|
Problem: Trying to create a fontset handle when 'guifontset' is not set.
Solution: Add curly braces around the code block. (Max Kirillov)
|
|
Problem: ml_get error when searching, caused by curwin not matching curbuf.
Solution: Avoid changing curbuf. (Lech Lorens)
|
|
Problem: Can't build Motif version.
Solution: Fix wrongly named variable. (Ike Devolder)
|
|
Problem: Leaking resources when setting GUI font.
Solution: Free the font. (Ken Takata)
|
|
Problem: With an 8 color terminal the selected menu item is black on black,
because darkGrey as bg is the same as black.
Solution: Swap fg and bg colors. (James McCoy)
|
|
Problem: Compiler warning from Clang.
Solution: Use a different way to point inside a string. (Dominique Pelle)
|
|
Problem: When 'cursorline' is set the line number highlighting can't be set
separately.
Solution: Add "CursorLineNr". (Howard Buchholz)
|
|
Problem: In a terminal with few colors the omnicomplete menu may be hard to
see when using the default colors.
Solution: Use more explicit colors. (suggested by Alex Henrie)
|
|
Problem: Compiler warnings for shadowed variables.
Solution: Remove or rename the variables.
|
|
Problem: On a 64 bit system "syn sync fromstart" is very slow. (Bjorn
Steinbrink)
Solution: Store the state when starting to parse from the first line.
|
|
Problem: Syntax "extend" doesn't work correctly.
Solution: Avoid calling check_state_ends() recursively (Ben Schmidt)
|
|
Problem: When there is a "containedin" syntax argument highlighting may be
wrong. (Radek)
Solution: Reset current_next_list. (Ben Schmidt)
|
|
Problem: Unsafe string copying.
Solution: Use vim_strncpy() instead of strcpy(). Use vim_strcat() instead
of strcat().
|
|
Problem: Can't compile with tiny features. (Tony Mechelynck)
Solution: Move #define outside of #ifdef.
|
|
Problem: A syntax file with a huge number of items or clusters causes weird
behavior, a hang or a crash. (Yukihiro Nakadaira)
Solution: Check running out of IDs. (partly by Ben Schmidt)
|
|
Problem: Conceal: using Tab for cchar causes problems. (ZyX)
Solution: Do not accept a control character for cchar.
|
|
Problem: smatch reports errors.
Solution: Fix the reported errors. (Dominique Pelle)
|
|
|
|
through them.
|
|
|
|
|
|
can show the 'cchar' for each of them.
|
|
replacement character for both.
|
|
(Matt Wozniski)
|
|
|
|
Cleanup white space.
|
|
|
