vi (or any clone, like vim) saves the tty modes when it starts before setting its own, and restores them on exit; so that doesn't necessarily tell you anything.
Knowing the tty name for each, one could (from another window) do e.g. stty </dev/tty003 to see the tty modes of that other window while vi is running. But I wouldn't expect anything much from that either. $TERM should be the same (dtterm), check (in each window) with env | grep TERM (to be sure you're seeing the exported value) The dtterm terminfo entry should exist; check with infocmp dtterm and see that it gives some output and looks reasonable. (I could post mine, if necessary). If all of those check out, you may have found a bug. I have seen cases with various terminal emulators where a given tab or window gets fouled up enough that the only recourse is to exit it and start a new one. I'd like to think that shouldn't happen, but it does sometimes. Is there anything different you might have done in one but not the other before the vi session? Accidentally cat-ing a binary file to the terminal can be a severe stress test of whether a terminal reacts badly to malformed escape sequences (or sometimes to valid ones, if they change its behavior). > On Jun 18, 2018, at 08:50, Antonis Tsolomitis <antonis.tsolomi...@gmail.com> > wrote: > > > The screenshot dtterm.png shows two dtterms runing vi (vim) > The one on the left shows erratic behavior since it repeats the info line of > vi > at several heights while the dtterm on the right is a freshly started one and > behaves correctly. > When this happens with vi you have to stop and start a fresh dtterm since > what you > see does not correspond to the truth. There are lines showing text and text > does not exist on these. > > Then I exited vi from both of them and run stty -a. This is the content of > screenshot dtterm2 which shows > that the output is identical. > > The system is Ubuntu 14.04LTS. CDE is latest stable. > > Antonis. > > <dtterm.png><dtterm2.png>------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! > http://sdm.link/slashdot_______________________________________________ > cdesktopenv-devel mailing list > cdesktopenv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
signature.asc
Description: Message signed with OpenPGP
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
