Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!adobe!heaven!heaven.woodside.ca.us From: glenn@heaven.woodside.ca.us (Glenn Reid) Newsgroups: comp.sys.next Subject: Re: /LocalApps and NXPortFromName Keywords: open -a Edit Message-ID: <460@heaven.woodside.ca.us> Date: 14 Mar 91 17:18:44 GMT References: Sender: glenn@heaven.woodside.ca.us Lines: 24 In article scott@erick.gac.edu (Scott Hess) writes: > At least in 1.0, it seems there was a named socket used by Edit to allow > openfile to work. It was located down in ye olde /tmp directory. I > don't see it there right now, though, so maybe it's changed. But, openfile's > man page specifically states that it will not open the file unless Edit > is running. There is a better way to open files with Edit. It doesn't even require that Edit be running. There is a new -a switch added to the "open" command in 2.0 that lets you explicitly supply the name of the application in which to open the file (rather than letting the workspace determine it based on the file extension). For example, to open a PostScript file in Edit (instead of the default Preview), do this: localhost> open -a Edit myfile.ps If you don't like to type, you could always alias "openfile" to "open -a Edit" and you get the best of both worlds, and no more of those "Can't connect to Edit" messages. Glenn Reid RightBrain Software glenn@heaven.woodside.ca.us NeXT/PostScript developers ..{adobe,next}!heaven!glenn 415-851-1785 (fax 851-1470)