help-emacs-windows
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [h-e-w] Problems with gnuserv in XP


From: Guy Gascoigne-Piggford
Subject: RE: [h-e-w] Problems with gnuserv in XP
Date: Fri, 20 Sep 2002 14:44:12 -0700

Well here are a few of things that may help you both sort out what's
happening.  BTW I use emacs and gnuclient on XP all of the time so I know
what it can work.

1) After running emacs, open the task manager and check that gnuserv is
actually running, what you describing sounds like its exited.

2)  Try running the tools outside of emacs.

First make sure that neither emacs nor gnuserv are running.

Open two command prompts, in one just run gnuserv in the other type
gnuclient c:/foo.txt

If the gnuserv window has a message about not being able to bind to a socket
then go back and check that gnuserv really isn't running.  By default
gnuserv binds to port 21490.  You can find out what is using a specific port
on XP by running netstat -o, the final column is a process id which you
lookup with a ps like tool or with the task manager.

If some other application is using this port number then you change the port
we're using by setting an environment variable:

GNU_PORT=21490

Anyway, assuming that you got this far then in the gnuserv window you should
see something like this:

1928 (server-edit-files '((1 . "c:/foo.txt")))

with a little character at the end representing a control d.

At this point the gnuserv window just has this text in it and the gnuclient
one is waiting to be told that the file has been completed.

The number, 1928 in this case, represents the socket id and will probably be
different in your case.

Into the gnuserv window type this:

1928/3:nil

followed by a new line. Replacing the 1928 with the appropriate socket id
from the previous line.

Assuming that all is well with the world the gnuserve window should take
this and not print out an error (silence is good in this case).  The
gnuclient window should return to the command prompt having been told that
the edit is complete.

Exit gnuserv by hitting control-C.

2) If that worked then you should be able to run inside emacs.

In you .emacs file you can also add the line:

         (get-buffer-create "*server*")

before the line saying 

         (require 'gnuserv)

If a buffer called *server* is present then gnuserv log all its messages to
it.

Start up emacs again, either directly or via gnuclientw, examine the
*server* buffer and look for any error messages.

If there are sill problems mail them back to the list and I'll see what I
can do.

As far as I know the latest version of the NT emacs version of gnuserv is at

http://www.wyrdrune.com/gnuserv.html This is different to the version
shipped with XEmacs, they have incompatible protocols.

Guy


-----Original Message-----
From: Eli Daniel [mailto:address@hidden 
Sent: Friday, September 20, 2002 10:14 AM
To: address@hidden; address@hidden
Subject: RE: [h-e-w] Problems with gnuserv in XP

Fredrik, 

I am seeing exactly the same behavior on my W2K machine.  I attributed
this to the fact that I have a new machine and had forgotten to
configure something.  But the other difference is that I have W2K
service pack 3 on here for the first time.  I wonder if something in
Windows has changed.

Anyway, if you do resolve your issue, please let me know.

-Eli

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of Fredrik Oberg
Sent: Friday, September 20, 2002 12:31 AM
To: address@hidden
Subject: [h-e-w] Problems with gnuserv in XP

Hi, 
I use gnuserv and a short-cut in my sendto directory to 
easy edit files. I've added the gnuserv exe-files to my 
emacs\bin directory and put gnuserv.el in emacs\site-lisp. 
The path in the sendto shortcut is set to  

C:\Program\emacs-21.2\bin\gnuclientw.exe -q -F

In my .emacs I've added

(setenv "GNUSERV_SHOW_EMACS" "1")  
(setq gnuserv-frame (selected-frame))
(require 'gnuserv)
(gnuserv-start)
(message "gnuserv started.")

On my NT and W2k machine, this works fine but not on my XP 
home machine. If I use the sendto-shortcut when no emacs is 
running, emacs opens and displays the selected file. But if 
emacs is allready running and I try to send another file to 
it, nothing happens. The hourglass is displayed but nothing 
happens in emacs. No messages are added to the *messages* 
buffer.  

Can anybody help me on this?

Thanks in advance
Fredrik








reply via email to

[Prev in Thread] Current Thread [Next in Thread]