[PATCH] Handle case of unmapped K when exiting termdebug
From: Rene Kita
If K is not mapped to anything the dictionary is empty and the if clause
is false. K is then still mapped to :Evaluate. This will result in an
error E492 when using K.
---
Steps to reproduce:
- :unmap K
- :packadd termdebug
- :Termdebug
- quit
- :map K
runtime/pack/dist/opt/termdebug/plugin/termdebug.vim | 2 ++
1 file changed, 2 insertions(+)
diff --git a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
index bf38dc93a..301ac7a5c 100644
--- a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
+++ b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
@@ -729,6 +729,8 @@ func s:DeleteCommands()
if exists('s:k_map_saved') && !empty(s:k_map_saved)
call mapset('n', 0, s:k_map_saved)
unlet s:k_map_saved
+ else
+nunmap K
endif
if has('menu')
--
2.25.1
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20201206165839.167428-1-vim%40rkta.de.
[PATCH] Handle case of unmapped K when exiting termdebug
From: Rene Kita
If K is not mapped to anything the dictionary is empty and the if clause
is false. K is then still mapped to :Evaluate. This will result in an
error E492 when using K.
---
Steps to reproduce:
- :unmap K
- :packadd termdebug
- :Termdebug
- quit
- :map K
runtime/pack/dist/opt/termdebug/plugin/termdebug.vim | 2 ++
1 file changed, 2 insertions(+)
diff --git a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
index bf38dc93a..301ac7a5c 100644
--- a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
+++ b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
@@ -729,6 +729,8 @@ func s:DeleteCommands()
if exists('s:k_map_saved') && !empty(s:k_map_saved)
call mapset('n', 0, s:k_map_saved)
unlet s:k_map_saved
+ else
+nunmap K
endif
if has('menu')
--
2.25.1
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20201206160253.160711-1-vim%40rkta.de.
[PATCH] Handle case of unmapped K when exiting termdebug
-- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20201206165744.167161-1-vim%40rkta.de.
[PATCH] Handle case of unmapped K when exiting termdebug
From: Rene Kita
If K is not mapped to anything the dictionary is empty and the if clause
is false. K is then still mapped to :Evaluate. This will result in an
error E492 when using K.
---
Steps to reproduce:
- :unmap K
- :packadd termdebug
- :Termdebug
- quit
- :map K
runtime/pack/dist/opt/termdebug/plugin/termdebug.vim | 2 ++
1 file changed, 2 insertions(+)
diff --git a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
index bf38dc93a..301ac7a5c 100644
--- a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
+++ b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim
@@ -729,6 +729,8 @@ func s:DeleteCommands()
if exists('s:k_map_saved') && !empty(s:k_map_saved)
call mapset('n', 0, s:k_map_saved)
unlet s:k_map_saved
+ else
+nunmap K
endif
if has('menu')
--
2.25.1
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20201207093559.194406-1-vim%40rkta.de.
Re: Issue 390 in vim: [[2;2R printed in buffer area on vim startup
Comment #5 on issue 390 by dbarn...@google.com: [[2;2R printed in buffer area on vim startup https://code.google.com/p/vim/issues/detail?id=390 I got it to repro again and changing the length checks like #3 above doesn't seem to have helped. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 393 in vim: Gvim Font-glitches for combining characters (pango-view has no problems) in Ubuntu Mono font
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 393 by ludwi...@gmx.de: Gvim Font-glitches for combining characters (pango-view has no problems) in Ubuntu Mono font https://code.google.com/p/vim/issues/detail?id=393 What steps will reproduce the problem? 1. Consider a text file with one line: á i.e. between the minus signs: U+0061 U+0301 (g8: 61 + cc 81) 2. gvim -u NONE -U NONE -N -c 'set gfn=Ubuntu\ Mono\ 30' What is the expected output? What do you see instead? The expected output: the same es the output of pango-view -t á- --font=Ubuntu mono 65 There is a screen-shot attached with the output of Gvim and the expected output (of pango-view). This problem does not occur with e.g. se gfn=Bitstream\ Vera\ Sans\ Mono\ Bold\ 12 What version of the product are you using? On what operating system? Gvim 7.4.826 on Fedora 22 Please provide any additional information below. VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 14 2015 13:47:52) Included patches: 1-207, 209-826 Huge version with GTK2 GUI. Features included (+) or not (-): +acl -ebcdic +localmap+printer +title +arabic +emacs_tags -lua +profile +toolbar +autocmd +eval+menu+python/dyn +user_commands +balloon_eval+ex_extra+mksession -python3 +vertsplit +browse +extra_search+modify_fname+quickfix +virtualedit ++builtin_terms +farsi +mouse +reltime +visual +byte_offset +file_in_path+mouseshape +rightleft +visualextra +cindent +find_in_path+mouse_dec +ruby/dyn+viminfo +clientserver+float +mouse_gpm +scrollbind +vreplace +clipboard +folding -mouse_jsbterm +signs +wildignore +cmdline_compl -footer +mouse_netterm +smartindent +wildmenu +cmdline_hist+fork() +mouse_sgr -sniff +windows +cmdline_info+gettext -mouse_sysmouse +startuptime +writebackup +comments-hangul_input+mouse_urxvt +statusline +X11 +conceal +iconv +mouse_xterm -sun_workshop -xfontset +cryptv +insert_expand +multi_byte +syntax +xim +cscope +jumplist+multi_lang +tag_binary +xsmp_interact +cursorbind +keymap -mzscheme+tag_old_static +xterm_clipboard +cursorshape +langmap +netbeans_intg -tag_any_white -xterm_save +dialog_con_gui +libcall +path_extra -tcl +xpm +diff+linebreak +perl+terminfo +digraphs+lispindent +persistent_undo +termresponse +dnd +listcmds+postscript +textobjects Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -O2 -g -pipe -Wall -Werror=format-security -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -L. -Wl,-z,relro -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,--enable-new-dtags -Wl,-z,relro -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lSM -lICE -lXpm -lXt -lX11 -lSM -lICE -lm -lnsl -lselinux -lncurses -lacl -lattr -lgpm -ldl -Wl,--enable-new-dtags -fstack-protector -L/usr/local/lib -L/usr/lib64/perl5/CORE -lperl -lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc Attachments: GvimUbuntuFontProblem.png 27.0 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 393 in vim: Gvim Font-glitches for combining characters (pango-view has no problems) in Ubuntu Mono font
Comment #1 on issue 393 by ludwi...@gmx.de: Gvim Font-glitches for combining characters (pango-view has no problems) in Ubuntu Mono font https://code.google.com/p/vim/issues/detail?id=393 The dotted circle looks like the glyph for U+25CC. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 389 in vim: 'linebreak' breaks c% if the last visual selection was block
Updates: Status: Fixed Comment #1 on issue 389 by brammool...@gmail.com: 'linebreak' breaks c% if the last visual selection was block https://code.google.com/p/vim/issues/detail?id=389 Fix included in patch 7.4.818 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 392 in vim: Support new Python 3.5 keywords and builtins (syntax)
Comment #1 on issue 392 by chrisbr...@googlemail.com: Support new Python 3.5 keywords and builtins (syntax) https://code.google.com/p/vim/issues/detail?id=392 Please contact the maintainer of the syntax file. He will then send updated files for inclusion with Vim to Bram. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 392 in vim: Support new Python 3.5 keywords and builtins (syntax)
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 392 by yseliva...@gmail.com: Support new Python 3.5 keywords and builtins (syntax) https://code.google.com/p/vim/issues/detail?id=392 The attached patch adds highlighting for new coroutines: async def foo(): await b() and new builtins -- StopAsyncIteration and RecursionError Attachments: python35.patch 1.1 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 385 in vim: expansion of environment variables fails in Vim backtick expression
Updates: Status: Fixed Comment #1 on issue 385 by chrisbr...@googlemail.com: expansion of environment variables fails in Vim backtick expression https://code.google.com/p/vim/issues/detail?id=385 Documentation has been updated and behaviour clarified as of https://code.google.com/p/vim/source/detail?r=349e6c01f35d00f6035aec42fc43d02173eb00cc -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 385 in vim: expansion of environment variables fails in Vim backtick expression
Comment #2 on issue 385 by zyx@gmail.com: expansion of environment variables fails in Vim backtick expression https://code.google.com/p/vim/issues/detail?id=385 I would say that status should change to WontFix, not Fixed in this case. Documenting this does not make it look like a valid behaviour. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 391 in vim: Kindle
Updates: Status: Invalid Comment #1 on issue 391 by chrisbr...@googlemail.com: Kindle https://code.google.com/p/vim/issues/detail?id=391 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 391 in vim: Kindle
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 391 by ruby.bar...@gmail.com: Kindle https://code.google.com/p/vim/issues/detail?id=391 What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 390 in vim: [[2;2R printed in buffer area on vim startup
Comment #3 on issue 390 by brammool...@gmail.com: [[2;2R printed in buffer area on vim startup https://code.google.com/p/vim/issues/detail?id=390 You could try this: in src/term.c, change the length checks to one less: if ((*T_CRV != NUL || *T_U7 != NUL) ((tp[0] == ESC len = 2 tp[1] == '[') || (tp[0] == CSI len = 1)) (VIM_ISDIGIT(*argp) || *argp == '' || *argp == '?')) Assuming that you only received ESC [ it would currently not check for a match, it needs another character. Disadvantage: if you actually type ESC [ the same would happen... -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 390 in vim: [[2;2R printed in buffer area on vim startup
Comment #2 on issue 390 by dbarn...@google.com: [[2;2R printed in buffer area on vim startup https://code.google.com/p/vim/issues/detail?id=390 Oh, and it's a transient issue not consistently reproducible. I think it has something to do with my machine being slow and/or using vim over SSH, but it repros in xterm, gnome-term, etc. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 390 in vim: [[2;2R printed in buffer area on vim startup
Comment #1 on issue 390 by dbarn...@google.com: [[2;2R printed in buffer area on vim startup https://code.google.com/p/vim/issues/detail?id=390 Adding `set t_u7=` to the top of my vimrc as a workaround fixes it. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 390 in vim: [[2;2R printed in buffer area on vim startup
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 390 by dbarn...@google.com: [[2;2R printed in buffer area on vim startup https://code.google.com/p/vim/issues/detail?id=390 What steps will reproduce the problem? 1. SSH into server running slowly (?) 2. Start vim with many plugins enabled (?) 3. Observe [[2;2R at the top of the buffer area (see screenshot). What is the expected output? What do you see instead? I expect that part of the buffer area to be blank. Instead I see [[2;2R junk that goes away if I refresh the terminal with ctrl-L. What version of the product are you using? On what operating system? vim 7.4.622 on Ubuntu Linux 14.04 This is very similar to #183 which was closed as not reproducible and was speculated to be fixed by patch 7.4.207. Attachments: vim_garbage.png 37.5 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 183 in vim: [[2;2R printed in messages area on BufEnter shell command
Comment #6 on issue 183 by dbarn...@google.com: [[2;2R printed in messages area on BufEnter shell command https://code.google.com/p/vim/issues/detail?id=183 Still seeing similar issue as of 7.4.622, except in my case it appears at the top of the buffer area instead of the messages area. I filed #390 with details. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 389 in vim: 'linebreak' breaks c% if the last visual selection was block
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 389 by chris.morganiser: 'linebreak' breaks c% if the last visual
selection was block
https://code.google.com/p/vim/issues/detail?id=389
Précis: when the 'linebreak' option is set and visual block mode was the
last visual mode entered, c% removes the text for deletion in a blockwise
manner rather than the character-wise manner that should be the case.
Detailed steps to reproduce (no special configuration is required;
vim -u NONE exhibits the buggy behaviour):
Enter this demonstrative text:
abcd{ef
ghijklm
no}pqrs
Go to the opening {.
Enter and exit visual block mode (C-VC-V).
At some point no later than this, :set linebreak.
c%Esc
The expected contents of the buffer is this:
abcdpqrs
The actual contents of the buffer is this:
abef
ghlm
nors
I haven’t experimented much more, but d% is not buggy.
I am using Vim 7.4.778 on Arch Linux, 64-bit (huge with GTK2 GUI).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Issue 382 in vim: Patch for /runtime/syntax/python.vim
Comment #5 on issue 382 by e.kawasc...@gmail.com: Patch for /runtime/syntax/python.vim https://code.google.com/p/vim/issues/detail?id=382 Thank you. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 388 in vim: javascript syntax highlight regex error
Comment #3 on issue 388 by chrisbr...@googlemail.com: javascript syntax highlight regex error https://code.google.com/p/vim/issues/detail?id=388 Please report to the maintainer of the syntax plugin. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 239 in vim: Python file with large numbers stalls the editor
Updates: Status: Fixed Comment #3 on issue 239 by chrisbr...@googlemail.com: Python file with large numbers stalls the editor https://code.google.com/p/vim/issues/detail?id=239 should be fixed as of https://code.google.com/p/vim/source/detail?r=b2673982c625503d99459f31b6c0a347e703321a -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 386 in vim: Fix highlighting comments in VB syntax file
Updates: Status: Fixed Comment #1 on issue 386 by chrisbr...@googlemail.com: Fix highlighting comments in VB syntax file https://code.google.com/p/vim/issues/detail?id=386 Fixed as of https://code.google.com/p/vim/source/detail?r=b2673982c625503d99459f31b6c0a347e703321a -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'
Updates: Status: Fixed Comment #4 on issue 381 by chrisbr...@googlemail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 fixed -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 388 in vim: javascript syntax highlight regex error
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 388 by moritz.d...@gmail.com: javascript syntax highlight regex error https://code.google.com/p/vim/issues/detail?id=388 What steps will reproduce the problem? 1.Create a JS file 2.Type abc.match(/\\/); 3.Turn on syntax highlighting What is the expected output? What do you see instead? The entire block /\\/ should be highlighted as a regular expression What happens is that the second backslash escapes the second slash even though it should not What version of the product are you using? On what operating system? Ubuntu Vim 7.4m patches 1-488 Please provide any additional information below. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 388 in vim: javascript syntax highlight regex error
Comment #1 on issue 388 by moritz.d...@gmail.com: javascript syntax highlight regex error https://code.google.com/p/vim/issues/detail?id=388 Correction of typo: Ubuntu 15.04 vim, patches 1-488 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 388 in vim: javascript syntax highlight regex error
Comment #2 on issue 388 by moritz.d...@gmail.com: javascript syntax highlight regex error https://code.google.com/p/vim/issues/detail?id=388 Correction of typo: Ubuntu 15.04, Vim 7.4, patches 1-488 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 382 in vim: Patch for /runtime/syntax/python.vim
Updates: Status: Fixed Comment #4 on issue 382 by chrisbr...@googlemail.com: Patch for /runtime/syntax/python.vim https://code.google.com/p/vim/issues/detail?id=382 I think this is fixed as of https://code.google.com/p/vim/source/detail?r=b2673982c625503d99459f31b6c0a347e703321a -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 379 in vim: vimscript's own syntax highlighter ignores line continuations
Updates: Cc: drc...@campbellfamily.biz Comment #1 on issue 379 by chrisbr...@googlemail.com: vimscript's own syntax highlighter ignores line continuations https://code.google.com/p/vim/issues/detail?id=379 CC'ing Charles as vim syntax file maintainer. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 79 in vim: Use 'path' setting for filename completion (compl-filename)
Comment #5 on issue 79 by brammool...@gmail.com: Use 'path' setting for filename completion (compl-filename) https://code.google.com/p/vim/issues/detail?id=79 This feature is most useful to expand header files, without knowing where they are: #include fooCTRL-XCTRL-F In that situation we don't want the absolute file name. Would require adding an extra flag to expand_wildcards, such as EW_RELATIVE, and code to handle that. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 224 in vim: Patch for /src/Make_mvc.mak
Comment #4 on issue 224 by ktakata6...@gmail.com: Patch for /src/Make_mvc.mak https://code.google.com/p/vim/issues/detail?id=224 Updated for 7.4.794. Attachments: Make_mvc.mak.patch 5.7 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 319 in vim: New option to not beep with 'showmatch'
Updates: Status: Fixed Comment #12 on issue 319 by chrisbr...@googlemail.com: New option to not beep with 'showmatch' https://code.google.com/p/vim/issues/detail?id=319 fixed with 7.4.793 and the new 'belloff' option -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 387 in vim: Clicking gvim close window button is interrupted by File Changed dialog.
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 387 by fri...@google.com: Clicking gvim close window button is interrupted by File Changed dialog. https://code.google.com/p/vim/issues/detail?id=387 What steps will reproduce the problem? 1. Open a file in gvim. 2. Unfocus the gvim window. 3. Change file outside of gvim. 4. Click close window button on window. What is the expected output? What do you see instead? Expect: window closes immediately. Actual: closing is interrupted by dialog W11 Warning: File ... has changed since editing started [OK] [Load File]. This dialog is meaningless if the buffer is clean, since the next action will be to quit. What version of the product are you using? On what operating system? OS: Linux with XFCE4 (Xubuntu). $ gvim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 9 2015 16:31:56) Included patches: 1-622 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by dbarn...@google.com Huge version with GTK2 GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +syntax +arabic +file_in_path+mouse_sgr +tag_binary +autocmd +find_in_path-mouse_sysmouse +tag_old_static +balloon_eval+float +mouse_urxvt -tag_any_white +browse +folding +mouse_xterm +tcl ++builtin_terms -footer +multi_byte +terminfo +byte_offset +fork() +multi_lang +termresponse +cindent +gettext -mzscheme+textobjects +clientserver-hangul_input+netbeans_intg +title +clipboard +iconv +path_extra +toolbar +cmdline_compl +insert_expand +perl+user_commands +cmdline_hist+jumplist+persistent_undo +vertsplit +cmdline_info+keymap +postscript +virtualedit +comments+langmap +printer +visual +conceal +libcall +profile +visualextra +cryptv +linebreak +python +viminfo +cscope +lispindent -python3 +vreplace +cursorbind +listcmds+quickfix+wildignore +cursorshape +localmap+reltime +wildmenu +dialog_con_gui +lua +rightleft +windows +diff+menu+ruby+writebackup +digraphs+mksession +scrollbind +X11 +dnd +modify_fname+signs -xfontset -ebcdic +mouse +smartindent +xim +emacs_tags +mouseshape -sniff +xsmp_interact +eval+mouse_dec +startuptime +xterm_clipboard +ex_extra+mouse_gpm +statusline -xterm_save +extra_search-mouse_jsbterm -sun_workshop+xpm Please provide any additional information below. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 386 in vim: Fix highlighting comments in VB syntax file
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 386 by vzeit...@gmail.com: Fix highlighting comments in VB syntax file https://code.google.com/p/vim/issues/detail?id=386 Currently comments introduced with rem are not highlighted as comments in VB[Script] files. To fix this, rem keyword needs to be removed as this conflicts with its use as start region marker for vbComment syntax region. Patch: -- 8 -- --- syntax/vb.vim 2015-07-19 01:08:13.0 +0200 +++ syntax/vb.vim2015-07-19 01:02:42.322321200 +0200 @@ -223,7 +223,7 @@ syn keyword vbStatement GoTo Gosub Implements Kill LSet Let Lib LineInput syn keyword vbStatement Load Lock Loop Mid MkDir Name Next On OnError Open syn keyword vbStatement Option Preserve Private Property Public Put RSet -syn keyword vbStatement RaiseEvent Randomize ReDim Redim Rem Reset Resume +syn keyword vbStatement RaiseEvent Randomize ReDim Redim Reset Resume syn keyword vbStatement Return RmDir SavePicture SaveSetting Seek SendKeys syn keyword vbStatement Sendkeys Set SetAttr Static Step Stop Sub Time syn keyword vbStatement Type Unload Unlock Until Wend While Width With -- 8 -- -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 384 in vim: VIM crashes on :py import threading
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 384 by beo...@gmail.com: VIM crashes on :py import threading https://code.google.com/p/vim/issues/detail?id=384 What steps will reproduce the problem? 1. Compile vim on Windows with python2.7 support 2. Run :py import threading in gvim What is the expected output? What do you see instead? Expected: no output Actual: VIM crashes, and `Fatal Python error: PyThreadState_Get: no current thread` is printed to console What version of the product are you using? On what operating system? 7.4.781 on Windows (compiled with mingw64 with mingw64 Python 2.7 on MSYS2) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 385 in vim: expansion of environment variables fails in Vim backtick expression
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 385 by pavol.ju...@gmail.com: expansion of environment variables fails in Vim backtick expression https://code.google.com/p/vim/issues/detail?id=385 What steps will reproduce the problem? vim -u NONE -i NONE -N :e `=$HOME . '/.vimrc'` What is the expected output? What do you see instead? Vim should open the .vimrc file in my HOME directory. Instead I see the following error: E15: Invalid expression: /Users/pjuhas . '/.vimrc' It seems that $HOME gets expanded _before_ parsing the VimL expression in backticks. This would be OK for shell-expanded backtick expressions, but not for Vim expressions of the `=expr` kind. What version of the product are you using? On what operating system? Vim 7.4.712 on OS X Yosemite 10.10.4. This is likely independent of the OS. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 382 in vim: Patch for /runtime/syntax/python.vim
Comment #3 on issue 382 by zvezdanp...@gmail.com: Patch for /runtime/syntax/python.vim https://code.google.com/p/vim/issues/detail?id=382 I just sent a patch to vim-dev with some additional updates. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 382 in vim: Patch for /runtime/syntax/python.vim
Status: New Owner: Labels: Type-Patch New issue 382 by e.kawasc...@gmail.com: Patch for /runtime/syntax/python.vim https://code.google.com/p/vim/issues/detail?id=382 modify exceptions Attachments: python.vim.patch 2.8 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 382 in vim: Patch for /runtime/syntax/python.vim
Comment #2 on issue 382 by e.kawasc...@gmail.com: Patch for /runtime/syntax/python.vim https://code.google.com/p/vim/issues/detail?id=382 fix source url Attachments: python.vim.patch 2.8 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 382 in vim: Patch for /runtime/syntax/python.vim
Comment #1 on issue 382 by e.kawasc...@gmail.com: Patch for /runtime/syntax/python.vim https://code.google.com/p/vim/issues/detail?id=382 fix source url -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 383 in vim: Add support for marshalling JSON
Comment #1 on issue 383 by zyx@gmail.com: Add support for marshalling
JSON
https://code.google.com/p/vim/issues/detail?id=383
`null` is usually parsed in as zero, not as an empty string (depends on the
plugin author obviously; I use zero, same does NeoVim for msgpack Nil).
tojson/fromjson names break usual naming: it is mostly either get/set{smth}
(getline/setline, etc) or {smth}{action} (foldopen, foldclose, …), so
jsondump/parse are better. To dump/parse null, true, false unambigiously I
propose a second argument: a dictionary looking like
:let specialsdict = {'null': {}, 'true': {}, 'false': {}}
:echo jsonparse(true, specialsdict) is# specialdicts.true
1
:echo jsondump([specialsdict.null, {}, 0, ''], specialsdict)
[null, {}, 0, ]
Note that 99% of JSON you may parse with eval like in VAM (it has a regex
that verifies that parsing is safe). But you don’t get normal errors in
this case. It also does not work with surrogate pairs.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Issue 383 in vim: Add support for marshalling JSON
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 383 by daviebd...@gmail.com: Add support for marshalling JSON
https://code.google.com/p/vim/issues/detail?id=383
Could vim have a built-in tojson({value}) and fromjson({json}) helpers to
serialize and deserialize JSON?
JSON is used in lots of vim plugins like
https://github.com/Valloric/YouCompleteMe,
https://github.com/google/vim-maktaba,
https://github.com/MarcWeber/vim-addon-manager, and eventually Vundle
(https://github.com/VundleVim/Vundle.vim/pull/560). These can either use
slow hacks or depend on python support, but it would be best if vim just
had native, performant support for JSON marshalling built in.
Expected behavior
:echo tojson({'a': [1, 'foo'], 'b': 2.1}) ==# '{a: [1, foo], b:
2.1}'
1
:echo fromjson([1.0, {}, []]) ==# [1.0, {}, []]
1
:echo tojson(fromjson('[null, true, false]')) ==# '[null, true, false]'
1
Note in the last example there needs to be a way to represent null, true,
and false unambiguously even though vim doesn't have these primitives.
Also, fromjson() could use an option to translate into standard vim
equivalents like '', 1, and 0.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'
Comment #3 on issue 381 by h.east@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 This problem occurs in vim 7.4.757 to 7.4.765. (fixed by 7.4.766) If you use urxvt and using transparency, check below thread and try local patch rbg_fix4.patch https://groups.google.com/d/topic/vim_dev/LLGjKaEzNUY/discussion If we want to urgently resolved, try out the following method. 1. 't_RB' cleard in your .vimrc. set t_RB= 2. 'bg' set to 'dark' or 'light' in your .vimrc set bg=dark 3. Disable transparency. Please see https://bbs.archlinux.org/viewtopic.php?pid=1541962#p1541962 Thank you -- Best regards, Hirohito Higashi -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'
Comment #2 on issue 381 by odabr...@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 I cannot reproduce this. File test.vim contains set nocompatible Testing with vim -u test.vim -U NONE --noplugin test.vim shows the contents of test.vim without g, as shown above. Tested with vim 7.4.000 and vim 7.4.769. Could you try to reproduce it with the file and command line above? If it does not reproduce the problem, then something in your ~/.vimrc or in a plugin is likely the reason for the problem. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 381 by expro...@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 What steps will reproduce the problem? 1. find a text file with non-empty first line, like foo.txt 2. add 'set nocompatible' to ~/.vimrc 3. run 'vim foo.txt' What is the expected output? What do you see instead? - The first char of first line of foo.txt will always be 'g' regardless what the file contains. What version of the product are you using? On what operating system? - VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 29 2015 10:20:34) - Linux 4.0.7-2-ARCH #1 SMP PREEMPT Tue Jun 30 08:04:42 UTC 2015 i686 GNU/Linux -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'
Comment #1 on issue 381 by expro...@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 correction: - The first char of first line of **the buffer** will always be 'g' regardless what the file contains. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 380 in vim: v:hlsearch doesn't work when in a function.
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 380 by kassiobo...@gmail.com: v:hlsearch doesn't work when in a function. https://code.google.com/p/vim/issues/detail?id=380 What steps will reproduce the problem? 1. create a function: function! X() let @/ = 'test' let v:hlsearch = 1 endfunction 2. given that `set hlsearch` is set, call the function, What is the expected output? What do you see instead? Was expected that the words `test` get highlight on all buffers, but doesn't work. PS.: If I execute those `let` commands, without a function, it works. What version of the product are you using? On what operating system? VIM - Vi IMproved 7.4 (2013 Aug 10, compiled May 11 2015 14:26:15) MacOS X (unix) version Included patches: 1-728 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 380 in vim: v:hlsearch doesn't work when in a function.
Comment #2 on issue 380 by odabr...@gmail.com: v:hlsearch doesn't work when in a function. https://code.google.com/p/vim/issues/detail?id=380 Correction: please replace @ in the last comment with @/. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 380 in vim: v:hlsearch doesn't work when in a function.
Comment #1 on issue 380 by odabr...@gmail.com: v:hlsearch doesn't work when in a function. https://code.google.com/p/vim/issues/detail?id=380 This is done on purpose: the highlighting state is saved and restored for a user function, see ':help :nohlsearch' and ':help function-search-undo'. I believe this is done so that the user's last search state is not accidentally changed by functions (or autocommands), which may do searches just to do their work. This is not documented in ':help v:hlsearch', but the help for :nohlsearch is linked from there. Also, the documentation for @ mentions this: ':help /', or a bit above ':help @/'. Not sure if this is a bug. Maybe the v:hlsearch documentation should more clearly point this out? As in the help for v:searchforward, which points this out and links to 'function-search-undo'. Also, are you asking for a way to force setting the search state from a function? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 380 in vim: v:hlsearch doesn't work when in a function.
Comment #4 on issue 380 by odabr...@gmail.com: v:hlsearch doesn't work when in a function. https://code.google.com/p/vim/issues/detail?id=380 This patch adds two lines to the docs of v:hlsearch. Attachments: hg-vim-7.4-clarify-v-hlsearch-docs.patch 511 bytes -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 380 in vim: v:hlsearch doesn't work when in a function.
Updates: Status: Fixed Comment #6 on issue 380 by brammool...@gmail.com: v:hlsearch doesn't work when in a function. https://code.google.com/p/vim/issues/detail?id=380 I'll include the patch, thanks. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 379 in vim: vimscript's own syntax highlighter ignores line continuations
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 379 by anntzer@gmail.com: vimscript's own syntax highlighter ignores line continuations https://code.google.com/p/vim/issues/detail?id=379 What steps will reproduce the problem? Highlight the following source with vim's own highlighter: syn keyword foo bar print syn keyword foo \ bar print What is the expected output? What do you see instead? Neither print should highlighted as they are in a keyword list for syn keyword. The second print gets highlighted, I guess because vim.vim doesn't handle the line continuation properly. What version of the product are you using? On what operating system? vim 7.4.738 on Arch Linux. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 91 in vim: File-Open does not update window content correctly - Appeared first in v7-3-638
Comment #10 on issue 91 by gugelge...@gmail.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 Same Problem here: Ubuntu 14.04 in a VMware Workstation environment. If I start vim with athena (vim.athena -g) I cannot reproduce it. Two other Ubuntu 14.04 installations under Virtualbox do not show the problem. The current workaround for me is to start gvim with --sync option. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 203 in vim: Nothing in register * problem (vim+tmux or vim+screen )
Comment #22 on issue 203 by keith.hu...@gmail.com: Nothing in register * problem (vim+tmux or vim+screen ) https://code.google.com/p/vim/issues/detail?id=203 Problem persists on 7.4-738 + tmux 2.0. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 203 in vim: Nothing in register * problem (vim+tmux or vim+screen )
Comment #23 on issue 203 by keith.hu...@gmail.com: Nothing in register * problem (vim+tmux or vim+screen ) https://code.google.com/p/vim/issues/detail?id=203 It looks like the issue may be to the use of the unnamed clipboard. Usually I have set clipboard=unnamed so that copied text goes to PRIMARY system buffer. This works great initially before detaching disconnecting from tmux/SSH session. When I commented out that line in my .vimrc file, copying and pasting no longer worked from vim to the OS, but within vim it worked across multiple sessions without issues. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 377 in vim: gvim keeps creating ~/.gnome2/Vim, ignores XDG
Updates: Status: Invalid Comment #2 on issue 377 by chrisbr...@googlemail.com: gvim keeps creating ~/.gnome2/Vim, ignores XDG https://code.google.com/p/vim/issues/detail?id=377 Closing, since this is not a Vim bug, but rather a gnome bug. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 378 in vim: Hit Enter twice after make
Comment #1 on issue 378 by carlosjo...@gmail.com: Hit Enter twice after make
https://code.google.com/p/vim/issues/detail?id=378
To reproduce, try:
1) Write this simple 3-line python script:
#
#
1/0
2) let l:errorformat=' File %f\, line %l%.%#' | let
l:makeprg='python %'
3a) Move the cursor to the first line and :make
= Fine
3b) Move the cursor to the third line and :make
= Double Hit Enter prompt
Notice the error is just empty because of the way errorformat was defined.
The problem is not that the message is too long! (although, strangely
enough, setting cmdheight to 2 supresses the extra prompt...)
There is another situation when the Hit Enter prompt is shown twice
and yet it's also unrelated to long messages: when there are no valid
entries in the qf list. In the example above, replace `1/0` for
`print('hello')` and repeat the steps. Now both 3a and 3b end up
showing a double prompt, despite there is nowhere to jump to and no
valid error message to show.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Issue 377 in vim: gvim keeps creating ~/.gnome2/Vim, ignores XDG
Comment #1 on issue 377 by john.b.l...@gmail.com: gvim keeps creating ~/.gnome2/Vim, ignores XDG https://code.google.com/p/vim/issues/detail?id=377 IIUC this behaviour is not in vim code, so cannot be fixed in vim. It's in the gnome 2 libraries, which were superseded by Gnome 3 about 5 years ago. Gnome 3 uses GTK+ 3, which was a rewrite, so revising gvim to use gnome 3 would not be easy, and there seems to be nothing gained (and some features to lose) by doing it. Opinions may vary. Regards, John Little -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 378 in vim: Hit Enter twice after make
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 378 by carlosjo...@gmail.com: Hit Enter twice after make https://code.google.com/p/vim/issues/detail?id=378 (I'm deleting this from the forum and reporting it here) The fact that the hit enter prompt is shown twice sometimes after :make when an error is found by quickfix was asked a number of times in the user list and in stackoverflow, but AFAIK it was just workarounded by making make silent or cmdheight larger. Now I've found a specific situation when the problem seem to be clearly reproducible: when the cursor was already on the line containing the first qf valid error immediately before running the make command (that is, the curaor was already on the line where make will automatically jump). In this case the qf error message is echoed as usual, except that the editor hasn't been redrawn yet and the hit enter prompt is presented again. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 376 in vim: langmap applies to Command-line mappings
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 376 by larry.ve...@gmail.com: langmap applies to Command-line mappings https://code.google.com/p/vim/issues/detail?id=376 I'm observing this issue on OS X with Vim 7.4, patches 1–729, +langmap (among others). It seems similar to a previously-reported problem with Insert mode (http://thread.gmane.org/gmane.editors.vim.devel/48562) that was fixed by patch 7.4.552. In the same vein, the problem should be reproducible by starting Vim like so… vim -u NONE -c 'cnoremap } X| set langmap=+} langnoremap' …entering Command-line mode, and trying to type a +. This should produce a +, but it inserts X instead. The attached patch fixes the issue, as far as I can tell. Attachments: cmdline-mapping-langmap.patch 1.3 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 365 in vim: Adding a setting doesn't check for existing trailing comma
Updates: Status: Fixed Comment #5 on issue 365 by brammool...@gmail.com: Adding a setting doesn't check for existing trailing comma https://code.google.com/p/vim/issues/detail?id=365 Fixed with patch 7.4.741 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 365 in vim: Adding a setting doesn't check for existing trailing comma
Comment #6 on issue 365 by tankorsm...@gmail.com: Adding a setting doesn't check for existing trailing comma https://code.google.com/p/vim/issues/detail?id=365 Thanks guys. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 374 in vim: Completion for :cd from 'cdpath'
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 374 by dhah...@gmail.com: Completion for :cd from 'cdpath' https://code.google.com/p/vim/issues/detail?id=374 The `cd` command should consider the `cdpath` setting for completion of relative paths. Currently the completion appears to use only the current working directory when completing relative paths. This means that `:cd fooTab` should complete `foobar` if there exists `/path/in/cdpath/foobar` (and `/path/in/cdpath` is in `cdpath`). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 375 in vim: Listchars should have a 'space' option
Updates: Status: Invalid Comment #1 on issue 375 by chrisbr...@googlemail.com: Listchars should have a 'space' option https://code.google.com/p/vim/issues/detail?id=375 fixed by 7.4.710 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 370 in vim: % character not rendered properly all of a sudden
Comment #6 on issue 370 by john.b.l...@gmail.com: % character not rendered properly all of a sudden https://code.google.com/p/vim/issues/detail?id=370 Sounds like a corrupt font cache. HTH. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 373 in vim: jumplist: go to prev/next entry from another file
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 373 by dhah...@gmail.com: jumplist: go to prev/next entry from another file https://code.google.com/p/vim/issues/detail?id=373 I often use the jumplist, and then want to advance in it backwards/forwards per file. It would be helpful if e.g. `gC-o` and `gC-i` would go to the prev/next entry in the jumplist that is from another file than the current one. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 370 in vim: % character not rendered properly all of a sudden
Updates: Status: Done Comment #5 on issue 370 by chrisbr...@googlemail.com: % character not rendered properly all of a sudden https://code.google.com/p/vim/issues/detail?id=370 (closing) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 372 in vim: Error while opening a file containin ':ex'
Updates: Status: Done Comment #1 on issue 372 by chrisbr...@googlemail.com: Error while opening a file containin ':ex' https://code.google.com/p/vim/issues/detail?id=372 You are seeing the effect of the modeline (:h modeline) If you don't need modelines, you can disable them. (closing) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 372 in vim: Error while opening a file containin ':ex'
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 372 by malviyan...@gmail.com: Error while opening a file containin ':ex' https://code.google.com/p/vim/issues/detail?id=372 What steps will reproduce the problem? 1. Create a new file say temp.txt with contetnt like This is a normal line #Now this is tricky ex: Here must be problem It should work fine. Problem in line 4 ex: Problem Again 2. File has ':ex' in its second and Fourth lines 3.Save and close the file 4. Open file create above with vim-. What is the expected output? What do you see instead? Expected Output: File should be opened for editing. Actual Output: temp.txt 4L, 124C Error detected while processing modelines: line2: E518: Unknown option: Here Press ENTER or type command to continue What version of the product are you using? On what operating system? VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Apr 28 2012 20:34:45) LSB Version: :base-4.0-amd64:base-4.0-ia32:base-4.0-noarch:core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch Distributor ID: OracleServer Description:Oracle Linux Server release 6.5 Release:6.5 Please provide any additional information below. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 371 in vim: Windows: If file name on command line starts with space, preceding backslash is lost
Comment #1 on issue 371 by ch...@chrullrich.net: Windows: If file name on command line starts with space, preceding backslash is lost https://code.google.com/p/vim/issues/detail?id=371 Same behavior with 7.4.729 (tuxproject.de). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 371 in vim: Windows: If file name on command line starts with space, preceding backslash is lost
Comment #2 on issue 371 by chrisbr...@googlemail.com: Windows: If file name on command line starts with space, preceding backslash is lost https://code.google.com/p/vim/issues/detail?id=371 works with gvim test/\ testfile.txt -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 371 in vim: Windows: If file name on command line starts with space, preceding backslash is lost
Comment #4 on issue 371 by ch...@chrullrich.net: Windows: If file name on command line starts with space, preceding backslash is lost https://code.google.com/p/vim/issues/detail?id=371 It's not a workaround, decent or not. I don't think it was meant as one, either. The main impact of this bug is that it breaks opening files from the shell context menu, because you can't influence the path that Explorer passes to Vim in that case. With tab completion in a command prompt window, it is nearly as bad, but at least there I could fix up the path to make Vim understand it before I run it. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 371 in vim: Windows: If file name on command line starts with space, preceding backslash is lost
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 371 by ch...@chrullrich.net: Windows: If file name on command line starts with space, preceding backslash is lost https://code.google.com/p/vim/issues/detail?id=371 What steps will reproduce the problem? 1. Create a file named testfile.txt (leading space). 2. Start Vim and pass the file name on the command line, including at least one parent directory (i.e. gvim.exe test\ testfile.txt) What is the expected output? What do you see instead? I would expect Vim to open the file. Instead, it swallows the backslash before the space and opens test testfile.txt as a new file. What version of the product are you using? On what operating system? 7.4.711 (Cream vanilla), Windows 8.1 Please provide any additional information below. The same effect occurs when using the shell context menu. The bug is in Vim, see below: C:\testpy -3 -c import sys; print(str(sys.argv)) test\ testfile.txt ['-c', 'test\\ testfile.txt'] Python does not lose the backslash. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 370 in vim: % character not rendered properly all of a sudden
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 370 by omar.oth...@booking.com: % character not rendered properly all of a sudden https://code.google.com/p/vim/issues/detail?id=370 What steps will reproduce the problem? Not sure, it happened all of a sudden, but it is currently persistent so feel free to ask me to run any commands on my computer and will report it back here. What is the expected output? What do you see instead? The % character looks correct if I put the cursor on it, but when I move away I see the strange shape you see in the screenshot on the first line (after the backslash). Note that this is not a hiccup, I close vim and opened the file again. What version of the product are you using? On what operating system? $ vim -v version 7.3.315 $ lsb_release -a LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: CentOS Description:CentOS release 6.5 (Final) Release:6.5 Codename: Final Attachments: Screenshot from 2015-06-10 14:49:37.png 143 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 370 in vim: % character not rendered properly all of a sudden
Comment #1 on issue 370 by fritzoph...@gmail.com: % character not rendered properly all of a sudden https://code.google.com/p/vim/issues/detail?id=370 What does :verbose set conceallevel? concealcursor? listchars? say? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 361 in vim: vimgrep over arglist doesn't work on Windows
Updates: Status: Done Comment #5 on issue 361 by chrisbr...@googlemail.com: vimgrep over arglist doesn't work on Windows https://code.google.com/p/vim/issues/detail?id=361 Fixed by 7.4.730 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 370 in vim: % character not rendered properly all of a sudden
Comment #3 on issue 370 by chrisbr...@googlemail.com: % character not rendered properly all of a sudden https://code.google.com/p/vim/issues/detail?id=370 Is this gvim or terminal vim? Does it make a difference? If you turn syntax off, does it look correctly? Could this be a font issue (e.g. try in your gvim a different guifont setting or change your terminals font please). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 370 in vim: % character not rendered properly all of a sudden
Comment #4 on issue 370 by omar.oth...@booking.com: % character not rendered properly all of a sudden https://code.google.com/p/vim/issues/detail?id=370 It is terminal vim, I don't have gvim installed. Changing the syntax highlighting had no effect, but changing the terminal font did! Now I'm confused, since I've been using the same terminal settings forever and it started to happen only today, so I thought a vim update did something wrong. Sorry for disturbance, and thanks for the clever suggestion, Chris! -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 370 in vim: % character not rendered properly all of a sudden
Comment #2 on issue 370 by omar.oth...@booking.com: % character not rendered properly all of a sudden https://code.google.com/p/vim/issues/detail?id=370 :verbose set conceallevel? concealcursor? listchars? conceallevel=0 concealcursor= listchars=eol:$ -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #11 on issue 369 by brammool...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 Looks like the patch does not encrypt any data blocks, because it checks the flag before doing encryption, and the flag is never set at that point. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #12 on issue 369 by chrisbr...@googlemail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 Well, as i said, i don't know much about the encryption, but I checked, that it created an encrypted file when running Vim with that patch. At least I got a binary file that I was able to decrypt on Linux as well (where the maxmem option does not trigger). Also the flag is set in ml_encrypt_data() aroud line 4881 (looking from the diff). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Updates: Status: Fixed Comment #13 on issue 369 by brammool...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 Fixed by patch 7.4.730. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Updates: Labels: patch Comment #10 on issue 369 by chrisbr...@googlemail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 I think, this patch fixes it. Attachments: issue_369.diff 1.8 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 368 in vim: Temporary file creation non-comprehensively fails when all the variations are taken for the name
Updates: Status: Invalid Comment #1 on issue 368 by chrisbr...@googlemail.com: Temporary file creation non-comprehensively fails when all the variations are taken for the name https://code.google.com/p/vim/issues/detail?id=368 Note, you can always get help for each error number. And there you'll see: ,[ :h E138 ]- | When you get error E138: Can't write viminfo file | check that no old temp files were left behind (e.g. | ~/.viminf*) and that you can write in the directory of | the .viminfo file. ` Therefore closing. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #9 on issue 369 by chrisbr...@googlemail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 I think, I found the problem. We are setting the key and the cryptmethod. When writing the buffer, Vim gets each line and when getting a line, it will need to find the block, it belongs to, which means, it will eventually call mf_get() to read a new block from the disc. But, in mf_get() we are calling ml_decrypt_data() to decrypt the block, if a key is set. Unfortunately, the block isn't actually encrypted yet... That means, it happens only, if the file does need several blocks and more than 'maxmem' kbytes. My guess is, this happens, because on Windows 'mm' defaults to 2048, while on Linux, maxmem defaults to half of the memory available, so therefore, this bug does not trigger there, because it can read all blocks into memory when reading the buffer and does not need to get the block from the disc again. Unfortunately, I don't have a patch available yet. As side note, it looks strange, that the maxmem limit on Windows is so much smaller than on Linux. One might consider increasing this limit on Windows as well. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #8 on issue 369 by dominiqu...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 I can reproduce the valgrind errors reported in my previous comment using the following minimalistic 2-lines ~/.vimrc: $ cat ~/.vimrc set maxmem=256 set cm=blowfish Then typing... $ valgrind --log-file=vg.log --track-origins=yes ./vim --noplugin num.txt -c 'set key=num' ... causes the valgrind errors reported in my previous comment in vg.log. num.txt is the file attached in this ticket by bug submitter. The bug does not happen if num.txt is truncated to a few lines. So it only happens with large files. I'm using: * vim-7.4.729 (huge) * on Linux x86_64 (xubuntu-14.04.2) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #6 on issue 369 by fritzoph...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 Did you try disabling swap files? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 361 in vim: vimgrep over arglist doesn't work on Windows
Updates: Labels: patch Comment #4 on issue 361 by chrisbr...@googlemail.com: vimgrep over arglist doesn't work on Windows https://code.google.com/p/vim/issues/detail?id=361 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #5 on issue 369 by stlee...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 I downloaded and installed gvim-7-4-711.exe and while the problem doesn't happen exactly as I state now, the corruption is still there. Just page down to the second or third page and there is garbage in the middle of the file instead of the end of the file. One other thing I noticed now is that even with the zip encryption, corruption occurred in the middle of the file. Vim 7.3 does not have this problem so it seems like a regression. Also using blowfish takes much longer to encrypt and decrypt compared to Vim 7.3. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #2 on issue 369 by benjamin...@rockwellcollins.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 Actually we've seen problems encrypting large files at least as late as 7.4.608: https://groups.google.com/d/topic/vim_use/NFvXEopHBOI/discussion I don't think those problems were ever tracked down and fixed. Perhaps this problem is similar. However, I cannot reproduce it with the attached test file, using either blowfish2 or blowfish methods in 7.4.682. If you're still able to reproduce, try disabling swap files before encrypting. That's what worked as a workaround in the linked thread. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #3 on issue 369 by benjamin...@rockwellcollins.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 Actually we've seen problems encrypting large files at least as late as 7.4.608: https://groups.google.com/d/topic/vim_use/NFvXEopHBOI/discussion I don't think those problems were ever tracked down and fixed. Perhaps this problem is similar. However, I cannot reproduce it with the attached test file, using either blowfish2 or blowfish methods in 7.4.682. If you're still able to reproduce, try disabling swap files before encrypting. That's what worked as a workaround in the linked thread. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #7 on issue 369 by dominiqu...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 Using valgrind, I can see problems using Vim-7.4.729 on Linux x86_64. When doing: $ valgrind --log-file=vg.log --leak-check=yes --track-fds=yes --num-callers=50 --track-origins=yes vim num.txt :set cm=blowfish :set key=num After this, I can already see bugs with valgrind: === ==7298== Memcheck, a memory error detector ==7298== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==7298== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info ==7298== Command: ./vim num.txt ==7298== Parent PID: 2437 ==7298== ==7298== Use of uninitialised value of size 8 ==7298==at 0x410614: bf_e_block (blowfish.c:360) ==7298==by 0x410E46: bf_e_cblock (blowfish.c:396) ==7298==by 0x41157E: crypt_blowfish_encode (blowfish.c:618) ==7298==by 0x415291: crypt_encode (crypt.c:448) ==7298==by 0x4C2A24: ml_encrypt_data (memline.c:4874) ==7298==by 0x5E0D57: mf_write_block (memfile.c:1139) ==7298==by 0x5E0C56: mf_write (memfile.c:1095) ==7298==by 0x5E06FD: mf_release (memfile.c:870) ==7298==by 0x5DFFD8: mf_get (memfile.c:453) ==7298==by 0x4BB1AB: ml_upd_block0 (memline.c:940) ==7298==by 0x4BA837: ml_set_crypt_key (memline.c:515) ==7298==by 0x512B91: did_set_string_option (option.c:6166) ==7298==by 0x510853: do_set (option.c:4894) ==7298==by 0x47C23A: ex_set (ex_docmd.c:11996) ==7298==by 0x46D148: do_one_cmd (ex_docmd.c:2940) ==7298==by 0x469EC8: do_cmdline (ex_docmd.c:1133) ==7298==by 0x4F89F7: nv_colon (normal.c:5393) ==7298==by 0x4F1DD8: normal_cmd (normal.c:1160) ==7298==by 0x5D7A65: main_loop (main.c:1347) ==7298==by 0x5D738A: main (main.c:1047) ==7298== Uninitialised value was created by a heap allocation ==7298==at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==7298==by 0x4E0F46: lalloc (misc2.c:926) ==7298==by 0x4E0E1E: alloc (misc2.c:821) ==7298==by 0x5DF70A: mf_open (memfile.c:135) ==7298==by 0x4BA2D6: ml_open (memline.c:316) ==7298==by 0x4057AE: open_buffer (buffer.c:98) ==7298==by 0x5D96C7: create_windows (main.c:2692) ==7298==by 0x5D703D: main (main.c:881) ==7298== skip many other access to uninitialized memory ==7298== Syscall param write(buf) points to uninitialised byte(s) ==7298==at 0x6646870: __write_nocancel (syscall-template.S:81) ==7298==by 0x49AA51: write_eintr (fileio.c:10393) ==7298==by 0x5E0D81: mf_write_block (memfile.c:1145) ==7298==by 0x5E0C56: mf_write (memfile.c:1095) ==7298==by 0x5E06FD: mf_release (memfile.c:870) ==7298==by 0x5DFFD8: mf_get (memfile.c:453) ==7298==by 0x4BB1AB: ml_upd_block0 (memline.c:940) ==7298==by 0x4BA837: ml_set_crypt_key (memline.c:515) ==7298==by 0x512B91: did_set_string_option (option.c:6166) ==7298==by 0x510853: do_set (option.c:4894) ==7298==by 0x47C23A: ex_set (ex_docmd.c:11996) ==7298==by 0x46D148: do_one_cmd (ex_docmd.c:2940) ==7298==by 0x469EC8: do_cmdline (ex_docmd.c:1133) ==7298==by 0x4F89F7: nv_colon (normal.c:5393) ==7298==by 0x4F1DD8: normal_cmd (normal.c:1160) ==7298==by 0x5D7A65: main_loop (main.c:1347) ==7298==by 0x5D738A: main (main.c:1047) ==7298== Address 0x8afb575 is 373 bytes inside a block of size 4,096 alloc'd ==7298==at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==7298==by 0x4E0F46: lalloc (misc2.c:926) ==7298==by 0x4E0E1E: alloc (misc2.c:821) ==7298==by 0x4C2960: ml_encrypt_data (memline.c:4862) ==7298==by 0x5E0D57: mf_write_block (memfile.c:1139) ==7298==by 0x5E0C56: mf_write (memfile.c:1095) ==7298==by 0x5E06FD: mf_release (memfile.c:870) ==7298==by 0x5DFFD8: mf_get (memfile.c:453) ==7298==by 0x4BB1AB: ml_upd_block0 (memline.c:940) ==7298==by 0x4BA837: ml_set_crypt_key (memline.c:515) ==7298==by 0x512B91: did_set_string_option (option.c:6166) ==7298==by 0x510853: do_set (option.c:4894) ==7298==by 0x47C23A: ex_set (ex_docmd.c:11996) ==7298==by 0x46D148: do_one_cmd (ex_docmd.c:2940) ==7298==by 0x469EC8: do_cmdline (ex_docmd.c:1133) ==7298==by 0x4F89F7: nv_colon (normal.c:5393) ==7298==by 0x4F1DD8: normal_cmd (normal.c:1160) ==7298==by 0x5D7A65: main_loop (main.c:1347) ==7298==by 0x5D738A: main (main.c:1047) ==7298== Uninitialised value was created by a heap allocation ==7298==at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==7298==by 0x4E0F46: lalloc (misc2.c:926) ==7298==by 0x4E0E1E: alloc (misc2.c:821) ==7298==by 0x5DF70A: mf_open (memfile.c:135) ==7298==by 0x4BA2D6: ml_open (memline.c:316) ==7298==by 0x4057AE: open_buffer (buffer.c:98) ==7298==by 0x5D96C7: create_windows (main.c:2692) ==7298==by 0x5D703D: main (main.c:881) ==7298== Then when
Re: Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Comment #1 on issue 369 by vega.ja...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 It sounds like you're using the installer from vim.org, which is severely outdated. Testing with the latest code in Mercurial, I don't see your problem. I'd suggest using the installers the Cream project makes available (http://sourceforge.net/projects/cream/files/Vim), since it seems this has already been fixed. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 369 in vim: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3.
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 369 by stlee...@gmail.com: Crypt method blowfish corrupts large files in 7.4. Okay in 7.3. https://code.google.com/p/vim/issues/detail?id=369 What steps will reproduce the problem? 1. Create a large file (e.g. 2 MB file). You can use the num.txt.gz attachment but gunzip it first. 2. Use vim to load num.txt and configure these settings. set cm=blowfish set key=num w num2.txt 3. Use vim to load num2.txt. Enter num for the password. Go to the end of the file. The file is corrupted. What is the expected output? What do you see instead? It should show the original file contents. What version of the product are you using? On what operating system? VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 10 2013 14:33:40) This was on a Windows 8.1 machine, but it happens on Mac and Linux as well. Vim 7.3.46 does not have this problem. Using crypt method zip does not have this problem. Attachments: num.txt.gz 6.0 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 365 in vim: Adding a setting doesn't check for existing trailing comma
Comment #1 on issue 365 by chrisbr...@googlemail.com: Adding a setting doesn't check for existing trailing comma https://code.google.com/p/vim/issues/detail?id=365 What is the reason, you are adding a trailing comma? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 365 in vim: Adding a setting doesn't check for existing trailing comma
Comment #2 on issue 365 by tankorsm...@gmail.com: Adding a setting doesn't check for existing trailing comma https://code.google.com/p/vim/issues/detail?id=365 It was a typo originally. I spent a few hours trying to figure out why my tags file weren't being found and I traced it back to the python.vim adding to wildignore. I had ':set wildignore=type1, type2, type3,' in my vimrc and everything worked fine, but if I switched to a different directory and back, I'd lose my tags file, and nothing would get it back, despite the tags file being right there. The python.vim was doing ':set wildignore+=.pyc' or something, and that would result in `wildignore=type1, type2, type3,,pyc`, and that'd absolutely break tags support. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 365 in vim: Adding a setting doesn't check for existing trailing comma
Comment #3 on issue 365 by chrisbr...@googlemail.com: Adding a setting doesn't check for existing trailing comma https://code.google.com/p/vim/issues/detail?id=365 Well, here is a patch, that should prevent that. Attachments: set_trailing_comma.diff 1.4 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 365 in vim: Adding a setting doesn't check for existing trailing comma
Comment #4 on issue 365 by tankorsm...@gmail.com: Adding a setting doesn't check for existing trailing comma https://code.google.com/p/vim/issues/detail?id=365 Thanks! I'll make a ticket for the tags breaking. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 332 in vim: `colorcolumn` adds trailing whitespace to any multiline copy-pasted content
Updates: Status: Invalid Comment #5 on issue 332 by chrisbr...@googlemail.com: `colorcolumn` adds trailing whitespace to any multiline copy-pasted content https://code.google.com/p/vim/issues/detail?id=332 I think in that case, this is unavoidable and one better uses the explicit +y command to copy and paste to the system clipboard. Closing as invalid in this case. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
