February 2005 - xemacs-cvs＠xemacs.org - XEmacs Mailing List Archives

CVS update by vins MODIFIED: xemacs/lisp, window-xemacs.el ... 19 years, 10 months

CVS Monitor

User: vins Date: 05/02/19 23:02:06 Modified: xemacs/lisp Tag: release-21-4 ChangeLog buffer.el window-xemacs.el Log: - Document use of same-window-buffer-names and same-window-regexps by pop-to-buffer and display-buffer. - Announce latin-euro-standards, update mule-base packages. Revision Changes Path No revision No revision 1.241.2.75 +4 -0 XEmacs/xemacs/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/ChangeLog,v retrieving revision 1.241.2.74 retrieving revision 1.241.2.75 diff -u -r1.241.2.74 -r1.241.2.75 --- ChangeLog 2005/02/14 04:15:22 1.241.2.74 +++ ChangeLog 2005/02/19 22:01:55 1.241.2.75 ＠＠ -1,3 +1,7 ＠＠ +2005-02-19 Norbert Koch <viteno(a)xemacs.org> + + * etc/PACKAGES: Announce latin-euro-standards, update mule-base. + 2005-02-12 Vin Shelton <acs(a)xemacs.org> * etc/OXYMORONS: New list. No revision No revision 1.8.4.6 +4 -1 XEmacs/xemacs/etc/Attic/PACKAGES Index: PACKAGES =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/Attic/PACKAGES,v retrieving revision 1.8.4.5 retrieving revision 1.8.4.6 diff -u -r1.8.4.5 -r1.8.4.6 --- PACKAGES 2004/04/20 02:56:26 1.8.4.5 +++ PACKAGES 2005/02/19 22:01:59 1.8.4.6 ＠＠ -370,6 +370,9 ＠＠ *** egg-its MULE: Wnn (4.2 and 6) support. SJ3 support. +*** latin-euro-standards +MULE: Support for the Latin{7,8,9,10} character sets & coding systems. + *** latin-unity MULE: find single ISO 8859 character set to encode a buffer. ＠＠ -383,7 +386,7 ＠＠ MULE: Dictionary support. *** mule-base -MULE: Basic Mule support, required for building with Mule. +MULE: Basic Mule support. *** mule-ucs MULE: Extended coding systems (including Unicode) for XEmacs. No revision No revision 1.266.2.80 +7 -0 XEmacs/xemacs/lisp/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/ChangeLog,v retrieving revision 1.266.2.79 retrieving revision 1.266.2.80 diff -u -r1.266.2.79 -r1.266.2.80 --- ChangeLog 2005/02/06 19:23:37 1.266.2.79 +++ ChangeLog 2005/02/19 22:02:00 1.266.2.80 ＠＠ -1,3 +1,10 ＠＠ +2005-02-16 Aidan Kehoe <kehoea(a)parhasard.net> + + * buffer.el (pop-to-buffer): + * window-xemacs.el (display-buffer): + Document use of `same-window-buffer-names,' `same-window-regexps' + by pop-to-buffer and display-buffer. + 2005-02-06 Vin Shelton <acs(a)xemacs.org> * XEmacs 21.4.17 is released 1.4.2.1 +6 -1 XEmacs/xemacs/lisp/buffer.el Index: buffer.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/buffer.el,v retrieving revision 1.4 retrieving revision 1.4.2.1 diff -u -r1.4 -r1.4.2.1 --- buffer.el 2001/04/12 18:21:11 1.4 +++ buffer.el 2005/02/19 22:02:02 1.4.2.1 ＠＠ -71,7 +71,12 ＠＠ another window even if BUFNAME is already visible in the selected window. If optional third arg is non-nil, it is the frame to pop to this buffer on. -If `focus-follows-mouse' is non-nil, keyboard focus is left unchanged." +If `focus-follows-mouse' is non-nil, keyboard focus is left unchanged. + +Buffers with names that are members of the `same-window-buffer-names' +list, or that match an element of the `same-window-regexps' list are +treated specially by this function--they are always selected in the +same window rather than in a different one." ;; #ifdef I18N3 ;; #### Doc string should indicate that the buffer name will get ;; translated. 1.10.2.3 +4 -0 XEmacs/xemacs/lisp/window-xemacs.el Index: window-xemacs.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/window-xemacs.el,v retrieving revision 1.10.2.2 retrieving revision 1.10.2.3 diff -u -r1.10.2.2 -r1.10.2.3 --- window-xemacs.el 2003/09/14 01:43:25 1.10.2.2 +++ window-xemacs.el 2005/02/19 22:02:02 1.10.2.3 ＠＠ -376,6 +376,10 ＠＠ If `pop-up-frames' is non-nil, make a new frame if no window shows BUFFER. +If the buffer name is a member of the `same-window-buffer-names' list, +or matches one of the `same-window-regexps' expressions, display the +buffer in the currently selected window. + Returns the window displaying BUFFER." (interactive "BDisplay buffer:\nP")

1 participants
0 comments

CVS update by viteno MODIFIED: xemacs-builds/viteno ... 19 years, 10 months

CVS Monitor

User: viteno Date: 05/02/19 21:48:56 Modified: xemacs-builds/viteno package-index setup-packages.ini Log: Package database backup: - viper-1.38 Revision Changes Path 1.195 +6 -6 XEmacs/xemacs-builds/viteno/package-index Index: package-index =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs-builds/viteno/package-index,v retrieving revision 1.194 retrieving revision 1.195 diff -u -r1.194 -r1.195 --- package-index 2005/02/19 11:54:49 1.194 +++ package-index 2005/02/19 20:48:55 1.195 ＠＠ -1636,19 +1636,19 ＠＠ (package-get-update-base-entry (quote (viper (standards-version 1.1 - version "1.37" + version "1.38" author-version "3.09" - date "2003-10-31" - build-date "2003-10-31" + date "2005-02-19" + build-date "2005-02-19" maintainer "Michael Kifer <kifer(a)cs.sunysb.edu>" distribution xemacs priority low category "standard" dump nil description "VI emulation support." - filename "viper-1.37-pkg.tar.gz" - md5sum "5bd6157ea98d1cc9399e91eb3b684c8c" - size 327719 + filename "viper-1.38-pkg.tar.gz" + md5sum "68a848586e6599bbebc7ec5009ab3e70" + size 329307 provides (viper-cmd viper-ex viper-init viper-keym viper-macs viper-mous viper-util viper) requires (xemacs-base) type regular 1.188 +2 -2 XEmacs/xemacs-builds/viteno/setup-packages.ini Index: setup-packages.ini =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs-builds/viteno/setup-packages.ini,v retrieving revision 1.187 retrieving revision 1.188 diff -u -r1.187 -r1.188 --- setup-packages.ini 2005/02/19 11:54:49 1.187 +++ setup-packages.ini 2005/02/19 20:48:55 1.188 ＠＠ -208,8 +208,8 ＠＠ install: packages/tpu-1.14-pkg.tar.gz 59529 ＠ viper -version: 1.37 -install: packages/viper-1.37-pkg.tar.gz 327719 +version: 1.38 +install: packages/viper-1.38-pkg.tar.gz 329307 ＠ eterm version: 1.15

1 participants
0 comments

CVS update by viteno MODIFIED: packages/xemacs-packages/viper ... 19 years, 10 months

CVS Monitor

User: viteno Date: 05/02/19 21:36:50 Modified: packages/xemacs-packages/viper ChangeLog Makefile Log: Increment VERSION in Makefile Revision Changes Path 1.52 +4 -0 XEmacs/packages/xemacs-packages/viper/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/ChangeLog,v retrieving revision 1.51 retrieving revision 1.52 diff -u -r1.51 -r1.52 --- ChangeLog 2005/02/19 19:30:05 1.51 +++ ChangeLog 2005/02/19 20:36:50 1.52 ＠＠ -1,3 +1,7 ＠＠ +2005-02-19 Norbert Koch <viteno(a)xemacs.org> + + * Makefile (VERSION): XEmacs package 1.38 released. + 2005-02-19 Michael Kifer <kifer(a)cs.stonybrook.edu> * viper-cmd.el (viper-prefix-commands): make into a defconst. 1.46 +1 -1 XEmacs/packages/xemacs-packages/viper/Makefile Index: Makefile =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/Makefile,v retrieving revision 1.45 retrieving revision 1.46 diff -u -r1.45 -r1.46 --- Makefile 2003/10/31 17:14:39 1.45 +++ Makefile 2005/02/19 20:36:50 1.46 ＠＠ -17,7 +17,7 ＠＠ # the Free Software Foundation, Inc., 59 Temple Place - Suite 330, # Boston, MA 02111-1307, USA. -VERSION = 1.37 +VERSION = 1.38 AUTHOR_VERSION = 3.09 MAINTAINER = Michael Kifer <kifer(a)cs.sunysb.edu> PACKAGE = viper

1 participants
0 comments

CVS update by viteno MODIFIED: packages ... 19 years, 10 months

CVS Monitor

User: viteno Date: 05/02/19 21:36:26 Modified: packages ChangeLog Log: Package release Revision Changes Path 1.503 +2 -0 XEmacs/packages/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/ChangeLog,v retrieving revision 1.502 retrieving revision 1.503 diff -u -r1.502 -r1.503 --- ChangeLog 2005/02/19 11:41:28 1.502 +++ ChangeLog 2005/02/19 20:36:25 1.503 ＠＠ -1,5 +1,7 ＠＠ 2005-02-19 Norbert Koch <viteno(a)xemacs.org> + * Packages released: viper. + * Packages released: ediff. 2005-02-16 Norbert Koch <viteno(a)xemacs.org>

1 participants
0 comments

CVS update by michaelk MODIFIED: packages/xemacs-packages/viper, viper-util.el, viper-init.el ... 19 years, 10 months

CVS Monitor

User: michaelk Date: 05/02/19 20:30:10 Modified: packages/xemacs-packages/viper viper.texi viper.el viper-util.el viper-macs.el viper-keym.el viper-init.el viper-ex.el viper-cmd.el ChangeLog Log: * viper-cmd.el (viper-prefix-commands): make into a defconst. (viper-exec-buffer-search): use regexp-quote to quote the buffer string. (viper-minibuffer-setup-sentinel): make some variables buffer-local. (viper-skip-separators): bug fix. (viper-set-searchstyle-toggling-macros): allow to unset macros in a particular major mode. (viper-del-backward-char-in-replace): don't put deleted char on the kill ring. * viper-ex.el (viper-color-display-p): new function. (viper-has-face-support-p): use viper-color-display-p. * viper-keym.el (viper-gnus-modifier-map): new keymap. * viper-macs.el (viper-unrecord-kbd-macro): bug fix. * viper-util.el (viper-glob-unix-files): fix shell status check. (viper-file-remote-p): make equivalent to file-remote-p. * viper.el (viper-major-mode-modifier-list): use viper-gnus-modifier-map. Revision Changes Path 1.26 +52 -31 XEmacs/packages/xemacs-packages/viper/viper.texi Index: viper.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper.texi,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- viper.texi 2002/10/16 06:16:26 1.25 +++ viper.texi 2005/02/19 19:30:03 1.26 ＠＠ -314,8 +314,8 ＠＠ Viper defines ＠kbd{C-\} as its Meta key in Vi state. ＠xref{Vi State}, for more info.＠refill -Emacs is structured as a lisp interpreter around a C core. Emacs keys -cause lisp functions to be called. It is possible to call these +Emacs is structured as a Lisp interpreter around a C core. Emacs keys +cause Lisp functions to be called. It is possible to call these functions directly, by typing ＠kbd{M-x function-name}. ＠node Loading Viper, States in Viper, Emacs Preliminaries, Overview ＠＠ -596,7 +596,7 ＠＠ Viper uses Emacs Regular Expressions for searches. These are a superset of Vi regular expressions, excepting the change-of-case escapes ＠samp{\u}, ＠samp{\L}, -＠dots{}, etc. ＠xref{Regular Expressions,,Regular Expressions,emacs,The +＠dots{}, etc. ＠xref{Regexps,,Syntax of Regular Expressions,emacs,The GNU Emacs Manual}, for details. Files specified to ＠kbd{:e} use ＠code{csh} regular expressions (globbing, wildcards, what have you). ＠＠ -1194,7 +1194,7 ＠＠ from the menubar. Viper customization group is located under the ＠emph{Emulations} customization group, which in turn is under the ＠emph{Editing} group (or simply by typing ＠kbd{:customize}). All Viper -faces are grouped together under Viper's +faces are grouped together under Viper's ＠emph{Highlighting} group. Try it: it is really simple! ＠＠ -1312,7 +1312,7 ＠＠ hit ＠kbd{C-x} followed by ＠kbd{2}, then the current window will be split into 2. Except for novice users, ＠kbd{C-c} is also set to execute an Emacs command from the current major mode. ＠key{ESC} will do the same, if you -configure ＠key{ESC} as Meta by setting ＠code{viper-no-multiple-ESC} to nil +configure ＠key{ESC} as Meta by setting ＠code{viper-no-multiple-ESC} to ＠code{nil} in ＠file{.viper}. ＠xref{Customization}. ＠kbd{C-\} in Insert, Replace, or Vi states will make Emacs think ＠kbd{Meta} has been hit.＠refill ＠item \ ＠＠ -1742,18 +1742,18 ＠＠ Setting this variable too high may slow down your typing. Setting it too low may make it hard to type macros quickly enough. -＠item viper-translate-all-ESC-keysequences t on tty, nil on windowing display +＠item viper-translate-all-ESC-keysequences ＠code{t} on tty, ＠code{nil} on windowing display Normally, Viper lets Emacs translate only those ESC key sequences that are defined in the low-level key-translation-map or function-key-map, such as those emitted by the arrow and function keys. Other sequences, e.g., ＠kbd{\\e/}, are treated as ＠kbd{ESC} command followed by a ＠kbd{/}. This is good for people who type fast and tend to hit other characters right after they hit -ESC. Other people like Emacs to translate ＠kbd{ESC} sequences all the time. +ESC. Other people like Emacs to translate ＠kbd{ESC} sequences all the time. The default is to translate all sequences only when using a dumb terminal. This permits you to use ＠kbd{ESC} as a meta key in insert mode. For instance, hitting ＠kbd{ESC x} fast would have the effect of typing ＠kbd{M-x}. If your dumb terminal is not so dumb and understands the meta key, then you -probably will be better off setting this variable to nil. Try and see which +probably will be better off setting this variable to ＠code{nil}. Try and see which way suits you best. ＠item viper-ex-style-motion t Set this to ＠code{nil}, if you want ＠kbd{l,h} to cross ＠＠ -1764,8 +1764,8 ＠＠ at the beginning of a line in Insert state, ＠key{X} and ＠key{x} to delete characters across lines in Vi command state, etc. ＠item viper-ESC-moves-cursor-back t -It t, cursor moves back 1 character when switching from insert state to vi -state. If nil, the cursor stays where it was before the switch. +It ＠code{t}, cursor moves back 1 character when switching from insert state to vi +state. If ＠code{nil}, the cursor stays where it was before the switch. ＠item viper-always t ＠code{t} means: leave it to Viper to decide when a buffer must be brought up in Vi state, ＠＠ -1873,17 +1873,17 ＠＠ insert state. ＠item viper-replace-region-end-delimiter "$" A string used to mark the end of replacement regions. It is used only on -TTYs or if ＠code{viper-use-replace-region-delimiters} is non-nil. +TTYs or if ＠code{viper-use-replace-region-delimiters} is non-＠code{nil}. ＠item viper-replace-region-start-delimiter "" A string used to mark the beginning of replacement regions. It is used -only on TTYs or if ＠code{viper-use-replace-region-delimiters} is non-nil. +only on TTYs or if ＠code{viper-use-replace-region-delimiters} is non-＠code{nil}. ＠item viper-use-replace-region-delimiters -If non-nil, Viper will always use ＠code{viper-replace-region-end-delimiter} and +If non-＠code{nil}, Viper will always use ＠code{viper-replace-region-end-delimiter} and ＠code{viper-replace-region-start-delimiter} to delimit replacement regions, even on color displays (where this is unnecessary). By default, this -variable is non-nil only on TTYs or monochrome displays. +variable is non-＠code{nil} only on TTYs or monochrome displays. ＠item viper-allow-multiline-replace-regions t -If non-nil, multi-line text replacement regions, such as those produced by +If non-＠code{nil}, multi-line text replacement regions, such as those produced by commands ＠kbd{c55w}, ＠kbd{3C}, etc., will stay around until the user exits the replacement mode. In this variable is set to ＠code{nil}, Viper will emulate the standard Vi behavior, which supports only intra-line ＠＠ -2035,7 +2035,7 ＠＠＠code{viper-insert-global-user-map}, and ＠code{viper-emacs-global-user-map}, as explained below. Each of these key maps affects the corresponding Viper state. The keymap ＠code{viper-insert-global-user-map} also affects Viper's Replace -state. +state. ＠noindent If you want to ＠＠ -2066,7 +2066,7 ＠＠＠end example ＠noindent -Each Emacs command key calls some lisp function. If you have enabled the +Each Emacs command key calls some Lisp function. If you have enabled the Help, (＠pxref{Rudimentary Changes}) ＠kbd{C-h k} will show you the function for each specific key; ＠kbd{C-h b} will show all bindings, and ＠kbd{C-h m} will provide information on the major mode in effect. If Help is not ＠＠ -2219,7 +2219,7 ＠＠＠code{viper-want-emacs-keys-in-vi} and ＠code{viper-want-emacs-keys-in-insert} to ＠code{nil}). If ＠code{viper-always} is set to ＠code{t} (which is the default), Viper -will try to bring each buffer +will try to bring each buffer in the Viper state that is most appropriate for that buffer. Usually, this would be the Vi state, but sometimes it could be the Insert state or the Emacs state. ＠＠ -2285,7 +2285,7 ＠＠ bind common keys to specialized commands. This might make sense for modes that bind only a small number of common keys. For instance, Viper subverts the Shell mode by changing the bindings for ＠kbd{C-m} and ＠kbd{C-d} using -＠code{viper-add-local-keys} described in section on customization +＠code{viper-add-local-keys} described in the section on customization (＠pxref{Customization}). In some cases, some ＠emph{minor} modes might override certain essential ＠＠ -2294,7 +2294,7 ＠＠＠code{M-x viper-mode} will correct the situation. Viper knows about several such minor modes and takes care of them, so the above trick is usually not necessary. If you find that some minor mode, e.g., -(a)code{nasty-mode.el} interferes with Viper, putting the following in +＠code{nasty-mode} interferes with Viper, putting the following in ＠file{.viper} should fix the problem: ＠lisp (viper-harness-minor-mode "nasty-mode") ＠＠ -2305,7 +2305,7 ＠＠ It may not be always obvious which minor mode is at fault. The only guidance here is to look into the file that defines the minor mode you are -suspecting, say ＠code{nasty-mode.el}, and see if it has a variable called +suspecting, say ＠file{nasty-mode.el}, and see if it has a variable called ＠code{nasty-mode-map}. Then check if there is a statement of the form ＠lisp (define-key nasty-mode-map key function) ＠＠ -2316,6 +2316,18 ＠＠ suspicion is wrong, no harm is done if you harness a minor mode that doesn't need to be harnessed. +It is recommended to harness even those minor modes that don't override +Viper keys, but still have their own keymaps. A general way to +make a minor mode, ＠code{my-mode}, +compatible with Viper is to have the file ＠file{my-mode.el} include the following code: + +＠lisp +(when (fboundp 'viper-harness-minor-mode) + (let ((lib (file-name-sans-extension + (file-name-nondirectory load-file-name)))) + (viper-harness-minor-mode lib))) +＠end lisp + ＠vindex ＠code{viper-want-emacs-keys-in-vi} ＠vindex ＠code{viper-want-emacs-keys-in-insert} ＠vindex ＠code{viper-always} ＠＠ -2371,11 +2383,19 ＠＠＠end example ＠findex ＠code{viper-set-searchstyle-toggling-macros} +If you don't like this feature as a default, but would still like to have +it in some major modes, you can do so by first unsetting it globally, as +shown above, and then setting it in the desired major modes as follows: +＠example +(viper-set-searchstyle-toggling-macros nil 'c-mode) +(viper-set-searchstyle-toggling-macros nil 'lisp-mode) +＠end example + ＠item Vi-isms in Emacs state Some people find it useful to use the Vi-style search key, `/', to invoke search in modes which Viper leaves in emacs-state. These modes are: -＠code{dired-mode}, ＠code{mh-folder-mode}, ＠code{gnus-group-mode}, -＠code{gnus-summary-mode}, ＠code{Info-mode}, and ＠code{Buffer-menu-mode} +＠code{dired-mode}, ＠code{mh-folder-mode}, +＠code{Info-mode}, and ＠code{Buffer-menu-mode} (more may be added in the future). So, in the above modes, Viper binds `/' so that it will behave Vi-style. Furthermore, in those major modes, Viper binds `:' to invoke ex-style commands, like in vi-state. And, as described ＠＠ -2390,7 +2410,7 ＠＠ To unbind the macros `//' and `///' for a major mode where you feel they are undesirable, execute ＠code{viper-set-emacs-state-searchstyle-macros} with a -non-nil argument. This can be done either interactively, by supplying a +non-＠code{nil} argument. This can be done either interactively, by supplying a prefix argument, or by placing ＠example (viper-set-emacs-state-searchstyle-macros 'undefine) ＠＠ -2661,7 +2681,7 ＠＠ purpose of mouse search and mouse insert. By default, this is set to ＠code{double-click-time} in Emacs and to ＠code{mouse-track-multi-click-time} milliseconds in XEmacs. -＠end table +＠end table ＠kindex ＠kbd{S-Mouse-1} ＠kindex ＠kbd{S-Mouse-2} ＠kindex ＠kbd{meta shift button1up} ＠＠ -2731,7 +2751,7 ＠＠ specially, if this key sequence is bound to a macro. Viper provides Vi-style keyboard macros through the usual Ex commands, -＠kbd{:map} and +＠kbd{:map} and ＠kbd{:map!}. These macros are much more powerful in Viper than they are in the original Vi and in other emulators. This is because Viper implements an enhanced vi-style ＠＠ -2779,7 +2799,7 ＠＠ macros) lets the user define keyboard macros that ask for confirmation or even prompt the user for input and then continue. To do this, one should type ＠kbd{C-x q} (for confirmation) or ＠kbd{C-u C-x q} (for prompt). -For details, ＠pxref{Kbd Macro Query,,Customization,emacs,The GNU Emacs +For details, ＠pxref{Keyboard Macro Query,,Customization,emacs,The GNU Emacs Manual} ＠refill When the user finishes defining a macro (which is done by typing ＠kbd{C-x)} --- ＠＠ -3143,7 +3163,7 ＠＠ We also use ＠samp{word} for alphanumeric/non-alphanumeric words, and ＠samp{WORD} for whitespace delimited words. ＠samp{char} refers to any -ASCII character, ＠samp{CHAR} to non-whitespace character. +＠acronym{ASCII} character, ＠samp{CHAR} to non-whitespace character. Brackets ＠samp{[]} indicate optional parameters; ＠samp{<count>} also optional, usually defaulting to 1. Brackets are elided for ＠samp{<count>} to eschew obfuscation. ＠＠ -3363,7 +3383,7 ＠＠ Find the next bracket/parenthesis/brace and go to its match. By default, Viper ignores brackets/parentheses/braces that occur inside parentheses. You can change this by setting -＠code{viper-parse-sexp-ignore-comments} to nil in your ＠file{.viper} file. +＠code{viper-parse-sexp-ignore-comments} to ＠code{nil} in your ＠file{.viper} file. This option can also be toggled interactively if you quickly hit ＠kbd{%%%}. This latter feature is implemented as a vi-style keyboard macro. If you ＠＠ -4047,8 +4067,8 ＠＠＠item :args List files not shown anywhere with counts for next ＠item :n [count] [+<cmd>] [<files>] -Edit <count> file, or edit files. The count comes from ＠kbd{:args}. -＠item :N [count] [+<cmd>] [<files>] +Edit <count> file, or edit files. The count comes from ＠kbd{:args}. +＠item :N [count] [+<cmd>] [<files>] Like ＠kbd{:n}, but the meaning of the variable ＠var{ex-cycle-other-window} is reversed. ＠item :b ＠＠ -4475,6 +4495,7 ＠＠ gvr＠(a)halcyon.com (George V.＠: Reilly), hatazaki＠(a)bach.convex.com (Takao Hatazaki), hpz＠(a)ibmhpz.aug.ipp-garching.mpg.de (Hans-Peter Zehrfeld), +irie＠(a)t.email.ne.jp (Irie Tetsuya), jackr＠(a)dblues.engr.sgi.com (Jack Repenning), jamesm＠(a)bga.com (D.J.＠: Miller II), jjm＠(a)hplb.hpl.hp.com (Jean-Jacques Moreau), 1.27 +5 -5 XEmacs/packages/xemacs-packages/viper/viper.el Index: viper.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper.el,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- viper.el 2003/05/18 17:57:25 1.26 +++ viper.el 2005/02/19 19:30:04 1.27 ＠＠ -3,12 +3,12 ＠＠ ;; and a venomous VI PERil. ;; Viper Is also a Package for Emacs Rebels. -;; Copyright (C) 1994, 95, 96, 97, 98, 99, 2000, 01, 02 Free Software Foundation, Inc. +;; Copyright (C) 1994, 95, 96, 97, 98, 99, 2000, 01, 02, 05 Free Software Foundation, Inc. ;; Author: Michael Kifer <kifer(a)cs.stonybrook.edu> ;; Keywords: emulations -(defconst viper-version "3.11.2 of January 4, 2002" +(defconst viper-version "3.11.4 of February 19, 2005" "The current version of Viper") ;; This file is part of GNU Emacs. ＠＠ -466,7 +466,7 ＠＠ (nth 0 triple) (nth 1 triple) (eval (nth 2 triple)))) viper-major-mode-modifier-list)) -;; We change standard bindings in some major mode, making them slightly +;; We change standard bindings in some major modes, making them slightly ;; different than in "normal" vi/insert/emacs states (defcustom viper-major-mode-modifier-list '((help-mode emacs-state viper-slash-and-colon-map) ＠＠ -482,8 +482,8 ＠＠ (dired-mode emacs-state viper-dired-modifier-map) (tar-mode emacs-state viper-slash-and-colon-map) (mh-folder-mode emacs-state viper-slash-and-colon-map) - (gnus-group-mode emacs-state viper-slash-and-colon-map) - (gnus-summary-mode emacs-state viper-slash-and-colon-map) + (gnus-group-mode emacs-state viper-gnus-modifier-map) + (gnus-summary-mode emacs-state viper-gnus-modifier-map) (Info-mode emacs-state viper-slash-and-colon-map) (Buffer-menu-mode emacs-state viper-slash-and-colon-map) ) 1.20 +13 -19 XEmacs/packages/xemacs-packages/viper/viper-util.el Index: viper-util.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper-util.el,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- viper-util.el 2003/05/18 17:57:25 1.19 +++ viper-util.el 2005/02/19 19:30:04 1.20 ＠＠ -394,17 +394,17 ＠＠ command))) (goto-char (point-min)) ;; Issue an error, if no match. - (if (> status 0) - (save-excursion - (skip-chars-forward " \t\n\j") - (if (looking-at "ls:") - (viper-forward-Word 1)) - (error "%s: %s" - (if (stringp gshell) - gshell - "shell") - (buffer-substring (point) (viper-line-pos 'end))) - )) + (unless (eq 0 status) + (save-excursion + (skip-chars-forward " \t\n\j") + (if (looking-at "ls:") + (viper-forward-Word 1)) + (error "%s: %s" + (if (stringp gshell) + gshell + "shell") + (buffer-substring (point) (viper-line-pos 'end))) + )) (goto-char (point-min)) (viper-get-filenames-from-buffer 'one-per-line)) )) ＠＠ -662,14 +662,8 ＠＠ ;; define remote file test -(or (fboundp 'viper-file-remote-p) ; user supplied his own function: use it - (defun viper-file-remote-p (file-name) - (car (cond ((featurep 'efs-auto) (efs-ftp-path file-name)) - ((fboundp 'file-remote-p) (file-remote-p file-name)) - (t (require 'ange-ftp) - ;; Can happen only in Emacs, since XEmacs has file-remote-p - (ange-ftp-ftp-name file-name)))))) - +(defun viper-file-remote-p (file-name) + (file-remote-p file-name)) ;; This is a simple-minded check for whether a file is under version control. 1.7 +25 -18 XEmacs/packages/xemacs-packages/viper/viper-macs.el Index: viper-macs.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper-macs.el,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- viper-macs.el 2003/05/18 17:57:25 1.6 +++ viper-macs.el 2005/02/19 19:30:04 1.7 ＠＠ -329,6 +329,8 ＠＠ ;; Accepts as macro names: strings and vectors. ;; strings must be strings of characters; vectors must be vectors of keys ;; in canonic form. The canonic form is essentially the form used in XEmacs +;; More general definitions are inherited by more specific scopes: +;; global->major mode->buffer. More specific definitions override more general (defun viper-record-kbd-macro (macro-name state macro-body &optional scope) "Record a Vi macro. Can be used in `.viper' file to define permanent macros. MACRO-NAME is a string of characters or a vector of keys. STATE is ＠＠ -451,22 +453,22 ＠＠ (list (list (cons scope nil)) nil (cons t nil)))))) (setq old-elt (assoc macro-name (eval macro-alist-var))) - (if (null old-elt) - (progn - ;; insert new-elt in macro-alist-var and keep the list sorted - (define-key - keymap - (vector (viper-key-to-emacs-key (aref macro-name 0))) - 'viper-exec-mapped-kbd-macro) - (setq lis (eval macro-alist-var)) - (while (and lis (string< (viper-array-to-string (car (car lis))) - (viper-array-to-string macro-name))) - (setq lis2 (cons (car lis) lis2)) - (setq lis (cdr lis))) - - (setq lis2 (reverse lis2)) - (set macro-alist-var (append lis2 (cons new-elt lis))) - (setq old-elt new-elt))) + (if (null old-elt) + (progn + ;; insert new-elt in macro-alist-var and keep the list sorted + (define-key + keymap + (vector (viper-key-to-emacs-key (aref macro-name 0))) + 'viper-exec-mapped-kbd-macro) + (setq lis (eval macro-alist-var)) + (while (and lis (string< (viper-array-to-string (car (car lis))) + (viper-array-to-string macro-name))) + (setq lis2 (cons (car lis) lis2)) + (setq lis (cdr lis))) + + (setq lis2 (reverse lis2)) + (set macro-alist-var (append lis2 (cons new-elt lis))) + (setq old-elt new-elt))) (setq old-sub-elt (cond ((eq scope t) (viper-kbd-global-pair old-elt)) ((symbolp scope) (assoc scope (viper-kbd-mode-alist old-elt))) ＠＠ -484,6 +486,11 ＠＠ ;; macro name must be a vector of viper-style keys +;; viper-unrecord-kbd-macro doesn't have scope. Macro definitions are inherited +;; from global -> major mode -> buffer +;; More specific definition overrides more general +;; Can't unrecord definition for more specific, if a more general definition is +;; in effect (defun viper-unrecord-kbd-macro (macro-name state) "Delete macro MACRO-NAME from Viper STATE. MACRO-NAME must be a vector of viper-style keys. This command is used by Viper ＠＠ -546,7 +553,7 ＠＠ (setq macro-pair mode-mapping) (message "%S is unmapped for %s in %S" (viper-display-macro macro-name) state-name major-mode)) - ((cdr (setq macro-pair (viper-kbd-global-pair macro-entry))) + ((cdr (setq macro-pair global-mapping)) (message "Global mapping for %S in %s is removed" (viper-display-macro macro-name) state-name)) ＠＠ -560,7 +567,7 ＠＠ (progn (set macro-alist-var (delq macro-entry (eval macro-alist-var))) (if (viper-can-release-key (aref macro-name 0) - (eval macro-alist-var)) + (eval macro-alist-var)) (define-key keymap (vector (viper-key-to-emacs-key (aref macro-name 0))) 1.9 +4 -0 XEmacs/packages/xemacs-packages/viper/viper-keym.el Index: viper-keym.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper-keym.el,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- viper-keym.el 2003/05/18 17:57:25 1.8 +++ viper-keym.el 2005/02/19 19:30:04 1.9 ＠＠ -455,6 +455,10 ＠＠ (define-key viper-dired-modifier-map ":" 'viper-ex) (define-key viper-dired-modifier-map "/" 'viper-search-forward) +(defvar viper-gnus-modifier-map (make-sparse-keymap) + "This map modifies Gnus behavior.") +(define-key viper-gnus-modifier-map ":" 'viper-ex) + ;;; Code 1.15 +11 -0 XEmacs/packages/xemacs-packages/viper/viper-init.el Index: viper-init.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper-init.el,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- viper-init.el 2003/05/18 17:57:25 1.14 +++ viper-init.el 2005/02/19 19:30:04 1.15 ＠＠ -70,6 +70,16 ＠＠ window-system )) +(defun viper-color-display-p () + (condition-case nil + (viper-cond-compile-for-xemacs-or-emacs + (eq (device-class (selected-device)) 'color) ; xemacs form + (if (fboundp 'display-color-p) ; emacs form + (display-color-p) + (x-display-color-p)) + ) + (error nil))) + ;; in XEmacs: device-type is tty on tty and stream in batch. (defun viper-window-display-p () (and (viper-device-type) (not (memq (viper-device-type) '(tty stream pc))))) ＠＠ -97,6 +107,7 ＠＠ (defun viper-has-face-support-p () (cond ((viper-window-display-p)) (viper-force-faces) + ((viper-color-display-p)) (viper-emacs-p (memq (viper-device-type) '(pc))) (viper-xemacs-p (memq (viper-device-type) '(tty pc))))) 1.20 +2 -2 XEmacs/packages/xemacs-packages/viper/viper-ex.el Index: viper-ex.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper-ex.el,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- viper-ex.el 2003/05/18 17:57:25 1.19 +++ viper-ex.el 2005/02/19 19:30:05 1.20 ＠＠ -1,6 +1,6 ＠＠ ;;; viper-ex.el --- functions implementing the Ex commands for Viper -;; Copyright (C) 1994, 95, 96, 97, 98, 2000, 01, 02 Free Software Foundation, Inc. +;; Copyright (C) 1994, 95, 96, 97, 98, 2000, 01, 02, 04, 05 Free Software Foundation, Inc. ;; Author: Michael Kifer <kifer(a)cs.stonybrook.edu> ＠＠ -1458,7 +1458,7 ＠＠ (if (eq 1 (length name)) (setq char (string-to-char name)) (error "`%s': Spurious text \"%s\" after mark name" - name (substring name 1) viper-SpuriousText)) + name (substring name 1))) (save-window-excursion (setq viper-ex-work-buf (get-buffer-create viper-ex-work-buf-name)) (set-buffer viper-ex-work-buf) 1.25 +49 -29 XEmacs/packages/xemacs-packages/viper/viper-cmd.el Index: viper-cmd.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/viper-cmd.el,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- viper-cmd.el 2003/05/18 17:57:25 1.24 +++ viper-cmd.el 2005/02/19 19:30:05 1.25 ＠＠ -1063,7 +1063,7 ＠＠ ;; call the actual function to execute ESC (if no other symbols followed) ;; or the key bound to the ESC sequence (if the sequence was issued - ;; with very short delay between characters. + ;; with very short delay between characters). (if (eq cmd 'viper-intercept-ESC-key) (setq cmd (cond ((eq viper-current-state 'vi-state) ＠＠ -1529,7 +1529,8 ＠＠ nil) (defun viper-exec-buffer-search (m-com com) - (setq viper-s-string (buffer-substring (point) viper-com-point)) + (setq viper-s-string + (regexp-quote (buffer-substring (point) viper-com-point))) (setq viper-s-forward t) (setq viper-search-history (cons viper-s-string viper-search-history)) (setq viper-intermediate-command 'viper-exec-buffer-search) ＠＠ -1982,6 +1983,16 ＠＠ (let ((hook (if viper-vi-style-in-minibuffer 'viper-change-state-to-insert 'viper-change-state-to-emacs))) + ;; making buffer-local variables so that normal buffers won't affect the + ;; minibuffer and vice versa. Otherwise, command arguments will affect + ;; minibuffer ops and insertions from the minibuffer will change those in + ;; the normal buffers + (make-local-variable 'viper-d-com) + (make-local-variable 'viper-last-insertion) + (make-local-variable 'viper-command-ring) + (setq viper-d-com nil + viper-last-insertion nil + viper-command-ring nil) (funcall hook) )) ＠＠ -2707,7 +2718,7 ＠＠ (viper-backward-char-carefully) (if (looking-at "\n") (viper-skip-all-separators-backward 'within-line) - (or (bobp) (forward-char))))) + (or (viper-looking-at-separator) (forward-char))))) (defun viper-forward-word-kernel (val) ＠＠ -3630,33 +3641,39 ＠＠ (setq msg "Search style remains unchanged"))) (princ msg t))) -(defun viper-set-searchstyle-toggling-macros (unset) +(defun viper-set-searchstyle-toggling-macros (unset &optional major-mode) "Set the macros for toggling the search style in Viper's vi-state. The macro that toggles case sensitivity is bound to `//', and the one that toggles regexp search is bound to `///'. -With a prefix argument, this function unsets the macros. " +With a prefix argument, this function unsets the macros. +If MAJOR-MODE is set, set the macros only in that major mode." (interactive "P") - (or noninteractive - (if (not unset) - (progn - ;; toggle case sensitivity in search - (viper-record-kbd-macro - "//" 'vi-state - [1 (meta x) v i p e r - t o g g l e - s e a r c h - s t y l e return] - 't) - ;; toggle regexp/vanila search - (viper-record-kbd-macro - "///" 'vi-state - [2 (meta x) v i p e r - t o g g l e - s e a r c h - s t y l e return] - 't) - (if (interactive-p) - (message - "// and /// now toggle case-sensitivity and regexp search"))) - (viper-unrecord-kbd-macro "//" 'vi-state) - (sit-for 2) - (viper-unrecord-kbd-macro "///" 'vi-state)))) - - + (let (scope) + (if (and major-mode (symbolp major-mode)) + (setq scope major-mode) + (setq scope 't)) + (or noninteractive + (if (not unset) + (progn + ;; toggle case sensitivity in search + (viper-record-kbd-macro + "//" 'vi-state + [1 (meta x) v i p e r - t o g g l e - s e a r c h - s t y l e return] + scope) + ;; toggle regexp/vanila search + (viper-record-kbd-macro + "///" 'vi-state + [2 (meta x) v i p e r - t o g g l e - s e a r c h - s t y l e return] + scope) + (if (interactive-p) + (message + "// and /// now toggle case-sensitivity and regexp search"))) + (viper-unrecord-kbd-macro "//" 'vi-state) + (sit-for 2) + (viper-unrecord-kbd-macro "///" 'vi-state))) + )) + + (defun viper-set-parsing-style-toggling-macro (unset) "Set `%%%' to be a macro that toggles whether comment fields should be parsed for matching parentheses. This is used in conjunction with the `%' command. ＠＠ -4112,7 +4129,8 ＠＠ (interactive) (if (and viper-ex-style-editing (bolp)) (beep 1) - (delete-backward-char 1 t))) + ;; don't put on kill ring + (delete-backward-char 1 nil))) (defun viper-del-backward-char-in-replace () ＠＠ -4124,13 +4142,15 ＠＠ (interactive) (cond (viper-delete-backwards-in-replace (cond ((not (bolp)) - (delete-backward-char 1 t)) + ;; don't put on kill ring + (delete-backward-char 1 nil)) (viper-ex-style-editing (beep 1)) ((bobp) (beep 1)) (t - (delete-backward-char 1 t)))) + ;; don't put on kill ring + (delete-backward-char 1 nil)))) (viper-ex-style-editing (if (bolp) (beep 1) 1.51 +26 -1 XEmacs/packages/xemacs-packages/viper/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/viper/ChangeLog,v retrieving revision 1.50 retrieving revision 1.51 diff -u -r1.50 -r1.51 --- ChangeLog 2003/10/31 17:14:39 1.50 +++ ChangeLog 2005/02/19 19:30:05 1.51 ＠＠ -1,3 +1,28 ＠＠ +2005-02-19 Michael Kifer <kifer(a)cs.stonybrook.edu> + + * viper-cmd.el (viper-prefix-commands): make into a defconst. + (viper-exec-buffer-search): use regexp-quote to quote the buffer + string. + (viper-minibuffer-setup-sentinel): make some variables buffer-local. + (viper-skip-separators): bug fix. + (viper-set-searchstyle-toggling-macros): allow to unset macros in a + particular major mode. + (viper-del-backward-char-in-replace): don't put deleted char on the + kill ring. + + * viper-ex.el (viper-color-display-p): new function. + (viper-has-face-support-p): use viper-color-display-p. + + * viper-keym.el (viper-gnus-modifier-map): new keymap. + + * viper-macs.el (viper-unrecord-kbd-macro): bug fix. + + * viper-util.el (viper-glob-unix-files): fix shell status check. + (viper-file-remote-p): make equivalent to file-remote-p. + + * viper.el (viper-major-mode-modifier-list): use + viper-gnus-modifier-map. + 2003-10-31 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.37 released. ＠＠ -6,7 +31,7 ＠＠ * Makefile (VERSION): XEmacs package 1.36 released. -2002-05-18 Michael Kifer <kifer(a)cs.stonybrook.edu> +2003-05-18 Michael Kifer <kifer(a)cs.stonybrook.edu> * all files: eliminated trailing spaces from lines.

1 participants
0 comments

CVS update by stephent MODIFIED: xemacs/man/internals ... 19 years, 10 months

CVS Monitor

User: stephent Date: 05/02/19 17:19:00 Modified: xemacs/man/internals internals.texi Log: autoconf and Xft docs <874qg8msql.fsf(a)tleepslib.sk.tsukuba.ac.jp> Revision Changes Path 1.288 +45 -0 XEmacs/xemacs/man/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/ChangeLog,v retrieving revision 1.287 retrieving revision 1.288 diff -u -r1.287 -r1.288 --- ChangeLog 2005/02/18 06:29:35 1.287 +++ ChangeLog 2005/02/19 16:18:52 1.288 ＠＠ -1,3 +1,48 ＠＠ +2005-02-19 Stephen J. Turnbull <stephen(a)xemacs.org> + + * internals/internals.texi (Introduction to Writing C Code): + Change "mostly warning-free" to "warning-free" to encourage + reporting warnings as bugs. + (The configure Script): + Incorporate Malcolm Purvis's notes from configure.ac. Document + his implementations of keyword and complex options, and remove + descriptions of my obsolete code. + +2005-01-16 Stephen J. Turnbull <stephen(a)xemacs.org> + + * internals/internals.texi (Better Rendering Support -- + Configuration with the Interim Patches): + Improve notes on configuration. + +2004-12-15 Stephen J. Turnbull <stephen(a)xemacs.org> + + * internals/internals.texi (Better Rendering Support -- + Configuration with the Interim Patches): Menubar uses xftFont + resource, too. + +2005-02-03 Stephen J. Turnbull <stephen(a)xemacs.org> + + * internals/internals.texi (XEmacs from the Perspective of + Building): Mention autoconf. + (The Modules of XEmacs): Point Next the The Build Configuration + System and add Modules for Building XEmacs to the menu. + (A Summary of the Various XEmacs Modules): Add Modules for + Building XEmacs to menu, and Modules for Build Configuration, + Modules for Compiling XEmacs, and Modules for Preloading Lisp to + the table of sections. + (Low-Level Modules): Point Previous to Modules for Building XEmacs. + (Modules for Building XEmacs): + (Modules for Build Configuration): + (Modules for Compiling XEmacs): + (Modules for Preloading Lisp): + (The Build Configuration System): + (Adding Configurable Features): + (The configure Script): + (The Makefile Precursors): + New nodes. + (Rules When Writing New C Code): + Point Previous to The Build Configuration System. + 2005-02-18 Stephen J. Turnbull <stephen(a)xemacs.org> * XEmacs 21.5.19 "chives" is released. 1.60 +479 -46 XEmacs/xemacs/man/internals/internals.texi Index: internals.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/internals/internals.texi,v retrieving revision 1.59 retrieving revision 1.60 diff -u -r1.59 -r1.60 --- internals.texi 2005/01/26 09:48:27 1.59 +++ internals.texi 2005/02/19 16:18:56 1.60 ＠＠ -311,6 +311,7 ＠＠ * XEmacs from the Perspective of Building:: * Build-Time Dependencies:: * The Modules of XEmacs:: +* The Build Configuration System:: * Rules When Writing New C Code:: * Regression Testing XEmacs:: * CVS Techniques:: ＠＠ -2409,7 +2410,9 ＠＠ The first step of building involves running the ＠file{configure} program and passing it various parameters to specify any optional features you want and compiler arguments and such, as described in the ＠file{INSTALL} -file. This determines what the build environment is, chooses the +file. (You may optionally run ＠file{autoconf} first to update the +＠file{configure} script. ＠xref{Modules for Build Configuration}.) +This determines what the build environment is, chooses the appropriate ＠file{s/} and ＠file{m/} file, and runs a series of tests to determine many details about your environment, such as which library functions are available and exactly how they work. The reason for ＠＠ -2520,12 +2523,13 ＠＠＠code{custom-declare-variable-list} to prevent the ＠samp{void-variable} error. (Currently this is only needed for ＠file{make-docfile.el}.) -＠node The Modules of XEmacs, Rules When Writing New C Code, Build-Time Dependencies, Top +＠node The Modules of XEmacs, The Build Configuration System, Build-Time Dependencies, Top ＠chapter The Modules of XEmacs ＠cindex modules of XEmacs ＠menu * A Summary of the Various XEmacs Modules:: +* Modules for Building XEmacs:: * Low-Level Modules:: * Basic Lisp Modules:: * Modules for Standard Editing Operations:: ＠＠ -2534,7 +2538,7 ＠＠ * Modules for Interfacing with the Operating System:: ＠end menu -＠node A Summary of the Various XEmacs Modules, Low-Level Modules, The Modules of XEmacs, The Modules of XEmacs +＠node A Summary of the Various XEmacs Modules, Modules for Building XEmacs, The Modules of XEmacs, The Modules of XEmacs ＠section A Summary of the Various XEmacs Modules ＠cindex summary of the various XEmacs modules ＠cindex modules, summary of the various XEmacs ＠＠ -2546,6 +2550,12 ＠＠＠itemize ＠bullet ＠item +＠ref{Modules for Build Configuration}. +＠item +＠ref{Modules for Compiling XEmacs}. +＠item +＠ref{Modules for Preloading Lisp}. +＠item ＠ref{Low-Level Modules}. ＠item ＠ref{Basic Lisp Modules}. ＠＠ -3021,8 +3031,66 ＠＠＠end multitable + +＠node Modules for Building XEmacs, Low-Level Modules, A Summary of the Various XEmacs Modules, The Modules of XEmacs +＠section Modules for Building XEmacs +＠cindex modules for building XEmacs +＠cindex building XEmacs, modules for + +＠menu +* Modules for Build Configuration:: +* Modules for Compiling XEmacs:: +* Modules for Preloading Lisp:: +＠end menu + + + +＠node Modules for Build Configuration, Modules for Compiling XEmacs, Modules for Building XEmacs, Modules for Building XEmacs +＠subsection Modules for Build Configuration +＠cindex modules for build configuration +＠cindex build configuration, modules for + +＠example +＠file{configure} +(a)file{config.h.in} +(a)file{Makefile.in.in} +＠end example + +＠example +(a)file{configure.ac} +(a)file{configure.in} +＠end example + +＠xref{The configure Script}. + + + +＠node Modules for Compiling XEmacs, Modules for Preloading Lisp, Modules for Build Configuration, Modules for Building XEmacs +＠subsection Modules for Compiling XEmacs +＠cindex modules for compiling xemacs +＠cindex compiling xemacs, modules for + +＠strong{Please write this node!} ＠c #### + +This node should contain descriptions of files like the various +Makefiles, and I guess cross-references to ellcc etc. + + -＠node Low-Level Modules, Basic Lisp Modules, A Summary of the Various XEmacs Modules, The Modules of XEmacs +＠node Modules for Preloading Lisp, , Modules for Compiling XEmacs, Modules for Building XEmacs +＠subsection Modules for Preloading Lisp +＠cindex modules for preloading lisp +＠cindex preloading lisp, modules for + +＠strong{Please write this node!} ＠c #### + +This node should contain descriptions of files like dumped-lisp.el +(maybe that goes in Modules for Build Configuration supra?), +update-elcs.el, and so on. + + + +＠node Low-Level Modules, Basic Lisp Modules, Modules for Building XEmacs, The Modules of XEmacs ＠section Low-Level Modules ＠cindex low-level modules ＠cindex modules, low-level ＠＠ -4055,8 +4123,328 ＠＠ This module provides some terminal-control code necessary on versions of AIX prior to 4.1. + + + +＠node The Build Configuration System, Rules When Writing New C Code, The Modules of XEmacs, Top +＠chapter The Build Configuration System +＠cindex build configuration +＠cindex configuration, build + +＠strong{Please write this node!} ＠c #### + +This node should describe XEmacs-specific techniques and idioms in the +configuration system. A particular example is the set of ＠samp{XE_} +macros in ＠file{configure.in} and ＠file{configure.ac}. -＠node Rules When Writing New C Code, Regression Testing XEmacs, The Modules of XEmacs, Top +＠menu +* Adding Configurable Features:: +* The configure Script:: +* The Makefile Precursors:: +＠end menu + + + +＠node Adding Configurable Features, The configure Script, The Build Configuration System, The Build Configuration System +＠section Adding Configurable Features +＠cindex adding configurable features +＠cindex configurable features, adding +＠cindex features, adding configurable + +Adding a configurable feature requires at least adding an option to the +＠file{configure} script and a macro definition to ＠file{src/config.h.in} +(＠pxref{The configure Script}), and often changes to Makefile precursors +(＠pxref{The Makefile Precursors}). + + + +＠node The configure Script, The Makefile Precursors, Adding Configurable Features, The Build Configuration System +＠section The configure Script +＠cindex configure script +＠cindex script, configure + +At the heart of the XEmacs build configuration system is the +＠file{configure} script. This beast is maintained using the Autoconf +system, which is a truly terrifying monstrosity based on a fundamentally +flawed programming model (extensive use of macros), with an +implementation about which I've never heard a nice word (GNU ＠file{m4}), +used to string together a large set of ＠emph{ad hoc} tests, to implement +a configuration language with conventions that are unimportant in simple +cases and counterintuitive when things get complicated. If that doesn't +scare you off, Welcome! I think you're ready to become a configure +hacker! (But be prepared for things to go downhill from here.) + +＠file{configure} is, of course, is written in POSIX shell language, and +autogenerated from a precursor (see? the first step was a doozy!) +Currently that precursor is called ＠file{configure.ac}, but in the +previous generation it was called ＠file{configure.in}. As of February +2005, ＠file{configure.ac} is used in the development mainline, but +because the semantics of many predefined macros changed drastically +between ＠file{autoconf} 2.13 and ＠file{autoconf} 2.50 (why not ``3.0''? +you got me), the XEmacs Project chose to stick with the devil it knew +for the stable line of XEmacs 21.4 releases. + +One reason for worrying about the semantic changes is the fact that +XEmacs uses a lot of homebrew code, including ＠file{m4} macros, to +implement special features in its ＠file{configure} script. Here are +some of the important features: + +＠itemize +＠item +Selectively enabling debugging, error checking, and tracing. +＠item +Complex options, which are set-valued (＠i{i.e.}, unordered; ordered +lists of options, for example ``take the first available from the +list,'' are neither used currently nor given special support). +＠end itemize + +Where these are implemented as ＠file{m4} macros, the prefix ＠samp{XE_} +is used to identify them as XEmacs features in the ＠file{configure} +precursor code. Here is a list of prototypes of the convenience macros +provided for performing common operations: + +＠c #### ＠var{}-ize the formal parameters of these functions? +＠table ＠code +＠item USAGE_ERROR(string) +prints a usage error and dies + +＠item PRINT_VAR(var var ...) +prints values of shell variables + +＠item XE_ADD_OBJS(foo.o ...) +＠strong{#### Please document me!} + +＠item XE_APPEND(value, varname) +＠strong{#### Please document me!} + +＠item XE_PREPEND(value, varname) +＠strong{#### Please document me!} + +＠item XE_DIE(message) +used for situations that can't lead to a successful build, such as +missing include files or conflicts between requested features. + +＠item XE_CHECK_FEATURE_DEPENDENCY(feature1, feature2) +＠strong{#### Please document me!} + +＠item XE_STRIP_4TH_COMPONENT(var) +＠strong{#### Please document me!} + +＠item CANONICALIZE_PATH(varname) +＠strong{#### Please document me!} + +＠item XE_PROTECT_LINKER_FLAGS(shell_var) +＠strong{#### Please document me!} + +＠item COLON_TO_SPACE(path) +Allow use of either ＠samp{:} or spaces for lists of directories. + +＠item XE_ADD_RUNPATH_DIR(directory) +＠strong{#### Please document me!} + +＠item XE_COMPUTE_RUNPATH() +＠strong{#### Please document me!} + +＠item XE_SPACE(var, words) +＠strong{#### Please document me!} + +＠item XE_SHLIB_STUFF +See ＠file{aclocal.m4}. +＠end table + +＠heading XEmacs keyword option support + +A ＠dfn{keyword} option is one that accepts one of a number of +pre-defined values (if support for sets of values is needed, see +``complex options'' below). For example, +＠samp{--with-mail-locking=flock}. + +Keyword options use expanded forms of ＠samp{AC_ARG_[WITH|ENABLE]} called +＠samp{XE_KEYWORD_ARG_[WITH|ENABLE]}, both taking 5 parameters. The +first 4 parameters of these macros are the same as original macros with +the exception that all four parameters are ＠strong{required}. The +＠var{action-if-true} code is run after the argument list has been +parsed. + +The 5th parameter is a list of supported keywords. The whole list must +be quoted but the individual keywords should not. + +If the option value is a not a valid keyword then an error message is +generated, otherwise the value is left untouched. + +This support is implemented via the following ＠file{GNU m4} macros. +Macros labelled ＠dfn{internal} are not expected to be used by +(a)file{configure.ac} programmers; they are part of the implementation of +higher-level features. + +＠table ＠code +＠item XE_KEYWORD_ARG_WITH(package, help-string, action-if-true, action-if-false, [keyword1, keyword2, ....]) +Expanded version of ＠samp{AC_ARG_WITH} for keyword options. All the +parameters are required. The last argument is a comma-separated list of +supported keywords, ＠file{m4}-quoted with ＠samp{[]}. + +＠item XE_KEYWORD_ARG_ENABLE(feature, help-string, action-if-true, action-if-false, [keyword1, keyword2, ....]) +Expanded version of ＠samp{AC_ARG_ENABLE} for keyword options. All the +parameters are required. The last argument is a comma-separated list of +supported keywords, ＠file{m4}-quoted with ＠samp{[]}. + +＠item XE_PARSE_KEYWORD_OPTION(prefix, cmdline-flag) +Internal macro to parse the option values. If an undeclared option is +found then an error is generated. + +＠item XE_KEYWORD(keyword) +Internal macro to declare an option value. + +＠end table + +＠heading XEmacs complex option support + +A ＠dfn{complex option} is one that takes a number of related values, as +a set. For example, we might use "--with-xft=all,nomenubars" for +compatibility with XFontSet i18n of menubars. (The example is +contrived, Xft looks much better than XFS.) Processing such an option +requires a number of auxiliary variables. + +Complex options use expanded forms of ＠samp{AC_ARG_[WITH|ENABLE]} called +＠samp{XE_COMPLEX_ARG_[WITH|ENABLE]}, both taking 5 parameters. The +first 4 parameters of these macros are the same as original macros with +the exception that all four parameters are ＠strong{required}. The +＠var{action-if-true} code is run after the argument list has been +parsed. + +The 5th parameter is a list of ＠samp{XE_COMPLEX_OPTION} macro calls that +define the valid components and their default values. The list must be +quoted but the individual macro calls should not. Here is how the +＠samp{sound} flag is defined: + +＠example +XE_COMPLEX_ARG_ENABLE([sound], + AC_HELP_STRING([--enable-sound],[Compile with sound support. + Valid types are `native', `nas' and `esd'. + Prefix a type with 'no' to disable. + The first type can be `none' or `all'. `none' means + `nonative,nonas,noesd'. `all' means `native,nas,esd'. + Later options override earlier ones for the same TYPE. + The default is to autodetect all sound support except + for ESD which defaults to off.]), + [], + [enable_sound_nas=""], + [XE_COMPLEX_OPTION([native],[""]), + XE_COMPLEX_OPTION([nas],[""]), + XE_COMPLEX_OPTION([esd],[no])]) +＠end example + +(Note that the help string will be reformatted by ＠file{autoconf} so +that all whitespace is first compressed to a single space, then folded +to appear in the right-hand column as above. Thus the help string may +appear differently when ＠code{./configure --help} is invoked.) + +＠c #### verify for INSTALL and xemacs Texinfo. +Each component is interpreted as a separate feature to be enabled or +disabled. As usual, the distinction between ``with'' and ``enable'' is +that ``with'' features require specific support from the system, usually +one or more optional libraries, and ``enable'' features are supported +entirely by code in XEmacs, but the user might want to switch it off for +some reason. Option values are stored in the variables +＠samp{with_＠var{package}_＠var{component}} or +＠samp{enable_＠var{feature}_＠var{component}} (＠i{e.g.} +＠samp{with_xft_menubars}). + +The user of ＠file{configure} specifies the configuration by providing a +list of components. The special components ＠samp{all} and ＠samp{none} +may occur first in the list, setting the defaults for all components to +＠samp{yes} or ＠samp{no} respectively. + +In ＠file{configure.ac}, default values of option values may be +＠samp{yes} which means that the option must be used and an error must +occur if there is a configuration problems (such as a missing library) +or ＠samp{no} which means that the option must not be used. The default +value can also be the null string ＠samp{""}, usually meaning that +＠file{configure} will attempt to find support for the feature on the +system, and will enable the configuration if it is available. Sometimes +the null string means that ＠file{configure}'s default is +system-dependent. (This usage is not consistent, and depends on the +implementation of the feature detector rather than the argument parser.) +Users cannot specify the null string for an individual component from +the command line. + +There are two possible uses in XEmacs for this kind of facility. One is +exemplified by sound: there are alternative protocols (native, ESD, NAS) +and each is supported by a corresponding library. The other is a single +library which may or may not be supported by multiple components of +XEmacs, as exemplified by Xft. This latter usage may be more common +during development of a feature. Perhaps specialized APIs should be +provided, see comment on ＠samp{XE_COMPLEX_OPTION_HELP_STRING} below. + +＠table ＠code +＠item XE_COMPLEX_OPTION(option, yesno) +Declare a complex option and its default value. The value ＠strong{must} +be either ＠samp{yes} or ＠samp{no} or the null string ＠samp{""}. The +null string means ``maybe'', whose semantics are determined by the +implementation of the option, not by the parser. Typical semantics are +``use the library if found in the usual places'' or ``default is +platform-dependent''. + +＠item XE_COMPLEX_OPTION_HELP_STRING(flag, long, short, components, libraries) +Format a boilerplate help string for complex options. + +This was originally written for the Xft option, and doesn't read so well +for options based on alternative libraries like sound. Hackers beware: +the API may be enhanced to deal with this in the future. + +＠item XE_COMPLEX_ARG_WITH(PACKAGE, HELP-STRING, ACTION-IF-TRUE, ACTION-IF-FALSE, [XE_COMPLEX_OPTION(a,yes), ....]) +Extended version of ＠samp{AC_ARG_WITH} for complex options. All the +parameters are required. + +＠item XE_COMPLEX_ARG_ENABLE(FEATURE, HELP-STRING, ACTION-IF-TRUE, ACTION-IF-FALSE, [XE_COMPLEX_OPTION(a,yes), ....]) +Expanded version of ＠samp{AC_ARG_ENABLE} for complex options. All the +parameters are required. + +＠item XE_EXPAND_COMPLEX_OPTION(prefix, component, yesno) +Internal macro create the option's shell variable containing the default +value and to note the values in an option list. + +＠item XE_EXPAND_COMPLEX_OPTIONS(prefix, option_list) +Internal macro which recursively expands an option list. + +＠item XE_INIT_COMPLEX_OPTION(prefix, option_list) +Internal macro to initialise the complex option shell variables. + +Variables of the form ＠samp{＠var{prefix}_＠var{option}} contain the +default value for that option. ＠samp{＠var{prefix}_types} contains a +space-separated list of all the options and ＠samp{＠var{prefix}_default} +contains a comma-separated list of all the default values. + +＠item XE_PARSE_COMPLEX_OPTION(prefix, cmdline-flag) +Internal macro to parse the option values. If an undeclared option is +found then an error is generated. + +＠end table + + + +＠node The Makefile Precursors, , The configure Script, The Build Configuration System +＠section The Makefile Precursors +＠cindex Makefile precursors +＠cindex precursors, Makefile + +＠strong{Please write this node!} ＠c #### + +As in other programs using a ＠file{configure} program, XEmacs's +Makefiles are not written, they are generated. The ＠file{configure} +program uses Makefile precursors, or templates, to generate the actual +Makefiles. In fact, it is a multistage process. The developer changes +the file ＠file{Makefile.in.in}, then ＠file{configure} first generates an +intermediate file ＠file{Makefile.in}, and finally produces a portable +Makefile called ＠file{Makefile}, and a Makefile optimized for ＠file{GNU +make} called ＠file{GNUmakefile}. + +This node describes XEmacs-specific techniques and idioms used in the +(a)file{Makefile.in.in} files. + + + +＠node Rules When Writing New C Code, Regression Testing XEmacs, The Build Configuration System, Top ＠chapter Rules When Writing New C Code ＠cindex writing new C code, rules when ＠cindex C code, rules when writing new ＠＠ -4090,8 +4478,8 ＠＠＠cindex coding conventions The C code is actually written in a dialect of C called ＠dfn{Clean C}, -meaning that it can be compiled, mostly warning-free, with either a C -or C++ compiler. Coding in Clean C has several advantages over plain +meaning that it can be compiled, warning-free, with either a C or C++ +compiler. Coding in Clean C has several advantages over plain C. C++ compilers are more nit-picking, and a number of coding errors have been found by compiling with C++. The ability to use both C and C++ tools means that a greater variety of development tools are ＠＠ -4102,6 +4490,7 ＠＠ classes, strictly limiting the permissible operations and catching illegal implicit casts and such. +＠c #### did Ben delete this, or just the CODING-STANDARDS file in ./etc? XEmacs follows the GNU coding standards, which are documented separately in ＠xref{top,,, standards, GNU Coding Standards}. This section mainly documents standards that are not included in that ＠＠ -23222,6 +23611,7 ＠＠ could "just work". + ＠node Future Work -- Better Rendering Support, , Future Work -- Lisp Engine Replacement, Future Work ＠section Future Work -- Better Rendering Support ＠cindex future work, better rendering support ＠＠ -23231,7 +23621,7 ＠＠ don't blame Ben (or Eric and Matthias, for that matter). Feel free to add, edit, and share the blame, guys! -＠c #### make these ＠urlref's!! +＠c #### Make these ＠urlref's!! As of late November 2004, this principally means adding support for the ＠file{Xft} library, which provides a more robust ＠emph{font configuration} mechanism via Keith Packard's ＠file{fontconfig} library ＠＠ -23244,7 +23634,7 ＠＠＠emph{face} support; ＠emph{widget} support (including the toolbar and menubar); and ＠emph{redisplay refactoring}. -＠c Describe Alexey Gladkov and Yury Konovalov's work. +＠c #### Describe Alexey Gladkov and Yury Konovalov's work. However, in late 2003 Eric Knauel <knauel＠(a)informatik.uni-tuebingen.de> and Matthias Neubauer <neubauer＠(a)informatik.uni-freiburg.de> put forward ＠＠ -23255,15 +23645,15 ＠＠ one may be made available for the Knauel-Matthias patch soon. ＠menu -* Better Rendering Support -- Issues:: +* Better Rendering Support -- Review Criteria:: * Better Rendering Support -- Implementation:: * Better Rendering Support -- Current Status:: * Better Rendering Support -- Configuration with the Interim Patches:: ＠end menu -＠node Better Rendering Support -- Issues, Better Rendering Support -- Implementation, , Future Work -- Better Rendering Support -＠subsection Better Rendering Support -- Issues +＠node Better Rendering Support -- Review Criteria, Better Rendering Support -- Implementation, , Future Work -- Better Rendering Support +＠subsection Better Rendering Support -- Review Criteria ＠cindex better rendering support, issues ＠cindex issues, better rendering support ＠＠ -23300,7 +23690,7 ＠＠ to properly support display of different faces in non-buffer, non-window contexts. -＠node Better Rendering Support -- Implementation, Better Rendering Support -- Current Status, Better Rendering Support -- Issues, Future Work -- Better Rendering Support +＠node Better Rendering Support -- Implementation, Better Rendering Support -- Current Status, Better Rendering Support -- Review Criteria, Future Work -- Better Rendering Support ＠subsection Better Rendering Support -- Implementation ＠cindex better rendering support, implementation ＠cindex implementation, better rendering support ＠＠ -23324,6 +23714,15 ＠＠ of ＠file{Xft}'s rendering functionality should be separated from use of ＠file{fontconfig}. +＠item fontconfig +Fontconfig is dramatically different from the X model in several ways. +In particular, ＠emph{fontconfig always returns a font}. However, the +font returned need not be anything like the desired font. This means +that XEmacs must adopt a strategy of delegating the search to +fontconfig, then sanity-checking the return, rather than trying to use +the fontconfig API to search using techniques appropriate for the X11 +core font API. + ＠item Font menus The ＠samp{Options->Font} and ＠samp{Options->Font Sizes} menus are broken, by design, not just by ＠file{Xft}. Although they work better ＠＠ -23492,6 +23891,26 ＠＠ These menus don't work. All fonts are greyed out. All sizes are available, but many (most?) faces don't change size, in particular, ＠samp{default} does not. + +＠item Antialiased text bleeding outside of reported extent +On my PowerBook G4 Titanium 15" screen, X.org server v6.8.1, + dimensions: 1280x833 pixels (433x282 millimeters), + resolution: 75x75 dots per inch, + depth of root window: 24 planes +(yes, those dimensions are broken), +with font "Bitstream Vera Sans Mono-16:dpi=75" antialiased text may +bleed out of the extent reported by XftTextExtents and other such +facilities. This is most obvious with the underscore character in that +font. The bottom of the underscore is antialiased, and insertions or +deletions in the same line before the underscore leave a series of +"phantom" underlines. Except that it doesn't happen on the very first +such insertion or deletion after a window refresh. A similar effect +sometimes occurs with deletions at the end of the line (no, I can't +define "sometimes"). See also comments in ＠file{redisplay-x.c}, +functions ＠code{x_output_string} and ＠code{x_output_display_block}. +(Mostly duplicated here.) + +I think this is probably an Xft bug, but I'm not sure. ＠end table ＠＠ -23504,44 +23923,25 ＠＠ mind when configuring: ＠itemize -＠item -The only way to configure widget fonts at the present time is to use X -resources (or hack the source and rebuild). Currently supported widgets -are -＠itemize ＠item -menubars -＠item -tab controls -＠end itemize - -Here are the resources I use. ＠strong{Warning:} ＠emph{This interface -will change.} The tab control has separate Font and XftFont resources, -and uses the X resource manager to instantiate a FontStruct from the -Font resource. The menubar on the other hand uses Font for both, but -converts to FontStruct if Xft is not compiled in, and leaves it as a -string if Xft is compiled in. There is no equivalent facility for -XftFont yet, and creating one that handles both FontStruct and XftFont -depending on XEmacs's configuration and the font name seems error-prone -at best. Probably we will revert to a simple string representation for -this resource, and convert to a face in XEmacs rather than a font in -Xt/Xft. -＠example -XEmacs*Tabs.xftFont: Bitstream Vera Sans-18 -XEmacs*menubar.font: Bitstream Vera Sans-18 -XEmacs.modeline.attributeFont: Bitstream Charter-26 -XEmacs.default.attributeFont: Bitstream Vera Sans Mono-24 -＠end example -No, I don't understand why I need to use different point sizes to get -what looks like good balance to my eyes. I do highly recommend use of a -proportional font in the modeline because it allows a lot more text to -fit there. +Although the menus don't work, it is possible to specify fonts for +＠emph{faces} using ＠code{set-face-font} (and other specifier-changing +functions). + +There currently is no explicit way to specify that a particular font be +used only for a given language. However, since many fonts support only +a limited repertoire such as ISO 8859/1, you can use the precedence of +specifications for a given specifier locale to get something of this +effect for non-Latin character sets. This will normally work rather +poorly for multiple Latin character sets, however, because the +repertoires tend to have large amounts of overlap. Support for +specifying font by ＠emph{language} as well as by character set is +planned. -＠item Because fonts supporting other languages tend to support English as well, if you want to use one font for English and another for the other language, you must use the ＠code{append} method when adding font -specifications for the other language. +specifications for the ＠emph{other} language. However, this leaves you with a problem if you want to change the other language's font: you have to remove the existing specification so it ＠＠ -23559,7 +23959,40 ＠＠ (set-face-font 'default "Mikachan-14" nil '(lang-ja) 'remove-tag-set-append) ＠end example + +＠item +The only way to configure widget fonts at the present time is to use X +resources (or hack the source and rebuild). Currently supported widgets +are +＠itemize +＠item +menubars +＠item +tab controls ＠end itemize + +Here are the resources I use. ＠strong{Warning:} ＠emph{This interface +will change.} The tab control and menubar have separate Font and +XftFont resources, and use the X resource manager to instantiate a +FontStruct from the Font resource. There is no converter facility for +XftFont yet, and creating one that handles both FontStruct and XftFont +depending on XEmacs's configuration and the font name seems error-prone +at best. Probably we will should to a simple string representation for +this resource, and convert to a face in XEmacs rather than a font in +Xt/Xft. +＠example +XEmacs*Tabs.xftFont: Bitstream Vera Sans-16 +XEmacs*menubar*xftFont: Bitstream Vera Sans-16 +XEmacs.modeline.attributeFont: Bitstream Charter-16 +XEmacs.default.attributeFont: Bitstream Vera Sans Mono-16 +＠end example +I highly recommend use of a proportional font in the modeline because it +allows a lot more text to fit there. (Previously the font sizes were +quite varied, and there was a comment that this weirdness gave good +balance. This isn't true on my main platform, Mac OS X, and needs to be +rechecked on Linux, where it was observed.) +＠end itemize + ＠node Future Work Discussion, Old Future Work, Future Work, Top

1 participants
0 comments

CVS update by stephent MODIFIED: xemacs/man/internals ... 19 years, 10 months

CVS Monitor

User: stephent Date: 05/02/19 15:43:46 Modified: xemacs/man/internals Tag: sjt-xft internals.texi Log: doc update <878y5kmx1u.fsf(a)tleepslib.sk.tsukuba.ac.jp> Revision Changes Path No revision No revision 1.418.2.7 +16 -0 XEmacs/xemacs/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/ChangeLog,v retrieving revision 1.418.2.6 retrieving revision 1.418.2.7 diff -u -r1.418.2.6 -r1.418.2.7 --- ChangeLog 2005/02/11 12:19:31 1.418.2.6 +++ ChangeLog 2005/02/19 14:43:30 1.418.2.7 ＠＠ -1,3 +1,19 ＠＠ +2005-02-19 Stephen J. Turnbull <stephen(a)xemacs.org> + + * configure.ac (XE_EXPAND_COMPLEX_OPTION): Use same name in comment. + (XEmacs keyword option support): + (XEmacs complex option support): + Move long header comments to internals.texi(The configure Script). + +2005-02-03 Stephen J. Turnbull <stephen(a)xemacs.org> + + * configure.ac: Trap --with-style flags, now --enable. + +2005-02-03 Stephen J. Turnbull <stephen(a)xemacs.org> + + * configure.ac (Autodetect native sound): + Handle NetBSD per Aidan's patch. + 2005-02-11 Malcolm Purvis <malcolmp(a)xemacs.org> * configure.ac: Added keyword option support. Converted database, 1.1.14.5 +67 -59 XEmacs/xemacs/configure.ac Index: configure.ac =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/configure.ac,v retrieving revision 1.1.14.4 retrieving revision 1.1.14.5 diff -u -r1.1.14.4 -r1.1.14.5 --- configure.ac 2005/02/11 12:19:44 1.1.14.4 +++ configure.ac 2005/02/19 14:43:30 1.1.14.5 ＠＠ -231,21 +231,15 ＠＠ dnl ============================= dnl dnl A "keyword" option is one that accepts one of a number of pre-defined -dnl values (if more than one value is needed see "complex options" below). -dnl For example --with-mail-locking=flock. +dnl values. For example --with-mail-locking=flock. +dnl The descriptions below provide prototypes and little more. dnl -dnl Complex options used an expanded forms of AC_ARG_[WITH|ENABLE] called -dnl XE_KEYWORD_ARG_[WITH|ENABLE] both taking 5 parameters. The first 4 -dnl parameters of these macros are the same as original macros with the -dnl exception that all four paramaters are REQUIRED. The ACTION-IF-TRUE code -dnl is run after the argument list has been parsed. +dnl For more information, +dnl (Info-goto-node "(internals)The configure Script") +dnl To edit the documentation, +dnl (progn (find-file "man/internals/internals.texi")) +dnl and search for "＠node The configure Script". dnl -dnl The 5th parameter is a list keywords. The list must be quoted but the -dnl individual macros should not. -dnl -dnl If the option value is a not a valid keyword then an error message is -dnl generated, otherwise rthe value is left untouched. -dnl dnl XE_PARSE_KEYWORD_OPTION(prefix, cmdline-flag) dnl --------------------------------------------- dnl ＠＠ -311,39 +305,19 ＠＠ dnl A "complex option" is one that takes a number of related values. dnl For example, we might use "--with-xft=all,nomenubars" for compatibility dnl with XFontSet i18n of menubars. (Silly, Xft looks much better than XFS.) -dnl Processing such an option requires a number of auxiliary variables. -dnl -dnl Complex options used an expanded forms of AC_ARG_[WITH|ENABLE] called -dnl XE_COMPLEX_ARG_[WITH|ENABLE] both taking 5 parameters. The first 4 -dnl parameters of these macros are the same as original macros with the -dnl exception that all four paramaters are REQUIRED. The ACTION-IF-TRUE code -dnl is run after the argument list has been parsed. dnl -dnl The 5th parameter is a list of XE_COMPLEX_OPTION macros that define the -dnl valid components and their default values. The list must be quoted but -dnl the individual macros should not. +dnl The descriptions below provide prototypes and little more. +dnl For more information, +dnl (Info-goto-node "(internals)The configure Script") +dnl To edit the documentation, +dnl (progn (find-file "man/internals/internals.texi")) +dnl and search for "＠node The configure Script". dnl -dnl Option values are stored in the variables with_<package>_<component> or -dnl enable_<feature>_<component> (eg with_xft_menubars). -dnl -dnl Option values are either 'yes' which means that the option must be used -dnl and an error must occur if there is a configuration problems (such as a -dnl missing library) or 'no' which means that the option must not be used. -dnl The default value can also be "", meaning maybe, which means 'yes' if the -dnl configuration is present otherwise no. Users cannot specify 'maybe' from -dnl the command line. -dnl -dnl There are two possible uses in XEmacs for this kind of facility. One is -dnl exemplified by sound: there are alternative protocols (native, ESD, NAS) -dnl and each is supported by a corresponding library. The other is a single -dnl library which may or may not be supported by multiple components of -dnl XEmacs, as exemplified by Xft. This latter usage may be more common -dnl during development of a feature. Perhaps specialized APIs should be -dnl provided, see comment on XE_COMPLEX_OPTION_HELP_STRING below. -dnl -dnl XE_COMPLEX_OPTION_DEFAULT(prefix, component, yesno) +dnl XE_EXPAND_COMPLEX_OPTION(prefix, component, yesno) dnl --------------------------------------------------- dnl +dnl #### documented as XE_COMPLEX_OPTION_DEFAULT(prefix, component, yesno) +dnl #### in Malcolm's version? dnl Internal macro create the option's shell variable containing the default dnl value and to note the values in an option list. dnl ＠＠ -492,7 +466,33 ＠＠ dnl Error-checking on old-style flags AC_ARG_WITH([mule],[],[XE_DIE([--enable-mule, NOT --with-mule])],[]) +AC_ARG_WITH([menubars],[],[XE_DIE([--enable-menubars, NOT --with-menubars])],[]) +AC_ARG_WITH([scrollbars],[],[XE_DIE([--enable-scrollbars, NOT --with-scrollbars])],[]) +AC_ARG_WITH([dialogs],[],[XE_DIE([--enable-dialogs, NOT --with-dialogs])],[]) +AC_ARG_WITH([widgets],[],[XE_DIE([--enable-widgets, NOT --with-widgets])],[]) +AC_ARG_WITH([sound],[],[XE_DIE([--enable-sound, NOT --with-sound])],[]) +AC_ARG_WITH([default-eol-detection],[],[XE_DIE([--enable-default-eol-detection, NOT --with-default-eol-detection])],[]) +AC_ARG_WITH([clash-detection],[],[XE_DIE([--enable-clash-detection, NOT --with-clash-detection])],[]) +AC_ARG_WITH([database],[],[XE_DIE([--enable-database, NOT --with-database])],[]) +AC_ARG_WITH([modules],[],[XE_DIE([--enable-modules, NOT --with-modules])],[]) +AC_ARG_WITH([toolbars],[],[XE_DIE([--enable-toolbars, NOT --with-toolbars])],[]) + +dnl I think these will be caught by autoconf internal checks, +dnl only --with-* are unchecked +dnl --external-widget --enable-external-widget +dnl --native-sound-lib=LIB --with-native-sound-lib +dnl --mail-locking=TYPE --with-mail-locking +dnl --rel-alloc --with-rel-alloc +dnl --use-number-lib --enable-bignum +dnl --debug --enable-debug +dnl --error-checking --enable-error-checking +dnl --memory-usage-stats --enable-memory-usage-stats +dnl --quick-build --enable-quick-build +dnl --use-union-type --enable-union-type +dnl --pdump --enable-pdump +dnl --use-kkcc --enable-kkcc +dnl parse flags AC_ARG_WITH([prefix], AC_HELP_STRING([--with-prefix=no],[Don't compile the value of --prefix into the executable.]), [true], [with_prefix=yes]) ＠＠ -4807,29 +4807,37 ＠＠ dnl Check for Linux/BSD native sound (also on recent Cygwins) if test -z "$sound_found"; then for dir in "machine" "sys" "linux"; do - AC_CHECK_HEADER(${dir}/soundcard.h, + AC_CHECK_HEADER(${dir}/soundcard.h, [ sound_found=yes - need_miscplay=yes - XE_ADD_OBJS(linuxplay.o) - [AC_DEFINE_UNQUOTED(SOUNDCARD_H_FILE, "${dir}/soundcard.h")] - break) + case "$canonical" in + *netbsd* ) + # #### this is probably not the right way to do this + # we should port to native NetBSD stuff + AC_CHECK_LIB(ossaudio, _oss_ioctl, + [native_sound_lib=-lossaudio + AC_MSG_WARN([Using NetBSD-deprecated -lossaudio])], + [sound_found=no]) + ;; + dnl Aidan sez: OpenBSD as well can use Linux's sound API, and needs + dnl the same library. Add here! + esac + break]) done + + if test "$sound_found" = "yes"; then + need_miscplay=yes + XE_ADD_OBJS(linuxplay.o) + [AC_DEFINE_UNQUOTED(SOUNDCARD_H_FILE, "${dir}/soundcard.h")] + fi fi if test "$sound_found" = "yes"; then - enable_sound_native=yes - - dnl NetBSD can use Linux's sound API, but it needs an extra library at - dnl link time to do so. (OpenBSD apparently needs the same; not written - dnl or tested.) - if test "$opsys" = "netbsd" ; then - AC_CHECK_LIB(ossaudio, _oss_ioctl, native_sound_lib="-lossaudio") - fi + enable_sound_native=yes else - if test "$enable_sound_native" = "yes" ; then - AC_MSG_WARN([No native libraries found. Disabling native sound support.]) - fi - enable_sound_native=no + if test "$enable_sound_native" = "yes" ; then + AC_MSG_WARN([No native libraries found. Disabling native sound support.]) + fi + enable_sound_native=no fi fi No revision No revision 1.269.2.4 +32 -1 XEmacs/xemacs/man/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/ChangeLog,v retrieving revision 1.269.2.3 retrieving revision 1.269.2.4 diff -u -r1.269.2.3 -r1.269.2.4 --- ChangeLog 2005/02/01 15:46:42 1.269.2.3 +++ ChangeLog 2005/02/19 14:43:37 1.269.2.4 ＠＠ -1,3 +1,34 ＠＠ +2005-02-19 Stephen J. Turnbull <stephen(a)xemacs.org> + + * internals/internals.texi (Introduction to Writing C Code): + Change "mostly warning-free" to "warning-free" to encourage + reporting warnings as bugs. + (The configure Script): + Incorporate Malcolm Purvis's notes from configure.ac. Document + his implementations of keyword and complex options, and remove + descriptions of my obsolete code. + +2005-02-03 Stephen J. Turnbull <stephen(a)xemacs.org> + * internals/internals.texi (XEmacs from the Perspective of + Building): Mention autoconf. + (The Modules of XEmacs): Point Next the The Build Configuration + System and add Modules for Building XEmacs to the menu. + (A Summary of the Various XEmacs Modules): Add Modules for + Building XEmacs to menu, and Modules for Build Configuration, + Modules for Compiling XEmacs, and Modules for Preloading Lisp to + the table of sections. + (Low-Level Modules): Point Previous to Modules for Building XEmacs. + (Modules for Building XEmacs): + (Modules for Build Configuration): + (Modules for Compiling XEmacs): + (Modules for Preloading Lisp): + (The Build Configuration System): + (Adding Configurable Features): + (The configure Script): + (The Makefile Precursors): + New nodes. + (Rules When Writing New C Code): + Point Previous to The Build Configuration System. 2005-01-16 Stephen J. Turnbull <stephen(a)xemacs.org> * internals/internals.texi (Better Rendering Support -- ＠＠ -386,7 +417,7 ＠＠ (Future Work -- Lisp Engine Replacement): Add pointers to new node. -04-11-16 Ben Wing <ben(a)xemacs.org> +2004-11-16 Ben Wing <ben(a)xemacs.org> * internals/internals.texi (Top): * internals/internals.texi (Introduction): No revision No revision 1.52.2.4 +396 -7 XEmacs/xemacs/man/internals/internals.texi Index: internals.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/internals/internals.texi,v retrieving revision 1.52.2.3 retrieving revision 1.52.2.4 diff -u -r1.52.2.3 -r1.52.2.4 --- internals.texi 2005/02/01 15:46:44 1.52.2.3 +++ internals.texi 2005/02/19 14:43:40 1.52.2.4 ＠＠ -311,6 +311,7 ＠＠ * XEmacs from the Perspective of Building:: * Build-Time Dependencies:: * The Modules of XEmacs:: +* The Build Configuration System:: * Rules When Writing New C Code:: * Regression Testing XEmacs:: * CVS Techniques:: ＠＠ -2331,7 +2332,9 ＠＠ The first step of building involves running the ＠file{configure} program and passing it various parameters to specify any optional features you want and compiler arguments and such, as described in the ＠file{INSTALL} -file. This determines what the build environment is, chooses the +file. (You may optionally run ＠file{autoconf} first to update the +＠file{configure} script. ＠xref{Modules for Build Configuration}.) +This determines what the build environment is, chooses the appropriate ＠file{s/} and ＠file{m/} file, and runs a series of tests to determine many details about your environment, such as which library functions are available and exactly how they work. The reason for ＠＠ -2442,12 +2445,13 ＠＠＠code{custom-declare-variable-list} to prevent the ＠samp{void-variable} error. (Currently this is only needed for ＠file{make-docfile.el}.) -＠node The Modules of XEmacs, Rules When Writing New C Code, Build-Time Dependencies, Top +＠node The Modules of XEmacs, The Build Configuration System, Build-Time Dependencies, Top ＠chapter The Modules of XEmacs ＠cindex modules of XEmacs ＠menu * A Summary of the Various XEmacs Modules:: +* Modules for Building XEmacs:: * Low-Level Modules:: * Basic Lisp Modules:: * Modules for Standard Editing Operations:: ＠＠ -2456,7 +2460,7 ＠＠ * Modules for Interfacing with the Operating System:: ＠end menu -＠node A Summary of the Various XEmacs Modules, Low-Level Modules, The Modules of XEmacs, The Modules of XEmacs +＠node A Summary of the Various XEmacs Modules, Modules for Building XEmacs, The Modules of XEmacs, The Modules of XEmacs ＠section A Summary of the Various XEmacs Modules ＠cindex summary of the various XEmacs modules ＠cindex modules, summary of the various XEmacs ＠＠ -2468,6 +2472,12 ＠＠＠itemize ＠bullet ＠item +＠ref{Modules for Build Configuration}. +＠item +＠ref{Modules for Compiling XEmacs}. +＠item +＠ref{Modules for Preloading Lisp}. +＠item ＠ref{Low-Level Modules}. ＠item ＠ref{Basic Lisp Modules}. ＠＠ -2943,8 +2953,66 ＠＠＠end multitable + +＠node Modules for Building XEmacs, Low-Level Modules, A Summary of the Various XEmacs Modules, The Modules of XEmacs +＠section Modules for Building XEmacs +＠cindex modules for building XEmacs +＠cindex building XEmacs, modules for + +＠menu +* Modules for Build Configuration:: +* Modules for Compiling XEmacs:: +* Modules for Preloading Lisp:: +＠end menu + + + +＠node Modules for Build Configuration, Modules for Compiling XEmacs, Modules for Building XEmacs, Modules for Building XEmacs +＠subsection Modules for Build Configuration +＠cindex modules for build configuration +＠cindex build configuration, modules for + +＠example +＠file{configure} +(a)file{config.h.in} +(a)file{Makefile.in.in} +＠end example + +＠example +(a)file{configure.ac} +(a)file{configure.in} +＠end example + +＠xref{The configure Script}. + + -＠node Low-Level Modules, Basic Lisp Modules, A Summary of the Various XEmacs Modules, The Modules of XEmacs +＠node Modules for Compiling XEmacs, Modules for Preloading Lisp, Modules for Build Configuration, Modules for Building XEmacs +＠subsection Modules for Compiling XEmacs +＠cindex modules for compiling xemacs +＠cindex compiling xemacs, modules for + +＠strong{Please write this node!} ＠c #### + +This node should contain descriptions of files like the various +Makefiles, and I guess cross-references to ellcc etc. + + + +＠node Modules for Preloading Lisp, , Modules for Compiling XEmacs, Modules for Building XEmacs +＠subsection Modules for Preloading Lisp +＠cindex modules for preloading lisp +＠cindex preloading lisp, modules for + +＠strong{Please write this node!} ＠c #### + +This node should contain descriptions of files like dumped-lisp.el +(maybe that goes in Modules for Build Configuration supra?), +update-elcs.el, and so on. + + + +＠node Low-Level Modules, Basic Lisp Modules, Modules for Building XEmacs, The Modules of XEmacs ＠section Low-Level Modules ＠cindex low-level modules ＠cindex modules, low-level ＠＠ -3977,8 +4045,328 ＠＠ This module provides some terminal-control code necessary on versions of AIX prior to 4.1. + + + +＠node The Build Configuration System, Rules When Writing New C Code, The Modules of XEmacs, Top +＠chapter The Build Configuration System +＠cindex build configuration +＠cindex configuration, build + +＠strong{Please write this node!} ＠c #### + +This node should describe XEmacs-specific techniques and idioms in the +configuration system. A particular example is the set of ＠samp{XE_} +macros in ＠file{configure.in} and ＠file{configure.ac}. + +＠menu +* Adding Configurable Features:: +* The configure Script:: +* The Makefile Precursors:: +＠end menu + + + +＠node Adding Configurable Features, The configure Script, The Build Configuration System, The Build Configuration System +＠section Adding Configurable Features +＠cindex adding configurable features +＠cindex configurable features, adding +＠cindex features, adding configurable + +Adding a configurable feature requires at least adding an option to the +＠file{configure} script and a macro definition to ＠file{src/config.h.in} +(＠pxref{The configure Script}), and often changes to Makefile precursors +(＠pxref{The Makefile Precursors}). + + + +＠node The configure Script, The Makefile Precursors, Adding Configurable Features, The Build Configuration System +＠section The configure Script +＠cindex configure script +＠cindex script, configure + +At the heart of the XEmacs build configuration system is the +＠file{configure} script. This beast is maintained using the Autoconf +system, which is a truly terrifying monstrosity based on a fundamentally +flawed programming model (extensive use of macros), with an +implementation about which I've never heard a nice word (GNU ＠file{m4}), +used to string together a large set of ＠emph{ad hoc} tests, to implement +a configuration language with conventions that are unimportant in simple +cases and counterintuitive when things get complicated. If that doesn't +scare you off, Welcome! I think you're ready to become a configure +hacker! (But be prepared for things to go downhill from here.) + +＠file{configure} is, of course, is written in POSIX shell language, and +autogenerated from a precursor (see? the first step was a doozy!) +Currently that precursor is called ＠file{configure.ac}, but in the +previous generation it was called ＠file{configure.in}. As of February +2005, ＠file{configure.ac} is used in the development mainline, but +because the semantics of many predefined macros changed drastically +between ＠file{autoconf} 2.13 and ＠file{autoconf} 2.50 (why not ``3.0''? +you got me), the XEmacs Project chose to stick with the devil it knew +for the stable line of XEmacs 21.4 releases. + +One reason for worrying about the semantic changes is the fact that +XEmacs uses a lot of homebrew code, including ＠file{m4} macros, to +implement special features in its ＠file{configure} script. Here are +some of the important features: + +＠itemize +＠item +Selectively enabling debugging, error checking, and tracing. +＠item +Complex options, which are set-valued (＠i{i.e.}, unordered; ordered +lists of options, for example ``take the first available from the +list,'' are neither used currently nor given special support). +＠end itemize + +Where these are implemented as ＠file{m4} macros, the prefix ＠samp{XE_} +is used to identify them as XEmacs features in the ＠file{configure} +precursor code. Here is a list of prototypes of the convenience macros +provided for performing common operations: + +＠c #### ＠var{}-ize the formal parameters of these functions? +＠table ＠code +＠item USAGE_ERROR(string) +prints a usage error and dies + +＠item PRINT_VAR(var var ...) +prints values of shell variables + +＠item XE_ADD_OBJS(foo.o ...) +＠strong{#### Please document me!} + +＠item XE_APPEND(value, varname) +＠strong{#### Please document me!} + +＠item XE_PREPEND(value, varname) +＠strong{#### Please document me!} + +＠item XE_DIE(message) +used for situations that can't lead to a successful build, such as +missing include files or conflicts between requested features. + +＠item XE_CHECK_FEATURE_DEPENDENCY(feature1, feature2) +＠strong{#### Please document me!} + +＠item XE_STRIP_4TH_COMPONENT(var) +＠strong{#### Please document me!} + +＠item CANONICALIZE_PATH(varname) +＠strong{#### Please document me!} + +＠item XE_PROTECT_LINKER_FLAGS(shell_var) +＠strong{#### Please document me!} + +＠item COLON_TO_SPACE(path) +Allow use of either ＠samp{:} or spaces for lists of directories. + +＠item XE_ADD_RUNPATH_DIR(directory) +＠strong{#### Please document me!} + +＠item XE_COMPUTE_RUNPATH() +＠strong{#### Please document me!} + +＠item XE_SPACE(var, words) +＠strong{#### Please document me!} + +＠item XE_SHLIB_STUFF +See ＠file{aclocal.m4}. +＠end table + +＠heading XEmacs keyword option support + +A ＠dfn{keyword} option is one that accepts one of a number of +pre-defined values (if support for sets of values is needed, see +``complex options'' below). For example, +＠samp{--with-mail-locking=flock}. + +Keyword options use expanded forms of ＠samp{AC_ARG_[WITH|ENABLE]} called +＠samp{XE_KEYWORD_ARG_[WITH|ENABLE]}, both taking 5 parameters. The +first 4 parameters of these macros are the same as original macros with +the exception that all four parameters are ＠strong{required}. The +＠var{action-if-true} code is run after the argument list has been +parsed. + +The 5th parameter is a list of supported keywords. The whole list must +be quoted but the individual keywords should not. + +If the option value is a not a valid keyword then an error message is +generated, otherwise the value is left untouched. + +This support is implemented via the following ＠file{GNU m4} macros. +Macros labelled ＠dfn{internal} are not expected to be used by +(a)file{configure.ac} programmers; they are part of the implementation of +higher-level features. + +＠table ＠code +＠item XE_KEYWORD_ARG_WITH(package, help-string, action-if-true, action-if-false, [keyword1, keyword2, ....]) +Expanded version of ＠samp{AC_ARG_WITH} for keyword options. All the +parameters are required. The last argument is a comma-separated list of +supported keywords, ＠file{m4}-quoted with ＠samp{[]}. + +＠item XE_KEYWORD_ARG_ENABLE(feature, help-string, action-if-true, action-if-false, [keyword1, keyword2, ....]) +Expanded version of ＠samp{AC_ARG_ENABLE} for keyword options. All the +parameters are required. The last argument is a comma-separated list of +supported keywords, ＠file{m4}-quoted with ＠samp{[]}. + +＠item XE_PARSE_KEYWORD_OPTION(prefix, cmdline-flag) +Internal macro to parse the option values. If an undeclared option is +found then an error is generated. + +＠item XE_KEYWORD(keyword) +Internal macro to declare an option value. + +＠end table + +＠heading XEmacs complex option support + +A ＠dfn{complex option} is one that takes a number of related values, as +a set. For example, we might use "--with-xft=all,nomenubars" for +compatibility with XFontSet i18n of menubars. (The example is +contrived, Xft looks much better than XFS.) Processing such an option +requires a number of auxiliary variables. + +Complex options use expanded forms of ＠samp{AC_ARG_[WITH|ENABLE]} called +＠samp{XE_COMPLEX_ARG_[WITH|ENABLE]}, both taking 5 parameters. The +first 4 parameters of these macros are the same as original macros with +the exception that all four parameters are ＠strong{required}. The +＠var{action-if-true} code is run after the argument list has been +parsed. + +The 5th parameter is a list of ＠samp{XE_COMPLEX_OPTION} macro calls that +define the valid components and their default values. The list must be +quoted but the individual macro calls should not. Here is how the +＠samp{sound} flag is defined: + +＠example +XE_COMPLEX_ARG_ENABLE([sound], + AC_HELP_STRING([--enable-sound],[Compile with sound support. + Valid types are `native', `nas' and `esd'. + Prefix a type with 'no' to disable. + The first type can be `none' or `all'. `none' means + `nonative,nonas,noesd'. `all' means `native,nas,esd'. + Later options override earlier ones for the same TYPE. + The default is to autodetect all sound support except + for ESD which defaults to off.]), + [], + [enable_sound_nas=""], + [XE_COMPLEX_OPTION([native],[""]), + XE_COMPLEX_OPTION([nas],[""]), + XE_COMPLEX_OPTION([esd],[no])]) +＠end example + +(Note that the help string will be reformatted by ＠file{autoconf} so +that all whitespace is first compressed to a single space, then folded +to appear in the right-hand column as above. Thus the help string may +appear differently when ＠code{./configure --help} is invoked.) + +＠c #### verify for INSTALL and xemacs Texinfo. +Each component is interpreted as a separate feature to be enabled or +disabled. As usual, the distinction between ``with'' and ``enable'' is +that ``with'' features require specific support from the system, usually +one or more optional libraries, and ``enable'' features are supported +entirely by code in XEmacs, but the user might want to switch it off for +some reason. Option values are stored in the variables +＠samp{with_＠var{package}_＠var{component}} or +＠samp{enable_＠var{feature}_＠var{component}} (＠i{e.g.} +＠samp{with_xft_menubars}). + +The user of ＠file{configure} specifies the configuration by providing a +list of components. The special components ＠samp{all} and ＠samp{none} +may occur first in the list, setting the defaults for all components to +＠samp{yes} or ＠samp{no} respectively. + +In ＠file{configure.ac}, default values of option values may be +＠samp{yes} which means that the option must be used and an error must +occur if there is a configuration problems (such as a missing library) +or ＠samp{no} which means that the option must not be used. The default +value can also be the null string ＠samp{""}, usually meaning that +＠file{configure} will attempt to find support for the feature on the +system, and will enable the configuration if it is available. Sometimes +the null string means that ＠file{configure}'s default is +system-dependent. (This usage is not consistent, and depends on the +implementation of the feature detector rather than the argument parser.) +Users cannot specify the null string for an individual component from +the command line. + +There are two possible uses in XEmacs for this kind of facility. One is +exemplified by sound: there are alternative protocols (native, ESD, NAS) +and each is supported by a corresponding library. The other is a single +library which may or may not be supported by multiple components of +XEmacs, as exemplified by Xft. This latter usage may be more common +during development of a feature. Perhaps specialized APIs should be +provided, see comment on ＠samp{XE_COMPLEX_OPTION_HELP_STRING} below. + +＠table ＠code +＠item XE_COMPLEX_OPTION(option, yesno) +Declare a complex option and its default value. The value ＠strong{must} +be either ＠samp{yes} or ＠samp{no} or the null string ＠samp{""}. The +null string means ``maybe'', whose semantics are determined by the +implementation of the option, not by the parser. Typical semantics are +``use the library if found in the usual places'' or ``default is +platform-dependent''. + +＠item XE_COMPLEX_OPTION_HELP_STRING(flag, long, short, components, libraries) +Format a boilerplate help string for complex options. + +This was originally written for the Xft option, and doesn't read so well +for options based on alternative libraries like sound. Hackers beware: +the API may be enhanced to deal with this in the future. + +＠item XE_COMPLEX_ARG_WITH(PACKAGE, HELP-STRING, ACTION-IF-TRUE, ACTION-IF-FALSE, [XE_COMPLEX_OPTION(a,yes), ....]) +Extended version of ＠samp{AC_ARG_WITH} for complex options. All the +parameters are required. + +＠item XE_COMPLEX_ARG_ENABLE(FEATURE, HELP-STRING, ACTION-IF-TRUE, ACTION-IF-FALSE, [XE_COMPLEX_OPTION(a,yes), ....]) +Expanded version of ＠samp{AC_ARG_ENABLE} for complex options. All the +parameters are required. + +＠item XE_EXPAND_COMPLEX_OPTION(prefix, component, yesno) +Internal macro create the option's shell variable containing the default +value and to note the values in an option list. + +＠item XE_EXPAND_COMPLEX_OPTIONS(prefix, option_list) +Internal macro which recursively expands an option list. + +＠item XE_INIT_COMPLEX_OPTION(prefix, option_list) +Internal macro to initialise the complex option shell variables. + +Variables of the form ＠samp{＠var{prefix}_＠var{option}} contain the +default value for that option. ＠samp{＠var{prefix}_types} contains a +space-separated list of all the options and ＠samp{＠var{prefix}_default} +contains a comma-separated list of all the default values. + +＠item XE_PARSE_COMPLEX_OPTION(prefix, cmdline-flag) +Internal macro to parse the option values. If an undeclared option is +found then an error is generated. + +＠end table + + + +＠node The Makefile Precursors, , The configure Script, The Build Configuration System +＠section The Makefile Precursors +＠cindex Makefile precursors +＠cindex precursors, Makefile + +＠strong{Please write this node!} ＠c #### + +As in other programs using a ＠file{configure} program, XEmacs's +Makefiles are not written, they are generated. The ＠file{configure} +program uses Makefile precursors, or templates, to generate the actual +Makefiles. In fact, it is a multistage process. The developer changes +the file ＠file{Makefile.in.in}, then ＠file{configure} first generates an +intermediate file ＠file{Makefile.in}, and finally produces a portable +Makefile called ＠file{Makefile}, and a Makefile optimized for ＠file{GNU +make} called ＠file{GNUmakefile}. + +This node describes XEmacs-specific techniques and idioms used in the +(a)file{Makefile.in.in} files. + + -＠node Rules When Writing New C Code, Regression Testing XEmacs, The Modules of XEmacs, Top +＠node Rules When Writing New C Code, Regression Testing XEmacs, The Build Configuration System, Top ＠chapter Rules When Writing New C Code ＠cindex writing new C code, rules when ＠cindex C code, rules when writing new ＠＠ -4012,8 +4400,8 ＠＠＠cindex coding conventions The C code is actually written in a dialect of C called ＠dfn{Clean C}, -meaning that it can be compiled, mostly warning-free, with either a C -or C++ compiler. Coding in Clean C has several advantages over plain +meaning that it can be compiled, warning-free, with either a C or C++ +compiler. Coding in Clean C has several advantages over plain C. C++ compilers are more nit-picking, and a number of coding errors have been found by compiling with C++. The ability to use both C and C++ tools means that a greater variety of development tools are ＠＠ -4024,6 +4412,7 ＠＠ classes, strictly limiting the permissible operations and catching illegal implicit casts and such. +＠c #### did Ben delete this, or just the CODING-STANDARDS file in ./etc? XEmacs follows the GNU coding standards, which are documented separately in ＠xref{top,,, standards, GNU Coding Standards}. This section mainly documents standards that are not included in that

1 participants
0 comments

CVS update by viteno MODIFIED: xemacs-builds/viteno ... 19 years, 10 months

CVS Monitor

User: viteno Date: 05/02/19 12:54:51 Modified: xemacs-builds/viteno package-index setup-packages.ini Log: Package database backup: - ediff-1.51 Revision Changes Path 1.194 +6 -6 XEmacs/xemacs-builds/viteno/package-index Index: package-index =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs-builds/viteno/package-index,v retrieving revision 1.193 retrieving revision 1.194 diff -u -r1.193 -r1.194 --- package-index 2005/02/16 22:31:20 1.193 +++ package-index 2005/02/19 11:54:49 1.194 ＠＠ -2010,19 +2010,19 ＠＠ (package-get-update-base-entry (quote (ediff (standards-version 1.1 - version "1.50" + version "1.51" author-version "2.75" - date "2004-02-20" - build-date "2004-02-20" + date "2005-02-19" + build-date "2005-02-19" maintainer "Michael Kifer <kifer(a)cs.sunysb.edu>" distribution xemacs priority medium category "standard" dump nil description "Interface over GNU patch." - filename "ediff-1.50-pkg.tar.gz" - md5sum "7d061f18835414731e4e3aca024f75d7" - size 305546 + filename "ediff-1.51-pkg.tar.gz" + md5sum "8ef3b96181efacfcf649c362f5effa13" + size 309434 provides (ediff-diff ediff-help ediff-hook ediff-init ediff-merg ediff-mult ediff-ptch ediff-tbar ediff-util ediff-vers ediff-wind ediff) requires (pcl-cvs elib dired xemacs-base edebug prog-modes) type regular 1.187 +2 -2 XEmacs/xemacs-builds/viteno/setup-packages.ini Index: setup-packages.ini =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs-builds/viteno/setup-packages.ini,v retrieving revision 1.186 retrieving revision 1.187 diff -u -r1.186 -r1.187 --- setup-packages.ini 2005/02/14 22:01:30 1.186 +++ setup-packages.ini 2005/02/19 11:54:49 1.187 ＠＠ -140,8 +140,8 ＠＠ install: packages/debug-1.17-pkg.tar.gz 108073 ＠ ediff -version: 1.50 -install: packages/ediff-1.50-pkg.tar.gz 305546 +version: 1.51 +install: packages/ediff-1.51-pkg.tar.gz 309434 ＠ emerge version: 1.11

1 participants
0 comments

CVS update by viteno MODIFIED: packages/xemacs-packages/ediff ... 19 years, 10 months

CVS Monitor

User: viteno Date: 05/02/19 12:42:42 Modified: packages/xemacs-packages/ediff ChangeLog Makefile Log: Increment VERSION in Makefile Revision Changes Path 1.81 +4 -0 XEmacs/packages/xemacs-packages/ediff/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ediff/ChangeLog,v retrieving revision 1.80 retrieving revision 1.81 diff -u -r1.80 -r1.81 --- ChangeLog 2005/02/19 04:43:38 1.80 +++ ChangeLog 2005/02/19 11:42:40 1.81 ＠＠ -1,3 +1,7 ＠＠ +2005-02-19 Norbert Koch <viteno(a)xemacs.org> + + * Makefile (VERSION): XEmacs package 1.51 released. + 2005-02-19 Michael Kifer <kifer(a)cs.stonybrook.edu> * ediff.el (ediff-set-diff-overlays-in-one-buffer, 1.63 +1 -1 XEmacs/packages/xemacs-packages/ediff/Makefile Index: Makefile =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ediff/Makefile,v retrieving revision 1.62 retrieving revision 1.63 diff -u -r1.62 -r1.63 --- Makefile 2004/02/20 08:25:30 1.62 +++ Makefile 2005/02/19 11:42:40 1.63 ＠＠ -17,7 +17,7 ＠＠ # the Free Software Foundation, Inc., 59 Temple Place - Suite 330, # Boston, MA 02111-1307, USA. -VERSION = 1.50 +VERSION = 1.51 AUTHOR_VERSION = 2.75 MAINTAINER = Michael Kifer <kifer(a)cs.sunysb.edu> PACKAGE = ediff

1 participants
0 comments

CVS update by viteno MODIFIED: packages ... 19 years, 10 months

CVS Monitor

User: viteno Date: 05/02/19 12:41:29 Modified: packages ChangeLog Log: Package release Revision Changes Path 1.502 +4 -0 XEmacs/packages/ChangeLog Index: ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/ChangeLog,v retrieving revision 1.501 retrieving revision 1.502 diff -u -r1.501 -r1.502 --- ChangeLog 2005/02/16 22:24:29 1.501 +++ ChangeLog 2005/02/19 11:41:28 1.502 ＠＠ -1,3 +1,7 ＠＠ +2005-02-19 Norbert Koch <viteno(a)xemacs.org> + + * Packages released: ediff. + 2005-02-16 Norbert Koch <viteno(a)xemacs.org> * Packages released: latin-euro-standards.

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

xemacs-cvs February 2005