[7825] in Athena Bugs
Re: 7.3 System Release Notes (24 Jul 91, 12:11)
daemon@ATHENA.MIT.EDU (lwvanels@ATHENA.MIT.EDU)
Fri Jul 26 16:35:14 1991
From: lwvanels@ATHENA.MIT.EDU
Date: Fri, 26 Jul 91 16:35:01 -0400
To: ckclark@ATHENA.MIT.EDU
Cc: dryfoo@ATHENA.MIT.EDU, testers@MIT.EDU
In-Reply-To: [7824]
Reply-To: lwvanels@MIT.EDU
dryfoo> 1) Section 2.3 -- "The following is a list of files that are commonly
dryfoo> reference by absolute pathnames..."
dryfoo> The list includes /usr/athena/emacs, should it also
dryfoo> include emacsclient ?
ckclark> (I *knew* it, Richard. I *told* you somenone point out the
ckclark> inconsistency in having a compatibility symlink for emacs but not for
ckclark> emacsclient!)
ckclark>
ckclark> At the time we decided to provid a compatibility symlink for emacs,
ckclark> the was only about two other programs which we said we needed
ckclark> symlinks for, and the goal was to keep these to a minimum. Since
ckclark> then the philosophy has changed so that it seems we provide
ckclark> symlinks from everywhere to everywhere else. It would be foolish
ckclark> to think that adding one more for emacsclient would hurt. The
ckclark> argument for not including it was, I quote,
ckclark> ``Anyone who references emacsclient created that reference themselves
ckclark> and knows how to fix it.''
The compatability symlink for emacsclient does exist on all of the
platforms, and has since the release first went out.
The point Gary was making was whether to list emacsclient as one of the
files that people commonly reference by an absolute pathname; that's purely
an issue of what we put in the release notes; I'll add that to the next
version of the system release notes.
-Lucien
