From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.multi-tty,gmane.emacs.help Subject: Re: M-x term, multi-tty, and terminal emulation problems Date: Wed, 03 May 2006 09:20:11 -0700 Message-ID: <200605031620.k43GKB4g004568@scanner2.ics.uci.edu> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1146673401 3691 80.91.229.2 (3 May 2006 16:23:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 3 May 2006 16:23:21 +0000 (UTC) Cc: multi-tty@lists.fnord.hu, help-gnu-emacs@gnu.org Original-X-From: multi-tty-bounces@lists.fnord.hu Wed May 03 18:23:20 2006 Return-path: Envelope-to: gem-multi-tty@m.gmane.org Original-Received: from ninsei.hu ([212.92.23.158]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FbK8A-0000fP-SC for gem-multi-tty@m.gmane.org; Wed, 03 May 2006 18:23:16 +0200 Original-Received: from [127.0.0.1] (nixon [127.0.0.1]) by chatsubo.ninsei.hu (Postfix) with ESMTP id 954C3785F; Wed, 3 May 2006 18:23:13 +0200 (CEST) Original-Received: from scanner2.ics.uci.edu (scanner2.ics.uci.edu [128.195.1.36]) by chatsubo.ninsei.hu (Postfix) with ESMTP id 437E57830 for ; Wed, 3 May 2006 18:23:12 +0200 (CEST) Original-Received: from vino.ics.uci.edu (vino.ics.uci.edu [128.195.11.198]) by scanner2.ics.uci.edu (8.13.6/8.13.5) with ESMTP id k43GKB4g004568; Wed, 3 May 2006 09:20:11 -0700 (PDT) Original-To: Mark Plaksin In-Reply-To: (Mark Plaksin's message of "Wed, 03 May 2006 08:24:05 -0400") Original-Lines: 46 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-0.84, required 5, autolearn=disabled, ALL_TRUSTED -1.44, J_CHICKENPOX_42 0.60) X-ICS-MailScanner-From: dann@vino.ics.uci.edu X-BeenThere: multi-tty@lists.fnord.hu X-Mailman-Version: 2.1.8rc1 Precedence: list List-Id: Discussions of multiple tty support in Emacs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: multi-tty-bounces@lists.fnord.hu Errors-To: multi-tty-bounces@lists.fnord.hu Xref: news.gmane.org gmane.emacs.multi-tty:555 gmane.emacs.help:34774 Archived-At: Mark Plaksin writes: > >From time to time I have terminal emulation problems with M-x term in > Emacs. I'm never certain whether the problems are caused by me and my > environment variables or by term.el itself. Maybe you can help me figure > it out. > > I use the multi-tty branch (based on CVS Emacs) and use M-x term to connect > to lots of different hosts and then run screen on each host. I put a > compiled version of eterm-color.ti on every host in ~/.terminfo and export > TERMINFO=~/.terminfo. I compile eterm-color.ti once per OS version (e.g., > HP-UX, Solaris, Debian, etc) and copy it around. > > Here's what I do; what's wrong with it? If nothing's wrong, presumably > there are problems in term.el and I'll set about debugging those. > > 1. Run xterm (TERM=xterm) > 2. Run screen (which sets TERM=screen) > 3. Run multi-tty emacs in TTY mode (i.e., no X window gets created) > 4. Detach from screen and get back to the xterm > 5. Run multi-tty's emacsclient to attach to the Emacs that's already > running. This time, an X window is created with Emacs inside. > 6. Run a shell inside of Emacs' terminal emulator (TERM=eterm-color) > 7. ssh to a remote host and get a shell (TERM=eterm-color) > 8. Run screen (which sets TERM=screen) > 9. Run vi or some other full screen app. > > Thanks for any help! Does screen use the "csr" terminfo capability? (You can check like this: M-x term-start-output-log, then run screen then look at the log for the "csr" terminfo string) "csr" is one of the things that M-x term has had problems with. Also smir/rmir might still have issues. You try removing csr, smir and rmir from eterm-color.ti and see if you still have problems. Note that eterm-color terminfo strings are almost the same as the xterm ones. If you save the M-x term output log to a file and run cat LOG in an xterm with the same number of lines and columns as the xterm buffer, the xterm should display the same thing as the M-x term buffer. If it does not, then it's probably an issue with M-x term --dan