[vim/vim] Vim sends last character of line twice when running in xterm.js (#1626)
Lucian Buzzo
I'm working on a new feature for xterm.js that allows line reflow.
sourcelair/xterm.js#609
I've found that when vim wraps a line that is too long, it sends the last character of the line twice.
Here is an example of the string data sent at 26 cols:
�[m�[H�[2J�[1;1Hlorem ipsum dolor sit amet�[2;1H�[1m�[34m~ �[3;1H~
Then if I resize to 25 cols I get this:
�[m�[H�[2J�[1;1Hlorem ipsum dolor sit amee�[2;1Ht
�[1m�[34m~
As you can see the e in amet is duplicated and vim sends a line with a length of 26 characters, even though the terminal width is set to 25 cols.
If I reduce the size by 1 column again, I get this:
�[m�[H�[2J�[1;1Hlorem ipsum dolor sit amm�[2;1Het
�[1m�[34m~
This time the m is duplicated, as it's the last character on that row.
I've found that this is happening when the terminal is xterm-color and vt100.
I'm not sure why this is happening and I was hoping the the Vim community could shed some light on this issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
Bram Moolenaar
Lucian Buzzo wrote:
> I'm working on a new feature for xterm.js that allows line reflow.
> I've found that when vim wraps a line that is too long, it sends the last character of the line twice.
> Here is an example of the string data sent at 26 cols:
> ```
> [m [H [2J [1;1Hlorem ipsum dolor sit amet [2;1H [1m [34m~ [3;1H~
> ```
> Then if I resize to 25 cols I get this:
> ```
> [m [H [2J [1;1Hlorem ipsum dolor sit amee [2;1Ht
> [1m [34m~
> ```
> As you can see the `e` in `amet` is duplicated and vim sends a line with a length of 26 characters, even though the terminal width is set to 25 cols.
>
> If I reduce the size by 1 column again, I get this:
> ```
> [m [H [2J [1;1Hlorem ipsum dolor sit amm [2;1Het
> [1m [34m~
> ```
> This time the `m` is duplicated, as it's the last character on that row.
>
>
> I'm not sure why this is happening and I was hoping the the Vim
> community could shed some light on this issue.
instead of has a line break. See src/screen.c, around line 5710.
xterm.js should replicate the behavior.
--
Yah, well, we had to carve our electrons out of driftwood we'd
find. In the winter. Uphill. Both ways.
/// Bram Moolenaar -- Br...@Moolenaar.net -- 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 ///
Lucian Buzzo
@brammool Thanks for the response!
What do you mean by "xterm.js should replicate the behavior" ? Perhaps I am being dense, but I don't understand what you mean 😄
Bram Moolenaar
Lucian Buzzo wrote:
> @brammool Thanks for the response!
> What do you mean by "xterm.js should replicate the behavior" ? Perhaps
If xterm.js is to be compatible with xterm, it should handle this
sequence of characters in the same way. Assuming you support
copy&paste.
--
Not too long ago, unzipping in public was illegal...
/// Bram Moolenaar -- Br...@Moolenaar.net -- 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 ///
—
Lucian Buzzo
Closed #1626.
Lucian Buzzo
@brammool Thanks for your help, I think this issue can be closed.
thecrazzymouse
This issue is still present in xterm.js
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.