Lennart: "Gnuclient just expands filenames before sending them to gnuserv. Filenames must then be single arguments to gnuclient. Actually that is not very good for the integration with the OS."
So it could be CMD's processing of text in the doskey macro that translates the \n into control chars. "However there will soon be a successor to gnuclient/gnuserv which is called emacsclient/server. (Unfortunately no one has yet got this working for MS Windows). BTW - should not this discussion by on the MS Windows port list?" Sounds reasonable. The emacsclient in the CVS version doesn't seem to have much functionality, compared to gnuclient. What's the benefit of emacsclient over gnuclient? That it's officially part of GNU Emacs? What's the problem with emacsclient on Windows anyway? Doesn't Windows support Berkeley sockets? Rob
