I made the following experiment: Emacs had two buffers, <file 1> and <file 2>,
and I entered the following text on the command line,

emacsclient -e <RET>
(kill-buffer (string [file 1])) <RET>
(kill-buffer (string [file 2])) <RET>
<CTRL-Z>

where [file 1] and [file 2] are the string argument forms of <file 1> and
<file 2>, resp. The result was that only the first buffer was killed.

Since Emacs version 21.3 does not have a built in server, I used the program
gnuserv, and I checked the operation of the corresponding gnuclientw program
with Emacs v. 21.3 in the identical situation. I entered the following text:

gnuclientw -e (kill-buf fer (string [file 1])) (kill-buffer (string [file 2]))
<RET>

and the result was as expected, i.e., both buffers got killed. Therefore, I
think that emacsclient has a bug.

In addition, my suggestion is that gnuclient be equipped with a command line
option to accept arguments as a continuation of the command line (i.e.,
similarly to gnuclientw).

Regards,
BV bostjanv@alum.mit.edu