From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: next-line + recenter (- redraw frame)?
Date: Mon, 27 Mar 2006 08:51:32 -0700 [thread overview]
Message-ID: <e091nd$vqv$1@sea.gmane.org> (raw)
In-Reply-To: <e04ura$bji$1@reader2.panix.com>
David Combs wrote:
> Never even knew it was there, sun.el.
>
> Questions:
>
> . What makes sun.el relevant to (only?) Sun computers, or Solaris?
It is relevant to Sun keyboards.
> . Is this sun.el so well liked that just about *anyone* running
> emacs on a Sun should put a load-file of it in their .emacs?
It should be loaded automatically:
,----[ C-h v term-file-prefix RET ]
| term-file-prefix's value is "term/"
|
| Documentation:
| If non-nil, Emacs startup does (load (concat term-file-prefix (getenv
"TERM")))
| You may set this variable to nil in your `.emacs' file if you do not wish
| the terminal-initialization file to be loaded.
|
| Defined in `paths.el'.
`----
And from the Emacs manual:
,----
|
| Terminal-specific Initialization
--------------------------------|
|
| Each terminal type can have a Lisp library to be loaded into Emacs
| when it is run on that type of terminal. For a terminal type named
| TERMTYPE, the library is called `term/TERMTYPE' and it is found by
| searching the directories `load-path' as usual and trying the suffixes
| `.elc' and `.el'. Normally it appears in the subdirectory `term' of
| the directory where most Emacs libraries are kept.
|
| The usual purpose of the terminal-specific library is to map the
| escape sequences used by the terminal's function keys onto more
| meaningful names, using `function-key-map'. See the file
| `term/lk201.el' for an example of how this is done. Many function keys
| are mapped automatically according to the information in the Termcap
| data base; the terminal-specific library needs to map only the function
| keys that Termcap does not specify.
|
| When the terminal type contains a hyphen, only the part of the name
| before the first hyphen is significant in choosing the library name.
| Thus, terminal types `aaa-48' and `aaa-30-rv' both use the library
| `term/aaa'. The code in the library can use `(getenv "TERM")' to find
| the full terminal type name.
|
| The library's name is constructed by concatenating the value of the
| variable `term-file-prefix' and the terminal type. Your `.emacs' file
| can prevent the loading of the terminal-specific library by setting
| `term-file-prefix' to `nil'.
|
| Emacs runs the hook `term-setup-hook' at the end of initialization,
| after both your `.emacs' file and any terminal-specific library have
| been read in. Add hook functions to this hook if you wish to override
| part of any of the terminal-specific libraries and to define
| initializations for terminals that do not have a library. *Note
| Hooks::.
|
`----
--
Kevin Rodgers
prev parent reply other threads:[~2006-03-27 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 16:54 next-line + recenter (- redraw frame)? Peter Tury
2006-03-03 17:36 ` Ralf Angeli
2006-03-06 8:17 ` Peter Tury
2006-03-06 8:43 ` Ralf Angeli
2006-03-06 9:34 ` Peter Tury
2006-03-03 22:20 ` Peter Dyballa
[not found] ` <mailman.1.1141424503.26251.help-gnu-emacs@gnu.org>
2006-03-06 8:36 ` Peter Tury
2006-03-26 2:38 ` David Combs
2006-03-26 10:10 ` Peter Dyballa
2006-03-27 15:51 ` Kevin Rodgers [this message]
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='e091nd$vqv$1@sea.gmane.org' \
--to=ihs_4664@yahoo.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.
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).