Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!geac!maccs!cs4g6ag From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) Newsgroups: comp.sys.ibm.pc Subject: Re: Need input for future DOS release Keywords: future DOS release Message-ID: <260E5E5A.5404@maccs.dcss.mcmaster.ca> Date: 26 Mar 90 18:24:26 GMT References: <53686@microsoft.UUCP> <2017@clyde.concordia.ca> <1990Mar22.202023.25752@seri.gov> <246@edpmgt.UUCP> Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) Organization: McMaster University, Hamilton, Ontario Lines: 27 In article <246@edpmgt.UUCP> gpitcher@edpmgt.UUCP (Glenn Pitcher) writes: $Couldn't the shell be altered to intercept those directory requests and $remap the characters before the actual open (or whatever) command is issued? If you alter the shell, this would only affect commands issued from the shell. Pathnames entered within applications would still require the use of the \ regardless of what you set. Changing the path separator, however, could be implemented as a DOS call so that changes would be universal. $> >3) Aliases and some sort of command history (currently provided by third $> > parties, of course, but there's no standard mechanism). $We have these capabilities on our PC's and I tell 'ya, I wonder how I ever $worked without them. Indeed! I never knew what I was missing until I started using Unix a fair bit. I now find COMMAND.COM so confining, compared to tcsh, that I've been driven to write my own command shell (yes, I know there are plenty available ... but I like rolling my own programs; and don't write me asking for a copy, as it's far from complete). -- Stephen M. Dunn cs4g6ag@maccs.dcss.mcmaster.ca = "\nI'm only an undergraduate!!!\n"; **************************************************************************** "So sorry, I never meant to break your heart ... but you broke mine."