[9fans] sam/rc script problem

[9fans] sam/rc script problem

[Rudolf Sykora]

Hello,

why do I get, running rc in linux (plan9port)

-----------------------------
; sam -d outit
 -. outit
$-/FERMI/+-
  FERMI LEVEL= 0.01     ITER= 70
q
-----------------------------

while

-----------------------------
; sam -d outit <<EOF
$-/FERMI/+-
q
EOF
 -. outit
  FERMI LEVEL= 0.07     ITER= 1
-----------------------------

that is, the second way finds the 1st occurence in the file while I
want the last one (as in the first case)?!
In Plan9 it works the same in both cases!

Thanks
Ruda

P.S.: Is there anything more intelligent than 'vt' for connecting to a
linux machine? I can't use a mouse in vt, window size change doesn't
propagate, sometimes I loose what was in the window... Simply, the
work with 'vt' (I 1st run 'vt' and then ssh to my linux machine; note
that I really need to run commands there) is very clumsy.

Re: [9fans] sam/rc script problem

[lucio]

> P.S.: Is there anything more intelligent than 'vt' for connecting to a
> linux machine? I can't use a mouse in vt, window size change doesn't
> propagate, sometimes I loose what was in the window... Simply, the
> work with 'vt' (I 1st run 'vt' and then ssh to my linux machine; note
> that I really need to run commands there) is very clumsy.

Use vncv(1), it's the only passable option.  At least, that's what I do.

++L

Re: [9fans] sam/rc script problem

[Steve Simon]

> P.S.: Is there anything more intelligent than 'vt' for connecting to a
> linux machine?

It all depends what you want to run on the linux box.

if you need VT in order to run your editor you could edit the file remotely
from plan9. To do this either run u9fs on the linux box, or pick up
sftpfs from contrib and use ssh. You can then import your linux boxes
namespace from plan9 (by convention put the magic in the 9fs script so its easy to do).

now you can edit files and run normal command line tools on plan9, and you only
need to use your ssh session to start programs. this (in my case at least) means I
no longer need vt and just use a rio window, so all the features of rio work
in the linx windows as elsewhere.

beware, bash can do some strange things to its output as you cut and paste long lines to it.
I usually run either a Bourne shell or Byron's rc(1) for Unix for sanity's sake.

if you get into this then you might like to take a look at rwd(1) which tries to keep
your local 'current dir' in sync with the remote one, allowing the plumber and
and filename completion to work.

It is very satisfying being able to plumb errors from a remote invocation of
gcc and see the file appear in sam on plan9.

-Steve

Re: [9fans] sam/rc script problem

[erik quanstrom]

On Tue Dec 16 08:09:34 EST 2008, steve@quintile.net wrote:
> > P.S.: Is there anything more intelligent than 'vt' for connecting to a
> > linux machine?
>
> It all depends what you want to run on the linux box.
>
> if you need VT in order to run your editor you could edit the file remotely
> from plan9. To do this either run u9fs on the linux box, or pick up
> sftpfs from contrib and use ssh. You can then import your linux boxes
> namespace from plan9 (by convention put the magic in the 9fs script so its easy to do).

really, what you'd like to do is elimate the vt escapes.
p9p can take care of most of this for you.  if you use
ed for your editor, then you're all set. :-)

- erik

Re: [9fans] sam/rc script problem

[Charles Forsyth]

>I usually run either a Bourne shell or Byron's rc(1) for Unix for sanity's sake.

If you use Plan 9 port's rc, and 9term, you'll find that shell windows also appear instantly, even on a Linux system.

Re: [9fans] sam/rc script problem

[gdiaz]

hello

it is possible to use sam -r from aplan9 machine to a linux one? it uses ssh too in plan9 isn't it?

that could be a nice option too, if you're able to distribute sam to your hosts.

slds.

gabi

Re: [9fans] sam/rc script problem

[Rudolf Sykora]

Well,
thanks so far for answering my PS...
... but what about my main question?
:)
Has anybody encountered it?
Ruda

Re: [9fans] sam/rc script problem

[erik quanstrom]

On Tue Dec 16 11:25:21 EST 2008, rudolf.sykora@gmail.com wrote:
> Well,
> thanks so far for answering my PS...
> ... but what about my main question?
> :)
> Has anybody encountered it?
> Ruda

i think rc is interpreting $ as a here document
variable and messing up.

this is one of the reasons i really don't like here
documents.  (i don't think they should be in the
shell at all.)  how about this:

echo '$-/FERMI/+-' | sam -d outit>[2]/dev/null

if you really want to use a here document, i believe
the wierdo escape is '$$'.  as in

; sam -d outit <<EOF
$$-/FERMI/+-=
EOF

- erik

Re: [9fans] sam/rc script problem

[Rudolf Sykora]

> i think rc is interpreting $ as a here document
> variable and messing up.

By why then i works nicely in plan9 and not in linux, although I use
'rc' in both?
R

Re: [9fans] sam/rc script problem

[Russ Cox]

> why do I get, running rc in linux (plan9port)
> -----------------------------
> ; sam -d outit
>  -. outit
> $-/FERMI/+-
>  FERMI LEVEL= 0.01     ITER= 70
> q
> -----------------------------
> -----------------------------
> ; sam -d outit <<EOF
> $-/FERMI/+-
> q
> EOF
>  -. outit
>  FERMI LEVEL= 0.07     ITER= 1
> -----------------------------
>
> that is, the second way finds the 1st occurence in the file while I
> want the last one (as in the first case)?!
> In Plan9 it works the same in both cases!

It works the same in both cases on Plan 9 only accidentally.
It turns out that $-/FERMI/ is the same as -/FERMI/ -- if you are
searching backward it doesn't matter whether you start at $
or at the beginning of the file.  On Plan 9:

cpu% cat <<EOF
	$-/FERMI/+-
	EOF
-/FERMI/+-
cpu%

Using the plan9port rc, I get the same behavior:

$ /usr/local/plan9/bin/rc   # plan9port rc
c2=; cat <<EOF
	$-/FERMI/+-
	EOF
-/FERMI/+-
c2=;

However, it looks like you are using Byron's Unix rc
implementation, not the plan9port one:

$ /usr/bin/rc  # byron's rc
c2=; cat <<EOF
	$-/FERMI/+-
	EOF
/FERMI/+-
c2=;

It leaves out the leading "-", which causes sam to do
a forward search and find a different line.

In all three cases, if you want to pass a $ through
uninterpreted, you should be using <<'EOF' not <<EOF.

Russ

Re: [9fans] sam/rc script problem

[Rudolf Sykora]

> In all three cases, if you want to pass a $ through
> uninterpreted, you should be using <<'EOF' not <<EOF.
>
> Russ

Thanks, that's it.
I have now reread Pike's paper on 'rc' and it's there, too.
Ruda

Re: [9fans] sam/rc script problem

[Martin Neubauer]

I tried your example (reduced to the to given lines) on my FreeBSD
system and got identical output both ways. So I suspect it's a linux
(or distro) thingie. I'm quite puzzled as to what could be the
cause, though.

Nevertheless, I'd still be cautious about here documents and variable
substitutions. (Maybe sam -d <<'EOF' would be better suited for
normal use.)

	Martin

* Rudolf Sykora (rudolf.sykora@gmail.com) wrote:
> > i think rc is interpreting $ as a here document
> > variable and messing up.
>
> By why then i works nicely in plan9 and not in linux, although I use
> 'rc' in both?
> R

Re: [9fans] sam/rc script problem

[erik quanstrom]

> Thanks, that's it.
> I have now reread Pike's paper on 'rc' and it's there, too.
> Ruda

you mean tom duff?

- erik

Re: [9fans] sam/rc script problem

[Rudolf Sykora]

> you mean tom duff?
>
> - erik
 Yes, of course, tom duff's, sure.
sorry.
R

Re: [9fans] sam/rc script problem

[erik quanstrom]

there's a new version of byron's rc on sources and ftp://rc.quanstro.net
which fixes the $- here document bug.

the real rc a better option.

- erik

Re: [9fans] sam/rc script problem

[Charles Forsyth]

>the real rc a better option.

it's one of the few times when the best choice is duff software.

Re: [9fans] sam/rc script problem

[Rudolf Sykora]

> if you need VT in order to run your editor you could edit the file remotely
> from plan9. To do this either run u9fs on the linux box, or pick up
> sftpfs from contrib and use ssh. You can then import your linux boxes
> namespace from plan9 (by convention put the magic in the 9fs script so its easy to do).

I've been using this for some time.

> now you can edit files and run normal command line tools on plan9, and you only
> need to use your ssh session to start programs. this (in my case at least) means I
> no longer need vt and just use a rio window, so all the features of rio work
> in the linx windows as elsewhere.
>
> beware, bash can do some strange things to its output as you cut and paste long lines to it.
> I usually run either a Bourne shell or Byron's rc(1) for Unix for sanity's sake.

well, this doesn't work for me, even when using just 'rc' (i.e. not bash).
When not using 'vt' I get CR printed at the end of each line, I can't
read man pages, etc.
Even though your approach allows me to use a mouse for e.g. copying,
mentioned cons are just too serious.

Ruda

Re: [9fans] sam/rc script problem

[erik quanstrom]

> well, this doesn't work for me, even when using just 'rc' (i.e. not bash).
> When not using 'vt' I get CR printed at the end of each line, I can't
> read man pages, etc.
> Even though your approach allows me to use a mouse for e.g. copying,
> mentioned cons are just too serious.

really, it's just too easy to create a script that eats crs and
other obnoxious man droppings.

- erik

Re: [9fans] sam/rc script problem

[michael block]

On Tue, Dec 16, 2008 at 13:25, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
> When not using 'vt' I get CR printed at the end of each line, I can't
> read man pages, etc.

ssh -r should strip carriage returns. to read man pages, i set my
MANPAGER environment variable to cat or to p9p's nobs. i might be
misunderstanding your problem though

-- m

Re: [9fans] sam/rc script problem

[Rudolf Sykora]

> ssh -r should strip carriage returns. to read man pages, i set my
> MANPAGER environment variable to cat or to p9p's nobs. i might be
> misunderstanding your problem though
>
> -- m

Thanks, better now.
Ruda