Hi all,
Thank you very much for your answers. Today in the morning I had an idea which
lead me to the solution: I used perfmon.exe for further analysis and I realized
that C1 Transitions/sec, C2 Transitions/sec, C3 Transitions/sec which is
basically the power down on idle for the processor went
James Hunt wrote:
> Updated patch attached.
Thanks, I'll include it.
When you make improvements, please send me the new version of the file.
--
No man may purchase alcohol without written consent from his wife.
[real standing law in Pennsylvania, United States of America]
//
Ernie Rael wrote:
> backspace --> backslash
Thanks!
--
It is illegal to take more than three sips of beer at a time while standing.
[real standing law in Texas, United States of America]
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///spo
Patch 7.3.139 (after 7.3.137)
Problem:When 'lazyredraw' is set ":ver" output can't be read.
Solution: Don't redraw the screen when at a prompt or command line.
Files: src/getchar.c, src/message.c, src/misc1.c
*** ../vim-7.3.138/src/getchar.c2011-03-03 15:04:01.0 +0100
Hi all,
This is my first post here and I am not 100% sure if this topic
really belongs here.. Anyway, I'll give it a try.
I recently dealt with using vim's python omnicompletion for SAGE
development (see www.sagemath.org).
In order to get SAGE working in vim I tried
:py import sage.all
Howev
Patch 7.3.140
Problem:Crash when drawing the "$" at end-of-line for list mode just after
the window border and 'cursorline' is set.
Solution: Don't check for 'cursorline'. (Quentin Carbonneaux)
Files: src/screen.c
*** ../vim-7.3.139/src/screen.c 2011-02-09 17:09:26.000
Kearn Holliday reported that this Python command crashes some versions
of Vim:
:python help(dir)
This is the stack I get in gdb:
Program received signal SIGSEGV, Segmentation fault.
0x0097d726 in ?? () from /usr/lib/libpython2.6.so.1.0
(gdb) where
#0 0x0097d726 in ?? () from /usr/lib/l
Patch 7.3.141
Problem:When a key code is not set get a confusing error message.
Solution: Change the error message to say the key code is not set.
Files: src/option.c, runtime/doc/options.txt
*** ../vim-7.3.140/src/option.c 2011-01-22 00:11:42.0 +0100
--- src/option.c2
On Tue, March 22, 2011 1:29 pm, Bram Moolenaar wrote:
>
> Patch 7.3.140
> Problem:Crash when drawing the "$" at end-of-line for list mode just
> after
> the window border and 'cursorline' is set.
> Solution: Don't check for 'cursorline'. (Quentin Carbonneaux)
> Files:src
Tobias Columbus wrote:
> This is my first post here and I am not 100% sure if this topic
> really belongs here.. Anyway, I'll give it a try.
>
> I recently dealt with using vim's python omnicompletion for SAGE
> development (see www.sagemath.org).
> In order to get SAGE working in vim I tried
Christian Brabandt wrote:
> On Tue, March 22, 2011 1:29 pm, Bram Moolenaar wrote:
> >
> > Patch 7.3.140
> > Problem:Crash when drawing the "$" at end-of-line for list mode just
> > after
> > the window border and 'cursorline' is set.
> > Solution: Don't check for 'cursorline'. (Quen
Patch 7.3.142
Problem:Python stdout doesn't have a flush() method, causing an import to
fail.
Solution: Add a dummy flush() method. (Tobias Columbus)
Files: src/if_py_both.h
*** ../vim-7.3.141/src/if_py_both.h 2010-10-27 12:17:54.0 +0200
--- src/if_py_both.h
On Mar 21, 6:02 pm, Ivan Krasilnikov wrote:
> On Mon, Mar 21, 2011 at 13:48, pmehrwald wrote:
> > Hi,
>
> > We are facing a severe problem on using :g on our machines at work. On
> > two different dell machines this command causes problems after
> > updating to x64 Windows 7 or Windows Server 2
make[1]: Entering directory `/root/.build/vim/vim-hg/vim/src/po'
OLD_PO_FILE_INPUT=yes msgfmt -v -o it.mo it.po
it.po:3790: `msgid' and `msgstr' entries do not both end with '\n'
msgfmt: found 1 fatal error
1781 translated messages.
make[1]: *** [it.mo] Error 1
make[1]: Leaving directory `/root/.b
On Tuesday 22 March 2011 13:40:19 you wrote:
> Kearn Holliday reported that this Python command crashes some
> versions
>
> of Vim:
> :python help(dir)
>
> This is the stack I get in gdb:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0097d726 in ?? () from /usr/lib/libpython
Wanted to suggest adding support for terminal colors to gvim. Currently, vim
in a terminal can get colored output from system commands that offer a
colored output feature (grep, ls, grep alternatives like ack-grep.) gvim
doesn't interpret the terminal color control characters shows the ascii
parts
Patch 7.3.143
Problem:Memfile is not tested sufficiently. Looking up blocks in a
memfile is slow when there are many blocks.
Solution: Add high level test and unittest. Adjust the number of hash
buckets to the number of blocks. (Ivan Krasilnikov)
Files: Fileli
On 22/03/11 16:20, Tony Mechelynck wrote:
make[1]: Entering directory `/root/.build/vim/vim-hg/vim/src/po'
OLD_PO_FILE_INPUT=yes msgfmt -v -o it.mo it.po
it.po:3790: `msgid' and `msgstr' entries do not both end with '\n'
msgfmt: found 1 fatal error
1781 translated messages.
make[1]: *** [it.mo] E
Kevin wrote:
Wanted to suggest adding support for terminal colors to gvim.
Currently, vim in a terminal can get colored output from system
commands that offer a colored output feature (grep, ls, grep
alternatives like ack-grep.) gvim doesn't interpret the terminal color
control characters show
Bram Moolenaar wrote:
> Patch 7.3.143
> Problem: Memfile is not tested sufficiently. Looking up blocks in a
> memfile is slow when there are many blocks.
> Solution: Add high level test and unittest. Adjust the number of hash
> buckets to the number of blocks. (Ivan K
Tobias Columbus wrote:
> On Tuesday 22 March 2011 13:40:19 you wrote:
> > Kearn Holliday reported that this Python command crashes some
> > versions
> >
> > of Vim:
> > :python help(dir)
> >
> > This is the stack I get in gdb:
>
> [...]
>
> I just had a look at what's going on there.
> :p
Dominique Pelle wrote:
> Patch-7.3.143 is meant to add src/memfile_test.c. I see the new file
> in the patch, but it's missing in Mercurial.
Sorry, forgot to do "hg addremove". Should be OK now.
--
Another bucket of what can only be described as human ordure hits ARTHUR.
ARTHUR: ... Right
> On Tuesday 22 March 2011 13:40:19 you wrote:
> > Kearn Holliday reported that this Python command crashes
> > some versions
> >
> > of Vim:
> > :python help(dir)
> >
> > This is the stack I get in gdb:
SNIP
> > Does someone have an idea why this happens or how to fix it?
>
> I just had a l
Since a couple of days I have been having the following problem with
vim:
I use it normally and after a while I am unable to save the file
using :wa
Each time I press enter nothing happens and when I press other key
other then enter (say space) the following
shows up
:wa92_parse_cmd_line()
I sear
Hi skeept!
On Di, 22 Mär 2011, skeept wrote:
> Since a couple of days I have been having the following problem with
> vim:
>
> I use it normally and after a while I am unable to save the file
> using :wa
> Each time I press enter nothing happens and when I press other key
> other then enter (say
On Tue, 22 Mar 2011, Christian Brabandt wrote:
Hi skeept!
On Di, 22 Mär 2011, skeept wrote:
[...] when I press other key other then enter (say space) the
following shows up :wa92_parse_cmd_line()
I searched in the vim source with grep and in my .vim folder but
could not find this string.
Reply to message «problem saving file (or other command mode)»,
sent 23:28:30 22 March 2011, Tuesday
by skeept:
> I searched in the vim source with grep and in my .vim folder but could
> not find this string.
You should not have searched for this string, but for `s:parse_cmd_line': see
`:h ' (`9
Hi Benjamin!
On Di, 22 Mär 2011, Benjamin R. Haskell wrote:
> On Tue, 22 Mar 2011, Christian Brabandt wrote:
>
> >Hi skeept!
> >
> >On Di, 22 Mär 2011, skeept wrote:
> >
> >>[...] when I press other key other then enter (say space) the
> >>following shows up :wa92_parse_cmd_line()
> >>
> >>I sea
Hi Bram!
On Di, 22 Mär 2011, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Tue, March 22, 2011 1:29 pm, Bram Moolenaar wrote:
> > >
> > > Patch 7.3.140
> > > Problem:Crash when drawing the "$" at end-of-line for list mode just
> > > after
> > > the window border and 'cu
Hi Bram!
On So, 20 Mär 2011, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Do, 17 Mär 2011, Bram Moolenaar wrote:
> >
> > > If you do gH it deletes the line. It's only on the last line that
> > > it makes the line empty. Let's call that a bug.
> > >
> > > Someone who wants to
On Mar 22, 1:27 pm, Charles Campbell
wrote:
> Perhaps the AnsiEsc plugin which colorizes text according to ansi escape
> sequences does what you want; you can get the plugin from:
>
> http://vim.sourceforge.net/scripts/script.php?script_id=302 (stable)
> http://mysite.verizon.net/astron
Tobias Columbus wrote:
> > On Tuesday 22 March 2011 13:40:19 you wrote:
> > > Kearn Holliday reported that this Python command crashes
> > > some versions
> > >
> > > of Vim:
> > > :python help(dir)
> > >
> > > This is the stack I get in gdb:
> SNIP
> > > Does someone have an idea why this ha
On 03/22/2011 09:28 PM, skeept wrote:
> Since a couple of days I have been having the following problem with
> vim:
>
> I use it normally and after a while I am unable to save the file
> using :wa
> Each time I press enter nothing happens and when I press other key
> other then enter (say space) t
Will Gray (graywh) wrote:
On Mar 22, 1:27 pm, Charles Campbell
wrote:
Perhaps the AnsiEsc plugin which colorizes text according to ansi escape
sequences does what you want; you can get the plugin from:
http://vim.sourceforge.net/scripts/script.php?script_id=302 (stable)
http://
On 23/03/11 3:21 AM, Kevin wrote:
Wanted to suggest adding support for terminal colors to gvim.
I want this, too, and it's on my to-do list to investigate implementing some
time.
That certainly shouldn't stop anyone else jumping in and doing it, though. No idea
when I might have enough time
35 matches
Mail list logo
