GNU bug report logs - #17170
24.3.50; debug: Terminal 3 is locked, cannot read from it

Previous Next

Full log

Message #29 received at 17170 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>
Cc: theonewiththeevillook <at> yahoo.fr, 17170 <at> debbugs.gnu.org
Subject: Re: bug#17170: 24.3.50;
 debug: Terminal 3 is locked, cannot read from it
Date: Sun, 06 Apr 2014 20:00:43 +0300

> X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,
> 	RCVD_IN_DNSWL_NONE autolearn=disabled version=3.3.2
> From: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>
> Cc: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>,  17170 <at> debbugs.gnu.org
> Date: Sun, 06 Apr 2014 18:41:54 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> > Please describe how you started the remote session, and how you got
> > into "emacs -nw" in the same session.  There's something I must be
> > missing here.
> 
> the remote session was started by opening gnome-terminal, then doing:
> $ tmux # this starts a new tmux session.
> $ cd ~/path/to/emacs/src
> $ gdb emacs # drops me in gdb.
> (gdb) r -nw
> 
> now emacs is started. I can detach from tmux and open graphical frames
> using "emacsclient -c".
> 
> When working remotely, I can either run emacsclient from ssh, or run
> "tmux a" for reattaching the initial frame. The reason I do this is to
> be able to reattach to the gdb session in case it takes control and I'm
> working over ssh.
> 
> I hope the picture is now complete.
> 
> -- 
> Nico.
> 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.