unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Raitza <spacefrogg-emacs@instandbesetzt.net>
To: Thomas Hisch <t.hisch@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: term/screen.el - screen terminfo/color setup
Date: Wed, 09 Nov 2011 18:20:47 +0100	[thread overview]
Message-ID: <1320858997-sup-5409@leandros> (raw)
In-Reply-To: <CA+e_Qicp4UgFd6aQgPz6-gFb4evMDtAHCjwYnYdeJCoqJt6BSQ@mail.gmail.com>

Thomas,

you need to put screen.el under <some-path>/term/screen.el with
<some-path> in 'load-path.

emacs searches for <TERM>.el in terms of the TERM environment variable
at startup time. See also comments in screen.el.

M

Excerpts from Thomas Hisch's message of Sat Nov 05 21:22:36 +0100 2011:
> @martin
> 
> what do I need to use your screen.el ? Should a simple load-file in a
> running emacs session inside gnu screen be sufficient ?
> 
> Regards
> thomas
> 
> On Sun, Oct 16, 2011 at 6:59 PM, Michael Raitza
> <spacefrogg-emacs@instandbesetzt.net> wrote:
> > Hi,
> >
> > the screen.el in bzr is incomplete as it just tries to impersonate xterm.
> > The screen terminfo description defines its own (different from e.g.
> > xterm) key bindings. As you can see my solution makes use of the
> > COLORTERM environment variable (as does xterm.el itself) and correctly
> > specifies the key bindings.
> >
> > One question: According to term/README the key binding for END should be
> > [end], but everyone else seems to specify [select] there (See comment
> > below in screen.el). Which one is correct?
> >
> >
> > M
> >




  reply	other threads:[~2011-11-09 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 20:49 term/screen.el - screen terminfo/color setup Michael Raitza
2011-10-16 11:04 ` Thomas Hisch
2011-10-16 13:32 ` Carsten Mattner
     [not found] ` <jwvy5wluek0.fsf-monnier+emacs@gnu.org>
2011-10-16 16:59   ` Michael Raitza
2011-11-05 20:22     ` Thomas Hisch
2011-11-09 17:20       ` Michael Raitza [this message]
2011-11-18 21:29     ` Samuel Bronson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1320858997-sup-5409@leandros \
    --to=spacefrogg-emacs@instandbesetzt.net \
    --cc=emacs-devel@gnu.org \
    --cc=t.hisch@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).