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 "gvim -u NONE -U NONE"
- :e foo.txt
(actually any file seems to work, regardless of filetype)
- press O to open a new line at top of file
- type in a single line of gibberish without Enter
- hit Esc
- press u to undo
At this point I should be seeing a diagnostic message in the message
line at the bottom, something of the sort "1 more line; after #1
15:17:56", yet I see none. But if I do :messages, it is present.
This has been a general problem I've been seeing, undo/redo messages
which are not being displayed, or what is more likely, they are being
displayed for a split second and then immediately being cleared or
over-written (I do occasionally see the message briefly blink before
disappearing). This seems to plague predominently single-line
changes, like in case above, but it is possible I've seen it at other
times too. It is hard to nail down when this does and does not
happen.
Any fixes or workarounds for this? Can others reproduce this? It's
really a minor issue, but it's one of those that, once you notice it
happening, it starts driving you mad...
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.
On gvim 7.0.017 (huge version for GTK2 GUI), when I hit u in your
scenario I see something flit by on the command-line, too fast to be
read; then it is blank again. Typing ":mess" at that point gives at the
bottom
1 line less; before #2 13 seconds ago
IIUC, on older versions of Vim it would have been merely "1 line less"
with no clearing.
BTW, the way to determine precisely which version you're using is with
the ":version" command. Usually the first few lines are enough; the rest
describe (in this order) which features were and weren't compiled-in,
where Vim looks for its files, and which arguments were given on the
command-lines to the compile and link commands.
Best regards,
Tony.
