Hi Bram Moolenaar, you wrote:
Speed should be OK this way, but it does keep up to 32 Kbyte allocated.
That may not seem much, but if we do this in many places it quickly adds
up.
Any keep limit greater than initial size (e.g. 16384 bytes) will give the
same effect in many cases. By many
Alexei Alexandrov wrote:
OK. Platform used for investigations: x86, Windows XP SP 2. Pentium 4
Northwood, 2.4 GHz, 512M RAM.
I did 2 things: understanding stack usage and performance measurement.
To understand the stack usage I added some simple logging to regexp.c:
printing ga_maxlen
Eric Leenman wrote:
Hi,
I'm doing a reinstall of gvim and placing my color and font setting in
a seperate file in the plugin.
This file is located in: C:\Program Files\Vim\vimfiles\plugin
And it contains the following:
[START OF FILE]
:hi Commentctermfg=darkgreen gui=None guifg=darkgreen
George V. Reilly wrote:
Yakov Lerner wrote:
On 2/4/07, Yakov Lerner [EMAIL PROTECTED] wrote:
On 2/4/07, Alexei Alexandrov [EMAIL PROTECTED] wrote:
Gnu malloc (glibc) is exceptionally fast, iirc. It is possible
to benchmark the malloc speed during the ./configure time.
And
Hi Vimers,
I wonder if I can highlight more things in Python, I would like to
highlight functions call , i.e in a Python source, in the following line:
os.popen(...)
be able to highlight the word popen.
is it possible ?
Thanks for your advices
Kib.
Kazuo Teramoto wrote:
Hi,
I love the Bram fortune file (I read it all, is fun) but now looks it
be updated (with From know your smileys and jokes about proofs...)
but it is not updated in Bram site, anyone know from are Bram take the
'know your smileys'?
Bye.
PS. I love the vim list, really, I
Albie Janse van Rensburg wrote:
Eric Leenman wrote:
Hi,
I'm doing a reinstall of gvim and placing my color and font setting in
a seperate file in the plugin.
This file is located in: C:\Program Files\Vim\vimfiles\plugin
And it contains the following:
[START OF FILE]
:hi Comment
A.J.Mechelynck wrote:
[...]
The highlight groups to use for files of a given syntax are in the
oops. The highlight groups to use for files of a given syntax are defined by
the script syntaxname.vim (where syntaxname is the relevant setting of the
'syntax' option), living in the
syntax
I've been using Vim with colorscheme evening, run in gnome-terminal set
to disallow bold text and to use the Rxvt colour palette, and it's been
working great for me.
So great, in fact, that now, when I want to give GVim a chance,
I can't stand its default interpretation of the evening
Shot (Piotr Szotkowski) wrote:
I've been using Vim with colorscheme evening, run in gnome-terminal set
to disallow bold text and to use the Rxvt colour palette, and it's been
working great for me.
So great, in fact, that now, when I want to give GVim a chance,
I can't stand its default
I've written a script to remove all the gui=bold properties, please be ware
that it isn't easy, since you cannot just set all the highlighting to
gui=NONE. For those who had a default value of gui=reverse, you should NOT
set it to gui=NONE, for those who had gui=reverse,bold, you should first
set
Hi Kib :)
* kib2 [EMAIL PROTECTED] dixit:
I wonder if I can highlight more things in Python, I would like to
highlight functions call , i.e in a Python source, in the following line:
os.popen(...)
be able to highlight the word popen.
is it possible ?
Yes, it is. First, check
Albie Janse van Rensburg wrote:
A.J.Mechelynck wrote:
Albie Janse van Rensburg wrote:
Eric Leenman wrote:
Hi,
I'm doing a reinstall of gvim and placing my color and font setting
in a seperate file in the plugin.
This file is located in: C:\Program Files\Vim\vimfiles\plugin
And it contains
Using Ctrl-V, I can see that Gvim doesn't see Alt-Ctrl or
Alt-Ctrl-Shift for normal keys, just for function keys,
insert/delete, home/end, page-up/down an the arrow keys.
This is NOT a Windows issue. My email program (The Bat!),
for example, lets me make use of all of those combinations.
I
Cameron Simpson wrote:
On 05Feb2007 01:44, ben lieb [EMAIL PROTECTED] wrote:
| Have you tried:
|:n path/file*
[...]
| That's better than where I was, thanks. Ideally the files would all be
| visible, either split on the screen, or in separate tabs. Is there a
| way to do this?
You're
ben lieb wrote,
Cameron Simpson wrote:
On 05Feb2007 01:44, ben lieb [EMAIL PROTECTED] wrote:
| Have you tried:
|:n path/file*
[...]
| That's better than where I was, thanks. Ideally the files would all be
| visible, either split on the screen, or in separate tabs. Is there a
| way to do
I'm not sure what you mean by properly indented files because I've
seen a lot of different styles in the verilog code I've reviewed even
though it is coming from a group if individuals at our company who
supposedly are designing to a company standard.
I have the following in my .vimrc:
set ai
After writing out a file, I would (sometimes, not always) like to
prevent 'u' from undoing past the :w into old changes, e.g.,
- change #1
- change #2
- :w
- change #3
- change #4
- 'u' undoes #4 and then #3, but then stops
This seems like such a simple thing, but to my surprise it's less
The easiest thing to do would probably just to do :e after your :w. :e will
re-read the file, wiping the undo buffer.
Max
-Original Message-
From: Phil Edwards [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 9:26 AM
To: vim@vim.org
Subject: Clearing undo history after a
On 2/5/07, Max Dyckhoff [EMAIL PROTECTED] wrote:
The easiest thing to do would probably just to do :e after your :w. :e will
re-read the file, wiping the undo buffer.
Ah, didn't know about that side effect. I knew there had to be an
easier solution. :-) Thanks!
phil
The easiest thing to do would probably just to do :e after
your :w. :e will re-read the file, wiping the undo buffer.
Ah, didn't know about that side effect. I knew there had to
be an easier solution. :-) Thanks!
Max is correct (and it is quite easy), though just be aware that
there are
Hi,
Following your comments, I've converted my file to a scheme and placed it in
C:\Program Files\Vim\vimfiles\colors
For testing I also placed a bw.vim and a print_bw.vim in it.
The problem now is that it doesn't get loaded.
When I type :colorscheme eric it says E185: Can not find colorscheme
Currently there is much spam in recent comments:
http://vim.sourceforge.net/tips/recent_notes.php
Andy
--
EOF
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Andy Wokula wrote:
Currently there is much spam in recent comments:
http://vim.sourceforge.net/tips/recent_notes.php
Last time this was discussed I got the impression that there is a
feeling that if no one reads the spam, then it is not a problem.
But I think the situation is worse than that.
That's strange, my marks are maintained when I do an reload
the buffer with :e, and the jumplist seems to be preserved,
too. I never use either mechanism, but a little experiment
shows they are still there. Perhaps there are other things
that are erased too though, a side-effect I hadn't thought
John Beckett schrieb:
Andy Wokula wrote:
Currently there is much spam in recent comments:
http://vim.sourceforge.net/tips/recent_notes.php
Last time this was discussed I got the impression that there is a
feeling that if no one reads the spam, then it is not a problem.
But I think the
Might be easier on the user to use the 'negative captcha' idea floating
about online:
Put a hidden form field called email, phone, login or some such
that a bot is likely to fill and use CSS to hide it. A human won't see
it, but a bot will (ignoring CSS). If the field ends up containing a
My suggestion: implement a reverse captcha. There is no additional overhead for
users, and friends of mine who have implemented it have found that it foils the
spammers, at least for now, with very little work.
http://damienkatz.net/2007/01/negative_captch.html
Max
-Original
Works? Anyway my question:
Is it possible to set a global textwidth option in
some way? It is annoying me that it is set to 78 after
pretty much every file I load.
Sucker-punch spam with award-winning
Works?
Yup.
Is it possible to set a global textwidth option in
some way? It is annoying me that it is set to 78 after
pretty much every file I load.
Edit your $HOME/.vimrc (or _vimrc on win32) and add the line
set tw=78
Presto!
-tim
No no, the options is local to a buffer. The only way
I can think of is to create a hook of some sort
(events) and do 'set tw=0' after a file loads, but
gurus might know better.
Need Mail bonding?
Go to the
Try putting the following in your ~/.vimrc.
set textwidth=0
A zero for textwidth, sounds bizarre.
- Original Message
From: John Doe [EMAIL PROTECTED]
To: vim@vim.org
Sent: Monday, February 5, 2007 4:10:14 PM
Subject: test and question
Works? Anyway my question:
Is it possible to set
Well, I am so happy I can post here again (I've been
shut out for about 1/2 year for no apparent reason).
So I need to catch up with the question backlog.
I used to be able to conjure regenerating timer events
in vim 6.4 like this:
here's a nice workaround for a regenerative
CursorHold
No no, the options is local to a buffer. The only way
I can think of is to create a hook of some sort
(events) and do 'set tw=0' after a file loads, but
gurus might know better.
Ah, I see the problem. Yes, vim has hooks (autocommands,
verbosely detailed at :help autocmd.txt where you can read
On 2007-02-05, John Doe [EMAIL PROTECTED] wrote:
No no, the options is local to a buffer. The only way
I can think of is to create a hook of some sort
(events) and do 'set tw=0' after a file loads, but
gurus might know better.
There are several ways to do this. If this is a problem for only
Hi,
On 2/5/07, ben lieb [EMAIL PROTECTED] wrote:
Cameron Simpson wrote:
On 05Feb2007 01:44, ben lieb [EMAIL PROTECTED] wrote:
| Have you tried:
|:n path/file*
[...]
| That's better than where I was, thanks. Ideally the files would all be
| visible, either split on the screen, or in
Yegappan Lakshmanan wrote:
Hi,
On 2/5/07, ben lieb [EMAIL PROTECTED] wrote:
Cameron Simpson wrote:
On 05Feb2007 01:44, ben lieb [EMAIL PROTECTED] wrote:
| Have you tried:
|:n path/file*
[...]
| That's better than where I was, thanks. Ideally the files would
all be
| visible, either
Max Dyckhoff wrote:
That's strange, my marks are maintained when I do an reload the buffer with :e,
and the jumplist seems to be preserved, too. I never use either mechanism, but
a little experiment shows they are still there. Perhaps there are other things
that are erased too though, a
Dear Vim users,
I will be doing a presentation on Vim, here is the announcement:
Open Source Developers @ Google Speaker Series: Bram Moolenaar
Tuesday, February 13, 19.00h
Title: Seven habits for effective text editing, 2.0.
Bram's presentation will give an overview of several ways to
On 2/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
The :set lines=9 columns=9 does not really maxmize the Vim window.
Since there's still borders for the window, a maximized window have no
borders (AFAIK this is true for WinXP and KDE).
Since you are highly unlikely to use a
Hi!
When I work with many buffers inside vim and suddenly need to :copen
:make project, vim opens buffer in which warning or error is detected.
This is very annoying, since I have to switch from pouped-up buffer where
error or warning is detected to last working one.
Is it possible to switch
I don't know if I am in error, but ':set lines=999 columns=999' from
.vimrc does not work for me under KDE 3.5. It works in ex mode, after
everything is loaded, but not from the .vimrc file (and yes I am using
gvim). There are also some notable strange effects:
au GUIEnter * set lines=999
42 matches
Mail list logo
