Issue 154 in vim: gVim 7.4a beta crashes from time to time

2013-07-22 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 154 by dief...@gmail.com: gVim 7.4a beta crashes from time to time http://code.google.com/p/vim/issues/detail?id=154 What steps will reproduce the problem? 1. use awesome wm 2. try to save a file in gvim gvim crashes

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

2013-07-22 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 153 by martin.g...@gmail.com: adding changelog entries to spec files using \c doesn't work properly http://code.google.com/p/vim/issues/detail?id=153 What steps will reproduce the problem? 1. open an (rpm) spec file 2. go

Issue 155 in vim: feature request: Option for keeping cursor position while scrolling by mouse

2013-07-22 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 155 by gade...@gmail.com: feature request: Option for keeping cursor position while scrolling by mouse http://code.google.com/p/vim/issues/detail?id=155 Right now, vim always shows cursor in viewable part of window

Issue 156 in vim: Vim exits with error ICE default IO error handler doing an exit(), pid = 6769, errno = 32

2013-07-22 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 156 by dominiqu...@gmail.com: Vim exits with error ICE default IO error handler doing an exit(), pid = 6769, errno = 32 http://code.google.com/p/vim/issues/detail?id=156 Summary: Vim exits with the error: ICE default IO

Re: Issue 156 in vim: Vim exits with error ICE default IO error handler doing an exit(), pid = 6769, errno = 32

2013-07-22 Fir de Conversatie vim
Comment #1 on issue 156 by dominiqu...@gmail.com: Vim exits with error ICE default IO error handler doing an exit(), pid = 6769, errno = 32 http://code.google.com/p/vim/issues/detail?id=156 The bug does not happen when starting vim with the -X option. So this works: $ for i in $(seq 1 60

Re: Issue 156 in vim: Vim exits with error ICE default IO error handler doing an exit(), pid = 6769, errno = 32

2013-07-23 Fir de Conversatie vim
Comment #3 on issue 156 by dominiqu...@gmail.com: Vim exits with error ICE default IO error handler doing an exit(), pid = 6769, errno = 32 http://code.google.com/p/vim/issues/detail?id=156 The error also happens when using options -u NONE --noplugin: $ for i in $(seq 1 60); do echo foo

Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-24 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 157 by octopusg...@gmail.com: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 What steps will reproduce the problem? 1. Make sure

Issue 158 in vim: :echo serverlist() leaks memory every time it is run.

2013-07-24 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 158 by dominiqu...@gmail.com: :echo serverlist() leaks memory every time it is run. http://code.google.com/p/vim/issues/detail?id=158 Description: the Ex command :echo serverlist() leaks memory every time it is run. What

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-25 Fir de Conversatie vim
Updates: Status: Started Comment #1 on issue 157 by drc...@campbellfamily.biz: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 Using the attached file (which I called simple6.vimrc

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-25 Fir de Conversatie vim
Comment #2 on issue 157 by octopusg...@gmail.com: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 First, thanks for your prompt reply. In /home/cnorton, I moved the .vim directory and .vimrc to other

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-25 Fir de Conversatie vim
Comment #3 on issue 157 by drc...@campbellfamily.biz: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 Since I didn't say previously, I used gvim 7.4a.35 to perform the test on a Scientific Linux

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-25 Fir de Conversatie vim
Comment #4 on issue 157 by octopusg...@gmail.com: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 I've got Decho installed, but am confused as to what script to write for netrw. This is reproduceable

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-25 Fir de Conversatie vim
Comment #5 on issue 157 by octopusg...@gmail.com: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 Chip: I got output and with DEcho on, the file is re-read back in as Unix. - Decho Tab /usr

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-25 Fir de Conversatie vim
Comment #6 on issue 157 by octopusg...@gmail.com: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 Once netwr.vim is replaced with the non-debug statements, the behavior returns. Re-read file comes

Re: Issue 158 in vim: :echo serverlist() leaks memory every time it is run.

2013-07-27 Fir de Conversatie vim
Updates: Status: WontFix Comment #1 on issue 158 by brammool...@gmail.com: :echo serverlist() leaks memory every time it is run. http://code.google.com/p/vim/issues/detail?id=158 XtCloseDisplay() is intentionally skipped. In os_unix.c: # if 0 /* Lesstif and Solaris crash

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-29 Fir de Conversatie vim
Comment #7 on issue 157 by octopusg...@gmail.com: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 This problem is resolved 7.4a beta. Thanks for your help. -- You received this message because

Re: Issue 157 in vim: gVim alters file type from Unix to DOS, with propert configuration directives in place.

2013-07-29 Fir de Conversatie vim
Updates: Status: Done Comment #8 on issue 157 by drc...@campbellfamily.biz: gVim alters file type from Unix to DOS, with propert configuration directives in place. http://code.google.com/p/vim/issues/detail?id=157 Problem resolved by upgrading vim (to 7.4a beta). -- You received

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

2013-08-11 Fir de Conversatie vim
Comment #6 on issue 28 by fvelasqu...@gmail.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 http://code.google.com/p/vim/issues/detail?id=28 I just installed vim 7.4 and the problem remains. The solution: In vmrc, the following lines exists by default

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

2013-08-11 Fir de Conversatie vim
Comment #7 on issue 28 by brammool...@gmail.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 http://code.google.com/p/vim/issues/detail?id=28 I do not see the problem out of the box. Starting gVim from the desktop results in a swap file c:\Users\bram\Desktop

Issue 159 in vim: Typo in Spanish tutorial tutor.es: vin

2013-08-12 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 159 by deleteso...@gmail.com: Typo in Spanish tutorial tutor.es: vin http://code.google.com/p/vim/issues/detail?id=159 http://code.google.com/p/vim/source/browse/runtime/tutor/tutor.es#123 says to run Vim you need to type

Issue 160 in vim: Russian tutor: wrong word замены instead of вставки

2013-08-18 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 160 by deleteso...@gmail.com: Russian tutor: wrong word замены instead of вставки http://code.google.com/p/vim/issues/detail?id=160 In http://code.google.com/p/vim/source/browse/runtime/tutor/tutor.ru , lesson 3.1, step

Issue 161 in vim: Can't see the output of :make while it's running in MS Windows

2013-08-21 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 161 by stefan.l...@gmail.com: Can't see the output of :make while it's running in MS Windows http://code.google.com/p/vim/issues/detail?id=161 What steps will reproduce the problem? 1. :set shellpipe 21\ |\ tee.exe 2

Re: Issue 161 in vim: Can't see the output of :make while it's running in MS Windows

2013-08-21 Fir de Conversatie vim
Comment #1 on issue 161 by stefan.l...@gmail.com: Can't see the output of :make while it's running in MS Windows http://code.google.com/p/vim/issues/detail?id=161 Additional info: ':!dir' does open a console window (in the foreground) -- You received this message because this project

Re: Issue 117 in vim: boolean to keep the sign column open at all times

2013-08-22 Fir de Conversatie vim
Comment #4 on issue 117 by b...@airbladesoftware.com: boolean to keep the sign column open at all times http://code.google.com/p/vim/issues/detail?id=117 I would like this too. Just about every plugin which uses signs has to include a hack to emulate sign-column-always-present behaviour

Re: Issue 161 in vim: Can't see the output of :make while it's running in MS Windows

2013-08-22 Fir de Conversatie vim
Comment #3 on issue 161 by stefan.l...@gmail.com: Can't see the output of :make while it's running in MS Windows http://code.google.com/p/vim/issues/detail?id=161 I just found the window (in ALT-TAB dialog and the task bar). It only has a very strange symbol. But in Vim 7.3 I could bring

Re: Issue 161 in vim: Can't see the output of :make while it's running in MS Windows

2013-08-22 Fir de Conversatie vim
Comment #2 on issue 161 by stefan.l...@gmail.com: Can't see the output of :make while it's running in MS Windows http://code.google.com/p/vim/issues/detail?id=161 Oh, I found the window. It is not reachable by ALT-TAB, but it is available in the task bar with a strange symbol. With Vim 7.3

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

2013-08-22 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 162 by chocol...@cpan.org: Patch for syntax/groovy.vim: tighten pattern for the import keyword http://code.google.com/p/vim/issues/detail?id=162 The attached patch fixes a nit in the groovy.vim syntax file that causes

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

2013-08-22 Fir de Conversatie vim
Comment #1 on issue 162 by chocol...@cpan.org: Patch for syntax/groovy.vim: tighten pattern for the import keyword http://code.google.com/p/vim/issues/detail?id=162 vim: 7.3 groovy.vim: 0.1.11 -- You received this message because this project is configured to send all issue notifications

Issue 163 in vim: load html.vim error

2013-08-23 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 163 by kos19...@gmail.com: load html.vim error http://code.google.com/p/vim/issues/detail?id=163 What steps will reproduce the problem? 1. vim *.html 2. 3. What is the expected output? What do you see instead? What version

Issue 164 in vim: Freeze on trying to match /\s\+\%#\@!$/ on a long line

2013-08-29 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 164 by harig...@gmail.com: Freeze on trying to match /\s\+\%#\@!$/ on a long line http://code.google.com/p/vim/issues/detail?id=164 Steps: 1. A very long line of HTML, f.e. repeat the following to make a single long

Re: Issue 164 in vim: Freeze on trying to match /\s\+\%#\@!$/ on a long line

2013-08-30 Fir de Conversatie vim
Comment #1 on issue 164 by brammool...@gmail.com: Freeze on trying to match /\s\+\%#\@!$/ on a long line http://code.google.com/p/vim/issues/detail?id=164 I cannot reproduce the problem. Perhaps you need to be more specific about the text? -- You received this message because this project

Re: Issue 164 in vim: Freeze on trying to match /\s\+\%#\@!$/ on a long line

2013-08-30 Fir de Conversatie vim
Comment #2 on issue 164 by harig...@gmail.com: Freeze on trying to match /\s\+\%#\@!$/ on a long line http://code.google.com/p/vim/issues/detail?id=164 Adding a file with the text. For me opening it and searching for the pattern /\s\+\%#\@!$/ makes Vim freeze for a long time if :set re=0

Issue 165 in vim: Width of line numbers in :hardcopy is hard coded

2013-09-03 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 165 by dale.oys...@gmail.com: Width of line numbers in :hardcopy is hard coded http://code.google.com/p/vim/issues/detail?id=165 The width of the line numbers (when enabled) in :hardcopy appears to be hard coded through

Issue 167 in vim: Support for Tcl 8.6

2013-09-06 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 167 by jan.nijt...@gmail.com: Support for Tcl 8.6 http://code.google.com/p/vim/issues/detail?id=167 What steps will reproduce the problem? See bug report here: [http://core.tcl.tk/tcl/info/8419b6d9ae] Starting with Tcl 8.6

Issue 168 in vim: A strange string would display, like ^[[1;3202;0c

2013-09-12 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 168 by wanghong...@gmail.com: A strange string would display, like ^[[1;3202;0c http://code.google.com/p/vim/issues/detail?id=168 What steps will reproduce the problem? I don't know how to reproduce this problem, it's

Re: Issue 169 in vim: Character won't map: – (U+2013, EN DASH)

2013-09-15 Fir de Conversatie vim
Comment #1 on issue 169 by zyx@gmail.com: Character won't map: – (U+2013, EN DASH) http://code.google.com/p/vim/issues/detail?id=169 This may be related to a wide set of problems with mapping[ to] strings containing 0x80 byte: EN DASH is 0xE2, *0x80*, 0x93; ¿ is 0xC2, 0xBF. -- You

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

2013-09-19 Fir de Conversatie vim
Comment #8 on issue 28 by ab...@yahoo.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 http://code.google.com/p/vim/issues/detail?id=28 Starting Vim from the start menu (which admittedly I've never done in 15+years using it until just now) sets the current

Issue 170 in vim: Support for Activestate perl 5.18.1.1800 on windows

2013-10-01 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 170 by z...@softvisio.net: Support for Activestate perl 5.18.1.1800 on windows http://code.google.com/p/vim/issues/detail?id=170 Please, add support for Activestate perl 5.18.1.1800 on windows. Building vim v7-4-045 from

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

2013-10-01 Fir de Conversatie vim
Comment #1 on issue 153 by matej.c...@gmail.com: adding changelog entries to spec files using \c doesn't work properly http://code.google.com/p/vim/issues/detail?id=153 I think the easiest way (and the way which actually works for me) is just use The Power of Python (and rpm-python

Re: Issue 167 in vim: Support for Tcl 8.6

2013-10-02 Fir de Conversatie vim
Updates: Status: Fixed Comment #1 on issue 167 by brammool...@gmail.com: Support for Tcl 8.6 http://code.google.com/p/vim/issues/detail?id=167 Included with patch 7.4.046 -- You received this message because this project is configured to send all issue notifications to this address

Issue 171 in vim: Patch for /runtime/syntax/d.vim

2013-10-04 Fir de Conversatie vim
Status: New Owner: Labels: Type-Patch New issue 171 by code.via...@gmail.com: Patch for /runtime/syntax/d.vim http://code.google.com/p/vim/issues/detail?id=171 fix highlighting string after variables what have 'import' or 'module' in name. Example: enum Problem { importVar

Re: Issue 171 in vim: Patch for /runtime/syntax/d.vim

2013-10-05 Fir de Conversatie vim
Comment #1 on issue 171 by jesse.k@gmail.com: Patch for /runtime/syntax/d.vim http://code.google.com/p/vim/issues/detail?id=171 This has been fixed in the development branch of d.vim https://github.com/JesseKPhillips/d.vim -- You received this message because this project is configured

Re: Issue 171 in vim: Patch for /runtime/syntax/d.vim

2013-10-06 Fir de Conversatie vim
Updates: Status: Fixed Comment #2 on issue 171 by brammool...@gmail.com: Patch for /runtime/syntax/d.vim http://code.google.com/p/vim/issues/detail?id=171 I'll include it in the distribution. Thanks Jesse. -- You received this message because this project is configured to send all

Issue 172 in vim: On GNOME, modal dialog file has changed does not receive focus when opened

2013-10-12 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 172 by lastor...@gmail.com: On GNOME, modal dialog file has changed does not receive focus when opened http://code.google.com/p/vim/issues/detail?id=172 To reproduce on Ubuntu GNOME 13.04 (trunk): 1. Open a file in GVIM

Re: Issue 172 in vim: On GNOME, modal dialog file has changed does not receive focus when opened

2013-10-13 Fir de Conversatie vim
Comment #1 on issue 172 by lastor...@gmail.com: On GNOME, modal dialog file has changed does not receive focus when opened http://code.google.com/p/vim/issues/detail?id=172 Not knowing GTK at all, my investigation efforts stopped at create_message_dialog and gui_mch_dialog in gui_gtk.c

Re: Issue 172 in vim: On GNOME, modal dialog file has changed does not receive focus when opened

2013-10-15 Fir de Conversatie vim
Comment #2 on issue 172 by john.b.l...@gmail.com: On GNOME, modal dialog file has changed does not receive focus when opened http://code.google.com/p/vim/issues/detail?id=172 FWIW, on Kubuntu 13.04, using the distro vim 7.3.547, (and also 7.4.52), with or without -u NONE, I don't see

Re: Issue 170 in vim: Support for Activestate perl 5.18.1.1800 on windows

2013-10-16 Fir de Conversatie vim
Comment #1 on issue 170 by gauchy...@gmail.com: Support for Activestate perl 5.18.1.1800 on windows http://code.google.com/p/vim/issues/detail?id=170 The modification of if_perl.xs to work around. 1. Perl_sv_free2: Perl 5.18.1 introduces a new file lib\CORE\inline.h, which defines inline

Re: Issue 170 in vim: Support for Activestate perl 5.18.1.1800 on windows

2013-10-16 Fir de Conversatie vim
Comment #2 on issue 170 by gauchy...@gmail.com: Support for Activestate perl 5.18.1.1800 on windows http://code.google.com/p/vim/issues/detail?id=170 The modification of if_perl.xs to work around. 1. Perl_sv_free2: Perl 5.18.1 introduces a new file lib\CORE\inline.h, which defines inline

Re: Issue 170 in vim: Support for Activestate perl 5.18.1.1800 on windows

2013-10-16 Fir de Conversatie vim
Comment #3 on issue 170 by alaska...@gmail.com: Support for Activestate perl 5.18.1.1800 on windows http://code.google.com/p/vim/issues/detail?id=170 Unfortunately this patch does not work with Activestate perl 5.18.1 x64. Part of error log: if_perl.c:1916:15: note: in expansion of macro

Issue 173 in vim: Error R6034 when starting VIM loading Python dynamically under Windows 7

2013-10-16 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 173 by ma...@von-oppen.com: Error R6034 when starting VIM loading Python dynamically under Windows 7 http://code.google.com/p/vim/issues/detail?id=173 Under Windows 7 (64 Bit) my VIM builds produce an runtime error R6034

Re: Issue 170 in vim: Support for Activestate perl 5.18.1.1800 on windows

2013-10-16 Fir de Conversatie vim
Comment #4 on issue 170 by gauchy...@gmail.com: Support for Activestate perl 5.18.1.1800 on windows http://code.google.com/p/vim/issues/detail?id=170 Sorry, I forgot to mention that I was building vim-7.3.1314. :P -- You received this message because this project is configured to send

Re: Issue 170 in vim: Support for Activestate perl 5.18.1.1800 on windows

2013-10-16 Fir de Conversatie vim
Comment #5 on issue 170 by gauchy...@gmail.com: Support for Activestate perl 5.18.1.1800 on windows http://code.google.com/p/vim/issues/detail?id=170 Sorry, I've forgot to mention that I was building vim-7.3.1314. :P vim-7.4 has a different vim.h, which doesn't include perl.h anymore

Re: Issue 170 in vim: Support for Activestate perl 5.18.1.1800 on windows

2013-10-17 Fir de Conversatie vim
Comment #6 on issue 170 by z...@softvisio.net: Support for Activestate perl 5.18.1.1800 on windows http://code.google.com/p/vim/issues/detail?id=170 Thanks, now works without any errors. Built and tested vim 7.4 with mingw-x64 and ActivePerl 5.18.1. -- You received this message because

Re: Issue 173 in vim: Error R6034 when starting VIM loading Python dynamically under Windows 7

2013-10-17 Fir de Conversatie vim
Comment #1 on issue 173 by ma...@von-oppen.com: Error R6034 when starting VIM loading Python dynamically under Windows 7 http://code.google.com/p/vim/issues/detail?id=173 here for reference the original error message box... Attachments: VIM_Error.png 22.4 KB -- You received

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

2013-10-20 Fir de Conversatie vim
Comment #2 on issue 98 by lurayl: python.vim indent plugin not pep8 compliant http://code.google.com/p/vim/issues/detail?id=98 As of http://code.google.com/p/vim/source/diff?spec=svn173c9c860e42e2af31d598aa6924b99d7e73bd1br=173c9c860e42e2af31d598aa6924b99d7e73bd1bformat=sidepath=/runtime

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

2013-10-20 Fir de Conversatie vim
Comment #3 on issue 98 by zyx@gmail.com: python.vim indent plugin not pep8 compliant http://code.google.com/p/vim/issues/detail?id=98 As of http://code.google.com/p/vim/source/diff?spec=svn173c9c860e42e2af31d598aa6924b99d7e73bd1br=173c9c860e42e2af31d598aa6924b99d7e73bd1bformat=sidepath

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

2013-10-20 Fir de Conversatie vim
Comment #4 on issue 98 by vega.ja...@gmail.com: python.vim indent plugin not pep8 compliant http://code.google.com/p/vim/issues/detail?id=98 It does not force. It provides defaults. You have a bunch of ways to reset them: modelines, :au Filetype python, `set exrc` (better to use some plugin

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

2013-10-20 Fir de Conversatie vim
Comment #5 on issue 98 by zyx@gmail.com: python.vim indent plugin not pep8 compliant http://code.google.com/p/vim/issues/detail?id=98 I think that correlates more to the fact that most languages don't have a self or community imposed coding style. Python, make, cobol, Go, and Java

Issue 174 in vim: Detect *.comp files as Mason

2013-10-24 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 174 by hinrik@gmail.com: Detect *.comp files as Mason http://code.google.com/p/vim/issues/detail?id=174 The attached patch makes vim assign the 'mason' filetype to files with the .comp extension, which denote Mason

Issue 175 in vim: A menu item of gvim 7.4 is not translated

2013-10-29 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 175 by baishu...@gmail.com: A menu item of gvim 7.4 is not translated http://code.google.com/p/vim/issues/detail?id=175 What steps will reproduce the problem? 1.Open gvim 7.4 on Simplified Chinese edition of Windows XP. 2

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

2013-11-02 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 176 by alexey.m...@gmail.com: Starting line-wise visual mode with a count ('[count]V') usually selects a wrong number of lines http://code.google.com/p/vim/issues/detail?id=176 What steps will reproduce the problem? --- 1

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

2013-11-02 Fir de Conversatie vim
Comment #1 on issue 176 by 676c7...@gmail.com: Starting line-wise visual mode with a count ('[count]V') usually selects a wrong number of lines http://code.google.com/p/vim/issues/detail?id=176 Not a bug, it has always been like this. This happens when you select something and then cancel

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

2013-11-02 Fir de Conversatie vim
Comment #2 on issue 176 by 676c7...@gmail.com: Starting line-wise visual mode with a count ('[count]V') usually selects a wrong number of lines http://code.google.com/p/vim/issues/detail?id=176 It's the other way around, sorry about that. The multiplication behaviour occurs after some

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

2013-11-02 Fir de Conversatie vim
Comment #3 on issue 176 by alexey.m...@gmail.com: Starting line-wise visual mode with a count ('[count]V') usually selects a wrong number of lines http://code.google.com/p/vim/issues/detail?id=176 I see, this is indeed documented at :h v, but not at :h V. In fact, it contradicts

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

2013-11-02 Fir de Conversatie vim
Comment #4 on issue 176 by alexey.m...@gmail.com: Starting line-wise visual mode with a count ('[count]V') usually selects a wrong number of lines http://code.google.com/p/vim/issues/detail?id=176 By the way, this is a new behaviour: [count] can be used with V since 7.4. -- You received

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

2013-11-05 Fir de Conversatie vim
Comment #9 on issue 28 by m...@mattperry.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 http://code.google.com/p/vim/issues/detail?id=28 This problem is occurring because the 'Start In' field is blank in the shortcuts in the Start menu. When a value isn't

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

2013-11-05 Fir de Conversatie vim
Comment #10 on issue 28 by mplistar...@gmail.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 http://code.google.com/p/vim/issues/detail?id=28 This problem is occurring because the 'Start In' field is blank in the shortcuts in the Start menu. When a value

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

2013-11-05 Fir de Conversatie vim
Comment #11 on issue 28 by fritzoph...@gmail.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 http://code.google.com/p/vim/issues/detail?id=28 The trigger may be that the current directory is not writable...but when the current directory is not writable, Vim

Issue 177 in vim: can not wipe buffer on bufhidden

2013-11-05 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 177 by liaoming...@gmail.com: can not wipe buffer on bufhidden http://code.google.com/p/vim/issues/detail?id=177 What steps will reproduce the problem? 1) set hidden. 2) set nocompatible set hidden syntax on autocmd

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

2013-11-06 Fir de Conversatie vim
Comment #1 on issue 177 by fritzoph...@gmail.com: can not wipe buffer on bufhidden http://code.google.com/p/vim/issues/detail?id=177 As noted by ZyX, my reply on the mailing list wasn't posted here. Sorry for the double post on vim_dev, I'm posing using the issue tracker now

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

2013-11-06 Fir de Conversatie vim
Comment #2 on issue 177 by zyx@gmail.com: can not wipe buffer on bufhidden http://code.google.com/p/vim/issues/detail?id=177 I do not see you posting an exact sequence of commands you used to test this behavior. When testing your code with # vim onbufhiddenwipe.vim paste

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

2013-11-06 Fir de Conversatie vim
Comment #3 on issue 177 by liaoming...@gmail.com: can not wipe buffer on bufhidden http://code.google.com/p/vim/issues/detail?id=177 thank you for your reply. here is how I reproduce it. 1) launch vim. 2) edit a file 3) tabnew opens another tab. 4) try to close the new tab by :x. when I

Re: Issue 140 in vim: netrw plugin NetrwTreeListing

2013-11-06 Fir de Conversatie vim
Comment #6 on issue 140 by jke...@connectwise.com: netrw plugin NetrwTreeListing http://code.google.com/p/vim/issues/detail?id=140 I can confirm this issue. Vim 7.4.26 MS-Windows 32-bit (console and gvim) It is not related to mapleader. Necessary and sufficient steps to reproduce: vim -u

Re: Issue 140 in vim: netrw plugin NetrwTreeListing

2013-11-09 Fir de Conversatie vim
Updates: Status: Fixed Comment #7 on issue 140 by drc...@campbellfamily.biz: netrw plugin NetrwTreeListing http://code.google.com/p/vim/issues/detail?id=140 Hello! Please try v150i of netrw from my website: http://.drchip.org/astronaut/vim/index.html#NETRW. Regards, C

Re: Issue 59 in vim: netrw breaks scripts.vim

2013-11-09 Fir de Conversatie vim
Updates: Status: Fixed Comment #6 on issue 59 by drc...@campbellfamily.biz: netrw breaks scripts.vim http://code.google.com/p/vim/issues/detail?id=59 I believe this problem was fixed awhile back. -- You received this message because this project is configured to send all issue

Re: Issue 67 in vim: scp resets several options

2013-11-09 Fir de Conversatie vim
Updates: Status: Fixed Comment #2 on issue 67 by drc...@campbellfamily.biz: scp resets several options http://code.google.com/p/vim/issues/detail?id=67 I believe that this problem was due to an out-of-date netrw and has been fixed awhile back. -- You received this message because

Re: Issue 140 in vim: netrw plugin NetrwTreeListing

2013-11-11 Fir de Conversatie vim
Comment #8 on issue 140 by jke...@connectwise.com: netrw plugin NetrwTreeListing http://code.google.com/p/vim/issues/detail?id=140 Thanks. The website says: Updated Nov 09, 2013 (v150i) But but netrw.vba says: let g:loaded_netrwPlugin = v150h I downloaded from this URL: http

Issue 178 in vim: make `:vim` an alias for `:edit`

2013-11-11 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 178 by ale...@ifit.com: make `:vim` an alias for `:edit` http://code.google.com/p/vim/issues/detail?id=178 On numerous occasions, I've found myself trying to open files--typically when I'm in a hurry--using ':vim' instead

Re: Issue 178 in vim: make `:vim` an alias for `:edit`

2013-11-11 Fir de Conversatie vim
Comment #1 on issue 178 by ale...@ifit.com: make `:vim` an alias for `:edit` http://code.google.com/p/vim/issues/detail?id=178 This is NOT a bug report, this is simply a feature request, most of which are usually done through the project's `issues` framework thing. Also, I don't mind

Re: Issue 178 in vim: make `:vim` an alias for `:edit`

2013-11-11 Fir de Conversatie vim
Comment #2 on issue 178 by zyx@gmail.com: make `:vim` an alias for `:edit` http://code.google.com/p/vim/issues/detail?id=178 :vim is :vimgrep. This will not be changed due to backwards compatibility. You can use cnoreabbrev/cnoremap to make an alias yourself like in e.g. http

Re: Issue 178 in vim: make `:vim` an alias for `:edit`

2013-11-11 Fir de Conversatie vim
Updates: Status: WontFix Labels: -Type-Defect Type-Enhancement Comment #3 on issue 178 by brammool...@gmail.com: make `:vim` an alias for `:edit` http://code.google.com/p/vim/issues/detail?id=178 As mentioned :vim already has a meaning, and we don't want to change

Re: Issue 178 in vim: make `:vim` an alias for `:edit`

2013-11-11 Fir de Conversatie vim
Comment #4 on issue 178 by ale...@ifit.com: make `:vim` an alias for `:edit` http://code.google.com/p/vim/issues/detail?id=178 Point taken; thank you for yalls' time and sorry for any inconvenience caused. -- You received this message because this project is configured to send all issue

Re: Issue 140 in vim: netrw plugin NetrwTreeListing

2013-11-12 Fir de Conversatie vim
Comment #9 on issue 140 by drc...@campbellfamily.biz: netrw plugin NetrwTreeListing http://code.google.com/p/vim/issues/detail?id=140 Try again -- I loaded the file onto my website again; I've downloaded it via ftp and via my browser, and was getting v150j. Make sure your browser's

Re: Issue 140 in vim: netrw plugin NetrwTreeListing

2013-11-12 Fir de Conversatie vim
Comment #10 on issue 140 by jke...@connectwise.com: netrw plugin NetrwTreeListing http://code.google.com/p/vim/issues/detail?id=140 Thanks, it seems to be fixed! -- You received this message because this project is configured to send all issue notifications to this address. You may

Re: Issue 140 in vim: netrw plugin NetrwTreeListing

2013-11-12 Fir de Conversatie vim
Comment #11 on issue 140 by jke...@connectwise.com: netrw plugin NetrwTreeListing http://code.google.com/p/vim/issues/detail?id=140 Will this be merged to Vim trunk any time soon? -- You received this message because this project is configured to send all issue notifications

Re: Issue 140 in vim: netrw plugin NetrwTreeListing

2013-11-12 Fir de Conversatie vim
Comment #12 on issue 140 by drc...@campbellfamily.biz: netrw plugin NetrwTreeListing http://code.google.com/p/vim/issues/detail?id=140 I let it stay on my website for some time, collecting bug reports, fixing problems, and occasionally extending it. After its properly aged, I send

Re: Issue 151 in vim: file management (copy/move) is broken on windows (netrw)

2013-11-12 Fir de Conversatie vim
Updates: Status: Accepted Owner: drc...@campbellfamily.biz Comment #1 on issue 151 by drc...@campbellfamily.biz: file management (copy/move) is broken on windows (netrw) http://code.google.com/p/vim/issues/detail?id=151 You need to find commands on your system that will copy

Issue 179 in vim: set backupdir does not support double trailing slashes to include path info in filename

2013-11-13 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 179 by ma...@chromium.org: set backupdir does not support double trailing slashes to include path info in filename http://code.google.com/p/vim/issues/detail?id=179 What steps will reproduce the problem? 1. add to your

Re: Issue 179 in vim: set backupdir does not support double trailing slashes to include path info in filename

2013-11-13 Fir de Conversatie vim
Comment #1 on issue 179 by gary@gmail.com: set backupdir does not support double trailing slashes to include path info in filename http://code.google.com/p/vim/issues/detail?id=179 This is already in todo.txt, under *known-bugs*, and a patch was submitted 21 Oct. 2010. It has

Re: Issue 169 in vim: Character won't map: – (U+2013, EN DASH)

2013-11-13 Fir de Conversatie vim
Comment #2 on issue 169 by janchris...@gmail.com: Character won't map: – (U+2013, EN DASH) http://code.google.com/p/vim/issues/detail?id=169 I have the same issue and would also be interested in a solution or workaround, once one is found. -- You received this message because

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

2013-11-13 Fir de Conversatie vim
Comment #12 on issue 28 by fritzoph...@gmail.com: out of the box, gVim 7.3.46 for Win32 cannot write swap files on Windows 7 http://code.google.com/p/vim/issues/detail?id=28 This patch will use environment variables for the temp directories for both 'directory' and 'backupdir' options

Issue 180 in vim: Map commands doesn't highlight in `autocmd`

2013-11-19 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 180 by hail2u: Map commands doesn't highlight in `autocmd` http://code.google.com/p/vim/issues/detail?id=180 What steps will reproduce the problem? 1. write `autocmd` that calls `nnoremap` (or other map commands) What

Issue 181 in vim: iskeyword is wrong for javascript and ruby

2013-11-22 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 181 by randomen...@gmail.com: iskeyword is wrong for javascript and ruby http://code.google.com/p/vim/issues/detail?id=181 What steps will reproduce the problem? 1. Open a javascript or ruby file with something like

Re: Issue 181 in vim: iskeyword is wrong for javascript and ruby

2013-11-22 Fir de Conversatie vim
Comment #1 on issue 181 by fritzoph...@gmail.com: iskeyword is wrong for javascript and ruby http://code.google.com/p/vim/issues/detail?id=181 I cannot reproduce this on my installation. I create a new buffer with text one.two, put my cursor on two and type viw. Only two is selected. I

Issue 182 in vim: Why include search recursively

2013-11-23 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 182 by hjp709...@gmail.com: Why include search recursively http://code.google.com/p/vim/issues/detail?id=182 When use keyword completions vim search the 'path' recursively, which takes tons of time. Why recursively

Re: Issue 182 in vim: Why include search recursively

2013-11-23 Fir de Conversatie vim
Comment #1 on issue 182 by hjp709...@gmail.com: Why include search recursively http://code.google.com/p/vim/issues/detail?id=182 recursively search is useful for c and cpp while not useful for languages like python and perl. -- You received this message because this project is configured

Issue 183 in vim: [[2;2R printed in messages area on BufEnter shell command

2013-11-26 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 183 by pbris...@gmail.com: [[2;2R printed in messages area on BufEnter shell command http://code.google.com/p/vim/issues/detail?id=183 What steps will reproduce the problem? 1. Add the following to example.vimrc

Re: Issue 183 in vim: [[2;2R printed in messages area on BufEnter shell command

2013-11-28 Fir de Conversatie vim
Comment #1 on issue 183 by brammool...@gmail.com: [[2;2R printed in messages area on BufEnter shell command http://code.google.com/p/vim/issues/detail?id=183 You should put set nocp in the script, otherwise the terminal version isn't requested. Despite that, I can't reproduce the problem

Re: Issue 183 in vim: [[2;2R printed in messages area on BufEnter shell command

2013-11-28 Fir de Conversatie vim
Comment #2 on issue 183 by pbris...@gmail.com: [[2;2R printed in messages area on BufEnter shell command http://code.google.com/p/vim/issues/detail?id=183 My bad on nocp, figured that out further down the ML thread but copied the wrong example into this issue. FWIW, this reproduces most

Issue 184 in vim: Setting (paste) input mode after setting ruler causes ruler to hide

2013-12-01 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 184 by kyle.hau...@gmail.com: Setting (paste) input mode after setting ruler causes ruler to hide http://code.google.com/p/vim/issues/detail?id=184 **What steps will reproduce the problem? 1. With file open in vim, issue

  1   2   3   4   5   6   7   8   9   10   >