emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacsclient bug


From: Len Trigg
Subject: Re: emacsclient bug
Date: Fri, 18 Jan 2008 06:56:19 +1300
User-agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/23.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

Stefan Monnier wrote:
> 
> > 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).

Cheers,
Len.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]