home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!news.u.washington.edu!ns1.nodak.edu!plains.NoDak.edu!bohlman
- From: bohlman@plains.NoDak.edu (Daemon)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: AUSH command/file name completion
- Keywords: AUSH completion
- Message-ID: <BxGI21.FuI@ns1.nodak.edu>
- Date: 9 Nov 92 16:06:00 GMT
- Article-I.D.: ns1.BxGI21.FuI
- References: <Scott.0dv0@ami.spacecoast.org> <1992Nov9.151700.8799@mlb.semi.harris.com>
- Sender: usenet@ns1.nodak.edu (News login)
- Organization: North Dakota Higher Education Computing Network
- Lines: 26
- Nntp-Posting-Host: plains.nodak.edu
-
- In article <1992Nov9.151700.8799@mlb.semi.harris.com> mwills@x102a.ess.harris.com (M. Scott Wills) writes:
- >
- >Now I wonder why a window specification on the NewAUSH command line
- >isn't working for me. "NewAUSH" by itself opens a large AUSH window,
- >but "NewAUSH CON:10/10/100/100/AUSH/CLOSE" does nothing. A disk
- >access takes place, but no error messages, and no AUSH window appear.
- >
- >Scott
- >--
- Unfortunately, the docs leave out that the format for NewAUSH is:
-
- NewAUSH [FROM file] [WINDOW CON:10/10/100/100/AUSH/CLOSE]
-
- The FROM variable is if you have a file as well as .aushrc that you want to
- execute.
- The WINDOW keyword tells it that a CON: specification follows.
- As of 1.55, NewAUSH (for 2.0) spits out it's usage format ala 2.0 if you don't
- do it correctly.
- Otherwise, I would have never figured this out...
-
- 1.55 can be found on amiga.physik.unizh.ch in /amiga/util/shells/, I believe..
- --
- `I think, therefore I am. Of course, that makes you a figment of my imagination'
- My opinions, of course, do not reflect the opinions of any organization I have
- ever been associated with in any way, shape, or form and they are very grateful.
- bohlman@plains.NoDak.edu bohlmand@milo.NoDak.edu
-