Am 31.12.2007 um 15:21 schrieb Carsten Bormann: > On Dec 31 2007, at 14:45, Peter Dyballa wrote: > >> Did you also try /Applications/Emacs.app/Contents/MacOS/bin/ >> emacsclient? > > Yes, this is the one that tries to kill the buffer immediately. > Looking again, I noticed that my usual alias calls it with -n. > If I call it without -n, rc3 immediately says: > >> Buffer `c.c' still has clients; kill it? (yes or no)
I can't reproduce this with the original Emacs.app from SourceForge. When I use emacsclient from a more recent CVS download, self- compiled, I can produce both of your messages, the one above and also that reported this morning and earlier in December. It depends on the versions of Emacs.app (original one or self-compiled) and that of emacsclient. Arguments to emacsclient play no role. Emacsclient(s) give different output from --help ... As a rule of thumb it's recommended to use that emacsclient that comes with the Emacs application. This is particularly then true, when emacsclient has been patched to support the multi-tty patch and the Emacs application has not. Then both ends of the line of communication don't understand each other – in all cases. To follow the above mentioned recommendation it's just necessary to use the proper shell alias, the one pointing to the application's own emacsclient programme. -- Mit friedvollen Grüßen Pete Irgendwer sollte den Kugelschreiber mit einem Kleiderbügel kreuzen, dass die Kulis sich vermehren, statt stets nur zu verschwinden! ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emacs-app-dev- mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
