X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,SARE_MSGID_LONG45,TW_YG,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <83sk66gqb7 DOT fsf AT garydjones DOT name> <4BE1C039 DOT 8030107 AT gmail DOT com> Date: Wed, 5 May 2010 13:46:29 -0600 Message-ID: Subject: Re: cygpath from emacs From: Steven Collins To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Not sure why it line wrapped the second comment when I sent this. The part reading "using DOS style paths." is part of the comment line above it. On Wed, May 5, 2010 at 1:42 PM, Steven Collins wrot= e: > Amazingly enough I solved this problem for myself just yesterday. > > ;; Add to your .emacs file. > ;; Handle locating files containing errors for compilers that report > using DOS style paths. > (when (eq system-type 'cygwin) > =A0 (require 'compile) > =A0 (setq compilation-parse-errors-filename-function > =A0=A0 =A0'(lambda (path) > =A0=A0 =A0=A0=A0 (replace-regexp-in-string "\n" "" > =A0=A0 =A0=A0=A0=A0=A0=A0 (shell-command-to-string (concat "cygpath --uni= x '" path "'")))))) > > On Wed, May 5, 2010 at 1:00 PM, Dave Korn > wrote: >> >> On 05/05/2010 19:24, Gary wrote: >> > I often find myself running a piece of software from within emacs that >> > expects, and spits out, Windows-style paths ("C:\..."). Handling sendi= ng >> > it Windows paths based on the Cygwin ones is fine, I just use a >> > script. >> > >> > Of course, the tool returning Windows paths is a PITA, because it means >> > I can't do M-x next-error :( Is there a solution, a way to "capture >> > them" and transform them before they end up in the emacs buffer, maybe? >> > I feel I should be able to work this out myself, but my brain refuses = to >> > bend around it :( >> >> =A0So you have a script that transforms the paths on the command-line and >> launches the app... why doesn't the script /also/ capture the output and >> transform it back? >> >> =A0 =A0cheers, >> =A0 =A0 =A0DaveK >> >> -- >> Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html >> FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/ >> Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html >> Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple >> > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple