Re: Issue 25 in vim: cross-compiling vim fails due to uint32_t check

Updates: Status: Fixed Comment #2 on issue 25 by chrisbr...@googlemail.com: cross-compiling vim fails due to uint32_t check https://code.google.com/p/vim/issues/detail?id=25 Fixed by 7.3.378 -- You received this message because this project is configured to send all issue notificat

Re: Issue 23 in vim: matchparen matches parens in strings with syntax off despite what :help matchparen says

Updates: Status: Invalid Comment #1 on issue 23 by chrisbr...@googlemail.com: matchparen matches parens in strings with syntax off despite what :help matchparen says https://code.google.com/p/vim/issues/detail?id=23 Documentation states explicitly, that syntax highlighting attributes

Re: Issue 7 in vim: terminal resize during file recovery

Comment #1 on issue 7 by chrisbr...@googlemail.com: terminal resize during file recovery https://code.google.com/p/vim/issues/detail?id=7 Is this still an issue? If I resize the terminal when Vim is displaying the Attention message, I see, that Vim is correctly resizing at least the dialo

Re: Issue 26 in vim: Ctrl-C doesn't perform interrupt after map/unmap

Comment #1 on issue 26 by chrisbr...@googlemail.com: Ctrl-C doesn't perform interrupt after map/unmap https://code.google.com/p/vim/issues/detail?id=26 This happens, because mapped_ctrl_c is never reset. This patch fixes it: diff --git a/src/getchar.c b/src/getchar.c --- a/src/getchar.c +++

Re: Issue 28 in vim: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7

Updates: Status: Fixed Comment #17 on issue 28 by chrisbr...@googlemail.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 https://code.google.com/p/vim/issues/detail?id=28 Fixed by 7.4.112 -- You received this message because this project is configured t

Re: Issue 34 in vim: D highlighter: Add new version identifiers and some built-in types

Updates: Status: Fixed Comment #6 on issue 34 by chrisbr...@googlemail.com: D highlighter: Add new version identifiers and some built-in types https://code.google.com/p/vim/issues/detail?id=34 If I read the runtime file correctly that are included with Vim 7.4.460, this patch seems

Re: Issue 29 in vim: online help has link to wrong node

Updates: Status: Invalid Comment #3 on issue 29 by chrisbr...@googlemail.com: online help has link to wrong node https://code.google.com/p/vim/issues/detail?id=29 (No comment was entered for this change.) -- You received this message because this project is configured to send all i

Re: Issue 54 in vim: :command -complete option affects processing command arguments

Comment #1 on issue 54 by chrisbr...@googlemail.com: :command -complete option affects processing command arguments https://code.google.com/p/vim/issues/detail?id=54 Let's just document that behaviour for now: diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt --- a/runtime/doc/map.txt +

Re: Issue 51 in vim: CSS Syntax structure incompatible with extended syntaxes (eg less)

Updates: Status: WontFix Comment #2 on issue 51 by chrisbr...@googlemail.com: CSS Syntax structure incompatible with extended syntaxes (eg less) https://code.google.com/p/vim/issues/detail?id=51 This should be taken to the maintainer of the syntax file. As of Vim 7.4.460, the mainta

Re: Issue 55 in vim: b:undo_ftplugin is not defined in some files under ftplugins (patch attached)

Updates: Status: Invalid Comment #3 on issue 55 by chrisbr...@googlemail.com: b:undo_ftplugin is not defined in some files under ftplugins (patch attached) https://code.google.com/p/vim/issues/detail?id=55 Runtime file updates should be taken to the maintainer of the files. Closing

Re: Issue 51 in vim: CSS Syntax structure incompatible with extended syntaxes (eg less)

Comment #3 on issue 51 by w.jq0...@gmail.com: CSS Syntax structure incompatible with extended syntaxes (eg less) https://code.google.com/p/vim/issues/detail?id=51 Hi, We have noticed this issue: https://GitHub.com/juleswang/css.vim/pull/38 There are two options to fix this issue: 1. The mai

Re: Issue 203 in vim: Nothing in register * problem (vim+tmux or vim+screen )

Comment #3 on issue 203 by boi...@gmail.com: Nothing in register * problem (vim+tmux or vim+screen ) https://code.google.com/p/vim/issues/detail?id=203 Same here, with iTerm2 which uses tmux under the hood. -- You received this message because this project is configured to send all issue n

Re: Issue 54 in vim: :command -complete option affects processing command arguments

Comment #2 on issue 54 by brammool...@gmail.com: :command -complete option affects processing command arguments https://code.google.com/p/vim/issues/detail?id=54 I'll include that change. -- You received this message because this project is configured to send all issue notifications to thi

Re: [patch] several problems with drawing overlong lines

Christian wrote: > I noticed some problems with Vim displaying lines, that are longer than > the actual screen size. > > For one, if the precedes listchar option is set, this will be drawn even > when 'showbreak' is set and the list option is not. The easy fix is: [...] > 2) When 'nu' or 'rn

Re: Issue 57 in vim: After creating a new line using moves one character forward

Comment #1 on issue 57 by chrisbr...@googlemail.com: After creating a new line using moves one character forward https://code.google.com/p/vim/issues/detail?id=57 The attached patch fixes the issue and includes a test. Attachments: issue_57.diff 1.2 KB -- You received this messag

Re: Issue 66 in vim: Mouse reporting for wide windows

Updates: Status: Fixed Comment #4 on issue 66 by chrisbr...@googlemail.com: Mouse reporting for wide windows https://code.google.com/p/vim/issues/detail?id=66 Should be fixed. Therefore closing. -- You received this message because this project is configured to send all issue notif

Re: Issue 71 in vim: gvim over ssh features undrawn characters

Updates: Status: Done Comment #8 on issue 71 by chrisbr...@googlemail.com: gvim over ssh features undrawn characters https://code.google.com/p/vim/issues/detail?id=71 Closing -- You received this message because this project is configured to send all issue notifications to this add

Re: Issue 73 in vim: Case mismatch in vim.vim syntax file (VimSynMtchCchar should be vimSynMtchCchar, lowercase leading v)

Updates: Status: Fixed Comment #1 on issue 73 by chrisbr...@googlemail.com: Case mismatch in vim.vim syntax file (VimSynMtchCchar should be vimSynMtchCchar, lowercase leading v) https://code.google.com/p/vim/issues/detail?id=73 ssems to be fixed, closing -- You received this messa

Re: Issue 75 in vim: Patch for /runtime/ftplugin/php.vim

Updates: Status: Invalid Comment #1 on issue 75 by chrisbr...@googlemail.com: Patch for /runtime/ftplugin/php.vim https://code.google.com/p/vim/issues/detail?id=75 This should be taken to the maintainer of the ftplugin file. He will send updated runtime files for inclusion with Vim

Re: Issue 51 in vim: CSS Syntax structure incompatible with extended syntaxes (eg less)

Comment #4 on issue 51 by chrisbr...@googlemail.com: CSS Syntax structure incompatible with extended syntaxes (eg less) https://code.google.com/p/vim/issues/detail?id=51 It seems there is no less.vim syntax or filetype plugin in Vims runtime file available. If you like to contribute, sends

Re: Issue 76 in vim: [patch] spec syntax: support %_unitdir and %global in spec.vim

Updates: Status: Invalid Comment #1 on issue 76 by chrisbr...@googlemail.com: [patch] spec syntax: support %_unitdir and %global in spec.vim https://code.google.com/p/vim/issues/detail?id=76 Please take the modifications of the runtime files to the maintainer of the file. He will de

Re: Issue 80 in vim: Feature request: variation for to return script base name

Updates: Status: WontFix Comment #5 on issue 80 by chrisbr...@googlemail.com: Feature request: variation for to return script base name https://code.google.com/p/vim/issues/detail?id=80 (No comment was entered for this change.) -- You received this message because this project is co

Re: Issue 81 in vim: Valgrind syntax src pattern matches too much

Updates: Status: Invalid Comment #1 on issue 81 by chrisbr...@googlemail.com: Valgrind syntax src pattern matches too much https://code.google.com/p/vim/issues/detail?id=81 Please take your changes to the maintainer of the file. If he decides to include your changes he will send an

Re: Issue 82 in vim: Vim does not correctly restore terminal title of xfce-terminal when exiting

Updates: Status: Invalid Comment #5 on issue 82 by chrisbr...@googlemail.com: Vim does not correctly restore terminal title of xfce-terminal when exiting https://code.google.com/p/vim/issues/detail?id=82 (No comment was entered for this change.) -- You received this message because t

Re: Issue 83 in vim: the changelog indicates that bram is abusing hg making the history a pain to deal with

Updates: Status: Invalid Comment #1 on issue 83 by chrisbr...@googlemail.com: the changelog indicates that bram is abusing hg making the history a pain to deal with https://code.google.com/p/vim/issues/detail?id=83 It might be an unusal way of using the tags feature of mercurial, but

Re: Issue 86 in vim: Minor bug in autoload/syntaxcomplete.vim line 459

Updates: Status: Invalid Comment #2 on issue 86 by chrisbr...@googlemail.com: Minor bug in autoload/syntaxcomplete.vim line 459 https://code.google.com/p/vim/issues/detail?id=86 This seems to be fixed, so closing. Please note, whenever you have problems with runtime files, first try t

Re: Issue 87 in vim: Patch for /runtime/autoload/syntaxcomplete.vim

Updates: Status: Duplicate Labels: -Type-Patch Comment #2 on issue 87 by chrisbr...@googlemail.com: Patch for /runtime/autoload/syntaxcomplete.vim https://code.google.com/p/vim/issues/detail?id=87 See issue 86, closing as duplicate -- You received this message because this pr

Re: Issue 91 in vim: File->Open does not update window content correctly - Appeared first in v7-3-638

Comment #1 on issue 91 by chrisbr...@googlemail.com: File->Open does not update window content correctly - Appeared first in v7-3-638 https://code.google.com/p/vim/issues/detail?id=91 Is this still reproducable? -- You received this message because this project is configured to send all is

Re: Issue 97 in vim: Fix --enable-pythoninterp on systems where python is a symlink to python3. [code]

Updates: Status: Fixed Comment #4 on issue 97 by chrisbr...@googlemail.com: Fix --enable-pythoninterp on systems where python is a symlink to python3. [code] https://code.google.com/p/vim/issues/detail?id=97 Should be fixed by 7.3.755. Closing -- You received this message because t

Re: Issue 98 in vim: python.vim indent plugin not pep8 compliant

Updates: Status: Fixed Comment #6 on issue 98 by chrisbr...@googlemail.com: python.vim indent plugin not pep8 compliant https://code.google.com/p/vim/issues/detail?id=98 Closing. Please note, that if you have problems with an included runtime file, first bring the issue to the maint

Re: Issue 101 in vim: Patch for /runtime/syntax/registry.vim

Updates: Status: Invalid Comment #1 on issue 101 by chrisbr...@googlemail.com: Patch for /runtime/syntax/registry.vim https://code.google.com/p/vim/issues/detail?id=101 You should take your changes to the maintainer of the file. If he includes your changes, he will send updated runt

Re: Issue 108 in vim: rst syntax file, completion

Updates: Status: Invalid Comment #6 on issue 108 by chrisbr...@googlemail.com: rst syntax file, completion https://code.google.com/p/vim/issues/detail?id=108 Closing as invalid for now. -- You received this message because this project is configured to send all issue notifications

Re: Issue 116 in vim: xxd -i output syntactically incorrect for empty files.

Updates: Status: Fixed Comment #2 on issue 116 by chrisbr...@googlemail.com: xxd -i output syntactically incorrect for empty files. https://code.google.com/p/vim/issues/detail?id=116 Should be fixed by Vim 7.3.835 -- You received this message because this project is configured to sen

Vim creating a 4193 file, results in wrong readings by inotify

Trying to debug having some tests running twice using guard gem and rspec, I realized that the problem was actually vim that creates a file called `4193`. I found a discussion in 2009*, but it has to do with windows. Basically the problem was that while rspec is running, the listen gem found th

Re: Issue 123 in vim: Windows gui: window position is changed when invoking :vert & :tab under certain conditions

Comment #1 on issue 123 by chrisbr...@googlemail.com: Windows gui: window position is changed when invoking :vert & :tab under certain conditions https://code.google.com/p/vim/issues/detail?id=123 This happens, because Vim will add a gui scrollbar, causing to resize. A workaround is to disa

Re: Issue 124 in vim: vim.vim syntax highlighting bug when option string starts with 'z'

Updates: Cc: drc...@campbellfamily.biz Comment #1 on issue 124 by chrisbr...@googlemail.com: vim.vim syntax highlighting bug when option string starts with 'z' https://code.google.com/p/vim/issues/detail?id=124 Still seems to be an issue. CC'ing Charles, as he is the maintainer of the

Re: Issue 125 in vim: does not show up when showcmd is set.

Updates: Status: Fixed Comment #1 on issue 125 by chrisbr...@googlemail.com: does not show up when showcmd is set. https://code.google.com/p/vim/issues/detail?id=125 Fixed by 7.4.116 -- You received this message because this project is configured to send all issue notifications to

Re: Issue 126 in vim: [PATCH] Fix broken syntax highlighting for sh after runtime files update

Updates: Status: Fixed Comment #2 on issue 126 by chrisbr...@googlemail.com: [PATCH] Fix broken syntax highlighting for sh after runtime files update https://code.google.com/p/vim/issues/detail?id=126 Seems to be fixed. In any case, if you have problems with runtime files, please fi

Re: Issue 127 in vim: TFS Plugin Broken by latest VIM

Updates: Status: Invalid Comment #7 on issue 127 by chrisbr...@googlemail.com: TFS Plugin Broken by latest VIM https://code.google.com/p/vim/issues/detail?id=127 (No comment was entered for this change.) -- You received this message because this project is configured to send all is

Re: Issue 131 in vim: Wrong phrasing in runtime/tutor/tutor

Updates: Status: Invalid Comment #2 on issue 131 by chrisbr...@googlemail.com: Wrong phrasing in runtime/tutor/tutor https://code.google.com/p/vim/issues/detail?id=131 I think it is correct. So closing. -- You received this message because this project is configured to send all iss

Re: Issue 132 in vim: Crontab syntax highlighting doesn't work properly when day/month names are not lowercased

Updates: Status: Invalid Comment #2 on issue 132 by chrisbr...@googlemail.com: Crontab syntax highlighting doesn't work properly when day/month names are not lowercased https://code.google.com/p/vim/issues/detail?id=132 Please report the problem to the maintainer of the file. He will

Re: Issue 139 in vim: VISUAL selection appearance

Updates: Status: Invalid Comment #1 on issue 139 by chrisbr...@googlemail.com: VISUAL selection appearance https://code.google.com/p/vim/issues/detail?id=139 I think what you are seeing is described briefly below :h VisualNOS This is actually a feature, so closing this issue. -- You

Re: Issue 139 in vim: VISUAL selection appearance

Comment #2 on issue 139 by chrisbr...@googlemail.com: VISUAL selection appearance https://code.google.com/p/vim/issues/detail?id=139 It is actually :h hl-VisualNOS -- You received this message because this project is configured to send all issue notifications to this address. You may adju

Re: Issue 141 in vim:

Updates: Status: Invalid Comment #3 on issue 141 by chrisbr...@googlemail.com: https://code.google.com/p/vim/issues/detail?id=141 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address.

Re: Issue 149 in vim: Bug in history management with multiple file buffers

Updates: Status: Invalid Comment #2 on issue 149 by chrisbr...@googlemail.com: Bug in history management with multiple file buffers https://code.google.com/p/vim/issues/detail?id=149 (No comment was entered for this change.) -- You received this message because this project is config

Re: Issue 153 in vim: adding changelog entries to spec files using \c doesn't work properly

Updates: Status: Invalid Comment #2 on issue 153 by chrisbr...@googlemail.com: adding changelog entries to spec files using \c doesn't work properly https://code.google.com/p/vim/issues/detail?id=153 Please bring up this issue with the maintainer of the runtime file. If he decides t

Re: Issue 162 in vim: Patch for syntax/groovy.vim: tighten pattern for the "import" keyword

Updates: Status: Fixed Comment #2 on issue 162 by chrisbr...@googlemail.com: Patch for syntax/groovy.vim: tighten pattern for the "import" keyword https://code.google.com/p/vim/issues/detail?id=162 I believe this is fixed in the current runtime files. If not, please bring up the iss

Re: Issue 163 in vim: load html.vim error

Updates: Status: Fixed Comment #1 on issue 163 by chrisbr...@googlemail.com: load html.vim error https://code.google.com/p/vim/issues/detail?id=163 I believe this is fixed with the latest runtime files. If not, please report the problem to the maintainer of the file. He will then send

Re: Issue 176 in vim: Starting line-wise visual mode with a count ('[count]V') usually selects a wrong number of lines

Updates: Status: Fixed Comment #5 on issue 176 by chrisbr...@googlemail.com: Starting line-wise visual mode with a count ('[count]V') usually selects a wrong number of lines https://code.google.com/p/vim/issues/detail?id=176 (No comment was entered for this change.) -- You received

Re: Issue 177 in vim: can not wipe buffer on bufhidden

Updates: Status: Invalid Comment #4 on issue 177 by chrisbr...@googlemail.com: can not wipe buffer on bufhidden https://code.google.com/p/vim/issues/detail?id=177 (No comment was entered for this change.) -- You received this message because this project is configured to send all i

Re: Issue 75 in vim: Patch for /runtime/ftplugin/php.vim

Updates: Labels: -Type-Patch Runtime Comment #2 on issue 75 by chrisbr...@googlemail.com: Patch for /runtime/ftplugin/php.vim https://code.google.com/p/vim/issues/detail?id=75 (No comment was entered for this change.) -- You received this message because this project is configured to

Re: Issue 51 in vim: CSS Syntax structure incompatible with extended syntaxes (eg less)

Updates: Labels: -Type-Defect -Priority-Medium Runtime Comment #5 on issue 51 by chrisbr...@googlemail.com: CSS Syntax structure incompatible with extended syntaxes (eg less) https://code.google.com/p/vim/issues/detail?id=51 (No comment was entered for this change.) -- You received t

Re: Issue 76 in vim: [patch] spec syntax: support %_unitdir and %global in spec.vim

Updates: Labels: -Type-Defect Runtime Comment #2 on issue 76 by chrisbr...@googlemail.com: [patch] spec syntax: support %_unitdir and %global in spec.vim https://code.google.com/p/vim/issues/detail?id=76 (No comment was entered for this change.) -- You received this message because t

Re: Issue 81 in vim: Valgrind syntax src pattern matches too much

Updates: Labels: Runtime Comment #2 on issue 81 by chrisbr...@googlemail.com: Valgrind syntax src pattern matches too much https://code.google.com/p/vim/issues/detail?id=81 (No comment was entered for this change.) -- You received this message because this project is configured to se

Re: Issue 101 in vim: Patch for /runtime/syntax/registry.vim

Updates: Labels: Runtime Comment #2 on issue 101 by chrisbr...@googlemail.com: Patch for /runtime/syntax/registry.vim https://code.google.com/p/vim/issues/detail?id=101 (No comment was entered for this change.) -- You received this message because this project is configured to send a

Re: Issue 108 in vim: rst syntax file, completion

Updates: Labels: Runtime Comment #7 on issue 108 by chrisbr...@googlemail.com: rst syntax file, completion https://code.google.com/p/vim/issues/detail?id=108 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue

Re: Issue 124 in vim: vim.vim syntax highlighting bug when option string starts with 'z'

Updates: Labels: Runtime Comment #2 on issue 124 by chrisbr...@googlemail.com: vim.vim syntax highlighting bug when option string starts with 'z' https://code.google.com/p/vim/issues/detail?id=124 (No comment was entered for this change.) -- You received this message because this pro

Re: Issue 153 in vim: adding changelog entries to spec files using \c doesn't work properly

Updates: Labels: Runtime Comment #3 on issue 153 by chrisbr...@googlemail.com: adding changelog entries to spec files using \c doesn't work properly https://code.google.com/p/vim/issues/detail?id=153 (No comment was entered for this change.) -- You received this message because this

Re: Issue 162 in vim: Patch for syntax/groovy.vim: tighten pattern for the "import" keyword

Updates: Labels: Runtime Comment #3 on issue 162 by chrisbr...@googlemail.com: Patch for syntax/groovy.vim: tighten pattern for the "import" keyword https://code.google.com/p/vim/issues/detail?id=162 (No comment was entered for this change.) -- You received this message because this

Re: Some abbreviations work only as imaps

Hi Bram! On Mo, 29 Sep 2014, Bram Moolenaar wrote: > > Christian wrote: > > > On Mi, 24 Sep 2014, Gevisz wrote: > > > Some abbreviations expand as desired and some do not. > > > > > > > Are there any circumstances different between a working abbreviation > > > > and a not working abbreviation?

Re: Some abbreviations work only as imaps

Christian wrote: > > > On Mi, 24 Sep 2014, Gevisz wrote: > > > > Some abbreviations expand as desired and some do not. > > > > > > > > > Are there any circumstances different between a working abbreviation > > > > > and a not working abbreviation? > > > > > > > > They may be very similar. For e

Issue 262 in vim: `set background` destroys additional highlighting

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 262 by hkj...@me.com: `set background` destroys additional highlighting https://code.google.com/p/vim/issues/detail?id=262 What steps will reproduce the problem? 1. Use a plug-in that does highlighting but not by filetype.