Request For Feedback: "timeout per-mapping" wish, like :nnoremap lhs rhs

I'd lile to hear people feedback about "timeout per-mapping" wish, like: :noremap XYZ .. I have certain mappings for which wish to define smaller timeout that my usual keyboard timeout. Does anybody have feedback ? Yakov --~--~-~--~~~---~--~~ You re

Patch 7.1.311

Patch 7.1.311 Problem:Compiler warning for missing sentinel in X code. Solution: Change 0 to NULL. (Markus Heidelberg) Files: src/mbyte.c *** ../vim-7.1.310/src/mbyte.c Wed Jun 4 10:59:18 2008 --- src/mbyte.c Wed Jun 4 18:34:43 2008 *** *** 5520,5532 preedit

Patch 7.1.310

Patch 7.1.310 Problem:Incomplete utf-8 byte sequence at end of the file is not detected. Accessing memory that wasn't written. Solution: Check the last bytes in the buffer for being a valid utf-8 character. (mostly by Ben Schmidt) Also fix that the report

Patch 7.1.307

Patch 7.1.307 Problem:Many warnings when compiling with Python 2.5. Solution: Use ssize_t instead of int for some types. (James Vega) Files: src/if_python.c *** ../vim-7.1.306/src/if_python.c Thu Mar 8 10:20:28 2007 --- src/if_python.c Wed May 7 16:55:44 2008 *

Patch 7.1.309

Patch 7.1.309 Problem:Installing and testing with a shadow directory doesn't work. (James Vega) Solution: Add "po" to the list of directories to link. Also link the Vim scripts in testdir. And a few more small fixes. Files: src/Makefile *** ../vim-7.1.308/sr

Re: CSS syntax highlighting bug in runtime/syntax/css.vim ?

> Hi Vim users/devs :) > > I found a possible small bug in the CSS syntax file. > > Problem: > When changing the iskeyword option then syntax highlighting will go wrong. > > Steps to reproduce: >When I was tweaking my .vimrc I set > >setlocal iskeyword+=- > >for CSS files

Patch 7.1.308

Patch 7.1.308 Problem:When in readonly mode ":options" produces an error. Solution: Reset 'readonly'. (Gary Johnson) Files: runtime/optwin.vim *** ../vim-7.1.307/runtime/optwin.vim Sat May 5 19:13:05 2007 --- runtime/optwin.vim Mon May 12 22:30:28 2008 *** *** 1,7 ***

Re: Floating point syntax

On Thu 5-Jun-08 7:35am -0600, John Beckett wrote: > Bill McCarthy wrote: >> My eval.c is the current release patched by both your latest >> and John Beckett's fix. You new patch fails with: >> >> vim\vimfp> patch -b -p 0 -i Brams-may_not_work_with_jb.diff >> patching file src/eval.c Hunk #1 FAIL

RE: Floating point syntax

Bill McCarthy wrote: > My eval.c is the current release patched by both your latest > and John Beckett's fix. You new patch fails with: > > vim\vimfp> patch -b -p 0 -i Brams-may_not_work_with_jb.diff > patching file src/eval.c Hunk #1 FAILED at 4799. > 1 out of 1 hunk FAILED -- saving rejects to

Re: Floating point syntax

Nico Weber wrote: > > Yes, but most people appear to be OK with the &123.456 syntax. Thus > > if you want something else, you need to come up with good arguments. > > I still haven't seen any good arguments why an editor needs floating > point numbers at all, other than "hey, it can be don