[1337] in Athena Bugs
(VS2000) Version 6.0R: /usr/athena/emacsclient solution
daemon@ATHENA.MIT.EDU (jik@ATHENA.MIT.EDU)
Tue Nov 8 11:45:59 1988
From: <jik@ATHENA.MIT.EDU>
Date: Tue, 8 Nov 88 11:45:15 EST
To: wesommer@ATHENA.MIT.EDU
Cc: bugs@ATHENA.MIT.EDU
In-Reply-To: Bill Sommerfeld's message of Tue, 8 Nov 88 11:39:52 EST <8811081639.AA22590@BINKLEY.MIT.EDU>
Perhaps it can divine the name of the directory by reading pigeon
entrails, but it _can't_ get the information through the UNIX kernel.
Point taken.
2) emacsclient should not simply abort if it can't open the parent
directory. It should signal an intelligent error. If it had said,
"can't open .." I would immediately have realized that I was in a
problem directory and moved back into my homedir. Of course, this
shouldn't be a problem at all because of (1) above, but we do what we
can, right...
Blame the FSF.
This is not an appropriate answer, I think. The bug should be *fixed*
in our emacs sources and sent to the FSF for fixing in their sources.
We shouldn't just say, "Blame the FSF," and pretend the bug will go
away.
jik
