🚀 go-pugleaf

In article <1991Jan2.143228@comet.Berkeley.EDU> wbaker%comet.Berkeley.EDU@ucbvax.berkeley.edu (Wendell Craig Baker) writes:
>...
>I am, however having a few problems with emacsclient and long
>filenames and I am wondering if anyone else is having the same
>problem, and if so, what the fix/workaround is.

I posted a bug relating to 18.55 emacsclient and long argument lists
and have a workaround which seems to be ok. This may be related to
your problem.

The symptom of this bug is that the argument list passed to emacs is
split into two instead of one line:

>...
>- The emacs indicates that it has received the file (the *server*
>  buffer contains an entry for the new file) but there is no buffer
>  allocated for the file.

Are you sure the argument is a single line?

If the argument(s) are being split into two (or more) lines then this
should help:
% diff server.el $EMACSLISP/server.el
125,130d124
< (defvar last-client ""
<   "Exists due to often occuring bug in argument list passed through socket.
< The arguments are split up into two strings instead of one, so last client
< hangs on to the client id and unused portion of the last argument string
< and tries to make a usable argument list when the second string comes in.")
< 
135,138c129
<   (if (and (not (eq 0 (string-match "Client: \\([0-9]+\\) " string)))
< 	   (not (eq 0 (string-match "Client: \\([0-9]+\\) " 
< 				    (setq string (concat 
< 						  last-client string))))))
---
>   (if (not (eq 0 (string-match "Client: " string)))
140,141c131,132
<     (setq last-client (substring string (match-beginning 0) (match-end 0)))
<     (let ((client (list (substring string (match-beginning 1) (match-end 1))))
---
>     (setq string (substring string (match-end 0)))
>     (let ((client (list (substring string 0 (string-match " " string))))
155d145
<       (setq last-client (concat last-client (substring string 0 (string-match "\n" string))))
-- 
sja.
uunet!mitel!spock!stephena