Max Dyckhoff wrote:
Thanks Tony,
A.J.Mechelynck wrote:
Keeping things around is one thing, keeping them in memory is another. By
using ":set hidden" you _tell_ Vim to keep in memory the _whole data_ of every
single buffer you visited during the current session, which IMHO is a little
overdoing
Thanks Tony,
A.J.Mechelynck wrote:
> Keeping things around is one thing, keeping them in memory is another. By
> using ":set hidden" you _tell_ Vim to keep in memory the _whole data_ of every
> single buffer you visited during the current session, which IMHO is a little
> overdoing it. By setting
Max Dyckhoff wrote:
[...]
I do have 'hidden' set, because I like to keep things around. :ls! shows that I
currently have about 550 buffers open. I know this seems like a lot, but we do
have a large code base!
[...]
Keeping things around is one thing, keeping them in memory is another. By
usi
On 4/4/07, Yakov Lerner <[EMAIL PROTECTED]> wrote:
> On 4/4/07, Max Dyckhoff <[EMAIL PROTECTED]> wrote:
>> I do have 'hidden' set, because I like to keep things around.
>> :ls! shows that I currently have about 550 buffers open. we do
>> have a large code base!
>
> Then get another 1-2 GB of RAM. I
On 4/4/07, Max Dyckhoff <[EMAIL PROTECTED]> wrote:
On 4/4/07, Yakov Lerner <[EMAIL PROTECTED]> wrote:
> Max,
>
> I recalled two more things. Is your 'hidden' option set ? If it's set,
> vim *will* grow. With 'hidden' set, vim will keep in memory much data
> about old buffers. If you want to mini
On 4/4/07, Yakov Lerner <[EMAIL PROTECTED]> wrote:
> Max,
>
> I recalled two more things. Is your 'hidden' option set ? If it's set,
> vim *will* grow. With 'hidden' set, vim will keep in memory much data
> about old buffers. If you want to minimize memory, first thing you'd do is
> ':set nohidden
On 4/4/07, Max Dyckhoff <[EMAIL PROTECTED]> wrote:
My instance of vim (gvim on Windows) appears to have a memory leak, which makes
me sad. Is this a common thing for everyone, or is there something in my setup
which might be causing it? It's pretty serious.
When I start gvim and load my standa
On 4/3/07, Max Dyckhoff <[EMAIL PROTECTED]> wrote:
My instance of vim (gvim on Windows) appears to have a memory leak, which makes
me sad. Is this a common thing for everyone, or is there something in my setup
which might be causing it? It's pretty serious.
When I start gvim and load my standa
> :sp on a new buffer causes a raise of 4-8K.
> :q on a split causes a raise of 4-8K.
> Switching to/from gvim causes a small increase, typically 4-8K for a few
> switches.
> Searching (with *) for a word in a .c file (with syntax highlighting) causes
> it to increase. If you hold down * then
My instance of vim (gvim on Windows) appears to have a memory leak, which makes
me sad. Is this a common thing for everyone, or is there something in my setup
which might be causing it? It's pretty serious.
When I start gvim and load my standard session, it will take up about 86MB of
RAM. This
10 matches
Mail list logo
