Hello,
Vim 7.1b on Windows XP doesn't properly recognizes words. It does not
count Polish diacritics in, so each one is treated as separate word.
This is serious bug and with taking into account that Windows users can
have problems with getting patched versions it is IMO showstopper.
In its
Hi Bram,
Find attached a patch that corrects the following in the docs -
- Tidy up the use of Tab, Tab, tab etc
- Fix the highlighting for the title of getwinposx() in eval.txt.
There is a missing '' at the start of the previous line to terminate
the previous highlighting.
- One or two
Mikolaj Machowski wrote:
Vim 7.1b on Windows XP doesn't properly recognizes words. It does not
count Polish diacritics in, so each one is treated as separate word.
This is serious bug and with taking into account that Windows users can
have problems with getting patched versions it is
What is 'iskeyword' set to and where was it set?
:15verbose se isk?
returns
n:\mikolaj\pf\vim\vim71b\vimrc_example.vim
m.
INFERNAL: From Paris to Berlin
Potężna dawka hitów! CD+DVD już w sklepach!
Mikolaj Machowski wrote:
Vim 7.1b on Windows XP doesn't properly recognizes words. It does not
count Polish diacritics in, so each one is treated as separate word.
This is serious bug and with taking into account that Windows users can
have problems with getting patched versions
Hi,
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
If you had checked out a copy of the sources before, please run this
command in
Patch 7.1b.002
Problem:When 'maxmem' is large there can be an overflow in computations.
(Thomas Wiegner)
Solution: Use the same mechanism as in mch_total_mem(): first reduce the
multiplier as much as possible.
Files: src/memfile.c
***
Nicolas Weber wrote:
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
If you had checked out a copy of the sources before, please
Following description lifted from bug filed at
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
[EMAIL PROTECTED]:~$ rm .viminfo
[EMAIL PROTECTED]:~$ ln -s /dev/null .viminfo
[EMAIL PROTECTED]:~$ ls -l .viminfo
lrwxrwxrwx 1 sa sa 9 2007-01-12 17:16 .viminfo - /dev/null
[EMAIL
Micah Cowan wrote:
Following description lifted from bug filed at
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
[EMAIL PROTECTED]:~$ rm .viminfo
[EMAIL PROTECTED]:~$ ln -s /dev/null .viminfo
[EMAIL PROTECTED]:~$ ls -l .viminfo
lrwxrwxrwx 1 sa sa 9 2007-01-12 17:16 .viminfo -
Michael Wookey wrote:
Hello vimmers,
I am running 7.1a.001 on OSX and have just noticed the following from
console vim (running in Terminal.app and also occurs in iTerm.app).
If I change the colour scheme I receive a lot of error output. For
example:
:colorscheme desert
Results in:
Micah Cowan [EMAIL PROTECTED] writes:
Is there a good reason not to simply follow symlinks when they are
encountered, as this user obviously expected?
If it did follow the symlink to /dev/null, and tried to read from that
device, it would fail. You can't (or at least, shouldn't) read from
Taylor Venable wrote:
[...]
If it did follow the symlink to /dev/null, and tried to read from that
device, it would fail. You can't (or at least, shouldn't) read from
/dev/null because it's a sink, not a source. What kind of behavior
would you expect, trying to read from /dev/null?
[...]
On 5/12/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nicolas Weber wrote:
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
If you
14 matches
Mail list logo
