Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <00cf01c223aa$d28db530$75247bd5@Minotaur>
From: "Dr Francis J. Wright" <F.J.Wright@qmul.ac.uk>
To: "Matt Swift" <swift@alum.mit.edu>
Cc: <cygwin@cygwin.com>, <help-emacs-windows@gnu.org>
References: <000001c222e2$53bcf180$65ff3018@swift.xxx>
Subject: Re: new-style Cygwin symlinks, NTEmacs' dired mode, and ls-lisp.el
Date: Thu, 4 Jul 2002 23:28:04 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

From: "Matt Swift" <swift@alum.mit.edu>
To: <F.J.Wright@maths.qmw.ac.uk>
Cc: <cygwin@cygwin.com>; <ntemacs-users@cs.washington.edu>
Sent: Wednesday, July 03, 2002 11:38 PM
Subject: new-style Cygwin symlinks, NTEmacs' dired mode, and ls-lisp.el


> Maybe this has already been done, but I have hacked ls-lisp.el so that
> it understands the new-style Cygwin symlinks (which seem like Windows
> shortcuts to Windows, but not to ls-lisp.el).  I have had to
> reverse-engineer and hack without a full understanding of shortcut
> headers.  Putting the following code in a startup .el file works for me
> with EmacsNT 20.7.  It causes Emacs to do two things after loading
> dired: load ls-lisp, then redefine one function defined in ls-lisp.el.
> My modifications are commented and labeled with "MSS".   I am sending
> this email because I think others may be interested in this code.
> Someone with full knowledge could make this code more efficient and
> address the question of robustness with odd file names and unusual
> symlink headers.

I also have some revisions to ls-lisp in progress, one of which is support
for Cygwin-generated shortcut files.  I want to test it a bit more before I
release it.  However, I will only support NT Emacs 21, and my new code will
not work with earlier versions.

Francis


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/