Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-18 Thread Bram Moolenaar
Maciej Kalisiak wrote: > I've created a seperate thread for this issue, even though I discussed > it briefly earlier, as I've done some testing and it seems this may be > a Vim bug. > > NOTES > - using Vim 7.0, downloaded and installed about 2 days ago > - running under WinXP SP2 > > STEPS TO R

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread A.J.Mechelynck
Eric Arnold wrote: On 6/2/06, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: Eric Arnold wrote: > Have you tried resizing your command line: > > :set cmdheight=10 > I have, and I still see the problem. Have you tried reproducing it? I could, with no problem. Yes, I see it now. It only seems to ha

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread Eric Arnold
On 6/2/06, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: Eric Arnold wrote: > Have you tried resizing your command line: > > :set cmdheight=10 > I have, and I still see the problem. Have you tried reproducing it? I could, with no problem. Yes, I see it now. It only seems to happen with 'O", not '

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread A.J.Mechelynck
Gerald Lai wrote: On Sat, 3 Jun 2006, A.J.Mechelynck wrote: Eric Arnold wrote: Have you tried resizing your command line: :set cmdheight=10 I have, and I still see the problem. Have you tried reproducing it? I could, with no problem. I can't test this because my home computer with Vim 7 i

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread Gerald Lai
On Sat, 3 Jun 2006, A.J.Mechelynck wrote: Eric Arnold wrote: Have you tried resizing your command line: :set cmdheight=10 I have, and I still see the problem. Have you tried reproducing it? I could, with no problem. I can't test this because my home computer with Vim 7 is down. What happen

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread A.J.Mechelynck
Eric Arnold wrote: Have you tried resizing your command line: :set cmdheight=10 I have, and I still see the problem. Have you tried reproducing it? I could, with no problem. Best regards, Tony.

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread Eric Arnold
Have you tried resizing your command line: :set cmdheight=10 On 6/2/06, Maciej Kalisiak <[EMAIL PROTECTED]> wrote: I've created a seperate thread for this issue, even though I discussed it briefly earlier, as I've done some testing and it seems this may be a Vim bug. NOTES - using Vim 7.0, d

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread A.J.Mechelynck
Maciej Kalisiak wrote: On 02/06/06, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: If successive messages flit by too fast, they can in some cases erase one another. As long as they appear in ":messages" it shouldn't really be a problem. I get the same behaviour as you mention later in your email.

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread Maciej Kalisiak
On 02/06/06, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: If successive messages flit by too fast, they can in some cases erase one another. As long as they appear in ":messages" it shouldn't really be a problem. I get the same behaviour as you mention later in your email. Admittedly this is a min

Re: problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread A.J.Mechelynck
Maciej Kalisiak wrote: I've created a seperate thread for this issue, even though I discussed it briefly earlier, as I've done some testing and it seems this may be a Vim bug. NOTES - using Vim 7.0, downloaded and installed about 2 days ago - running under WinXP SP2 STEPS TO REPRODUCE - fire up

problem (expanded): undo/redo messages often immediately hidden

2006-06-02 Thread Maciej Kalisiak
I've created a seperate thread for this issue, even though I discussed it briefly earlier, as I've done some testing and it seems this may be a Vim bug. NOTES - using Vim 7.0, downloaded and installed about 2 days ago - running under WinXP SP2 STEPS TO REPRODUCE - fire up "gvim -u NONE -U NONE"