Hi Klaus,
Its been a while since you wrote the original message, but a late
answer is better the none :-) I´m using the Cygwin Version of XEmacs
21.4.5 under Win2K (while i have chosen the first by myself, the
second has been chosen for me :-|), so I think I can answer some of
your questions.
Berndl, Klaus wrote:
> - Which port should i use: native win32 oder cygwin-build? I´m a
heavy
> cygwin-user and i do most of my tasks from bash command-line:
Use the cygwin port. It just has a better feel about it. I also
recommend installing cygwin to the root of your harddrive. This
makes Windows almost bearable.
> + If i use the cygwin-port (which uses cygwin-path-style i
suppose), is it
> still possible opening files from the Windows-Explorer with
XEmacs (by
> defining an association with a certain file-type and by
drag&Drop?
yes
> + Allows the cygwin-port also windows-path-styles?
yes
> + Are there performance differences between the native and the
cygwin-build
> XEmacs?
none (means: none noticeable during normal work. I haven't done
benchmarks :-)
> + Are there stability differences between native and cygwin
version?
> + In general: Has the native port advantages compared with the
cygwin-port
> and if yes which ones?
I dont know. ( the only crashes I had so far were related to xml-mode
(probably while loading and initializing xslt-process-2.1)
> + Is with the cygwin-port bash the default shell?
no, it´s /bin/sh, but you can easily set bash with the following lines:
(setq shell-file-name "bash")
(setq shell-command-switch "-c")
(setq explicit-shell-file-name shell-file-name)
(setenv "SHELL" shell-file-name)
(setq explicit-sh-args '("-login" "-i"))
> + is it possible to call non-cygwin programs from within
> XEmacs with all the aspects concerning the path-style submit
to the
> program (e.g. win32-program need normally its path-arguments in
> windows-style).
yes, but you have the same issues as with other cygwin programs, while
PATH etc will be converted for you, you need to convert commandline
args explicitly or specify them in windows style. If you use bash as
shell you have to escape bashslashes of course. When calling java,
JDE does the work for you.
> + Does the native port understand cygwin-path-style...
It does, but I was getting ugly mixed style pathes with filename
completion, last time I checked.
> + Does JDE working better with the cygwin or the native port.
I haven`t tried JDE with the native port, so I can not comment on
this one, but you must be prepared to solve some minor issues with each
new JDE beta regarding path and filename conversion. 2.2.9beta5 did
break the beanshell eval on cygwin, this is what it solved for me:
--- ../../orig/jde-2.2.9beta5/lisp/jde.el Thu Nov 8 12:38:06 2001
+++ jde.el Wed Nov 14 11:58:14 2001
@@ -1062,7 +1062,8 @@
(nth index2 (match-data)))
":/"
(substring new-path (match-end 0)))))
- (substitute ?\\ ?\/ new-path))
+;; (substitute ?\\ ?\/ new-path)
+ )
path))))
(defcustom jde-cygwin-path-converter
'(jde-cygwin-path-converter-internal)
@@ -2193,9 +2194,8 @@
(defun jde-create-prj-values-str ()
(let ((directory-sep-char ?/)) ;; Override NT/XEmacs setting
- (format "jde.util.JdeUtilities.setProjectValues(\"%s\", %s);"
- jde-current-project
- (jde-build-path-arg nil jde-global-classpath t))))
+ (format "jde.util.JdeUtilities.setProjectValues(\"%s\", \"%s\");"
+ jde-current-project jde-global-classpath)))
(defun jde-jeval (java-statement &optional eval-return)
--
Ole Arndt http://www.tivano.de/
Your mouse has moved. Windows 2000 must be restarted for
the change to take effect. Reboot now?
