home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!portal!lll-winken!elroy.jpl.nasa.gov!swrinde!gatech!news.byu.edu!news.mtholyoke.edu!nic.umass.edu!amherst!amherst.edu!mkrogers
- From: mkrogers@amherst.edu
- Newsgroups: comp.sys.next.programmer
- Subject: Re: Command-line apps now harder (Can you pass arguments?)
- Message-ID: <1992Sep6.100035.1@amherst.edu>
- Date: 6 Sep 92 14:00:35 GMT
- References: <1992Sep2.141110.19865@pencom.com> <1992Sep4.194248.568@leland.Stanford.EDU> <60105@mimsy.umd.edu>
- Sender: usenet@amhux2.amherst.edu (USENET News System)
- Organization: Amherst College, Amherst Mass.
- Lines: 20
- Nntp-Posting-Host: amh.amherst.edu
-
- In article <60105@mimsy.umd.edu>, alex@cs.umd.edu (Alex Blakemore) writes:
- > In article <1992Sep4.194248.568@leland.Stanford.EDU> cooldude@elaine49.stanford.edu writes:
- >> How can you also pass arguments to the application being opened. e.g, open
- >> bar.app and have it open a file called "foo".
- >
- > open foo.x
- >
- > will open the file foo.x using whatever app you've selected
- > as the default app for files with suffix x, just as if
- > you'ld double clicked it in a Workspace file viewer.
-
- Try "open -a bar foo". You can leave off the .app extension of bar
- if it has one.
-
- > no extension - and you'll get the default app - probably Edit.
-
- This is what happens to me. I don't know if there's a default
- you can dwrite to change this.
-
- -mike rogers
-