Mercurial > hg > xemacs-beta
view etc/TERMS @ 872:79c6ff3eef26
[xemacs-hg @ 2002-06-20 21:18:01 by ben]
font changes etc.; some 21.4 changes
mule/mule-msw-init-late.el: Specify charset->windows-registry conversion.
mule/mule-x-init.el: Delete extra mule font additions here. Put them in faces.c.
cl-macs.el: Document better.
font-lock.el: Move Lisp function regexp to lisp-mode.el.
lisp-mode.el: Various indentation fixes:
Handle flet functions better.
Handle argument lists in defuns and flets.
Handle quoted lists, e.g. property lists -- don't indent like
function calls. Distinguish between lambdas and other lists.
lisp-mode.el: Handle this form.
faces.el, font-menu.el, font.el, gtk-faces.el, msw-faces.el, msw-font-menu.el, x-faces.el, x-init.el: Major overhaul of face-handling code:
-- Fix lots of bogus code in msw-faces.el, msw-font-menu.el,
font-menu.el that was "truenaming" font specs -- i.e. in the
process of frobbing a particular field in a general user-specified
font spec with wildcarded fields, sticking in particular values
for all the remaining wildcarded fields. This bug was rampant
everywhere except in x-faces.el (the oldest and only correctly
written code). This also means that we need to work with font
names at all times and not font instances, because a font instance
is essentially a truenamed font.
-- Total rewrite of extremely junky code in msw-faces.el. Work
with names as well as font instances, and return names; stop
truenaming when canonicalizing and frobbing; fix handling of the
combined style field, i.e. weight/slant (also fixed in font.el).
-- Totally rewrite the frobbing functions in faces.el. This time,
we frob all the instantiators rather than just computing a single
instance value and working backwards. That way, e.g., `bold' will
work for all charsets that have bold available, rather than only
for whatever charset was part of the computed font instance
(another example of the truename virus). Also fix up code to look
at the fallbacks (all of them) when no global value present, so we
don't need to put something in the global value. Intelligently
handle a request to frob a buffer locale, rather than signalling
an error. When frobbing instantiators, try hard to figure out
what device type is associated with them, and frob each according
to its own proper device type. Correctly handle inheritance
vectors given as instantiators. Preserve existing tags when
putting back frobbed instantiators. Extract out general
specifier-frobbing code into specifier.el. Document everything
cleanly. Do lots of other things better, etc.
-- Don't duplicatively set a global specification for the default
font -- it's already in the fallback and we no longer need a
default global specification present. Delete various code in
x-faces.el and msw-faces.el that duplicated the lists of fonts in
faces.c.
-- init-global-faces was not being called at all under MS Windows!
Major bogosity. That caused device-specific values to get stuck
into all the fonts, making it very hard to change them -- setting
global specs caused nothing to happen.
-- Correct weight names in font.el.
-- Lots more font fixups in objects*.c.
Printer.el: Warning fix.
specifier.el: Add more args to map-specifier.
Add various "heuristic" specifier functions to aid in creation of
specifier-munging code such as in faces.el.
subr.el: New functions.
lwlib.c: Fix warning.
config.inc.samp: Clean up, add args to control fastcall (not yet supported! the
changes needed are in another ws of mine), profile support, vc6
support, union-type.
xemacs.dsp, xemacs.mak: Semi-major overhaul.
Fix bug where dump-id was always getting recomputed, forcing a
redump even when nothing changed.
Add support for fastcall. Support edit-and-continue (on by
default) with vc6. Use incremental linking when doing a debug
compilation. Add support for profiling.
Consolidate the various debug flags.
Partial support for "batch-compiling" -- compiling many files on a
single invocation of the compiler. Doesn't seem to help that much
for me, so it's not finished or enabled by default.
Remove HAVE_MSW_C_DIRED, we always do.
Correct some sloppy use of directories.
s/cygwin32.h: Allow pdump to work under Cygwin (mmap is broken, so need to undefine
HAVE_MMAP).
s/win32-common.h, s/windowsnt.h: Support for fastcall. Add WIN32_ANY for identifying all Win32
variants (Cygwin, native, MinGW). Both of these are properly used
in another ws.
alloc.c, balloon-x.c, buffer.c, bytecode.c, callint.c, cm.c, cmdloop.c, cmds.c, console-gtk.c, console-gtk.h, console-msw.c, console-msw.h, console-stream.c, console-stream.h, console-tty.c, console-tty.h, console-x.c, console-x.h, console.c, console.h, device-gtk.c, device-msw.c, device-tty.c, device-x.c, device.c, device.h, devslots.h, dialog-gtk.c, dialog-msw.c, dialog-x.c, dialog.c, dired-msw.c, editfns.c, emacs.c, event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, event-tty.c, event-unixoid.c, events.c, extents.c, extents.h, faces.c, fileio.c, fns.c, frame-gtk.c, frame-msw.c, frame-tty.c, frame-x.c, frame.c, frame.h, glyphs-eimage.c, glyphs-gtk.c, glyphs-msw.c, glyphs-widget.c, glyphs-x.c, glyphs.c, glyphs.h, gui-gtk.c, gui-msw.c, gui-x.c, gui.c, gutter.c, input-method-xlib.c, intl-encap-win32.c, intl-win32.c, keymap.c, lisp.h, macros.c, menubar-gtk.c, menubar-msw.c, menubar-x.c, menubar.c, menubar.h, minibuf.c, mule-charset.c, nt.c, objects-gtk.c, objects-gtk.h, objects-msw.c, objects-msw.h, objects-tty.c, objects-tty.h, objects-x.c, objects-x.h, objects.c, objects.h, postgresql.c, print.c, process.h, redisplay-gtk.c, redisplay-msw.c, redisplay-output.c, redisplay-tty.c, redisplay-x.c, redisplay.c, redisplay.h, scrollbar-gtk.c, scrollbar-msw.c, scrollbar-x.c, scrollbar.c, select-gtk.c, select-msw.c, select-x.c, select.c, signal.c, sound.c, specifier.c, symbols.c, syntax.c, sysdep.c, syssignal.h, syswindows.h, toolbar-common.c, toolbar-gtk.c, toolbar-msw.c, toolbar-x.c, toolbar.c, unicode.c, window.c, window.h: The following are the major changes made:
(1) Separation of various header files into an external and an
internal version, similar to the existing separation of process.h
and procimpl.h. Eventually this should be done for all Lisp
objects. The external version has the same name as currently; the
internal adds -impl. The external file has XFOO() macros for
objects, but the structure is opaque and defined only in the
internal file. It's now reasonable to move all prototypes in
lisp.h into the appropriate external file, and this should be
done. Currently, separation has been done on extents.h,
objects*.h, console.h, device.h, frame.h, and window.h.
For c/d/f/w, the most basic properties are available in the
external header file, with the macros resolving to functions. In
the internal header file, the macros are redefined to directly
access the structure. Also, the global MARK_FOO_CHANGED macros
have been made into functions so that they can be accessed without
needing to include lots of -impl headers -- they are used in
almost exclusively in non-time-critical functions, and take up
enough time that the function overhead will be negligible.
Similarly, the function overhead from making the basic properties
mentioned above into functions is negligible, and code that does
heavy accessing of c/d/f/w structures inevitably ends up needing
the internal header files, anyway.
(2) More face changes.
-- Major rewrite of objects-msw.c. Now handles wildcard specs
properly, rather than "truenaming" (or even worse, signalling an
error, which previously happened with some of the fallbacks if you
tried to use them in make-font-instance!).
-- Split charset matching of fonts into two stages -- one to find
a font specifically designed for a particular charset (by
examining its registry), the second to find a Unicode font that
can support the charset. This needs to proceed as two complete,
separate instantiations in order to work properly (otherwise many
of the fonts in the HELLO page look wrong). This should also make
it easy to support iso10646 (Unicode) fonts under X.
-- All default values for fonts are now completely specified in
the fallbacks. Stuff from mule-x-init.el has all been moved here,
merged with the existing specs, and totally rethought so you get
sensible results. (HELLO now looks much better!).
-- Generalize the "default X/GTK device" stuff into a
per-device-type "default device".
-- Add mswindows-{set-}charset-registry. In time,
charset<->code-page conversion functions will be removed.
-- Wrap protective code around calls to compute device specifier tags,
and do this computation before calling the face initialization code
because the latter may need these tags to be correctly updated.
(3) Other changes.
EmacsFrame.c, glyphs-msw.c, eval.c, gui-x.c, intl-encap-win32.c, search.c, signal.c, toolbar-msw.c, unicode.c: Warning fixes.
config.h.in: #undefs meant to be frobbed by configure *MUST* go inside of
#ifndef WIN32_NO_CONFIGURE, and everything else *MUST* go outside!
eval.c: Let detailed backtraces be detailed.
specifier.c: Don't override user's print-string-length/print-length settings.
glyphs.c: New function image-instance-instantiator.
config.h.in, sysdep.c: Changes for fastcall.
sysdep.c, nt.c: Fix up a previous botched patch that tried to add support for both
EEXIST and EACCES. IF THE BOTCHED PATCH WENT INTO 21.4, THIS FIXUP
NEEDS TO GO IN, TOO.
search.c: Fix *evil* crash due to incorrect synching of syntax-cache code
with 21.1. THIS SHOULD GO INTO 21.4.
author | ben |
---|---|
date | Thu, 20 Jun 2002 21:19:10 +0000 |
parents | 376386a54a3c |
children |
line wrap: on
line source
This file describes what you must or might want to do to termcap entries to make terminals work properly and efficiently with Emacs. Information on likely problems with specific types of terminals appears at the end of the file. *** What you want in a terminal *** Vital 1. Easy to compute suitable padding for. 2. Never ever sends ^S/^Q unless you type them, at least in one mode. Nice for speed 1. Supports insert/delete of multiple lines in one command. 2. Same for multiple characters, though doing them one by one is usually fast enough except on emulators running on machines with bitmap screens. Nice for usability 1. Considerably more than 24 lines. 2. Meta key (shift-like key that controls the 0200 bit in every character you type). *** New termcap strings *** Emacs supports certain termcap strings that are not described in the 4.2 manual but appear to be standard in system V. The one exception is `cS', which I invented. `AL' insert several lines. Takes one parameter, the number of lines to be inserted. You specify how to send this parameter using a %-construct, just like the cursor positions in the `cm' string. `DL' delete several lines. One parameter. `IC' insert several characters. One parameter. `DC' delete several characters. One parameter. `rp' repeat a character. Takes two parameters, the character to be repeated and the number of times to repeat it. Most likely you will use `%.' for sending the character to be repeated. Emacs interprets a padding spec with a * as giving the amount of padding per repetition. WARNING: Many terminals have a command to repeat the *last character output* N times. This means that the character will appear N+1 times in a row when the command argument is N. However, the `rp' string's parameter is the total number of times wanted, not one less. Therefore, such repeat commands may be used in an `rp' string only if you use Emacs's special termcap operator `%a-c\001' to subtract 1 from the repeat count before substituting it into the string. It is probably safe to use this even though the Unix termcap does not accept it because programs other than Emacs probably won't look for `rp' anyway. `cs' set scroll region. Takes two parameters, the vertical positions of the first line to include in the scroll region and the last line to include in the scroll region. Both parameters are origin-zero. The effect of this should be to cause a following insert-line or delete-line not to move lines below the bottom of the scroll region. This is not the same convention that Emacs version 16 used. That is because I was led astray by unclear documentation of the meaning of %i in termcap strings. Since the termcap documentation for `cs' is also unclear, I had to deduce the correct parameter conventions from what would make the VT-100's `cs' string work properly. From an incorrect assumption about %i, I reached an incorrect conclusion about `cs', but the result worked correctly on the VT100 and ANSII terminals. In Emacs version 17, both `cs' and %i work correctly. The version 16 convention was to pass, for the second parameter, the line number of the first line beyond the end of the scroll region. `cS' set scroll region. Differs from `cs' in taking parameters differently. There are four parameters: 1. Total number of lines on the screen. 2. Number of lines above desired scroll region. 3. Number of lines below (outside of) desired scroll region. 4. Total number of lines on the screen, like #1. This is because an Ambassador needs the parameters like this. `cr', `do', `le' Emacs will not attempt to use ^M, ^J or ^H for cursor motion unless these capabilities are present and say to use those characters. `km' Says the terminal has a Meta key. Defining these strings is important for getting maximum performance from your terminal. Make sure that the `ti' string sets all modes needed for editing in Emacs. For example, if your terminal has a mode that controls wrap at the end of the line, you must decide whether to specify the `am' flag in the termcap entry; whichever you decide, the `ti' string should contain commands to set the mode that way. (Emacs also sends the `vs' string after the `ti' string. You can put the mode-setting commands in either one of them.) *** Specific Terminal Types *** Watch out for termcap entries for Ann Arbor Ambassadors that give too little padding for clear-screen. 7.2 msec per line is right. These are the strings whose padding you probably should change: :al=1*\E[L:dl=1*\E[M:cd=7.2*\E[J:cl=7.2*\E[H\E[J: I have sometimes seen `\E[2J' at the front of the `ti' string; this is a clear-screen, very slow, and it can cause you to get Control-s sent by the terminal at startup. I recommend removing the `\E[2J' from the `ti' string. The `ti' or `vs' strings also usually need stuff added to them, such as \E[>33;52;54h\E[>30;37;38;39l You might want to add the following to the `te' or `ve' strings: \E[>52l\E[>37h The following additional capabilities will improve performance: :AL=1*\E[%dL:DL=1*\E[%dM:IC=4\E[%d@:DC=4\E[%dP:rp=1*%.\E[%a-c\001%db: If you find that the Meta key does not work, make sure that :km: is present in the termcap entry. Watch out for termcap entries for VT100's that fail to specify the `sf' string, or that omit the padding needed for the `sf' and `sr' strings (2msec per line affected). What you need is :sf=2*^J:sr=2*\EM:cs=\E[%i%d;%dr: The Concept-100 and Concept-108 have many modes that `ti' strings often fail to initialize. If you have problems on one of these terminals, that is probably the place to fix them. These terminals can support an `rp' string. Watch out on HP terminals for problems with standout disappearing on part of the mode line. These problems are due to the absence of :sg#0: which some HP terminals need. The vi55 is said to require `ip=2'. The Sun console should have these capabilities for good performance. :AL=\E[%dL:DL=\E[%dM:IC=\E[%d@:DC=\E[%dP: The vt220 needs to be set to vt220 mode, 7 bit, space parity in order to work fully with TERM=vt220. If you are using a LAT terminal concentrator, you need to issue these commands to turn off flow control: set port flow control disable define port flow control disable On System V, in the terminfo database, various terminals may have the `xt' flag that should not have it. `xt' should be present only for the Teleray 1061 or equivalent terminal. In particular, System V for the 386 often has `xt' for terminal type AT386 or AT386-M, which is used for the console. You should delete this flag. Here is how: You can get a copy of the terminfo "source" for at386 using the command: `infocmp at386 >at386.tic'. Edit the file at386.tic and remove the `xt' flag. Then compile the new entry with: `tic at386.tic'. It is also reported that these terminal types sometimes have the wrong reverse-scroll string. It should be \E[T, but sometimes is given as \E[S. Here is what watserv1!maytag!focsys!larry recommends for these terminals: # This copy of the terminfo description has been fixed. # The suggestions came from a number of usenet postings. # # Intel AT/386 for color card with monochrome display # AT386-M|at386-m|386AT-M|386at-m|at/386 console, am, bw, eo, xon, cols#80, lines#25, acsc=``a1fxgqh0jYk?lZm@nEooppqDrrsstCu4vAwBx3yyzz{{||}}~~, bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, clear=\E[2J\E[H, cr=\r, cub=\E[%p1%dD, cub1=\E[D, cud=\E[%p1%dB, cud1=\E[B, cuf=\E[%p1%dC, cuf1=\E[C, cup=\E[%i%p1%02d;%p2%02dH, cuu=\E[%p1%dA, cuu1=\E[A, dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM, dl1=\E[1M, ech=\E[%p1%dX,ed=\E[J, el=\E[K, el1=\E[1K\E[X, flash=^G, home=\E[H, hpa=\E[%i%p1%dG, ich=\E[%p1%d@, ich1=\E[1@, il=\E[%p1%dL, il1=\E[1L, ind=\E[S, indn=\E[%p1%dS, invis=\E[9m, is2=\E[0;10;38m, kbs=\b, kcbt=^], kclr=\E[2J, kcub1=\E[D, kcud1=\E[B, kcuf1=\E[C, kcuu1=\E[A, kdch1=\E[P, kend=\E[Y, kf1=\EOP, kf10=\EOY, kf11=\EOZ, kf12=\EOA, kf2=\EOQ, kf3=\EOR, kf4=\EOS, kf5=\EOT, kf6=\EOU, kf7=\EOV, kf8=\EOW, kf9=\EOX, khome=\E[H, kich1=\E[@, knp=\E[U, kpp=\E[V, krmir=\E0, rev=\E[7m, ri=\E[T, rin=\E[%p1%dT, rmacs=\E[10m, rmso=\E[m, rmul=\E[m, sgr=\E[10m\E[0%?%p1%p3%|%t;7%;%?%p2%t;4%;%?%p4%t;5%;%?%p6%t;1%;%?%p9%t;12%;%?%p7%t;9%;m, sgr0=\E[0;10m, smacs=\E[12m, smso=\E[7m, smul=\E[4m, # # AT&T 386 color console # AT386|at386|386AT|386at|at/386 console, colors#8, ncv#3, pairs#64, is2=\E[0;10;39m, op=\E[0m, setb=\E[%?%p1%{0}%=%t40m %e%p1%{1}%=%t44m %e%p1%{2}%=%t42m %e%p1%{3}%=%t46m %e%p1%{4}%=%t41m %e%p1%{5}%=%t45m %e%p1%{6}%=%t43m %e%p1%{7}%=%t47m%;, setf=\E[%?%p1%{0}%=%t30m %e%p1%{1}%=%t34m %e%p1%{2}%=%t32m %e%p1%{3}%=%t36m %e%p1%{4}%=%t31m %e%p1%{5}%=%t35m %e%p1%{6}%=%t33m %e%p1%{6}%=%t33m %e%p1%{7}%=%t37m%;, use=at386-m, # # Color console version that supports underline but maps blue # foreground color to cyan. # AT386-UL|at386-ul|386AT-UL|386at-ul|at/386 console, is2=\E[0;10;38m, use=at386,