unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "David J. Biesack" <David.Biesack@sas.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 4902@emacsbugs.donarmstrong.com
Subject: bug#4902: 23.1; directory-abbrev-alist is not handled early enough
Date: Wed, 11 Nov 2009 15:57:03 -0500	[thread overview]
Message-ID: <ytbws1wye3k.fsf@sas.com> (raw)
In-Reply-To: <83pr7ooqok.fsf@gnu.org> (message from Eli Zaretskii on Wed, 11 Nov 2009 20:35:23 +0200)

> Date: Wed, 11 Nov 2009 20:35:23 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> CC: <4902@emacsbugs.donarmstrong.com>, <monnier@IRO.UMontreal.CA>
> 
> > Date: Wed, 11 Nov 2009 07:47:36 -0500
> > From: "David J. Biesack" <David.Biesack@sas.com>
> > CC: 4902@emacsbugs.donarmstrong.com, monnier@IRO.UMontreal.CA
> > 
> > > 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 there.
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	other threads:[~2009-11-11 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 17:54 bug#4902: 23.1; directory-abbrev-alist is not handled early enough David Biesack
2009-11-10 19:35 ` Stefan Monnier
2009-11-10 19:52   ` David J. Biesack
2009-11-10 21:02     ` Stefan Monnier
2009-11-10 21:29       ` David J. Biesack
2009-11-11  4:11         ` Eli Zaretskii
2009-11-11 12:47           ` David J. Biesack
2009-11-11 18:35             ` Eli Zaretskii
2009-11-11 20:57               ` David J. Biesack [this message]
2009-11-11 14:52         ` Stefan Monnier
2009-11-11 19:41           ` David J. Biesack
2019-11-02  5:21           ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ytbws1wye3k.fsf@sas.com \
    --to=david.biesack@sas.com \
    --cc=4902@emacsbugs.donarmstrong.com \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).