Grex Info Conference

View Responses

Grex Info Item 162: Pine problems
Entered by raven on Thu Jul 7 01:49:15 UTC 1994:

        I am having problems using pine recently. When I go into pine a lot
of garbage appears on the screen things like "k8 1h9" etc. Any thing I
type into it (like c for compose) it gets followed by extra characters
like 7m.  I was away on vacation for a couple of weeks, and I'm configuring
a new terminal emulator, I used 7N1. Hope this helps I need pine back.

12 responses total.

#1 of 12 by raven on Thu Jul 7 02:10:38 1994:

        Hmm I just checked my comm settings and it was 8N1. Also gopher and
lynx give me garbage <sigh>.

#2 of 12 by scg on Thu Jul 7 02:15:24 1994:

Try 7E1 and see if that works.  Also make sure you have your terminal type
set correctly.

#3 of 12 by kentn on Thu Jul 7 02:28:18 1994:

I've had similar problems with pine 3.89.  I'll check my term settings
next time (though I normally run 8N1 with high bit stripped...so that
maybe the problem); I had thought it was just a problem with my vt102
termcap...

#4 of 12 by raven on Thu Jul 7 02:34:10 1994:

        I checked my terminal setting and it was set to TTY. Well I feel
just a *little* dumb now.

#5 of 12 by remmers on Thu Jul 7 09:27:30 1994:

Well, your terminal was certainly dumb.  :)

#6 of 12 by rcurl on Fri Apr 25 03:30:24 1997:

I received e-mail, which I read in pine, and then hit "y" to print a copy. 
I was connected with NCSA Telnet 2.7b4, using FreePPP, on an ethernet
link. The machine froze and all I could get out of MacsBug was that the
bomb hit in NCSA Telnet. I had to reboot, and got a "serious errors" 
dialog from Norton Disk Doctor, and had to run that to rebundle the bits,
etc. So I tried printing that message at home - and exactly the same thing
happened. I then exported the message, and looked at it with vi, and it
had double-length lines, but I didn't notice any none ascii characters. I
reformatted it in pico and printed it as a selection. So, what could be in
an e-mail message that would bomb a Mac when trying to use the Y print
command? Nothing like this had ever happened to me before.

#7 of 12 by srw on Sat May 3 04:24:53 1997:

Perhaps a bug in the printing support within NCSA telnet 2.7. It is common
to find bugs where they overwrite fixed-length arrays. If the lines were
overlong, perhaps someone made a bad assumption and didn't check. That's just
a guess. NCSA doesn't have a great record in this area, although I use 2.7
without incident. I have never tried support for printing via term-emulation.

#8 of 12 by rcurl on Sat May 3 06:34:44 1997:

Please clarify "overwrite fixed-length arrays" and "bad assumption". Somehow
the problem had to be caused by something in the message when attempting
to print with "Y" (which has been enabled, and has always worked on
every other message - hundreds - that I have printed).

#9 of 12 by valerie on Sat May 3 12:41:02 1997:

This response has been erased.

#10 of 12 by rcurl on Sat May 3 19:04:32 1997:

OK. I get it. I just can read all the Macsbug output, or maybe it would
have told me that (or, maybe not...). Thaks for the "fmt" hint. I did
essentially the same thing by reformatting the message in pico. Would
yoiu explain (again, briefly) what pcprint does, compared to what "Y" in
pine does?

#11 of 12 by valerie on Thu May 8 12:15:10 1997:

This response has been erased.

#12 of 12 by rcurl on Thu May 8 15:53:59 1997:

I have written to the company that sent the message that bombed NCSA Telnet
and suggested they format their mailer to wrap lines. No response, though,
to know if they have.

Response not possible - You must register and login before posting.