Mercurial > emacs
annotate admin/notes/iftc @ 83416:4513d8dcdfd5
Reimplement and extend support for terminal-local environment variables.
* lisp/termdev.el: New file. Move terminal parameter-related functions
here from frame.el.
(terminal-getenv, with-terminal-environment): Reimplement and extend.
(terminal-setenv, terminal-setenv-internal): New functions.
* lisp/frame.el (make-frame-on-tty, framep-on-display, suspend-frame):
Extend doc string, update parameter names.
(terminal-id, terminal-parameter-alist, terminal-parameters)
(terminal-parameter-p, terminal-parameter, set-terminal-parameter)
(terminal-handle-delete-frame, terminal-getenv, terminal-getenv)
(with-terminal-environment): Move to termdev.el.
* lisp/loadup.el: Load termdev as well.
* lisp/Makefile.in (lisp, shortlisp): Add termdev.elc.
* lisp/makefile.MPW (shortlisp): Ditto.
* lisp/ebuff-menu.el (electric-buffer-menu-mode-map): Bind C-z to
`suspend-frame', not `suspend-emacs'.
* lisp/echistory.el (electric-history-map): Ditto.
* lisp/ebrowse.el (ebrowse-electric-list-mode-map): Ditto.
* lisp/ebrowse.el (ebrowse-electric-position-mode-map): Ditto.
* lisp/startup.el (normal-splash-screen): Use `save-buffers-kill-display'
instead of `save-buffers-kill-emacs'.
* lisp/x-win.el (x-initialize-window-system): Add 'global-ok option to
`terminal-getenv'.
* src/term.c (suspend-tty): Update doc string.
git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-456
| author | Karoly Lorentey <lorentey@elte.hu> |
|---|---|
| date | Thu, 22 Dec 2005 21:02:45 +0000 |
| parents | 695cf19ef79e |
| children | 375f2633d815 ef719132ddfa |
| rev | line source |
|---|---|
| 45625 | 1 Iso-Functional Type Contour |
| 2 | |
| 3 | |
| 4 This is a term coined to describe "column int->float" change approach, and can | |
| 5 be used whenever low-level types need to change (hopefully not often!) but the | |
| 6 meanings of the values (whose type has changed) do not. | |
| 7 | |
| 8 The premise is that changing a low-level type potentially means lots of code | |
| 9 needs to be changed as well, and the question is how to do this incrementally, | |
| 10 which is the preferred way to change things. | |
| 11 | |
| 12 Say LOW and HIGH are C functions: | |
| 13 | |
| 14 int LOW (void) { return 1; } | |
| 15 void HIGH (void) { int value = LOW (); } | |
| 16 | |
| 17 We want to convert LOW to return float, so we cast HIGH usage: | |
| 18 | |
| 19 float LOW (void) { return 1.0; } | |
| 20 void HIGH (void) { int value = (int) LOW (); } /* iftc */ | |
| 21 | |
| 22 The comment /* iftc */ is used to mark this type of casting to differentiate | |
| 23 it from other casting. We commit the changes and can now go about modifying | |
| 24 LOW and HIGH separately. When HIGH is ready to handle the type change, the | |
| 25 cast can be removed. | |
| 52401 | 26 |
| 27 ;;; arch-tag: 3309cc41-5d59-421b-b7be-c94b04083bb5 |
