Ar an ceathrú lá de mí Iúil, scríobh FKtPp:
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.
This is very odd, and is a use case we should fix. I’ve managed to reproduce
it, using your recipe, but not to fix the bug; I’ll try to keep working on
this.
The ?\ in eshell-mode has specical meaning!!!
Is there an error less value for the directory-sep-char in XEmacs
world?
I don’t know of one on Win32 native builds, outside of ?/ with Cygwin
support.
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta