9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jacob Todd <jaketodd422@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] writing to /dev/$winid/addr
Date: Thu, 24 Apr 2014 00:18:57 -0400	[thread overview]
Message-ID: <CAB8pEY6qS-M1XuwCPy0uOL4tw5YaMqZhSzrcscY-+7OxAECs+g@mail.gmail.com> (raw)
In-Reply-To: <CAJ1xhMWna_CekxVnmMMn1dweriy2JiPNQqushfp3KYNzXDF0=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

Then why did you say it was rc? What's wrong with you.
On Apr 24, 2014 12:18 AM, "Alexander Kapshuk" <alexander.kapshuk@gmail.com>
wrote:

> That's OK. It's actually ksh on AIX.
>
> Thanks for your feedback anyway.
>
>
> On Wed, Apr 23, 2014 at 10:34 PM, erik quanstrom <quanstro@quanstro.net>
> wrote:
> >> >>> #!/bin/rc
> >> >>> {
> >> >>>  echo 'echo $SYSNAME!`uname -n`!$USER'
> >> >>>  echo 'PS1='':; '' PS2='' '''
> >> >>> } >/dev/$winid/body
> >> > this is not valid rc.
> >> >
> >> > - erik
> >> >
> >> If it's not too much trouble, would you mind demonstrating what valid rc
> >> would be for the part of the script in question.
> >
> > i'm wrong of course if the shell you're running is bash,
> > the script itself is reasonable rc.  i was confused by an
> > rc script emitting bash.
> >
> > - erik
> >
>
>

[-- Attachment #2: Type: text/html, Size: 1417 bytes --]

  reply	other threads:[~2014-04-24  4:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 13:53 Alexander Kapshuk
2014-04-23  7:29 ` Alexander Kapshuk
2014-04-23 17:03   ` Bence Fábián
2014-04-23 18:07     ` erik quanstrom
2014-04-23 19:13       ` Alexander Kapshuk
2014-04-23 19:34         ` erik quanstrom
2014-04-24  4:15           ` Alexander Kapshuk
2014-04-24  4:18             ` Jacob Todd [this message]
2014-04-24  4:25               ` Alexander Kapshuk
2014-04-25  6:35                 ` Bence Fábián

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=CAB8pEY6qS-M1XuwCPy0uOL4tw5YaMqZhSzrcscY-+7OxAECs+g@mail.gmail.com \
    --to=jaketodd422@gmail.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).