Re: emacsclient bug

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> > I use emacs pretty much exclusively in multi-tty mode, seldom creating
>> > actual X frames.  I recently switched from the pre-emacs-22 multi-tty
>> > branch to the new emacs-23 snapshot (from a few days ago) and have
>> > noticed some changes.
>> 
>> > 1) Start a new emacs in a tty
>> 
>> > 2) (server-start)
>> 
>> > 3) In another shell, do:
>> >    $ emacsclient <somefilename>
>> 
>> > 4) BUG: emacs opens a new frame.  It should instead load into my
>> > existing emacs tty.  The old multi-tty emacsclient did this correctly
>> 
>> This is not a bug: the behavior was chosen to better match the previous
>> non-multi-tty behavior.  You need to add the "-t" argument to tell
>> emacsclient to open a new frame in the local tty.

> I should add that I think the bug is only after freshly invoking
> server-start -- if you create a tty emacsclient (with emacsclient -t)
> in another tty, then step 3 will result in somefilename being opened
> in an existing tty frame (as desired).

Hmm... looks like I misunderstood the original bug.
Are you saying that if you start

  tty1> emacs -f emacs-server
  tty2> emacsclient foo.bar

that the emacsclient causes a new frame to be opened in tty2 or in tty1
(it should be in tty1)?


        Stefan