ibe 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.
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.
;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.
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
1 - 100 din 1493 matches
Mail list logo
