There seems to be a problem with the encoding on patch 7.3.336 as
obtained from ftp://ftp.vim.org/pub/vim/patches/ (it's ok when fetched
from code.google.com). This affects test83.
It looks like the contents has an extra utf8 encoding applied, so for
example what was 0x82 0x60 (=CP932 version
Hello,
It seems for me that cw and ce commands works the same while dw and de and
other operator like commands have a different behaviour. I did testing with
vim -u NONE (I also use the default 'cpo').
How to reproduce:
put the cursor at the beginning of word1 and try both cw and ce normal
On Wed, April 11, 2012 12:54, Marcin Szamotulski wrote:
Hello,
It seems for me that cw and ce commands works the same while dw and de and
other operator like commands have a different behaviour. I did testing
with
vim -u NONE (I also use the default 'cpo').
How to reproduce:
put the
Maybe you should contact the maintainer of this syntax file?
--
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
On Wednesday, April 11, 2012 5:54:55 AM UTC-5, Marcin Szamotulski wrote:
Hello,
It seems for me that cw and ce commands works the same while dw and de and
other operator like commands have a different behaviour. I did testing with
vim -u NONE (I also use the default 'cpo').
How to
On 07:26 Wed 11 Apr , Ben Fritz wrote:
On Wednesday, April 11, 2012 5:54:55 AM UTC-5, Marcin Szamotulski wrote:
Hello,
It seems for me that cw and ce commands works the same while dw and de and
other operator like commands have a different behaviour. I did testing with
vim -u NONE
On 04/09/12 15:53, Myk Taylor wrote:
On 04/09/12 11:49, Myk Taylor wrote:
I've noticed that my svn commit messages aren't colored properly when I
add a file with history (via svn copy, for example). I've attached a
small patch for the svn.vim syntax file to correct the regex.
I filed issue 61
John Beckett wrote:
The problem is that (I think) Vim uses the 'shell' option to
determine what shell to use to run :! commands, and some users
would change that to some quirky shell like 4NT or a host of
others. If netrw checks for 'cmd', it could conceivably fail the
check but 'move' and
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 62 by michael@gmail.com: Netrw v145: '/' character in 'is
keyword' leaks into new buffers
http://code.google.com/p/vim/issues/detail?id=62
What steps will reproduce the problem?
1. Edit a file in Vim over FTP using
Comment #1 on issue 62 by michael@gmail.com: Netrw v145: '/' character
in 'is keyword' leaks into new buffers
http://code.google.com/p/vim/issues/detail?id=62
Sorry, that 'iso' above should read: 'isk'
--
You received this message from the vim_dev maillist.
Do not top-post! Type your
Comment #2 on issue 62 by drc...@campbellfamily.biz: Netrw v145: '/'
character in 'is keyword' leaks into new buffers
http://code.google.com/p/vim/issues/detail?id=62
I tried the given steps with v146d and did not observe the issue.
iskeyword is supposed to be local-to-buffer, but
Comment #3 on issue 62 by michael@gmail.com: Netrw v145: '/' character
in 'is keyword' leaks into new buffers
http://code.google.com/p/vim/issues/detail?id=62
Hi, thanks for the response.
In terms of reproducing the problem, I think you may have to browse a
directory using Netrw
David wrote:
There seems to be a problem with the encoding on patch 7.3.336 as
obtained from ftp://ftp.vim.org/pub/vim/patches/ (it's ok when fetched
from code.google.com). This affects test83.
It looks like the contents has an extra utf8 encoding applied, so for
example what was 0x82
The following code throws off the syntax coloring on my gVim, run from
Windows 7. I'm using version 7.3:
function find_locale() {
while read -r LOC NETW REALM; do
if [ $1 == $NETW ]; then
return 0
fi
# problem begins on the line below
#done $IP_RANGES
Bram Moolenaar wrote:
David wrote:
There seems to be a problem with the encoding on patch 7.3.336 as
obtained from ftp://ftp.vim.org/pub/vim/patches/ (it's ok when fetched
from code.google.com). This affects test83.
It looks like the contents has an extra utf8 encoding applied, so
On Thu, Apr 12, 2012 at 02:43, KyleFlavin kyle.fla...@gmail.com wrote:
It doesn't seem to like the line:
done $IP_RANGES
Try putting let g:is_bash=1 in your vimrc. This syntax is a bash extension.
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
16 matches
Mail list logo
