I'm seeking for good ideas how to robustly solve this problem.
I want to use cygwin as development environment on win for scripts using the systems Perl (ActiveState)
Especially I want to use Emacs there because some el-module provider don't want to fix problems with win-emacs.
The problem is that cygwin uses a unix stile paths while the win-perl expect win-style path
While using cygwin-emacs with cygwin-perl works calling win-perl from emacs fails because the path to the script can't be resolved.
Example: C:\tmp\tst_flymake.pl is /cygdrive/c/tmp/tst_flymake.pl in emacs.
One workaround is to use a wrapper to call win-perl which does the translation:
perl `cygpath -w /cygdrive/c/tmp/tst_flymake.pl`
But the warnings and errors emitted from win-perl will be windows-style again and emacs will fail to automatically jump to the correct line number.
I also tried to work with softlinks to establish a common compromise path-system, like linking C: to /cygdrive/c/ but with little success.
I am sure I can come out with a more or less stable solution with several layers of complicated translations, but would appreciate other ideas...
Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!
PS: before the emacs bashing starts, VIM users should face the same problem even more, because of more dependencies on a unix like environment.
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |