X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7E120.D67E6933@onstor-exch02.onstor.net>; Fri, 17 Aug 2007 14:49:15 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Arrow keys in PROM
Date: Fri, 17 Aug 2007 14:49:14 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0507E034@onstor-exch02.onstor.net>
In-Reply-To: <20070817154555.5e997bb1@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Arrow keys in PROM
Thread-Index: AcfhIF7q+yl15NPzQBK7DZ0y4vvEtgAAFRFA
From: "Warren Gale" <warren.gale@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Ok, Thanks

Warren


-----Original Message-----
From: Andy Sharp=20
Sent: Friday, August 17, 2007 3:46 PM
To: Warren Gale
Subject: Re: Arrow keys in PROM

For such comments you can just say 'A', like thus:

if (rc =3D=3D 0x41) /* 'A' */

But just check it in as is.  Save that tidbit for next time.

Cheers and thanks,

a


On Fri, 17 Aug 2007 15:39:52 -0700 "Warren Gale"
<warren.gale@onstor.com> wrote:

> Look better ?
>=20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Friday, August 17, 2007 3:15 PM
> To: Warren Gale
> Subject: Re: Arrow keys in PROM
>=20
> On Fri, 17 Aug 2007 14:40:18 -0700 "Warren Gale"
> <warren.gale@onstor.com> wrote:
>=20
> > Yup, your right.
> >=20
> > I do have the newer clients out on MD and with editing it's fine.
> > I may as well go home when I start a build, especially for the ssc.
> >=20
> > I do have a backup copy of the local clients out on MD.
> > (using a version of your rsync cron job)
> > So I don't lose more that a day's worth..
> > But this will have the current changes and not associated=20
> > with the p4 client spec.
> >=20
> > What windoish stuff.. Me Not use windows for anything except e-mail,
> >  and vnc, and word, and excel, and uh, well I don't use it for P4.
> >=20
> >=20
> > If you're nice I'll set up a vnc session and you can look at the
> > changes there.
> > I'll even have a window open in the right environment waiting.
> >=20
> > Server  10.1.1.74:3.0
> > Passwd  warren
>=20
> ew.  weird.
>=20
> ok, code/sm-serio/serio-api.c
>=20
> line 250, lose the space after the left paren
> most programmers associate the octal 033 as escape, rather than the
> hex 0x1b
>=20
> lines 254, 258, 260, 262, 264, put a comment indicating what character
> that is.
>=20
>=20
> hey, what's with the
>=20
> }
>  else
>      return;
>=20
> so butt ugly...I'm just sayin'
>=20
>=20
>=20
> > Thanks,
> > Warren
> >=20
> > -----Original Message-----
> > From: Andy Sharp=20
> > Sent: Friday, August 17, 2007 1:58 PM
> > To: Warren Gale
> > Subject: Re: Arrow keys in PROM
> >=20
> > On Fri, 17 Aug 2007 13:29:46 -0700 "Warren Gale"
> > <warren.gale@onstor.com> wrote:
> >=20
> > > LOL... Yea.
> > >=20
> > > Ok, I did the "p4 change" and it gave me=20
> > > a change list number of  25070.
> > >=20
> > > Not sure if you are going to be able to see the files,
> > > since they are local on my desktop. (be for I went to MD)
> > > I still don't have a "homes" dir on MD.
> >=20
> > you should always have your p4 branch checked out to at
> > least /n/users or whatever the equivalent in winblows is.  that way
> > you at least benefit from snapshots and backups.
> >=20
> > i use two different clients.  one just for checking out and editing,
> > in my home dir; and one on a local disk for building and testing.  i
> > do all the edits on the home dir client, then run a little script
> > that copies the changes to the local dir directory, and do my
> > builds there. that way i never lose a change and it's easy to see
> > them from any computer, making reviews easy.  and my working tree
> > gets snapshot-ed and backed up and all that delicious stuff.  I
> > know it can be slow for you guys, but actually it shouldn't be.
> > Brian said you guys have a fast link now adays.  but editing is
> > usually a slow activity anyway, and copying the changed files takes
> > hardly any time even for largish source files over a slow link.
> >=20
> > > Maybe using "tkdiff" on the 2 files ??
> > > I'm not much of a p4 person either. (1st time I've used "p4
> > > change")
> > >=20
> > > I'm sure you can ssh into my desktop if you like .
> >=20
> > not if you don't have my home directory, and i don't know what your
> > desktop machine is.
> >=20
> > > P4 client is "warreng-bc-diag"
> > >=20
> > > Let me know.
> > >=20
> > > Thanks,
> > > Warren
> > >=20
> > > -----Original Message-----
> > > From: Andy Sharp=20
> > > Sent: Friday, August 17, 2007 12:58 PM
> > > To: Warren Gale
> > > Subject: Re: Arrow keys in PROM
> > >=20
> > > Well, I'll have to scrape my jaw off the dirty carpet here in
> > > Camphell.  I just tried the ctrl sequences, and sure enough they
> > > are there.
> > >=20
> > > Cheers,
> > >=20
> > > a
> > >=20
> > > On Fri, 17 Aug 2007 11:53:46 -0700 "Warren Gale"
> > > <warren.gale@onstor.com> wrote:
> > >=20
> > > > Andy,
> > > >=20
> > > >    Ok so I went and looked...  Well the history stuff is already
> > > > there.
> > > >=20
> > > >    CTRL P  previous  CTRL N next, CTRL B  back, and CTRL F
> > > > forward.
> > > >=20
> > > >    CTRL H back space and erase or backspace key.
> > > >
> > > > Anyway I added the escape sequences to look for the arrow keys.
> > > > So now that works also.
> > >=20
> > > So you're saying you can add escape sequence interpreters to just
> > > do the same thing, that's so awesome.  I take back all those bad
> > > things I said about PMON ~:^)
> > >=20
> > > > Please review the changes to the 2 files located at
> > > > "/n/users/warreng/bc_proms/code2review" which have the
> > > > originals and new files.  Looks like I'll be able to get it into
> > > > this next release :-)
> > >=20
> > > Use the 'p4 change' command to capture the changed files into a
> > > change list (without checking them in).  Then send me the
> > > changelist number.
> > >=20
> > > > =20
> > > >=20
> > > > Thanks,
> > > >=20
> > > > Warren
> > > >=20
> > > > =20
> > > >=20
> > > > PS I'm re-visiting the memory allocation stuff again.
> > > >=20
> > > > =20
> > > >=20
