Well that someone was me. The short version is that I completely dropped the ball on this and after volunteering to look at porting emacsclient to Windows never had the time to actually do it. I updated gnuclient at the time and then ran out of time when looking at all of the changes in the new emacsclient.
Many moons ago when I looked at emacsclient it was a C client and a C server in a very similar pattern to gnuclient, now it's a lisp server wrapping core emacs functionality and a C client. Whilst I'm probably quite capable of dealing with the C code, I'm a complete neophyte when it comes to lisp and so part of my problem is not really having the time to learn enough lisp to add the support needed to get an acceptable working version. I feel pretty bad about this, but can't really kid myself that I'll suddenly get or make time. Guy David Kastrup wrote: >Lennart Borgman <[EMAIL PROTECTED]> writes: > > > >>I just want to tell that w32 still have no working >>emacsclient/server. Gnuserver/client is a workaround, but as far as >>I understand this can currently not be part of Emacs because of >>license problems. >> >>This sums up (in my opinion) that we can not distribute a fully >>working Emacs on w32. What should we do about this? >> >> > >Well, obviously port emacsclient. Somebody already took a look of it >IIRC, but nothing has been heard of it since. > >And with any other stuff: if nobody does the work, it will not be >done. As far as I remember, this is a "simple" nobody-did-it-yet >case. It is not part of any strategy or something. > > > _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel
