Re: Odd :ver behavior in RH 8.0
- Aric Blumer wrote:
> I can reproduce this problem in a fully patched vim61 that I compiled asThis is weird. I can't explain it. Did you try removing "-O2" from the
> well as the RPMs at nirvani.org:
> In a large gvim window with greater than 36 lines, when I enter :ver,
> the information is displayed, then there is a beep, then it disappears.
> If I make the number of lines 36 or less, it doesn't do it (I correctly
> get the "Hit enter or command" message). The beeps are caused by the
> cursor being moved down and reaching the end of the file. It seems to be
> related to the number of pixels rather than number of lines, because
> changing the font size changes when the problem occurs in terms of text
> Also, one more oddity: If I cover a large portion of the gvim window
> with another one, it behaves correctly. If I bring the gvim window to
> the top without resizing it, the problem occurs again. Looks like it
> might be a GTK problem--it never happens in a console with the same
> Before I investigate more, can anyone reproduce this?
compilation, in case it's the gcc optimizer problem again?
The term "free software" is defined by Richard M. Stallman as
being software that isn't necessarily for free. Confusing?
Let's call it "Stallman software" then!
-- Bram Moolenaar
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
/// Creator of Vim - Vi IMproved -- http://www.vim.org \\\
\\\ Project leader for A-A-P -- http://www.a-a-p.org ///
\\\ Lord Of The Rings helps Uganda - http://iccf-holland.org/lotr.html ///