🚀 go-pugleaf

stef@zweig.SUN (Stephane Payrard) writes:
< THIS IS NOT REALLY A BUG REPORT BUT A RFE
...
< lrwxrwxrwx  1 root           12 Apr 16 18:45 /usr/spool ->../var/spool

< Suppose I have a file which "canonic" (ie: without symbolic links)
< pathanme is /usr/spool/X/log.  If I sucessessively do
< M-xfind-file/usr/spool/X/log and M-xfind-file/var/spool/X/log, I end
< up with two buffers where I really want one: in the 2 cases, I
< reference the same file so I would have expected gnu-emacs smart enough to
< figure out that there is only one file involved.

On the other hand, there is a hack to allow compiling code for more
than one machine from a single set of sources, involving setting up a
tree of simlinks to the *files*.  The problem with the above
suggestion is that if I edit the file /d4m/utl/sun3os3/src/foo/bar/baz.c
(which is a symlink to /d4m/utl/shared/src/foo/bar/baz.c), I don't
want my changes saved back *through* the symlink, and I want
/d4m/utl/sun4os4/src/foo/bar/baz.c to come up as a *different* buffer,
even though it is also a symlink to the same real file.

The difference seems to be that in Stephane's case, one of the
directory path elements is a symlink (symlink-to-dir), whereas in mine
the symlink is to the file itself.  Both of these cases should
probably be handled seperately (and be seperately programmable).

		-- Paul Placeway <pplaceway@bbn.com>