VanDyke Software Forums

VanDyke Software Forums (https://forums.vandyke.com/index.php)
-   General (https://forums.vandyke.com/forumdisplay.php?f=11)
-   -   securecrt xterm terminal emulation issue with vim (https://forums.vandyke.com/showthread.php?t=12803)

Killing 09-05-2017 03:48 PM

securecrt xterm terminal emulation issue with vim
 
With a recent update to vim its doing something new with the terminal information and is causing file corruption in combination with the xterm emulation of securecrt.

According to this post securecrt isn't doing what an xterm would.

This is with:
Version 8.1.2 (x64 build 1362) - Official Release - April 27, 2017

ekoranyi 09-05-2017 04:04 PM

Hi Killing,

I'm sorry you're having trouble.

What was the update to VIM, from what version to what version?

What does the file corruption look like?

Would it be possible for you to provide a screenshot of the corruption you are seeing and perhaps an example of a different application that is not having this trouble. To help ensure we don't accidentally expose sensitive information can you send the screenshot to Support@VanDyke.com with "Attn: Eric forum post 12803" in the subject line?

Killing 09-05-2017 04:15 PM

I'm still trying to determine from exact from version I had before the upgrade but I have confirmed the following:
1. vim-8.0.0600 works
2. vim-8.0.1035 is broken
3. vim -u NONE <file> or vim -u NORC <file> don't display the corruption.
4. Unsetting TERM environment variable doesn't display the corruption.

The corruption displays as an initial p instead real first character of the file e.g.
p Core settings
keyrate="fast"

instead of:
# Core settings
keyrate="fast"

Doesn't matter what the first char of the file is p is always displayed.

From reading the post in the vim forum I believe its meant to display the cursor but due to the emulation issue its not.

Killing 09-05-2017 04:36 PM

For reference this is one of the github issues from vim side for this which has lots of information your developers may be interested in:
https://github.com/vim/vim/issues/2008

ekoranyi 09-05-2017 05:04 PM

Hi Killing,

SecureCRT does not support the '$q q' escape sequence. Do you have any documentation from xterm about this particular escape sequence? If so I'd be interested in taking a look at what this sequence does.

I have recorded your idea in our database of SecureCRT feature requests so that the product director can evaluate it for possible inclusion in a future release.

Should a version of SecureCRT become available with this feature, we will be sure to let you know. If you would like to be contacted directly please send an email to Support@VanDyke.com with "Attn: Eric forum post 12803" in the subject line.

ekoranyi 09-12-2017 02:21 PM

Hi Killing,

What version of VIM are you using? I've tried recreating the issue using VIM version 8.0.1097 and it appears to display correctly?

Would it be possible for you to provide a raw log of your session when you see the issue. To avoid exposing potentially sensitive data we ask that you do not post the log to the forums. Please email the resulting log to Support@VanDyke.com with "Attn: Eric forum post 12803" in the subject.

Please choose Raw Log Session from the main File drop down menu, connect to your session, launch VIM, when the issue presents you can disconnect. Please then email the log created for review.

Thank you in advance for helping get to the bottom of the issue.


All times are GMT -6. The time now is 02:59 AM.