From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: [9fans] a little gotcha
Date: Fri, 7 Jul 2006 09:34:59 -0500 [thread overview]
Message-ID: <8657272b05ba2ec52844951f8bcceda6@quanstro.net> (raw)
don't do this under 9term in plan9port:
@{cd /somewhere; tar c} | tar x
took me a while to figure out what was going on, as just catting
the output looked fine.
1: "
the explaination is missing; i'm assuming that you're running into this
magic:
fn cd { builtin cd $* && awd }
where awd outputs magic xterm escape codes. if that's what you're talking
about the quick solution is
@{ builtin cd /somewhere; tar c} | tar x
another way to work with this is to do this
fn awd { tty -s < /dev/fd/1 && builtin awd $* }
asswards combackability. ☺. i tried to convince russ that
9term needed a /dev/label analog but he didn't agree.
his point was that you still need xterm escape sequences,
since most distributions use them in their shell prompts.
- erik
On Fri Jul 7 06:12:37 CDT 2006, rog@vitanuova.com wrote:
> don't do this under 9term in plan9port:
>
> @{cd /somewhere; tar c} | tar x
>
> took me a while to figure out what was going on, as just catting
> the output looked fine.
next reply other threads:[~2006-07-07 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 14:34 erik quanstrom [this message]
2006-07-07 15:17 ` rog
2006-07-07 16:46 ` Russ Cox
2006-07-07 16:56 ` rog
2006-07-07 17:10 ` Micah Stetson
2006-07-07 17:30 ` quanstro
2006-07-07 17:38 ` quanstro
2006-07-07 19:15 ` Charles Forsyth
2006-07-08 2:55 ` Ronald G Minnich
2006-07-08 17:47 ` David Leimbach
2006-07-08 19:08 ` Micah Stetson
2006-07-09 0:45 ` Ronald G Minnich
2006-07-09 0:39 ` quanstro
2006-07-07 18:19 ` Paul Lalonde
2006-07-07 18:26 ` Lyndon Nerenberg
2006-07-07 19:00 ` David Leimbach
-- strict thread matches above, loose matches on Subject: below --
2006-07-07 11:06 rog
2006-07-07 16:45 ` Russ Cox
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=8657272b05ba2ec52844951f8bcceda6@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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).