Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!spool.mu.edu!agate!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: stty -g output ...
Message-ID: <14500@dog.ee.lbl.gov>
Date: 19 Jun 91 19:59:44 GMT
References: <27243@adm.brl.mil>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 24
X-Local-Date: Wed, 19 Jun 91 12:59:44 PDT

In article <27243@adm.brl.mil> Michael Panosh - Unix Education@relay.cs.net
writes:
>... there is no *good* reason the stty command should not output a
>recognisable, STANDARD format ...

For -g, there *is* such a reason; for others, the format should be
described in the manuals, so that you can read it.

Remember, -g is, in effect, `save the current state'.  In
implementation A, the current state is `erase, kill, and mode'; in
implementation B, it is `ispeed, ospeed, lflags, iflags, oflags,
cflags, discard, dsusp, eof, eol, eol2, erase, intr, kill, lnext, quit,
reprint, start, status, stop, susp, werase'.  Tomorrow, implementation
C will add `swtch', implementation D will add 42 incompatible options,
and implementation E will do something completely different.  When they
change, -g output will change to encode the new state.

Incidentally, the `g format of the day' on implementation B is:
gfmt1:cflag=5a00:iflag=2b22:lflag=5cb:oflag=7:discard=f:dsusp=19:eof=4:\
eol=ff:eol2=ff:erase=8:intr=3:kill=18:lnext=16:quit=1c:reprint=12:start=11:\
status=14:stop=13:susp=1a:werase=17:ispeed=9600:ospeed=9600
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov