cygpath from emacs

[Steven Collins]

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)
  (require 'compile)
  (setq compilation-parse-errors-filename-function
    '(lambda (path)
       (replace-regexp-in-string "\n" ""
          (shell-command-to-string (concat "cygpath --unix '" path "'"))))))

On Wed, May 5, 2010 at 1:00 PM, Dave Korn
<dave.korn.cygwin@googlemail.com> 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 sending
> > 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 :(
>
>  So 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?
>
>    cheers,
>      DaveK
>
> --
> 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
>

--
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