Re: Bug on FreeBSD 5.4

2009-12-02 Fir de Conversatie JD
On Dec 3, 1:46 am, Tony Mechelynck wrote: > On 03/12/09 05:20, JD wrote: > > > Vim is hardlocking for me on every single run on my FreeBSD 5.4 > > system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken. > > > It appears to compile fine, but on run, it fails to respond to any > > keystr

Re: Bug on FreeBSD 5.4

2009-12-02 Fir de Conversatie JD
On Dec 3, 1:21 am, Gary Johnson wrote: > On 2009-12-02, JD wrote: > > Vim is hardlocking for me on every single run on my FreeBSD 5.4 > > system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken. > > > It appears to compile fine, but on run, it fails to respond to any > > keystrokes and

Re: Bug on FreeBSD 5.4

2009-12-02 Fir de Conversatie Tony Mechelynck
On 03/12/09 05:20, JD wrote: > Vim is hardlocking for me on every single run on my FreeBSD 5.4 > system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken. > > It appears to compile fine, but on run, it fails to respond to any > keystrokes and eats nearly 100% of my CPU till I send it a >

Re: Bug on FreeBSD 5.4

2009-12-02 Fir de Conversatie Gary Johnson
On 2009-12-02, JD wrote: > Vim is hardlocking for me on every single run on my FreeBSD 5.4 > system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken. > > It appears to compile fine, but on run, it fails to respond to any > keystrokes and eats nearly 100% of my CPU till I send it a > SIG

Bug on FreeBSD 5.4

2009-12-02 Fir de Conversatie JD
Vim is hardlocking for me on every single run on my FreeBSD 5.4 system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken. It appears to compile fine, but on run, it fails to respond to any keystrokes and eats nearly 100% of my CPU till I send it a SIGKILL...Please help. :) Thanks -- Y

RE: Problem with "without Cream" vim-7.2.303 _vimrc

2009-12-02 Fir de Conversatie John Beckett
Steve Hall wrote: > Hmm, so then the original MyDiff() might have been ok for you? No. People have complained on the wiki that the "Vim without Cream" distribution does NOT work with diff. There were several misguided suggestions for how to make it work. Last March, I did some quick investigations

Re: Problem with "without Cream" vim-7.2.303 _vimrc

2009-12-02 Fir de Conversatie Steve Hall
On Wed, 2009-12-02 at 15:33 -0800, Gary Johnson wrote: > > I just ran that experiment on this minimalist system on which I had > installed vim "without Cream" 7.2.303. I commented-out the "set > diffexpr=MyDiff()" line in my _vimrc, then executed "Diff with Vim" > from the Explorer context menu o

RE: Problem with "without Cream" vim-7.2.303 _vimrc

2009-12-02 Fir de Conversatie Steve Hall
On Thu, 2009-12-03 at 10:02 +1100, John Beckett wrote: > > I'm too lazy to check at the moment (I build my own Vim), but > does the official Windows distribution of Vim include diff.exe? Yes, in fact the one provided by the default Vim distro. > I have an old system with "Vim without Cream" and

Re: Problem with "without Cream" vim-7.2.303 _vimrc

2009-12-02 Fir de Conversatie Gary Johnson
On 2009-12-03, John Beckett wrote: > Steve Hall wrote: > > I guess I still don't quite understand why MyDiff is > > required, internally Vim should be able to deal with it's own > > diff.exe. User options should be allowed to override it, but > > why does the default install have to condition use

RE: Problem with "without Cream" vim-7.2.303 _vimrc

2009-12-02 Fir de Conversatie John Beckett
Steve Hall wrote: > I'm concerned about relying on things outside the default Vim > distro since it is too complicated for me to package. Between > the various versions of Windows and 32- and 64-bit > complexities, building binaries in addition to the Vim ones is > too risky. > > Same goes for putt

Re: Bug with bufexists()

2009-12-02 Fir de Conversatie c9s
oh i missed the 'test1' sorry. On Dec 2, 7:58 am, "Larson, David" wrote: > Looking through the source code, I realize that this is a false alarm. The > test1 Makefile is actually a link to the file shown in buffer 4, which > bufexists is clever enough to figure out. Should the help entry for >

Re: Bug with bufexists()

2009-12-02 Fir de Conversatie c9s
actually the buffer is not wiped out. so it still exist. i dont think this is a bug. you should use buflisted() function to detect buffer. On Dec 2, 7:58 am, "Larson, David" wrote: > Looking through the source code, I realize that this is a false alarm. The > test1 Makefile is actually a link t

Patch 7.2.315

2009-12-02 Fir de Conversatie Bram Moolenaar
Patch 7.2.315 Problem:Python libs can't be found on 64 bit system. Solution: Add lib64 to the list of directories. (Michael Henry) Files: src/auto/configure, src/configure.in *** ../vim-7.2.314/src/auto/configure 2009-11-17 17:13:03.0 +0100 --- src/auto/configure 2009-12-02

Patch 7.2.314

2009-12-02 Fir de Conversatie Bram Moolenaar
Patch 7.2.314 Problem:Missing function in small build. Solution: Always include concat_str. Files: src/misc1.c *** ../vim-7.2.313/src/misc1.c 2009-12-02 17:15:04.0 +0100 --- src/misc1.c 2009-12-02 17:44:55.0 +0100 *** *** 4666,4672 return dest;

Patch 7.2.313

2009-12-02 Fir de Conversatie Bram Moolenaar
Patch 7.2.313 Problem:Command line completion doesn't work after "%:h" and similar. Solution: Expand these items before doing the completion. Files: src/ex_getln.c, src/misc1.c, src/proto/misc1.pro *** ../vim-7.2.312/src/ex_getln.c 2009-09-18 17:24:54.0 +0200 --- src/ex_

Patch 7.2.312

2009-12-02 Fir de Conversatie Bram Moolenaar
Patch 7.2.312 Problem:iconv() returns an invalid character sequence when conversion fails. It should return an empty string. (Yongwei Wu) Solution: Be more strict about invalid characters in the input. Files: src/mbyte.c *** ../vim-7.2.311/src/mbyte.c 2009-06-16 15:23:07

RE: Problem with "without Cream" vim-7.2.303 _vimrc

2009-12-02 Fir de Conversatie Steve Hall
From: "John Beckett", Tue, December 01, 2009 10:14 pm > > Sorry, I should have reported this to Steve because the issue > came up on the wiki. I put my understanding of the problem and > the best solution for a user here: > http://vim.wikia.com/wiki/Running_diff > > We are talking about Windows sys

Patch 7.2.311

2009-12-02 Fir de Conversatie Bram Moolenaar
Patch 7.2.311 Problem:Can't compile with FreeMiNT. Solution: Change #ifdef for limits.h. (Alan Hourihane) Files: src/fileio.c *** ../vim-7.2.310/src/fileio.c 2009-11-18 20:12:15.0 +0100 --- src/fileio.c2009-12-02 13:30:07.0 +0100 *** *** 21,27

Patch 7.2.310

2009-12-02 Fir de Conversatie Bram Moolenaar
Patch 7.2.310 Problem:When a filetype plugin in ~/.vim/ftdetect uses ":setfiletype" and the file starts with a "# comment" it gets "conf" filetype. Solution: Check for "conf" filetype after using ftdetect plugins. Files: runtime/filetype.vim *** ../vim-7.2.309/runtime/file

Re: Menu translation & wrong encoding in Windows 7

2009-12-02 Fir de Conversatie Mojca Miklavec
On Wed, Dec 2, 2009 at 10:19, Mojca Miklavec wrote: > Hello, > > I have submitted Slovenian Vim menu translation a while ago while I > was still using XP (and then didn't use Windows for ages; menu > translations don't work with Aqua Vim at all) and the encoding worked > properly. > > Now I tried

Re: Menu translation & wrong encoding in Windows 7

2009-12-02 Fir de Conversatie Mojca Miklavec
Hello, I have now tested the Polish version (I switched the system language to Polish) and it shows exactly the same problem (screenshot attached - hopefully 31k is still within the allowed limits). Mojca On Wed, Dec 2, 2009 at 10:19, Mojca Miklavec wrote: > Hello, > > I have submitted Slovenian

Menu translation & wrong encoding in Windows 7

2009-12-02 Fir de Conversatie Mojca Miklavec
Hello, I have submitted Slovenian Vim menu translation a while ago while I was still using XP (and then didn't use Windows for ages; menu translations don't work with Aqua Vim at all) and the encoding worked properly. Now I tried it on Windows 7 and discovered that the language is set to Slovenia