From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <53567454.2050509@gmail.com> <535810E5.1010507@gmail.com> <63ad87826698c76996628eaa50699e64@ladd.quanstro.net> Date: Fri, 25 Apr 2014 08:35:23 +0200 Message-ID: From: =?UTF-8?B?QmVuY2UgRsOhYmnDoW4=?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11346bd2a3cd1e04f7d82b6f Subject: Re: [9fans] writing to /dev/$winid/addr Topicbox-Message-UUID: db85848e-ead8-11e9-9d60-3106f5b1d025 --001a11346bd2a3cd1e04f7d82b6f Content-Type: text/plain; charset=UTF-8 to clarify: it is an rc script, but the echo commands pump commands to a ksh through an acme win window. then he collects the output 2014-04-24 6:25 GMT+02:00 Alexander Kapshuk : > I'm sorry I confused you. In my second email I did mention that the > script was used to set a prompt and an acme window name when running > win and being logged onto UNIX. > > > On Thu, Apr 24, 2014 at 7:18 AM, Jacob Todd wrote: > > 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 > > >> 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 > >> > > >> > > > > --001a11346bd2a3cd1e04f7d82b6f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
to clarify:
it is an rc script, but the echo commands p= ump commands to a ksh through an acme win window.
then he collects the o= utput


2014-04-24 6:25 GMT+02:00 Alexander Kapshuk <alexander.kapshuk= @gmail.com>:
I'm sorry I confused you. In my second e= mail I did mention that the
script was used to set a prompt and an acme window name when running
win and being logged onto UNIX.


On Thu, Apr 24, 2014 at 7:18 AM, Jacob Todd <jaketodd422@gmail.com> wrote:
> 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
>> >> >>> {
>> >> >>> =C2=A0echo 'echo $SYSNAME!`uname -n`!$US= ER'
>> >> >>> =C2=A0echo 'PS1=3D'':; ''= ; PS2=3D'' '''
>> >> >>> } >/dev/$winid/body
>> >> > this is not valid rc.
>> >> >
>> >> > - erik
>> >> >
>> >> If it's not too much trouble, would you mind demonstr= ating 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 ba= sh,
>> > the script itself is reasonable rc. =C2=A0i was confused by a= n
>> > rc script emitting bash.
>> >
>> > - erik
>> >
>>
>


--001a11346bd2a3cd1e04f7d82b6f--