[9fans] a little gotcha

[9fans] a little gotcha

[rog]

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.

Re: [9fans] a little gotcha

[Russ Cox]

maybe awd or that fn cd needs to check isatty.

russ

Re: [9fans] a little gotcha

[Ronald G Minnich]

Micah Stetson wrote:
>> have some fun. In plan9ports rio, make a real little xterm window (with
>> bash in it), hit ^R, and watch the window disappear. It's fun if you're
>> like me and have a low fun threshhold :-)
>
>
> I feel left out.  It doesn't work for me.  How will I have fun?
>
> Micah

dang.

Well, in plan 9ports, I frequently don't use 9term (sorry), I use xterm.
You have to make it REALLY small, like 2 characters.

ron

Re: [9fans] a little gotcha

[quanstro]

he good news on the xterm front is they *finally* got utf-8 working.
about 10 years after 9term did.

- erik

On Sat Jul  8 19:47:56 CDT 2006, rminnich@lanl.gov wrote:
>
> Well, in plan 9ports, I frequently don't use 9term (sorry), I use xterm.
> You have to make it REALLY small, like 2 characters.
>
> ron

Re: [9fans] a little gotcha

[Micah Stetson]

> have some fun. In plan9ports rio, make a real little xterm window (with
> bash in it), hit ^R, and watch the window disappear. It's fun if you're
> like me and have a low fun threshhold :-)

I feel left out.  It doesn't work for me.  How will I have fun?

Micah

Re: [9fans] a little gotcha

[Ronald G Minnich]

Charles Forsyth wrote:
>>but there are some fancier editing tricks that readline uses that
>
>
> would readline be the thing that is always annoying me when i
> try to send a line that's a little longer than it expects and i get a weird sequence
> out, then most of the line repeated, then it settles down a bit until next time?
>

have some fun. In plan9ports rio, make a real little xterm window (with
bash in it), hit ^R, and watch the window disappear. It's fun if you're
like me and have a low fun threshhold :-)

ron

Re: [9fans] a little gotcha

[Charles Forsyth]

> but there are some fancier editing tricks that readline uses that

would readline be the thing that is always annoying me when i
try to send a line that's a little longer than it expects and i get a weird sequence
out, then most of the line repeated, then it settles down a bit until next time?

Re: [9fans] a little gotcha

[Lyndon Nerenberg]

> Add another 9term user.

9term++

About the only time I fire up xterm any more is to run pine.

Re: [9fans] a little gotcha

[Paul Lalonde]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Add another 9term user.

Paul

On 7-Jul-06, at 9:46 AM, Russ Cox wrote:

>> stuff should *generate* them... it's a pity really that writing a
>> 9p fileserver
>> for 9term to implement awd functionality isn't roughly the same
>> amount of code
>> as interpreting the escape-sequence.
>
> not the point.  most people i know using p9p don't actually use 9term.
> i do, but i'm in the minority.
>
> russ

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFErqXMpJeHo/Fbu1wRAj5sAKCwBxM5cAElUNl7P/Zv3AZu1+v/eACdGJU6
MSq9hkXqPdtaCL7G9csNpd4=
=EKbk
-----END PGP SIGNATURE-----

Re: [9fans] a little gotcha

[quanstro]

On Fri Jul  7 12:41:38 CDT 2006, quanstro@quanstro.net wrote:
>oh, for isatty
>	fn awd {tty -s </dev/fd/1 && awd $*}

that should be
	fn awd {tty -s </dev/fd/1 && builtin awd $*}

d'oh.

Re: [9fans] a little gotcha

[quanstro]

i've used 9term since it first appeared.  but it's true.  it doesn't
quite fit into unix.  readline, for example, does not work well.
i've added some support to recognize color escapes (and ignore them),
but there are some fancier editing tricks that readline uses that
9term doesn't recognize.  i didn't have the energy to fix those.
instead, i avoid bash. ;-)

oh, for isatty
	fn awd {tty -s </dev/fd/1 && awd $*}

- erik

On Fri Jul  7 11:58:20 CDT 2006, rog@vitanuova.com wrote:
> > most people i know using p9p don't actually use 9term.
> > i do, but i'm in the minority.
>
> well then you're in a minority of one more. i can't see how anyone
> would go back to a 70s tty emulation after having used rio for a while.
> if i can't edit any text in the window or go into hold mode, i feel
> like one hand's being tied behind my back...
>
> anyway, an isatty check seems like a good plan.

Re: [9fans] a little gotcha

[Micah Stetson]

> well then you're in a minority of one more. i can't see how anyone
> would go back to a 70s tty emulation after having used rio for a while.

I was surprised it was a minority.  I wouldn't want to live in a world
of xterms.

Micah

Re: [9fans] a little gotcha

[rog]

> most people i know using p9p don't actually use 9term.
> i do, but i'm in the minority.

well then you're in a minority of one more. i can't see how anyone
would go back to a 70s tty emulation after having used rio for a while.
if i can't edit any text in the window or go into hold mode, i feel
like one hand's being tied behind my back...

anyway, an isatty check seems like a good plan.

Re: [9fans] a little gotcha

[Russ Cox]

> stuff should *generate* them... it's a pity really that writing a 9p fileserver
> for 9term to implement awd functionality isn't roughly the same amount of code
> as interpreting the escape-sequence.

not the point.  most people i know using p9p don't actually use 9term.
i do, but i'm in the minority.

russ

Re: [9fans] a little gotcha

[rog]

> his point was that you still need xterm escape sequences,
> since most distributions use them in their shell prompts.

it might be reasonable to interpret them (along with cr-lf and bs), but that doesn't mean that p9p
stuff should *generate* them... it's a pity really that writing a 9p fileserver
for 9term to implement awd functionality isn't roughly the same amount of code
as interpreting the escape-sequence.

[9fans] a little gotcha

[erik quanstrom]

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.