From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] ssh - pine - "garbage" characters
Date: Thu, 29 May 2008 11:01:35 -0400 [thread overview]
Message-ID: <1606d45dacd5329659b63f9bb4742991@coraid.com> (raw)
In-Reply-To: Pine.NEB.4.64.0805291420400.2903@sdf.lonestar.org
> More specifically, I can ssh from Plan 9 into my account at SDF
> (sdf.lonestar.org aka freeshell.org). I've played around with ssh options
> some and improved what I am seeing in the terminal connected to that
> account, but when I fire up Pine to attempt reading my email, I get a
> screen that is 1/2 muck/garbage characters.
going on the assumption that the "garbage" characters
are in fact cursor address escapes, you could try using
vt(1) to do a little bit of vt100 emulation.
- erik
next reply other threads:[~2008-05-29 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 15:01 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-29 14:48 Glenn Becker
2008-05-29 14:58 ` Christian Kellermann
2008-05-29 15:08 ` Russ Cox
2008-05-29 17:35 ` Glenn Becker
2008-05-29 23:45 ` Glenn Becker
2008-05-29 15:41 ` Axel Belinfante
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1606d45dacd5329659b63f9bb4742991@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).