🚀 go-pugleaf

In article <x2x1H7+7&9@atlantis.psu.edu> barr@pop.psu.edu (David Barr) writes:
>In article <1992Oct4.211709.23321@Princeton.EDU> ramirez.Princeton.EDU!penrose (Christopher Penrose) writes:
>>
>>I hate to sound like an obnoxious UNIX geek, but it seems that tcsh users
>>are poseurs:
>
>Well if you say things like this, I can see how people might think that.
>
>>no one has noticed or fixed (to my limited knowledge) a really  
>>obnoxious bug.  When using tcsh command-line editting with lines greater than
>>the screen width, the cursor gets "lost" and edits are placed in strange places  
>>on the line.  This gives me vertigo.  I am using the binary compiled on a NeXT.
>>All our servers have succumbed to this brain-teasing binary too.  It is the  
>>foul 6.02 binary that is lurking on the archives.
>
>>Does anyone have any info regarding the maker of this evil binary?  Can I
>>submit bug reports?  Or am I just experiencing localized reality failure?
>>Should I just sit quietly and expect to be ignored?
>
>Again, please be a little more understanding when reporting bugs.
>Calling it "evil," "foul," "virulent," and "obnoxious" only get people
>mad.  A simple "I seem to be having problems with command-line editing
>on my NeXT running <os version>.  I'm running tcsh <version>, from the
>binary I ftp'd from <host>" will do.  People will be much more
>repsonsive to your problems.  I can see why you would be ignored.
>
>I've never had this problem.  I've tried to duplicate your problem on a
>NeXT running 2.0 and tcsh 6.00.  I run tcsh normally on Sun's, and have
>been using 6.02 there and have never had a problem there, either.  I
>suspect a terminal bug.  What terminal are you using?
>

As the maintainer of the evil tcsh source [but not the maker of the
evil tcsh binary], I am going to try to reply and clarify the
situation.

The terminal handling has been changed in tcsh-6.02. Specifically the
tcsh command line editor in 6.02 uses the rightmost column of the
terminal and does not use carriage return to wrap to the next line
(when possible). The advantage of this new scheme is that window system
users can cut and paste multi-line commands without splitting them [To
my knowledge no other shell does this correctly].

Unfortunately handling line wrapping this way is more expensive and
assumes that your termcap "am" [automatic margin] and "xn" [magic
margin] variables are set correctly, otherwise the screen will appear
gargbled.

Even if your termcap description is incorrect, you can use :

settc am <no|yes> and
settc xn <no|yes> 

to remedy the situation.

As David Barr said:

The key question is what terminal are you using and what is the termcap/
terminfo description for it?

christos