From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Anthony R. Cassandra" Newsgroups: gmane.emacs.devel Subject: Re: support for tty frames from windowed emacs session Date: Sat, 8 Mar 2003 16:25:46 -0600 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <15978.28138.30541.343605@groovy.cassandra.org> References: <15977.15192.682739.618251@groovy.cassandra.org> <9791-Sat08Mar2003113505+0200-eliz@elta.co.il> <5x3clx4iow.fsf@kfs2.cua.dk> Reply-To: arc@cassandra.org NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1047162555 10516 80.91.224.249 (8 Mar 2003 22:29:15 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sat, 8 Mar 2003 22:29:15 +0000 (UTC) Cc: arc@cassandra.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Mar 08 23:29:14 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18rmoc-0002jS-00 for ; Sat, 08 Mar 2003 23:29:14 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18rnA5-0004Fj-00 for ; Sat, 08 Mar 2003 23:51:26 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18rmnZ-0001Qd-02 for emacs-devel@quimby.gnus.org; Sat, 08 Mar 2003 17:28:09 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18rmn2-0000yr-00 for emacs-devel@gnu.org; Sat, 08 Mar 2003 17:27:36 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18rmmJ-0008Cr-00 for emacs-devel@gnu.org; Sat, 08 Mar 2003 17:26:54 -0500 Original-Received: from [216.30.78.113] (helo=cassandra.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18rmlP-0007U8-00 for emacs-devel@gnu.org; Sat, 08 Mar 2003 17:25:55 -0500 Original-Received: (from arc@localhost) by cassandra.org (8.11.2/8.11.2) id h28MPki17153; Sat, 8 Mar 2003 16:25:46 -0600 Original-To: storm@cua.dk (Kim F. Storm) In-Reply-To: <5x3clx4iow.fsf@kfs2.cua.dk> X-Mailer: VM 6.95 under Emacs 20.7.1 Original-cc: Eli Zaretskii Original-cc: emacs-devel@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:12186 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:12186 >I would like to know more specifically what functionality is >requested here. What qualifies as a "tty" in this regard? >A serial port, a pty, etc? >>From any sort of non-X/windowed terminal. >I never thought I needed this -- why is it important? Here a common situation: I have my home machine and my work machine, both running gnu-emacs in X, both with their own context including normal files and especially email buffers (separate email accounts). These are two separate contexts, as my work and email logically should and are separated. However, from home I want access to my work context and from work I want access to my home context (both via ssh). Since both these machines are behind firewalls, getting an X connections forwarded (even with ssh) is not always easy or desirable (such as if I want to access via an MSWindoze ssh client.) What I presently have to do is ensure that I have quit my email (vm) before leaving work or leaving home because vm is quite tempermental if another emacs session has accessed its INBOX. I would prefer to establish my ssh connection (via an xterm, but without X forwarded) and just connect to the running emacs on the remote machine. Essentially I want the same behavior as 'make-frame-on-display' gives me, only without the reliance on X. BTW: xemacs along with gnuserv/"gnuclient -nw" gives exactly this functionality "out-of-the-box" (my friend confirmed this last night). >What kind of TERMINFO entry would be used for the tty? I am not intimately familiar with all the possible terminfo and termcap stuff aside from knowing there is a lot of cryptic syntax to figue out and a lot of possible cases to worry about. Personally, I'd be happy if is just supported some basic terminal types such as what is established via my ssh connection in the xterm. However, the developer side of my personality would probably not be satisfied with a point solution, and would want to solve the whole problem. >What about the setup of the tty (ioctls, etc)? Shall emacs do that? These are exactly the sorts of issues I am not currently familiar enough with, which is why I am hoping someone with a little more experience in these areas could give me a sort of feasibility assessment on the effort required to add this support. >Although there might not be _major_ technical problems, I don't think >it will be trivial to implement. Yes, I believe to do it properly would not be, though this is just based on my cursory looks, and the bewilderment I experience, in termcap files. -tony