Yegappan Lakshmanan wrote:
> On Tue, Jul 2, 2013 at 10:28 PM, Yegappan Lakshmanan
> <[email protected]> wrote:
> > Hi,
> >
> > On Tue, Jul 2, 2013 at 8:14 PM, Yegappan Lakshmanan <[email protected]>
> > wrote:
> >> Hi,
> >>
> >> On Tue, Jul 2, 2013 at 10:25 AM, Bram Moolenaar <[email protected]> wrote:
> >>>
> >>> Yegappan Lakshmanan wrote:
> >>>
> >>>> I see a problem in xterm screen refresh with the recent versions of Vim.
> >>>> The text displayed in the command line is not cleared.
> >>>>
> >>>> Steps to reproduce this problem:
> >>>>
> >>>> $ vim -u NONE -i NONE -N -c 'set cmdheight=2' -c 'set laststatus=2'
> >>>> <press CTRL-G to display the current file name and other information>
> >>>> <Press :e to edit a file>
> >>>>
> >>>> In the last step, the file name and other information displayed by
> >>>> CTRL-G are not cleared. Even if I force a screen refresh using CTRL-L
> >>>> or the ":redraw!" command, the text is not cleared.
> >>>>
> >>>> I don't see this problem with Vim 7.3.
> >>>>
> >>>> After this problem is seen, if I suspend Vim (using CTRL-Z) and
> >>>> resume it (using fg), then the screen is cleared properly.
> >>>
> >>> I cannot reproduce this problem. I do see the first message from CTRL-G
> >>> disappearing, that's most likely the other bug.
> >>> For me pressing ":" to type the ":e" command already clears the info
> >>> from CTRL-G.
> >>>
> >>> Since you say CTRL-G gives info, you actually are editing a file?
> >>>
> >>
> >> This problem is caused by the 7.3.859 patch ( 'ambiwidth' must be set
> >> by the user).
> >> When I remove this patch, I don't see this screen refresh problem.
> >>
> >
> > This problem is caused by the may_req_ambiguous_character_width()
> > function added by the above patch (859).
> >
> > When I set the 'ambwidth' option in the .vimrc file, the screen is properly
> > refreshed and the problem is not seen.
> >
>
> I tried the latest Vim version (7.3.1294). I still see the xterm
> screen refresh problem. The changes made for patch 1288 didn't fix
> this problem.
I still don't see this problem. You could compile with DEBUG_TERMRESPONSE.
You need to change "if 0" to "if 1" in src/term.c for that. Then look
at the termresponse.log file.
Also check your $TERM environment variable.
--
ARTHUR: Did you say shrubberies?
ROGER: Yes. Shrubberies are my trade. I am a shrubber. My name is Roger
the Shrubber. I arrange, design, and sell shrubberies.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
