Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcc6!sdcc19!sdcc15!pa1343
From: pa1343@sdcc15.ucsd.edu (pa1343)
Newsgroups: comp.emacs
Subject: Re: MicroEmacs is dangerous!!
Message-ID: <1032@sdcc15.ucsd.edu>
Date: 4 Feb 89 04:02:09 GMT
References: <1028@sdcc15.ucsd.edu> <1713@cps3xx.UUCP>
Reply-To: pa1343@sdcc15.UUCP ()
Distribution: usa
Organization: University of California, San Diego
Lines: 19

Thanks for the suggestions.  What I think happened is that I forked a Shell
do Mess-Dos and cd'ed to the b: drive.  Then when I was back in emacs, I 
thought I was in c:/work/john and was instead on b:/.
I shouldn't have this problem on UNIX because I wouldn't edit a no-permission
file in the first place, and if I forked a shell in UNIX, it would not alter theEmacs directory location.  As to the file name problem.  Maybe it's not a bug, 
but it would be nice if the program were to ask for a filename if none existed
instead of giving an error message.  Then again, I am relatively new to emacs
and there may be a different write comand which does this.  If I find time 
between classes and uEmacs 3.9 compiles on Turbo C 1.5, I will think about
adding the two changes I suggested.  This is not certain though.
By the way, I have uEmacs 3.8 running on UNIX V.1.2 and I was wondering if
somebody may have ported the DOS .emacsrc to vt100 format.
Thanks again.

-- 
+------------------------------------------------------------------------------+
| John J. Marco -- pa1343@sdcc15.ucsd.edu | 
| ...!uunet!ucsd!sdcc15!pa1343		  |  
+------------------------------------------------------------------------------+