From: Eric Abrahamsen <girzel@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [BUG?] emacs-23.1 OSX emacsclient always opens a new frame
Date: Wed, 19 Aug 2009 13:14:15 +0800 [thread overview]
Message-ID: <1431335B-FA51-41CA-BE82-814D11F5F364@gmail.com> (raw)
In-Reply-To: <h6dpr3$csf$1@reader1.panix.com>
On Aug 18, 2009, at 4:47 PM, Mark Evenson wrote:
> 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?
Whoops, -n is --no-wait, nothing to do with frames, not sure what I
was thinking. I'm using emacs 23 CVS head on Leopard, and it doesn't
create a frame by default (I see there's a -c --create-frame option
that *will* force it to make a new frame). It works just the way you'd
expect it to...
Eric
>
> --
> "A screaming comes across the sky. It has happened before, but there
> is nothing to compare to it now."
next prev parent reply other threads:[~2009-08-19 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 10:54 [BUG?] emacs-23.1 OSX emacsclient always opens a new frame Mark Evenson
2009-08-18 8:10 ` Peter Dyballa
[not found] ` <mailman.4841.1250583053.2239.help-gnu-emacs@gnu.org>
2009-08-18 8:47 ` Mark Evenson
2009-08-19 5:14 ` Eric Abrahamsen [this message]
[not found] ` <mailman.4860.1250658888.2239.help-gnu-emacs@gnu.org>
2009-08-19 7:19 ` Mark Evenson
2009-08-20 8:28 ` [SOLVED] " Mark Evenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431335B-FA51-41CA-BE82-814D11F5F364@gmail.com \
--to=girzel@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.