smcup/rmcup is in Nevada 76 for xterm

If the title means anything to you, then it could be of two things:
o You are ancient in the computing age :)
o You are a vi user

Thanks to Brian Utterback, a simple fix as he said by simply updating a couple of terminfo file on Solaris. Now, when you vi in a gnome-terminal or xterm, the screen area where you vi drawn over is restored when you exit the editor. Though it is a little thing, but it is little thing in life that enriches the user experience and so is work more pleasurable.

Unfortunately, it also caused a regressive behaviour in another bug. Though I think this is probably the right behaviour for less(1) or more(1). Pity I don't have a Linux box to test how does it looks at the moment.

Well, let's see how thing go

Comments:

This introduce an undeciered behaviour in the pager less and editor vi by restoring the screen to what it was before the command was issued. It is _NOT_ a good thing IMNSHO.

Posted by Thommy M. on November 18, 2007 at 11:53 PM GMT+00:00 #

I hate this misfeature. Restoring the old terminfo entry for xterm was the first thing I did in snv76

Posted by Daniel Rock on November 19, 2007 at 01:23 AM GMT+00:00 #

I hate this misfeature, too. It is an abomination. If I want to run vi in an "alternate window" and have my original window intact when I exit, I type "xterm -e vi". Most of the time, when I run vi or man or less from a shell prompt, I intentionally arrange for the text of interest to be still on the screen when I return to the prompt so that I can refer to it as I type the next command.

But I'm glad that the Solaris terminfo is now the same as on other modern systems. It's the right thing to do, even though it means that now, all the systems I use are equally abominable by default. :-)

The main reason that I don't use gnome-terminal is that it has no way to turn off this annoying behavior. At least xterm lets me, the user, decide what behavior I want, rather than the maintainer of the terminfo database on each remote machine I use.

This also underscores why the "new" terminfo strings are the right way to go: The most flexible and user-satisfying arrangement is for all screen-based programs and all terminfo databases to emit the appropriate ti/te sequences, and for all terminal programs to have a preference setting that the user can control as desired.

Posted by Mike Ditto on November 19, 2007 at 03:05 AM GMT+00:00 #

If it is any consolation, I find it rather annoying as well, and I made the fix. But the previous terminfo entry was incorrect. But the creators of vi and less choose to use the capabilities that map in the alternate screen. Without the correct terminfo entry, it was impossible for any program to get the desired behavior.

Posted by Brian Utterback on November 19, 2007 at 08:38 AM GMT+00:00 #

Thanks all for the comment.

We should fix@source. Without the correct terminfo, we can never fix at source. Though I know it is not funny when something one gets use to for years just change.

But more does behave like less behaves prior to b76. Use more instead less may be a reasonable alternative.

Posted by Ghee on November 19, 2007 at 09:08 AM GMT+00:00 #

Post a Comment:
Comments are closed for this entry.
About

I work in the Desktop Group Site Meter

Search

Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today