On 8/18/09 10:10 AM, Peter Dyballa wrote:
[…]
Are you making your tests without any customisation?
(/Applications/Emacs.app/Contents/MacOS/bin/Emacs -Q &) Could be this
customisation causes the behaviour you see... (My self-compiled
Emacs.app, Tiger PPC, does *not* create a new frame when I invoke
emacsclient, but I prefer to work with at least one frame. All the
time.)
Testing this without customization yields the same result of an
additional frame popping up, immediately prompting me whether I wish
to kill the buffer that still has clients, so this doesn't seem to
be the issue.
Maybe a Tiger v Leopard difference? Could someone running Leopard
with emacs-23.1 please comment on the behavior of emacsclient under
their setup?