Hello Sabine, Thank you for following up. That version is fairly out of date. I would definitely recommend installing one of the InnoSetup kits available from ftp://ftp.xemacs.org/pub/xemacs/windows/testing. There is a 21.5-b25 kit there now, and sometime today or tomorrow there will be a 21.5-b26 kit there to replace it. Regards, Vin -- Whoever you are, no matter how lonely, the world offers itself to your imagination, calls to you like the wild geese, harsh and exciting-- over and over announcing your place in the family of things. Mary Oliver

Hello Adrian, am 01.04.2006 schriebst Du: I use XEmacs 21.4.13 since Sept. 2002, especially for Gnus. Both versions create a problem with gnuserv: Debugger entered--Lisp error: (file-error "Searching for program" "No such file or directory" "gnuserv") start-process-internal("gnuserv" nil "gnuserv") apply(start-process-internal "gnuserv" nil "gnuserv" nil) start-process("gnuserv" nil "gnuserv") gnuserv-start-1(nil) gnuserv-start(nil) call-interactively(gnuserv-start) command-execute(gnuserv-start t) execute-extended-command(nil) call-interactively(execute-extended-command) [...] OK I have set the default-directory in my init.el now. [...] Gruesse Sabine

On 4/1/06, Adrian Aichner <adrian(a)xemacs.org&gt; wrote: You are right, of course. I have spent too much of my life worrying about this kind of nonsense. I replaced the space characters with underscores - please see my recent kit announcements posted to xemacs-beta. As far as the 'Start in' field in the shortcut - that is easily customized and I don't necessarily think it makes a lot of sense to set it in the setup kit. I'll think about this and see if anything worthwhile comes to mind. - Vin -- Whoever you are, no matter how lonely, the world offers itself to your imagination, calls to you like the wild geese, harsh and exciting-- over and over announcing your place in the family of things. Mary Oliver

On 4/2/06, Sabine 'Sani' Schulz <nemo(a)schnuerpel.net&gt; wrote: In the newest setup kits, I have modified the 'Start in' field to be %USERPROFILE%\"My Documents". I'm not sure what I think about this change. - Vin

On 4/4/06, Adrian Aichner <adrian(a)xemacs.org&gt; wrote: Well, this is the result of expanding a macro in InnoSetup - {userdoc}. I think those macros are customized to the locale, but rather than speculating, perhaps someone would like to try one of the new setup kits: ftp://ftp.xemacs.org/pub/xemacs/windows/testing/XEmacs_Setup_21.4.19-5.exe and ftp://ftp.xemacs.org/pub/xemacs/windows/testing/XEmacs_Setup_21.5-b26-2.exe in a non-English locale? As I wrote, I'm fairly ambivalent about this particular change and would be happy to leave the 'Start in' field blank in the shortcuts. Please let me know what you think and also what the results of your tests are. - Vin -- Whoever you are, no matter how lonely, the world offers itself to your imagination, calls to you like the wild geese, harsh and exciting-- over and over announcing your place in the family of things. Mary Oliver

I have this same problem. I've changed savehist-coding-system to 'raw-text, which seems to work ok, but will probably bite me if I ever switch to using a mule-enabled emacs. Robert

vin> Patches are certainly welcome to address this problem. Untested, posted for discussion. This has the advantage of picking up UTF-8 if Mule-UCS is already loaded, which is normally done in init.el. We could try a `require' to make sure. Index: savehist.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/savehist.el,v retrieving revision 1.4 diff -u -r1.4 savehist.el --- savehist.el 14 Nov 2005 07:05:54 -0000 1.4 +++ savehist.el 7 Apr 2006 15:54:27 -0000 ＠＠ -135,12 +135,17 ＠＠ ;; This should be capable of representing characters used by Emacs. ;; We prefer UTF-8 over ISO 2022 because it is well-known outside -;; Mule. XEmacs prir to 21.5 had UTF-8 provided by an external +;; Mule. XEmacs prior to 21.5 had UTF-8 provided by an external ;; package which may not be loaded, which is why we check for version. -(defvar savehist-coding-system (if (and (featurep 'xemacs) - (<= emacs-major-version 21) - (< emacs-minor-version 5)) - 'iso-2022-8 'utf-8) +(defvar savehist-coding-system (if (featurep 'xemacs) + (if (featurep 'mule) + (or (find-coding-system 'utf-8) + (find-coding-system 'iso-2022-8) + ;; #### eh?! should error? + (find-coding-system 'binary)) + 'binary) + ;; assume Emacs 20, at least + 'utf-8)) "The coding system savehist uses for saving the minibuffer history. Changing this value while Emacs is running is supported, but considered unwise, unless you know what you are doing.") -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

Adrian Aichner wrote: AFAICT, the relevant registry key is: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Personal There are a whole bunch of these keys under "Shell Folders", so I would guess that those are all of the per-user directories which are meaningful to the shell. -- Glynn Clements <glynn(a)gclements.plus.com&gt;