Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!news.cs.indiana.edu!msi.umn.edu!noc.MR.NET!gacvx2.gac.edu!gacvx2.gac.edu!scott Newsgroups: comp.sys.next Subject: Re: Laziness Message-ID: From: scott@erick.gac.edu (Scott Hess) Date: 6 May 91 13:55:22 References: <1991May1.142136.19889@sinix.UUCP> <660@rosie.NeXT.COM> Organization: Gustavus Adolphus College Nntp-Posting-Host: erick.gac.edu In-reply-to: jmynatt@ragnarok's message of 3 May 91 20:50:22 GMTLines: 55 In article <660@rosie.NeXT.COM> jmynatt@ragnarok (Jim Mynatt) writes: In article <1991May1.142136.19889@sinix.UUCP> dhg@sinix.UUCP (David Griffith) writes: > I'm lazy. That's why I like the file browser in Workspace Manager. I > hate typing "cd, ls, cd... etc". But here's the problem: you've > browsed your way down a deep directory path and decided you want to > do something unixy with the files you see. So you'd like to launch > a terminal window at the current directory. But you can't! It's so < rambling deleted > What Terminal (or Stuart) needs to do is provide a service which expects a 'thing' (document or directory) and then cd to the appropriate directory before initing or becoming key (if already running). Then the file viewer menu would provide something like Services>Terminal>cd to dir p (or something similar). Of course a new app could be written that provides the service then launches Terminal. Aren't services wonderful? Are you listening Scott Hess? Sure. I'm always listening. As pointed out in another post, the main problem is that Stuart really can't be sure who's running in the subshell. Say I drop a file into emacs while running GNUS. You'll be telling it something like "Give me a fried shoe with cheese on it, and force it down my throat". Well, not quite that, of course, but it will make about as much sense. Then again, that's up to the user. If the user can't handle it, that's the user's problem. The Workspace _still_ needs that ability. For instance, if you could copy the pathname of the current file from the Workspace, you could then move to (say) an Open Panel and paste the pathname in there, and it would then go to the path. I'm sure it could be used in other places (say you get a reference to a documentation file - copy and paste it into Workspace to get there). But, as I don't see NeXT jumping on this, I could probably manage to implement something of the sort eventually. Maybe not tomorrow, that's for certain :-). But, eventually . . . what is really needed is a subshell that understands/can work with Stuart. I'd love to have something that I could send special escape sequences and the like to that could then understand those as mouse-based selection, and cut, and copy, and paste. Then, this wouldn't be a problem at all. Would this be a possibility with tcsh? Anyone out there with a AT&T license that would be willing to work on something of the sort this summer? Or maybe it could just be added to Bash? Later, -- scott hess scott@gac.edu Independent NeXT Developer GAC Undergrad