🚀 go-pugleaf

In article <1992Oct4.211709.23321@Princeton.EDU>,
	ramirez.Princeton.EDU!penrose (Christopher Penrose) writes:
>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?

In article <x2x1H7+7&9@atlantis.psu.edu>,
	barr@pop.psu.edu (David Barr) writes:
>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?

David is correct.  Christopher, you were an obnoxious :-).  You
should have waited for my reply to your bug report because ... it's
a Stuart2.4 thing.  Simply turn off "Tabs can wraparound" from the
Emulation pane of an Inspector-type panel, and it'll work just
fine.  If you want to fix this for an entire site, read
"Features/Site Preferences" in the online manual.

To reliably invoke the psuedo-bug ("psuedo" because it's a feature
that can be disabled :-), get a line in tcsh that's wider than the
window's width.  Do a Control-E to go to the end of the line, and
then use a couple Meta-b sequences to get back to somewhere in the
first physical line of the long line.  Then, do Control-E again,
and you'll notice that the cursor is positioned wrong, and the
second physical line has been changed.

BTW:  I'd been noting that this was happening, too, but for some
obscure reason it didn't occur to me that it was Stuart at fault.
I don't know why.  It was pretty obvious (to me) once I looked at
the problem.  Previously it had been happening in such a way that
I didn't realize where the problem was (it's not in the editing,
it's in the positioning that happens a couple moves prior to the
editing).

Sheepishly,
--
scott hess <shess@ssesco.com>       <A port is a port, of course, of course>
12901 Upton Avenue South, #326  Burnsville, MN 55337 (612) 895-1208 Anytime!
<You praise me with faint damns, the dragon growled.  -Castle Roogna, Xanth>