IMHO we should handle the cygwin/native-window-path topic as other poackages like printing.el do... Take a look in printing.el To see how to deal with the problem that external programs do not understand cygwin-paths (and java is nothing else than an external program)
Ciao Klaus Léopold Bailly wrote: > Ed Mooney <Ed.Mooney <at> Sun.COM> writes: > >> >> Try setting jde-cygwin-path-converter to >> jde-cygwin-path-converter-cygpath: >> >> M-x customize-variable RET jde-cygwin-path-converter >> >> FSF emacs, XEmacs and NT/Emacs are the only versions the user's >> guide[1] claims the JDEE supports. [1] >> http://jdee.sunsite.dk/jdedoc/html/jde-ug/jde-ug-content.html#Intro > > Yes, but there's a way to support cygwin Emacs too. > > The problem with the official release of jdee is that it does not > make the difference between paths for java and paths for emacs. They > are computed the same way by jde-normalize-path. > > Such a treatment is not suitable for hybrid environment like cygwin > Emacs : emacs wants Unix style paths whereas java wants Windows style > paths. > > My proposed patch (see last thread) split jde-normalize-path in two > functions, one (with cygwin) for java paths and the other (without > cygwin) for emacs paths. > > Unfortunately this is not compatible with NT/Emacs, that always wants > Windows style paths... > > But I'm sure we could find a unified solution. > >> >> Felix Dorner wrote: >>> Hi, >>> >>> motivated by the ongoing cygwin thread I installed: cygwin, cygwin >>> emacs, jde. The jde-bsh-run command now involves: >>> > [...] >>> The java executable obviously cannot deal with those unix style >>> pathnames. I did not find a real "guide" on setting up the jde with >>> cygwin emacs, so I hope someone can help me here.
