Re: [Bug: 21.5-b28] command-syntax-error (info-mode #'call-process-internal) vs. eshell (windows platform) path completation

It is a bit complex to reproduce this: 1) you have to use a native widnows build. 2) (setq directory-sep-char ?/) in your init.el 3) make gzip avaiable avaiable in your path 4) have gziped info manual in your info dir (I have cygwin ones). 5) try view a info node inside the gziped manual. you will got an error of no such info node error, further edebug show that it was because the #'call-process-internal got an "the syntax of the command is not correct" error[1], and result an empty *info* buffer. remove/comment-out the (setq directory-sep-char ?/) in init.el will resolve this error. But it will cause the eshell path completation complete an extra ?\ character[2]. when you type enter after that ?\ character, you'll got an directory not found error.

The ?\ in eshell-mode has specical meaning!!! Is there an error less value for the directory-sep-char in XEmacs world?