unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* Error in emacsclient operation
@ 2007-06-10  6:30 Bostjan Vilfan
  2007-06-10 19:12 ` Eli Zaretskii
  0 siblings, 1 reply; 2+ messages in thread
From: Bostjan Vilfan @ 2007-06-10  6:30 UTC (permalink / raw)
  To: bug-gnu-emacs


[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]


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-buffer (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




      ____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/ 

[-- Attachment #1.2: Type: text/html, Size: 1624 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Error in emacsclient operation
  2007-06-10  6:30 Error in emacsclient operation Bostjan Vilfan
@ 2007-06-10 19:12 ` Eli Zaretskii
  0 siblings, 0 replies; 2+ messages in thread
From: Eli Zaretskii @ 2007-06-10 19:12 UTC (permalink / raw)
  To: Bostjan Vilfan; +Cc: bug-gnu-emacs

> Date: Sat, 9 Jun 2007 23:30:07 -0700 (PDT)
> From: Bostjan Vilfan <bvilf@yahoo.com>
> 
> 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.

Thank you for your report.

Try this command, it works for me:

  emacsclient -e "(kill-buffer \"file 1\")" "(kill-buffer \"file 2\")"

> 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-buffer (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.

Given the above command I suggested, do you still think emacsclient
has a bug?  The fact that gnuclientw works differently is not a proof,
since emacsclient's UI does not mimic that of gnuclientw's.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-06-10 19:12 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-10  6:30 Error in emacsclient operation Bostjan Vilfan
2007-06-10 19:12 ` Eli Zaretskii

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).