Re: emacsclient bug

[Dan Nicolaescu]

Dan Nicolaescu <address@hidden> writes:

  > Stefan Monnier <address@hidden> writes:
  > 
  >   > >     That fact that the Emacs server does not yet have an X11 
connection open
  >   > >     is not taken into account to decide what to: if the client does 
not
  >   > >     explicitly ask for a tty, then the default is to use an X11 frame.
  >   > 
  >   > > That might not be the right thing to do.  It seems to me that the most
  >   > > convenient behavior for emacsclient is to use (by default) the tty or
  >   > > display that Emacs is already using.  It would do that unless you
  >   > > specify -display or -nw or -t.
  >   > 
  >   > > Doesn't that seem right to you?
  >   > 
  >   > Yes, I've just changed it, so that now it behaves by default as it used
  >   > to in Emacs-22: connection to $DISPLAY is only attempted if it's
  >   > explicitly requested by a --display parameter.  It makes the default
  >   > not only closer to previous behavior but also "safer" I believe.
  > 
  > Does it work? 
  > 
  > After updating from CVS and make bootstrap
  > 
  > emacs -Q -f server-start&
  > 
  > emacsclient ~/.emacs 
  > just hangs

I fixed this.

There's still one issue left: "-c" does not work anymore, it creates a
tty frame.