[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#4902: 23.1; directory-abbrev-alist is not handled early enough

From: David J. Biesack
Subject: bug#4902: 23.1; directory-abbrev-alist is not handled early enough
Date: Wed, 11 Nov 2009 15:57:03 -0500

> Date: Wed, 11 Nov 2009 20:35:23 +0200
> From: Eli Zaretskii <address@hidden>
> CC: <address@hidden>, <address@hidden>
> > Date: Wed, 11 Nov 2009 07:47:36 -0500
> > From: "David J. Biesack" <address@hidden>
> > CC: address@hidden, address@hidden
> > 
> > > About the only thing I can suggest is to run with the drive u: being
> > > the current drive.  Then /foo/bar on both Windows and Unix will refer
> > > to the same place, and you don't need any mapping at all.
> > 
> > that still won't work for Unix network paths that are not mapped in U:
> What prevents you from mapping them all to U: ?

There are dozens if not hundreds of them.  U: is mapped (by our IT department)
to our Unix login (Unix/User, hence U:) directory. 
Other things are not our login directories and it would be wrong to map them 
Similarly, we would not want to require each user to duplicate a bunch of
drive mappings on their desktops (or symlinks in their unix login directories)
Thus, We use UNC paths for these other locations.
For example, I would access your login at \\sashq\root\u\eliz 
whereas it would be U:\ for your, and you would see mine
at \\sashq\root\u\sasdjb

This has all evolved over a period of years...

David J. Biesack, SAS
SAS Campus Dr. Cary, NC 27513
www.sas.com    (919) 531-7771

reply via email to

[Prev in Thread] Current Thread [Next in Thread]