[mew-int 2209] Re: make client process failed, connection refused
CHENG Gao
chenggao at example.com
Thu Sep 21 18:35:14 JST 2006
*On Thu, 21 Sep 2006 15:06:22 +0900 (JST)
* Kazu Yamamoto (山本和彦) <kazu at example.com> climbed out of the dark hell and cried out:
>> I use Emacs23 (emacs-unicode-2 branch) build with mingw, and as
>> instructed in readme, I did addpm, and then run mew from cmd shell,
>> and what I got is error: Any Emacsen cannot found. <- Obviously a typo
>> here. Has Emacs been installed correctly?
>
> Uhhm. I have never tried the Unicode branch.
>
> I'm using both NTEmacs and Meadow on Windows XP and they runs Mew very
> well.
Yamamoto-san, I found the problem and solution.
I checked Windoes Registry and found there is no reg for Emacs. It's the
same case for Emacs 22 and Emacs 23 (all built with recent cvs source).
I checked mew.c and know it depends on reg value of emacs_dir.
I checked addpm.c code, and found its usage is
usage: addpm [-q] [emacs_path [icon_path]]
so it means emacs_path and icon_path are both optional.
But seems it's not true.
Installation of cvs emacs (head and unicode-2 branch) does run
addpm.exe. But it only creates a shortcut to runemacs.exe, and no
registry item is added.
So in cmd shell, I run
addpm c:/emacs
and it added all registry items, and mew installation worked.
So seems it's a bug with Emacs code.
At last I have two suggestions:
1. Change line 47-48 of 00readme.w32 from
C:\> cd emacs-21.3\
C:\emacs-21.3\bin>addpm
to
C:\> cd emacs-21.3\
C:\emacs-21.3\bin>addpm C:\emacs-21.3
or maybe better to:
C:\> cd emacs
C:\emacs\bin>addpm c:\emacs
since many users use cvs emacs or emacs-unicode-2.
2. Change mew.c to use emacs_dir environment var before registry item.
Seems mew.c is only dependent on windows registry.
Now emacs can run well without any registry entry set. If mew can run
well with environment var, it will be a cleaner way.
I'll look into mew configuration problem and report back.
Thanks for your help.
More information about the Mew-int
mailing list