Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <00cf01c223aa$d28db530$75247bd5@Minotaur> From: "Dr Francis J. Wright" To: "Matt Swift" Cc: , References: <000001c222e2$53bcf180$65ff3018 AT swift DOT 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 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 From: "Matt Swift" To: Cc: ; 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/