[PATCH] Pre-behavior-ws changes, PLEASE REVIEW
19 years, 10 months
Ben Wing
Ben Wing
PLEASE REVIEW!
This is a repost of a prior posting. Before integrating my workspace that
implements behaviors, I want to put in the necessary package changes.
Some of these changes are to packages that are externally maintained, but
I'm not exactly sure which, or who I should mail the changes to, or other
procedural-related stuff.
Norbert, could you comment?
NB This is minus the pending-del patch that caused controversy last time;
that is in a separate post.
Here is what I wrote before:
----------------------------
This contains patches from an old package ws. Most of them add support for
define-behavior, which I have heavily modified in another ws of mine. They
conditionalize on define-behavior-group, since the old version of
define-behavior doesn't allow arbitrary keywords and hence will break with
the new defns. (define-behavior-group exists only in the new ws.)
The idea is that the Tools menu is replaced with a menu generated by
behavior.el, where each behavior can specify the way to enable/disable,
other commands, a doc string, etc. Variables can also be frobbed because
the same ws adds support for auto-generated custom-defines.el, which
specifies all the vars of a package without the need to load the whole
package. A few changes have been added to make this work better.
One side effect of this is that PACKAGES MAY NO LONGER MODIFY MENUS
THEMSELVES. I've been trying to get package maintainers to be more
well-behaved about this for awhile (and have encountered some resistance),
but it really must happen now that the Tools menu has totally changed.
Some packages have been forcibly hacked in this patch; obviously this won't
go in without the consent of the package maintainer.
Similarly, I've put in some hacks to fix up some of the remaining packages
that illegally set themselves up upon loading. With the behavior interface
there is a consistent way to enable/disable packages in any case.
mule-packages/skk/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* skk-foreword.el:
Autoload for custom-defines.
unsupported/simon/epop3/ChangeLog addition:
2003-03-09 Ben Wing <ben(a)xemacs.org>
* Makefile:
Delete explicit compile:: and binkit: rules.
Don't add custom-load.elc to the list of generated elc's.
xemacs-packages/calendar/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* calendar.el:
* calendar.el ('calendar): New.
Add define-behavior.
xemacs-packages/cookie/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* yow.el:
* yow.el ('yow): New.
Add define-behavior.
xemacs-packages/debug/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* dbx.el:
* dbx.el ('dbx): New.
* gdb.el:
* gdb.el ('gdb): New.
Add define-behavior.
xemacs-packages/ediff/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* ediff-hook.el:
* ediff-hook.el (progn):
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
* ediff-hook.el ('ediff): New.
Add define-behavior.
xemacs-packages/edit-utils/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* avoid.el:
* avoid.el ('avoid): New.
* avoid.el (avoid):
* balloon-help.el:
* balloon-help.el ('balloon-help): New.
* balloon-help.el (balloon-help):
* blink-cursor.el:
* blink-cursor.el ('blink-cursor): New.
* blink-paren.el:
* blink-paren.el ('blink-paren): New.
* completion.el:
* completion.el ('completion): New.
* completion.el (completion):
* dabbrev.el:
* dabbrev.el ('dabbrev): New.
* dabbrev.el (dabbrev):
* desktop.el:
* desktop.el ('desktop): New.
* desktop.el (desktop):
Add define-behavior support.
* edit-faces.el:
* edit-faces.el ('edit-faces): New.
* edit-toolbar.el:
* edit-toolbar.el ('edit-toolbar): New.
* edit-toolbar.el (edit-toolbar):
* fast-lock.el:
* fast-lock.el ('fast-lock): New.
* fast-lock.el (fast-lock):
* file-part.el:
* file-part.el ('file-part): New.
* file-part.el (file-part):
* floating-toolbar.el:
* floating-toolbar.el ('floating-toolbar): New.
* floating-toolbar.el (floating-toolbar):
* flow-ctrl.el:
* flow-ctrl.el ('flow-control): New.
* flow-ctrl.el (flow-control):
* func-menu.el:
* func-menu.el ('func-menu): New.
* hippie-exp.el:
* hippie-exp.el ('hippie-expand): New.
* hippie-exp.el (hippie-expand):
* id-select.el:
* id-select.el ('id-select): New.
* id-select.el (id-select):
* iswitchb.el:
* iswitchb.el ('iswitchb): New.
* iswitchb.el (iswitchb):
* lazy-lock.el:
* lazy-lock.el ('lazy-lock): New.
* lazy-lock.el (lazy-lock):
* page-ext.el:
* page-ext.el ('page-ext): New.
* page-ext.el (page-ext):
* paren.el:
* paren.el ('paren): New.
* paren.el (paren):
* permanent-buffers.el:
* permanent-buffers.el ('permanent-buffers): New.
* permanent-buffers.el (permanent-buffers):
* popper.el:
* popper.el ('popper): New.
* popper.el (popper):
* power-macros.el:
* power-macros.el ('power-macros): New.
* power-macros.el (power-macros):
* recent-files.el:
* recent-files.el ('recent-files): New.
* recent-files.el (recent-files):
* redo.el:
* redo.el ('redo): New.
* redo.el (redo):
* reportmail.el:
* reportmail.el ('reportmail): New.
* reportmail.el (reportmail):
* resume.el:
* resume.el ('resume): New.
* resume.el (resume):
* rsz-minibuf.el:
* rsz-minibuf.el ('resize-minibuffer): New.
* rsz-minibuf.el (resize-minibuffer):
* saveconf.el:
* saveconf.el ('save-context): New.
* saveconf.el (save-context):
* savehist.el:
* savehist.el ('save-history): New.
* savehist.el (save-history):
* scroll-in-place.el:
* scroll-in-place.el ('scroll-in-place): New.
* scroll-in-place.el (scroll-in-place):
* setnu.el:
* setnu.el ('setnu): New.
* toolbar-utils.el:
* toolbar-utils.el ('toolbar-utils): New.
* toolbar-utils.el (toolbar-utils):
* toolbar-utils.el ('toolbar-add-exec-macro): New.
* toolbar-utils.el (toolbar-add-exec-macro):
* uniquify.el:
* uniquify.el ('uniquify): New.
* vertical-mode.el:
* vertical-mode.el ('vertical-mode): New.
* where-was-i-db.el:
* where-was-i-db.el ('where-was-i-db): New.
* where-was-i-db.el (where-was-i-db):
* winring.el:
* winring.el ('winring): New.
* winring.el (winring):
Add define-behavior support.
* detached-minibuf.el:
* detached-minibuf.el (add-minibuf-options): Removed.
* detached-minibuf.el ('detached-minibuffer): New.
* detached-minibuf.el (toggle-minibuf): New.
Do not modify Options menu when define-behavior is set; not allowed.
Add define-behavior support. Delete `add-minibuf-options'.
Move minibuffer options to the behavior commands submenu.
* foldout.el:
* foldout.el (foldout-inhibit-key-bindings): Removed.
* foldout.el (foldout-install): New.
* foldout.el ('foldout): New.
* foldout.el (foldout):
Remove option to modify key bindings when loaded. Packages should
never do anything when loaded. Create an install function to do it
instead. Add define-behavior support and incorporate install function.
* lazy-shot.el:
* lazy-shot.el ('lazy-shot): New.
* lazy-shot.el (lazy-shot):
Add define-behavior support.
* live-icon.el:
* live-icon.el ('live-icon): New.
* saveplace.el:
* saveplace.el ('save-place): New.
* shell-font.el:
* shell-font.el (shell-font):
* shell-font.el ('shell-font): New.
Add define-behavior support.
Don't auto-install upon load.
xemacs-packages/efs/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* efs.el:
* efs.el ('efs): New.
* efs.el (efs):
Add define-behavior support.
xemacs-packages/eudc/ChangeLog addition:
2004-11-07 Ben Wing <ben(a)xemacs.org>
* eudc.el:
* eudc.el (eudc-menu): New.
* eudc.el (not):
* eudc.el ('eudc): New.
Add define-behavior support.
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
xemacs-packages/footnote/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* footnote.el:
* footnote.el (footnote-mode):
* footnote.el ('footnote): New.
xemacs-packages/games/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* gamegrid.el:
* gamegrid.el (gamegrid): New.
* snake.el:
* snake.el (snake): New.
* sokoban.el:
* sokoban.el (sokoban): New.
* tetris.el:
* tetris.el (tetris): New.
Define a custom group for each of these.
* sokoban.el ('sokoban): New.
* tetris.el ('tetris): New.
Add define-behavior support.
xemacs-packages/ispell/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* ispell.el:
* ispell.el ('ispell): New.
Add define-behavior support.
xemacs-packages/mh-e/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* mh-e.el:
* mh-e.el ('mh): New.
Add define-behavior support.
xemacs-packages/mine/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* xmine.el:
* xmine.el ('xmine): New.
Add define-behavior support.
xemacs-packages/misc-games/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* NeXTify.el:
* NeXTify.el (NeXTify): New.
* advocacy.el:
* advocacy.el (advocacy): New.
* blackbox.el:
* blackbox.el (blackbox): New.
* conx.el:
* conx.el (conx): New.
* decipher.el:
* decipher.el (decipher): New.
* dissociate.el:
* dissociate.el (dissociate): New.
* doctor.el:
* doctor.el (doctor): New.
* dunnet.el:
* dunnet.el (dunnet): New.
* flame.el:
* flame.el (flame): New.
* gomoku.el (gomoku): New.
* hanoi.el:
* hanoi.el (hanoi): New.
* life.el:
* life.el (life): New.
* morse.el:
* morse.el (morse): New.
* mpuz.el:
* mpuz.el (mpuz): New.
* rot13.el:
* rot13.el (rot13): New.
* studly.el:
* studly.el (studly): New.
Define a custom group for each of these.
* doctor.el ('doctor): New.
* dunnet.el ('dunnet): New.
* flame.el ('flame): New.
* hanoi.el ('hanoi): New.
* life.el ('life): New.
* mpuz.el ('mpuz): New.
Add define-behavior support.
xemacs-packages/os-utils/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* jka-compr.el:
* jka-compr.el ('jka-compr): New.
Add define-behavior support.
xemacs-packages/pcl-cvs/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* pcl-cvs-defs.el (progn):
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
* pcl-cvs.el:
* pcl-cvs.el ('pcl-cvs): New.
Add define-behavior support.
xemacs-packages/ps-print/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* ps-mule.el:
Add custom-define cookie for custom-defines.el support.
xemacs-packages/psgml/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* psgml-html.el (html-mode):
Clean up font-lock setup. XEmacs has done it the FSF way
for time immemorial.
xemacs-packages/text-modes/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* filladapt.el:
* filladapt.el ('filladapt): New.
* filladapt.el (filladapt):
Add define-behavior support.
* flyspell.el:
Add custom-define cookie for flyspell-emacs.
xemacs-packages/vc/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* vc-hooks.el:
* vc-hooks.el (featurep):
* vc-hooks.el ('vc): New.
Add autoload cookie for custom-defines.
Add define-behavior support.
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
xemacs-packages/vm/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* vm-version.el:
* vm-version.el ('vm): New.
Add define-behavior support.
xemacs-packages/w3/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* lisp/w3.el:
* lisp/w3.el ('w3): New.
Add define-behavior support.
xemacs-packages/xemacs-base/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* compile.el:
* compile.el ('grep): New.
* compile.el ('compile): New.
Add define-behavior support for compile and grep.
* shell.el:
* shell.el ('shell): New.
Add define-behavior support.
packages2 source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: xemacs-packages/xemacs-base/shell.el xemacs-packages/xemacs-base/compile.el xemacs-packages/w3/lisp/w3.el xemacs-packages/vm/vm-version.el xemacs-packages/vc/vc-hooks.el xemacs-packages/text-modes/flyspell.el xemacs-packages/text-modes/filladapt.el xemacs-packages/psgml/psgml-html.el xemacs-packages/ps-print/ps-mule.el xemacs-packages/pcl-cvs/pcl-cvs.el xemacs-packages/pcl-cvs/pcl-cvs-defs.el xemacs-packages/pc/pending-del.el xemacs-packages/os-utils/jka-compr.el xemacs-packages/misc-games/studly.el xemacs-packages/misc-games/rot13.el xemacs-packages/misc-games/mpuz.el xemacs-packages/misc-games/morse.el xemacs-packages/misc-games/life.el xemacs-packages/misc-games/hanoi.el xemacs-packages/misc-games/gomoku.el xemacs-packages/misc-games/flame.el xemacs-packages/misc-games/dunnet.el xemacs-packages/misc-games/doctor.el xemacs-packages/misc-games/dissociate.el xemacs-packages/misc-games/decipher.el xemacs-packages/misc-games/conx.el xemacs-packages/misc-games/b!
lackbox.el xemacs-packages/misc-games/advocacy.el xemacs-packages/misc-games/NeXTify.el xemacs-packages/mine/xmine.el xemacs-packages/mh-e/mh-e.el xemacs-packages/ispell/ispell.el xemacs-packages/games/tetris.el xemacs-packages/games/sokoban.el xemacs-packages/games/snake.el xemacs-packages/games/gamegrid.el xemacs-packages/footnote/footnote.el xemacs-packages/eudc/eudc.el xemacs-packages/efs/efs.el xemacs-packages/edit-utils/winring.el xemacs-packages/edit-utils/where-was-i-db.el xemacs-packages/edit-utils/vertical-mode.el xemacs-packages/edit-utils/uniquify.el xemacs-packages/edit-utils/toolbar-utils.el xemacs-packages/edit-utils/shell-font.el xemacs-packages/edit-utils/setnu.el xemacs-packages/edit-utils/scroll-in-place.el xemacs-packages/edit-utils/saveplace.el xemacs-packages/edit-utils/savehist.el xemacs-packages/edit-utils/saveconf.el xemacs-packages/edit-utils/rsz-minibuf.el xemacs-packages/edit-utils/resume.el xemacs-packages/edit-utils/reportmail.el xemacs-package!
s/edit-utils/redo.el xemacs-packages/edit-utils/recent-files.e!
l xemacs
-packages/edit-utils/power-macros.el xemacs-packages/edit-utils/popper.el xemacs-packages/edit-utils/permanent-buffers.el xemacs-packages/edit-utils/paren.el xemacs-packages/edit-utils/page-ext.el xemacs-packages/edit-utils/live-icon.el xemacs-packages/edit-utils/lazy-shot.el xemacs-packages/edit-utils/lazy-lock.el xemacs-packages/edit-utils/iswitchb.el xemacs-packages/edit-utils/id-select.el xemacs-packages/edit-utils/hippie-exp.el xemacs-packages/edit-utils/func-menu.el xemacs-packages/edit-utils/foldout.el xemacs-packages/edit-utils/flow-ctrl.el xemacs-packages/edit-utils/floating-toolbar.el xemacs-packages/edit-utils/file-part.el xemacs-packages/edit-utils/fast-lock.el xemacs-packages/edit-utils/edit-toolbar.el xemacs-packages/edit-utils/edit-faces.el xemacs-packages/edit-utils/detached-minibuf.el xemacs-packages/edit-utils/desktop.el xemacs-packages/edit-utils/dabbrev.el xemacs-packages/edit-utils/completion.el xemacs-packages/edit-utils/blink-paren.el xemacs-packages/e!
dit-utils/blink-cursor.el xemacs-packages/edit-utils/balloon-help.el xemacs-packages/edit-utils/avoid.el xemacs-packages/ediff/ediff-hook.el xemacs-packages/debug/gdb.el xemacs-packages/debug/dbx.el xemacs-packages/cookie/yow.el xemacs-packages/calendar/calendar.el mule-packages/skk/skk-foreword.el
cvs server: Diffing .
cvs server: Diffing mule-packages
cvs server: Diffing mule-packages/edict
cvs server: Diffing mule-packages/egg-its
cvs server: Diffing mule-packages/latin-unity
cvs server: Diffing mule-packages/leim
cvs server: Diffing mule-packages/leim/quail
cvs server: Diffing mule-packages/locale
cvs server: Diffing mule-packages/locale/app-defaults
cvs server: Diffing mule-packages/locale/app-defaults/de
cvs server: Diffing mule-packages/locale/app-defaults/fr
cvs server: Diffing mule-packages/locale/app-defaults/ja
cvs server: Diffing mule-packages/locale/app-defaults/ro
cvs server: Diffing mule-packages/locale/start-files
cvs server: Diffing mule-packages/locale/start-files/fr
cvs server: Diffing mule-packages/locale/start-files/ja
cvs server: Diffing mule-packages/locale/start-files/ro
cvs server: Diffing mule-packages/lookup
cvs server: Diffing mule-packages/lookup/etc
cvs server: Diffing mule-packages/lookup/lisp
cvs server: Diffing mule-packages/lookup/packages
cvs server: Diffing mule-packages/lookup/packages/dict-misc
cvs server: Diffing mule-packages/lookup/packages/jitenban97
cvs server: Diffing mule-packages/lookup/texi
cvs server: Diffing mule-packages/mule-base
Index: mule-packages/skk/skk-foreword.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/mule-packages/skk/skk-foreword.el,v
retrieving revision 1.5
diff -u -p -r1.5 skk-foreword.el
--- mule-packages/skk/skk-foreword.el 2002/04/28 07:12:27 1.5
+++ mule-packages/skk/skk-foreword.el 2005/01/31 20:55:38
＠＠ -453,6 +453,8 ＠＠
(define-obsolete-function-alias 'skk-isearch-backward 'isearch-backward)
(define-obsolete-function-alias 'skk-isearch-backward-regexp 'isearch-backward-regexp)
+;; XEmacs: this must autoload, for custom-defines
+;;;###autoload
(defconst skk-background-mode
;; from font-lock-make-faces of font-lock.el Welcome!
(cond
cvs server: Diffing mule-packages/skk/etc
cvs server: Diffing mule-packages/skk/texi
cvs server: Diffing unsupported
cvs server: Diffing unsupported/rendhalver
cvs server: Diffing unsupported/scop
cvs server: Diffing unsupported/scop/antlr-mode
cvs server: Diffing unsupported/scop/antlr-mode/lisp
cvs server: Diffing unsupported/scop/cogre
cvs server: Diffing unsupported/scop/ecb
cvs server: Diffing unsupported/scop/ede
cvs server: Diffing unsupported/scop/generic-modes
cvs server: Diffing unsupported/scop/vc
cvs server: Diffing unsupported/simon
cvs server: Diffing unsupported/simon/asn1
cvs server: Diffing unsupported/simon/epop3
cvs server: Diffing unsupported/simon/flim
cvs server: Diffing unsupported/simon/flim/tests
cvs server: Diffing unsupported/stephen
cvs server: Diffing unsupported/stephen/synfl
cvs server: Diffing unsupported/stephen/synfl/doc
cvs server: Diffing xemacs-packages
cvs server: Diffing xemacs-packages/Sun
cvs server: Diffing xemacs-packages/ada
cvs server: Diffing xemacs-packages/apel
cvs server: Diffing xemacs-packages/auctex
cvs server: Diffing xemacs-packages/auctex/etc
cvs server: Diffing xemacs-packages/auctex/images
cvs server: Diffing xemacs-packages/auctex/texi
cvs server: Diffing xemacs-packages/bbdb
cvs server: Diffing xemacs-packages/bbdb/lisp
cvs server: Diffing xemacs-packages/bbdb/misc
cvs server: Diffing xemacs-packages/bbdb/tex
cvs server: Diffing xemacs-packages/bbdb/texinfo
cvs server: Diffing xemacs-packages/bbdb/utils
cvs server: Diffing xemacs-packages/build
cvs server: Diffing xemacs-packages/c-support
cvs server: Diffing xemacs-packages/calc
cvs server: Diffing xemacs-packages/calendar
Index: xemacs-packages/calendar/calendar.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/calendar/calendar.el,v
retrieving revision 1.7
diff -u -p -r1.7 calendar.el
--- xemacs-packages/calendar/calendar.el 2003/08/28 06:57:28 1.7
+++ xemacs-packages/calendar/calendar.el 2005/01/31 20:55:39
＠＠ -2629,6 +2629,21 ＠＠ Defaults to today's date if DATE is not
(run-hooks 'calendar-load-hook)
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'calendar
+ "Not documented."
+:group 'editing ;; #### ?? Where does this go ??
+:commands
+ '(["%_3-Month Calendar" calendar]
+ ["%_Diary" diary]
+ ["%_Holidays" holidays]
+ ;; we're all pagans at heart ...
+ ["%_Phases of the Moon" phases-of-moon]
+ ["%_Sunrise/Sunset" sunrise-sunset])
+))
+
(provide 'calendar)
;;; Local variables:
cvs server: Diffing xemacs-packages/cc-mode
cvs server: Diffing xemacs-packages/clearcase
cvs server: Diffing xemacs-packages/cookie
Index: xemacs-packages/cookie/yow.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/cookie/yow.el,v
retrieving revision 1.2
diff -u -p -r1.2 yow.el
--- xemacs-packages/cookie/yow.el 2002/03/22 17:58:54 1.2
+++ xemacs-packages/cookie/yow.el 2005/01/31 20:55:40
＠＠ -134,6 +134,17 ＠＠ If called interactively, display a list
(doctor-ret-or-read 1)
(doctor-ret-or-read 1)))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'yow
+ "Not documented."
+:group 'games
+:commands
+ '(["Quote from %_Zippy" yow]
+ ["Ps%_ychoanalyze Zippy!" psychoanalyze-pinhead]))
+)
+
(provide 'yow)
;;; yow.el ends here
cvs server: Diffing xemacs-packages/crisp
cvs server: Diffing xemacs-packages/debug
Index: xemacs-packages/debug/dbx.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/debug/dbx.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 dbx.el
--- xemacs-packages/debug/dbx.el 1998/01/14 06:44:09 1.1.1.1
+++ xemacs-packages/debug/dbx.el 2005/01/31 20:55:40
＠＠ -168,6 +168,18 ＠＠ BEGIN bounds the search. If QUIET, just
(process-send-string dbx-process
(concat "stop at \"" file-name "\":" line "\n"))))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'dbx
+ "Not documented."
+:short-doc "DBX"
+:group 'programming
+:commands
+ '(["%_DBX..." dbx]))
+)
+
(provide 'dbx)
;;; dbx.el ends here
Index: xemacs-packages/debug/gdb.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/debug/gdb.el,v
retrieving revision 1.5
diff -u -p -r1.5 gdb.el
--- xemacs-packages/debug/gdb.el 2002/09/24 05:52:56 1.5
+++ xemacs-packages/debug/gdb.el 2005/01/31 20:55:40
＠＠ -711,6 +711,17 ＠＠ It is for customization by you.")
(set-buffer (find-file-noselect (car gdb-last-frame)))
(gdb-clear)))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'gdb
+ "Not documented."
+:short-doc "GDB"
+:group 'programming
+:commands
+ '(["%_GDB..." gdb]))
+)
+
(provide 'gdb)
;;; gdb.el ends here
cvs server: Diffing xemacs-packages/dictionary
cvs server: Diffing xemacs-packages/dictionary/debian
cvs server: Diffing xemacs-packages/dired
cvs server: Diffing xemacs-packages/docbookide
cvs server: Diffing xemacs-packages/ecb
cvs server: Diffing xemacs-packages/ecb/ecb-images
cvs server: Diffing xemacs-packages/ecb/ecb-images/default
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-10
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-14
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-15
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-16
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-17
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-18
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-19
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-20
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-21
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-10
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-14
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-15
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-16
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-17
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-18
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-19
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-20
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-21
cvs server: Diffing xemacs-packages/ecb/ecb-images/methods
cvs server: Diffing xemacs-packages/ecb/ecb-images/methods/height-14_to_21
cvs server: Diffing xemacs-packages/ecb/ecb-images/sources
cvs server: Diffing xemacs-packages/ecb/ecb-images/sources/height-14_to_21
cvs server: Diffing xemacs-packages/ecrypto
cvs server: Diffing xemacs-packages/edebug
cvs server: Diffing xemacs-packages/ediff
Index: xemacs-packages/ediff/ediff-hook.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ediff/ediff-hook.el,v
retrieving revision 1.11
diff -u -p -r1.11 ediff-hook.el
--- xemacs-packages/ediff/ediff-hook.el 2003/05/18 17:49:46 1.11
+++ xemacs-packages/ediff/ediff-hook.el 2005/01/31 20:55:41
＠＠ -149,8 +149,10 ＠＠
))
;; put these menus before Object-Oriented-Browser in Tools menu
+ ;; Sorry, this is not allowed in 21.5.
(if (and (featurep 'menubar) (not (featurep 'infodock))
- (not (featurep 'ediff-hook)))
+ (not (featurep 'ediff-hook))
+ (not (fboundp 'define-behavior-group)))
(ediff-xemacs-init-menus)))
;; Emacs--only if menu-bar is loaded
＠＠ -367,6 +369,14 ＠＠
) ; if purify-flag
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'ediff
+"Not documented."
+:group 'files
+:commands (list ediff-menu ediff-merge-menu epatch-menu ediff-misc-menu))
+)
(provide 'ediff-hook)
cvs server: Diffing xemacs-packages/ediff/etc
cvs server: Diffing xemacs-packages/edit-utils
Index: xemacs-packages/edit-utils/avoid.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/avoid.el,v
retrieving revision 1.6
diff -u -p -r1.6 avoid.el
--- xemacs-packages/edit-utils/avoid.el 2002/04/10 23:35:37 1.6
+++ xemacs-packages/edit-utils/avoid.el 2005/01/31 20:55:41
＠＠ -404,4 +404,37 ＠＠ definition of \"random distance\".)"
;;;###autoload
(add-minor-mode 'mouse-avoidance-mode 'mouse-avoidance-mode-line-string)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'avoid
+"For those who are annoyed by the mouse pointer obscuring text,
+this mode moves the mouse pointer - either just a little out of
+the way, or all the way to the corner of the frame.
+
+Customize `mouse-avoidance-mode' to one of the symbols `banish',
+`exile', `jump', `animate', `cat-and-mouse', `proteus', or `none'.
+
+Effects of the different modes:
+ * banish: Move the mouse to the upper-right corner on any keypress.
+ * exile: Move the mouse to the corner only if the cursor gets too close,
+ and allow it to return once the cursor is out of the way.
+ * jump: If the cursor gets too close to the mouse, displace the mouse
+ a random distance & direction.
+ * animate: As `jump', but shows steps along the way for illusion of motion.
+ * cat-and-mouse: Same as `animate'.
+ * proteus: As `animate', but changes the shape of the mouse pointer too.
+
+Whenever the mouse is moved, the frame is also raised.
+
+\(see `mouse-avoidance-threshold' for definition of \"too close\",
+and `mouse-avoidance-nudge-dist' and `mouse-avoidance-nudge-var' for
+definition of \"random distance\".)"
+:short-doc "Keep mouse away from cursor"
+:enable #'(lambda ()
+ (mouse-avoidance-mode 'animate))
+:disable #'(lambda ()
+ (mouse-avoidance-mode 'none)))
+)
+
;;; avoid.el ends here
Index: xemacs-packages/edit-utils/balloon-help.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/balloon-help.el,v
retrieving revision 1.6
diff -u -p -r1.6 balloon-help.el
--- xemacs-packages/edit-utils/balloon-help.el 2002/01/22 14:22:56 1.6
+++ xemacs-packages/edit-utils/balloon-help.el 2005/01/31 20:55:42
＠＠ -586,3 +586,52 ＠＠ This command must be bound to a mouse ev
(add-hook 'pre-command-hook 'balloon-help-pre-command-hook)
(add-hook 'mouse-leave-frame-hook 'balloon-help-mouse-leave-frame-hook)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'balloon-help
+"With Balloon Help enabled, a small frame is displayed whenever
+the mouse rests on an object that has a help property of some
+kind. The text of that help property is displayed in the frame.
+
+If you want Balloon Help mode enabled in some buffers only, use
+`balloon-help-minor-mode' instead.
+
+For extents, the 'balloon-help' property is checked.
+
+For toolbar buttons, the help-string slot of the toolbar button
+is checked.
+
+If the value is a string, it is used as the help message.
+
+If the property's value is a symbol, it is assumed to be the name
+of a function and it will be called with one argument, the object
+under the mouse, and the return value of that function will be
+used as the help message.
+
+The balloon-help frame is a transient window that is not
+normally decorated by window managers, so the following
+window manager directives may not be needed. But if they
+are:
+
+For ol[v]wm use this in .Xdefaults:
+ olvwm.NoDecor: balloon-help
+ or
+ olwm.MinimalDecor: balloon-help
+
+For fvvm version 1 use this in your .fvwmrc:
+ NoTitle balloon-help
+or
+ Style \"balloon-help\" NoTitle, NoHandles, BorderWidth 0
+
+For twm use this in your .twmrc:
+ NoTitle { \"balloon-help\" }
+"
+:short-doc "Balloon help"
+:group 'display
+:enable #'(lambda ()
+ (balloon-help-mode 1))
+:disable #'(lambda ()
+ (balloon-help-mode 0)))
+)
Index: xemacs-packages/edit-utils/blink-cursor.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/blink-cursor.el,v
retrieving revision 1.4
diff -u -p -r1.4 blink-cursor.el
--- xemacs-packages/edit-utils/blink-cursor.el 2001/12/04 02:15:32 1.4
+++ xemacs-packages/edit-utils/blink-cursor.el 2005/01/31 20:55:42
＠＠ -134,6 +134,19 ＠＠ each TIMEOUT secs (can be a float)."
(if (not last-input-time)
(setq last-input-time (cons 0 0))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'blink-cursor
+"Enable or disable a blinking cursor."
+:short-doc "Make cursor blink"
+:group 'keyboard
+:enable #'(lambda ()
+ (blink-cursor-mode 1))
+:disable #'(lambda ()
+ (blink-cursor-mode 0)))
+)
+
(provide 'blink-cursor)
;;; blink-cursor.el ends here
Index: xemacs-packages/edit-utils/blink-paren.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/blink-paren.el,v
retrieving revision 1.2
diff -u -p -r1.2 blink-paren.el
--- xemacs-packages/edit-utils/blink-paren.el 2000/10/06 09:08:00 1.2
+++ xemacs-packages/edit-utils/blink-paren.el 2005/01/31 20:55:42
＠＠ -176,6 +176,19 ＠＠ With a non-positive argument, turns it o
(interactive)
(blink-paren 1))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'blink-paren
+"Blink the matching paren."
+:short-doc "Blink the matching paren"
+:group 'display
+:enable #'(lambda ()
+ (blink-paren 1))
+:disable #'(lambda ()
+ (blink-paren 0)))
+)
+
(provide 'blink-paren)
(blink-paren 1)
Index: xemacs-packages/edit-utils/completion.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/completion.el,v
retrieving revision 1.4
diff -u -p -r1.4 completion.el
--- xemacs-packages/edit-utils/completion.el 2004/06/18 05:43:55 1.4
+++ xemacs-packages/edit-utils/completion.el 2005/01/31 20:55:42
＠＠ -2722,6 +2722,180 ＠＠ TYPE is the type of the wrapper to be ad
(cmpl-statistics-block
(record-completion-file-loaded))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'completion
+"After you type a few characters, pressing the \"complete\" key inserts
+the rest of the word you are likely to type.
+
+This watches all the words that you type and remembers them. When
+typing a new word, pressing \"complete\" (meta-return) \"completes\" the
+word by inserting the most recently used word that begins with the
+same characters. If you press meta-return repeatedly, it cycles
+through all the words it knows about.
+
+ If you like the completion then just continue typing, it is as if you
+entered the text by hand. If you want the inserted extra characters
+to go away, type control-w or delete. More options are described below.
+
+ The guesses are made in the order of the most recently \"used\". Typing
+in a word and then typing a separator character (such as a space) \"uses\"
+the word. So does moving a cursor over the word. If no words are found,
+it uses an extended version of the dabbrev style completion.
+
+ You automatically save the completions you use to a file between
+sessions.
+
+ Completion enables programmers to enter longer, more descriptive
+variable names while typing fewer keystrokes than they normally would.
+
+
+Full documentation
+--------------------
+
+ A \"word\" is any string containing characters with either word or symbol
+syntax. [E.G. Any alphanumeric string with hyphens, underscores, etc.]
+Unless you change the constants, you must type at least three characters
+for the word to be recognized. Only words longer than 6 characters are
+saved.
+
+ When you load this file, completion will be on. I suggest you use the
+compiled version (because it is noticeably faster).
+
+ M-X completion-mode toggles whether or not new words are added to the
+database by changing the value of enable-completion.
+
+ SAVING/LOADING COMPLETIONS
+ Completions are automatically saved from one session to another
+(unless save-completions-flag or enable-completion is nil).
+Loading this file (or calling initialize-completions) causes EMACS
+to load a completions database for a saved completions file
+(default: ~/.completions). When you exit, EMACS saves a copy of the
+completions that you
+often use. When you next start, EMACS loads in the saved completion file.
+
+ The number of completions saved depends loosely on
+*saved-completions-decay-factor*. Completions that have never been
+inserted via \"complete\" are not saved. You are encouraged to experiment
+with different functions (see compute-completion-min-num-uses).
+
+ Some completions are permanent and are always saved out. These
+completions have their num-uses slot set to T. Use
+add-permanent-completion to do this
+
+ Completions are saved only if enable-completion is T. The number of old
+versions kept of the saved completions file is controlled by
+completions-file-versions-kept.
+
+COMPLETE KEY OPTIONS
+ The complete function takes a numeric arguments.
+ control-u :: leave the point at the beginning of the completion rather
+ than the middle.
+ a number :: rotate through the possible completions by that amount
+ `-' :: same as -1 (insert previous completion)
+
+HOW THE DATABASE IS MAINTAINED
+ <write>
+
+UPDATING THE DATABASE MANUALLY
+ m-x kill-completion
+ kills the completion at point.
+ m-x add-completion
+ m-x add-permanent-completion
+
+UPDATING THE DATABASE FROM A SOURCE CODE FILE
+ m-x add-completions-from-buffer
+ Parses all the definition names from a C or LISP mode buffer and
+ adds them to the completion database.
+
+ m-x add-completions-from-lisp-file
+ Parses all the definition names from a C or Lisp mode file and
+ adds them to the completion database.
+
+UPDATING THE DATABASE FROM A TAGS TABLE
+ m-x add-completions-from-tags-table
+ Adds completions from the current tags-table-buffer.
+
+HOW A COMPLETION IS FOUND
+ <write>
+
+STRING CASING
+ Completion is string case independent if case-fold-search has its
+ normal default of T. Also when the completion is inserted the case of the
+ entry is coerced appropriately.
+ [E.G. APP --> APPROPRIATELY app --> appropriately
+ App --> Appropriately]
+
+INITIALIZATION
+ The form `(initialize-completions)' initializes the completion system by
+trying to load in the user's completions. After the first cal, further
+calls have no effect so one should be careful not to put the form in a
+site's standard site-init file.
+
+--------------------------------------------------------------------------
+
+
+
+--------------------------------------------------------------------------
+Functions you might like to call
+--------------------------------------------------------------------------
+
+ add-completion string &optional num-uses
+ Adds a new string to the database
+
+ add-permanent-completion string
+ Adds a new string to the database with num-uses = T
+
+
+ kill-completion string
+ Kills the completion from the database.
+
+ clear-all-completions
+ Clears the database
+
+ list-all-completions
+ Returns a list of all completions.
+
+
+ next-completion string &optional index
+ Returns a completion entry that starts with string.
+
+ find-exact-completion string
+ Returns a completion entry that exactly matches string.
+
+ complete
+ Inserts a completion at point
+
+ initialize-completions
+ Loads the completions file and sets up so that exiting emacs will
+ save them.
+
+ save-completions-to-file &optional filename
+ load-completions-from-file &optional filename
+
+----------------------------------------------
+Other functions
+----------------------------------------------
+
+ get-completion-list string
+
+These things are for manipulating the structure
+ make-completion string num-uses
+ completion-num-uses completion
+ completion-string completion
+ set-completion-num-uses completion num-uses
+ set-completion-string completion string
+"
+:group 'editing
+:short-doc "Dynamic word completion"
+:require 'completion
+:enable #'(lambda ()
+ (initialize-completion))
+ ;; can't :disable
+ )
+)
+
(provide 'completion)
;;; completion.el ends here
Index: xemacs-packages/edit-utils/dabbrev.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/dabbrev.el,v
retrieving revision 1.4
diff -u -p -r1.4 dabbrev.el
--- xemacs-packages/edit-utils/dabbrev.el 2004/11/09 04:19:58 1.4
+++ xemacs-packages/edit-utils/dabbrev.el 2005/01/31 20:55:43
＠＠ -1055,6 +1055,61 ＠＠ Leaves point at the location of the star
"^No possible abbreviation preceding point$"))
(add-to-list 'debug-ignored-errors mess))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'dabbrev
+"The purpose with this package is to let you write just a few
+characters of words you've written earlier to be able to expand
+them.
+
+To expand a word, just put the point right after the word and press
+M-/ (dabbrev-expand) or M-C-/ (dabbrev-completion).
+
+Check out the customizable variables below to learn about all the
+features of this package.
+
+ Hints and tips for major modes writers:
+
+Recommended values C/Lisp etc text
+dabbrev-case-fold-search nil t
+dabbrev-case-replace nil t
+
+Set the variables you want special for your mode like this:
+(set (make-local-variable 'dabbrev-case-replace) nil)
+Then you don't interfere with other modes.
+
+If your mode handles buffers that refers to other buffers
+(i.e. compilation-mode, gud-mode), then try to set
+`dabbrev-select-buffers-function' or `dabbrev-friend-buffer-function'
+to a function that point out those buffers.
+
+Same goes for major-modes that are connected to other modes. There
+are for instance a number of mail-modes. One for reading, one for
+creating a new mail etc. Maybe those should be connected.
+
+Example for GNUS (when we write a reply, we want dabbrev to look in
+the article for expansion):
+(set (make-local-variable 'dabbrev-friend-buffer-function)
+ (lambda (buffer)
+ (save-excursion
+ (set-buffer buffer)
+ (memq major-mode '(news-reply-mode gnus-article-mode)))))
+
+
+Known bugs and limitations.
+- Possible to do several levels of `dabbrev-completion' in the
+ minibuffer.
+- dabbrev-completion doesn't handle resetting the globals variables
+ right. It resets them after finding the abbrev."
+:short-doc "dynamic abbreviation package"
+:group 'editing
+:commands '(["Expand previous word \"dynamically\"" dabbrev-expand])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
(provide 'dabbrev)
;; dabbrev.el ends here
Index: xemacs-packages/edit-utils/desktop.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/desktop.el,v
retrieving revision 1.8
diff -u -p -r1.8 desktop.el
--- xemacs-packages/edit-utils/desktop.el 2004/06/17 11:09:39 1.8
+++ xemacs-packages/edit-utils/desktop.el 2005/01/31 20:55:43
＠＠ -796,6 +796,77 ＠＠ to provide correct modes for autoloaded
(desktop-load-default)
(desktop-read))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'desktop
+"Save the Desktop, i.e.,
+ - some global variables
+ - the list of buffers with associated files. For each buffer also
+ - the major mode
+ - the default directory
+ - the point
+ - the mark & mark-active
+ - buffer-read-only
+ - some local variables
+
+To use this, first put these two lines in the bottom of your .emacs
+file (the later the better):
+
+ (desktop-load-default)
+ (desktop-read)
+
+Between these two lines you may wish to add something that updates the
+variables `desktop-globals-to-save' and/or `desktop-locals-to-save'. If
+for instance you want to save the local variable `foobar' for every buffer
+in which it is local, you could add the line
+
+ (setq desktop-locals-to-save (cons 'foobar desktop-locals-to-save))
+
+To avoid saving excessive amounts of data you may also wish to add
+something like the following
+
+ (add-hook 'kill-emacs-hook
+ '(lambda ()
+ (desktop-truncate search-ring 3)
+ (desktop-truncate regexp-search-ring 3)))
+
+which will make sure that no more than three search items are saved. You
+must place this line *after* the `(desktop-load-default)' line. See also
+the variable `desktop-save-hook'.
+
+Start Emacs in the root directory of your \"project\"
+. The desktop saver
+is inactive by default. You activate it by M-x desktop-save RET. When
+you exit the next time the above data will be saved. This ensures that
+all the files you were editing will be reloaded the next time you start
+Emacs from the same directory and that points will be set where you
+left them. If you save a desktop file in your home directory it will
+act as a default desktop when you start Emacs from a directory that
+doesn't have its own. I never do this, but you may want to.
+
+Some words on minor modes: Most minor modes are controlled by
+buffer-local variables, which have a standard save / restore
+mechanism. To handle all minor modes, we take the following
+approach: (1) check whether the variable name from
+`minor-mode-alist' is also a function; and (2) use translation
+table `desktop-minor-mode-table' in the case where the two names
+are not the same.
+
+By the way: don't use desktop.el to customize Emacs -- the file .emacs
+in your home directory is used for that. Saving global default values
+for buffers is an example of misuse.
+
+PLEASE NOTE: The kill ring can be saved as specified by the variable
+`desktop-globals-to-save' (by default it isn't). This may result in saving
+things you did not mean to keep. Use M-x desktop-clear RET."
+:short-doc "save partial status of Emacs when killed"
+:group 'editing
+;; #### Write the hooks correctly so they don't require manual modification
+;; of init.el.
+ )
+)
+
(provide 'desktop)
;;; desktop.el ends here
Index: xemacs-packages/edit-utils/detached-minibuf.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/detached-minibuf.el,v
retrieving revision 1.2
diff -u -p -r1.2 detached-minibuf.el
--- xemacs-packages/edit-utils/detached-minibuf.el 2001/01/15 05:54:31 1.2
+++ xemacs-packages/edit-utils/detached-minibuf.el 2005/01/31 20:55:43
＠＠ -42,11 +42,11 ＠＠
:group 'frames)
-(defcustom add-minibuf-options t
- "*If nil, prevent minibuffer options from being added to the Options menu.\
-This must be set before detached-minibuf is loaded."
-:type 'boolean
-:group 'detached-minibuf)
+; (defcustom add-minibuf-options t
+; "*If nil, prevent minibuffer options from being added to the Options menu.\
+; This must be set before detached-minibuf is loaded."
+;:type 'boolean
+;:group 'detached-minibuf)
(defcustom minibuf-frame-height 1
"*The height in lines of the minibuffer frame created by make-detached-minibuf"
:type 'integer
＠＠ -64,72 +64,31 ＠＠ This must be set before detached-minibuf
:type 'integer
:group 'detached-minibuf)
-;;
-;; Add minibuffer options to the Options menu
-(if add-minibuf-options
- (progn
- (defun toggle-minibuf ()
- (interactive)
- (if (equal (frame-property (selected-frame) 'minibuffer) t)
-
- ;; This frame already has a minibuffer, so remove the minibuffer.
- ;; Unfortunately, we must delete and redraw the frame
- (let ((fp (frame-properties (selected-frame)))
- (buf (current-buffer))
- (orig (selected-frame)))
-
- ;; Create and select the new frame;
- ;; we have to do this before we delete the old frame.
- (setq fp (plist-remprop fp 'window-id)
- fp (plist-remprop fp 'minibuffer))
- (select-frame
- (make-frame (plist-put fp 'minibuffer nil)))
- (switch-to-buffer buf)
-
- (set-frame-properties
- orig (list 'minibuffer default-minibuffer-frame))
- (delete-frame orig t))
-
- ;; This frame does not have a minibuffer, so add one
- (set-frame-property (selected-frame) 'minibuffer t)))
-
- ;; The menu structure is different before XEmacs 21.2.
- ;; Under 21.1 and previous, add menu items to
- ;; Options/Frame Appearance. Under 21.2+, add the
- ;; menu items to Options/Display.
- (let ((entry-name (if (fboundp 'purecopy-menubar)
- '("Options" "Frame Appearance")
- '("Options" "Display"))))
- (add-menu-button entry-name
- "------"
- nil)
- (add-menu-button entry-name
- ["Toggle minibuffer"
- (toggle-minibuf)
- :style toggle
- :active (not (equal (selected-frame)
- default-minibuffer-frame))
- :selected (equal
- (frame-property (selected-frame) 'minibuffer)
- t)]
- nil)
- (add-menu-button entry-name
- ["Default minibuffer here"
- (setq default-minibuffer-frame (selected-frame))
- :style toggle
- :active (let ((mbf (frame-property
- (selected-frame) 'minibuffer)))
- (or (equal mbf (selected-frame))
- (equal mbf t)))
- :selected (equal (selected-frame)
- default-minibuffer-frame)]
- nil)
- (add-menu-button entry-name
- ["Make a detached minibuffer"
- (make-detached-minibuf)
- :style nil]
- nil))))
+(defun toggle-minibuf ()
+ "Toggle whether the minibuffer exists in the current frame."
+ (interactive)
+ (if (equal (frame-property (selected-frame) 'minibuffer) t)
+ ;; This frame already has a minibuffer, so remove the minibuffer.
+ ;; Unfortunately, we must delete and redraw the frame
+ (let ((fp (frame-properties (selected-frame)))
+ (buf (current-buffer))
+ (orig (selected-frame)))
+
+ ;; Create and select the new frame;
+ ;; we have to do this before we delete the old frame.
+ (setq fp (plist-remprop fp 'window-id)
+ fp (plist-remprop fp 'minibuffer))
+ (select-frame
+ (make-frame (plist-put fp 'minibuffer nil)))
+ (switch-to-buffer buf)
+
+ (set-frame-properties
+ orig (list 'minibuffer default-minibuffer-frame))
+ (delete-frame orig t))
+
+ ;; This frame does not have a minibuffer, so add one
+ (set-frame-property (selected-frame) 'minibuffer t)))
;;
;; Create a minibuffer-only frame.
;;
＠＠ -163,6 +122,39 ＠＠ This must be set before detached-minibuf
;; Bogus! But it avoids annoying screen flash at startup
(if (not command-line-args-left)
(frame-notice-user-settings)))))
+
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'detached-minibuffer
+"Support a detached minibuffer"
+:short-doc "Support a detached minibuffer"
+:group 'buffers-and-windows
+:commands '(["Toggle minibuffer"
+ (toggle-minibuf)
+ :style toggle
+ :active (not (equal (selected-frame)
+ default-minibuffer-frame))
+ :selected (equal
+ (frame-property (selected-frame) 'minibuffer)
+ t)]
+ ["Default minibuffer here"
+ (setq default-minibuffer-frame (selected-frame))
+ :style toggle
+ :active (let ((mbf (frame-property
+ (selected-frame) 'minibuffer)))
+ (or (equal mbf (selected-frame))
+ (equal mbf t)))
+ :selected (equal (selected-frame)
+ default-minibuffer-frame)]
+ ["Make a detached minibuffer"
+ (make-detached-minibuf)
+ :style nil])
+ ;; no :enable
+ ;; no :disable
+ )
+)
(provide 'detached-minibuf)
Index: xemacs-packages/edit-utils/edit-faces.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/edit-faces.el,v
retrieving revision 1.4
diff -u -p -r1.4 edit-faces.el
--- xemacs-packages/edit-utils/edit-faces.el 1999/11/27 20:49:58 1.4
+++ xemacs-packages/edit-utils/edit-faces.el 2005/01/31 20:55:43
＠＠ -370,4 +370,21 ＠＠ M-x edit-faces."
(delete-window))
(kill-buffer "*Edit Faces*"))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'edit-faces
+"This is the file that won't die. Even though we have otherwise completely
+converted to custom, there is still apparently a need to view a lot of
+faces in one buffer."
+:short-doc "Interactive face editing mode"
+:group 'display
+:commands '(["Edit faces" edit-faces]
+ )
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
;;; edit-faces.el ends here
Index: xemacs-packages/edit-utils/edit-toolbar.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/edit-toolbar.el,v
retrieving revision 1.3
diff -u -p -r1.3 edit-toolbar.el
--- xemacs-packages/edit-utils/edit-toolbar.el 2000/07/16 11:22:46 1.3
+++ xemacs-packages/edit-utils/edit-toolbar.el 2005/01/31 20:55:44
＠＠ -542,6 +542,29 ＠＠ Alternatively, I can do this for you now
(or exists (edit-toolbar-prompt-for-initialization))))
(set-buffer-modified-p nil))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'edit-toolbar
+"To use edit-toolbar.el, simply type M-x edit-toolbar RET
+
+For help on the various commands you can type ? in a edit-toolbar
+buffer. To save a modified toolbar type C-x C-s in an edit-toolbar
+buffer. If you want to use a saved toolbar in your future XEmacs
+sessions, add the following line of code to your .emacs file:
+
+ (load \"~/.xemacs/.toolbar\")
+"
+:short-doc "Interactive toolbar editing mode"
+:group 'toolbars
+:commands '(["Edit toolbar" edit-toolbar]
+ )
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
(provide 'edit-toolbar)
;;; edit-toolbar.el ends here
Index: xemacs-packages/edit-utils/fast-lock.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/fast-lock.el,v
retrieving revision 1.3
diff -u -p -r1.3 fast-lock.el
--- xemacs-packages/edit-utils/fast-lock.el 2000/04/07 08:47:40 1.3
+++ xemacs-packages/edit-utils/fast-lock.el 2005/01/31 20:55:44
＠＠ -766,6 +766,55 ＠＠ See `fast-lock-get-face-properties' for
(unless (assq 'fast-lock-mode minor-mode-alist)
(setq minor-mode-alist (append minor-mode-alist '((fast-lock-mode nil)))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'fast-lock
+"Fast Lock mode is a Font Lock support mode.
+It makes visiting a file in Font Lock mode faster by restoring its face text
+properties from automatically saved associated Font Lock cache files.
+
+See also the lazy-lock package. (But don't use the two at the same time!)
+
+When you visit a file (which has `font-lock-mode' enabled) that has a
+corresponding Font Lock cache file associated with it, the Font Lock cache
+will be loaded from that file instead of being generated by Font Lock code.
+
+Caveats:
+
+A cache will be saved when visiting a compressed file using crypt++, but not
+be read. This is a \"feature\"/\"consequence\"/\"bug\" of crypt++.
+
+Version control packages are likely to stamp all over file modification
+times. Therefore the act of checking out may invalidate a cache.
+
+More specifically:
+
+If Fast Lock mode is enabled, and the current buffer does not contain any text
+properties, any associated Font Lock cache is used if its timestamp matches the
+buffer's file, and its `font-lock-keywords' match those that you are using.
+
+Font Lock caches may be saved:
+- When you save the file's buffer.
+- When you kill an unmodified file's buffer.
+- When you exit Emacs, for all unmodified or saved buffers.
+Depending on the value of `fast-lock-save-events'.
+See also the commands `fast-lock-read-cache' and `fast-lock-save-cache'.
+
+Use \\[font-lock-fontify-buffer] to fontify the buffer if the cache is bad.
+
+Various methods of control are provided for the Font Lock cache. In general,
+see variable `fast-lock-cache-directories' and function `fast-lock-cache-name'.
+For saving, see variables `fast-lock-minimum-size', `fast-lock-save-events',
+`fast-lock-save-others' and `fast-lock-save-faces'."
+:short-doc "Automagic text properties caching for fast Font Lock mode"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'font-lock-mode-hook 'turn-on-fast-lock))
+:disable #'(lambda ()
+ (remove-hook 'font-lock-mode-hook 'turn-on-fast-lock))
+ )
+)
;; Provide ourselves:
(provide 'fast-lock)
Index: xemacs-packages/edit-utils/file-part.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/file-part.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 file-part.el
--- xemacs-packages/edit-utils/file-part.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/file-part.el 2005/01/31 20:55:44
＠＠ -271,3 +271,28 ＠＠ Marks the master buffer as modified."
(set-buffer (extent-buffer x))
(set-buffer-modified-p t)))))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'file-part
+"Treat a section of a buffer as a separate file.
+
+Commands:
+
+`make-file-part'
+
+ Make a file part on buffer BUFFER out of the region. Call it NAME.
+This command creates a new buffer containing the contents of the
+region and marks the buffer as referring to the specified buffer,
+called the `master buffer'. When the file-part buffer is saved,
+its changes are integrated back into the master buffer. When the
+master buffer is deleted, all file parts are deleted with it.
+"
+:short-doc "treat a section of a buffer as a separate file"
+:group 'files
+:commands '(["Make file part" make-file-part])
+ ;; no :enable
+ ;; no :disable
+ )
+)
Index: xemacs-packages/edit-utils/floating-toolbar.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/floating-toolbar.el,v
retrieving revision 1.3
diff -u -p -r1.3 floating-toolbar.el
--- xemacs-packages/edit-utils/floating-toolbar.el 2000/10/06 09:08:01 1.3
+++ xemacs-packages/edit-utils/floating-toolbar.el 2005/01/31 20:55:44
＠＠ -382,4 +382,63 ＠＠ extent local toolbar."
(not (eq (device-type) 'x))
(setq floating-toolbar-frame (floating-toolbar-make-toolbar-frame 0 0)))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'floating-toolbar
+"The command `floating-toolbar' pops up a small frame
+containing a toolbar. The command should be bound to a
+button-press event. If the mouse press happens over an
+extent that has a non-nil 'floating-toolbar property, the
+value of that property is the toolbar instantiator that will
+be displayed. Otherwise the toolbar displayed is taken from
+the variable `floating-toolbar'. This variable can be made
+buffer local to produce buffer local floating toolbars.
+
+`floating-toolbar-or-popup-mode-menu' works like `floating-toolbar'
+except that if no toolbar is found, `popup-mode-menu' is called.
+
+`floating-toolbar-from-extent-or-popup-mode-menu' works like
+`floating-toolbar-or-popup-mode-menu' except only extent local
+toolbars are used; the value of floating-toolbar is not used.
+
+Installation:
+
+You will also need to bind a mouse click to `floating-toolbar' or to
+`floating-toolbar-or-popup-mode-menu'.
+
+For 19.12 users:
+ If you are using fvwm, [tv]twm or ol[v]wm, you can also add
+ the following lines to various configuration file to use
+ minimal decorations on the toolbar frame.
+
+ In .emacs:
+ (setq floating-toolbar-frame-name \"floating-toolbar\")
+
+ For ol[v]wm use this in .Xdefaults:
+ olvwm.NoDecor: floating-toolbar
+ or
+ olwm.MinimalDecor: floating-toolbar
+
+ For fvvm use this in your .fvwmrc:
+ NoTitle floating-toolbar
+ or
+ Style \"floating-toolbar\" NoTitle, NoHandles, BorderWidth 0
+
+ For twm use this in your .twmrc:
+ NoTitle { \"floating-toolbar\" }
+
+Under 19.13 and later versions the floating-toolbar frame uses a
+transient window that is not normally decorated by window
+managers. So the window manager directives should not be
+needed for XEmacs 19.13 and beyond."
+:short-doc "popup toolbar support for XEmacs"
+:group 'toolbars
+:commands '(["Pop up floating toolbar" floating-toolbar])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
;;; floating-toolbar.el ends here
Index: xemacs-packages/edit-utils/flow-ctrl.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/flow-ctrl.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 flow-ctrl.el
--- xemacs-packages/edit-utils/flow-ctrl.el 1998/01/14 06:36:15 1.1.1.1
+++ xemacs-packages/edit-utils/flow-ctrl.el 2005/01/31 20:55:44
＠＠ -115,6 +115,35 ＠＠ value of \"vt100-nam\" is treated the sa
(if term
(enable-flow-control))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'flow-control
+"Terminals that use XON/XOFF flow control can cause problems with
+GNU Emacs users. This file contains Emacs Lisp code that makes it
+easy for a user to deal with this problem, when using such a
+terminal.
+
+To invoke these adjustments, a user need only invoke the function
+enable-flow-control-on with a list of terminal types in his/her own
+.emacs file. As arguments, give it the names of one or more terminal
+types in use by that user which require flow control adjustments.
+Here's an example:
+
+ (enable-flow-control-on \"vt200\" \"vt300\" \"vt101\" \"vt131\")
+
+Portability note: This uses (getenv \"TERM\"), and therefore probably
+won't work outside of UNIX-like environments.
+"
+:short-doc "help for lusers on cu(1) or ttys with wired-in ^S/^Q flow control"
+:group 'tty
+:enable #'(lambda ()
+ (enable-flow-control 1))
+:disable #'(lambda ()
+ (enable-flow-control -1))
+ )
+)
+
(provide 'flow-ctrl)
;;; flow-ctrl.el ends here
Index: xemacs-packages/edit-utils/foldout.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/foldout.el,v
retrieving revision 1.2
diff -u -p -r1.2 foldout.el
--- xemacs-packages/edit-utils/foldout.el 2000/04/07 09:15:56 1.2
+++ xemacs-packages/edit-utils/foldout.el 2005/01/31 20:55:44
＠＠ -101,11 +101,11 ＠＠
;; To use foldout, put this in your .emacs:-
;;
-;; (require 'foldout)
+;; (foldout-install)
;;
;; If you don't want it loaded until you need it, try this instead:-
;;
-;; (eval-after-load "outline" '(require 'foldout))
+;; (eval-after-load "outline" '(foldout-install))
;;; Advertisements:
＠＠ -518,9 +518,6 ＠＠ if the event didn't occur on a heading."
;;; Keymaps:
-(defvar foldout-inhibit-key-bindings nil
- "Set non-NIL before loading foldout to inhibit key bindings.")
-
(defvar foldout-mouse-modifiers '(meta control)
"List of modifier keys to apply to foldout's mouse events.
＠＠ -544,8 +541,9 ＠＠ Valid modifiers are shift, control, meta
((eq button 3)
(funcall 'foldout-mouse-hide-or-exit event click-count))))))
-(if foldout-inhibit-key-bindings
- ()
+;;;###autoload
+(defun foldout-install ()
+ "Install foldout."
(define-key outline-mode-map "\C-c\C-z" 'foldout-zoom-subtree)
(define-key outline-mode-map "\C-c\C-x" 'foldout-exit-fold)
(define-key outline-minor-mode-map
＠＠ -574,6 +572,86 ＠＠ Valid modifiers are shift, control, meta
(define-key outline-minor-mode-map mouse-2 'mouse-track)
(define-key outline-minor-mode-map mouse-3 'mouse-track)
))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'foldout
+"This file provides folding editor extensions for outline-mode and
+outline-minor-mode buffers. What's a \"folding editor\"? Read on...
+
+Imagine you're in an outline-mode buffer and you've hidden all the text and
+subheadings under your level-1 headings. You now want to look at the stuff
+hidden under one of these headings. Normally you'd do C-c C-e (show-entry)
+to expose the body or C-c C-i to expose the child (level-2) headings.
+
+With foldout, you do C-c C-z (foldout-zoom-subtree). This exposes the body
+and child subheadings and narrows the buffer so that only the level-1
+heading, the body and the level-2 headings are visible. If you now want to
+look under one of the level-2 headings, position the cursor on it and do C-c
+C-z again. This exposes the level-2 body and its level-3 child subheadings
+and narrows the buffer again. You can keep on zooming in on successive
+subheadings as much as you like. A string in the modeline tells you how
+deep you've gone.
+
+When zooming in on a heading you might only want to see the child
+subheadings. You do this by specifying a numeric argument: C-u C-c C-z.
+You can specify the number of levels of children too (c.f. show-children):
+e.g. M-2 C-c C-z exposes two levels of child subheadings. Alternatively,
+you might only be interested in the body. You do this by specifying a
+negative argument: M-- C-c C-z. You can also cause the whole subtree to be
+expanded, similar to C-c C-s (show-subtree), by specifying a zero argument:
+M-0 C-c C-z.
+
+While you're zoomed in you can still use outline-mode's exposure and hiding
+functions. It won't upset foldout at all. Also, since the buffer is
+narrowed, \"global\" editing actions will only affect the stuff under the
+zoomed-in heading. This is useful for restricting changes to a particular
+chapter or section of your document.
+
+You unzoom (exit) a fold by doing C-c C-x (foldout-exit-fold). This hides
+all the text and subheadings under the top-level heading and returns you to
+the previous view of the buffer. Specifying a numeric argument exits that
+many folds. Specifying a zero argument exits *all* folds.
+
+You might want to exit a fold *without* hiding the text and subheadings.
+You do this by specifying a negative argument. For example, M--2 C-c C-x
+exits two folds and leaves the text and subheadings exposed.
+
+Foldout also provides mouse bindings for entering and exiting folds and for
+showing and hiding text. Hold down Meta and Control, then click a mouse
+button as follows:-
+
+ mouse-1 (foldout-mouse-zoom) zooms in on the heading clicked on:-
+
+ single click expose body
+ double click expose subheadings
+ triple click expose body and subheadings
+ quad click expose entire subtree
+
+ mouse-2 (foldout-mouse-show) exposes text under the heading clicked on:-
+
+ single click expose body
+ double click expose subheadings
+ triple click expose body and subheadings
+ quad click expose entire subtree
+
+ mouse-3 (foldout-mouse-hide-or-exit) hides text under the heading clicked
+ on or exits the fold:-
+
+ single click hide subtree
+ double click exit fold and hide text
+ triple click exit fold without hiding text
+ quad click exit all folds and hide text
+
+You can change the modifier keys used by setting `foldout-mouse-modifiers'.
+"
+:short-doc "Folding extensions for outline-mode"
+:group 'editing
+:require 'foldout
+:enable #'foldout-install
+ )
+)
(provide 'foldout)
Index: xemacs-packages/edit-utils/func-menu.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/func-menu.el,v
retrieving revision 1.28
diff -u -p -r1.28 func-menu.el
--- xemacs-packages/edit-utils/func-menu.el 2004/12/22 21:42:03 1.28
+++ xemacs-packages/edit-utils/func-menu.el 2005/01/31 20:55:45
＠＠ -2752,6 +2752,48 ＠＠ and then kill it will not be slowed down
(set-buffer buffer)
(turn-on-fume-mode)))))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'func-menu
+ "Suppose you have a file with a lot of functions in it. Well, this
+package makes it easy to jump to any of those functions. The names of
+the functions in the current buffer are automatically put into menubar
+menu, you select one of the function-names and the point is moved to
+that very function. The mark is pushed on the mark-ring, so you can
+easily go back to where you were. Alternatively, you can use enter the
+name of the desired function via the minibuffer which offers
+completing read input. In addition, the name of the function before
+point is optionally displayed in the modeline."
+:short-doc "Add a menu of defined functions"
+:require 'func-menu
+:group 'menus
+:enable #'(lambda ()
+ (add-hook 'find-file-hooks 'fume-add-menubar-entry)
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (setq fume-display-in-modeline-p t)
+ (fume-add-menubar-entry)))
+ (buffer-list)))
+:disable #'(lambda ()
+ (remove-hook 'find-file-hooks 'fume-add-menubar-entry)
+ (fset 'widen (symbol-function 'fume-widen))
+ (fset 'narrow-to-region (symbol-function 'narrow-to-region))
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (fume-remove-menubar-entry)
+ (setq fume-display-in-modeline-p nil)
+ (fume-remove-post-command-hook
+ 'fume-tickle-modeline)
+ (fume-remove-post-command-hook
+ 'fume-maybe-install-modeline-feature)
+ (fume-remove-post-command-hook
+ 'fume-rescan-buffer-trigger)))
+ (buffer-list))))
+
+)
+
(provide 'func-menu)
;;; func-menu.el ends here
Index: xemacs-packages/edit-utils/hippie-exp.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/hippie-exp.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 hippie-exp.el
--- xemacs-packages/edit-utils/hippie-exp.el 1998/01/14 06:36:15 1.1.1.1
+++ xemacs-packages/edit-utils/hippie-exp.el 2005/01/31 20:55:46
＠＠ -1124,6 +1124,138 ＠＠ string). It returns t if a new completi
(point)))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'hippie-expand
+"`hippie-expand' is a single function for a lot of different kinds
+of completions and expansions. Called repeatedly it tries all
+possible completions in succession.
+Which kinds of completions to try, and in which order, is
+determined by the contents of `hippie-expand-try-functions-list'.
+Much customization of `hippie-expand' can be made by changing the
+order of, removing, or inserting new functions in this list.
+Given a positive numeric argument, `hippie-expand' jumps directly
+ARG functions forward in this list. Given some other argument
+\(a negative argument or just Ctrl-U) it undoes the tried
+completion.
+
+If the variable `hippie-expand-verbose' is non-nil, `hippie-expand'
+outputs in a message which try-function in the list that is used
+currently (ie. was used currently and will be tried first the next
+time).
+The variable `hippie-expand-max-buffers' determines in how many
+buffers, apart from the current, to search for expansions in. It
+is used by the try-functions named \"-all-buffers\".
+The variable `hippie-expand-ignore-buffers' is a list of regexps
+matching buffer names (as strings) or major modes (as atoms) of
+buffers that should not be searched by the try-functions named
+\"-all-buffers\".
+See also the macro `make-hippie-expand-function' below.
+
+A short description of the current try-functions in this file:
+ `try-complete-file-name' : very convenient to have in any buffer,
+ and not just in the minibuffer or (some) shell-mode. It goes
+ through all possible completions instead of just completing as
+ much as is unique.
+ `try-complete-file-name-partially' : To insert in the list just
+ before `try-complete-file-name' for those who want first to get
+ a file name completed only as many characters as is unique.
+ `try-expand-all-abbrevs' : can be removed if you don't use abbrevs.
+ Otherwise it looks through all abbrev-tables, starting with
+ the local followed by the global.
+ `try-expand-line' : Searches the buffer for an entire line that
+ begins exactly as the current line. Convenient sometimes, for
+ example as a substitute for (or complement to) the history
+ list in shell-like buffers. At other times, only confusing.
+ `try-expand-line-all-buffers' : Like `try-expand-line' but searches
+ in all buffers (except the current). (This may be a little
+ slow, don't use it unless you are really fond of `hippie-expand'.)
+ `try-expand-list' : Tries to expand the text back to the nearest
+ open delimiter, to a whole list from the buffer. Convenient for
+ example when writing lisp or TeX.
+ `try-expand-list-all-buffers' : Like `try-expand-list' but searches
+ in all buffers (except the current).
+ `try-expand-dabbrev' : works exactly as dabbrev-expand (but of
+ course in a way compatible with the other try-functions).
+ `try-expand-dabbrev-all-buffers' : perhaps the most useful of them,
+ like `dabbrev-expand' but searches all Emacs buffers (except the
+ current) for matching words. (No, I don't find this one
+ particularly slow.)
+ `try-expand-dabbrev-visible': Searches the currently visible parts of
+ all windows. Can be put before `try-expand-dabbrev-all-buffers' to
+ first try the expansions you can see.
+ `try-expand-dabbrev-from-kill': Searches the kill ring for a suitable
+ completion of the word. Good to have, just in case the word was not
+ found elsewhere.
+ `try-expand-whole-kill' : Tries to complete text with a whole entry
+ from the kill ring. May be good if you don't know how far up in
+ the kill-ring the required entry is, and don't want to mess with
+ \"Choose Next Paste\".
+ `try-complete-lisp-symbol' : like `lisp-complete-symbol', but goes
+ through all possibilities instead of completing what is unique.
+ Might be tedious (usually a lot of possible completions) and
+ since its function is much like `lisp-complete-symbol', which
+ already has a key of its own, you might want to remove this.
+ `try-complete-lisp-symbol-partially' : To insert in the list just
+ before `try-complete-lisp-symbol' for those who first want to get
+ completion of what is unique in the name.
+
+Not all of the above functions are by default in
+`hippie-expand-try-functions-list'. This variable is better set
+in \".emacs\" to make `hippie-expand' behave maximally convenient
+according to personal taste. Also, instead of loading the
+variable with all kinds of try-functions above, it might be an
+idea to use `make-hippie-expand-function' to construct different
+`hippie-expand'-like functions, with different try-lists and bound
+to different keys. It is also possible to make
+`hippie-expand-try-functions-list' a buffer local variable, and
+let it depend on the mode (by setting it in the mode-hooks).
+
+To write new try-functions, consider the following:
+Each try-function takes one argument OLD which is nil the first
+time the function is called and true in succeeding calls for the
+same string to complete. The first time the function has to
+extract the string before point to complete, and substitute the
+first completion alternative for it. On following calls it has to
+substitute the next possible completion for the last tried string.
+The try-function is to return t as long as it finds new
+possible completions. When there are no more alternatives it has
+to restore the text before point to its original contents, and
+return nil (don't beep or message or anything).
+The try-function can (should) use the following functions:
+ `he-init-string' : Initializes the text to substitute to the
+ contents of the region BEGIN to END. Also sets the variable
+ `he-search-string' to the text to expand.
+ `he-substitute-string' : substitutes STR into the region
+ initialized with `he-init-string'. (An optional second argument
+ TRANS-CASE non-nil, means transfer of case from the abbreviation
+ to the expansion is ok if that is enabled in the buffer.)
+ `he-reset-string' : Resets the initialized region to its original
+ contents.
+There is also a variable: `he-tried-table' which is meant to contain
+all tried expansions so far. The try-function can check this
+variable to see whether an expansion has already been tried
+(hint: `he-string-member').
+
+Known bugs
+
+It may happen that some completion suggestion occurs twice, in
+spite of the use of `he-tried-table' to prevent that. This is
+because different try-functions may try to complete different
+lengths of text, and thus put different amounts of the
+text in `he-tried-table'. Anyway this seems to occur seldom enough
+not to be too disturbing. Also it should NOT be possible for the
+opposite situation to occur, that `hippie-expand' misses some
+suggestion because it thinks it has already tried it."
+:short-doc "expand text trying various ways to find its expansion"
+:group 'editing
+:commands '(["Hippie-expand text at point" hippie-expand])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
(provide 'hippie-exp)
;;; hippie-exp.el ends here
Index: xemacs-packages/edit-utils/id-select.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/id-select.el,v
retrieving revision 1.5
diff -u -p -r1.5 id-select.el
--- xemacs-packages/edit-utils/id-select.el 2001/04/21 23:25:47 1.5
+++ xemacs-packages/edit-utils/id-select.el 2005/01/31 20:55:46
＠＠ -1285,6 +1285,75 ＠＠ Ordering of entries is largely irrelevan
:type '(repeat (list (sexp :tag "Syntax-Char" function)))
:group 'id-select)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'id-select
+"This is a radically cool, drop in mouse and keyboard-based library for
+selecting successively bigger syntactical regions within a buffer.
+Simply load this library and you are ready to try it out by
+double-clicking on various kinds of characters in different buffer major
+modes. You'll quickly get the hang of it. (It also provides a command
+to jump between beginning and end tags within HTML and SGML buffers.)
+
+A great deal of smarts are built-in so that it does the right thing
+almost all of the time; many other attempts at similar behavior such as
+thing.el fail to deal with many file format complexities.
+
+Double clicks of the Selection Key (left mouse key) at the same point
+will select bigger and bigger regions with each successive use. The
+first double click selects a region based upon the character at the
+point of the click. For example, with the point over an opening or
+closing grouping character, such as { or }, the whole grouping is
+selected, e.g. a C function. When on an _ or - within a programming
+language variable name, the whole name is selected. The type of
+selection is displayed in the minibuffer as feedback. When using a
+language based mainly on indenting, like Bourne shell, a double click on
+the first alpha character of a line, such as an if statement, selects
+the whole statement.
+
+---------------
+
+This whole package is driven by a single function, available in mouse
+and keyboard forms, that first marks a region based on the syntax
+category of the character following point. Successive invocations mark
+larger and larger regions until the whole buffer is marked. See the
+documentation for the function, id-select-syntactical-region, for the
+kinds of syntax categories handled.
+
+Loading this package automatically installs its functionalty on
+double-clicks (or higher) of the left mouse key. (See the documentation
+for the variable, mouse-track-click-hook, for how this is done.) A
+single click of the left button will remove the region and reset point.
+
+The function, id-select-thing, may be bound to a key to provide the same
+syntax-driven region selection functionality. {C-c C-m} is a
+reasonable site-wide choice since this key is seldom used and it
+mnemonically indicates marking something. {C-c s} may be preferred as a
+personal binding.
+
+Use {C-g} to unmark the region when done. Use,
+id-select-thing-with-mouse, if you want to bind this to a mouse key and
+thereby use single clicks instead of double clicks.
+
+Three other commands are also provided:
+ id-select-and-copy-thing - mark and copy the syntactical unit to the
+ kill ring
+ id-select-and-kill-thing - kill the syntactical unit at point
+ id-select-goto-matching-tag - In HTML and SGML modes (actually any
+ listed in the variable, `id-select-markup-modes'), moves point to the
+ start of the tag paired with the closest tag that point is within or
+ which it precedes, so you can quickly jump back and forth between
+ open and close tags.
+"
+:short-doc "Syntactic region selection"
+:group 'editing
+:enable #'(lambda ()
+ (add-hook 'mouse-track-click-hook 'id-select-double-click-hook))
+:disable #'(lambda ()
+ (remove-hook 'mouse-track-click-hook 'id-select-double-click-hook))
+ )
+)
(provide 'id-select)
Index: xemacs-packages/edit-utils/iswitchb.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/iswitchb.el,v
retrieving revision 1.3
diff -u -p -r1.3 iswitchb.el
--- xemacs-packages/edit-utils/iswitchb.el 2001/07/20 14:09:12 1.3
+++ xemacs-packages/edit-utils/iswitchb.el 2005/01/31 20:55:47
＠＠ -1352,6 +1352,166 ＠＠ This is an example function which can be
;;; HOOKS
(add-hook 'minibuffer-setup-hook 'iswitchb-minibuffer-setup)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'iswitchb
+"As you type in a substring, the list of buffers currently matching
+the substring are displayed as you type. The list is ordered so
+that the most recent buffers visited come at the start of the list.
+The buffer at the start of the list will be the one visited when
+you press return. By typing more of the substring, the list is
+narrowed down so that gradually the buffer you want will be at the
+top of the list. Alternatively, you can use C-s an C-r to rotate
+buffer names in the list until the one you want is at the top of
+the list. Completion is also available so that you can see what is
+common to all of the matching buffers as you type.
+
+This code is similar to a couple of other packages. Michael R Cook
+<mcook(a)cognex.com> wrote a similar buffer switching package, but
+does exact matching rather than substring matching on buffer names.
+I also modified a couple of functions from icomplete.el to provide
+the completion feedback in the minibuffer.
+
+; Example
+
+If I have two buffers called \"123456\" and \"123\", with \"123456\" the
+most recent, when I use iswitchb, I first of all get presented with
+the list of all the buffers
+
+ iswitch {123456,123}
+
+ If I then press 2:
+ iswitch 2[3]{123456,123}
+
+ The list in {} are the matching buffers, most recent first (buffers
+ visible in the current frame are put at the end of the list by
+ default). At any time I can select the item at the head of the
+ list by pressing RET. I can also bring the put the first element
+ at the end of the list by pressing C-s, or put the last element at
+ the head of the list by pressing C-r. The item in [] indicates
+ what can be added to my input by pressing TAB. In this case, I
+ will get \"3\" added to my input. So, press TAB:
+ iswitch 23{123456,123}
+
+ At this point, I still have two matching buffers.
+ If I want the first buffer in the list, I simply press RET. If I
+ wanted the second in the list, I could press C-s to move it to the
+ top of the list and then RET to select it.
+
+However, If I type 4, I only have one match left:
+ iswitch 234[123456] [Matched]
+
+Since there is only one matching buffer left, it is given in [] and we
+see the text [Matched] afterwards. I can now press TAB or RET to go
+to that buffer.
+
+ If however, I now type \"a\":
+ iswitch 234a [No match]
+ There are no matching buffers. If I press RET or TAB, I can be
+ prompted to create a new buffer called \"234a\".
+
+ Of course, where this function comes in really useful is when you
+ can specify the buffer using only a few keystrokes. In the above
+ example, the quickest way to get to the \"123456\" buffer would be
+ just to type 4 and then RET (assuming there isn't any newer buffer
+ with 4 in its name).
+
+ To see a full list of all matching buffers in a separate buffer,
+ hit ? or press TAB when there are no further completions to the
+ substring. Repeated TAB presses will scroll you through this
+ separate buffer.
+
+ The buffer at the head of the list can be killed by pressing C-k.
+ If the buffer needs saving, you will be queried before the buffer
+ is killed.
+
+ If you find that the file you are after is not in a buffer, you can
+ press C-x C-f to immediately drop into find-file.
+
+
+ See the doc string of iswitchb for full keybindings and features.
+ (describe-function 'iswitchb)
+
+; Customisation
+
+ See the User Variables section below for easy ways to change the
+ functionality of the program. These are accessible using the
+ custom package.
+ To modify the keybindings, use the hook provided. For example:
+\(add-hook 'iswitchb-define-mode-map-hook
+ 'iswitchb-my-keys)
+
+\(defun iswitchb-my-keys ()
+ \"Add my keybindings for iswitchb.\"
+ (define-key iswitchb-mode-map \" \" 'iswitchb-next-match)
+ )
+
+ Seeing all the matching buffers
+
+ If you have many matching buffers, they may not all fit onto one
+ line of the minibuffer. In this case, you should use rsz-mini
+ (resize-minibuffer-mode). You can also limit iswitchb so that it
+ only shows a certain number of lines -- see the documentation for
+ `iswitchb-minibuffer-setup-hook'.
+
+
+ Changing the list of buffers
+
+ By default, the list of current buffers is most recent first,
+ oldest last, with the exception that the buffers visible in the
+ current frame are put at the end of the list. A hook exists to
+ allow other functions to order the list. For example, if you add:
+
+ (add-hook 'iswitchb-make-buflist-hook 'iswitchb-summaries-to-end)
+
+ then all buffers matching \"Summary\" are moved to the end of the
+ list. (I find this handy for keeping the INBOX Summary and so on
+ out of the way.) It also moves buffers matching \"output\*$\" to the
+ end of the list (these are created by AUC TeX when compiling.)
+ Other functions could be made available which alter the list of
+ matching buffers (either deleting or rearranging elements.)
+
+ Font-Lock
+
+ If you have font-lock loaded, the first matching buffer is
+ highlighted. To switch this off, set (setq iswitchb-use-fonts nil)
+ I don't use font-lock that much, so I've hardcoded the faces. If
+ this is too harsh, let me know. Colouring of the matching buffer
+ name was suggested by Carsten Dominik (dominik(a)strw.leidenuniv.nl)
+
+
+ Replacement for read-buffer
+
+ iswitchb-read-buffer has been written to be a drop in replacement
+ for the normal buffer selection routine `read-buffer'. To use
+ iswitch for all buffer selections in Emacs, add:
+ (setq read-buffer-function 'iswitchb-read-buffer)
+ (This variable should be present in Emacs 20.3+)
+ XEmacs users can get the same behaviour by doing:
+ (defalias 'read-buffer 'iswitchb-read-buffer)
+ since `read-buffer' is defined in lisp.
+
+ Regexp matching
+
+ There is limited provision for regexp matching within iswitchb,
+ enabled through `iswitchb-regexp'. This allows you to type `c$'
+ for example and see all buffer names ending in `c'. This facility
+ is quite limited though in two respects. First, you can't
+ currently type in expressions like `[0-9]' directly -- you have to
+ type them in when iswitchb-regexp is nil and then toggle on the
+ regexp functionality. Likewise, don't enter an expression
+ containing `\' in regexp mode. If you try, iswitchb gets confused,
+ so just hit C-g and try again. Secondly, no completion mechanism
+ is currently offered when regexp searching."
+:short-doc "Dynamic buffer switching"
+:group 'keyboard
+:enable #'(lambda ()
+ (iswitchb-default-keybindings))
+ ;; No :disable
+ )
+)
+
(provide 'iswitchb)
;;; iswitchb.el ends here
Index: xemacs-packages/edit-utils/lazy-lock.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/lazy-lock.el,v
retrieving revision 1.11
diff -u -p -r1.11 lazy-lock.el
--- xemacs-packages/edit-utils/lazy-lock.el 2004/11/08 02:38:42 1.11
+++ xemacs-packages/edit-utils/lazy-lock.el 2005/01/31 20:55:47
＠＠ -1070,6 +1070,76 ＠＠ will take place when text is fontified s
;;;###autoload
(add-minor-mode 'lazy-lock-mode 'lazy-lock-mode-line-string)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'lazy-lock
+
+"Make visiting buffers in `font-lock-mode' faster by making fontification
+be demand-driven and stealthy. Fontification only occurs when, and where,
+necessary. You can now use the so-called \"gaudier\" fontification regexps
+on big files without frustration.
+
+In a buffer (which has `font-lock-mode' enabled) which is at least
+`lazy-lock-minimum-size' characters long, only the visible portion of the
+buffer will be fontified. Motion around the buffer will fontify those
+visible portions that were not previous fontified.
+
+If stealth fontification is enabled, fontification will occur in invisible
+parts of the buffer after `lazy-lock-stealth-time' seconds of idle time.
+Caveats:
+
+Lazy Lock mode does not work efficiently with Outline mode. This is because
+when in Outline mode, although text may be hidden (not visible in the
+window), the text is visible to Emacs Lisp code (not surprisingly) and Lazy
+Lock fontifies it mercilessly. Hopefully this will be fixed one day.
+
+When Lazy Lock mode is enabled, fontification can be lazy in a number of ways:
+
+- Demand-driven buffer fontification if `lazy-lock-minimum-size' is non-nil.
+ This means initial fontification does not occur if the buffer is greater than
+ `lazy-lock-minimum-size' characters in length. Instead, fontification occurs
+ when necessary, such as when scrolling through the buffer would otherwise
+ reveal unfontified areas. This is useful if buffer fontification is too slow
+ for large buffers.
+
+- Deferred on-the-fly fontification if `lazy-lock-defer-on-the-fly' is non-nil.
+ This means on-the-fly fontification does not occur as you type. Instead,
+ fontification is deferred until after `lazy-lock-defer-time' seconds of Emacs
+ idle time, while Emacs remains idle. This is useful if fontification is too
+ slow to keep up with your typing.
+
+- Deferred context fontification if `lazy-lock-defer-contextually' is non-nil.
+ This means fontification updates the buffer corresponding to true syntactic
+ context, after `lazy-lock-defer-time' seconds of Emacs idle time, while Emacs
+ remains idle. Otherwise, fontification occurs on modified lines only, and
+ subsequent lines can remain fontified corresponding to previous syntactic
+ contexts. This is useful where strings or comments span lines.
+
+- Stealthy buffer fontification if `lazy-lock-stealth-time' is non-nil.
+ This means remaining unfontified areas of buffers are fontified if Emacs has
+ been idle for `lazy-lock-stealth-time' seconds, while Emacs remains idle.
+ This is useful if any buffer has any deferred fontification.
+
+Basic Font Lock mode on-the-fly fontification behaviour fontifies modified
+lines only. Thus, if `lazy-lock-defer-contextually' is non-nil, Lazy Lock mode
+on-the-fly fontification may fontify differently, albeit correctly. In any
+event, to refontify some lines you can use \\[font-lock-fontify-block].
+
+Stealth fontification only occurs while the system remains unloaded.
+If the system load rises above `lazy-lock-stealth-load' percent, stealth
+fontification is suspended. Stealth fontification intensity is controlled via
+the variable `lazy-lock-stealth-nice' and `lazy-lock-stealth-lines', and
+verbosity is controlled via the variable `lazy-lock-stealth-verbose'."
+:short-doc "Lazy demand-driven fontification for fast Font Lock mode"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock))
+:disable #'(lambda ()
+ (remove-hook 'font-lock-mode-hook 'turn-on-lazy-lock))
+ )
+)
+
;; Provide ourselves:
(provide 'lazy-lock)
Index: xemacs-packages/edit-utils/lazy-shot.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/lazy-shot.el,v
retrieving revision 1.6
diff -u -p -r1.6 lazy-shot.el
--- xemacs-packages/edit-utils/lazy-shot.el 2002/11/28 18:55:08 1.6
+++ xemacs-packages/edit-utils/lazy-shot.el 2005/01/31 20:55:47
＠＠ -321,6 +321,30 ＠＠ stealth locking functions."
(if font-lock-mode
(add-hook 'after-change-functions 'font-lock-after-change-function
nil t)))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'lazy-shot
+"This is an experimental demand based font-lock implemenation. It
+is almost equal in functionality and interface to lazy-lock 2.09
+Does somebody really need defer-locking?
+
+It is exprimental in the sense that it relies on C support from
+the redisplay engine, that is experimental. The code in this file
+is more or less finished. The C code support experimental because
+the current design is rumoured to be ugly. Secondly because
+XEmacs does actually display the \"un-font-locked\" parts of the
+buffer first, the user notices flashing as the buffer is repainted
+with color/fonts."
+:short-doc "Lazy font locking for XEmacs"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'font-lock-mode-hook 'turn-on-lazy-shot))
+:disable #'(lambda ()
+ (remove-hook 'font-lock-mode-hook 'turn-on-lazy-shot))
+ )
+)
(provide 'lazy-shot)
Index: xemacs-packages/edit-utils/live-icon.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/live-icon.el,v
retrieving revision 1.2
diff -u -p -r1.2 live-icon.el
--- xemacs-packages/edit-utils/live-icon.el 1999/11/27 20:49:59 1.2
+++ xemacs-packages/edit-utils/live-icon.el 2005/01/31 20:55:47
＠＠ -139,8 +139,23 ＠＠
;; fr))
;; (frame-list)))
-(add-hook 'unmap-frame-hook 'live-icon-one-frame)
;;(start-itimer "live-icon" 'live-icon-all-frames 120 120)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'live-icon
+"Make frame icons represent the current frame contents.
+Generates little pixmaps representing the contents of your frames."
+:short-doc "make frame icons represent the current frame contents"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'unmap-frame-hook 'live-icon-one-frame))
+:disable #'(lambda ()
+ (remove-hook 'unmap-frame-hook 'live-icon-one-frame))
+ )
+)
+
(provide 'live-icon)
;;; live-icon.el ends here
Index: xemacs-packages/edit-utils/page-ext.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/page-ext.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 page-ext.el
--- xemacs-packages/edit-utils/page-ext.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/page-ext.el 2005/01/31 20:55:48
＠＠ -785,6 +785,225 ＠＠ to the same line in the pages buffer."
(make-local-variable 'pages-pos-list)
(make-local-variable 'pages-directory-buffer-narrowing-p))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'page-ext
+"You may use these commands to handle an address list or other
+small data base.
+
+ Summary
+
+The current page commands are:
+
+ forward-page C-x ]
+ backward-page C-x [
+ narrow-to-page C-x p
+ count-lines-page C-x l
+ mark-page C-x C-p (change this to C-x C-p C-m)
+ sort-pages not bound
+ what-page not bound
+
+The new page handling commands all use `C-x C-p' as a prefix. This
+means that the key binding for `mark-page' must be changed.
+Otherwise, no other changes are made to the current commands or
+their bindings.
+
+New page handling commands:
+
+ next-page C-x C-p C-n
+ previous-page C-x C-p C-p
+ search-pages C-x C-p C-s
+ add-new-page C-x C-p C-a
+ sort-pages-buffer C-x C-p s
+ set-page-delimiter C-x C-p C-l
+ pages-directory C-x C-p C-d
+ pages-directory-for-addresses C-x C-p d
+ pages-directory-goto C-c C-c
+
+
+ Using the page commands
+
+The page commands are helpful in several different contexts. For
+example, programmers often divide source files into sections using the
+`page-delimiter'; you can use the `pages-directory' command to list
+the sections.
+
+You may change the buffer local value of the `page-delimiter' with
+the `set-page-delimiter' command. This command is bound to `C-x C-p
+C-l' The command prompts you for a new value for the page-delimiter.
+Called with a prefix-arg, the command resets the value of the
+page-delimiter to its original value.
+
+You may set several user options:
+
+ The `pages-directory-buffer-narrowing-p' variable causes the
+ `pages-directory-goto' command to narrow to the destination page.
+
+ The `pages-directory-for-adding-page-narrowing-p' variable, causes the
+ `add-new-page' command to narrow to the new entry.
+
+ The `pages-directory-for-adding-new-page-before-current-page-p' variable
+ causes the `add-new-page' command to insert a new page before current
+ page.
+
+These variables are true by default.
+
+Additional, addresses-related user options are described in the next page
+of this file.
+
+
+ Handling an address list or small data base
+
+You may use the page commands to handle an address list or other
+small data base. Put each address or entry on its own page. The
+first line of text in each page is a `header line' and is listed by
+the `pages-directory' or `pages-directory-for-addresses' command.
+
+Specifically:
+
+ 1. Begin each entry with a `page-delimiter' (which is, by default,
+ `^L' at the beginning of the line).
+
+ 2. The first line of text in each entry is the `heading line'; it
+ will appear in the pages-directory-buffer which is constructed
+ using the `C-x C-p C-d' (pages-directory) command or the `C-x
+ C-p d' (pages-directory-for-addresses) command.
+
+ The heading line may be on the same line as the page-delimiter
+ or it may follow after. It is the first non-blank line on the
+ page. Conventionally, the heading line is placed on the line
+ immediately following the line containing page-delimiter.
+
+ 3. Follow the heading line with the body of the entry. The body
+ extends up to the next `page-delimiter'. The body may be of any
+ length. It is conventional to place a blank line after the last
+ line of the body.
+
+For example, a file might look like this:
+
+ FSF
+ Free Software Foundation
+ 59 Temple Place - Suite 330
+ Boston, MA 02111-1307 USA.
+ (617) 542-5942
+ gnu(a)gnu.org
+
+
+ House Subcommittee on Intellectual Property,
+ U.S. House of Representatives,
+ Washington, DC 20515
+
+ Congressional committee concerned with permitting or preventing
+ monopolistic restrictions on the use of software technology.
+
+
+ George Lakoff
+ ``Women, Fire, and Dangerous Things:
+ What Categories Reveal about the Mind''
+ 1987, Univ. of Chicago Press
+
+ About philosophy, Whorfian effects, and linguistics.
+
+
+ OBI (On line text collection.)
+ Open Book Initiative
+ c/o Software Tool & Die
+ 1330 Beacon St, Brookline, MA 02146 USA
+ (617) 739-0202
+ obi(a)world.std.com
+
+In this example, the heading lines are:
+
+ FSF
+ House Subcommittee on Intellectual Property
+ George Lakoff
+ OBI (On line text collection.)
+
+The `C-x C-p s' (sort-pages-buffer) command sorts the entries in the
+buffer alphabetically.
+
+You may use any of the page commands, including the `next-page',
+`previous-page', `add-new-page', `mark-page', and `search-pages'
+commands.
+
+You may use either the `C-x C-p d' (pages-directory-for-addresses)
+or the `C-x C-p C-d' (pages-directory) command to construct and
+display a directory of all the heading lines.
+
+In the directory, you may position the cursor over a heading line
+and type `C-c C-c' (pages-directory-goto) to go to the entry to
+which it refers in the pages buffer.
+
+You can type `C-c C-p C-a' (add-new-page) to add a new entry in the
+pages buffer or address file. This is the same command you use to
+add a new entry when you are in the pages buffer or address file.
+
+If you wish, you may create several different directories,
+one for each different buffer.
+
+`pages-directory-for-addresses' in detail
+
+The `pages-directory-for-addresses' assumes a default addresses
+file. You do not need to specify the addresses file but merely type
+`C-x C-p d' from any buffer. The command finds the file, constructs
+a directory for it, and switches you to the directory. If you call
+the command with a prefix arg, `C-u C-x C-p d', it prompts you for a
+file name.
+
+You may customize the addresses commands:
+
+ The `pages-addresses-file-name' variable determines the name of
+ the addresses file; by default it is \"~/addresses\".
+
+ The `pages-directory-for-addresses-goto-narrowing-p' variable
+ determines whether `pages-directory-goto' narrows the addresses
+ buffer to the entry, which it does by default.
+
+ The `pages-directory-for-addresses-buffer-keep-windows-p' variable
+ determines whether `pages-directory-for-addresses' deletes other
+ windows to show as many lines as possible on the screen or works
+ in the usual Emacs manner and keeps other windows. Default is to
+ keep other windows.
+
+ The `pages-directory-for-adding-addresses-narrowing-p' variable
+ determines whether `pages-directory-for-addresses' narrows the
+ addresses buffer to a new entry when you are adding that entry.
+ Default is to narrow to new entry, which means you see a blank
+ screen before you write the new entry.
+
+`pages-directory' in detail
+
+Call the `pages-directory' command from the buffer for which you
+want a directory created; it creates a directory for the buffer and
+pops you to the directory.
+
+The `pages-directory' command has several options:
+
+ Called with a prefix arg, `C-u C-x C-p C-d', the `pages-directory'
+ prompts you for a regular expression and only lists only those
+ header lines that are part of pages that contain matches to the
+ regexp. In the example above, `C-u C-x C-p C-d 617 RET' would
+ match the telephone area code of the first and fourth entries, so
+ only the header lines of those two entries would appear in the
+ pages-directory-buffer.
+
+ Called with a numeric argument, the `pages-directory' command
+ lists the number of lines in each page. This is helpful when you
+ are printing hardcopy.
+
+ Called with a negative numeric argument, the `pages-directory'
+ command lists the lengths of pages whose contents match a regexp.
+"
+:short-doc "Extended page handling commands"
+:require 'page-ext
+:custom-group 'pages
+:group 'editing
+:enable #'ignore
+ ;; No :disable
+ )
+)
+
;;; Place `provide' at end of file.
(provide 'page-ext)
Index: xemacs-packages/edit-utils/paren.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/paren.el,v
retrieving revision 1.3
diff -u -p -r1.3 paren.el
--- xemacs-packages/edit-utils/paren.el 1998/10/10 13:59:43 1.3
+++ xemacs-packages/edit-utils/paren.el 2005/01/31 20:55:48
＠＠ -391,6 +391,50 ＠＠ See also `paren-mode' and `paren-highlig
(paren-set-mode (if (and (numberp arg) (> arg 0))
'blink-paren -1) t))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'paren
+"Purpose of this package:
+
+ This package highlights matching parens (or whole sexps) for easier
+ editing of source code, particularly lisp source code.
+
+The `paren-highlight' hook function runs after each command and
+checks to see if the cursor is at a parenthesis. If so, then it
+highlights, in one of several ways, the matching parenthesis.
+
+Priority is given to matching parentheses right before the cursor because
+that's what makes sense when you're typing a lot of closed parentheses.
+
+This is especially intuitive if you frequently use forward-sexp (M-C-f)
+and backward-sexp (M-C-b) to maneuver around in source code.
+
+Different faces are used for matching and mismatching parens so that it
+is easier to see mistakes as you type them. Audible feedback is optional.
+
+If a (mis)matching paren is offscreen, then a message is sent to the modeline.
+
+If paren-mode is `sexp', entire S-expressions are highlighted instead of
+just matching parens.
+"
+:short-doc "Highlight (un)matching parens and whole expressions"
+:custom-group 'paren-matching
+:group 'display
+:enable #'(lambda ()
+ (paren-set-mode (if (and (boundp 'highlight-paren-expression)
+ ;; bletcherous blink-paren no-naming-convention
+ highlight-paren-expression)
+ 'sexp
+ (if (device-on-window-system-p)
+ 'blink-paren
+ 'paren))
+ t))
+:disable #'(lambda ()
+ (paren-set-mode -1 t))
+ )
+)
+
(provide 'blink-paren)
(provide 'paren)
Index: xemacs-packages/edit-utils/permanent-buffers.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/permanent-buffers.el,v
retrieving revision 1.3
diff -u -p -r1.3 permanent-buffers.el
--- xemacs-packages/edit-utils/permanent-buffers.el 2000/10/06 09:08:01 1.3
+++ xemacs-packages/edit-utils/permanent-buffers.el 2005/01/31 20:55:48
＠＠ -223,6 +223,30 ＠＠ regenerated fresh and empty. See also th
(interactive)
(message "permanent-buffers version %s" permanent-buffers-version))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'permanent-buffers
+"A permanent buffer is a buffer that you don't want to kill, mainly used for
+testing or temporary stuff. The *scratch* buffer is the most famous example
+of what could be a permanent buffer. This package allows you to define
+several permanent buffers (the scratch buffer can be one of them) that
+will never disapear. If you kill them or save their contents, they will be
+regenerated. You can also specify a set of lisp forms to eval in the buffer
+when it is (re)generated.
+
+The package is implemented in a minor-mode fashion. You can customize the
+default value of `permanent-buffers-mode' or use
+`turn-on-permanent-buffers' at startup. Within an XEmacs session, use
+`permanent-buffers-mode' or `tun-o[n|ff]-oermanent-buffers'. You might also
+want to customize `permanent-buffers-alist'."
+:short-doc "Permanent buffers management package"
+:group 'buffers-and-windows
+:enable #'turn-on-permanent-buffers
+:disable #'turn-off-permanent-buffers
+ )
+)
+
(provide 'permanent-buffers)
;;; permanent-buffers.el ends here
Index: xemacs-packages/edit-utils/popper.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/popper.el,v
retrieving revision 1.3
diff -u -p -r1.3 popper.el
--- xemacs-packages/edit-utils/popper.el 1998/10/02 06:10:33 1.3
+++ xemacs-packages/edit-utils/popper.el 2005/01/31 20:55:49
＠＠ -1807,6 +1807,213 ＠＠ window is deleted, the display jump is a
(popper-install))
+;; XEmacs:
+
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'popper
+"\
+1. VERSION:
+
+This version of popper is based on version 2.40, which as far as I can
+tell is the last version distributed by Chris McConnell, the original
+author of popper. I have been unsuccessful at contacting him and so
+have decided to take over maintenance of the package for XEmacs. New
+versions distributed by me will be designated \"2.40 XEmacs X.Y\". This
+designation is not meant to imply that this is an XEmacs-specific
+version, only that it is the version distributed with XEmacs. This
+version incorporates significant bug fixes and changes with respect to
+the original. Overall it should work much better. Please let me know
+if you have any problems or suggestions.
+
+2. DESCRIPTION:
+
+This module provides a single shrink-wrapped window for displaying
+temporary text called the popper window. At any time there is at
+most one popper window on a given emacs frame. If there is an entry
+for the buffer being displayed on popper-min-heights, the size of
+the window will be from that entry. If the buffer is empty, the
+size of the window will be popper-empty-min. Otherwise its size
+will be the minimum of the number of lines of text being displayed
+and half the number of lines in the currently selected window when
+the popper window was created. It will work with any function that
+uses temporary windows or that has been wrapped with popper-wrap.
+The window can be scrolled or buried from any other window.
+
+When a buffer is displayed using the function
+with-output-to-temp-buffer, the text will be displayed in the
+popper window if the name of the buffer is in popper-pop-buffers
+or popper-pop-buffers is set to `t' and the name is not in
+popper-no-pop-buffers. If you have a buffer with a process, you
+can cause it to automatically scroll by setting
+popper-scroll-buffers to `t' or to a list of buffer names to
+scroll. Many kinds of completion and help information are
+displayed this way. In general any buffer with *'s around its
+name will be a temporary buffer. Some commands like shell-command
+do not use with-output-to-temp-buffer even though you might like
+to have their output be temporary. For commands like this, you
+can define a wrapper using the function popper-wrap.
+
+If popper-use-message-buffer is non-nil then popper output that is
+one line or less will be displayed in the minibuffer.
+
+The default binding for C-x o is changed so that when a buffer is
+displayed in a popper window, it will be skipped if it is in
+popper-buffers-to-skip or popper-buffers-to-skip is `t' and it is
+not in popper-buffers-no-skip.
+
+3. USAGE:
+
+Load this file, preferably after byte-compiling it. By default
+popper does not install itself unless the variable
+`popper-install-when-load' has been set non-nil before it is loaded.
+To manually install popper, type the command M-x popper-install. If
+you later decide popper is not your cup-o-tea, you may un-install it
+using the command M-x popper-unstall.
+
+Once installed, all temporary windows will be handled by popper by
+default. If you do not define custom key bindings using the
+popper-load-hook, the bindings for manipulating the popper temporary
+window will be:
+
+ * C-z C-z, C-z z, C-z 1 : popper-bury-output
+ Alternately hide or show the temporary pop-up window.
+
+ * C-z C-v, C-z v : popper-scroll-output
+ Scroll the popper output window.
+
+ * C-z M-v, C-z V : popper-scroll-output-back
+ Scroll the popper output window backwards.
+
+ * C-z < : popper-beginning-of-buffer
+ Scroll the popper output window to the beginning of the buffer.
+
+ * C-z > : popper-end-of-buffer
+ Scroll the popper output window to the end of the buffer.
+
+ * C-z C-j, C-z j, C-z C-o, C-z o : popper-jump-to-popper
+ Select the popper window, or jump back to the previous window
+ if the popper window is already selected. With a C-u argument,
+ show the popper window first if necessary.
+
+ * C-z C-s : popper-isearch-forward
+ Do incremental search forward in the popper buffer.
+
+ * C-z C-r : popper-isearch-backward
+ Do incremental search backward in the popper buffer.
+
+ * C-z C-M-s : popper-isearch-forward-regexp
+ Do regexp incremental search forward in the popper buffer.
+
+ * C-z C-M-r : popper-isearch-backward-regexp
+ Do regexp incremental search backward in the popper buffer.
+
+ * C-z g : popper-grow-output
+ Grow the popper output window.
+
+ * C-z G, C-z M-g : popper-shrink-output
+ Shrink the popper output window.
+
+ * C-z C-b, C-z b : popper-switch-buffer
+ Prompt for a different popper temporary buffer to show.
+
+ * C-z C-k, C-z k : popper-kill
+ Kill or bury the current popper buffer and drop it off of the
+ stack of popper buffers for this frame. If the stack of popper
+ buffers (for the selected frame) is not empty, show the new
+ top-most buffer. The buffer is killed if it has been saved with
+ `popper-save'; otherwise it is just buried.
+
+ * C-z C-x, C-z x : popper-cycle
+ Cycle through all popper buffers (for the selected frame) by
+ dropping the current popper buffer to bottom of the stack.
+
+ * C-z s : popper-save
+ Save the current popper buffer by renaming it so that it won't be
+ overwritten.
+
+ * C-x o : popper-other-window
+ Like other-window, but (by default) skips the popper window.
+ Use a C-u prefix to select the popper window. See the variables
+ `popper-buffers-to-skip' and `popper-buffers-no-skip'.
+
+ * C-x 0 : popper-delete-window
+ Like delete-window, but hides and re-shows the popper window
+ around the call to delete-window. Also, the variable
+ `popper-delete-window-can-delete-frame' can be set to nil to
+ prevent deletion of the frame if the user attempts to delete the
+ last window.
+
+Note that \"C-z\" is the popper-prefix, and that many bindings in the
+popper map are chosen by analogy to a similar command in the \"C-x\"
+map. If you have suggestions for more intuitive or easily typed
+bindings, or additional user commands that would be nice, please let
+me know.
+
+4. USER CUSTOMIZATION:
+
+See the section `Popper user variables' below for configurable
+variables. Here is a sample load hook for your .emacs:
+
+\(defun gk:popper-load-hook ()
+ (setq popper-install-when-load t) ; Hooray!
+ (setq popper-mode-line-text \" Popper\") ; I know the key bindings
+ (setq popper-no-pop-buffers '(\"^Man: \")) ; don't pop manual buffers
+ (setq popper-max-heights '((\".*\" . (40)))) ; use at most 40%
+ (setq popper-delete-window-can-delete-frame nil) ; extremely losing...
+ )
+\(add-hook 'popper-load-hook 'gk:popper-load-hook)
+\(require 'popper)
+
+Once popper is installed, you may wrap a command that does not use
+`with-output-to-temp-buffer' so that it will work with popper as
+follows:
+
+\(popper-wrap command \"*Command Output*\")
+
+This may not yet work in all cases. It is known not to work for
+M-x compile at this time (See the TODO list below).
+
+When loaded, popper checks the values of certain user variable for
+possible problems, unless `popper-inhibit-warnings' is non-nil. In
+addition, if `popper-fix-incompatible-settings' has been set non-nil,
+popper will set these variables to values known to work best.
+See also the variable `popper-suggested-settings'.
+
+5. WARNINGS:
+
+This package redefines the value of `temp-buffer-show-function'.
+It also advises the functions `split-window' and `pop-to-buffer'
+so that the popper window is buried before calling the old
+definition. The macro `popper-wrap' uses defadvice.
+"
+:short-doc "Shrink-wrapped temporary windows for Emacs"
+:group 'buffers-and-windows
+;;; (defun gk:popper-load-hook ()
+;;; (setq popper-install-when-load t) ; Hooray!
+;;; (setq popper-mode-line-text " Popper") ; I know the key bindings
+;;; (setq popper-no-pop-buffers '("^Man: ")) ; don't pop manual buffers
+;;; (setq popper-max-heights '((".*" . (40)))) ; use at most 40%
+;;; (setq popper-delete-window-can-delete-frame nil) ; extremely losing...
+;;; )
+
+:enable #'(lambda ()
+ (unless (fboundp 'behavior-popper-load-hook)
+ (defun behavior-popper-load-hook ()
+ ;; I know the key bindings
+ (setq popper-mode-line-text " Popper")
+ ;; don't pop manual buffers
+ (setq popper-no-pop-buffers '("^Man: "))
+ ;; use at most 40%
+ (setq popper-max-heights '((".*" . (40))))
+ ;; extremely losing...
+ (setq popper-delete-window-can-delete-frame nil)))
+ (add-hook 'popper-load-hook 'behavior-popper-load-hook)
+ (popper-install))
+:disable #'(lambda ()
+ (popper-unstall))
+ )
+)
;;;
;;; Finally, provide the feature
;;;
Index: xemacs-packages/edit-utils/power-macros.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/power-macros.el,v
retrieving revision 1.1
diff -u -p -r1.1 power-macros.el
--- xemacs-packages/edit-utils/power-macros.el 2000/10/18 17:54:30 1.1
+++ xemacs-packages/edit-utils/power-macros.el 2005/01/31 20:55:49
＠＠ -1926,6 +1926,37 ＠＠ The buffer is created if it doesn't exis
;;}}}
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'power-macros
+"Keyboard Macros are a very powerful tool, if you know how to use them
+the right way! Without this extension it is, however, a bit difficult in
+Emacs to define and maintain several macros at a time. This problem is
+solved with this package.
+
+When you have loaded this package Emacs will, upon completion of
+macro definition, ask you which key you want to assign this macro
+to and ask for a description of the macro.
+If something is already bound to this key, Emacs will ask you
+whether you want to override this binding. Furthermore, this
+package also takes care of saving the macro to your .emacs file
+for later Emacs sessions.
+
+The description for all the defined macros may be obtained with the
+function `pm-manage-macros'. Using this function you can also
+manage you power-macros. You execute this function by pressing `M-x' and
+typing `pm-manage-macros'."
+:short-doc "Easy multiple macro maintenance"
+:group 'editing
+:require 'power-macros
+:enable #'ignore
+ ;; no :disable
+ )
+)
+
+
(provide 'power-macros)
(message "Loading power-macros...done")
Index: xemacs-packages/edit-utils/recent-files.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/recent-files.el,v
retrieving revision 1.9
diff -u -p -r1.9 recent-files.el
--- xemacs-packages/edit-utils/recent-files.el 2004/11/08 02:38:42 1.9
+++ xemacs-packages/edit-utils/recent-files.el 2005/01/31 20:55:49
＠＠ -766,4 +766,162 ＠＠ with a prefix argument, you will be prom
(read-coding-system "Coding system: ")
nil)))
(find-file filename codesys))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'recent-files
+"Recent-files adds the menu \"Recent Files\" (or whatever name you
+choose, see \"Customization:\" below) to Emacs's menubar. Its
+entries are the files (and directories) that have recently been
+opened by Emacs. You can open one of these files again by
+selecting its entry in the \"Recent Files\" menu. The list of file
+entries in this menu is preserved from one Emacs session to
+another. You can prevent Emacs from saving this list by selecting
+\"Don't save recent-files list on exit\" from the menu. If you have
+disabled saving, you can re-enable it by selecting \"Save
+recent-files list on exit\".
+
+The menu has permanent and non-permanent entries. Permanent
+entries are marked with an asterisk in front of the filename. The
+non-permanent entries are hidden in a submenu.
+
+Each time you open a file in Emacs, it is added as a non-permanent
+entry to the menu. The value of `recent-files-number-of-entries'
+determines how many non-permanent entries are held in the
+menu. When the number of non-permanent entries reaches this value,
+the least recently added non-permanent entry is removed from the
+menu when another non-permanent entry is added. It is not removed
+from the list, though; it may reappear when entries are deleted
+from the list. The number of entries saved to disk is the value of
+the variable `recent-files-number-of-saved-entries'.
+
+Permanent entries are not removed from the menu. You can make a
+file entry permanent by selecting \"Make <buffer> permanent\" (where
+<buffer> is the name of the current buffer) when the current
+buffer holds this file. \"Make <buffer> non-permanent\" makes the
+file entry of the current buffer non-permanent.
+
+The command \"Kill buffer <buffer> and delete entry\" is handy when
+you have accidently opened a file but want to keep neither the
+buffer nor the entry.
+
+You can erase the list of non-permanent entries by selecting
+\"Erase non-permanent entries\" from the menu.
+
+Customization:
+
+There are lots of variables to control the behaviour of
+recent-files. You do not have to change any of them if you like it
+as it comes out of the box. However, you may want to look at these
+options to make it behave different.
+
+`recent-files-number-of-entries'
+ Controls how many non-permanent entries are shown in the
+ recent-files list. The default is 15.
+
+`recent-files-number-of-saved-entries'
+ Controls how many non-permanent entries are saved to disk when
+ Emacs exits or recent-files-save-the-list is called. The
+ default is 50.
+
+`recent-files-save-file'
+ The name of the file where the recent-files list is saved
+ between Emacs session. You probably don't need to change this.
+ The default is \".recent-files.el\" in your home directory.
+
+`recent-files-dont-include'
+ A list of regular expressions for files that should not be
+ included into the recent-files list. This list is empty by
+ default. For instance, a list to exclude all .newsrc
+ files, all auto-save-files, and all files in the /tmp
+ directory (but not the /tmp directory itself) would look
+ like this:
+ (setq recent-files-dont-include
+ '(\"/\\.newsrc\" \"~$\" \"^/tmp/.\"))
+ The default is empty.
+
+`recent-files-use-full-names'
+ If the value of this variable is non-nil, the full pathnames of
+ the files are shown in the recent-files menu. Otherwise only
+ the filename part (or the last name component if it is a
+ directory) is shown in the menu. The default it t, i.e. show
+ full names.
+
+`recent-files-filename-replacements'
+ This is a list of pairs of regular expressions and replacement
+ strings. If a filename matches one of the regular expressions,
+ the matching part is replaced by the replacement string for
+ display in the recent-files menu.
+ Example: My home directory is \"/users/mmc/nickel/\". I want to
+ replace it with \"~/\". I also want to replace the directory
+ \"/imports/teleservices/mmc/avc2/\", where I work a lot, with
+ \".../avc2/\". The list then looks like
+ (setq recent-files-filename-replacements
+ '((\"/users/mmc/nickel/\" . \"~/\")
+ (\"/imports/teleservices/mmc/avc2/\" . \".../avc2/\")))
+ Only the first match is replaced. So, if you have several
+ entries in this list that may match a filename simultaneously,
+ put the one you want to match (usually the most special) in
+ front of the others. The default is to replace the home
+ directory with \"~\".
+
+`recent-files-sort-function'
+ Contains a function symbol to sort the display of filenames in
+ the recent-files menu. Supplied are two functions,
+ 'recent-files-dont-sort and 'recent-files-sort-alphabetically.
+ The first, which is the default, preserves the order of \"most
+ recent on top\".
+
+`recent-files-permanent-submenu'
+ If this variable is non-nil, the permanent entries are put into
+ a separate submenu of the recent-files menu. The default is
+ nil.
+
+`recent-files-non-permanent-submenu'
+ If this variable is non-nil, the non-permanent entries are put
+ into a separate submenu of the recent-files menu. The default
+ is nil. (You can set both `recent-files-permanent-submenu' and
+ `recent-files-non-permanent-submenu' to t to have both lists in
+ separate submenus.)
+
+`recent-files-commands-submenu'
+ If this variable is non-nil, the commands if recent-files are
+ placed in a submenu of the recent-files menu. The default is
+ nil.
+
+`recent-files-commands-submenu-title'
+ If the commands are placed in a submenu, this string is used as
+ the title of the submenu. The default is \"Commands...\".
+
+`recent-files-actions-on-top'
+ If this variable is non-nil, the \"action\" menu entries (\"Make
+ <buffer> permanent\" etc.) are put on top of the menu. Otherwise
+ they appear below the file entries or submenus. The default is
+ nil.
+
+`recent-files-permanent-first'
+ If this variable is t, the permanent entries are put first in
+ the recent-files menu, i.e. above the non-permanent entries. If
+ the value is nil, non-permanent entries appear first. If the
+ value is neither t nor nil, the entries are sorted according to
+ recent-files-sort-function. The default is 'sort.
+
+`recent-files-find-file-command'
+ This variable contains to commandto execute when a file entry
+ is selected from the menu. Usually this will be `find-file',
+ which is the default.
+
+KNOWN BUG:
+ - recent-files overwrites the recent-files-save-file
+ unconditionally when Emacs exits. If you have two Emacs
+ processes running, the one exiting later will overwrite the
+ file without merging in the new entries from the other Emacs
+ process. This can be avoided by disabling the save on exit from
+ the menu."
+:short-doc "`Recent Files' menu"
+:group 'menus
+:enable 'recent-files-initialize)
+)
+
;;; EOF
Index: xemacs-packages/edit-utils/redo.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/redo.el,v
retrieving revision 1.2
diff -u -p -r1.2 redo.el
--- xemacs-packages/edit-utils/redo.el 2000/11/16 14:11:57 1.2
+++ xemacs-packages/edit-utils/redo.el 2005/01/31 20:55:50
＠＠ -200,4 +200,34 ＠＠ A numeric argument serves as a repeat co
(message "Undo!"))
(setq last-buffer-undo-list buffer-undo-list))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'redo
+"XEmacs' normal undo system allows you to undo an arbitrary
+number of buffer changes. These undos are recorded as ordinary
+buffer changes themselves. So when you break the chain of
+undos by issuing some other command, you can then undo all
+the undos. The chain of recorded buffer modifications
+therefore grows without bound, truncated only at garbage
+collection time.
+
+The redo/undo system is different in two ways:
+ 1. The undo/redo command chain is only broken by a buffer
+ modification. You can move around the buffer or switch
+ buffers and still come back and do more undos or redos.
+ 2. The `redo' command rescinds the most recent undo without
+ recording the change as a _new_ buffer change. It
+ completely reverses the effect of the undo, which
+ includes making the chain of buffer modification records
+ shorter by one, to counteract the effect of the undo
+ command making the record list longer by one."
+:short-doc "Standard undo/redo commands"
+:group 'editing
+:require 'redo
+:enable #'identity
+ ;; no :disable
+)
+)
+
;;; redo.el ends here
Index: xemacs-packages/edit-utils/reportmail.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/reportmail.el,v
retrieving revision 1.3
diff -u -p -r1.3 reportmail.el
--- xemacs-packages/edit-utils/reportmail.el 1999/12/01 08:30:51 1.3
+++ xemacs-packages/edit-utils/reportmail.el 2005/01/31 20:55:50
＠＠ -994,4 +994,97 ＠＠ non-nil, always match using regexps."
(progn (message "Reportmail: %s" mesg)
(sit-for display-time-debugging-delay)))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'reportmail
+"When new mail arrives, a brief blurb about it will be displayed in the
+mode line, and a more verbose message will be printed in the echo area.
+But unlike most echo-area messages, this message will not go away at
+the next keystroke - it doesn't go away until the next extended-command
+is used. This is cool because that means you won't miss seeing the
+subject of the newly-arrived mail because you happened to be typing when
+it arrived.
+
+But if you set the variable `display-time-flush-echo-area' to t, then this
+message will be cleared every `display-time-interval' seconds. This means
+the message will be around for at most 30 seconds or so, which you may
+prefer.
+
+Site Configuration
+------------------
+
+The variables display-time-incoming-mail-file and
+display-time-message-separator identify the location and format of
+your waiting messages. If you are in the CMU SCS environment, or
+are on a generic BSD unix system, this code should work right away.
+Otherwise, you might need to modify the values of these to make things
+work.
+
+Junk Mail
+---------
+
+The reportmail package has a notion of \"junk mail,\" which can be used to
+reduce the frequency of irritating interruptions by reporting only the
+arrival of messages that seem to be interesting. If you're on a lot
+of high-volume mailing lists, this can be quite convenient. To use
+this facility, add something like the following to your .emacs file:
+
+ ;; The value of this variable is a list of lists, where the first
+ ;; element in each list is the name of a header field and the
+ ;; remaining elements are various elements of the value of this
+ ;; header field that signal the junkiness of a message.
+ (setq display-time-junk-mail-checklist
+ '((\"From\" \"bcp\" \"Benjamin Pierce\" \"Benjamin.Pierce\"
+ \"Mail Delivery Subsystem\" \"network\" \"daemon＠bartok\")
+ (\"To\" \"sml-request\" \"sml-redistribution-request\"
+ \"scheme\" \"TeXhax-Distribution-list\")
+ (\"Resent-From\" \"Benjamin.Pierce\")
+ (\"Sender\" \"WRITERS\" \"Haskell\" \"Electronic Music Digest\" \"NEW-LIST\")))
+
+By default, the entries in this list are matched exactly as
+substrings of the given header fields. If an entry begins with
+the character ^ it will be matched as a regular expression. If the
+variable display-time-match-using-regexps is set, then all entries
+will be matched as regular expressions.
+
+Note that elements of display-time-my-addresses are NOT automatically
+included in display-time-junk-mail-checklist. If you want mail from
+yourself to be considered junkmail, you must add your addresses to
+display-time-junk-mail-checklist too.
+
+
+Xbiff Interface
+---------------
+
+If you normally keep your emacs window iconified, reportmail can
+maintain an xbiff or xbiff++ display as well. The xbiff window will only
+be highlighted when non-junk mail is waiting to be read. For example:
+
+ (if window-system-version
+ (setq display-time-use-xbiff t))
+ (setq display-time-xbiff-arg-list '(\"-update\" \"30\" \"-geometry\" \"+0+0\"))
+ (setq display-time-xbiff-program \"xbiff++\")
+"
+:short-doc "Display time, load, new mail in mode line"
+:group 'display
+:require 'reportmail
+:enable #'(lambda ()
+ (setq display-time-my-addresses
+ (nconc
+ (and user-mail-address user-mail-address)
+ (and user-mail-address (string-match "^\\(.*\\)＠"
+ user-mail-address)
+ (match-string 1))
+ (list (user-full-name) (user-login-name))))
+
+ ;; By default, mail arrival is reported with a message but no
+ ;; beep
+ (setq display-time-mail-ring-bell t)
+
+ (display-time))
+ ;; no :disable
+ )
+)
+
(provide 'reportmail)
Index: xemacs-packages/edit-utils/resume.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/resume.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 resume.el
--- xemacs-packages/edit-utils/resume.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/resume.el 2005/01/31 20:55:50
＠＠ -126,6 +126,32 ＠＠
(write-region (point-min) (point-max) file nil 'quiet))
(set-buffer-modified-p nil)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'resume
+"The purpose of this library is to handle command line arguments
+when you resume an existing Emacs job.
+
+You can't get the benefit of this library by using the `xemacs' command,
+since that always starts a new Emacs job. Instead you must use a
+command called `edit' which knows how to resume an existing Emacs job
+if you have one, or start a new Emacs job if you don't have one.
+
+To define the `edit' command, run the script etc/emacs.csh (if you use CSH),
+or etc/emacs.bash if you use BASH. You would normally do this in your
+login script."
+:short-doc "Process command line args from within a suspended XEmacs job"
+:group 'processes
+:enable #'(lambda ()
+ (add-hook 'suspend-hook 'resume-suspend-hook)
+ (add-hook 'suspend-resume-hook 'resume-process-args))
+:disable #'(lambda ()
+ (remove-hook 'suspend-hook 'resume-suspend-hook)
+ (remove-hook 'suspend-resume-hook 'resume-process-args))
+ )
+)
+
(provide 'resume)
;;; resume.el ends here
Index: xemacs-packages/edit-utils/rsz-minibuf.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/rsz-minibuf.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 rsz-minibuf.el
--- xemacs-packages/edit-utils/rsz-minibuf.el 1998/01/14 06:36:14 1.1.1.1
+++ xemacs-packages/edit-utils/rsz-minibuf.el 2005/01/31 20:55:50
＠＠ -225,6 +225,55 ＠＠ respectively."
(set-frame-size (selected-frame) (frame-width)
(plist-get minibuffer-frame-plist 'height)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'resize-minibuffer
+"This package allows the entire contents (or as much as possible) of the
+minibuffer to be visible at once when typing. As the end of a line is
+reached, the minibuffer will resize itself. When the user is done
+typing, the minibuffer will return to its original size.
+
+In window systems where it is possible to have a frame in which the
+minibuffer is the only window, the frame itself can be resized.
+
+\[[ NOTE: The code to resize frames has not been tested under Lucid Emacs,
+because detached minibuffers are broken. ]] not accurate.
+
+Note that the minibuffer and echo area are not the same! They simply
+happen to occupy roughly the same place on the frame. Messages put in
+the echo area will not cause any resizing by this package.
+
+This package is considered a minor mode but it doesn't put anything in
+minor-mode-alist because this mode is specific to the minibuffer, which
+has no modeline.
+
+When this behavior is enabled, the minibuffer is dynamically resized to
+contain the entire region of text put in it as you type.
+
+The maximum height to which the minibuffer can grow is controlled by the
+variable `resize-minibuffer-window-max-height'.
+
+The variable `resize-minibuffer-window-exactly' determines whether the
+minibuffer window should ever be shrunk to make it no larger than needed to
+display its contents.
+
+When using a window system, it is possible for a minibuffer to be the sole
+window in a frame. Since that window is already its maximum size, the only
+way to make more text visible at once is to increase the size of the frame.
+The variable `resize-minibuffer-frame' controls whether this should be
+done. The variables `resize-minibuffer-frame-max-height' and
+`resize-minibuffer-frame-exactly' are analogous to their window
+counterparts."
+:short-doc "Dynamically resize minibuffer to display entire contents"
+:group 'buffers-and-windows
+:enable #'(lambda ()
+ (resize-minibuffer-mode 1))
+:disable #'(lambda ()
+ (resize-minibuffer-mode -1))
+ )
+)
+
(provide 'rsz-minibuf)
Index: xemacs-packages/edit-utils/saveconf.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/saveconf.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 saveconf.el
--- xemacs-packages/edit-utils/saveconf.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/saveconf.el 2005/01/31 20:55:50
＠＠ -282,3 +282,60 ＠＠ point is set in each window to what is w
(save-excursion
(set-buffer (get-buffer-create "*scratch*"))
default-directory))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'save-context
+"This package of functions gives Emacs the ability to remember which
+files were being visited, the windows that were on them, and the
+value of point in their buffers the last Emacs session in the same
+directory. This is an emulation of an old Gosling Emacs feature.
+
+The relevant commands are save-context and recover-context.
+
+Most of the time you'll want an Emacs session's context saved even if
+you choose not to recover it later. To avoid having to manually
+M-x save-context at each emacs exit, put the line:
+ (setq auto-save-and-recover-context t)
+in your .emacs or in default.el in the lisp directory of the Emacs
+distribution. The context will then automatically be saved when
+Emacs exits.
+
+By default only the contexts of visible buffers (buffers with windows
+on them) are saved. Setting the variable save-buffer-context to t
+causes the contexts of all buffers to be saved.
+
+Put this file in the \"lisp\" directory of the emacs distribution in a
+file called saveconf.el. Byte-compile it.
+
+There are two ways to use this package.
+ 1) Put the line
+ (require 'saveconf)
+ in the file site-init.el in the lisp directory of the Emacs
+ directory and rebuild Emacs. If you get the \"Pure Lisp storage
+ exhausted\" error message when rebuilding Emacs, increase PURESIZE
+ in src/config.h by about 30000 bytes and try again. It's almost
+ certain that this will happen to you so you might as well increase
+ PURESIZE beforehand.
+
+ This is the preferred mode of operation because it allows the
+ package to become part of Emacs' startup sequence and automatically
+ restore context in a directory if Emacs is invoked without any
+ command line arguments.
+
+ 2) Put these lines
+ (require 'saveconf)
+ (if (null (cdr command-line-args))
+ (setq inihibit-startup-message (recover-context)))
+ at the end of your .emacs file or the default.el file in the
+ lisp directory of the Emacs distribution. This causes the
+ context saved in the current directory to be recovered whenever
+ Emacs is invoked without any arguments.
+"
+:short-doc "Save buffer and window configs between editing sessions"
+:group 'buffers-and-windows
+;; #### Write the hooks correctly so they don't require manual modification
+;; of init.el.
+ )
+)
Index: xemacs-packages/edit-utils/savehist.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/savehist.el,v
retrieving revision 1.2
diff -u -p -r1.2 savehist.el
--- xemacs-packages/edit-utils/savehist.el 1999/11/27 20:49:59 1.2
+++ xemacs-packages/edit-utils/savehist.el 2005/01/31 20:55:50
＠＠ -200,6 +200,33 ＠＠ A variable will be saved if it is bound
(subseq arg 0 n)
arg))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'save-history
+"Many editors (e.g. Vim) have the feature of saving minibuffer
+history to an external file after exit. This package provides the
+same feature in Emacs. When Emacs is about the exit,
+`savehist-save' will dump the contents of various minibuffer
+histories (as determined by `savehist-history-variables') to a save
+file (`~/.emacs-history' by default). Although the package was
+designed for saving the minibuffer histories, any variables can be
+saved that way.
+
+To use savehist, put the following to `~/.emacs':
+
+\(require 'savehist)
+\(savehist-load)
+
+Be sure to have `savehist.el' in a directory that is in your
+load-path, and byte-compile it."
+:short-doc "Save minibuffer history"
+:group 'editing
+;; #### Write the hooks correctly so they don't require manual modification
+;; of init.el.
+ )
+)
+
(provide 'savehist)
;;; savehist.el ends here
Index: xemacs-packages/edit-utils/saveplace.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/saveplace.el,v
retrieving revision 1.2
diff -u -p -r1.2 saveplace.el
--- xemacs-packages/edit-utils/saveplace.el 2002/10/19 20:18:07 1.2
+++ xemacs-packages/edit-utils/saveplace.el 2005/01/31 20:55:50
＠＠ -232,11 +232,28 ＠＠ To save places automatically in all file
(if save-place-loaded
(save-place-alist-to-file)))
-(add-hook 'find-file-hooks 'save-place-find-file-hook t)
-
-(add-hook 'kill-emacs-hook 'save-place-kill-emacs-hook)
-
-(add-hook 'kill-buffer-hook 'save-place-to-alist)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'save-place
+"Automatically save place in files, so that visiting them later
+\(even during a different Emacs session) automatically moves point
+to the saved position, when the file is first found. Uses the
+value of buffer-local variable save-place to determine whether to
+save position or not."
+:short-doc "Automatically save place in files"
+:require 'saveplace
+:group 'buffers-and-windows
+:enable #'(lambda ()
+ (add-hook 'find-file-hooks 'save-place-find-file-hook t)
+ (add-hook 'kill-emacs-hook 'save-place-kill-emacs-hook)
+ (add-hook 'kill-buffer-hook 'save-place-to-alist))
+:disable #'(lambda ()
+ (remove-hook 'find-file-hooks 'save-place-find-file-hook t)
+ (remove-hook 'kill-emacs-hook 'save-place-kill-emacs-hook)
+ (remove-hook 'kill-buffer-hook 'save-place-to-alist))
+ )
+)
(provide 'saveplace) ; why not...
Index: xemacs-packages/edit-utils/scroll-in-place.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/scroll-in-place.el,v
retrieving revision 1.4
diff -u -p -r1.4 scroll-in-place.el
--- xemacs-packages/edit-utils/scroll-in-place.el 2002/05/11 05:41:23 1.4
+++ xemacs-packages/edit-utils/scroll-in-place.el 2005/01/31 20:55:51
＠＠ -1575,6 +1575,156 ＠＠ call this function from other code."
;; This doesn't work with Red Gnus
;; (add-hook 'gnus-article-mode-hook 'turn-off-scroll-in-place)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'scroll-in-place
+"This package provides improved vertical scrolling commands for XEmacs.
+These new commands offer the following features:
+
++ When a scrolling command is executed, XEmacs tries to keep point as
+ close as possible to its original window position (window line and
+ column). This is what \"scroll in place\" means: point stays \"in place\"
+ within the window. (There are times when point must be moved from its
+ original window position in order to execute the scroll; see below.)
+
+ The variable `scroll-in-place', which is true by default, determines
+ whether or not the standard XEmacs scrolling commands (`scroll-down',
+ `scroll-up', `scroll-other-window-down', and `scroll-other-window') use
+ the \"in place\" features listed here. When `scroll-in-place' is `nil'
+ the standard XEmacs scrolling commands essentially just call the
+ original versions of themselves. (Note that even when `scroll-in-place'
+ is `nil' the new versions of `scroll-down' and `scroll-up' have slightly
+ different behavior when a minibuffer window is the selected window. See
+ below.)
+
+ It is possible to turn off (or turn on) \"in place\" scrolling for certain
+ buffers by making buffer-local bindings of the variable `scroll-in-
+ place' for those buffers. The variable `scroll-in-place' is not usually
+ buffer-local, but you can make it so if you desire.
+
++ Because the improved scrolling commands keep point at its original
+ window position, these scrolling commands are \"reversible.\" The
+ `scroll-up' command undoes the effect of the immediately previous
+ `scroll-down' command (if any) and vice versa. In other words, if you
+ scroll up and then immediately scroll back down, the window config-
+ uration is restored to its exact original state. This allows you to
+ browse through a buffer more easily, as you can always get back to the
+ original configuration.
+
+ Note, however, that the improved scrolling commands are guaranteed to be
+ reversible only if there are no intervening non-scrolling commands.
+ Also, if you give a prefix argument to a scrolling command (in order to
+ specify the number of lines to scroll by), previous scrolling commands
+ may no longer be reversible. More specifically, if the new prefix
+ argument has a different magnitude than the previous scrolling distance,
+ then any previous scrolling commands are not reversible. The new prefix
+ argument takes precedence.
+
+ You might find it useful to think of the scrolling commands as forming
+ \"chains.\" A scrolling command either starts or continues a chain. By
+ issuing a non-scrolling command or by changing the number of lines to be
+ scrolled, you break the chain. (Note that simply changing the scrolling
+ direction won't break the chain; changing the absolute number of lines
+ to be scrolled is what breaks the chain.) Scrolling commands are
+ guaranteed to be reversible only within the current chain. Hopefully
+ that's clear enough.
+
++ When a scrolling command is given a prefix argument (which specifies the
+ number of lines to scroll by), then that argument becomes the default
+ scrolling distance for all immediately subsequent scrolling commands.
+ This means that you can easily set the scrolling distance for a chain
+ of scrolling commands. Note that a new prefix argument or any non-
+ scrolling command breaks the chain (as described above), and any further
+ scrolling commands will use the usual defaults (or the prefix argument
+ you specify at that time, of course).
+
+ However, there are cases in which one doesn't want the current scrolling
+ command to use the default scrolling distance that was set by the
+ previous scrolling command. For example, suppose that you had special
+ commands that scrolled one line up and one line down. When you invoke
+ one of these commands, the \"in place\" scrolling routines set the default
+ scrolling distance to be just one line. Now suppose that you use one of
+ your special commands and then immediately invoke `scroll-up' (`C-v'),
+ expecting it to scroll by a near windowful of text. You would be
+ disappointed --- because the previous command set the default scrolling
+ distance to be just one line, `scroll-up' just scrolls by one line.
+
+ To solve this problem, \"scroll-in-place\" allows you to divide scrolling
+ commands into separate \"groups.\" Commands in a group can only form
+ chains with (and therefore, inherit defaults from) commands in the same
+ group. (Note that no command can be in more than one group.) If you
+ invoke a scrolling command that is not in the same group as that of the
+ immediately previous scrolling command, then the previous chain is
+ broken and you start a new chain --- with a new set of defaults.
+
+ So to solve the problem described above, you could put your one-line
+ scrolling commands in their own group. Once that is done, the standard
+ scrolling commands will not form chains with your one-line scrolling
+ commands, and therefore will not use the default scrolling distance set
+ by those commands. Problem solved!
+
+ By default, all \"in place\" scrolling commands are in a single group. If
+ you want to partition some commands into separate groups, you must do
+ that yourself *before* any \"in place\" commands are invoked. For more
+ information about grouping commands, see the documentation for the
+ variables `scroll-command-groups' and `scroll-default-command-group'.
+
++ The improved scrolling commands will avoid displaying empty lines past
+ the end of the buffer when possible. In other words, just as you can't
+ see \"dead space\" before the beginning of the buffer text, the new
+ scrolling commands try to avoid displaying \"dead space\" past the end of
+ the buffer text. This behavior is somewhat configurable; see the
+ documentation for the variable `scroll-allow-blank-lines-past-eob'.
+
+ Dead space will be displayed if it is necessary in order to make a
+ previous scrolling action reversible, however.
+
++ If the scrolling commands cannot keep point at its initial window
+ position (because a buffer boundary is on screen and the window can't be
+ scrolled as far as necessary to keep point at the right place), point is
+ allowed to temporarily stray from its initial window position. That is,
+ point moves the correct number of window lines, even if it means that it
+ has to stray from its desired window position. This straying is undone
+ when (and if) the scrolling action is reversed.
+
++ If a scrolling command tries to move point past a buffer boundary, point
+ is instead moved to the boundary (the beginning or the end of the buffer
+ as appropriate) and an appropriate message is displayed. This motion is
+ reversible, of course.
+
+ However, if point was already at the buffer boundary when the scrolling
+ command was invoked, the command signals an appropriate error instead.
+
++ When a minibuffer window is the selected window, the new versions of
+ `scroll-up' and `scroll-down' either scroll the window in the variable
+ `minibuffer-scroll-window' (which is usually the window of completions)
+ or the `next-window' if there is no `minibuffer-scroll-window'. This is
+ usually much more useful than scrolling the minibuffer itself. (Note
+ that this feature is available even when the variable `scroll-in-place'
+ is `nil'.)
+
++ When a scrolling command is scrolling a window other than the selected
+ window, it will signal an appropriate buffer boundary error if the
+ window cannot be scrolled (because the appropriate buffer boundary is
+ already visible). This means that an error is signalled even in cases
+ that would be allowed (by \"straying\" point or by moving it to the buffer
+ boundary) if the window were selected.
+
+ (If an error were not signalled in these cases, then there would be many
+ cases in which the last scroll in a particular direction would appear to
+ do nothing because only the point position would change --- the
+ displayed text would stay the same! To avoid these cases the scrolling
+ commands signal boundary errors \"prematurely\" when the window to be
+ scrolled is not selected.)"
+:short-doc "Keep cursor on same line when scrolling"
+:group 'editing
+:require 'scroll-in-place
+:enable #'turn-on-scroll-in-place
+:disable #'turn-off-scroll-in-place)
+)
+
+
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;
Index: xemacs-packages/edit-utils/setnu.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/setnu.el,v
retrieving revision 1.3
diff -u -p -r1.3 setnu.el
--- xemacs-packages/edit-utils/setnu.el 2002/07/24 18:36:50 1.3
+++ xemacs-packages/edit-utils/setnu.el 2005/01/31 20:55:51
＠＠ -447,3 +447,17 ＠＠ it is created based on where the extent
(add-hook 'before-change-functions 'setnu-before-change-function)
(add-hook 'after-change-functions 'setnu-after-change-function)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'setnu
+"vi-style line number mode for XEmacs"
+:short-doc "vi-style line number mode for XEmacs"
+:group 'display
+:enable #'(lambda ()
+ (setnu-mode 1))
+:disable #'(lambda ()
+ (setnu-mode -1))
+ )
+)
Index: xemacs-packages/edit-utils/shell-font.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/shell-font.el,v
retrieving revision 1.2
diff -u -p -r1.2 shell-font.el
--- xemacs-packages/edit-utils/shell-font.el 1998/04/23 11:12:00 1.2
+++ xemacs-packages/edit-utils/shell-font.el 2005/01/31 20:55:51
＠＠ -148,13 +148,31 ＠＠ face-manipulation functions."
(set-process-filter proc 'shell-font-process-filter))
nil)
-(add-hook 'shell-mode-hook 'install-shell-fonts)
-(add-hook 'telnet-mode-hook 'install-shell-fonts)
-(add-hook 'gdb-mode-hook 'install-shell-fonts)
-
;; for compatibility with the 19.8 version
;(fset 'install-shell-font-prompt 'install-shell-fonts)
(make-obsolete 'install-shell-font-prompt 'install-shell-fonts)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'shell-font
+"The prompt in your shell-buffers will appear bold-italic, process
+output will appear in normal face, and typein will appear in bold.
+
+The faces shell-prompt, shell-input and shell-output can be modified
+as desired, for example, (copy-face 'italic 'shell-prompt)."
+:short-doc "Decorate a shell buffer with fonts"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'shell-mode-hook 'install-shell-fonts)
+ (add-hook 'telnet-mode-hook 'install-shell-fonts)
+ (add-hook 'gdb-mode-hook 'install-shell-fonts))
+:disable #'(lambda ()
+ (remove-hook 'shell-mode-hook 'install-shell-fonts)
+ (remove-hook 'telnet-mode-hook 'install-shell-fonts)
+ (remove-hook 'gdb-mode-hook 'install-shell-fonts))
+ )
+)
(provide 'shell-font)
Index: xemacs-packages/edit-utils/toolbar-utils.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/toolbar-utils.el,v
retrieving revision 1.2
diff -u -p -r1.2 toolbar-utils.el
--- xemacs-packages/edit-utils/toolbar-utils.el 2002/12/12 03:28:33 1.2
+++ xemacs-packages/edit-utils/toolbar-utils.el 2005/01/31 20:55:52
＠＠ -479,6 +479,61 ＠＠ This function will not find spacers."
(setq pos (1+ pos)))
(if toolbar pos nil)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'toolbar-utils
+"This contains utilities for managing XEmacs toolbars.
+
+`restore-initial-toolbar'
+
+Restores the default toolbar defined by initial-toolbar-spec.
+There is also a cache of killed buttons in `button-palette'.
+
+`toolbar-add-button-on-the-fly'
+
+Add an button at POSITION to the default toolbar of the selected window.
+
+`toolbar-add-kbd-macro'
+
+Add a button invoking a keyboard macro to the toolbar of the current buffer.
+The button is added at the end of the left group.
+
+`toolbar-add-execute-macro-button'
+
+Add a button to the global toolbar to execute the last keyboard macro."
+:short-doc "Toolbar utility functions"
+:group 'toolbars
+:commands '(["Add toolbar button on-the-fly" toolbar-add-button-on-the-fly]
+ ["Add button for a macro to toolbar" toolbar-add-kbd-macro]
+ ["Add execute-last-macro button to toolbar" toolbar-add-execute-macro-button]
+ ["Restore initial toolbar" restore-initial-toolbar])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'toolbar-add-exec-macro
+"Add a button to the global toolbar to execute the last keyboard macro.
+
+Unlike `toolbar-add-kbd-macro', this does not copy the macro. The macro
+executed will change with redefinitions.
+
+Due to a simple implementation, this button will not appear in buffers with
+local toolbars if invoked after the toolbar is installed. If you like this
+button, it's probably best to invoke this function in your init file.
+
+See also the `toolbar-utils' behavior."
+:short-doc "Add execute-macro button to the toolbar"
+:group 'toolbars
+:enable #'toolbar-add-execute-macro-button
+ ;; no :disable
+ )
+)
+
(provide 'toolbar-utils)
;;; toolbar-utils.el ends here
Index: xemacs-packages/edit-utils/uniquify.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/uniquify.el,v
retrieving revision 1.5
diff -u -p -r1.5 uniquify.el
--- xemacs-packages/edit-utils/uniquify.el 2001/12/27 00:47:21 1.5
+++ xemacs-packages/edit-utils/uniquify.el 2005/01/31 20:55:52
＠＠ -475,4 +475,27 ＠＠ Meant to be called from the `uniquify-ig
(add-hook 'kill-buffer-hook 'delay-uniquify-rationalize-file-buffer-names)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'uniquify
+"Emacs's standard method for making buffer names unique adds <2>, <3>,
+etc. to the end of (all but one of) the buffers. This file replaces
+that behavior, for buffers visiting files and dired buffers, with a
+uniquification that adds parts of the file name until the buffer names
+are unique. For instance, buffers visiting /u/mernst/tmp/Makefile and
+/usr/projects/zaphod/Makefile would be named Makefile|tmp and
+Makefile|zaphod, respectively (instead of Makefile and Makefile<2>).
+Other buffer name styles are also available."
+:short-doc "unique buffer names dependent on file name"
+:require 'uniquify
+:group 'buffers-and-windows
+:enable #'(lambda ()
+ (setq uniquify-buffer-name-style 'post-forward))
+:disable #'(lambda ()
+ (setq uniquify-buffer-name-style nil))
+ )
+)
+
+
;;; uniquify.el ends here
Index: xemacs-packages/edit-utils/vertical-mode.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/vertical-mode.el,v
retrieving revision 1.2
diff -u -p -r1.2 vertical-mode.el
--- xemacs-packages/edit-utils/vertical-mode.el 2002/03/24 20:52:50 1.2
+++ xemacs-packages/edit-utils/vertical-mode.el 2005/01/31 20:55:52
＠＠ -72,5 +72,23 ＠＠
minor-mode-alist (cons
'(vertical-mode " Vertical") minor-mode-alist))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'vertical-mode
+"This minor mode allows you to conviently edit things that are oriented
+vertically (like tables in computer programs): after each action, cursor
+moves down. Therefore, to move block of text to the right, you simply enter
+vertical mode and then hold spacebar, waiting for autorepeat to do the job
+for you."
+:short-doc "edit vertical tables"
+:group 'editing
+:enable #'(lambda ()
+ (vertical-mode 1))
+:disable #'(lambda ()
+ (vertical-mode -1))
+ )
+)
+
(provide 'vertical-mode)
;;; vertical-mode.el ends here
Index: xemacs-packages/edit-utils/where-was-i-db.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/where-was-i-db.el,v
retrieving revision 1.5
diff -u -p -r1.5 where-was-i-db.el
--- xemacs-packages/edit-utils/where-was-i-db.el 2000/10/06 09:08:02 1.5
+++ xemacs-packages/edit-utils/where-was-i-db.el 2005/01/31 20:55:52
＠＠ -358,6 +358,108 ＠＠ that, for obvious reasons. If it isn't
wwi-db))))
(put 'wwi-with-open-database 'lisp-indent-function 1)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'where-was-i-db
+"This Good Thing will make XEmacs keep track of where you were last
+time you visited a file.
+
+It works by installing functions on the `find-file-hooks' and on
+the buffer-local `kill-buffer-hook'. When a buffer is killed, if
+it was visiting a file, and place saving has been enabled for it, a
+database entry is made, saving the location of `point'. When you
+visit a file, the database is queried, keyed on `buffer-file-name',
+and if an entry is found, point is set to the value retrieved, and
+place saving is enabled again for that buffer.
+
+There is a command, which is initially not bound to a keystroke in
+this incarnation; and may never be, since I think completion works
+well enough:
+
+`M-x toggle-where-was-i' aka `M-x tog[TAB]w[TAB]'
+
+... that will turn place saving on and off on a per-file, buffer-
+local basis. If `where-was-i-db' has been turned off in a buffer
+and then you kill it, or exit XEmacs, any record for that file will
+be purged from the database, and you'll start at the top of the
+file next time you open it, with place saving turned off there.
+
+Place saving is automatically still `on' when you visit a file you'd
+toggled it on for in a previous session or visitation. (That's the
+point of it, after all.)
+
+Toggling place saving on in a buffer visiting a file is all that is
+required to cause the `where-was-i-db' feature to be autoloaded, as
+`toggle-where-was-i' will call on `install-where-was-i' if the
+`wwi-ffh' has not yet been installed. That WILL NOT cause this
+feature to be automatically enabled in your next XEmacs invocation,
+however. For that, you must customize and save
+`wwi-auto-install-on-startup-flag'.
+There is more information about this in its docstring.
+
+ This feature can be unloaded with:
+
+`C-u M-x install-where-was-i'
+
+... this will call `unload-feature', as well as traverse the
+`buffer-list' removing the buffer-local `kill-buffer-hook'
+installed by this program. Note that any buffers that got place
+saving enabled by having had an entry in the database for them when
+they were first visited (thus restoring point to where it was the
+last time you had visited the file), will not have an updated entry
+made, nor the old entry removed (as would happen if you
+`toggle-where-was-i' to off in just that buffer), after you
+uninstall this feature like that.
+
+If you toggle it on again in a buffer visiting a file, then kill
+that buffer, the point will be saved for it. When you kill the
+other buffers that had place saving enabled before you uninstalled
+the feature with `C-u M-x install-where-was-i', no `where-was-i-db'
+database update will happen for them, since their buffer-local
+`kill-buffer-hook' will have been cleaned of the member
+`wwi-save-where-i-am', the function that writes the `point' entry
+to the database when a buffer is killed. If you then re-visit one
+of those files, point will get restored to the location it did the
+last time you visited that file with `where-was-i-db' installed.
+
+To remove a file from the place saving database, simply visit it,
+`M-x toggle-where-was-i' to switch `where-was-i-db' off, then kill
+that buffer. You can see how this works by looking at the
+definition of `wwi-save-where-i-am'. I dare you not to... (may as
+well use VI.)
+
+After a period of time, the database of saved file positions will
+become cluttered with the names of files that no longer exist. You
+may vacume out the crumbs using:
+
+`M-x wwi-vacume-where-was-i-db'
+
+... which will prompt you for an optional regular expression to
+match files you want records removed for. It will traverse the
+database and remove entries for file names that either match the
+regexp, or that are (not (file-exists-p file-name)). The main
+reason for this command is the removal of stale entries, for files
+that no longer exist on the filesystem.
+
+Note also that running `wwi-vacume-where-was-i-db' will cause EFS
+traffic, if you've saved your place in any remote files. Don't be
+surprised if your dialing daemon picks up the phone when you run
+the vacume function. You should be able to purge the database of
+all EFS entries with a simple regular expression passed to
+`wwi-vacume-where-was-i-db'. Of course, you might not want to do
+that, for obvious reasons. If it isn't obvious, use VI or PICO.
+"
+:short-doc "Keep persistent state in visited files"
+:group 'files
+:enable #'(lambda ()
+ (install-where-was-i 1))
+:enable #'(lambda ()
+ (install-where-was-i -1))
+ )
+)
+
(provide 'where-was-i-db)
Index: xemacs-packages/edit-utils/winring.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/winring.el,v
retrieving revision 1.2
diff -u -p -r1.2 winring.el
--- xemacs-packages/edit-utils/winring.el 2004/01/05 16:56:54 1.2
+++ xemacs-packages/edit-utils/winring.el 2005/01/31 20:55:52
＠＠ -588,6 +588,106 ＠＠ in a timely way.\n\n")
;; ...and the init fence
(setq winring-initialized t)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'winring
+"This package provides lightweight support for circular rings of
+window configurations. A window configuration is the layout of
+windows and associated buffers within a frame. There is always at
+least one configuration on the ring, the current configuration.
+You can create new configurations and cycle through the layouts in
+either direction. You can also delete configurations from the ring
+\(except the last one of course!). Window configurations are named,
+and you can jump to and delete named configurations. Display of
+the current window configuration name in the mode line is only
+supported as of Emacs 20.3 and XEmacs 21.0.
+
+Window configuration rings are frame specific. That is, each frame
+has its own ring which can be cycled through independently of other
+frames. This is the way I like it.
+
+You are always looking at the current window configuration for each
+frame, which consists of the windows in the frame, the buffers in
+those windows, and point in the current buffer. As you run
+commands such as \"C-x 4 b\", \"C-x 2\", and \"C-x 0\" you are modifying
+the current window configuration. When you jump to a new
+configuration, the layout that existed before the jump is captured,
+and the ring is rotated to the selected configuration. Window
+configurations are captured with `current-window-configuration',
+however winring also saves point for the current buffer.
+
+Note that by default, this binds the winring keymap to the C-x 7
+prefix, but you can change this by setting the value of
+`winring-keymap-prefix', before you call `winring-initialize'.
+Note that this is a change from previous versions of winring; the
+prefix used to be M-o but was changed on the suggestion of RMS.
+
+The following commands are defined:
+
+ C-x 7 n -- Create a new window configuration. The new
+ configuration will contain a single buffer, the one
+ named in the variable `winring-new-config-buffer-name'
+
+ With C-u, winring prompts for the name of the new
+ configuration. If you don't use C-u the function in
+ `winring-name-generator' will be called to get the
+ new configuration's name.
+
+ C-x 7 2 -- Create a duplicate of the current window
+ configuration. C-u has the same semantics as with
+ \"C-x 7 c\".
+
+ C-x 7 j -- Jump to a named configuration (prompts for the name).
+
+ C-x 7 0 -- Kill the current window configuration and rotate to the
+ previous layout on the ring. You cannot delete the
+ last configuration in the ring. With C-u, prompts
+ for the name of the configuration to kill.
+
+ C-x 7 o -- Go to the next configuration on the ring.
+
+ C-x 7 p -- Go to the previous configuration on the ring.
+
+ Note that the sequence `C-x 7 o C-x 7 p' is a no-op;
+ it leaves you in the same configuration you were in
+ before the sequence.
+
+ C-x 7 r -- Rename the current window configuration.
+
+ C-x 7 b -- Submit a bug report on winring.
+
+ C-x 7 v -- Echo the winring version.
+
+As mentioned, window configuration names can be displayed in the
+modeline, but this feature only works with Emacs 20.3 and XEmacs
+21.0. A patch for XEmacs 20.4 to support this feature is available
+at the URL below. Note that the default value of
+`winring-show-names' is currently nil by default because if your
+X/Emacs doesn't have the necessary support, ugly things can happen
+\(no you won't crash your X/Emacs -- it just won't do what you
+want).
+
+If your X/Emacs has the necessary support, you can turn on display
+of window configuration names by setting `winring-show-names' to
+t. If you don't like the position in the modeline where winring
+names are shown, you can change this by passing in your own
+modeline hacker function to `winring-initialize'.
+
+ Winring on the Web:
+
+The winring Web page (including the aforementioned XEmacs 20.4
+patch) is
+
+ http://www.python.org/emacs/winring/
+"
+:short-doc "Window configuration rings"
+:group 'buffers-and-windows
+:enable #'winring-initialize
+ ;; no :disable
+ )
+)
+
(provide 'winring)
cvs server: Diffing xemacs-packages/edt
cvs server: Diffing xemacs-packages/efs
Index: xemacs-packages/efs/efs.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/efs/efs.el,v
retrieving revision 1.22
diff -u -p -r1.22 efs.el
--- xemacs-packages/efs/efs.el 2004/10/02 14:06:04 1.22
+++ xemacs-packages/efs/efs.el 2005/01/31 20:55:56
＠＠ -10837,6 +10837,39 ＠＠ in file name expansion."
(put 'file-name-completion 'efs 'efs-file-name-completion)
(put 'file-name-all-completions 'efs 'efs-file-name-all-completions)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'efs
+"EFS is a system for transparent file-transfer between remote VMS, CMS,
+MTS, MVS, Twenex, Explorer (the last two are Lisp machines), TOPS-20,
+DOS (running the Distinct, Novell, FTP software, NCSA, Microsoft in both
+unix and DOS mode, Super TCP, and Hellsoft FTP servers), Windows NT
+\(running the Microsoft or Hummingbird ftp servers), Unix descriptive
+listings (dl), KA9Q, OS/2 hosts using FTP. This means that you can edit,
+copy and otherwise manipulate files on any machine you have access to
+from within Emacs as if it were a local file. EFS works by introducing
+an extended filename syntax, and overloading functions such as
+`insert-file-contents' so that accessing a remote file causes
+appropriate commands to be sent to an FTP process.
+
+The syntax to use is like this:
+
+\(for anonymous:) /ftp.xemacs.org:/pub/xemacs/
+\(for non-anonymous:) /ben＠gwyn.tux.org:/etc/mail/xemacs/aliases-xemacs
+
+You can specify either a file or a directory (in the latter case,
+Dired will be brought up). All operations in XEmacs on such files
+should work exactly as on any other files, modulo the additional
+slowness."
+:short-doc "Transparent file access over FTP"
+:group 'internet
+:require 'efs-auto
+:enable #'ignore
+ ;; can't :disable
+ )
+)
+
;;;; ------------------------------------------------------------
;;;; Finally run any load-hooks.
;;;; ------------------------------------------------------------
cvs server: Diffing xemacs-packages/eicq
cvs server: Diffing xemacs-packages/eieio
cvs server: Diffing xemacs-packages/elib
cvs server: Diffing xemacs-packages/emerge
cvs server: Diffing xemacs-packages/erc
cvs server: Diffing xemacs-packages/escreen
cvs server: Diffing xemacs-packages/eshell
cvs server: Diffing xemacs-packages/ess
cvs server: Diffing xemacs-packages/ess/etc
cvs server: Diffing xemacs-packages/ess/etc/icons
cvs server: Diffing xemacs-packages/ess/lisp
cvs server: Diffing xemacs-packages/ess/texi
cvs server: Diffing xemacs-packages/eterm
cvs server: Diffing xemacs-packages/eterm/etc
cvs server: Diffing xemacs-packages/eterm/etc/e
cvs server: Diffing xemacs-packages/eudc
Index: xemacs-packages/eudc/eudc.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/eudc/eudc.el,v
retrieving revision 1.22
diff -u -p -r1.22 eudc.el
--- xemacs-packages/eudc/eudc.el 2001/08/17 12:31:41 1.22
+++ xemacs-packages/eudc/eudc.el 2005/01/31 20:55:57
＠＠ -1363,6 +1363,18 ＠＠ This does nothing except loading eudc by
;;}}}
;;;###autoload
+(defvar eudc-menu
+ '("Directory Search"
+ ["Load Hotlist of Servers" eudc-load-eudc t]
+ ["New Server" eudc-set-server t]
+ "---"
+ ["Query with Form" eudc-query-form t]
+ ["Expand Inline Query" eudc-expand-inline t]
+ "---"
+ ["Get Email" eudc-get-email t]
+ ["Get Phone" eudc-get-phone t]))
+
+;;;###autoload
(cond ((not (string-match "XEmacs" emacs-version))
(defvar eudc-tools-menu (make-sparse-keymap "Directory Search"))
(fset 'eudc-tools-menu (symbol-value 'eudc-tools-menu))
＠＠ -1383,17 +1395,10 ＠＠ This does nothing except loading eudc by
'("New Server" . eudc-set-server))
(define-key eudc-tools-menu [load]
'("Load Hotlist of Servers" . eudc-load-eudc)))
-
- (t
- (let ((menu '("Directory Search"
- ["Load Hotlist of Servers" eudc-load-eudc t]
- ["New Server" eudc-set-server t]
- "---"
- ["Query with Form" eudc-query-form t]
- ["Expand Inline Query" eudc-expand-inline t]
- "---"
- ["Get Email" eudc-get-email t]
- ["Get Phone" eudc-get-phone t])))
+
+ ;; Packages under XEmacs 21.5+ may not directly modify the menubar.
+ ((not (fboundp 'define-behavior-group))
+ (let ((menu eudc-menu))
(if (not (featurep 'eudc-autoloads))
(if (string-match "XEmacs" emacs-version)
(if (and (featurep 'menubar)
＠＠ -1414,6 +1419,16 ＠＠ This does nothing except loading eudc by
(cdr menu)))))))))))
;;}}}
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'eudc
+"Not documented."
+:short-doc "Directory Search"
+:group 'internet
+:commands (cdr eudc-menu))
+)
(provide 'eudc)
cvs server: Diffing xemacs-packages/footnote
Index: xemacs-packages/footnote/footnote.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/footnote/footnote.el,v
retrieving revision 1.7
diff -u -p -r1.7 footnote.el
--- xemacs-packages/footnote/footnote.el 2002/04/23 20:35:26 1.7
+++ xemacs-packages/footnote/footnote.el 2005/01/31 20:55:58
＠＠ -788,22 +788,6 ＠＠ being set it is automatically widened."
(define-key global-map footnote-prefix footnote-mode-map))
;;;###autoload
-(if (progn (condition-case () (require 'easymenu) (error nil))
- (fboundp 'easy-menu-add-item))
- (easy-menu-add-item nil '("Cmds")
- '("Footnotes"
- ["Add Footnote" Footnote-add-footnote t]
- ["Delete Footnote" Footnote-delete-footnote t]
- ["Goto Footnote" Footnote-goto-footnote t]
- ["Back to Message" Footnote-back-to-message t]
- ["Renumber Footnotes" Footnote-renumber-footnotes t]
- "--"
- ["Set Footnote Style" Footnote-set-style t]
- ["Cycle Footnote Style" Footnote-cycle-style t]
- )))
-
-
-;;;###autoload
(defun footnote-mode (&optional arg)
"Toggle footnote minor mode.
\\<message-mode-map>
＠＠ -860,6 +844,26 ＠＠ key binding
(setq minor-mode-alist
(cons '(footnote-mode footnote-mode-line-string)
minor-mode-alist)))
+
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'footnote
+ "Not documented."
+:short-doc "Footnotes"
+:group 'editing
+:commands
+ '(["Add Footnote" Footnote-add-footnote]
+ ["Delete Footnote" Footnote-delete-footnote]
+ ["Goto Footnote" Footnote-goto-footnote]
+ ["Back to Message" Footnote-back-to-message]
+ ["Renumber Footnotes" Footnote-renumber-footnotes]
+ "--"
+ ["Set Footnote Style" Footnote-set-style]
+ ["Cycle Footnote Style" Footnote-cycle-style]
+ ))
+)
(provide 'footnote)
cvs server: Diffing xemacs-packages/forms
cvs server: Diffing xemacs-packages/fortran-modes
cvs server: Diffing xemacs-packages/frame-icon
cvs server: Diffing xemacs-packages/frame-icon/etc
cvs server: Diffing xemacs-packages/fsf-compat
cvs server: Diffing xemacs-packages/games
Index: xemacs-packages/games/gamegrid.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/gamegrid.el,v
retrieving revision 1.5
diff -u -p -r1.5 gamegrid.el
--- xemacs-packages/games/gamegrid.el 2003/06/14 18:48:26 1.5
+++ xemacs-packages/games/gamegrid.el 2005/01/31 20:55:58
＠＠ -1,4 +1,4 ＠＠
-;;; gamegrid.el -- Library for implementing grid-based games on Emacs.
+;;; gamegrid.el --- Library for implementing grid-based games on Emacs.
;; Copyright (C) 1998 Free Software Foundation, Inc.
＠＠ -34,6 +34,10 ＠＠
;; Modified: 2003-06-14, update email address, remove URL
;; Tested with XEmacs 20.3/4/5 and Emacs 19.34
+
+(defgroup gamegrid nil
+ "Library for implementing grid-based games on Emacs."
+:group 'games)
(eval-when-compile
(require 'cl))
Index: xemacs-packages/games/snake.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/snake.el,v
retrieving revision 1.4
diff -u -p -r1.4 snake.el
--- xemacs-packages/games/snake.el 2003/06/14 18:48:26 1.4
+++ xemacs-packages/games/snake.el 2005/01/31 20:55:58
＠＠ -40,6 +40,10 ＠＠
(require 'gamegrid)
+(defgroup snake nil
+ "Implementation of Snake for Emacs"
+:group 'games)
+
;; ;;;;;;;;;;;;; customization variables ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(defvar snake-use-glyphs t
Index: xemacs-packages/games/sokoban.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/sokoban.el,v
retrieving revision 1.7
diff -u -p -r1.7 sokoban.el
--- xemacs-packages/games/sokoban.el 2003/06/14 18:48:27 1.7
+++ xemacs-packages/games/sokoban.el 2005/01/31 20:55:58
＠＠ -1,4 +1,4 ＠＠
-;;; sokoban.el -- Implementation of Sokoban for Emacs.
+;;; sokoban.el --- Implementation of Sokoban for Emacs.
;; Copyright (C) 1998 Free Software Foundation, Inc.
＠＠ -50,6 +50,10 ＠＠
;; The levels and some of the pixmaps were
;; taken directly from XSokoban
+(defgroup sokoban nil
+ "Implementation of Sokoban for Emacs."
+:group 'games)
+
(eval-when-compile
(require 'cl))
＠＠ -754,6 +758,16 ＠＠ sokoban-mode keybindings:
(gamegrid-kill-timer)
(sokoban-mode)
(sokoban-start-game))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'sokoban
+ "Not documented."
+:group 'games
+:commands
+ '(["Sokoban" sokoban]))
+)
(provide 'sokoban)
Index: xemacs-packages/games/tetris.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/tetris.el,v
retrieving revision 1.4
diff -u -p -r1.4 tetris.el
--- xemacs-packages/games/tetris.el 2003/06/14 18:48:27 1.4
+++ xemacs-packages/games/tetris.el 2005/01/31 20:55:59
＠＠ -1,4 +1,4 ＠＠
-;;; tetris.el -- Implementation of Tetris for Emacs.
+;;; tetris.el --- Implementation of Tetris for Emacs.
;; Copyright (C) 1998 Free Software Foundation, Inc.
＠＠ -59,6 +59,10 ＠＠
;; Tested with XEmacs 20.3/4/5, 21.4.13 and Emacs 19.34
+(defgroup tetris nil
+ "Implementation of Tetris for Emacs."
+:group 'games)
+
(eval-when-compile
(require 'cl))
＠＠ -806,6 +810,16 ＠＠ tetris-mode keybindings:
(gamegrid-kill-timer)
(tetris-mode)
(tetris-start-game))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'tetris
+ "Not documented."
+:group 'games
+:commands
+ '(["Tetris" tetris]))
+)
(provide 'tetris)
cvs server: Diffing xemacs-packages/general-docs
cvs server: Diffing xemacs-packages/general-docs/texi
cvs server: Diffing xemacs-packages/general-docs/texi/packages
cvs server: Diffing xemacs-packages/general-docs/texi/xemacs
cvs server: Diffing xemacs-packages/gnats
cvs server: Diffing xemacs-packages/gnats/etc
cvs server: Diffing xemacs-packages/gnats/lib-src
cvs server: Diffing xemacs-packages/gnats/texi
cvs server: Diffing xemacs-packages/gnus
cvs server: Diffing xemacs-packages/gnus/etc
cvs server: Diffing xemacs-packages/gnus/etc/gnus
cvs server: Diffing xemacs-packages/gnus/etc/smilies
cvs server: Diffing xemacs-packages/gnus/etc/sounds
cvs server: Diffing xemacs-packages/gnus/gnus
cvs server: xemacs-packages/gnus/gnus/make.bat is a new entry, no comparison available
cvs server: Diffing xemacs-packages/gnus/gnus/lisp
cvs server: xemacs-packages/gnus/gnus/lisp/gnus.el is a new entry, no comparison available
cvs server: Diffing xemacs-packages/gnus/gnus/texi
cvs server: Diffing xemacs-packages/gnus/lisp
cvs server: Diffing xemacs-packages/gnus/texi
cvs server: Diffing xemacs-packages/gnus/texi/etc
cvs server: Diffing xemacs-packages/gnus/texi/herds
cvs server: Diffing xemacs-packages/gnus/texi/misc
cvs server: Diffing xemacs-packages/gnus/texi/picons
cvs server: Diffing xemacs-packages/gnus/texi/ps
cvs server: Diffing xemacs-packages/gnus/texi/screen
cvs server: Diffing xemacs-packages/gnus/texi/smilies
cvs server: Diffing xemacs-packages/gnus/texi/xface
cvs server: Diffing xemacs-packages/haskell-mode
cvs server: Diffing xemacs-packages/hm--html-menus
cvs server: Diffing xemacs-packages/hm--html-menus/etc
cvs server: Diffing xemacs-packages/hm--html-menus/etc/idd
cvs server: Diffing xemacs-packages/hm--html-menus/etc/templates
cvs server: Diffing xemacs-packages/hyperbole
cvs server: Diffing xemacs-packages/hyperbole/kotl
cvs server: Diffing xemacs-packages/hyperbole/man
cvs server: Diffing xemacs-packages/ibuffer
cvs server: Diffing xemacs-packages/idlwave
cvs server: Diffing xemacs-packages/igrep
cvs server: Diffing xemacs-packages/ilisp
cvs server: Diffing xemacs-packages/ilisp/docs
cvs server: Diffing xemacs-packages/ilisp/extra
cvs server: Diffing xemacs-packages/ilisp/pictures
cvs server: Diffing xemacs-packages/ispell
Index: xemacs-packages/ispell/ispell.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ispell/ispell.el,v
retrieving revision 1.21
diff -u -p -r1.21 ispell.el
--- xemacs-packages/ispell/ispell.el 2005/01/23 13:50:55 1.21
+++ xemacs-packages/ispell/ispell.el 2005/01/31 20:56:03
＠＠ -3530,6 +3530,22 ＠＠ Both should not be used to define a buff
(add-to-list 'debug-ignored-errors "^No word found to check!$")
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'ispell
+ "Not documented."
+:short-doc "Spell-Check"
+:group 'editing
+:commands
+ '(["%_Buffer" ispell-buffer]
+ "---"
+ ["%_Word" ispell-word]
+ ["%_Complete Word" ispell-complete-word]
+ ["%_Region" ispell-region :active (region-active-p)]
+ ))
+)
+
(provide 'ispell)
cvs server: Diffing xemacs-packages/jde
cvs server: Diffing xemacs-packages/jde/doc
cvs server: Diffing xemacs-packages/jde/doc/html
cvs server: Diffing xemacs-packages/jde/doc/html/bsh-ug
cvs server: Diffing xemacs-packages/jde/doc/html/bsh-ug/images
cvs server: Diffing xemacs-packages/jde/doc/html/css
cvs server: Diffing xemacs-packages/jde/doc/html/jdb-ug
cvs server: Diffing xemacs-packages/jde/doc/html/jdb-ug/images
cvs server: Diffing xemacs-packages/jde/doc/html/jde-ug
cvs server: Diffing xemacs-packages/jde/doc/html/jde-ug/images
cvs server: Diffing xemacs-packages/jde/doc/html/jdebug-ug
cvs server: Diffing xemacs-packages/jde/doc/html/jdebug-ug/images
cvs server: Diffing xemacs-packages/jde/doc/src
cvs server: Diffing xemacs-packages/jde/doc/src/css
cvs server: Diffing xemacs-packages/jde/doc/src/jde-ug
cvs server: Diffing xemacs-packages/jde/doc/src/jde-ug/images
cvs server: Diffing xemacs-packages/jde/doc/src/styles
cvs server: Diffing xemacs-packages/jde/doc/src/styles/html
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl/au
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl/img
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl/txt
cvs server: Diffing xemacs-packages/jde/java
cvs server: Diffing xemacs-packages/jde/java/bsh-commands
cvs server: Diffing xemacs-packages/jde/java/bsh-commands/bsh
cvs server: Diffing xemacs-packages/jde/java/bsh-commands/bsh/commands
cvs server: Diffing xemacs-packages/jde/java/doc
cvs server: Diffing xemacs-packages/jde/java/doc/jde
cvs server: Diffing xemacs-packages/jde/java/doc/jde/debugger
cvs server: Diffing xemacs-packages/jde/java/lib
cvs server: Diffing xemacs-packages/jde/java/src
cvs server: Diffing xemacs-packages/jde/java/src/jde
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger/command
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger/expr
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger/spec
cvs server: Diffing xemacs-packages/jde/java/src/jde/parser
cvs server: Diffing xemacs-packages/jde/java/src/jde/util
cvs server: Diffing xemacs-packages/jde/java/src/jde/wizards
cvs server: Diffing xemacs-packages/jde/lisp
cvs server: Diffing xemacs-packages/liece
cvs server: Diffing xemacs-packages/liece/dcc
cvs server: Diffing xemacs-packages/liece/doc
cvs server: Diffing xemacs-packages/liece/etc
cvs server: Diffing xemacs-packages/liece/etc/icons
cvs server: Diffing xemacs-packages/liece/etc/po
cvs server: Diffing xemacs-packages/liece/etc/styles
cvs server: Diffing xemacs-packages/liece/lisp
cvs server: Diffing xemacs-packages/mail-lib
cvs server: Diffing xemacs-packages/mailcrypt
cvs server: Diffing xemacs-packages/mew
cvs server: Diffing xemacs-packages/mew/mew
cvs server: Diffing xemacs-packages/mew/mew/OS2
cvs server: Diffing xemacs-packages/mew/mew/Win32
cvs server: Diffing xemacs-packages/mew/mew/bin
cvs server: Diffing xemacs-packages/mew/mew/contrib
cvs server: Diffing xemacs-packages/mew/mew/etc
cvs server: Diffing xemacs-packages/mew/mew/etc/etc
cvs server: Diffing xemacs-packages/mew/mew/info
cvs server: Diffing xemacs-packages/mh-e
Index: xemacs-packages/mh-e/mh-e.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mh-e/mh-e.el,v
retrieving revision 1.7
diff -u -p -r1.7 mh-e.el
--- xemacs-packages/mh-e/mh-e.el 2003/09/02 23:39:26 1.7
+++ xemacs-packages/mh-e/mh-e.el 2005/01/31 20:56:04
＠＠ -2504,6 +2504,16 ＠＠ well.")
"^There is no other window$"))
(add-to-list 'debug-ignored-errors mess))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'mh
+ "Not documented."
+:group 'internet
+:commands
+ '(["Read Mail (MH)..." (mh-rmail t)]))
+)
+
;;; Local Variables:
;;; indent-tabs-mode: nil
;;; sentence-end-double-space: nil
cvs server: Diffing xemacs-packages/mine
Index: xemacs-packages/mine/xmine.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mine/xmine.el,v
retrieving revision 1.5
diff -u -p -r1.5 xmine.el
--- xemacs-packages/mine/xmine.el 2000/10/06 09:20:18 1.5
+++ xemacs-packages/mine/xmine.el 2005/01/31 20:56:04
＠＠ -865,5 +865,16 ＠＠ We set up the XMine buffer, set up the k
(if ext (xmine-select-button ext)
(xmine-select-button (xmine-field-button-at xmine-width y)))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'xmine
+ "Not documented."
+:short-doc "Mine game"
+:group 'games
+:commands
+ '(["Mine Game" xmine]))
+)
+
(provide 'xmine)
cvs server: Diffing xemacs-packages/mine/etc
cvs server: Diffing xemacs-packages/misc-games
Index: xemacs-packages/misc-games/NeXTify.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/NeXTify.el,v
retrieving revision 1.2
diff -u -p -r1.2 NeXTify.el
--- xemacs-packages/misc-games/NeXTify.el 1999/11/27 20:49:55 1.2
+++ xemacs-packages/misc-games/NeXTify.el 2005/01/31 20:56:04
＠＠ -28,6 +28,10 ＠＠
;;; Code:
+(defgroup NeXTify nil
+ "Character insertion variation"
+:group 'games)
+
(defun SeLF-insert-command (arg)
"Insert the character you TyPE.
Whichever character you TyPE to run ThIS command is inserted."
Index: xemacs-packages/misc-games/advocacy.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/advocacy.el,v
retrieving revision 1.4
diff -u -p -r1.4 advocacy.el
--- xemacs-packages/misc-games/advocacy.el 1999/11/27 20:49:55 1.4
+++ xemacs-packages/misc-games/advocacy.el 2005/01/31 20:56:04
＠＠ -1,4 +1,4 ＠＠
-;;; advocacy.el -- blatant XEmacs self promotion
+;;; advocacy.el --- blatant XEmacs self promotion
;; Copyright (C) 1996, 1997 Free Software Foundation, Inc.
;; Copyright (C) 1996 Chuck Thompson <cthomp(a)xemacs.org>
＠＠ -20,6 +20,10 ＠＠
;; along with XEmacs; see the file COPYING. If not, write to the
;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
;; Boston, MA 02111-1307, USA.
+
+(defgroup advocacy nil
+ "blatant XEmacs self promotion"
+:group 'games)
;;;###autoload
(defvar xemacs-praise-sound-file "im_so_happy"
Index: xemacs-packages/misc-games/blackbox.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/blackbox.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 blackbox.el
--- xemacs-packages/misc-games/blackbox.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/blackbox.el 2005/01/31 20:56:05
＠＠ -70,6 +70,10 ＠＠
;;; Code:
+(defgroup blackbox nil
+ "blackbox game in Emacs Lisp"
+:group 'games)
+
(defvar blackbox-mode-map nil "")
(if blackbox-mode-map
Index: xemacs-packages/misc-games/conx.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/conx.el,v
retrieving revision 1.2
diff -u -p -r1.2 conx.el
--- xemacs-packages/misc-games/conx.el 1999/11/27 20:49:55 1.2
+++ xemacs-packages/misc-games/conx.el 2005/01/31 20:56:05
＠＠ -70,6 +70,10 ＠＠
;;; o It could stand to be faster...
;;; Code:
+(defgroup conx nil
+ "Yet another dissociater"
+:group 'games)
+
(defconst conx-version "1.6, 6-may-94.")
(defvar conx-bounce 10) ; 1/x
Index: xemacs-packages/misc-games/decipher.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/decipher.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 decipher.el
--- xemacs-packages/misc-games/decipher.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/decipher.el 2005/01/31 20:56:05
＠＠ -93,6 +93,10 ＠＠
(eval-when-compile
(require 'cl))
+(defgroup decipher nil
+ "Cryptanalyze monoalphabetic substitution ciphers"
+:group 'games)
+
(defvar decipher-force-uppercase t
"*Non-nil means to convert ciphertext to uppercase.
Nil means the case of the ciphertext is preserved.
Index: xemacs-packages/misc-games/dissociate.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/dissociate.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 dissociate.el
--- xemacs-packages/misc-games/dissociate.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/dissociate.el 2005/01/31 20:56:05
＠＠ -31,6 +31,10 ＠＠
;;; Code:
+(defgroup dissociate nil
+ "scramble text amusingly for Emacs."
+:group 'games)
+
;;;###autoload
(defun dissociated-press (&optional arg)
"Dissociate the text of the current buffer.
Index: xemacs-packages/misc-games/doctor.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/doctor.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 doctor.el
--- xemacs-packages/misc-games/doctor.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/doctor.el 2005/01/31 20:56:06
＠＠ -44,6 +44,10 ＠＠
;;; Code:
+(defgroup doctor nil
+ "psychological help for frustrated users."
+:group 'games)
+
(defun doctor-cadr (x) (car (cdr x)))
(defun doctor-caddr (x) (car (cdr (cdr x))))
(defun doctor-cddr (x) (cdr (cdr x)))
＠＠ -1637,5 +1641,17 ＠＠ Hack on previous word, setting global va
(interactive)
(insert "Mein fuehrer!!\n")
(doctor-read-print))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'doctor
+ "Not documented."
+:group 'games
+:commands
+ '(["%_Psychoanalyst" doctor]))
+)
+
+
;;; doctor.el ends here
Index: xemacs-packages/misc-games/dunnet.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/dunnet.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 dunnet.el
--- xemacs-packages/misc-games/dunnet.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/dunnet.el 2005/01/31 20:56:07
＠＠ -36,6 +36,10 ＠＠
;;; be writable by all.
+(defgroup dunnet nil
+ "Text adventure for Emacs"
+:group 'games)
+
(defvar dun-log-file "/usr/local/dunnet.score"
"Name of file to store score information for dunnet.")
＠＠ -3336,5 +3340,15 ＠＠ File not found")))
(dun-mprinc "\n")
(setq dun-batch-mode t)
(dun-batch-loop))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'dunnet
+ "Not documented."
+:group 'games
+:commands
+ '(["Dunnet (Adventure)" dunnet]))
+)
;;; dunnet.el ends here
Index: xemacs-packages/misc-games/flame.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/flame.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 flame.el
--- xemacs-packages/misc-games/flame.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/flame.el 2005/01/31 20:56:07
＠＠ -40,6 +40,11 ＠＠
;;;
;;; Code:
+
+(defgroup flame nil
+ "Automated insults"
+:group 'games)
+
(random t)
(defvar sentence
＠＠ -338,5 +343,15 ＠＠
(flame2 (if (= (random 2) 0) 2 1))
(sit-for 0)
(doctor-ret-or-read 1)))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'flame
+ "Not documented."
+:group 'games
+:commands
+ '(["Random Flames" flame]))
+)
;;; flame.el ends here
Index: xemacs-packages/misc-games/gomoku.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/gomoku.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 gomoku.el
--- xemacs-packages/misc-games/gomoku.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/gomoku.el 2005/01/31 20:56:07
＠＠ -74,6 +74,9 ＠＠
;;; Code:
+(defgroup gomoku nil
+ "Gomoku game between you and Emacs"
+:group 'games)
;;;
;;; GOMOKU MODE AND KEYMAP.
;;;
Index: xemacs-packages/misc-games/hanoi.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/hanoi.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 hanoi.el
--- xemacs-packages/misc-games/hanoi.el 1998/01/14 06:30:54 1.1.1.1
+++ xemacs-packages/misc-games/hanoi.el 2005/01/31 20:56:07
＠＠ -58,6 +58,10 ＠＠
;;; Code:
+(defgroup hanoi nil
+ "towers of hanoi in GNUmacs"
+:group 'games)
+
;;;
;;; hanoi-topos - direct cursor addressing
;;;
＠＠ -243,6 +247,16 ＠＠
(progn
(backward-char (/ (+ len 1) 2))
(delete-char 1) (insert ?\|))))))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'hanoi
+ "Not documented."
+:group 'games
+:commands
+ '(["Towers of Hanoi" hanoi]))
+)
(provide 'hanoi)
Index: xemacs-packages/misc-games/life.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/life.el,v
retrieving revision 1.2
diff -u -p -r1.2 life.el
--- xemacs-packages/misc-games/life.el 2000/11/18 04:27:37 1.2
+++ xemacs-packages/misc-games/life.el 2005/01/31 20:56:08
＠＠ -32,6 +32,10 ＠＠
;;; Code:
+(defgroup life nil
+ "John Horton Conway's `Life' game for GNU Emacs"
+:group 'games)
+
(defconst life-patterns
[("＠＠＠" " ＠＠" "＠＠＠")
("＠＠＠ ＠＠＠" "＠＠ ＠＠ " "＠＠＠ ＠＠＠")
＠＠ -283,6 +287,16 ＠＠ generations (this defaults to 1)."
;; XEmacs change
(define-error 'life-extinct "All life has perished" 'quit)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'life
+ "Not documented."
+:group 'games
+:commands
+ '(["Game of Life" life]))
+)
(provide 'life)
Index: xemacs-packages/misc-games/morse.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/morse.el,v
retrieving revision 1.2
diff -u -p -r1.2 morse.el
--- xemacs-packages/misc-games/morse.el 2002/11/18 22:11:45 1.2
+++ xemacs-packages/misc-games/morse.el 2005/01/31 20:56:08
＠＠ -24,10 +24,14 ＠＠
;;; Commentary:
-;; Converts text to Morse code and back with M-x morese-region and
+;; Converts text to Morse code and back with M-x morse-region and
;; M-x unmorse-region (though Morse code is no longer official :-().
;;; Code:
+
+(defgroup morse nil
+ "convert text to morse code and back"
+:group 'games)
(defvar morse-code '(("a" . ".-")
("b" . "-...")
Index: xemacs-packages/misc-games/mpuz.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/mpuz.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 mpuz.el
--- xemacs-packages/misc-games/mpuz.el 1998/01/14 06:30:54 1.1.1.1
+++ xemacs-packages/misc-games/mpuz.el 2005/01/31 20:56:08
＠＠ -33,6 +33,10 ＠＠
;;; Code:
+(defgroup mpuz nil
+ "multiplication puzzle for XEmacs"
+:group 'games)
+
(random t) ; randomize
(defvar mpuz-silent nil
＠＠ -441,5 +445,15 ＠＠ You may abort a game by typing \\<mpuz-m
(or (mpuz-digit-solved-p digit)
(setq list (cons digit list))))
(mapcar 'mpuz-correct-guess list)))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'mpuz
+ "Not documented."
+:group 'games
+:commands
+ '(["Multiplication Puzzle" mpuz]))
+)
;;; mpuz.el ends here
Index: xemacs-packages/misc-games/rot13.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/rot13.el,v
retrieving revision 1.2
diff -u -p -r1.2 rot13.el
--- xemacs-packages/misc-games/rot13.el 2000/09/25 03:16:51 1.2
+++ xemacs-packages/misc-games/rot13.el 2005/01/31 20:56:08
＠＠ -35,6 +35,10 ＠＠
;;; Code:
+(defgroup rot13 nil
+ "display a buffer in rot13."
+:group 'games)
+
(defvar rot13-display-table
(let ((i -1)
(a (char-to-int ?a))
Index: xemacs-packages/misc-games/studly.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/studly.el,v
retrieving revision 1.2
diff -u -p -r1.2 studly.el
--- xemacs-packages/misc-games/studly.el 2003/09/20 20:26:31 1.2
+++ xemacs-packages/misc-games/studly.el 2005/01/31 20:56:08
＠＠ -32,6 +32,10 ＠＠
;;; Code:
+(defgroup studly nil
+ "StudlyCaps (tm)(r)(c)(xxx)"
+:group 'games)
+
(defun studlify-region (begin end)
"Studlify-case the region"
(interactive "*r")
cvs server: Diffing xemacs-packages/mmm-mode
cvs server: Diffing xemacs-packages/net-utils
cvs server: Diffing xemacs-packages/ocaml
cvs server: Diffing xemacs-packages/oo-browser
cvs server: Diffing xemacs-packages/oo-browser/man
cvs server: Diffing xemacs-packages/oo-browser/man/im
cvs server: Diffing xemacs-packages/oo-browser/tree-w32
cvs server: Diffing xemacs-packages/oo-browser/tree-x
cvs server: Diffing xemacs-packages/os-utils
Index: xemacs-packages/os-utils/jka-compr.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/os-utils/jka-compr.el,v
retrieving revision 1.9
diff -u -p -r1.9 jka-compr.el
--- xemacs-packages/os-utils/jka-compr.el 2003/05/30 12:55:07 1.9
+++ xemacs-packages/os-utils/jka-compr.el 2005/01/31 20:56:08
＠＠ -983,6 +983,22 ＠＠ The return value is the entry in `file-n
;; No no no no!
;(jka-compr-install)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'jka-compr
+ "This package implements low-level support for reading, writing,
+and loading compressed files. It hooks into the low-level file
+I/O functions (including write-region and insert-file-contents) so
+that they automatically compress or uncompress a file if the file
+appears to need it (based on the extension of the file name).
+Packages like Rmail, VM, GNUS, and Info should be able to work
+with compressed files without modification."
+:short-doc "Transparently handle compressed files"
+:group 'files
+:enable #'jka-compr-install
+:disable #'jka-compr-uninstall)
+)
(provide 'jka-compr)
cvs server: Diffing xemacs-packages/pc
Index: xemacs-packages/pcl-cvs/pcl-cvs-defs.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/pcl-cvs/pcl-cvs-defs.el,v
retrieving revision 2.4
diff -u -p -r2.4 pcl-cvs-defs.el
--- xemacs-packages/pcl-cvs/pcl-cvs-defs.el 2002/06/24 22:06:46 2.4
+++ xemacs-packages/pcl-cvs/pcl-cvs-defs.el 2005/01/31 20:56:09
＠＠ -466,7 +466,10 ＠＠ It is expected to call the function.")
;;;###autoload
(if (progn (condition-case () (require 'easymenu) (error nil))
- (fboundp 'easy-menu-add-item))
+ (and (fboundp 'easy-menu-add-item)
+ ;; Packages under XEmacs 21.5+ may not directly modify the
+ ;; menubar.
+ (not (fboundp 'define-behavior-group))))
(easy-menu-add-item nil '("tools")
'("PCL CVS"
["Update Directory" cvs-update t]
Index: xemacs-packages/pcl-cvs/pcl-cvs.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/pcl-cvs/pcl-cvs.el,v
retrieving revision 2.41
diff -u -p -r2.41 pcl-cvs.el
--- xemacs-packages/pcl-cvs/pcl-cvs.el 2002/01/26 22:27:31 2.41
+++ xemacs-packages/pcl-cvs/pcl-cvs.el 2005/01/31 20:56:10
＠＠ -2112,6 +2112,20 ＠＠ Anything else means to do it only if the
(when (eq major-mode 'cvs-mode)
(setq ad-return-value list-buffers-directory)))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'pcl-cvs
+ "Not documented."
+:short-doc "PCL CVS"
+:group 'files
+:commands
+ '(["Update Directory" cvs-update t]
+ ["Examine Directory" cvs-examine t]
+ ["Status Directory" cvs-status t]
+ ["Checkout Module" cvs-checkout t]))
+)
+
;; provide this package
(run-hooks 'pcl-cvs-load-hook)
cvs server: Diffing xemacs-packages/pcomplete
cvs server: Diffing xemacs-packages/perl-modes
cvs server: Diffing xemacs-packages/pgg
cvs server: Diffing xemacs-packages/prog-modes
cvs server: Diffing xemacs-packages/ps-print
Index: xemacs-packages/ps-print/ps-mule.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ps-print/ps-mule.el,v
retrieving revision 1.4
diff -u -p -r1.4 ps-mule.el
--- xemacs-packages/ps-print/ps-mule.el 2002/07/30 12:40:40 1.4
+++ xemacs-packages/ps-print/ps-mule.el 2005/01/31 20:56:10
＠＠ -298,6 +298,7 ＠＠ font family.
See also the variable `ps-font-info-database'.")
+;;;###custom-define
(defconst ps-mule-font-info-database-latin
'((latin-iso8859-1
(normal nil nil iso-8859-1)))
cvs server: Diffing xemacs-packages/ps-print/etc
cvs server: Diffing xemacs-packages/ps-print/etc/ps-print
cvs server: Diffing xemacs-packages/ps-print-nomule
cvs server: Diffing xemacs-packages/psgml
Index: xemacs-packages/psgml/psgml-html.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/psgml/psgml-html.el,v
retrieving revision 1.18
diff -u -p -r1.18 psgml-html.el
--- xemacs-packages/psgml/psgml-html.el 2003/08/29 08:19:58 1.18
+++ xemacs-packages/psgml/psgml-html.el 2005/01/31 20:56:12
＠＠ -265,24 +265,8 ＠＠ More specifically:
sgml-omittag t
sgml-shorttag t)
- ;; font-lock setup for various emacsen: XEmacs, Emacs 19.29+, Emacs <19.29.
- ;; By Ulrik Dickow <dickow(a)nbi.dk>. (Last update: 05-Sep-1995).
- (cond (running-xemacs ; XEmacs/Lucid
- (put major-mode 'font-lock-keywords-case-fold-search t))
- ;; XEmacs (19.13, at least) guesses the rest correctly.
- ;; If any older XEmacsen don't, then tell me.
- ;;
- ((string-lessp "19.28.89" emacs-version) ; Emacs 19.29 and later
- (make-local-variable 'font-lock-defaults)
- (setq font-lock-defaults '(html-font-lock-keywords t t)))
- ;;
- (t ; Emacs 19.28 and older
- (make-local-variable 'font-lock-keywords-case-fold-search)
- (make-local-variable 'font-lock-keywords)
- (make-local-variable 'font-lock-no-comments)
- (setq font-lock-keywords-case-fold-search t)
- (setq font-lock-keywords html-font-lock-keywords)
- (setq font-lock-no-comments t)))
+ (make-local-variable 'font-lock-defaults)
+ (setq font-lock-defaults '(html-font-lock-keywords t t))
(if html-helper-do-write-file-hooks
(add-hook 'local-write-file-hooks 'html-helper-update-timestamp))
cvs server: Diffing xemacs-packages/psgml-dtds
cvs server: Diffing xemacs-packages/psgml-dtds/etc
cvs server: Diffing xemacs-packages/psgml-dtds/etc/ISO_8879-1986
cvs server: Diffing xemacs-packages/psgml-dtds/etc/ISO_8879-1986/entities
cvs server: Diffing xemacs-packages/psgml-dtds/etc/cdtd
cvs server: Diffing xemacs-packages/python-modes
cvs server: Diffing xemacs-packages/reftex
cvs server: Diffing xemacs-packages/riece
cvs server: Diffing xemacs-packages/riece/doc
cvs server: Diffing xemacs-packages/riece/lisp
cvs server: Diffing xemacs-packages/riece/lisp/test
cvs server: Diffing xemacs-packages/rmail
cvs server: Diffing xemacs-packages/rmail/etc
cvs server: Diffing xemacs-packages/ruby-modes
cvs server: Diffing xemacs-packages/sasl
cvs server: Diffing xemacs-packages/scheme
cvs server: Diffing xemacs-packages/semantic
cvs server: Diffing xemacs-packages/sgml
cvs server: Diffing xemacs-packages/sh-script
cvs server: Diffing xemacs-packages/sieve
cvs server: Diffing xemacs-packages/slider
cvs server: Diffing xemacs-packages/slider/etc
cvs server: Diffing xemacs-packages/sml-mode
cvs server: Diffing xemacs-packages/sounds-au
cvs server: Diffing xemacs-packages/sounds-wav
cvs server: Diffing xemacs-packages/speedbar
cvs server: Diffing xemacs-packages/strokes
cvs server: Diffing xemacs-packages/supercite
cvs server: Diffing xemacs-packages/texinfo
cvs server: Diffing xemacs-packages/text-modes
Index: xemacs-packages/text-modes/filladapt.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/text-modes/filladapt.el,v
retrieving revision 1.5
diff -u -p -r1.5 filladapt.el
--- xemacs-packages/text-modes/filladapt.el 2002/10/29 12:27:58 1.5
+++ xemacs-packages/text-modes/filladapt.el 2005/01/31 20:56:13
＠＠ -986,3 +986,41 ＠＠ See filladapt-adapt."
(while ei-list
(filladapt-set-extent-endpoints (car ei-list) 1 1)
(setq ei-list (cdr ei-list))))))))))
+
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'filladapt
+ "These functions enhance the default behavior of Emacs' Auto Fill
+mode and the commands `fill-paragraph', `lisp-fill-paragraph',
+`fill-region-as-paragraph' and `fill-region'.
+
+The chief improvement is that the beginning of a line to be
+filled is examined and, based on information gathered, an
+appropriate value for fill-prefix is constructed. Also the
+boundaries of the current paragraph are located. This occurs
+only if the fill prefix is not already non-nil.
+
+The net result of this is that blurbs of text that are offset
+from left margin by asterisks, dashes, and/or spaces, numbered
+examples, included text from USENET news articles, etc. are
+generally filled correctly with no fuss."
+:short-doc "Adaptive (smart) filling"
+:require 'filladapt
+:group 'editing
+:enable #'(lambda ()
+ (setq-default filladapt-mode t)
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (unless filladapt-mode
+ (filladapt-mode 1))))
+ (buffer-list)))
+:disable #'(lambda ()
+ (setq-default filladapt-mode nil)
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (when filladapt-mode
+ (filladapt-mode -1))))
+ (buffer-list))))
+)
\ No newline at end of file
Index: xemacs-packages/text-modes/flyspell.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/text-modes/flyspell.el,v
retrieving revision 1.14
diff -u -p -r1.14 flyspell.el
--- xemacs-packages/text-modes/flyspell.el 2003/01/03 21:15:12 1.14
+++ xemacs-packages/text-modes/flyspell.el 2005/01/31 20:56:13
＠＠ -57,6 +57,7 ＠＠
;*---------------------------------------------------------------------*/
;* Which emacs are we currently running */
;*---------------------------------------------------------------------*/
+;;;###custom-define
(defvar flyspell-emacs
(cond
((string-match "XEmacs" emacs-version)
cvs server: Diffing xemacs-packages/textools
cvs server: Diffing xemacs-packages/time
cvs server: Diffing xemacs-packages/time/etc
cvs server: Diffing xemacs-packages/tm
cvs server: Diffing xemacs-packages/tm/lib-src
cvs server: Diffing xemacs-packages/tm/texi
cvs server: Diffing xemacs-packages/tooltalk
cvs server: Diffing xemacs-packages/tpu
cvs server: Diffing xemacs-packages/tramp
cvs server: Diffing xemacs-packages/tramp/lisp
cvs server: Diffing xemacs-packages/tramp/test
cvs server: Diffing xemacs-packages/tramp/texi
cvs server: Diffing xemacs-packages/vc
Index: xemacs-packages/vc/vc-hooks.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/vc/vc-hooks.el,v
retrieving revision 1.12
diff -u -p -r1.12 vc-hooks.el
--- xemacs-packages/vc/vc-hooks.el 2003/10/27 15:09:55 1.12
+++ xemacs-packages/vc/vc-hooks.el 2005/01/31 20:56:14
＠＠ -1241,6 +1241,7 ＠＠ Returns t if checkout was successful, ni
;(put 'vc-toggle-read-only 'menu-enable 'vc-mode)
;(put 'vc-register 'menu-enable '(and buffer-file-name (not vc-mode)))
+;;;###autoload
(defconst vc-menu
'("VC"
:filter vc-menu-filter
＠＠ -1318,6 +1319,7 ＠＠ Returns t if checkout was successful, ni
result))
(and (featurep 'menubar)
+ (not (fboundp 'define-behavior-group))
current-menubar
(car (find-menu-item current-menubar '("Tools")))
(add-submenu '("Tools") vc-menu "Compare")
＠＠ -1338,7 +1340,8 ＠＠ Returns t if checkout was successful, ni
;;;###autoload
(and (featurep 'menubar)
(featurep 'xemacs)
- (not (or (featurep 'vc-hooks) (featurep 'infodock)))
+ (not (or (featurep 'vc-hooks) (featurep 'infodock)
+ (fboundp 'define-behavior-group)))
current-menubar
(car (find-menu-item current-menubar '("Tools")))
(add-submenu '("Tools")
＠＠ -1346,5 +1349,15 ＠＠ Returns t if checkout was successful, ni
["Load VC" vc-load-vc-hooks t])
"Compare"))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'vc
+ "Not documented."
+:short-doc "VC"
+:group 'files
+:enable 'vc-load-vc-hooks
+:commands (cdr vc-menu))
+)
;;; vc-hooks.el ends here
cvs server: Diffing xemacs-packages/vc-cc
cvs server: Diffing xemacs-packages/vhdl
cvs server: Diffing xemacs-packages/view-process
cvs server: Diffing xemacs-packages/viper
cvs server: Diffing xemacs-packages/viper/etc
cvs server: Diffing xemacs-packages/vm
Index: xemacs-packages/vm/vm-version.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/vm/vm-version.el,v
retrieving revision 1.28
diff -u -p -r1.28 vm-version.el
--- xemacs-packages/vm/vm-version.el 2003/09/03 00:43:45 1.28
+++ xemacs-packages/vm/vm-version.el 2005/01/31 20:56:14
＠＠ -106,5 +106,15 ＠＠
(image-type-available-p type)
(or (featurep type) (eq type 'xbm))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'vm
+ "Not documented."
+:group 'internet
+:commands
+ '(["Read Mail (VM)..." vm]))
+)
+
(provide 'vm)
(provide 'vm-version)
cvs server: Diffing xemacs-packages/vm/etc
cvs server: Diffing xemacs-packages/w3
Index: xemacs-packages/w3/lisp/w3.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/w3/lisp/w3.el,v
retrieving revision 1.7
diff -u -p -r1.7 w3.el
--- xemacs-packages/w3/lisp/w3.el 2000/10/06 09:15:23 1.7
+++ xemacs-packages/w3/lisp/w3.el 2005/01/31 20:56:17
＠＠ -2591,6 +2591,17 ＠＠ Current keymap is:
(run-hooks 'w3-mode-hook)
(widget-setup))))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'w3
+ "Not documented."
+:group 'internet
+:commands
+ '(["Browse the Web" w3]))
+)
+
(require 'mm)
(require 'url)
(require 'w3-parse)
cvs server: Diffing xemacs-packages/w3/texi
cvs server: Diffing xemacs-packages/x-symbol
cvs server: Diffing xemacs-packages/x-symbol/etc
cvs server: Diffing xemacs-packages/x-symbol/fonts
cvs server: Diffing xemacs-packages/x-symbol/lisp
cvs server: Diffing xemacs-packages/x-symbol/man
cvs server: Diffing xemacs-packages/x-symbol/origfonts
cvs server: Diffing xemacs-packages/xemacs-base
Index: xemacs-packages/xemacs-base/compile.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/xemacs-base/compile.el,v
retrieving revision 1.32
diff -u -p -r1.32 compile.el
--- xemacs-packages/xemacs-base/compile.el 2004/06/28 20:19:43 1.32
+++ xemacs-packages/xemacs-base/compile.el 2005/01/31 20:56:19
＠＠ -2345,6 +2345,170 ＠＠ See variable `compilation-parse-errors-f
(substring dir (length parent-expanded)))))
dir)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'grep
+ "See the Emacs user's manual."
+:short-doc "%_Grep"
+:group nil
+:commands
+ '(:filter
+ (lambda (menu)
+ (if (or (not (boundp 'grep-history)) (null grep-history))
+ menu
+ (let ((items
+ (submenu-generate-accelerator-spec
+ (mapcar #'(lambda (label-value)
+ (vector (first label-value)
+ (list 'grep (second label-value))))
+ (Menubar-items-truncate-history
+ grep-history 10 50)))))
+ (append menu '("---") items))))
+ ["%_Grep..." grep :active (fboundp 'grep)]
+ ["%_Kill Grep" kill-compilation
+:active (and (fboundp 'kill-compilation)
+ (fboundp 'compilation-find-buffer)
+ (let ((buffer (condition-case nil
+ (compilation-find-buffer)
+ (error nil))))
+ (and buffer (get-buffer-process buffer))))]
+ "---"
+ ["Grep %_All Files in Current Directory..."
+ grep-all-files-in-current-directory
+:active (fboundp 'grep-all-files-in-current-directory)]
+ ["Grep All Files in Current Directory %_Recursively..."
+ grep-all-files-in-current-directory-and-below
+:active (fboundp 'grep-all-files-in-current-directory-and-below)]
+ "---"
+ ["Grep %_C and C Header Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.[chCH]"
+ ; i wanted to also use *.cc and *.hh.
+ ; see long comment below under Perl.
+ )
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep C Hea%_der Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.[hH]"
+ ; i wanted to also use *.hh.
+ ; see long comment below under Perl.
+ )
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep %_E-Lisp Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.el")
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep %_Perl Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.pl"
+ ; i wanted to use this:
+ ; " *.pl *.pm *.am"
+ ; but grep complains if it can't
+ ; match anything in a glob, and
+ ; that screws other things up.
+ ; perhaps we need to first scan
+ ; each separate glob in the directory
+ ; to see if there are any files in
+ ; that glob, and if not, omit it.
+ )
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep %_HTML Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.*htm*")
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ "---"
+ ["%_Next Match" next-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["Pre%_vious Match" previous-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["%_First Match" first-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["G%_oto Match" compile-goto-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ "---"
+ ["%_Set Grep Command..."
+ (progn
+ (require 'compile)
+ (customize-set-variable
+ 'grep-command
+ (read-shell-command "Default Grep Command: " grep-command)))
+:active (fboundp 'grep)
+ ]
+ ))
+)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'compile
+ "See the Emacs user's manual."
+:short-doc "%_Compile"
+:group nil
+:commands
+ '(:filter
+ (lambda (menu)
+ (if (or (not (boundp 'compile-history)) (null compile-history))
+ menu
+ (let ((items
+ (submenu-generate-accelerator-spec
+ (mapcar #'(lambda (label-value)
+ (vector (first label-value)
+ (list 'compile (second label-value))))
+ (Menubar-items-truncate-history
+ compile-history 10 50)))))
+ (append menu '("---") items))))
+ ["%_Compile..." compile :active (fboundp 'compile)]
+ ["%_Repeat Compilation" recompile :active (fboundp 'recompile)]
+ ["%_Kill Compilation" kill-compilation
+:active (and (fboundp 'kill-compilation)
+ (fboundp 'compilation-find-buffer)
+ (let ((buffer (condition-case nil
+ (compilation-find-buffer)
+ (error nil))))
+ (and buffer (get-buffer-process buffer))))]
+ "---"
+ ["%_Next Error" next-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["Pre%_vious Error" previous-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["%_First Error" first-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["G%_oto Error" compile-goto-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ))
+)
+
+
(provide 'compile)
;;; compile.el ends here
Index: xemacs-packages/xemacs-base/shell.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/xemacs-base/shell.el,v
retrieving revision 1.12
diff -u -p -r1.12 shell.el
--- xemacs-packages/xemacs-base/shell.el 2004/11/23 04:10:54 1.12
+++ xemacs-packages/xemacs-base/shell.el 2005/01/31 20:56:19
＠＠ -1192,6 +1192,22 ＠＠ Returns t if successful."
(message "Directory item: %d" index)
t))))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'shell
+ "See the Emacs user's manual."
+:short-doc "Shell"
+:group 'processes
+:commands
+ '(["%_Shell" shell
+:active (fboundp 'shell)]
+ ["S%_hell Command..." shell-command
+:active (fboundp 'shell-command)]
+ ["Shell Command on %_Region..." shell-command-on-region
+:active (and (fboundp 'shell-command-on-region) (region-exists-p))]))
+)
+
(provide 'shell)
;;; shell.el ends here
cvs server: Diffing xemacs-packages/xemacs-base/etc
cvs server: Diffing xemacs-packages/xemacs-devel
- 2 participants
- 1 comments
[PATCH] Time to consider pending-del default
19 years, 10 months
Ben Wing
Ben Wing
I'd like to get this resolved. I know that Mike Sperber doesn't like this,
but I think we need to come to a vote.
Comments?
Index: xemacs-packages/pc/pending-del.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/pc/pending-del.el,v
retrieving revision 1.10
diff -u -p -r1.10 pending-del.el
--- xemacs-packages/pc/pending-del.el 2002/05/23 04:41:58 1.10
+++ xemacs-packages/pc/pending-del.el 2005/01/31 20:56:08
＠＠ -37,7 +37,7 ＠＠
;;; Code:
;;;###autoload
-(defcustom pending-delete-mode nil
+(defcustom pending-delete-mode t
"Non-nil when Pending Delete mode is enabled. In Pending Delete mode, typed
text replaces the selected region. Normally, you shouldn't modify this
variable by hand, but use the function `pending-delete-mode' instead. However,
- 4 participants
- 3 comments
[COMMIT] Documentation updates
19 years, 10 months
Ben Wing
Ben Wing
NOTE: This patch has been committed.
ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* GETTING.GNU.SOFTWARE: Delete.
* Makefile.in.in (SOURCES):
Delete GETTING.GNU.SOFTWARE from SOURCES.
* PROBLEMS:
Delete reference to check_cygwin_setup.sh.
etc/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
Delete stuff that is irrelevant, mislocated or woefully out-of-date.
* GNU: Delete.
* SERVICE: Delete.
* ORDERS, ORDERS.EUROPE, ORDERS.JAPAN: Delete.
* CHARSETS, CODINGS: Delete.
* DEBUG, LPF, MORE.STUFF, MOTIVATION: Delete.
* aliases.ksh: Delete. (moved to xemacs-builds/steve)
* README.HYPERBOLE, README.OO-BROWSER: Delete.
* chr.png, chrm.png: Move to photos/.
* check_cygwin_setup.sh: Delete.
* gnu.xpm, gnu.xbm, sink.xbm: Delete.
* ms-kermit, ms-kermit-7bit: Delete.
* TERMS: Delete.
* DISTRIB, FTP, MACHINES, MAILINGLISTS, PACKAGES:
Delete and move to FAQ.
* BETA:
Delete and move to man/beta.texi.
* README: Update.
lisp/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* help.el:
* help.el (describe-distribution): Go to appropriate FAQ entry.
* help.el (describe-beta): Go to info file.
* help.el (describe-project): Removed.
man/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* xemacs/help.texi (Misc Help):
Delete references to DISTRIB. Point to FAQ.
* xemacs/new.texi:
Update sample code for version checking.
* xemacs/xemacs.texi (Distrib):
* xemacs/xemacs.texi (Intro):
Delete references to DISTRIB. Point directly to web site.
Update stuff referring to GNU Emacs. Delete references to Win-Emacs.
2005-01-31 Ben Wing <ben(a)xemacs.org>
* Makefile:
* Makefile (info_files):
* Makefile (html_files):
* Makefile (dvi_files):
* Makefile (pdf_files):
* Makefile ($(INFODIR)/beta.info):
Add beta.texi and built files.
* xemacs-faq.texi (Top):
* xemacs-faq.texi (Introduction):
* xemacs-faq.texi (Q1.0.3):
* xemacs-faq.texi (Q1.0.4):
* xemacs-faq.texi (Q1.0.5):
* xemacs-faq.texi (Q1.0.6):
* xemacs-faq.texi (Q1.1.1):
* xemacs-faq.texi (Q1.1.2):
* xemacs-faq.texi (Q1.1.3):
* xemacs-faq.texi (Q1.1.4):
* xemacs-faq.texi (Q1.2.1):
* xemacs-faq.texi (Q1.2.2):
* xemacs-faq.texi (Q1.2.3):
* xemacs-faq.texi (Q1.2.4):
* xemacs-faq.texi (Q1.2.5):
* xemacs-faq.texi (Q1.2.6):
* xemacs-faq.texi (Q1.2.7):
* xemacs-faq.texi (Q1.2.8):
* xemacs-faq.texi (Q1.2.9):
* xemacs-faq.texi (Q1.2.10):
* xemacs-faq.texi (Q1.2.11):
* xemacs-faq.texi (Q1.2.12):
* xemacs-faq.texi (Q1.2.13):
* xemacs-faq.texi (Q1.3.1):
* xemacs-faq.texi (Q1.3.2):
* xemacs-faq.texi (Q1.3.3):
* xemacs-faq.texi (Q1.3.4):
* xemacs-faq.texi (Q1.3.5):
* xemacs-faq.texi (Q1.3.6):
* xemacs-faq.texi (Q1.3.7):
* xemacs-faq.texi (Q1.3.8):
* xemacs-faq.texi (Q1.4.1):
* xemacs-faq.texi (Q1.4.2):
* xemacs-faq.texi (double-word): New.
* xemacs-faq.texi (Q1.4.3):
* xemacs-faq.texi (Q1.4.4):
* xemacs-faq.texi (Q1.4.5):
* xemacs-faq.texi (Q1.5.1):
* xemacs-faq.texi (Q1.5.2):
* xemacs-faq.texi (Q1.5.3):
* xemacs-faq.texi (Q1.6.1):
* xemacs-faq.texi (Q1.6.2):
* xemacs-faq.texi (Q1.6.3):
* xemacs-faq.texi (Q1.6.4):
* xemacs-faq.texi (Q1.6.5):
* xemacs-faq.texi (Q1.6.6):
* xemacs-faq.texi (Q1.7.1):
* xemacs-faq.texi (Q1.8.1):
* xemacs-faq.texi (Q1.8.2):
* xemacs-faq.texi (Q1.8.3):
* xemacs-faq.texi (Q1.8.4):
* xemacs-faq.texi (Q1.8.5):
* xemacs-faq.texi (Q1.8.6):
* xemacs-faq.texi (Q1.8.7):
* xemacs-faq.texi (Q1.8.8):
* xemacs-faq.texi (Q1.8.9):
* xemacs-faq.texi (Q2.2.1):
* xemacs-faq.texi (Q2.2.2):
* xemacs-faq.texi (Q2.4.2):
* xemacs-faq.texi (Advanced):
* xemacs-faq.texi (Q7.0.1):
* xemacs-faq.texi (Q7.0.2):
* xemacs-faq.texi (Q7.0.3):
* xemacs-faq.texi (Q7.0.4):
* xemacs-faq.texi (Q7.0.5):
* xemacs-faq.texi (Q7.0.6):
* xemacs-faq.texi (Q7.1.1):
* xemacs-faq.texi (Q7.1.2):
* xemacs-faq.texi (Q7.1.3):
* xemacs-faq.texi (Q7.1.4):
* xemacs-faq.texi (Q7.1.5):
* xemacs-faq.texi (Q7.1.6):
* xemacs-faq.texi (Q7.1.7):
* xemacs-faq.texi (Q7.1.8):
* xemacs-faq.texi (Q7.1.9):
* xemacs-faq.texi (Q7.1.10):
* xemacs-faq.texi (Q7.1.11):
* xemacs-faq.texi (Q7.2.1):
* xemacs-faq.texi (Q7.2.2):
* xemacs-faq.texi (Q7.2.3):
* xemacs-faq.texi (Other Packages):
* xemacs-faq.texi (Current Events):
* xemacs-faq.texi (Legacy Versions):
Major overhaul of section 1. Add mailing list info, update
downloading info, add info on CVS, etc.
nt/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* xemacs.mak (install):
Also copy BUGS, README, COPYING and Installation.
docs-misc source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: nt/xemacs.mak man/xemacs/xemacs.texi man/xemacs/new.texi man/xemacs/help.texi man/xemacs-faq.texi man/Makefile lisp/help.el etc/README PROBLEMS Makefile.in.in
cvs server: Diffing .
Index: Makefile.in.in
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/Makefile.in.in,v
retrieving revision 1.23
diff -u -p -r1.23 Makefile.in.in
--- Makefile.in.in 2004/12/07 12:52:31 1.23
+++ Makefile.in.in 2005/01/31 19:45:57
＠＠ -598,7 +598,7 ＠＠ extraclean:
## Note: it's no disaster if these productions miss a file or two; tar
## and VC will swiftly let you know if this happens, and it is easily
## corrected.
-SOURCES = ChangeLog GETTING.GNU.SOFTWARE INSTALL Makefile.in.in PROBLEMS \
+SOURCES = ChangeLog INSTALL Makefile.in.in PROBLEMS \
README build-install.in configure make-dist move-if-change
.PHONY: unlock relock TAGS tags dist info dvi mcs
Index: PROBLEMS
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/PROBLEMS,v
retrieving revision 1.68
diff -u -p -r1.68 PROBLEMS
--- PROBLEMS 2003/09/19 16:24:33 1.68
+++ PROBLEMS 2005/01/31 19:45:58
＠＠ -783,12 +783,6 ＠＠ the system malloc. Andy Piper writes:
Try configuring with pdump or without system malloc.
-*** In general use etc/check_cygwin_setup.sh to trap environment problems.
-
-The script etc/check_cygwin_setup.sh will attempt to detect whether
-you have a suitable environment for building. This script may not work
-correctly if you are using ash instead of bash (see below).
-
*** Syntax errors running configure scripts, make failing with exit code 127
in inexplicable situations, etc.
＠＠ -1004,7 +998,7 ＠＠ certain thing in the XKeysymDB file. Th
or in /usr/openwin/lib/. If you keep yours in a different place, set the
environment variable $XKEYSYMDB to point to it before starting emacs. If
you still have the problem after doing that, perhaps your version of X is
-too old. There is a copy of the MIT X11R5 XKeysymDB file in the emacs `etc'
+too old. There is a copy of the MIT X11R6 XKeysymDB file in the emacs `etc'
directory. Try using that one.
*** My X resources used to work, and now some of them are being ignored.
cvs server: Diffing dynodump
cvs server: Diffing dynodump/i386
cvs server: Diffing dynodump/ppc
cvs server: Diffing dynodump/sparc
cvs server: Diffing etc
cvs server: cannot find etc/BETA
cvs server: etc/CHARSETS was removed, no comparison available
cvs server: etc/CODINGS was removed, no comparison available
cvs server: etc/COPYING.LIB was removed, no comparison available
Index: etc/README
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/README,v
retrieving revision 1.9
diff -u -p -r1.9 README
--- etc/README 2003/03/27 12:57:44 1.9
+++ etc/README 2005/01/31 19:46:02
＠＠ -3,40 +3,21 ＠＠ This directory contains some text files
of interest to XEmacs users, some programs used by or with XEmacs, and
the file of on-line documentation for XEmacs.
-BETA Information about Beta versions
-CHARSETS Character set descriptions
-CODING-STANDARDS XEmacs C & Lisp coding standards
-CODINGS Character set codings
-COOKIES Urban Legend, or True Story? :-)
COPYING GNU Public License
-COPYING.LIB Library GNU Public License
-DEBUG Hints on how to debug XEmacs
-DISTRIB How to obtain copies of XEmacs and Emacs
+ChangeLog ChangeLog for etc/
+ETAGS.EBNF Description of TAGS file format
Emacs.ad Sample Resource file
-FTP XEmacs FTP Mirrors
-GNU GNU Manifesto
-GOATS Complete XEmacs internals documentation
+HELLO Hello in many languages (Mule test file)
InstallGuide Fast track to installation
-LPF Information about the League for Programming Freedom
-MACHINES List of known machines configurations (OLD)
-MAILINGLISTS List of available Mailing lists
-MORE.STUFF List of useful unbundled packages
-NEWS XEmacs 21.4 release information
-ORDERS
-ORDERS.EUROPE
-ORDERS.JAPAN Order forms for GNU software
-PACKAGES List of packages available for 21.4 release
+NEWS XEmacs 21.5 release information
+ONEWS Older release information
+OONEWS Even older release information
README This file
-README.HYPERBOLE
-README.OO-BROWSER How to obtain Hyperbole and the OO-Browser
-SERVICE How to obtain paid support for free software
-TERMS Information about termcap entries
TUTORIAL Tutorial for first time users (English version)
TUTORIAL.* Tutorials in non-English languages
+VEGETABLES XEmacs 21.5 code names
XKeysymDB X Keysym Database with Motif bindings
-aliases.sh Useful shell aliases
cbx.png "Created by XEmacs" logo
-check_cygwin_setup.sh Script to check for presence of Cygwin
ctags.1 Ctags man page
custom/ Images used in Custom mode
editclient.sh Either start up XEmacs or connect to a running one
＠＠ -44,18 +25,15 ＠＠ emacskeys.sco
emacsstrs.sco Special files for running on an SCO console
eos/ Images for EOS support (GUD)
etags.1 Etags man page
-gnu.xbm
-gnu.xpm Image of a Gnu.
gnuattach.1 Gnuattach man page
gnuclient.1 Gnuclient man page
gnudoit.1 Gnudoit man page
gnuserv.1 Gnuserv man page
gnuserv.README Original README file from gnuserv
-gnusref.tex Gnus reference card
gray1.xbm Gray bitmap
-ms-kermit
-ms-kermit-7bit Files for running XEmacs through kermit
-photos/*.Z Various pictures of XEmacs developers
+idd/ ?
+package-index.LATEST.gpg ?
+photos/* Various pictures of XEmacs developers
recycle.xpm
recycle2.xpm Two versions of oversized Recycle cursor
refcard.ps.gz Postscript version of XEmacs reference card
＠＠ -63,19 +41,18 ＠＠ refcard.tex XEmacs reference card
sample.Xdefaults (legacy -- to be removed)
sample.Xresources Example ~/.Xresources file
sample.init.el Example ~/.xemacs/init.el file
-sink.xbm A Gnu icon
sparcworks/ Support files for Sparcworks
tests/ Testcases for external widget
-time/ Image files for display-time
toolbar/ Image files for the toolbar
trash.xpm Garbage can icon
+unicode/ Unicode conversion tables
xemacs-beta.xpm XEmacs Beta logo
+xemacs-enhanced.png "XEmacs-enhanced" logo
xemacs-fe.sh XEmacs frontend driver
xemacs-icon.xpm
xemacs-icon2.xbm
xemacs-icon2.xpm
xemacs-icon3.xpm Various versions of an XEmacs WM icon
-xemacs-ja.1 Japanese XEmacs man page
xemacs.1 XEmacs man page
xemacs.xbm
xemacs.xpm XEmacs logo used on the splash screen
cvs server: etc/README.HYPERBOLE was removed, no comparison available
cvs server: etc/README.OO-BROWSER was removed, no comparison available
cvs server: etc/SERVICE was removed, no comparison available
cvs server: etc/TERMS was removed, no comparison available
cvs server: etc/aliases.ksh was removed, no comparison available
cvs server: etc/check_cygwin_setup.sh was removed, no comparison available
cvs server: etc/chr.png was removed, no comparison available
cvs server: etc/chrm.png was removed, no comparison available
cvs server: etc/gnu.xbm was removed, no comparison available
cvs server: etc/gnu.xpm was removed, no comparison available
cvs server: etc/ms-kermit was removed, no comparison available
cvs server: etc/ms-kermit-7bit was removed, no comparison available
cvs server: etc/sink.xbm was removed, no comparison available
cvs server: Diffing etc/custom
cvs server: Diffing etc/custom/example-themes
cvs server: Diffing etc/eos
cvs server: Diffing etc/idd
cvs server: Diffing etc/photos
cvs server: Diffing etc/sparcworks
cvs server: Diffing etc/tests
cvs server: Diffing etc/tests/external-widget
cvs server: Diffing etc/toolbar
cvs server: Diffing etc/unicode
cvs server: Diffing etc/unicode/ibm
cvs server: Diffing etc/unicode/mule-ucs
cvs server: Diffing etc/unicode/other
cvs server: Diffing etc/unicode/unicode-consortium
cvs server: Diffing info
cvs server: Diffing lib-src
cvs server: Diffing lisp
Index: lisp/help.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/help.el,v
retrieving revision 1.43
diff -u -p -r1.43 help.el
--- lisp/help.el 2004/09/15 08:30:26 1.43
+++ lisp/help.el 2005/01/31 19:46:09
＠＠ -1,7 +1,7 ＠＠
;;; help.el --- help commands for XEmacs.
;; Copyright (C) 1985, 1986, 1992-4, 1997 Free Software Foundation, Inc.
-;; Copyright (C) 2001, 2002 Ben Wing.
+;; Copyright (C) 2001, 2002, 2003 Ben Wing.
;; Maintainer: FSF
;; Keywords: help, internal, dumped
＠＠ -696,12 +696,17 ＠＠ describes the minor mode."
(defun describe-distribution ()
"Display info on how to obtain the latest version of XEmacs."
(interactive)
- (Help-find-file (locate-data-file "DISTRIB")))
+ (save-window-excursion
+ (info)
+ (Info-find-node "xemacs-faq" "Q1.1.1"))
+ (switch-to-buffer "*info*"))
(defun describe-beta ()
"Display info on how to deal with Beta versions of XEmacs."
(interactive)
- (Help-find-file (locate-data-file "BETA")))
+ (save-window-excursion
+ (info "(beta)Top"))
+ (switch-to-buffer "*info*"))
(defun describe-copying ()
"Display info on how you may redistribute copies of XEmacs."
＠＠ -712,11 +717,6 ＠＠ describes the minor mode."
"Show a list of all defined mouse buttons, and their definitions."
(interactive)
(describe-bindings nil t))
-
-(defun describe-project ()
- "Display info on the GNU project."
- (interactive)
- (Help-find-file (locate-data-file "GNU")))
(defun describe-no-warranty ()
"Display info on all the kinds of warranty XEmacs does NOT have."
cvs server: Diffing lisp/mule
cvs server: Diffing lisp/term
cvs server: Diffing lock
cvs server: Diffing lwlib
cvs server: Diffing man
Index: man/Makefile
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/Makefile,v
retrieving revision 1.33
diff -u -p -r1.33 Makefile
--- man/Makefile 2004/12/07 12:52:45 1.33
+++ man/Makefile 2005/01/31 19:46:11
＠＠ -42,6 +42,7 ＠＠ HTMLDIR = ../html
PHOTODIR = ../etc/photos
info_files = \
+ $(INFODIR)/beta.info \
$(INFODIR)/cl.info \
$(INFODIR)/custom.info \
$(INFODIR)/emodules.info \
＠＠ -59,6 +60,7 ＠＠ info_files = \
$(INFODIR)/xemacs-faq.info
html_files = \
+ $(HTMLDIR)/beta.html \
$(HTMLDIR)/cl.html \
$(HTMLDIR)/custom.html \
$(HTMLDIR)/emodules.html \
＠＠ -76,6 +78,7 ＠＠ html_files = \
$(HTMLDIR)/xemacs-faq.html
dvi_files = \
+ beta.dvi \
cl.dvi \
custom.dvi \
emodules.dvi \
＠＠ -93,6 +96,7 ＠＠ dvi_files = \
xemacs-faq.dvi
pdf_files = \
+ beta.pdf \
cl.pdf \
custom.pdf \
emodules.pdf \
＠＠ -237,6 +241,9 ＠＠ new-users-guide-srcs = \
new-users-guide/search.texi \
new-users-guide/xmenu.texi
+$(INFODIR)/beta.info: beta.texi
+ $(MAKEINFO) -o $(INFODIR)/beta.info beta.texi
+
$(INFODIR)/cl.info : cl.texi
$(MAKEINFO) -o $(INFODIR)/cl.info cl.texi
＠＠ -339,6 +346,9 ＠＠ extraclean: distclean
$(RM) *~ \#* */*~ */\#*
############################################################################
+
+$(HTMLDIR)/beta.html: beta.texi
+ $(TEXI2HTML) beta.texi
$(HTMLDIR)/cl.html : cl.texi
$(TEXI2HTML_SPLIT) cl.texi
cvs server: man/beta.texi is a new entry, no comparison available
Index: man/xemacs-faq.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/xemacs-faq.texi,v
retrieving revision 1.82
diff -u -p -r1.82 xemacs-faq.texi
--- man/xemacs-faq.texi 2004/12/29 05:08:26 1.82
+++ man/xemacs-faq.texi 2005/01/31 19:46:14
＠＠ -194,63 +194,77 ＠＠ library directory>/info/}. For example i
1 Introduction, Policy, Credits
-1.0: Introduction
+1.0: What is XEmacs?
* Q1.0.1:: What is XEmacs?
* Q1.0.2:: What is the current version of XEmacs?
-* Q1.0.3:: Where can I find it?
-* Q1.0.4:: Are binaries available?
-* Q1.0.5:: How does XEmacs differ from GNU Emacs?
-* Q1.0.6:: How much does XEmacs differ?
-* Q1.0.7:: Is XEmacs "GNU"?
-* Q1.0.8:: What is the correct way to refer to XEmacs and GNU Emacs?
-* Q1.0.9:: Why haven't XEmacs and GNU Emacs merged?
-* Q1.0.10:: Where can I get help?
-* Q1.0.11:: Where are the mailing lists archived?
-* Q1.0.12:: How do you pronounce XEmacs?
-* Q1.0.13:: What does XEmacs look like?
-* Q1.0.14:: Where can I obtain a printed copy of the XEmacs User's Manual?
-
-1.1: Versions for Different Operating Systems
-* Q1.1.1:: Do I need X11 to run XEmacs?
-* Q1.1.2:: Is there a port of XEmacs to Microsoft Windows?
-* Q1.1.3:: Can I build XEmacs on MS Windows with X support? Do I need to?
-* Q1.1.4:: What are Cygwin and MinGW, and do I need them to run XEmacs?
-* Q1.1.5:: What are the differences between the various MS Windows emacsen?
-* Q1.1.6:: Is there a port of XEmacs to the Macintosh?
-* Q1.1.7:: Is there a port of XEmacs to NextStep?
-* Q1.1.8:: Is there a port of XEmacs to OS/2?
-* Q1.1.9:: How does the port cope with differences in the Windows user interface?
-
-1.2: Policies
-* Q1.2.1:: What is the FAQ editorial policy?
-* Q1.2.2:: How do I become a beta tester?
-* Q1.2.3:: How do I contribute to XEmacs itself?
-
-1.3: Credits
-* Q1.3.1:: Who wrote XEmacs?
-* Q1.3.2:: Who contributed to this version of the FAQ?
-* Q1.3.3:: Who contributed to the FAQ in the past?
-
-1.4: Internationalization
-* Q1.4.1:: What is the status of internationalization support aka MULE (including Asian language support)?
-* Q1.4.2:: How can I help with internationalization?
-* Q1.4.3:: How do I type non-ASCII characters?
-* Q1.4.4:: Can XEmacs messages come out in a different language?
-* Q1.4.5:: Please explain the various input methods in MULE/XEmacs
-* Q1.4.6:: How do I portably code for MULE/XEmacs?
-* Q1.4.7:: How about Cyrillic modes?
-* Q1.4.8:: Does XEmacs support Unicode?
-* Q1.4.9:: How does XEmacs display Unicode?
-
-1.5: Getting Started
-* Q1.5.1:: What is an ＠file{init.el} or ＠file{.emacs} and is there a sample one?
-* Q1.5.2:: Where do I put my ＠file{init.el} file?
-* Q1.5.3:: Can I use the same ＠file{init.el} with the other Emacs?
-* Q1.5.4:: Any good XEmacs tutorials around?
-* Q1.5.5:: May I see an example of a useful XEmacs Lisp function?
-* Q1.5.6:: And how do I bind it to a key?
-* Q1.5.7:: What's the difference between a macro and a function?
-* Q1.5.8:: What is ＠code{Custom}?
+* Q1.0.3:: How do you pronounce XEmacs?
+* Q1.0.4:: What does XEmacs look like?
+* Q1.0.5:: Who wrote XEmacs?
+* Q1.0.6:: Who wrote the FAQ?
+
+1.1: Getting XEmacs
+* Q1.1.1:: Where can I find XEmacs?
+* Q1.1.2:: Are binaries available?
+* Q1.1.3:: How do I get the bleeding-edge sources?
+* Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
+
+1.2: Versions for Different Operating Systems
+* Q1.2.1:: Do I need X11 to run XEmacs?
+* Q1.2.2:: What versions of Unix does XEmacs run on?
+* Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
+* Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
+* Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
+* Q1.2.6:: What are the differences between the various MS Windows emacsen?
+* Q1.2.7:: How does the port cope with differences in the Windows user interface?
+* Q1.2.8:: Is there a port of XEmacs to the Macintosh?
+* Q1.2.9:: Is there a port of XEmacs to MS-DOS?
+* Q1.2.10:: Is there a port of XEmacs to OS/2?
+* Q1.2.11:: Is there a port of XEmacs to NextStep?
+* Q1.2.12:: Is there a port of XEmacs to VMS?
+
+1.3: Getting Started
+* Q1.3.1:: What is an ＠file{init.el} or ＠file{.emacs} and is there a sample one?
+* Q1.3.2:: Where do I put my ＠file{init.el} file?
+* Q1.3.3:: Can I use the same ＠file{init.el} with the other Emacs?
+* Q1.3.4:: Any good XEmacs tutorials around?
+* Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
+* Q1.3.6:: And how do I bind it to a key?
+* Q1.3.7:: What's the difference between a macro and a function?
+* Q1.3.8:: What is ＠code{Custom}?
+
+1.4: Getting Help
+* Q1.4.1:: Where can I get help?
+* Q1.4.2:: Which mailing lists are there?
+* Q1.4.2:: Where are the mailing lists archived?
+* Q1.4.3:: How can I get two instances of info?
+* Q1.4.4:: How do I add new Info directories?
+
+1.5: Contributing to XEmacs
+* Q1.5.1:: How do I submit changes to the FAQ?
+* Q1.5.2:: How do I become a beta tester?
+* Q1.5.3:: How do I contribute to XEmacs itself?
+
+1.6: Politics (XEmacs vs. GNU Emacs)
+* Q1.6.1:: What is GNU Emacs?
+* Q1.6.2:: How does XEmacs differ from GNU Emacs?
+* Q1.6.3:: How much does XEmacs differ?
+* Q1.6.4:: Is XEmacs "GNU"?
+* Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
+* Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
+
+1.7: External Packages
+* Q1.7.1:: Which external packages are there?
+
+1.8: Internationalization
+* Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
+* Q1.8.2:: How can I help with internationalization?
+* Q1.8.3:: How do I type non-ASCII characters?
+* Q1.8.4:: Can XEmacs messages come out in a different language?
+* Q1.8.5:: Please explain the various input methods in MULE/XEmacs
+* Q1.8.6:: How do I portably code for MULE/XEmacs?
+* Q1.8.7:: How about Cyrillic modes?
+* Q1.8.8:: Does XEmacs support Unicode?
+* Q1.8.9:: How does XEmacs display Unicode?
2 Installation and Troubleshooting
＠＠ -473,36 +487,32 ＠＠ library directory>/info/}. For example i
7 Advanced Customization Using XEmacs Lisp
-7.0: Online Help
-* Q7.0.1:: How can I get two instances of info?
-* Q7.0.2:: How do I add new Info directories?
-
-7.1: Emacs Lisp and ＠file{init.el}
-* Q7.1.1:: What version of Emacs am I running?
-* Q7.1.2:: How can I evaluate Emacs-Lisp expressions?
-* Q7.1.3:: ＠code{(setq tab-width 6)} behaves oddly.
-* Q7.1.4:: How can I add directories to the ＠code{load-path}?
-* Q7.1.5:: How to check if a lisp function is defined?
-* Q7.1.6:: Can I force the output of ＠code{(face-list)} to a buffer?
-
-7.2: Emacs Lisp Programming Techniques
-* Q7.2.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
-* Q7.2.2:: Can I generate "fake" keyboard events?
-* Q7.2.3:: Could you explain ＠code{read-kbd-macro} in more detail?
-* Q7.2.4:: What is the performance hit of ＠code{let}?
-* Q7.2.5:: What is the recommended use of ＠code{setq}?
-* Q7.2.6:: What is the typical misuse of ＠code{setq}?
-* Q7.2.7:: I like the ＠code{do} form of cl, does it slow things down?
-* Q7.2.8:: I like recursion, does it slow things down?
-* Q7.2.9:: How do I put a glyph as annotation in a buffer?
-* Q7.2.10:: ＠code{map-extents} won't traverse all of my extents!
-* Q7.2.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
-
-7.3: Mathematics
-* Q7.3.1:: What are bignums, ratios, and bigfloats in Lisp?
-* Q7.3.2:: XEmacs segfaults when I use very big numbers!
-* Q7.3.3:: Bignums are really slow!
-* Q7.3.4:: Equal bignums don't compare as equal! What gives?
+7.0: Emacs Lisp and ＠file{init.el}
+* Q7.0.1:: What version of Emacs am I running?
+* Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
+* Q7.0.3:: ＠code{(setq tab-width 6)} behaves oddly.
+* Q7.0.4:: How can I add directories to the ＠code{load-path}?
+* Q7.0.5:: How to check if a lisp function is defined?
+* Q7.0.6:: Can I force the output of ＠code{(face-list)} to a buffer?
+
+7.1: Emacs Lisp Programming Techniques
+* Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
+* Q7.1.2:: Can I generate "fake" keyboard events?
+* Q7.1.3:: Could you explain ＠code{read-kbd-macro} in more detail?
+* Q7.1.4:: What is the performance hit of ＠code{let}?
+* Q7.1.5:: What is the recommended use of ＠code{setq}?
+* Q7.1.6:: What is the typical misuse of ＠code{setq}?
+* Q7.1.7:: I like the ＠code{do} form of cl, does it slow things down?
+* Q7.1.8:: I like recursion, does it slow things down?
+* Q7.1.9:: How do I put a glyph as annotation in a buffer?
+* Q7.1.10:: ＠code{map-extents} won't traverse all of my extents!
+* Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
+
+7.2: Mathematics
+* Q7.1.1:: What are bignums, ratios, and bigfloats in Lisp?
+* Q7.1.2:: XEmacs segfaults when I use very big numbers!
+* Q7.1.3:: Bignums are really slow!
+* Q7.1.4:: Equal bignums don't compare as equal! What gives?
8 Other External Packages
＠＠ -537,7 +547,6 ＠＠ library directory>/info/}. For example i
10.0: XEmacs 21.1
* Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
-
＠end detailmenu
＠end menu
＠＠ -574,66 +583,81 ＠＠ this FAQ please send email to ＠email{xem
Include ＠samp{XEmacs FAQ} on the Subject: line.
＠menu
-1.0: Introduction
+1.0: What is XEmacs?
* Q1.0.1:: What is XEmacs?
* Q1.0.2:: What is the current version of XEmacs?
-* Q1.0.3:: Where can I find it?
-* Q1.0.4:: Are binaries available?
-* Q1.0.5:: How does XEmacs differ from GNU Emacs?
-* Q1.0.6:: How much does XEmacs differ?
-* Q1.0.7:: Is XEmacs "GNU"?
-* Q1.0.8:: What is the correct way to refer to XEmacs and GNU Emacs?
-* Q1.0.9:: Why haven't XEmacs and GNU Emacs merged?
-* Q1.0.10:: Where can I get help?
-* Q1.0.11:: Where are the mailing lists archived?
-* Q1.0.12:: How do you pronounce XEmacs?
-* Q1.0.13:: What does XEmacs look like?
-* Q1.0.14:: Where can I obtain a printed copy of the XEmacs User's Manual?
-
-1.1: Versions for Different Operating Systems
-* Q1.1.1:: Do I need X11 to run XEmacs?
-* Q1.1.2:: Is there a port of XEmacs to Microsoft Windows?
-* Q1.1.3:: Can I build XEmacs on MS Windows with X support? Do I need to?
-* Q1.1.4:: What are Cygwin and MinGW, and do I need them to run XEmacs?
-* Q1.1.5:: What are the differences between the various MS Windows emacsen?
-* Q1.1.6:: Is there a port of XEmacs to the Macintosh?
-* Q1.1.7:: Is there a port of XEmacs to NextStep?
-* Q1.1.8:: Is there a port of XEmacs to OS/2?
-* Q1.1.9:: How does the port cope with differences in the Windows user interface?
-
-1.2: Policies
-* Q1.2.1:: What is the FAQ editorial policy?
-* Q1.2.2:: How do I become a beta tester?
-* Q1.2.3:: How do I contribute to XEmacs itself?
-
-1.3: Credits
-* Q1.3.1:: Who wrote XEmacs?
-* Q1.3.2:: Who contributed to this version of the FAQ?
-* Q1.3.3:: Who contributed to the FAQ in the past?
-
-1.4: Internationalization
-* Q1.4.1:: What is the status of internationalization support aka MULE (including Asian language support)?
-* Q1.4.2:: How can I help with internationalization?
-* Q1.4.3:: How do I type non-ASCII characters?
-* Q1.4.4:: Can XEmacs messages come out in a different language?
-* Q1.4.5:: Please explain the various input methods in MULE/XEmacs
-* Q1.4.6:: How do I portably code for MULE/XEmacs?
-* Q1.4.7:: How about Cyrillic modes?
-* Q1.4.8:: Does XEmacs support Unicode?
-* Q1.4.9:: How does XEmacs display Unicode?
-
-1.5: Getting Started
-* Q1.5.1:: What is an ＠file{init.el} or ＠file{.emacs} and is there a sample one?
-* Q1.5.2:: Where do I put my ＠file{init.el} file?
-* Q1.5.3:: Can I use the same ＠file{init.el} with the other Emacs?
-* Q1.5.4:: Any good XEmacs tutorials around?
-* Q1.5.5:: May I see an example of a useful XEmacs Lisp function?
-* Q1.5.6:: And how do I bind it to a key?
-* Q1.5.7:: What's the difference between a macro and a function?
-* Q1.5.8:: What is ＠code{Custom}?
+* Q1.0.3:: How do you pronounce XEmacs?
+* Q1.0.4:: What does XEmacs look like?
+* Q1.0.5:: Who wrote XEmacs?
+* Q1.0.6:: Who wrote the FAQ?
+
+1.1: Getting XEmacs
+* Q1.1.1:: Where can I find XEmacs?
+* Q1.1.2:: Are binaries available?
+* Q1.1.3:: How do I get the bleeding-edge sources?
+* Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
+
+1.2: Versions for Different Operating Systems
+* Q1.2.1:: Do I need X11 to run XEmacs?
+* Q1.2.2:: What versions of Unix does XEmacs run on?
+* Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
+* Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
+* Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
+* Q1.2.6:: What are the differences between the various MS Windows emacsen?
+* Q1.2.7:: How does the port cope with differences in the Windows user interface?
+* Q1.2.8:: Is there a port of XEmacs to the Macintosh?
+* Q1.2.9:: Is there a port of XEmacs to MS-DOS?
+* Q1.2.10:: Is there a port of XEmacs to OS/2?
+* Q1.2.11:: Is there a port of XEmacs to NextStep?
+* Q1.2.12:: Is there a port of XEmacs to VMS?
+
+1.3: Getting Started
+* Q1.2.13::
+* Q1.3.1:: What is an ＠file{init.el} or ＠file{.emacs} and is there a sample one?
+* Q1.3.2:: Where do I put my ＠file{init.el} file?
+* Q1.3.3:: Can I use the same ＠file{init.el} with the other Emacs?
+* Q1.3.4:: Any good XEmacs tutorials around?
+* Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
+* Q1.3.6:: And how do I bind it to a key?
+* Q1.3.7:: What's the difference between a macro and a function?
+* Q1.3.8:: What is ＠code{Custom}?
+
+1.4: Getting Help
+* Q1.4.1:: Where can I get help?
+* Q1.4.2:: Which mailing lists are there?
+* Q1.4.3:: How can I get two instances of info?
+* Q1.4.4:: How do I add new Info directories?
+
+1.5: Contributing to XEmacs
+* Q1.4.5::
+* Q1.5.1:: How do I submit changes to the FAQ?
+* Q1.5.2:: How do I become a beta tester?
+* Q1.5.3:: How do I contribute to XEmacs itself?
+
+1.6: Politics (XEmacs vs. GNU Emacs)
+* Q1.6.1:: What is GNU Emacs?
+* Q1.6.2:: How does XEmacs differ from GNU Emacs?
+* Q1.6.3:: How much does XEmacs differ?
+* Q1.6.4:: Is XEmacs "GNU"?
+* Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
+* Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
+
+1.7: External Packages
+* Q1.7.1:: Which external packages are there?
+
+1.8: Internationalization
+* Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
+* Q1.8.2:: How can I help with internationalization?
+* Q1.8.3:: How do I type non-ASCII characters?
+* Q1.8.4:: Can XEmacs messages come out in a different language?
+* Q1.8.5:: Please explain the various input methods in MULE/XEmacs
+* Q1.8.6:: How do I portably code for MULE/XEmacs?
+* Q1.8.7:: How about Cyrillic modes?
+* Q1.8.8:: Does XEmacs support Unicode?
+* Q1.8.9:: How does XEmacs display Unicode?
＠end menu
-＠unnumberedsec 1.0: Introduction
+＠unnumberedsec 1.0: What is XEmacs?
＠node Q1.0.1, Q1.0.2, Introduction, Introduction
＠unnumberedsubsec Q1.0.1: What is XEmacs?
＠＠ -667,134 +691,1208 ＠＠ XEmacs 19.16, released in November, 1997
and was also the last version without international language support.
＠node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
-＠unnumberedsubsec Q1.0.3: Where can I find it?
-
-The canonical source and binaries can be found at:
+＠unnumberedsubsec Q1.0.3: How do you pronounce XEmacs?
-＠example
-＠uref{http://ftp.xemacs.org/pub/xemacs/}
-＠end example
+The most common pronounciation is ＠samp{Eks eemax}.
＠node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
-＠unnumberedsubsec Q1.0.4: Are binaries available?
-
-MS Windows binaries are available at
-＠uref{http://www.xemacs.org/Download/win32/} for the native versions
-of 21.4 and 21.1. Cygwin binaries are now available as part of the
-standard Cygwin installation process. XEmacs also comes pre-built as
-part of many Linux distributions, such as Red Hat and SuSE.
+＠unnumberedsubsec Q1.0.4: What does XEmacs look like?
-Otherwise, you will need to build XEmacs yourself or get your system
-administrator to do it. Generally, this is not a difficult process
-under Unix and Mac OS X, as XEmacs has been tested under all of the
-common Unix versions and under Mac OS X and comes with an extensive
-configure script that is able to automatically detect most aspects of
-the configuration of your particular system.
+Screen snapshots are available at
+＠uref{http://www.xemacs.org/About/Screenshots/index.html}
+as part of the XEmacs website.
＠node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
-＠unnumberedsubsec Q1.0.5: How does XEmacs differ from GNU Emacs?
-
-For a detailed description of the differences between GNU Emacs and
-XEmacs and a detailed history of XEmacs, check out the
-＠example
-＠uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
-＠end example
+＠unnumberedsubsec Q1.0.5: Who wrote XEmacs?
-＠table ＠strong
-＠item User-Visible Editing Features
-XEmacs in general tries hard to conform to exist user-interface
-standards, and to work "out-of-the-box" without the need for obscure
-customization changes. GNU Emacs, particularly version 21, has gotten
-better about this (in many cases by copying the XEmacs behavior!), but
-still has some weirdnesses. For example, the standard method of
-selecting text using the Shift key works out-of-the-box in XEmacs.
+XEmacs is the result of the time and effort of many people, and the
+active developers have changed over time. There are two major
+components of the XEmacs effort -- writing the code itself and providing
+all the support work (testing the code, releasing beta and final
+versions, handling patches, reading bug reports, maintaining the web
+site, managing the mailing lists, etc. etc.). Neither component would
+work without the other.
-XEmacs has a built-in toolbar. Four toolbars can actually be configured
-simultaneously: top, bottom, left, and right toolbars.
+＠subheading CODING
-XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19
-(which provides a primitive form of vertical scrollbar), these are true
-toolkit scrollbars. A look-alike Motif scrollbar is provided for those
-who don't have Motif. (Even for those who do, the look-alike may be
-preferable as it is faster.)
+The primary code contributor over the years has been Ben Wing (active
+since late 1992). Between 1991 and 1995, large amounts of coding was
+contributed by Jamie Zawinski and Chuck Thompson. Many other people
+have authored major subsystems or otherwise contributed large amounts of
+code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
+Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
+Mlynarik, Stig, William Perry and plenty of others.
-XEmacs has buffer tabs along the top of the frame (although the
-position can be changed) that make it very easy to switch buffers.
+Primary XEmacs-specific subsystems and their authors:
-The menubar under XEmacs is better-designed, with more thought put into
-it.
+＠table ＠asis
+＠item Objects
+＠itemize ＠minus
+＠item
+Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
+＠item
+Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
+＠item
+Portable dumper, object descriptions: Olivier Galibert
+＠item
+KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
+＠item
+Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
+＠item
+Profiling: Ben Wing
+＠item
+Some byte-compilation and hash-table improvements: Martin Buchholz
+＠item
+Bignum: Jerry James
+＠end itemize
-XEmacs can ask questions using popup dialog boxes. Any command executed
-from a menu will ask yes/no questions with dialog boxes, while commands
-executed via the keyboard will use the minibuffer.
+＠item Internationalization/Mule
+＠itemize ＠minus
+＠item
+mostly Ben Wing; many ideas for future work, Stephen Turnbull
+＠end itemize
-XEmacs under MS Windows provides uses the standard file-dialog box for
-opening and saving files. Standard menu-accelerator behavior can easily
-be enabled using the Options menu, and integrates well into the existing
-keymap.
+＠item I/O
+＠itemize ＠minus
+＠item
+Basic event/event-stream implementation: Jamie Zawinski
+＠item
+Most event work since 1994: Ben Wing
+＠item
+Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
+＠item
+Process method abstraction, Windows process work: Kirill Katsnelson
+＠item
+Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
+＠item
+Lstreams: Ben Wing
+＠end itemize
-XEmacs has (still experimental) support for widgets of various sorts --
-buttons, text boxes, sliders, progress bars, etc. A progress bar is
-used in font lock to show the progress.
+＠item Display
+＠itemize ＠minus
+＠item
+Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
+＠item
+Glyphs: mostly Ben Wing
+＠item
+Specifiers: Ben Wing
+＠item
+Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
+＠item
+Widgets: Andy Piper
+＠item
+JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in ＠file{glyphs-eimage.c})
+＠item
+Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
+＠item
+Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
+＠item
+Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
+＠item
+Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
+＠item
+Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
+＠item
+Toolbars: implementation, chuck, much interface work, Ben Wing
+＠item
+Gutters, tabs: andy piper
+＠end itemize
-Experimental support for drag-and-drop protocols is provided from
-XEmacs 21.
+＠item Device subsystems
+＠itemize ＠minus
+＠item
+X Windows: Jamie Zawinksi, Ben Wing, others
+＠item
+GTK: William Perry, Malcolm Purvis
+＠item
+MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
+＠item
+TTY: Chuck Thompson, Ben Wing
+＠item
+Cygwin: Andy Piper
+＠end itemize
-＠item General Platform Support
-If you're running on a machine with audio hardware, you can specify
-sound files for XEmacs to play instead of the default X beep. See the
-documentation of the function load-sound-file and the variable
-sound-alist. XEmacs also supports the network sound protocols NAS and
-EsounD.
+＠item Misc
+＠itemize ＠minus
+＠item
+Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
+＠item
+Most initialization-related code: Ben Wing
+＠item
+Internals manual, much of Lisp manual: Ben Wing
+＠item
+FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
+＠end itemize
+＠end table
-XEmacs 21 supports database protocols with LISP bindings, currently
-including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
+＠subheading SUPPORT
-XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
-servers directly, as well as through the X Input Method (XIM)
-protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
-support the Quail family of input methods (implemented in LISP) for many
-languages.
+Currently, support duties are handled by many different people.
-XEmacs provides support for ToolTalk on systems that have
-it.
+Release managers have been
-＠item Packaged LISP Libraries
-Many more packages are provided standard with XEmacs than with GNU Emacs
-19 or 20.
+＠itemize ＠minus
+＠item
+Stephen Turnbull (April 2001 - January 2003, March 2004 - present, 21.2.47 - 21.4.12, 21.5.2 - 21.5.7, 21.5.17 - present)
+＠item
+Vin Shelton (May 2003 - present, 21.4.13 - present)
+＠item
+Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16)
+＠item
+Martin Buchholz (December 1998, November 1999 - May 2001, 21.2.7 - 21.2.8, 21.2.21 - 21.2.46, 21.5.0 - 21.5.1)
+＠item
+Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20)
+＠item
+Andy Piper (December 1998, 21.2.6)
+＠item
+Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
+＠item
+Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
+＠end itemize
-XEmacs 21 supports an integrated package management system which uses
-EFS to download, then automatically install prebuilt LISP
-libraries. This allows XEmacs users much more straightforward access to
-the "latest and greatest" version of any given library.
+The recent overlapping dates are intentional, since two or three trees
+are maintained simultaneously at any point.
-We are working on a standard method for enabling, disabling and
-otherwise controlling packages, which should make them very easy to use.
+Other major support work:
-＠item LISP Programming
-From XEmacs 20 on, characters are a separate type. Characters can be
-converted to integers (and many integers can be converted to
-characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
-Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
-20 (incorporating Mule 3 and later Mule 4) represent them as integers.
+＠itemize ＠minus
+＠item
+Adrian Aichner wrote and maintains the web site.
+＠item
+Stephen Turnbull has produced many of the beta and semi-stable releases
+and has attempted to be the "face" of XEmacs on the newsgroups and
+mailing lists.
+＠item
+Steve Youngs currently produces the beta releases (???).
+＠item
+Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns
+maintaining the packages.
+＠item
+Vin Shelton maintains the stable releases.
+＠item
+Testing - #### Norbert, Adrian, ???
+＠end itemize
-From XEmacs 20 on, the buffer is treated as an array of characters, and
-the representation of buffer text is not exposed to LISP. The GNU Emacs
-20 functions like buffer-as-multibyte are not supported.
+Portraits and email of some of the major developers:
-In XEmacs, events are first-class objects. GNU Emacs 19 represents them
-as integers, which obscures the differences between a key gesture and
-the ancient ASCII code used to represent a particular overlapping subset
-of them.
+＠itemize ＠bullet
+＠item ＠email{andy＠(a)xemacs.org, Andy Piper}
+＠html
+<br><img src="piper.png" alt="Portrait of Andy Piper"><br>
+＠end html
-In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19
-represents them as complicated combinations of association lists and
-vectors. If you use the advertised functional interface to manipulation
-of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU
-Emacs 19; if your code depends on the underlying implementation of
-keymaps, it will not.
+＠item ＠email{ben＠(a)xemacs.org, Ben Wing}
+＠html
+<br><img src="ben.png" alt="Portrait of Ben Wing"><br>
+＠end html
-XEmacs uses "extents" to represent all non-textual aspects of buffers;
+＠item ＠email{cthomp＠(a)xemacs.org, Chuck Thompson}
+＠html
+<br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
+＠end html
+
+＠item ＠email{hniksic＠(a)xemacs.org, Hrvoje Niksic}
+
+＠html
+<br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
+＠end html
+
+＠item ＠email{jwz＠(a)jwz.org, Jamie Zawinski}
+＠html
+<br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
+＠end html
+
+＠item ＠email{martin＠(a)xemacs.org, Martin Buchholz}
+＠html
+<br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
+＠end html
+
+＠item ＠email{mly＠(a)adoc.xerox.com, Richard Mlynarik}
+＠html
+<br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
+＠end html
+
+＠item ＠email{stephen＠(a)xemacs.org, Stephen Turnbull}
+
+＠item ＠email{steve＠(a)xemacs.org, Steve Baur}
+＠html
+<br><img src="slb.png" alt="Portrait of Steve Baur"><br>
+＠end html
+＠end itemize
+
+Many other people have contributed to XEmacs; this is partially
+enumerated in the ＠samp{About XEmacs} option in the Help menu.
+
+＠node Q1.0.6, Q1.1.1, Q1.0.5, Introduction
+＠unnumberedsubsec Q1.0.6: Who wrote the FAQ?
+
+The current version of this FAQ was created by ＠email{ben＠(a)xemacs.org,
+Ben Wing}.
+
+Previous contributors to the FAQ include
+
+＠itemize ＠bullet
+＠item ＠email{steve＠(a)xemacs.org, SL Baur}
+
+＠item ＠email{hniksic＠(a)xemacs.org, Hrvoje Niksic}
+
+＠item ＠email{binge＠(a)aloft.att.com, Curtis.N.Bingham}
+
+＠item ＠email{bruncott＠(a)dormeur.inria.fr, Georges Brun-Cottan}
+
+＠item ＠email{rjc＠(a)cogsci.ed.ac.uk, Richard Caley}
+
+＠item ＠email{cognot＠(a)ensg.u-nancy.fr, Richard Cognot}
+
+＠item ＠email{daku＠(a)nortel.ca, Mark Daku}
+
+＠item ＠email{wgd＠(a)martigny.ai.mit.edu, William G. Dubuque}
+
+＠item ＠email{eeide＠(a)cs.utah.edu, Eric Eide}
+
+＠item ＠email{af＠(a)biomath.jussieu.fr, Alain Fauconnet}
+
+＠item ＠email{cflatter＠(a)nrao.edu, Chris Flatters}
+
+＠item ＠email{ginsparg＠(a)adra.com, Evelyn Ginsparg}
+
+＠item ＠email{hall＠(a)aplcenmp.apl.jhu.edu, Marty Hall}
+
+＠item ＠email{dkindred＠(a)cmu.edu, Darrell Kindred}
+
+＠item ＠email{dmoore＠(a)ucsd.edu, David Moore}
+
+＠item ＠email{arup+＠(a)cmu.edu, Arup Mukherjee}
+
+＠item ＠email{nickel＠(a)prz.tu-berlin.de, Juergen Nickelsen}
+
+＠item ＠email{powell＠(a)csl.ncsa.uiuc.edu, Kevin R. Powell}
+
+＠item ＠email{dworkin＠(a)ccs.neu.edu, Justin Sheehy}
+
+＠item ＠email{stig＠(a)hackvan.com, Stig}
+
+＠item ＠email{Aki.Vehtari＠(a)hut.fi, Aki Vehtari}
+＠end itemize
+
+＠unnumberedsec 1.1: Getting XEmacs
+
+＠node Q1.1.1, Q1.1.2, Q1.0.6, Introduction
+＠unnumberedsubsec Q1.1.1: Where can I find XEmacs?
+
+To download XEmacs, visit the XEmacs WWW page at
+＠uref{http://www.xemacs.org/Download/}. The most up-to-date list of
+distribution sites can always be found there. Try to pick a site that
+is networkologically close to you. If you know of other mirrors of
+the XEmacs archives, please send e-mail to
+＠uref{mailto:webmaster＠＠xemacs.org} and we will list them here as well.
+
+The canonical distribution point is ftp.xemacs.org, available either
+through HTTP (＠uref{http://ftp.xemacs.org/}) or anonymous FTP
+(＠uref{ftp://ftp.xemacs.org/pub/xemacs/}).
+
+＠node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
+＠unnumberedsubsec Q1.1.2: Are binaries available?
+
+MS Windows binaries are available at
+＠uref{http://www.xemacs.org/Download/win32/} for the native versions
+of 21.4 and 21.1. Cygwin binaries are now available as part of the
+standard Cygwin installation process. XEmacs also comes pre-built as
+part of many Linux distributions, such as Red Hat and SuSE.
+
+Otherwise, you will need to build XEmacs yourself or get your system
+administrator to do it. Generally, this is not a difficult process
+under Unix and Mac OS X, as XEmacs has been tested under all of the
+common Unix versions and under Mac OS X and comes with an extensive
+configure script that is able to automatically detect most aspects of
+the configuration of your particular system.
+
+＠node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
+＠unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources?
+
+If you are interested in developing XEmacs, or getting the absolutely most
+recent, up-to-the-moment, bleeding-edge source code, you can directly
+access the master CVS source tree (read-only, of course, until you ask for
+and are granted permission to directly modify portions of the source tree)
+at cvs.xemacs.org. Directions on how to access the source tree are located
+at ＠uref{http://www.xemacs.org/Develop/cvsaccess.html}.
+
+Nightly CVS snapshots are available at
+＠uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}.
+
+＠node Q1.1.4, Q1.2.1, Q1.1.3, Introduction
+＠unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual?
+
+Pre-printed manuals are not available. If you are familiar with
+TeX, you can generate your own manual from the XEmacs sources.
+
+HTML and Postscript versions of XEmacs manuals are available from the
+XEmacs web site at
+＠uref{http://www.xemacs.org/Documentation/index.html}.
+
+＠unnumberedsec 1.2: Versions for Different Operating Systems
+
+＠node Q1.2.1, Q1.2.2, Q1.1.4, Introduction
+＠unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs?
+
+No. The name ＠dfn{XEmacs} is unfortunate in the sense that it is
+＠strong{not} an X Window System-only version of Emacs. XEmacs has
+full color support on a color-capable character terminal.
+
+＠node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
+＠unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on?
+
+For problems with particular machines and versions of Unix, see the
+＠file{PROBLEMS} file.
+
+Much effort has gone into making XEmacs work on as many different
+machines, configurations, and compilers as possible.
+
+Much effort has gone into making XEmacs 64-bit clean.
+
+Much effort has gone into removing system-specific code, and replacing
+such code with autodetection at configure time.
+
+The XEmacs core should build "out of the box" on most Unix-like systems.
+
+XEmacs 21.2 was tested and ＠samp{make check} succeeded on these Unix
+configurations as of 2001-02-10:
+
+＠example
+alphaev56-dec-osf4.0e (both Compaq C and gcc)
+i386-unknown-freebsd4.2
+i386-unknown-netbsdelf1.5
+i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc)
+i686-pc-linux-gnu
+hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc)
+mips-sgi-irix6.5 (both MIPSpro cc and gcc)
+rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc)
+sparc-sun-solaris2.6 (both Sun's Forte C and gcc)
+sparc-sun-solaris2.7 (both Sun's Forte C and gcc)
+sparc-sun-sunos4.1.4 (gcc)
+＠end example
+
+Some systems have a dual mode 32-bit/64-bit compiler. On most of
+these, XEmacs requires the ＠samp{--pdump} configure option to build
+correctly with the 64-bit version of the compiler.
+
+＠example
+mips-sgi-irix6.5, CC="gcc -mabi=64"
+mips-sgi-irix6.5, CC="cc -64"
+rs6000-ibm-aix4.3.0.0, CC="cc -q64"
+＠end example
+
+On most of these systems, XEmacs also builds with a C++ compiler,
+but not "out of the box". This feature is only for use by the
+maintainers.
+
+XEmacs 21.2 is known ＠emph{not} to work on any machines with m680x0
+processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there.
+
+VMS has never been supported by XEmacs. In fact, all the old VMS code
+inherited from Emacs has been removed. Sorry, all you VMS fans out there.
+
+＠node Q1.2.3, Q1.2.4, Q1.2.2, Introduction
+＠unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows?
+
+Yes. Beginning with release 21.0, XEmacs has worked under MS Windows
+and is fully-featured and actively developed. A group of dedicated
+developers actively maintains and improves the Windows-specific
+portions of the code. Some of the core developers, in fact, use
+Windows as their only development environment, and some features, such
+as printing, actually work better on Windows than native Unix and Mac
+OS X. The mailing list at ＠email{xemacs-winnt＠(a)xemacs.org} is dedicated
+to that effort (please use the -request address to
+subscribe). (Despite its name, XEmacs actually works on all versions
+of Windows.)
+
+The list name is misleading, as XEmacs supports and has been compiled on
+Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
+XP, and all newer versions of Windows. The MS Windows-specific code is
+based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
+MS-DOS.
+
+XEmacs also supports the Cygwin and MinGW development and runtime
+environments, where it also uses native Windows code for graphical
+features. In addition, under Cygwin it is possible to compile XEmacs
+to use an X server (and XFree86 is available as part of the standard
+Cygwin installation).
+
+＠node Q1.2.4, Q1.2.5, Q1.2.3, Introduction
+＠unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to?
+
+Yes, you can, but no you do not need to. In fact, we recommend that you
+use a native-GUI version unless you have a specific need for an X
+version.
+
+＠node Q1.2.5, Q1.2.6, Q1.2.4, Introduction
+＠unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs?
+
+To answer the second part of the question: No, you, you don't need
+Cygwin or MinGW to build or to run XEmacs. But if you have them and
+want to use them, XEmacs supports these environments.
+
+(One important reason to support Cygwin is that it lets the MS Windows
+developers test out their code in a Unix environment without actually
+having to have a Unix machine around. For this reason alone, Cygwin
+support is likely to remain supported for a long time in XEmacs. Same
+goes for the X support under Cygwin, for the same reasons. MinGW
+support, on the other hand, depends on volunteers to keep it up to date;
+but this is generally not hard.)
+
+Cygwin is a set of tools providing Unix-like API on top of Win32.
+It makes it easy to port large Unix programs without significant
+changes to their source code. It is a development environment as well
+as a runtime environment.
+
+When built with Cygwin, XEmacs supports all display types -- TTY, X &
+Win32 GUI, and can be built with support for all three simultaneously.
+If you build with Win32 GUI support then the Cygwin version uses the
+majority of the Windows-specific code, which is mostly related to
+display. If you want to build with X support you need X libraries (and
+an X server to display XEmacs on); see ＠ref{Q2.2.7}. TTY and Win32 GUI
+require no additional libraries beyond what comes standard with Cygwin.
+
+The advantages of the Cygwin version are that it integrates well with
+the Cygwin environment for existing Cygwin users; uses configure so
+building with different features is very easy; and actively supports X &
+TTY. Furthermore, the entire Cygwin environment and compiler are free,
+whereas Visual C++ costs money.
+
+The disadvantage is that it requires the whole Cygwin environment,
+whereas the native port requires only a suitable MS Windows compiler.
+Also, it follows the Unix filesystem and process model very closely
+(some will undoubtedly view this as an advantage).
+
+See ＠uref{http://www.cygwin.com/} for more information on
+Cygwin.
+
+MinGW is a collection of header files and import libraries that allow
+one to use GCC under the Cygwin environment to compile and produce
+exactly the same native Win32 programs that you can using Visual C++.
+Programs compiled with MinGW make use of the standard Microsoft runtime
+library ＠file{MSVCRT.DLL}, present on all Windows systems, and look,
+feel, and act like a standard Visual-C-produced application. (The only
+difference is the compiler.) This means that, unlike a
+standardly-compiled Cygwin application, no extra runtime support
+(e.g. Cygwin's ＠file{cygwin1.dll}) is required. This, along with the
+fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
+environment, for those die-hard Unix hackers out there), is the main
+advantage of MinGW. It is also potentially faster than Cygwin because
+it has less overhead when calling Windows, but you lose the POSIX
+emulation layer, which makes Unix programs harder to port. (But this is
+irrelevant for XEmacs since it's already ported to Win32.)
+
+See ＠uref{http://www.mingw.org/} for more information on MinGW.
+
+＠node Q1.2.6, Q1.2.7, Q1.2.5, Introduction
+＠unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen?
+
+XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
+Could you briefly explain the differences between them?
+
+Here is a recount of various Emacs versions running on MS Windows:
+
+＠itemize ＠bullet
+
+＠item
+XEmacs
+
+＠itemize ＠minus
+
+＠item
+Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
+in such a way to allow clean support of multiple window systems. At
+this time the TTY support was added, making X and TTY the first two
+"window systems" supported by XEmacs. The 19.12 design is the basis for
+the current native MS Windows code.
+
+＠item
+Some time during 1997, David Hobley (soon joined by Marc Paquette)
+imported some of the NT-specific portions of GNU Emacs, making XEmacs
+with X support compile under Windows NT, and creating the "X" port.
+
+＠item
+Several months later, Jonathan Harris sent out initial patches to use
+the Win32 API, thus creating the native port. Since then, various
+people have contributed, including Kirill M. Katsnelson (contributed
+support for menubars, subprocesses and network, as well as loads of
+other code), Andy Piper (ported XEmacs to Cygwin environment,
+contributed Windows unexec, Windows-specific glyphs and toolbars code,
+and more), Ben Wing (loads of improvements; primary MS Windows developer
+since 2000), Jeff Sparkes (contributed scrollbars support) and many
+others.
+＠end itemize
+
+＠item
+NT Emacs
+
+＠itemize ＠minus
+
+＠item
+NT Emacs was an early version of GNU Emacs 19 modified to compile and
+run under MS Windows 95 and NT using the native Win32 API. It was
+written by Geoff Voelker, and has long since been incorporated into
+the mainline GNU Emacs distribution.
+＠end itemize
+
+＠item
+Win-Emacs
+
+＠itemize ＠minus
+
+＠item
+Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
+compatibility libraries. Win-Emacs was written by Ben Wing. The MS
+Windows code never made it back to Lucid Emacs, and its creator (Pearl
+Software) has long since gone out of business.
+＠end itemize
+
+＠item
+GNU Emacs for DOS
+
+＠itemize ＠minus
+
+＠item
+GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
+port of GCC). Such an Emacs is heavily underfeatured, because it does
+not support long file names, lacks proper subprocesses support, and
+is far too big compared with typical DOS editors.
+＠end itemize
+
+＠item
+GNU Emacs compiled with Win32
+
+＠itemize ＠minus
+
+＠item
+Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
+under MS Windows using the DJGPP compiler and X libraries. The result
+is very similar to GNU Emacs compiled under MS DOS, only it works
+somewhat better because it runs in 32-bit mode, makes use of all the
+system memory, supports long file names, etc.
+＠end itemize
+
+＠end itemize
+
+＠node Q1.2.7, Q1.2.8, Q1.2.6, Introduction
+＠unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface?
+
+The XEmacs (and Emacs in general) user interface is pretty different
+from what is expected of a typical MS Windows program. How does the MS
+Windows port cope with it?
+
+As a general rule, we follow native MS Windows conventions as much as
+possible. 21.4 is a fairly complete Windows application, supporting
+native printing, system file dialog boxes, tool tips, etc. In cases
+where there's a clear UI conflict, we currently use normal Unix XEmacs
+behavior by default, but make sure the MS Windows "look and feel" (mark
+via shift-arrow, self-inserting deletes region, Alt selects menu items,
+etc.) is easily configurable (respectively: using the variable
+＠code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
+the default in these versions], or the ＠file{pc-select} package; using
+the ＠file{pending-del} package; and setting the variable
+＠code{menu-accelerator-enabled} to ＠code{menu-force} in 21.4 and above).
+In fact, if you use the sample ＠file{init.el} file as your init file,
+you will get all these behaviors automatically turned on.
+
+In future versions, some of these features might be turned on by
+default in the MS Windows environment.
+
+＠node Q1.2.8, Q1.2.9, Q1.2.7, Introduction
+＠unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh?
+
+Yes.
+
+XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
+will not feel very much like a Mac application as it has no Mac-specific
+code in it.
+
+There is also a port of XEmacs 19.14 that works on all recent versions
+of MacOS, from 8.1 through MacOS X, by ＠email{pjarvis＠(a)ispchannel.com,
+Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
+mode only (one single Macintosh window, 25 colors), but has a large
+number of Mac-specific additions. It's available at
+＠uref{http://homepage.mac.com/pjarvis/xemacs.html}.
+
+＠node Q1.2.9, Q1.2.10, Q1.2.8, Introduction
+＠unnumberedsubsec Q1.2.9: Is there a port of XEmacs to the Macintosh?
+
+Yes.
+
+XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
+will not feel very much like a Mac application as it has no Mac-specific
+code in it.
+
+There is also a port of XEmacs 19.14 that works on all recent versions
+of MacOS, from 8.1 through MacOS X, by ＠email{pjarvis＠(a)ispchannel.com,
+Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
+mode only (one single Macintosh window, 25 colors), but has a large
+number of Mac-specific additions. It's available at
+＠uref{http://homepage.mac.com/pjarvis/xemacs.html}.
+
+＠node Q1.2.10, Q1.2.11, Q1.2.9, Introduction
+＠unnumberedsubsec Q1.2.10: Is there a port of XEmacs to MS-DOS?
+
+No. We have never supported running on MS-DOS or Windows 3.1, and in
+fact have long since deleted all MS-DOS-related code.
+
+＠node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
+＠unnumberedsubsec Q1.2.11: Is there a port of XEmacs to OS/2?
+
+No, but Alexander Nikolaev <avn_1251＠(a)mail.ru> was at one point
+working on it.
+
+＠node Q1.2.12, Q1.2.13, Q1.2.11, Introduction
+＠unnumberedsubsec Q1.2.12: Is there a port of XEmacs to NextStep?
+
+Carl Edman, apparently no longer at ＠email{cedman＠(a)princeton.edu}, did
+the port of GNU Emacs to NeXTstep and expressed interest in doing the
+XEmacs port, but never went any farther.
+
+＠node Q1.2.13, Q1.3.1, Q1.2.12, Introduction
+＠unnumberedsubsec Q1.2.13: Is there a port of XEmacs to VMS?
+
+VMS has never been supported by XEmacs. In fact, all the old VMS code
+inherited from GNU Emacs has been removed. Sorry, all you VMS fans
+out there.
+
+＠unnumberedsec 1.3: Getting Started
+
+＠node Q1.3.1, Q1.3.2, Q1.2.13, Introduction
+＠unnumberedsubsec Q1.3.1: What is an ＠file{init.el} or ＠file{.emacs} and is there a sample one?
+
+The ＠file{init.el} or ＠file{.emacs} file is used to customize XEmacs to
+your tastes. Starting in 21.4, the preferred location for the init file
+is ＠file{~/.xemacs/init.el}; in previous versions, it was
+(a)file{~/.emacs}. 21.4 still accepts the old location, but the first
+time you run it, it will ask to migrate your file to the new location.
+If you answer yes, the file will be moved, and a "compatibility"
+(a)file{.emacs} file will be placed in the old location so that you can
+still run older versions of XEmacs, and versions of GNU Emacs, which
+expect the old location. The ＠file{.emacs} file present is just a stub
+that loads the real file in ＠file{~/.xemacs/init.el}.
+
+No two init files are alike, nor are they expected to be alike, but
+that's the point. The XEmacs distribution contains an excellent starter
+example in the ＠file{etc/} directory called ＠file{sample.init.el}
+(starting in 21.4) or ＠file{sample.emacs} in older versions. Copy this
+file from there to ＠file{~/.xemacs/init.el} (starting in 21.4) or
+(a)file{~/.emacs} in older versions, where ＠samp{~} means your home
+directory, of course. Then edit it to suit.
+
+You may bring the ＠file{sample.init.el} or ＠file{sample.emacs} file into
+an XEmacs buffer from the menubar. (The menu entry for it is always
+under the ＠samp{Help} menu, but its location under that has changed in
+various versions. Recently, look under the ＠samp{Samples} submenu.) To
+determine the location of the ＠file{etc/} directory type the command
+＠kbd{C-h v data-directory ＠key{RET}}.
+
+＠node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
+＠unnumberedsubsec Q1.3.2: Where do I put my ＠file{init.el} file?
+
+(a)file{init.el} is the name of the init file starting with 21.4, and is
+located in the subdirectory ＠file{.xemacs/} of your home directory. In
+prior versions, the init file is called ＠file{.emacs} and is located in
+your home directory.
+
+Your home directory under Windows is determined by the ＠samp{HOME}
+environment variable. If this is not set, it defaults to ＠samp{C:\}.
+To set this variable, modify ＠file{AUTOEXEC.BAT} under Windows 95/98, or
+select ＠samp{Control Panel->System->Advanced->Environment Variables...}
+under Windows NT/2000.
+
+＠node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
+＠unnumberedsubsec Q1.3.3: Can I use the same ＠file{init.el} with the other Emacs?
+
+Yes. The sample ＠file{init.el} included in the XEmacs
+distribution will show you how to handle different versions and flavors
+of Emacs.
+
+＠node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
+＠unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around?
+
+There's the XEmacs tutorial available from the Help Menu under
+＠samp{Help->Tutorials}, or by typing ＠kbd{C-h t}. To check whether
+it's available in a non-english language, type ＠kbd{C-u C-h t TAB}, type
+the first letters of your preferred language, then type ＠key{RET}.
+
+＠comment There's an Emacs Lisp tutorial at
+＠comment
+＠comment ＠example
+＠comment ＠uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
+＠comment ＠end example
+＠comment
+＠comment ＠email{erik＠(a)petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
+＠comment page at
+＠comment ＠iftex
+＠comment ＠*
+＠comment ＠end iftex
+＠comment ＠uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
+
+＠node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
+＠unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function?
+
+The following function does a little bit of everything useful. It does
+something with the prefix argument, it examines the text around the
+cursor, and it's interactive so it may be bound to a key. It inserts
+copies of the current word the cursor is sitting on at the cursor. If
+you give it a prefix argument: ＠kbd{C-u 3 M-x double-word} then it will
+insert 3 copies.
+
+＠lisp
+(defun double-word (count)
+ "Insert a copy of the current word underneath the cursor"
+ (interactive "*p")
+ (let (here there string)
+ (save-excursion
+ (forward-word -1)
+ (setq here (point))
+ (forward-word 1)
+ (setq there (point))
+ (setq string (buffer-substring here there)))
+ (while (>= count 1)
+ (insert string)
+ (decf count))))
+＠end lisp
+
+The best way to see what is going on here is to let XEmacs tell you.
+Put the code into an XEmacs buffer, and do a ＠kbd{C-h f} with the cursor
+sitting just to the right of the function you want explained. Eg. move
+the cursor to the SPACE between ＠code{interactive} and ＠samp{"*p"} and
+hit ＠kbd{C-h f} to see what the function ＠code{interactive} does. Doing
+this will tell you that the ＠code{*} requires a writable buffer, and
+＠code{p} converts the prefix argument to a number, and
+＠code{interactive} allows you to execute the command with ＠kbd{M-x}.
+
+＠node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
+＠unnumberedsubsec Q1.3.6: And how do I bind it to a key?
+
+To bind to a key do:
+
+＠lisp
+(global-set-key "\C-cd" 'double-word)
+＠end lisp
+
+Or interactively, ＠kbd{M-x global-set-key} and follow the prompts.
+
+＠node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
+＠unnumberedsubsec Q1.3.7: What's the difference between a macro and a function?
+
+Quoting from the Lisp Reference (a.k.a ＠dfn{Lispref}) Manual:
+
+＠dfn{Macros} enable you to define new control constructs and other
+language features. A macro is defined much like a function, but instead
+of telling how to compute a value, it tells how to compute another Lisp
+expression which will in turn compute the value. We call this
+expression the ＠dfn{expansion} of the macro.
+
+Macros can do this because they operate on the unevaluated expressions
+for the arguments, not on the argument values as functions do. They can
+therefore construct an expansion containing these argument expressions
+or parts of them.
+
+Do not confuse the two terms with ＠dfn{keyboard macros}, which are
+another matter, entirely. A keyboard macro is a key bound to several
+other keys. Refer to manual for details.
+
+＠node Q1.3.8, Q1.4.1, Q1.3.7, Introduction
+＠unnumberedsubsec Q1.3.8: What is ＠code{Custom}?
+
+＠code{Custom} is a system for customizing XEmacs options.
+
+You can access ＠code{Advanced (Customize)} from the ＠code{Options} menu
+or invoking one of customize commands by typing eg.
+＠kbd{M-x customize}, ＠kbd{M-x customize-face},
+＠kbd{M-x customize-variable} or ＠kbd{M-x customize-apropos}.
+
+There is also new ＠samp{browser} mode for Customize.
+Try it out with ＠kbd{M-x customize-browse}
+
+＠unnumberedsec 1.4: Getting Help
+
+＠node Q1.4.1, Q1.4.2, Q1.3.8, Introduction
+＠unnumberedsubsec Q1.4.1: Where can I get help?
+
+Probably the easiest way, if everything is installed, is to use Info, by
+pressing ＠kbd{C-h i}, or looking for an Info item on the
+Help Menu. ＠kbd{M-x apropos} can be used to look for particular commands.
+
+For items not found in the manual, try reading this FAQ
+and reading the Usenet group comp.emacs.xemacs.
+
+If you choose to post to a newsgroup, ＠strong{please use
+comp.emacs.xemacs}. Please do not post XEmacs related questions to
+gnu.emacs.help.
+
+If you cannot post or read Usenet news, there is a corresponding mailing
+list ＠email{xemacs-news＠(a)xemacs.org} which is available. It can be
+subscribed to via the Mailman Web interface or by sending mail to to
+＠email{xemacs-news-request＠(a)xemacs.org} with ＠samp{subscribe} in the
+body of the message. See also
+＠uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
+subscription, you may use the ＠email{xemacs-news-request＠(a)xemacs.org}
+address or the Web interface. Send a message with a subject of
+＠samp{unsubscribe} to be removed.
+
+＠node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
+＠unnumberedsubsec Q1.4.2: Which mailing lists are there?
+
+For complete, up-to-date info on the lists and how to subscribe, see
+＠uref{http://www.xemacs.org/Lists/}.
+
+＠table ＠samp
+
+＠item comp.emacs.xemacs
+is a Usenet newsgroup
+for XEmacs users to discuss problems and issues that arise
+for them. It's not generally an appropriate place to ask
+about apparent bugs (use ＠samp{xemacs-beta}), or future plans
+(use ＠samp{xemacs-design}).
+
+＠item xemacs-announce
+is a read-only, low
+volume list for announcements concerning the XEmacs project
+and new releases of the XEmacs software.
+
+＠item xemacs-beta
+is an open list for bug
+reports about beta versions of XEmacs. This includes the bug
+reports themselves, by both users and developers, as well as
+queries, follow-ups, and discussions further determining their
+nature and status. This is the primary channel for this kind
+of discussion; related code changes will usually not be
+applied until they have been discussed here. When such
+discussions touch on significant changes to the code (in
+particular, structural changes), or on changes to API's or
+external functionality, they should be moved to
+＠samp{xemacs-design}. Requests and proposals for
+non-bug-related changes do not belong on ＠samp{xemacs-beta},
+and should be sent to ＠samp{xemacs-design} instead.
+
+＠item xemacs-beta-ja
+is an open list for bug
+reports and design discussion related to Mule features,
+including Japanese handling, in beta versions of XEmacs.
+Japanese is the preferred language of discussion. For most
+timely presentation to reviewers, please consider sending
+appropriate discussion to ＠samp{xemacs-mule} or
+＠samp{xemacs-design} in English when convenient for
+the participants in discussion. When possible, bug reports
+not related to Mule (including Japanese) should be reported on
+＠samp{xemacs-beta} in English.
+
+＠item xemacs-buildreports
+is an open list for
+submission of build-reports on beta versions of XEmacs. For
+information on what the build-reports should contain, please
+see the `etc/BETA' file which is included in each beta
+distribution.
+
+＠item xemacs-cvs
+is a read-only list for notices
+and information on what has been committed to the XEmacs CVS
+trees, by whom, and for what.
+
+＠item xemacs-design
+is an open list for
+discussing the design of XEmacs. This includes discussion
+about planned and ongoing changes to functionality and API
+changes and additions as well as requests for them. This is
+the primary channel for this kind of discussion; related code
+changes will usually not be applied until they have been
+discussed here. This does not include bug reports, which go
+to ＠samp{xemacs-beta}.
+
+＠item xemacs-mule
+is an open mailing list for
+discussion of International extensions to XEmacs including
+Mule, XIM, I18n issues, etc, and is not confined to
+developmental issues. This list is not restricted to
+English, postings in all languages are welcome.
+
+＠item xemacs-news
+is an open list for discussion
+and bug reporting for XEmacs. This mailing list is
+bi-directionally gatewayed with the USENET newsgroup
+comp.emacs.xemacs.
+
+＠item xemacs-nt
+is a developers-only mailing
+list and is intended for people who wish to work actively on
+the porting of XEmacs to Microsoft Windows NT and Microsoft
+Windows '95.
+
+＠item xemacs-patches
+is an open, moderated
+list for submission of patches to the XEmacs distribution
+and its packages. Anyone may subscribe or submit to
+xemacs-patches, but all submissions are reviewed by the list
+moderator before they are distributed to the
+list. Discussion is not appropriate on xemacs-patches.
+
+＠item xemacs-users-ja
+is an open list for
+discussion and bug reporting for XEmacs. Japanese is the
+preferred language of discussion. It is not gated to
+comp.emacs.xemacs or the ＠samp{xemacs} list. For
+fastest response, bugs not specifically related to Japanese
+or Mule features should be reported on
+＠samp{xemacs-beta} (in English).
+
+＠item xemacs-users-ru
+is an open list for
+discussion and bug reporting for XEmacs. Russian is the
+preferred language of discussion. It is not gated to
+comp.emacs.xemacs or the ＠samp{xemacs} list. For
+fastest response, bugs not specifically related to Russian
+or Mule features should be reported on
+＠samp{xemacs-beta} (in English).
+＠end table
+
+＠node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
+＠unnumberedsubsec Q1.4.3: Where are the mailing lists archived?
+
+The archives can be found at ＠uref{http://list-archive.xemacs.org}
+
+＠node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
+＠unnumberedsubsec Q1.4.4: How can I get two instances of info?
+
+Before 21.4, you can't. The ＠code{info} package does not provide for
+multiple info buffers. In 21.4, this should be fixed. #### how?
+
+＠node Q1.4.5, Q1.5.1, Q1.4.4, Introduction
+＠unnumberedsubsec Q1.4.5: How do I add new Info directories?
+
+You use something like:
+
+＠lisp
+(setq Info-directory-list (cons
+ (expand-file-name "~/info")
+ Info-default-directory-list))
+＠end lisp
+
+＠email{davidm＠(a)prism.kla.com, David Masterson} writes:
+
+＠quotation
+Emacs Info and XEmacs Info do many things differently. If you're trying to
+support a number of versions of Emacs, here are some notes to remember:
+
+＠enumerate
+＠item
+Emacs Info scans ＠code{Info-directory-list} from right-to-left while
+XEmacs Info reads it from left-to-right, so append to the ＠emph{correct}
+end of the list.
+
+＠item
+Use ＠code{Info-default-directory-list} to initialize
+＠code{Info-directory-list} ＠emph{if} it is available at startup, but not
+all Emacsen define it.
+
+＠item
+Emacs Info looks for a standard ＠file{dir} file in each of the
+directories scanned from #1 and magically concatenates them together.
+
+＠item
+XEmacs Info looks for a ＠file{localdir} file (which consists of just the
+menu entries from a ＠file{dir} file) in each of the directories scanned
+from #1 (except the first), does a simple concatenation of them, and
+magically attaches the resulting list to the end of the menu in the
+＠file{dir} file in the first directory.
+＠end enumerate
+
+Another alternative is to convert the documentation to HTML with
+texi2html and read it from a web browser like Lynx or W3.
+＠end quotation
+
+＠unnumberedsec 1.5: Contributing to XEmacs
+
+＠node Q1.5.1, Q1.5.2, Q1.4.5, Introduction
+＠unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ?
+
+The FAQ is actively maintained and modified regularly. All links should
+be up to date. Unfortunately, some of the information is out of date --
+a situation which the FAQ maintainer is working on. All submissions are
+welcome, please e-mail submissions to ＠email{faq＠(a)xemacs.org, XEmacs FAQ
+maintainers}.
+
+Please make sure that ＠samp{XEmacs FAQ} appears on the Subject: line.
+If you think you have a better way of answering a question, or think a
+question should be included, we'd like to hear about it. Questions and
+answers included into the FAQ will be edited for spelling and grammar
+and will be attributed. Answers appearing without attribution are
+either from versions of the FAQ dated before May 1996 or are from
+previous FAQ maintainers. Answers quoted from Usenet news articles will
+always be attributed, regardless of the author.
+
+＠node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
+＠unnumberedsubsec Q1.5.2: How do I become a beta tester?
+
+Send an email message to ＠email{xemacs-beta-request＠(a)xemacs.org} with
+the line ＠samp{subscribe} in the body of the message.
+
+Be prepared to get your hands dirty, as beta testers are expected to
+identify problems as best they can.
+
+＠node Q1.5.3, Q1.6.1, Q1.5.2, Introduction
+＠unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself?
+
+It depends on the knowledge and time you possess. If you are able, by
+all means become a beta tester (＠pxref{Q1.5.2}). If you are a
+programmer, try to build XEmacs and see if you can improve it.
+
+Otherwise, you can still help by using XEmacs as your everyday editor
+(for pre-built binary versions, ＠pxref{Q1.1.2}) and reporting bugs you
+find to the mailing list.
+
+Another area where we need help is the documentation: We need good
+documentation for building XEmacs and for using it. This FAQ is a
+small step in that direction.
+
+Ben Wing ＠email{ben＠(a)xemacs.org} writes:
+
+＠quotation
+BTW if you have a wish list of things that you want added, you have to
+speak up about it! More specifically, you can do the following if you
+want a feature added (in increasing order of usefulness):
+
+＠itemize ＠bullet
+＠item
+Make a posting about a feature you want added.
+
+＠item
+Become a beta tester and make more postings about those same features.
+
+＠item
+Convince us that you're going to use the features in some cool and
+useful way.
+
+＠item
+Come up with a clear and well-thought-out API concerning the features.
+
+＠item
+Write the code to implement a feature and send us a patch.
+＠end itemize
+
+(not that we're necessarily requiring you to write the code, but we can
+always hope :)
+＠end quotation
+
+＠unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs)
+
+＠node Q1.6.1, Q1.6.2, Q1.5.3, Introduction
+＠unnumberedsubsec Q1.6.1: What is GNU Emacs?
+
+GNU Emacs and XEmacs are related open-source text editors. Both
+derive from GNU Emacs version 18; the split between the two happened
+in 1991 (for comparison, the oldest versions of GNU Emacs date from
+1984). For information on GNU Emacs, see
+＠uref{http://www.gnu.org/software/emacs/emacs.html}.
+
+＠node Q1.6.2, Q1.6.3, Q1.6.1, Introduction
+＠unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs?
+
+For a detailed description of the differences between GNU Emacs and
+XEmacs and a detailed history of XEmacs, check out the
+＠example
+＠uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
+＠end example
+
+＠table ＠strong
+＠item User-Visible Editing Features
+XEmacs in general tries hard to conform to exist user-interface
+standards, and to work "out-of-the-box" without the need for obscure
+customization changes. GNU Emacs, particularly version 21, has gotten
+better about this (in many cases by copying the XEmacs behavior!), but
+still has some weirdnesses. For example, the standard method of
+selecting text using the Shift key works out-of-the-box in XEmacs.
+
+XEmacs has a built-in toolbar. Four toolbars can actually be configured
+simultaneously: top, bottom, left, and right toolbars.
+
+XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19
+(which provides a primitive form of vertical scrollbar), these are true
+toolkit scrollbars. A look-alike Motif scrollbar is provided for those
+who don't have Motif. (Even for those who do, the look-alike may be
+preferable as it is faster.)
+
+XEmacs has buffer tabs along the top of the frame (although the
+position can be changed) that make it very easy to switch buffers.
+
+The menubar under XEmacs is better-designed, with more thought put into
+it.
+
+XEmacs can ask questions using popup dialog boxes. Any command executed
+from a menu will ask yes/no questions with dialog boxes, while commands
+executed via the keyboard will use the minibuffer.
+
+XEmacs under MS Windows provides uses the standard file-dialog box for
+opening and saving files. Standard menu-accelerator behavior can easily
+be enabled using the Options menu, and integrates well into the existing
+keymap.
+
+XEmacs has (still experimental) support for widgets of various sorts --
+buttons, text boxes, sliders, progress bars, etc. A progress bar is
+used in font lock to show the progress.
+
+Experimental support for drag-and-drop protocols is provided from
+XEmacs 21.
+
+＠item General Platform Support
+If you're running on a machine with audio hardware, you can specify
+sound files for XEmacs to play instead of the default X beep. See the
+documentation of the function load-sound-file and the variable
+sound-alist. XEmacs also supports the network sound protocols NAS and
+EsounD.
+
+XEmacs 21 supports database protocols with LISP bindings, currently
+including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
+
+XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
+servers directly, as well as through the X Input Method (XIM)
+protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
+support the Quail family of input methods (implemented in LISP) for many
+languages.
+
+XEmacs provides support for ToolTalk on systems that have
+it.
+
+＠item Packaged LISP Libraries
+Many more packages are provided standard with XEmacs than with GNU Emacs
+19 or 20.
+
+XEmacs 21 supports an integrated package management system which uses
+EFS to download, then automatically install prebuilt LISP
+libraries. This allows XEmacs users much more straightforward access to
+the "latest and greatest" version of any given library.
+
+We are working on a standard method for enabling, disabling and
+otherwise controlling packages, which should make them very easy to use.
+
+＠item LISP Programming
+From XEmacs 20 on, characters are a separate type. Characters can be
+converted to integers (and many integers can be converted to
+characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
+Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
+20 (incorporating Mule 3 and later Mule 4) represent them as integers.
+
+From XEmacs 20 on, the buffer is treated as an array of characters, and
+the representation of buffer text is not exposed to LISP. The GNU Emacs
+20 functions like buffer-as-multibyte are not supported.
+
+In XEmacs, events are first-class objects. GNU Emacs 19 represents them
+as integers, which obscures the differences between a key gesture and
+the ancient ASCII code used to represent a particular overlapping subset
+of them.
+
+In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19
+represents them as complicated combinations of association lists and
+vectors. If you use the advertised functional interface to manipulation
+of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU
+Emacs 19; if your code depends on the underlying implementation of
+keymaps, it will not.
+
+XEmacs uses "extents" to represent all non-textual aspects of buffers;
GNU Emacs 19 uses two distinct objects, "text properties" and
"overlays", which divide up the functionality between them. Extents are
a superset of the union of the functionality of the two GNU Emacs data
＠＠ -850,11 +1948,11 ＠＠ LISP libraries who are willing to mainta
automatically qualify for CVS accounts for their packages.
＠end table
-＠node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
-＠unnumberedsubsec Q1.0.6: How much does XEmacs differ?
+＠node Q1.6.3, Q1.6.4, Q1.6.2, Introduction
+＠unnumberedsubsec Q1.6.3: How much does XEmacs differ?
RMS has asserted at times that XEmacs is merely a "patch" on top of
-GNU Emacs (＠pxref{Q1.0.7}). In fact, probably not more than 5% of the
+GNU Emacs (＠pxref{Q1.6.4}). In fact, probably not more than 5% of the
code, if that, remains unchanged, and nearly 14 years of work has gone
into XEmacs at this point. (GNU Emacs itself is only than 20 years
old, and thus XEmacs has existed as a separate product for over 2/3 of
＠＠ -870,8 +1968,8 ＠＠ developers are instructed by RMS not to
This stems from self-imposed licensing restrictions on the part of GNU
Emacs -- and almost certainly out of hostility, as well.)
-＠node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
-＠unnumberedsubsec Q1.0.7: Is XEmacs "GNU"?
+＠node Q1.6.4, Q1.6.5, Q1.6.3, Introduction
+＠unnumberedsubsec Q1.6.4: Is XEmacs "GNU"?
RMS insists on the term "GNU XEmacs" and maintains that
＠＠ -884,7 +1982,7 ＠＠ is why the term "GNU XEmacs" is legitima
＠end quotation
In fact, FSF is ＠emph{not} the copyright holder for most of the code,
-as very little unmodified FSF code remains (＠pxref{Q1.0.6}).
+as very little unmodified FSF code remains (＠pxref{Q1.6.3}).
Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre
to the XEmacs developers given RMS's hostility and general lack of
＠＠ -897,8 +1995,8 ＠＠ from an endorsement. In fact, the GNU P
non-GNU software projects on the FSF web site, but again XEmacs is not
one of them.
-＠node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
-＠unnumberedsubsec Q1.0.8: What is the correct way to refer to XEmacs and GNU Emacs?
+＠node Q1.6.5, Q1.6.6, Q1.6.4, Introduction
+＠unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs?
Unfortunately even the naming of these two applications has become
politicized. Much of this stems from RMS, who has a history of
＠＠ -907,12 +2005,12 ＠＠ and "GNU/Linux".) We would prefer that t
Emacs" be used, which are neutral and acceptable to most people. RMS,
however, is not willing to accept these terms. He insists that, if
his product is called "GNU Emacs", then ours must be called "GNU
-XEmacs". (For our opinion of this term, ＠xref{Q1.0.7}.) On the other
+XEmacs". (For our opinion of this term, ＠xref{Q1.6.4}.) On the other
hand, if our product is to be called "XEmacs", as we prefer, then his
product must simply be called "Emacs". The intent of this seems
clear: RMS wants to make sure the names reflect his view that his
version is the "real" Emacs and ours is merely a derivative,
-second-class product (＠pxref{Q1.0.6}).
+second-class product (＠pxref{Q1.6.3}).
The XEmacs developers hope that you will use the neutral terms
"XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on
＠＠ -933,8 +2031,8 ＠＠ Emacs, produced by James Gosling. RMS,
to be insulting, so we refrain from using them as much as possible in
preference to GNU Emacs.)
-＠node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
-＠unnumberedsubsec Q1.0.9: Why haven't XEmacs and GNU Emacs merged?
+＠node Q1.6.6, Q1.7.1, Q1.6.5, Introduction
+＠unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged?
There are currently irreconcilable differences in the views about
technical, programming, design, organizational and legal matters
＠＠ -1013,656 +2111,426 ＠＠ If you have a comment to add regarding t
avoid posting to the newsgroups, because of the very heated flamewars
that often result. Mail your questions to
＠email{xemacs-beta＠(a)xemacs.org} and ＠email{emacs-devel＠(a)gnu.org}.
-
-＠node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
-＠unnumberedsubsec Q1.0.10: Where can I get help?
-
-Probably the easiest way, if everything is installed, is to use Info, by
-pressing ＠kbd{C-h i}, or looking for an Info item on the
-Help Menu. ＠kbd{M-x apropos} can be used to look for particular commands.
-
-For items not found in the manual, try reading this FAQ
-and reading the Usenet group comp.emacs.xemacs.
-
-If you choose to post to a newsgroup, ＠strong{please use
-comp.emacs.xemacs}. Please do not post XEmacs related questions to
-gnu.emacs.help.
-
-If you cannot post or read Usenet news, there is a corresponding mailing
-list ＠email{xemacs-news＠(a)xemacs.org} which is available. It can be
-subscribed to via the Mailman Web interface or by sending mail to to
-＠email{xemacs-news-request＠(a)xemacs.org} with ＠samp{subscribe} in the
-body of the message. See also
-＠uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
-subscription, you may use the ＠email{xemacs-news-request＠(a)xemacs.org}
-address or the Web interface. Send a message with a subject of
-＠samp{unsubscribe} to be removed.
-
-＠node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
-＠unnumberedsubsec Q1.0.11: Where are the mailing lists archived?
-
-The archives can be found at ＠uref{http://list-archive.xemacs.org}
-
-＠node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
-＠unnumberedsubsec Q1.0.12: How do you pronounce XEmacs?
-
-The most common pronounciation is ＠samp{Eks eemax}.
-
-＠node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
-＠unnumberedsubsec Q1.0.13: What does XEmacs look like?
-
-Screen snapshots are available at
-＠uref{http://www.xemacs.org/About/Screenshots/index.html}
-as part of the XEmacs website.
-＠node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
-＠unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs User's Manual?
+＠unnumberedsec 1.7: External Packages
-Pre-printed manuals are not available. If you are familiar with
-TeX, you can generate your own manual from the XEmacs sources.
+＠node Q1.7.1, Q1.8.1, Q1.6.6, Introduction
+＠unnumberedsubsec Q1.7.1: Which external packages are there?
-HTML and Postscript versions of XEmacs manuals are available from the
-XEmacs web site at
-＠uref{http://www.xemacs.org/Documentation/index.html}.
+＠subheading Normal Packages
-＠unnumberedsec 1.1: Versions for Different Operating Systems
+A very broad collection of elisp packages.
-＠node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
-＠unnumberedsubsec Q1.1.1: Do I need X11 to run XEmacs?
+＠table ＠asis
+＠item Sun
+Support for Sparcworks.
-No. The name ＠dfn{XEmacs} is unfortunate in the sense that it is
-＠strong{not} an X Window System-only version of Emacs. XEmacs has
-full color support on a color-capable character terminal.
+＠item ada
+Ada language support.
-＠node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
-＠unnumberedsubsec Q1.1.2: Is there a port of XEmacs to Microsoft Windows?
+＠item apel
+A Portable Emacs Library. Used by XEmacs MIME support.
-Yes. Beginning with release 21.0, XEmacs has worked under MS Windows
-and is fully-featured and actively developed. A group of dedicated
-developers actively maintains and improves the Windows-specific
-portions of the code. Some of the core developers, in fact, use
-Windows as their only development environment, and some features, such
-as printing, actually work better on Windows than native Unix and Mac
-OS X. The mailing list at ＠email{xemacs-winnt＠(a)xemacs.org} is dedicated
-to that effort (please use the -request address to
-subscribe). (Despite its name, XEmacs actually works on all versions
-of Windows.)
+＠item auctex
+Basic TeX/LaTeX support.
-The list name is misleading, as XEmacs supports and has been compiled on
-Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
-XP, and all newer versions of Windows. The MS Windows-specific code is
-based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
-MS-DOS.
+＠item bbdb
+The Big Brother Data Base: a rolodex-like database program.
-XEmacs also supports the Cygwin and MinGW development and runtime
-environments, where it also uses native Windows code for graphical
-features. In addition, under Cygwin it is possible to compile XEmacs
-to use an X server (and XFree86 is available as part of the standard
-Cygwin installation).
+＠item build
+Build XEmacs from within (UNIX, Windows).
-＠node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
-＠unnumberedsubsec Q1.1.3: Can I build XEmacs on MS Windows with X support? Do I need to?
+＠item c-support
+Basic single-file add-ons for editing C code.
-Yes, you can, but no you do not need to. In fact, we recommend that you
-use a native-GUI version unless you have a specific need for an X
-version.
+＠item calc
+Emacs calculator.
-＠node Q1.1.4, Q1.1.5, Q1.1.3, Introduction
-＠unnumberedsubsec Q1.1.4: What are Cygwin and MinGW, and do I need them to run XEmacs?
+＠item calendar
+Calendar and diary support.
-To answer the second part of the question: No, you, you don't need
-Cygwin or MinGW to build or to run XEmacs. But if you have them and
-want to use them, XEmacs supports these environments.
+＠item cc-mode
+C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support.
-(One important reason to support Cygwin is that it lets the MS Windows
-developers test out their code in a Unix environment without actually
-having to have a Unix machine around. For this reason alone, Cygwin
-support is likely to remain supported for a long time in XEmacs. Same
-goes for the X support under Cygwin, for the same reasons. MinGW
-support, on the other hand, depends on volunteers to keep it up to date;
-but this is generally not hard.)
+＠item clearcase
+New Clearcase Version Control for XEmacs (UNIX, Windows).
-Cygwin is a set of tools providing Unix-like API on top of Win32.
-It makes it easy to port large Unix programs without significant
-changes to their source code. It is a development environment as well
-as a runtime environment.
+＠item clearcase
+Support for the Clearcase version control system.
-When built with Cygwin, XEmacs supports all display types -- TTY, X &
-Win32 GUI, and can be built with support for all three simultaneously.
-If you build with Win32 GUI support then the Cygwin version uses the
-majority of the Windows-specific code, which is mostly related to
-display. If you want to build with X support you need X libraries (and
-an X server to display XEmacs on); see ＠ref{Q2.2.7}. TTY and Win32 GUI
-require no additional libraries beyond what comes standard with Cygwin.
+＠item cookie
+"Fortune cookie"-style messages. Includes Spook (suspicious phrases)
+and Yow (Zippy quotes).
-The advantages of the Cygwin version are that it integrates well with
-the Cygwin environment for existing Cygwin users; uses configure so
-building with different features is very easy; and actively supports X &
-TTY. Furthermore, the entire Cygwin environment and compiler are free,
-whereas Visual C++ costs money.
+＠item crisp
+Crisp/Brief emulation.
-The disadvantage is that it requires the whole Cygwin environment,
-whereas the native port requires only a suitable MS Windows compiler.
-Also, it follows the Unix filesystem and process model very closely
-(some will undoubtedly view this as an advantage).
+＠item debug
+GUD, gdb, dbx debugging support.
-See ＠uref{http://www.cygwin.com/} for more information on
-Cygwin.
+＠item dictionary
+Interface to RFC2229 dictionary servers.
-MinGW is a collection of header files and import libraries that allow
-one to use GCC under the Cygwin environment to compile and produce
-exactly the same native Win32 programs that you can using Visual C++.
-Programs compiled with MinGW make use of the standard Microsoft runtime
-library ＠file{MSVCRT.DLL}, present on all Windows systems, and look,
-feel, and act like a standard Visual-C-produced application. (The only
-difference is the compiler.) This means that, unlike a
-standardly-compiled Cygwin application, no extra runtime support
-(e.g. Cygwin's ＠file{cygwin1.dll}) is required. This, along with the
-fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
-environment, for those die-hard Unix hackers out there), is the main
-advantage of MinGW. It is also potentially faster than Cygwin because
-it has less overhead when calling Windows, but you lose the POSIX
-emulation layer, which makes Unix programs harder to port. (But this is
-irrelevant for XEmacs since it's already ported to Win32.)
+＠item dired
+The DIRectory EDitor is for manipulating, and running commands on
+files in a directory.
-See ＠uref{http://www.mingw.org/} for more information on MinGW.
+＠item docbookide
+DocBook editing support.
-＠node Q1.1.5, Q1.1.6, Q1.1.4, Introduction
-＠unnumberedsubsec Q1.1.5: What are the differences between the various MS Windows emacsen?
+＠item ecb
+Emacs source code browser.
-XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
-Could you briefly explain the differences between them?
+＠item ecrypto
+Crypto functionality in Emacs Lisp.
-Here is a recount of various Emacs versions running on MS Windows:
+＠item edebug
+An Emacs Lisp debugger.
-＠itemize ＠bullet
+＠item ediff
+Interface over GNU patch.
-＠item
-XEmacs
+＠item edit-utils
+Miscellaneous editor extensions, you probably need this.
-＠itemize ＠minus
+＠item edt
+DEC EDIT/EDT emulation.
-＠item
-Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
-in such a way to allow clean support of multiple window systems. At
-this time the TTY support was added, making X and TTY the first two
-"window systems" supported by XEmacs. The 19.12 design is the basis for
-the current native MS Windows code.
+＠item efs
+Treat files on remote systems the same as local files.
-＠item
-Some time during 1997, David Hobley (soon joined by Marc Paquette)
-imported some of the NT-specific portions of GNU Emacs, making XEmacs
-with X support compile under Windows NT, and creating the "X" port.
+＠item eieio
+Enhanced Implementation of Emacs Interpreted Objects.
-＠item
-Several months later, Jonathan Harris sent out initial patches to use
-the Win32 API, thus creating the native port. Since then, various
-people have contributed, including Kirill M. Katsnelson (contributed
-support for menubars, subprocesses and network, as well as loads of
-other code), Andy Piper (ported XEmacs to Cygwin environment,
-contributed Windows unexec, Windows-specific glyphs and toolbars code,
-and more), Ben Wing (loads of improvements; primary MS Windows developer
-since 2000), Jeff Sparkes (contributed scrollbars support) and many
-others.
-＠end itemize
+＠item elib
+Portable Emacs Lisp utilities library.
-＠item
-NT Emacs
+＠item emerge
+Another interface over GNU patch.
-＠itemize ＠minus
+＠item erc
+ERC is an Emacs InternetRelayChat client.
-＠item
-NT Emacs was an early version of GNU Emacs 19 modified to compile and
-run under MS Windows 95 and NT using the native Win32 API. It was
-written by Geoff Voelker, and has long since been incorporated into
-the mainline GNU Emacs distribution.
-＠end itemize
+＠item escreen
+Multiple editing sessions withing a single frame (like screen).
-＠item
-Win-Emacs
+＠item eshell
+Command shell implemented entirely in Emacs Lisp.
-＠itemize ＠minus
+＠item ess
+ESS: Emacs Speaks Statistics.
-＠item
-Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
-compatibility libraries. Win-Emacs was written by Ben Wing. The MS
-Windows code never made it back to Lucid Emacs, and its creator (Pearl
-Software) has long since gone out of business.
-＠end itemize
+＠item eterm
+Terminal emulation.
-＠item
-GNU Emacs for DOS
+＠item eudc
+Emacs Unified Directory Client (LDAP, PH).
-＠itemize ＠minus
+＠item footnote
+Footnoting in mail message editing modes.
-＠item
-GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
-port of GCC). Such an Emacs is heavily underfeatured, because it does
-not support long file names, lacks proper subprocesses support, and
-is far too big compared with typical DOS editors.
-＠end itemize
+＠item forms
+Forms editing support (obsolete, use Widget instead).
-＠item
-GNU Emacs compiled with Win32
+＠item fortran-modes
+Fortran support.
-＠itemize ＠minus
+＠item fortran-modes
+Fortran language support.
-＠item
-Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
-under MS Windows using the DJGPP compiler and X libraries. The result
-is very similar to GNU Emacs compiled under MS DOS, only it works
-somewhat better because it runs in 32-bit mode, makes use of all the
-system memory, supports long file names, etc.
-＠end itemize
+＠item frame-icon
+Set up mode-specific icons for each frame under XEmacs.
-＠end itemize
+＠item fsf-compat
+GNU Emacs compatibility files.
-＠node Q1.1.6, Q1.1.7, Q1.1.5, Introduction
-＠unnumberedsubsec Q1.1.6: Is there a port of XEmacs to the Macintosh?
+＠item games
+Tetris, Sokoban, and Snake.
-Yes.
+＠item general-docs
+General documentation. Presently, empty.
-XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
-will not feel very much like a Mac application as it has no Mac-specific
-code in it.
+＠item gnats
+XEmacs bug reports.
-There is also a port of XEmacs 19.14 that works on all recent versions
-of MacOS, from 8.1 through MacOS X, by ＠email{pjarvis＠(a)ispchannel.com,
-Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
-mode only (one single Macintosh window, 25 colors), but has a large
-number of Mac-specific additions. It's available at
-＠uref{http://homepage.mac.com/pjarvis/xemacs.html}.
+＠item gnus
+The Gnus Newsreader and Mailreader.
-＠node Q1.1.7, Q1.1.8, Q1.1.6, Introduction
-＠unnumberedsubsec Q1.1.7: Is there a port of XEmacs to NextStep?
+＠item haskell-mode
+Haskell editing support.
-Carl Edman, apparently no longer at ＠email{cedman＠(a)princeton.edu}, did
-the port of GNU Emacs to NeXTstep and expressed interest in doing the
-XEmacs port, but never went any farther.
+＠item hm--html-menus
+HTML editing.
-＠node Q1.1.8, Q1.1.9, Q1.1.7, Introduction
-＠unnumberedsubsec Q1.1.8: Is there a port of XEmacs to OS/2?
+＠item hyperbole
+Hyperbole: The Everyday Info Manager.
-No, but Alexander Nikolaev <avn_1251＠(a)mail.ru> is working on it.
+＠item ibuffer
+Advanced replacement for buffer-menu.
-＠node Q1.1.9, Q1.2.1, Q1.1.8, Introduction
-＠unnumberedsubsec Q1.1.9: How does the port cope with differences in the Windows user interface?
+＠item idlwave
+Editing and Shell mode for the Interactive Data Language.
-The XEmacs (and Emacs in general) user interface is pretty different
-from what is expected of a typical MS Windows program. How does the MS
-Windows port cope with it?
+＠item igrep
+Enhanced front-end for Grep.
-As a general rule, we follow native MS Windows conventions as much as
-possible. 21.4 is a fairly complete Windows application, supporting
-native printing, system file dialog boxes, tool tips, etc. In cases
-where there's a clear UI conflict, we currently use normal Unix XEmacs
-behavior by default, but make sure the MS Windows "look and feel" (mark
-via shift-arrow, self-inserting deletes region, Alt selects menu items,
-etc.) is easily configurable (respectively: using the variable
-＠code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
-the default in these versions], or the ＠file{pc-select} package; using
-the ＠file{pending-del} package; and setting the variable
-＠code{menu-accelerator-enabled} to ＠code{menu-force} in 21.4 and above).
-In fact, if you use the sample ＠file{init.el} file as your init file,
-you will get all these behaviors automatically turned on.
+＠item ilisp
+Front-end for interacting with Inferior Lisp (external lisps).
-In future versions, some of these features might be turned on by
-default in the MS Windows environment.
+＠item ispell
+Spell-checking with GNU ispell.
-＠unnumberedsec 1.2: Policies
+＠item jde
+Integrated Development Environment for Java.
-＠node Q1.2.1, Q1.2.2, Q1.1.9, Introduction
-＠unnumberedsubsec Q1.2.1: What is the FAQ editorial policy?
+＠item liece
+IRC (Internet Relay Chat) client for Emacs. Note, this package is
+deprecated and will be removed, use riece instead.
-The FAQ is actively maintained and modified regularly. All links should
-be up to date. Unfortunately, some of the information is out of date --
-a situation which the FAQ maintainer is working on. All submissions are
-welcome, please e-mail submissions to ＠email{faq＠(a)xemacs.org, XEmacs FAQ
-maintainers}.
+＠item mail-lib
+Fundamental lisp files for providing email support.
-Please make sure that ＠samp{XEmacs FAQ} appears on the Subject: line.
-If you think you have a better way of answering a question, or think a
-question should be included, we'd like to hear about it. Questions and
-answers included into the FAQ will be edited for spelling and grammar
-and will be attributed. Answers appearing without attribution are
-either from versions of the FAQ dated before May 1996 or are from
-previous FAQ maintainers. Answers quoted from Usenet news articles will
-always be attributed, regardless of the author.
+＠item mailcrypt
+Support for messaging encryption with PGP.
-＠node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
-＠unnumberedsubsec Q1.2.2: How do I become a beta tester?
+＠item mew
+Messaging in an Emacs World; a MIME-based email program.
-Send an email message to ＠email{xemacs-beta-request＠(a)xemacs.org} with
-the line ＠samp{subscribe} in the body of the message.
+＠item mh-e
+The XEmacs Interface to the MH Mail System.
-Be prepared to get your hands dirty, as beta testers are expected to
-identify problems as best they can.
+＠item mine
+Elisp implementation of the game 'Minehunt'.
-＠node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
-＠unnumberedsubsec Q1.2.3: How do I contribute to XEmacs itself?
+＠item misc-games
+Other amusements and diversions.
-It depends on the knowledge and time you possess. If you are able, by
-all means become a beta tester (＠pxref{Q1.2.2}). If you are a
-programmer, try to build XEmacs and see if you can improve it.
+＠item mmm-mode
+Support for Multiple Major Modes within a single buffer.
-Otherwise, you can still help by using XEmacs as your everyday editor
-(for pre-built binary versions, ＠pxref{Q1.0.4}) and reporting bugs you
-find to the mailing list.
+＠item net-utils
+Miscellaneous Networking Utilities.
-Another area where we need help is the documentation: We need good
-documentation for building XEmacs and for using it. This FAQ is a
-small step in that direction.
+＠item ocaml
+Objective Caml editing support.
-Ben Wing ＠email{ben＠(a)xemacs.org} writes:
+＠item oo-browser
+OO-Browser: The Multi-Language Object-Oriented Code Browser.
-＠quotation
-BTW if you have a wish list of things that you want added, you have to
-speak up about it! More specifically, you can do the following if you
-want a feature added (in increasing order of usefulness):
+＠item ocaml
+Objective Caml editing support.
-＠itemize ＠bullet
-＠item
-Make a posting about a feature you want added.
+＠item os-utils
+Miscellaneous single-file O/S utilities, for printing, archiving,
+compression, remote shells, etc.
-＠item
-Become a beta tester and make more postings about those same features.
+＠item pc
+PC style interface emulation.
-＠item
-Convince us that you're going to use the features in some cool and
-useful way.
+＠item pcl-cvs
+CVS frontend.
-＠item
-Come up with a clear and well-thought-out API concerning the features.
+＠item pcomplete
+Provides programmatic completion.
-＠item
-Write the code to implement a feature and send us a patch.
-＠end itemize
+＠item perl-modes
+Perl support.
-(not that we're necessarily requiring you to write the code, but we can
-always hope :)
-＠end quotation
+＠item pgg
+Emacs interface to various PGP implementations.
-＠unnumberedsec 1.3: Credits
+＠item prog-modes
+Support for various programming languages.
-＠node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
-＠unnumberedsubsec Q1.3.1: Who wrote XEmacs?
+＠item ps-print
+Printing functions and utilities.
-XEmacs is the result of the time and effort of many people, and the
-active developers have changed over time. There are two major
-components of the XEmacs effort -- writing the code itself and providing
-all the support work (testing the code, releasing beta and final
-versions, handling patches, reading bug reports, maintaining the web
-site, managing the mailing lists, etc. etc.). Neither component would
-work without the other.
+＠item psgml
+Validated HTML/SGML editing.
-＠subheading CODING
+＠item psgml-dtds
+A collection of DTDs for psgml. Note that this package is deprecated
+and will be removed in the future, most likely Q2/2003. Instead of using
+this, you should install needed DTDs yourself.
-The primary code contributor over the years has been Ben Wing (active
-since late 1992). Between 1991 and 1995, large amounts of coding was
-contributed by Jamie Zawinski and Chuck Thompson. Many other people
-have authored major subsystems or otherwise contributed large amounts of
-code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
-Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
-Mlynarik, Stig, William Perry and plenty of others.
+＠item python-modes
+Python language support.
-Primary XEmacs-specific subsystems and their authors:
+＠item reftex
+Emacs support for LaTeX cross-references, citations.
-＠table ＠asis
-＠item Objects
-＠itemize ＠minus
-＠item
-Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
-＠item
-Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
-＠item
-Portable dumper, object descriptions: Olivier Galibert
-＠item
-KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
-＠item
-Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
-＠item
-Profiling: Ben Wing
-＠item
-Some byte-compilation and hash-table improvements: Martin Buchholz
-＠item
-Bignum: Jerry James
-＠end itemize
+＠item riece
+IRC (Internet Relay Chat) client for Emacs.
-＠item Internationalization/Mule
-＠itemize ＠minus
-＠item
-mostly Ben Wing; many ideas for future work, Stephen Turnbull
-＠end itemize
+＠item rmail
+An obsolete Emacs mailer. If you do not already use it don't start.
-＠item I/O
-＠itemize ＠minus
-＠item
-Basic event/event-stream implementation: Jamie Zawinski
-＠item
-Most event work since 1994: Ben Wing
-＠item
-Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
-＠item
-Process method abstraction, Windows process work: Kirill Katsnelson
-＠item
-Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
-＠item
-Lstreams: Ben Wing
-＠end itemize
+＠item ruby-modes
+Ruby support.
-＠item Display
-＠itemize ＠minus
-＠item
-Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
-＠item
-Glyphs: mostly Ben Wing
-＠item
-Specifiers: Ben Wing
-＠item
-Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
-＠item
-Widgets: Andy Piper
-＠item
-JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in ＠file{glyphs-eimage.c})
-＠item
-Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
-＠item
-Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
-＠item
-Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
-＠item
-Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
-＠item
-Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
-＠item
-Toolbars: implementation, chuck, much interface work, Ben Wing
-＠item
-Gutters, tabs: andy piper
-＠end itemize
+＠item sasl
+Simple Authentication and Security Layer (SASL) library.
-＠item Device subsystems
-＠itemize ＠minus
-＠item
-X Windows: Jamie Zawinksi, Ben Wing, others
-＠item
-GTK: William Perry, Malcolm Purvis
-＠item
-MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
-＠item
-TTY: Chuck Thompson, Ben Wing
-＠item
-Cygwin: Andy Piper
-＠end itemize
+＠item scheme
+Front-end support for Inferior Scheme.
-＠item Misc
-＠itemize ＠minus
-＠item
-Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
-＠item
-Most initialization-related code: Ben Wing
-＠item
-Internals manual, much of Lisp manual: Ben Wing
-＠item
-FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
-＠end itemize
-＠end table
+＠item semantic
+Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator.
-＠subheading SUPPORT
+＠item sgml
+SGML/Linuxdoc-SGML editing.
-Currently, support duties are handled by many different people.
+＠item sh-script
+Support for editing shell scripts.
-Release managers have been
+＠item sieve
+Manage Sieve email filtering scripts.
-＠itemize ＠minus
-＠item
-Stephen Turnbull (April 2001 - present, 21.x - 21.x?)
-＠item
-Vin Shelton?
-＠item
-Steve Youngs (July 2002 - present??, 21.x - 21.x?)
-＠item
-Martin Buchholz (December 1998 - May 2001, 21.x - 21.x?)
-＠item
-Steve Baur (early 1997 - November 1998, 19.15 - 21.0)
-＠item
-Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
-＠item
-Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
-＠end itemize
+＠item slider
+User interface tool.
-The recent overlapping dates are intentional, since two or three trees
-are maintained simultaneously at any point.
+＠item sml-mode
+SML editing support.
-Other major support work:
+＠item sounds-au
+XEmacs Sun sound files.
-＠itemize ＠minus
-＠item
-Adrian Aichner wrote and maintains the web site.
-＠item
-Stephen Turnbull has produced many of the beta and semi-stable releases
-and has attempted to be the "face" of XEmacs on the newsgroups and
-mailing lists.
-＠item
-Steve Youngs currently produces the beta releases (???).
-＠item
-Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns
-maintaining the packages.
-＠item
-Vin Shelton maintains the stable releases.
-＠item
-Testing - #### Norbert, Adrian, ???
-＠end itemize
+＠item sounds-wav
+XEmacs Microsoft sound files.
-Portraits and email of some of the major developers:
+＠item speedbar
+Provides a separate frame with convenient references.
-＠itemize ＠bullet
-＠item ＠email{andy＠(a)xemacs.org, Andy Piper}
-＠html
-<br><img src="piper.png" alt="Portrait of Andy Piper"><br>
-＠end html
+＠item strokes
+Mouse enhancement utility.
-＠item ＠email{ben＠(a)xemacs.org, Ben Wing}
-＠html
-<br><img src="ben.png" alt="Portrait of Ben Wing"><br>
-＠end html
+＠item supercite
+An Emacs citation tool for News & Mail messages.
-＠item ＠email{cthomp＠(a)xemacs.org, Chuck Thompson}
-＠html
-<br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
-＠end html
+＠item texinfo
+XEmacs TeXinfo support.
+
+＠item text-modes
+Miscellaneous support for editing text files.
-＠item ＠email{hniksic＠(a)xemacs.org, Hrvoje Niksic}
+＠item textools
+Miscellaneous TeX support.
-＠html
-<br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
-＠end html
+＠item time
+Display time & date on the modeline.
-＠item ＠email{jwz＠(a)jwz.org, Jamie Zawinski}
-＠html
-<br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
-＠end html
+＠item tm
+Emacs MIME support. Not needed for gnus >= 5.8.0.
-＠item ＠email{martin＠(a)xemacs.org, Martin Buchholz}
-＠html
-<br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
-＠end html
+＠item tooltalk
+Support for building with Tooltalk.
-＠item ＠email{mly＠(a)adoc.xerox.com, Richard Mlynarik}
-＠html
-<br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
-＠end html
+＠item tpu
+DEC EDIT/TPU support.
-＠item ＠email{stephen＠(a)xemacs.org, Stephen Turnbull}
+＠item tramp
+Remote shell-based file editing. This is similar to EFS or Ange-FTP,
+but works with rsh/ssh and rcp/scp.
-＠item ＠email{steve＠(a)xemacs.org, Steve Baur}
-＠html
-<br><img src="slb.png" alt="Portrait of Steve Baur"><br>
-＠end html
-＠end itemize
+＠item vc
+Version Control for Free systems.
-Many other people have contributed to XEmacs; this is partially
-enumerated in the ＠samp{About XEmacs} option in the Help menu.
+＠item vc-cc
+Version Control for ClearCase (UnFree) systems.
-＠node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
-＠unnumberedsubsec Q1.3.2: Who contributed to this version of the FAQ?
+＠item vhdl
+Support for VHDL.
-The current version of this FAQ was created by ＠email{ben＠(a)xemacs.org,
-Ben Wing}.
+＠item view-process
+A Unix process browsing tool.
-＠node Q1.3.3, Q1.4.1, Q1.3.2, Introduction
-＠unnumberedsubsec Q1.3.3: Who contributed to the FAQ in the past?
+＠item viper
+VI emulation support.
-This is only a partial list, as many names were lost in a hard disk
-crash some time ago.
+＠item vm
+An Emacs mailer.
-＠itemize ＠bullet
-＠item ＠email{steve＠(a)xemacs.org, SL Baur}
+＠item w3
+A Web browser.
-＠item ＠email{hniksic＠(a)xemacs.org, Hrvoje Niksic}
+＠item x-symbol
+Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts.
-＠item ＠email{binge＠(a)aloft.att.com, Curtis.N.Bingham}
+＠item xemacs-base
+Fundamental XEmacs support, you almost certainly need this.
-＠item ＠email{bruncott＠(a)dormeur.inria.fr, Georges Brun-Cottan}
+＠item xemacs-devel
+XEmacs Lisp developer support. This package contains utilities for
+supporting Lisp development. It is a single-file package so it may be
+tailored.
-＠item ＠email{rjc＠(a)cogsci.ed.ac.uk, Richard Caley}
+＠item xlib
+Emacs interface to X server.
-＠item ＠email{cognot＠(a)ensg.u-nancy.fr, Richard Cognot}
+＠item xslide
+XSL editing support.
-＠item ＠email{daku＠(a)nortel.ca, Mark Daku}
+＠item xslt-process
+A minor mode for (X)Emacs which allows running an XSLT processor on a
+buffer.
-＠item ＠email{wgd＠(a)martigny.ai.mit.edu, William G. Dubuque}
+＠item xwem
+X Emacs Window Manager.
-＠item ＠email{eeide＠(a)cs.utah.edu, Eric Eide}
+＠item zenirc
+ZENIRC IRC Client.
+＠end table
-＠item ＠email{af＠(a)biomath.jussieu.fr, Alain Fauconnet}
+＠subheading Mule Support (mule)
-＠item ＠email{cflatter＠(a)nrao.edu, Chris Flatters}
+MULti-lingual Enhancement. Support for world scripts such as
+Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
+To use these packages your XEmacs must be compiled with Mule
+support.
-＠item ＠email{ginsparg＠(a)adra.com, Evelyn Ginsparg}
+＠table ＠asis
+＠item edict
+MULE: Lisp Interface to EDICT, Kanji Dictionary.
-＠item ＠email{hall＠(a)aplcenmp.apl.jhu.edu, Marty Hall}
+＠item egg-its
+MULE: Wnn (4.2 and 6) support. SJ3 support.
-＠item ＠email{dkindred＠(a)cmu.edu, Darrell Kindred}
+＠item latin-unity
+MULE: find single ISO 8859 character set to encode a buffer.
-＠item ＠email{dmoore＠(a)ucsd.edu, David Moore}
+＠item latin-unity
+Unify character sets in a buffer. When characters belong to disjoint
+character sets, this attempts to translate the characters so
+that they belong to one character set. If the buffer coding system is
+not sufficient, this suggests different coding systems.
-＠item ＠email{arup+＠(a)cmu.edu, Arup Mukherjee}
+＠item leim
+MULE: Quail. All non-English and non-Japanese language support.
-＠item ＠email{nickel＠(a)prz.tu-berlin.de, Juergen Nickelsen}
+＠item locale
+MULE: Localized menubars and localized splash screens.
-＠item ＠email{powell＠(a)csl.ncsa.uiuc.edu, Kevin R. Powell}
+＠item lookup
+Dictionary support. (This isn't an English dictionary program)
-＠item ＠email{dworkin＠(a)ccs.neu.edu, Justin Sheehy}
+＠item mule-base
+MULE: Basic Mule support, required for building with Mule.
-＠item ＠email{stig＠(a)hackvan.com, Stig}
+＠item mule-ucs
+MULE: Extended coding systems (including Unicode) for XEmacs.
-＠item ＠email{Aki.Vehtari＠(a)hut.fi, Aki Vehtari}
-＠end itemize
+＠item mule-ucs
+Extended coding systems (including Unicode) for XEmacs.
+
+＠item skk
+Another Japanese Language Input Method. Can be used without a
+separate process running as a dictionary server.
+＠end table
-＠unnumberedsec 1.4: Internationalization
+＠unnumberedsec 1.8: Internationalization
-＠node Q1.4.1, Q1.4.2, Q1.3.3, Introduction
-＠unnumberedsubsec Q1.4.1: What is the status of internationalization support aka MULE (including Asian language support)?
+＠node Q1.8.1, Q1.8.2, Q1.7.1, Introduction
+＠unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)?
Both the stable and development versions of XEmacs include
internationalization support (aka MULE). MULE currently (21.4) works on
＠＠ -1672,8 +2540,8 ＠＠ you build and use the development (21.5)
instability of the development tree. Binaries compiled without MULE
support run faster than MULE capable XEmacsen.
-＠node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
-＠unnumberedsubsec Q1.4.2: How can I help with internationalization?
+＠node Q1.8.2, Q1.8.3, Q1.8.1, Introduction
+＠unnumberedsubsec Q1.8.2: How can I help with internationalization?
If you would like to help, you may want to join the
＠email{xemacs-mule＠(a)xemacs.org} mailing list. Especially needed are
＠＠ -1683,24 +2551,24 ＠＠ use XEmacs/MULE regularly, and have some
Translations of the TUTORIAL and man page are welcome, and XEmacs does
support multilingual menus, but we have few current translations.
-(a)xref{Q1.2.2, How do I become a Beta Tester?}.
+(a)xref{Q1.5.2, How do I become a Beta Tester?}.
-＠node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
-＠unnumberedsubsec Q1.4.3: How do I type non-ASCII characters?
+＠node Q1.8.3, Q1.8.4, Q1.8.2, Introduction
+＠unnumberedsubsec Q1.8.3: How do I type non-ASCII characters?
＠xref{Q3.0.6, How can you type in special characters in XEmacs?}, in
part 3 of this FAQ, for some simple methods that also work in non-MULE
builds of XEmacs (but only for one-octet coded character sets, and
mostly for ISO 8859/1). Many of the methods available for Cyrillic
-((a)pxref{Q1.4.7, How about Cyrillic modes?}) work without MULE. MULE
-has more general capabilities. ＠xref{Q1.4.5, Please explain the
+((a)pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE
+has more general capabilities. ＠xref{Q1.8.5, Please explain the
various input methods in MULE/XEmacs}.
＠xref{Q4.0.8, How do I display non-ASCII characters?}, which covers
display of non-ASCII characters.
-＠node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
-＠unnumberedsubsec Q1.4.4: Can XEmacs messages come out in a different language?
+＠node Q1.8.4, Q1.8.5, Q1.8.3, Introduction
+＠unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language?
The message-catalog support was written but is badly bit-rotted. XEmacs
20 and 21 did ＠emph{not} support it, and early releases of XEmacs 22
＠＠ -1718,8 +2586,8 ＠＠ Emacs*XlwMenu.openInOtherWindow.labelStr
The name of the resource is derived from the non-localized entry by
removing punctuation and capitalizing as above.
-＠node Q1.4.5, Q1.4.6, Q1.4.4, Introduction
-＠unnumberedsubsec Q1.4.5: Please explain the various input methods in MULE/XEmacs
+＠node Q1.8.5, Q1.8.6, Q1.8.4, Introduction
+＠unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs
Mule supports a wide variety of input methods. There are three basic
classes: Lisp implementations, generic platform support, and library
＠＠ -1811,8 +2679,8 ＠＠ boiled-egg-like utilities.
Much of this information was provided by ＠email{morioka＠(a)jaist.ac.jp,
MORIOKA Tomohiko}.
-＠node Q1.4.6, Q1.4.7, Q1.4.5, Introduction
-＠unnumberedsubsec Q1.4.6: How do I portably code for MULE/XEmacs?
+＠node Q1.8.6, Q1.8.7, Q1.8.5, Introduction
+＠unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs?
MULE has evolved rapidly over the last few years, and the original third
party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
＠＠ -1876,8 +2744,8 ＠＠ Following is a sample to distinguish mul
＠end lisp
＠end quotation
-＠node Q1.4.7, Q1.4.8, Q1.4.6, Introduction
-＠unnumberedsubsec Q1.4.7: How about Cyrillic modes?
+＠node Q1.8.7, Q1.8.8, Q1.8.6, Introduction
+＠unnumberedsubsec Q1.8.7: How about Cyrillic modes?
＠email{ilya＠(a)math.ohio-state.edu, Ilya Zakharevich} writes:
＠＠ -1914,8 +2782,8 ＠＠ The fullest resource I found on Russian
XEmacs) is ＠uref{http://www.ibiblio.org/sergei/Software/Software.html}
＠end quotation
-＠node Q1.4.8, Q1.4.9, Q1.4.7, Introduction
-＠unnumberedsubsec Q1.4.8: Does XEmacs support Unicode?
+＠node Q1.8.8, Q1.8.9, Q1.8.7, Introduction
+＠unnumberedsubsec Q1.8.8: Does XEmacs support Unicode?
To get Unicode support, you need a Mule-enabled XEmacs.
＠＠ -1923,7 +2791,7 ＠＠ To get Unicode support, you need a Mule-
don't yet use it as the internal encoding.
21.4 supports Unicode partially -- as an external encoding for files,
-processes, and terminals, but without font support. ＠xref{Q1.4.9, How
+processes, and terminals, but without font support. ＠xref{Q1.8.9, How
does XEmacs display Unicode?}. To get Unicode support in 21.4,
install Mule-UCS from packages in the usual way, and put
＠＠ -1938,13 +2806,13 ＠＠ view the documentation of ＠code{set-codi
that files that are not UTF-8 are being mis-recognized as UTF-8.
Install standard national fonts (not Unicode fonts) for all character
-sets you use. ＠xref{Q1.4.9, How does XEmacs display Unicode??}.
+sets you use. ＠xref{Q1.8.9, How does XEmacs display Unicode??}.
Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
support 31-bit forms of Unicode (UTF-32 or UCS-4).
-＠node Q1.4.9, Q1.5.1, Q1.4.8, Introduction
-＠unnumberedsubsec Q1.4.9: How does XEmacs display Unicode?
+＠node Q1.8.9, , Q1.8.8, Introduction
+＠unnumberedsubsec Q1.8.9: How does XEmacs display Unicode?
Mule doesn't have a Unicode charset internally, so there's nothing to
bind a Unicode registry to. It would not be straightforward to create,
＠＠ -1965,158 +2833,6 ＠＠ extreme hackery. You can run -nw with (
Real Unicode support will be introduced in XEmacs 22.0.
-＠unnumberedsec 1.5: Getting Started
-
-＠node Q1.5.1, Q1.5.2, Q1.4.9, Introduction
-＠unnumberedsubsec Q1.5.1: What is an ＠file{init.el} or ＠file{.emacs} and is there a sample one?
-
-The ＠file{init.el} or ＠file{.emacs} file is used to customize XEmacs to
-your tastes. Starting in 21.4, the preferred location for the init file
-is ＠file{~/.xemacs/init.el}; in previous versions, it was
-(a)file{~/.emacs}. 21.4 still accepts the old location, but the first
-time you run it, it will ask to migrate your file to the new location.
-If you answer yes, the file will be moved, and a "compatibility"
-(a)file{.emacs} file will be placed in the old location so that you can
-still run older versions of XEmacs, and versions of GNU Emacs, which
-expect the old location. The ＠file{.emacs} file present is just a stub
-that loads the real file in ＠file{~/.xemacs/init.el}.
-
-No two init files are alike, nor are they expected to be alike, but
-that's the point. The XEmacs distribution contains an excellent starter
-example in the ＠file{etc/} directory called ＠file{sample.init.el}
-(starting in 21.4) or ＠file{sample.emacs} in older versions. Copy this
-file from there to ＠file{~/.xemacs/init.el} (starting in 21.4) or
-(a)file{~/.emacs} in older versions, where ＠samp{~} means your home
-directory, of course. Then edit it to suit.
-
-You may bring the ＠file{sample.init.el} or ＠file{sample.emacs} file into
-an XEmacs buffer from the menubar. (The menu entry for it is always
-under the ＠samp{Help} menu, but its location under that has changed in
-various versions. Recently, look under the ＠samp{Samples} submenu.) To
-determine the location of the ＠file{etc/} directory type the command
-＠kbd{C-h v data-directory ＠key{RET}}.
-
-＠node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
-＠unnumberedsubsec Q1.5.2: Where do I put my ＠file{init.el} file?
-
-(a)file{init.el} is the name of the init file starting with 21.4, and is
-located in the subdirectory ＠file{.xemacs/} of your home directory. In
-prior versions, the init file is called ＠file{.emacs} and is located in
-your home directory.
-
-Your home directory under Windows is determined by the ＠samp{HOME}
-environment variable. If this is not set, it defaults to ＠samp{C:\}.
-To set this variable, modify ＠file{AUTOEXEC.BAT} under Windows 95/98, or
-select ＠samp{Control Panel->System->Advanced->Environment Variables...}
-under Windows NT/2000.
-
-＠node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
-＠unnumberedsubsec Q1.5.3: Can I use the same ＠file{init.el} with the other Emacs?
-
-Yes. The sample ＠file{init.el} included in the XEmacs
-distribution will show you how to handle different versions and flavors
-of Emacs.
-
-＠node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
-＠unnumberedsubsec Q1.5.4: Any good XEmacs tutorials around?
-
-There's the XEmacs tutorial available from the Help Menu under
-＠samp{Help->Tutorials}, or by typing ＠kbd{C-h t}. To check whether
-it's available in a non-english language, type ＠kbd{C-u C-h t TAB}, type
-the first letters of your preferred language, then type ＠key{RET}.
-
-＠comment There's an Emacs Lisp tutorial at
-＠comment
-＠comment ＠example
-＠comment ＠uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
-＠comment ＠end example
-＠comment
-＠comment ＠email{erik＠(a)petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
-＠comment page at
-＠comment ＠iftex
-＠comment ＠*
-＠comment ＠end iftex
-＠comment ＠uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
-
-＠node Q1.5.5, Q1.5.6, Q1.5.4, Introduction
-＠unnumberedsubsec Q1.5.5: May I see an example of a useful XEmacs Lisp function?
-
-The following function does a little bit of everything useful. It does
-something with the prefix argument, it examines the text around the
-cursor, and it's interactive so it may be bound to a key. It inserts
-copies of the current word the cursor is sitting on at the cursor. If
-you give it a prefix argument: ＠kbd{C-u 3 M-x double-word} then it will
-insert 3 copies.
-
-＠lisp
-(defun double-word (count)
- "Insert a copy of the current word underneath the cursor"
- (interactive "*p")
- (let (here there string)
- (save-excursion
- (forward-word -1)
- (setq here (point))
- (forward-word 1)
- (setq there (point))
- (setq string (buffer-substring here there)))
- (while (>= count 1)
- (insert string)
- (decf count))))
-＠end lisp
-
-The best way to see what is going on here is to let XEmacs tell you.
-Put the code into an XEmacs buffer, and do a ＠kbd{C-h f} with the cursor
-sitting just to the right of the function you want explained. Eg. move
-the cursor to the SPACE between ＠code{interactive} and ＠samp{"*p"} and
-hit ＠kbd{C-h f} to see what the function ＠code{interactive} does. Doing
-this will tell you that the ＠code{*} requires a writable buffer, and
-＠code{p} converts the prefix argument to a number, and
-＠code{interactive} allows you to execute the command with ＠kbd{M-x}.
-
-＠node Q1.5.6, Q1.5.7, Q1.5.5, Introduction
-＠unnumberedsubsec Q1.5.6: And how do I bind it to a key?
-
-To bind to a key do:
-
-＠lisp
-(global-set-key "\C-cd" 'double-word)
-＠end lisp
-
-Or interactively, ＠kbd{M-x global-set-key} and follow the prompts.
-
-＠node Q1.5.7, Q1.5.8, Q1.5.6, Introduction
-＠unnumberedsubsec Q1.5.7: What's the difference between a macro and a function?
-
-Quoting from the Lisp Reference (a.k.a ＠dfn{Lispref}) Manual:
-
-＠dfn{Macros} enable you to define new control constructs and other
-language features. A macro is defined much like a function, but instead
-of telling how to compute a value, it tells how to compute another Lisp
-expression which will in turn compute the value. We call this
-expression the ＠dfn{expansion} of the macro.
-
-Macros can do this because they operate on the unevaluated expressions
-for the arguments, not on the argument values as functions do. They can
-therefore construct an expansion containing these argument expressions
-or parts of them.
-
-Do not confuse the two terms with ＠dfn{keyboard macros}, which are
-another matter, entirely. A keyboard macro is a key bound to several
-other keys. Refer to manual for details.
-
-＠node Q1.5.8, , Q1.5.7, Introduction
-＠unnumberedsubsec Q1.5.8: What is ＠code{Custom}?
-
-＠code{Custom} is a system for customizing XEmacs options.
-
-You can access ＠code{Advanced (Customize)} from the ＠code{Options} menu
-or invoking one of customize commands by typing eg.
-＠kbd{M-x customize}, ＠kbd{M-x customize-face},
-＠kbd{M-x customize-variable} or ＠kbd{M-x customize-apropos}.
-
-There is also new ＠samp{browser} mode for Customize.
-Try it out with ＠kbd{M-x customize-browse}
-
＠node Installation, Editing, Introduction, Top
＠unnumbered 2 Installation and Troubleshooting
＠＠ -2442,11 +3158,11 ＠＠ support. Almost all development is gear
there is little reason not to use it.
The second way to build is the Cygwin port. It takes advantage of
-Cygnus emulation library under Win32. ＠xref{Q1.1.4, What are Cygwin
+Cygnus emulation library under Win32. ＠xref{Q1.2.5, What are Cygwin
and MinGW, and do I need them to run XEmacs?}, for more information.
A third way is the MinGW port. It uses the Cygwin environment to
-build but does not require it at runtime. ＠xref{Q1.1.4, What are
+build but does not require it at runtime. ＠xref{Q1.2.5, What are
Cygwin and MinGW, and do I need them to run XEmacs?}, for more
information.
＠＠ -2465,7 +3181,7 ＠＠ You need Visual C++ 4.2, 5.0, or 6.0 for
some beta testers currently trying to compile with VC.NET, aka version
7.0, but we can't yet report complete success.) For the Cygwin and
MinGW versions, you need the Cygwin environment, which comes with GCC,
-the compiler used for those versions. ＠xref{Q1.1.4, What are Cygwin
+the compiler used for those versions. ＠xref{Q1.2.5, What are Cygwin
and MinGW, and do I need them to run XEmacs?}, for more information on
Cygwin and MinGW.
＠＠ -3195,7 +3911,7 ＠＠ about which memory addresses will be fre
problem for most people. 21.4 implements "portable dumping", which
eliminates the problem altogether. We recommend you use the 21.4
binaries, but you can use the 21.1 binaries if you are very paranoid
-about stability. ＠xref{Q1.0.4, Are binaries available?}.
+about stability. ＠xref{Q1.1.2, Are binaries available?}.
＠node Q2.4.3, Q2.4.4, Q2.4.2, Installation
＠unnumberedsubsec Q2.4.3: XEmacs won't start without network.
＠＠ -5957,95 +6673,39 ＠＠ This is part 7 of the XEmacs Frequently
section is devoted to advanced customization using XEmacs Lisp.
＠menu
-7.0: Online Help
-* Q7.0.1:: How can I get two instances of info?
-* Q7.0.2:: How do I add new Info directories?
-
-7.1: Emacs Lisp and ＠file{init.el}
-* Q7.1.1:: What version of Emacs am I running?
-* Q7.1.2:: How can I evaluate Emacs-Lisp expressions?
-* Q7.1.3:: ＠code{(setq tab-width 6)} behaves oddly.
-* Q7.1.4:: How can I add directories to the ＠code{load-path}?
-* Q7.1.5:: How to check if a lisp function is defined?
-* Q7.1.6:: Can I force the output of ＠code{(face-list)} to a buffer?
-
-7.2: Emacs Lisp Programming Techniques
-* Q7.2.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
-* Q7.2.2:: Can I generate "fake" keyboard events?
-* Q7.2.3:: Could you explain ＠code{read-kbd-macro} in more detail?
-* Q7.2.4:: What is the performance hit of ＠code{let}?
-* Q7.2.5:: What is the recommended use of ＠code{setq}?
-* Q7.2.6:: What is the typical misuse of ＠code{setq}?
-* Q7.2.7:: I like the ＠code{do} form of cl, does it slow things down?
-* Q7.2.8:: I like recursion, does it slow things down?
-* Q7.2.9:: How do I put a glyph as annotation in a buffer?
-* Q7.2.10:: ＠code{map-extents} won't traverse all of my extents!
-* Q7.2.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
-
-7.3: Mathematics
-* Q7.3.1:: What are bignums, ratios, and bigfloats in Lisp?
-* Q7.3.2:: XEmacs segfaults when I use very big numbers!
-* Q7.3.3:: Bignums are really slow!
-* Q7.3.4:: Equal bignums don't compare as equal! What gives?
+7.0: Emacs Lisp and ＠file{init.el}
+* Q7.0.1:: What version of Emacs am I running?
+* Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
+* Q7.0.3:: ＠code{(setq tab-width 6)} behaves oddly.
+* Q7.0.4:: How can I add directories to the ＠code{load-path}?
+* Q7.0.5:: How to check if a lisp function is defined?
+* Q7.0.6:: Can I force the output of ＠code{(face-list)} to a buffer?
+
+7.1: Emacs Lisp Programming Techniques
+* Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
+* Q7.1.2:: Can I generate "fake" keyboard events?
+* Q7.1.3:: Could you explain ＠code{read-kbd-macro} in more detail?
+* Q7.1.4:: What is the performance hit of ＠code{let}?
+* Q7.1.5:: What is the recommended use of ＠code{setq}?
+* Q7.1.6:: What is the typical misuse of ＠code{setq}?
+* Q7.1.7:: I like the ＠code{do} form of cl, does it slow things down?
+* Q7.1.8:: I like recursion, does it slow things down?
+* Q7.1.9:: How do I put a glyph as annotation in a buffer?
+* Q7.1.10:: ＠code{map-extents} won't traverse all of my extents!
+* Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
+
+7.2: Mathematics
+* Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
+* Q7.2.2:: XEmacs segfaults when I use very big numbers!
+* Q7.2.3:: Bignums are really slow!
+* Q7.2.4:: Equal bignums don't compare as equal! What gives?
＠end menu
-＠unnumberedsec 7.0: Online Help
+＠unnumberedsec 7.0: Emacs Lisp and ＠file{init.el}
＠node Q7.0.1, Q7.0.2, Advanced, Advanced
-＠unnumberedsubsec Q7.0.1: How can I get two instances of info?
-
-Before 21.4, you can't. The ＠code{info} package does not provide for
-multiple info buffers. In 21.4, this should be fixed. #### how?
-
-＠node Q7.0.2, Q7.1.1, Q7.0.1, Advanced
-＠unnumberedsubsec Q7.0.2: How do I add new Info directories?
-
-You use something like:
-
-＠lisp
-(setq Info-directory-list (cons
- (expand-file-name "~/info")
- Info-default-directory-list))
-＠end lisp
-
-＠email{davidm＠(a)prism.kla.com, David Masterson} writes:
-
-＠quotation
-Emacs Info and XEmacs Info do many things differently. If you're trying to
-support a number of versions of Emacs, here are some notes to remember:
-
-＠enumerate
-＠item
-Emacs Info scans ＠code{Info-directory-list} from right-to-left while
-XEmacs Info reads it from left-to-right, so append to the ＠emph{correct}
-end of the list.
-
-＠item
-Use ＠code{Info-default-directory-list} to initialize
-＠code{Info-directory-list} ＠emph{if} it is available at startup, but not
-all Emacsen define it.
-
-＠item
-Emacs Info looks for a standard ＠file{dir} file in each of the
-directories scanned from #1 and magically concatenates them together.
-
-＠item
-XEmacs Info looks for a ＠file{localdir} file (which consists of just the
-menu entries from a ＠file{dir} file) in each of the directories scanned
-from #1 (except the first), does a simple concatenation of them, and
-magically attaches the resulting list to the end of the menu in the
-＠file{dir} file in the first directory.
-＠end enumerate
-
-Another alternative is to convert the documentation to HTML with
-texi2html and read it from a web browser like Lynx or W3.
-＠end quotation
-
-＠unnumberedsec 7.1: Emacs Lisp and ＠file{init.el}
+＠unnumberedsubsec Q7.0.1: What version of Emacs am I running?
-＠node Q7.1.1, Q7.1.2, Q7.0.2, Advanced
-＠unnumberedsubsec Q7.1.1: What version of Emacs am I running?
-
How can ＠file{init.el} determine which of the family of
Emacsen I am using?
＠＠ -6061,8 +6721,8 ＠＠ For all new code, all you really need to
(defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
＠end lisp
-＠node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
-＠unnumberedsubsec Q7.1.2: How can I evaluate Emacs-Lisp expressions?
+＠node Q7.0.2, Q7.0.3, Q7.0.1, Advanced
+＠unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions?
I know I can evaluate Elisp expressions from ＠code{*scratch*} buffer
with ＠kbd{C-j} after the expression. How do I do it from another
＠＠ -6071,8 +6731,8 ＠＠ buffer?
Press ＠kbd{M-:} (the default binding of ＠code{eval-expression}), and
enter the expression to the minibuffer.
-＠node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
-＠unnumberedsubsec Q7.1.3: ＠code{(setq tab-width 6)} behaves oddly.
+＠node Q7.0.3, Q7.0.4, Q7.0.2, Advanced
+＠unnumberedsubsec Q7.0.3: ＠code{(setq tab-width 6)} behaves oddly.
If you put ＠code{(setq tab-width 6)} in your
＠file{init.el} file it does not work! Is there a reason
＠＠ -6081,8 +6741,8 ＠＠ for this? If you do it at the EVAL prom
Use ＠code{setq-default} instead, since ＠code{tab-width} is
all-buffer-local.
-＠node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
-＠unnumberedsubsec Q7.1.4: How can I add directories to the ＠code{load-path}?
+＠node Q7.0.4, Q7.0.5, Q7.0.3, Advanced
+＠unnumberedsubsec Q7.0.4: How can I add directories to the ＠code{load-path}?
Here are two ways to do that, one that puts your directories at the
front of the load-path, the other at the end:
＠＠ -6109,8 +6769,8 ＠＠ To add directories using Unix shell meta
＠end lisp
＠end quotation
-＠node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
-＠unnumberedsubsec Q7.1.5: How to check if a lisp function is defined?
+＠node Q7.0.5, Q7.0.6, Q7.0.4, Advanced
+＠unnumberedsubsec Q7.0.5: How to check if a lisp function is defined?
Use the following elisp:
＠＠ -6134,8 +6794,8 ＠＠ There is an incredible amount of broken
much better more often in more places if it did the above instead of
trying to divine its environment from the value of one variable.
-＠node Q7.1.6, Q7.2.1, Q7.1.5, Advanced
-＠unnumberedsubsec Q7.1.6: Can I force the output of ＠code{(face-list)} to a buffer?
+＠node Q7.0.6, Q7.1.1, Q7.0.5, Advanced
+＠unnumberedsubsec Q7.0.6: Can I force the output of ＠code{(face-list)} to a buffer?
It would be good having it in a buffer, as the output of
＠code{(face-list)} is too wide to fit to a minibuffer.
＠＠ -6147,10 +6807,10 ＠＠ If the minibuffer smallness is the only
simply press ＠kbd{C-h l} to get the former minibuffer contents in a
buffer.
-＠unnumberedsec 7.2: Emacs Lisp Programming Techniques
+＠unnumberedsec 7.1: Emacs Lisp Programming Techniques
-＠node Q7.2.1, Q7.2.2, Q7.1.6, Advanced
-＠unnumberedsubsec Q7.2.1: What is the difference in key sequences between XEmacs and GNU Emacs?
+＠node Q7.1.1, Q7.1.2, Q7.0.6, Advanced
+＠unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
＠email{clerik＠(a)naggum.no, Erik Naggum} writes;
＠＠ -6182,8 +6842,8 ＠＠ Another (even safer) way to be sure of t
<up>}, and converts it to the internal key representation of the Emacs
you use. The function is available both on XEmacs and GNU Emacs.
-＠node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
-＠unnumberedsubsec Q7.2.2: Can I generate "fake" keyboard events?
+＠node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
+＠unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events?
I wonder if there is an interactive function that can generate
＠dfn{fake} keyboard events. This way, I could simply map them inside
＠＠ -6203,8 +6863,8 ＠＠ This seems to work:
(lambda () (interactive) (cg--generate-char-event 4)))
＠end lisp
-＠node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
-＠unnumberedsubsec Q7.2.3: Could you explain ＠code{read-kbd-macro} in more detail?
+＠node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
+＠unnumberedsubsec Q7.1.3: Could you explain ＠code{read-kbd-macro} in more detail?
The ＠code{read-kbd-macro} function returns the internal Emacs
representation of a human-readable string (which is its argument).
＠＠ -6294,8 +6954,8 ＠＠ seven keys but ＠code{<right>} is a singl
use whitespace.
＠end quotation
-＠node Q7.2.4, Q7.2.5, Q7.2.3, Advanced
-＠unnumberedsubsec Q7.2.4: What is the performance hit of ＠code{let}?
+＠node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
+＠unnumberedsubsec Q7.1.4: What is the performance hit of ＠code{let}?
In most cases, not noticeable. Besides, there's no avoiding
＠code{let}---you have to bind your local variables, after all. Some
＠＠ -6304,8 +6964,8 ＠＠ function. I think because of clarity an
future implementation), ＠code{let}-s should be used (nested) in a way to
provide the clearest code.
-＠node Q7.2.5, Q7.2.6, Q7.2.4, Advanced
-＠unnumberedsubsec Q7.2.5: What is the recommended use of ＠code{setq}?
+＠node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
+＠unnumberedsubsec Q7.1.5: What is the recommended use of ＠code{setq}?
＠itemize ＠bullet
＠item Global variables
＠＠ -6367,8 +7027,8 ＠＠ returns the value of ＠code{inbox}, which
＠end lisp
＠end itemize
-＠node Q7.2.6, Q7.2.7, Q7.2.5, Advanced
-＠unnumberedsubsec Q7.2.6: What is the typical misuse of ＠code{setq}?
+＠node Q7.1.6, Q7.1.7, Q7.1.5, Advanced
+＠unnumberedsubsec Q7.1.6: What is the typical misuse of ＠code{setq}?
A typical misuse is probably ＠code{setq}ing a variable that was meant to
be local. Such a variable will remain bound forever, never to be
＠＠ -6409,8 +7069,8 ＠＠ While compiling toplevel forms:
** assignment to free variable flurghoze
＠end lisp
-＠node Q7.2.7, Q7.2.8, Q7.2.6, Advanced
-＠unnumberedsubsec Q7.2.7: I like the ＠code{do} form of cl, does it slow things down?
+＠node Q7.1.7, Q7.1.8, Q7.1.6, Advanced
+＠unnumberedsubsec Q7.1.7: I like the ＠code{do} form of cl, does it slow things down?
It shouldn't. Here is what Dave Gillespie has to say about cl.el
performance:
＠＠ -6451,8 +7111,8 ＠＠ You can find out how a macro expands by
function.
＠end quotation
-＠node Q7.2.8, Q7.2.9, Q7.2.7, Advanced
-＠unnumberedsubsec Q7.2.8: I like recursion, does it slow things down?
+＠node Q7.1.8, Q7.1.9, Q7.1.7, Advanced
+＠unnumberedsubsec Q7.1.8: I like recursion, does it slow things down?
Yes. The Emacs byte-compiler cannot do much to optimize recursion. But
think well whether this is a real concern in Emacs. Much of the Emacs
＠＠ -6462,8 +7122,8 ＠＠ fact that it is an interpreter.
Please try not to make your code much uglier to gain a very small speed
gain. It's not usually worth it.
-＠node Q7.2.9, Q7.2.10, Q7.2.8, Advanced
-＠unnumberedsubsec Q7.2.9: How do I put a glyph as annotation in a buffer?
+＠node Q7.1.9, Q7.1.10, Q7.1.8, Advanced
+＠unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer?
Here is a solution that will insert the glyph annotation at the
beginning of buffer:
＠＠ -6489,8 +7149,8 ＠＠ You can turn this to a function (that op
name), and inserts the glyph at ＠code{(point)} instead of
＠code{(point-min)}.
-＠node Q7.2.10, Q7.2.11, Q7.2.9, Advanced
-＠unnumberedsubsec Q7.2.10: ＠code{map-extents} won't traverse all of my extents!
+＠node Q7.1.10, Q7.1.11, Q7.1.9, Advanced
+＠unnumberedsubsec Q7.1.10: ＠code{map-extents} won't traverse all of my extents!
I tried to use ＠code{map-extents} to do an operation on all the extents
in a region. However, it seems to quit after processing a random number
＠＠ -6520,8 +7180,8 ＠＠ is:
nil))
＠end lisp
-＠node Q7.2.11, Q7.3.1, Q7.2.10, Advanced
-＠unnumberedsubsec Q7.2.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
+＠node Q7.1.11, Q7.2.1, Q7.1.10, Advanced
+＠unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
＠c New
＠email{hniksic＠(a)xemacs.org, Hrvoje Niksic} writes:
＠＠ -6532,10 +7192,10 ＠＠ results using ＠kbd{M-x profile-results}.
where the time is being spent.
＠end quotation
-＠unnumberedsec 7.3: Mathematics
+＠unnumberedsec 7.2: Mathematics
-＠node Q7.3.1, Q7.3.2, Q7.2.11, Advanced
-＠unnumberedsubsec Q7.3.1: What are bignums, ratios, and bigfloats in Lisp?
+＠node Q7.2.1, Q7.2.2, Q7.1.11, Advanced
+＠unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp?
Thanks to ＠email{james＠(a)xemacs.org, Jerry James}, XEmacs 21.5.18 and
later can use the capabilities of multiple-precision libraries that may
＠＠ -6563,7 +7223,7 ＠＠ User-visible changes in behavior include
＠itemize
＠item
Arithmetic can cause a segfault, depending on your MP library
-(a)ref{Q7.3.2, XEmacs segfaults when I use very big numbers!}.
+(a)ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
＠item
Terminology is not Common-Lisp-conforming. For example, ``integer'' for
＠＠ -6589,7 +7249,7 ＠＠ ratios, so there should be few surprises
can't be ruled out. ``Arbitrary'' precision means precisely what it
says. If you work with extremely large numbers, your machine may
arbitrarily decide to hand you an unpleasant surprise rather than a
-bignum ＠ref{Q7.3.2, XEmacs segfaults when I use very big numbers!}.
+bignum ＠ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
To configure with GNU MP, add
＠samp{--use-number-lib=gmp}
＠＠ -6604,8 +7264,8 ＠＠ eventually, but if your skills run more
than to writing new code, feel free to fill in the gap!
-＠node Q7.3.2, Q7.3.3, Q7.3.1, Advanced
-＠unnumberedsubsec Q7.3.2: XEmacs segfaults when I use very big numbers!
+＠node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
+＠unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers!
GMP by default allocates temporaries on the stack. If you run out of
stack space, you're dead; there is no way that we know of to reliably
＠＠ -6622,8 +7282,8 ＠＠ BSD MP implementations vary across vendo
yet.)
-＠node Q7.3.3, Q7.3.4, Q7.3.2, Advanced
-＠unnumberedsubsec Q7.3.3: Bignums are really slow!
+＠node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
+＠unnumberedsubsec Q7.2.3: Bignums are really slow!
Many Linux distributions compile all their packages for the i386, and
this is costly. An optimized version can give you two or three orders
＠＠ -6631,8 +7291,8 ＠＠ of magnitude better performance for a Pe
See ＠uref{http://www.swox.com/gmp/gmp-speed.html}.)
-＠node Q7.3.4, , Q7.3.3, Advanced
-＠unnumberedsubsec Q7.3.4: Equal bignums don't compare as equal! What gives?
+＠node Q7.2.4, , Q7.2.3, Advanced
+＠unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives?
Ah, Grasshopper, I see you are using ＠code{(eq x y)}. The Bodhisattva
CLTL2 warned of the illusion that equal numbers would be ＠samp{eq}!
＠＠ -6654,6 +7314,7 ＠＠ section is devoted to miscellaneous exte
elsewhere in XEmacs.
＠menu
+8.0: TeX
* Q8.0.1:: Is there something better than LaTeX mode?
* Q8.0.2:: What is AUCTeX? Where do you get it?
* Q8.0.3:: Problems installing AUCTeX.
＠＠ -7010,6 +7671,7 ＠＠ Information on older versions of XEmacs
the same directory, or ＠file{OONEWS} for really old versions.
＠menu
+9.0: Changes
* Q9.0.1:: What new features will be in XEmacs soon?
* Q9.0.2:: What's new in XEmacs 21.4?
* Q9.0.3:: What's new in XEmacs 21.1?
＠＠ -7339,6 +8001,7 ＠＠ updated versions of packages, but bug fi
to released XEmacsen, but users can apply themselves) are also accepted.
＠menu
+10.0: XEmacs 21.1
* Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
＠end menu
cvs server: Diffing man/internals
cvs server: Diffing man/lispref
cvs server: Diffing man/new-users-guide
cvs server: Diffing man/xemacs
Index: man/xemacs/help.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/xemacs/help.texi,v
retrieving revision 1.4
diff -u -p -r1.4 help.texi
--- man/xemacs/help.texi 2004/08/13 09:47:57 1.4
+++ man/xemacs/help.texi 2005/01/31 19:46:14
＠＠ -442,13 +442,12 ＠＠ actually ＠kbd{C-M-h}, which marks a defu
information. ＠kbd{C-h C-w} (＠code{describe-no-warranty}) displays the
full details on the complete absence of warranty for XEmacs. ＠kbd{C-h
n} (＠code{view-emacs-news}) displays the file ＠file{xemacs/etc/NEWS},
-which contains documentation on XEmacs changes arranged chronologically.
-＠kbd{C-h F} (＠code{xemacs-local-faq}) displays local version of the
-XEmacs frequently-answered-questions-list. ＠kbd{C-h t}
-(＠code{help-with-tutorial}) displays the learn-by-doing XEmacs
-tutorial. ＠kbd{C-h C-c} (＠code{describe-copying}) displays the file
-＠file{xemacs/etc/COPYING}, which tells you the conditions you must obey
-in distributing copies of XEmacs. ＠kbd{C-h C-d}
-(＠code{describe-distribution}) displays another file named
-＠file{xemacs/etc/DISTRIB}, which tells you how you can order a copy of
-the latest version of XEmacs.
+which contains documentation on XEmacs changes arranged
+chronologically. ＠kbd{C-h F} (＠code{xemacs-local-faq}) displays the
+local version of the XEmacs FAQ (Frequently Answered Questions list).
+＠kbd{C-h t} (＠code{help-with-tutorial}) displays the learn-by-doing
+XEmacs tutorial. ＠kbd{C-h C-c} (＠code{describe-copying}) displays the
+file ＠file{xemacs/etc/COPYING}, which tells you the conditions you
+must obey in distributing copies of XEmacs. ＠kbd{C-h C-d}
+(＠code{describe-distribution} displays the section of the FAQ that
+tells you how you can get the latest version of XEmacs.
Index: man/xemacs/new.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/xemacs/new.texi,v
retrieving revision 1.2
diff -u -p -r1.2 new.texi
--- man/xemacs/new.texi 2001/04/12 18:22:29 1.2
+++ man/xemacs/new.texi 2005/01/31 19:46:15
＠＠ -235,39 +235,74 ＠＠ commands are invoked only when you are i
＠cindex version number
＠example
-(cond ((string-match "Lucid" emacs-version)
+(cond ((string-match "XEmacs" emacs-version)
;;
- ;; Code for any version of Lucid Emacs or XEmacs goes here
+ ;; Code for any version of XEmacs goes here.
;;
))
-(cond ((and (string-match "XEmacs" emacs-version)
- (or (> emacs-major-version 19)
- (>= emacs-minor-version 12)))
+(cond ((not (string-match "XEmacs" emacs-version)))
;;
- ;; Code which requires XEmacs version 19.12 or newer goes here
+ ;; Code for any version of GNU Emacs goes here.
;;
))
-(cond ((>= emacs-major-version 19)
+(cond ((and (string-match "XEmacs" emacs-version)
+ (emacs-version>= 21 4))
;;
- ;; Code for any vintage-19 emacs goes here
+ ;; Code which requires XEmacs version 21.4 or newer goes here
;;
))
-(cond ((and (not (string-match "Lucid" emacs-version))
- (= emacs-major-version 19))
+(cond ((and (string-match "XEmacs" emacs-version)
+ (emacs-version>= 21 4 12)
+ (not (emacs-version>= 21 4 15)))
;;
- ;; Code specific to FSF Emacs 19 (not XEmacs) goes here
+ ;; Code which requires exactly XEmacs version 21.4.12 through
+ ;; 21.4.14, inclusive, goes here. (e.g. A bug was introduced in
+ ;; 21.4.12 and fixed in 21.4.15 but many of the versions of
+ ;; XEmacs around in the computer laboratory run those versions,
+ ;; so I need to introduce a workaround. In such a case, you
+ ;; should ideally try to conditionalize on something else,
+ ;; e.g. a feature symbol or a simple test that can be run to
+ ;; smoke out the bug.)
;;
))
-(cond ((< emacs-major-version 19)
+(cond ((and (not (string-match "XEmacs" emacs-version)
+ (emacs-version>= 20 2))
;;
- ;; Code specific to emacs 18 goes here
+ ;; Code which requires GNU Emacs version 20.2 or newer, but not XEmacs,
+ ;; goes here
;;
))
+
+＠end example
+
+＠emph{NOTE}: ＠strong{DO} use ＠code{(emacs-version>= ...)}. ＠strong{DO NOT}
+try to do this yourself using ＠code{emacs-major-version} and
+＠code{emacs-minor-version}. You will, with high probability, get it
+wrong. Typical attempts to replace ＠code{(emacs-version>= 21 4)} use
+
+＠example
+(and (>= emacs-major-version 21)
+ (>= emacs-minor-version 4))
+＠end example
+
+which correctly excludes 21.3 and all previous versions,
+but also excludes 22.0 through 22.3, 23.0 through 23.3, etc.
+
+A "more clever" version, as advocated in earlier versions
+of this very manual, was like this:
+
+＠example
+(or (> emacs-major-version 21)
+ (>= emacs-minor-version 4))
＠end example
+
+which correctly includes 21.4 and all following versions,
+but also includes 20.4 through 20.99999, 19.4 through
+19.99999, etc.
Alternatively, use ＠file{.xemacs/init.el} for an init file. ＠xref{Init File}.
Index: man/xemacs/xemacs.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/xemacs/xemacs.texi,v
retrieving revision 1.17
diff -u -p -r1.17 xemacs.texi
--- man/xemacs/xemacs.texi 2005/01/28 00:12:39 1.17
+++ man/xemacs/xemacs.texi 2005/01/31 19:46:15
＠＠ -996,27 +996,12 ＠＠ that they might get from you. The preci
the GNU General Public License that comes with XEmacs and also appears
following this section.
-The easiest way to get a copy of XEmacs is from someone else who has it.
-You need not ask for permission to do so, or tell any one else; just copy
-it.
+To get XEmacs, go to ＠uref{http://www.xemacs.org/Download/}.
-If you have access to the Internet, you can get the latest version of
-XEmacs from the anonymous FTP server ＠file{ftp.xemacs.org} in the directory
-＠file{/pub/xemacs}. It can also be found at numerous other archive
-sites around the world; check the file ＠file{etc/DISTRIB} in an XEmacs
-distribution for the latest known list.
-
-
＠unnumberedsec Getting Other Versions of Emacs
-
-The Free Software Foundation's version of Emacs (called ＠dfn{FSF Emacs}
-in this manual and often referred to as ＠dfn{GNU Emacs}) is available
-by anonymous FTP from ＠file{prep.ai.mit.edu}.
-Win-Emacs, an older version of XEmacs that runs on Microsoft Windows
-and Windows NT, is available by anonymous FTP from ＠file{ftp.netcom.com}
-in the directory ＠file{/pub/pe/pearl}, or from ＠file{ftp.cica.indiana.edu}
-as the files ＠file{wemdemo*.zip} in the directory ＠file{/pub/pc/win3/demo}.
+The Free Software Foundation's version of Emacs (＠dfn{GNU Emacs}) is
+available at ＠uref{http://www.gnu.org/software/emacs/emacs.html}.
＠node Intro, Glossary, Distrib, Top
＠unnumbered Introduction
＠＠ -1025,9 +1010,8 ＠＠ as the files ＠file{wemdemo*.zip} in the
self-documenting, customizable, extensible real-time display editor
Emacs. XEmacs provides many powerful display and user-interface
capabilities not found in other Emacsen and is mostly upwardly
-compatible with GNU Emacs from the Free Software Foundation
-(referred to as ＠dfn{FSF Emacs} in this manual). XEmacs also
-comes standard with a great number of useful packages.
+compatible with GNU Emacs from the Free Software Foundation. XEmacs
+also comes standard with a great number of useful packages.
We say that XEmacs is a ＠dfn{display} editor because normally the text
being edited is visible on the screen and is updated automatically as you
cvs server: Diffing modules
cvs server: Diffing modules/base64
cvs server: Diffing modules/common
cvs server: Diffing modules/ldap
cvs server: Diffing modules/postgresql
cvs server: Diffing modules/sample
cvs server: Diffing modules/sample/external
cvs server: Diffing modules/sample/internal
cvs server: Diffing modules/zlib
cvs server: Diffing netinstall
cvs server: Diffing nt
Index: nt/xemacs.mak
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/nt/xemacs.mak,v
retrieving revision 1.111
diff -u -p -r1.111 xemacs.mak
--- nt/xemacs.mak 2005/01/28 01:54:47 1.111
+++ nt/xemacs.mak 2005/01/31 19:46:16
＠＠ -1457,8 +1457,16 ＠＠ install: all
＠echo Installing in $(INSTALL_DIR) ...
＠echo PlaceHolder > PlaceHolder
＠$(COPY) $(SRCROOT)\PROBLEMS "$(INSTALL_DIR)\"
+ ＠$(COPY) $(SRCROOT)\BUGS "$(INSTALL_DIR)\"
+ ＠$(COPY) $(SRCROOT)\README "$(INSTALL_DIR)\"
+ ＠$(COPY) $(SRCROOT)\COPYING "$(INSTALL_DIR)\"
+ ＠$(COPY) $(SRCROOT)\Installation "$(INSTALL_DIR)\"
＠$(COPY) PlaceHolder "$(INSTALL_DIR)\lock\"
-$(DEL) "$(INSTALL_DIR)\lock\PlaceHolder"
+# ＠$(COPY) $(BLDLIB_SRC)\*.exe "$(INSTALL_DIR)\lib-src\"
+# ＠$(COPY) $(BLDLIB_SRC)\DOC "$(INSTALL_DIR)\lib-src\"
+# ＠$(COPY) $(CONFIG_VALUES) "$(INSTALL_DIR)\lib-src\"
+# ＠$(COPY) $(BLDSRC)\xemacs.exe "$(INSTALL_DIR)\bin\"
＠$(COPY) $(BLDLIB_SRC)\*.exe "$(INSTALL_DIR)\$(EMACS_CONFIGURATION)\"
＠$(COPY) $(BLDLIB_SRC)\DOC "$(INSTALL_DIR)\$(EMACS_CONFIGURATION)"
＠$(COPY) $(CONFIG_VALUES) "$(INSTALL_DIR)\$(EMACS_CONFIGURATION)"
cvs server: Diffing nt/installer
cvs server: Diffing nt/installer/Wise
cvs server: Diffing src
cvs server: Diffing src/m
cvs server: Diffing src/s
cvs server: Diffing tests
cvs server: Diffing tests/DLL
cvs server: Diffing tests/Dnd
cvs server: Diffing tests/automated
cvs server: Diffing tests/gtk
cvs server: Diffing tests/mule
cvs server: Diffing tests/tooltalk
- 4 participants
- 3 comments
[21.4] [PATCH] define ABORT always
19 years, 10 months
Ben Wing
Ben Wing
src/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* emacs.c:
Define assert_failed() always.
* lisp.h:
Always define ABORT().
latest-stable source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: src/lisp.h src/emacs.c
Index: src/emacs.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/emacs.c,v
retrieving revision 1.97.2.9
diff -u -p -r1.97.2.9 emacs.c
--- src/emacs.c 2005/01/31 02:55:09 1.97.2.9
+++ src/emacs.c 2005/01/31 19:33:09
＠＠ -3356,7 +3356,6 ＠＠ Non-nil return value means XEmacs is run
in one session without having to recompile. */
/* #define ASSERTIONS_DONT_ABORT */
-#ifdef USE_ASSERTIONS
/* This highly dubious kludge ... shut up Jamie, I'm tired of your slagging. */
static int in_assert_failed;
＠＠ -3429,7 +3428,6 ＠＠ assert_failed (const char *file, int lin
inhibit_non_essential_printing_operations = 0;
in_assert_failed = 0;
}
-#endif /* USE_ASSERTIONS */
#ifdef QUANTIFY
DEFUN ("quantify-start-recording-data", Fquantify_start_recording_data,
Index: src/lisp.h
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/lisp.h,v
retrieving revision 1.45.2.9
diff -u -p -r1.45.2.9 lisp.h
--- src/lisp.h 2005/01/31 02:55:21 1.45.2.9
+++ src/lisp.h 2005/01/31 19:33:11
＠＠ -243,11 +243,12 ＠＠ template<typename T> struct alignment_tr
time the assert checks take is measurable so let's not include them
in production binaries. */
-#ifdef USE_ASSERTIONS
/* Highly dubious kludge */
/* (thanks, Jamie, I feel better now -- ben) */
-void assert_failed (const char *, int, const char *);
# define ABORT() (assert_failed (__FILE__, __LINE__, "ABORT()"))
+void assert_failed (const char *, int, const char *);
+
+#ifdef USE_ASSERTIONS
# define assert(x) ((x) ? (void) 0 : assert_failed (__FILE__, __LINE__, #x))
#else
# ifdef DEBUG_XEMACS
- 2 participants
- 1 comments
[PATCH] Pre-behavior-ws changes, PLEASE REVIEW
19 years, 10 months
Ben Wing
Ben Wing
PLEASE REVIEW!
This is a repost of a prior posting. Before integrating my workspace that
implements behaviors, I want to put in the necessary package changes.
Some of these changes are to packages that are externally maintained, but
I'm not exactly sure which, or who I should mail the changes to, or other
procedural-related stuff.
Norbert, could you comment?
NB This is minus the pending-del patch that caused controversy last time;
that is in a separate post.
Here is what I wrote before:
----------------------------
This contains patches from an old package ws. Most of them add support for
define-behavior, which I have heavily modified in another ws of mine. They
conditionalize on define-behavior-group, since the old version of
define-behavior doesn't allow arbitrary keywords and hence will break with
the new defns. (define-behavior-group exists only in the new ws.)
The idea is that the Tools menu is replaced with a menu generated by
behavior.el, where each behavior can specify the way to enable/disable,
other commands, a doc string, etc. Variables can also be frobbed because
the same ws adds support for auto-generated custom-defines.el, which
specifies all the vars of a package without the need to load the whole
package. A few changes have been added to make this work better.
One side effect of this is that PACKAGES MAY NO LONGER MODIFY MENUS
THEMSELVES. I've been trying to get package maintainers to be more
well-behaved about this for awhile (and have encountered some resistance),
but it really must happen now that the Tools menu has totally changed.
Some packages have been forcibly hacked in this patch; obviously this won't
go in without the consent of the package maintainer.
Similarly, I've put in some hacks to fix up some of the remaining packages
that illegally set themselves up upon loading. With the behavior interface
there is a consistent way to enable/disable packages in any case.
mule-packages/skk/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* skk-foreword.el:
Autoload for custom-defines.
unsupported/simon/epop3/ChangeLog addition:
2003-03-09 Ben Wing <ben(a)xemacs.org>
* Makefile:
Delete explicit compile:: and binkit: rules.
Don't add custom-load.elc to the list of generated elc's.
xemacs-packages/calendar/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* calendar.el:
* calendar.el ('calendar): New.
Add define-behavior.
xemacs-packages/cookie/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* yow.el:
* yow.el ('yow): New.
Add define-behavior.
xemacs-packages/debug/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* dbx.el:
* dbx.el ('dbx): New.
* gdb.el:
* gdb.el ('gdb): New.
Add define-behavior.
xemacs-packages/ediff/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* ediff-hook.el:
* ediff-hook.el (progn):
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
* ediff-hook.el ('ediff): New.
Add define-behavior.
xemacs-packages/edit-utils/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* avoid.el:
* avoid.el ('avoid): New.
* avoid.el (avoid):
* balloon-help.el:
* balloon-help.el ('balloon-help): New.
* balloon-help.el (balloon-help):
* blink-cursor.el:
* blink-cursor.el ('blink-cursor): New.
* blink-paren.el:
* blink-paren.el ('blink-paren): New.
* completion.el:
* completion.el ('completion): New.
* completion.el (completion):
* dabbrev.el:
* dabbrev.el ('dabbrev): New.
* dabbrev.el (dabbrev):
* desktop.el:
* desktop.el ('desktop): New.
* desktop.el (desktop):
Add define-behavior support.
* edit-faces.el:
* edit-faces.el ('edit-faces): New.
* edit-toolbar.el:
* edit-toolbar.el ('edit-toolbar): New.
* edit-toolbar.el (edit-toolbar):
* fast-lock.el:
* fast-lock.el ('fast-lock): New.
* fast-lock.el (fast-lock):
* file-part.el:
* file-part.el ('file-part): New.
* file-part.el (file-part):
* floating-toolbar.el:
* floating-toolbar.el ('floating-toolbar): New.
* floating-toolbar.el (floating-toolbar):
* flow-ctrl.el:
* flow-ctrl.el ('flow-control): New.
* flow-ctrl.el (flow-control):
* func-menu.el:
* func-menu.el ('func-menu): New.
* hippie-exp.el:
* hippie-exp.el ('hippie-expand): New.
* hippie-exp.el (hippie-expand):
* id-select.el:
* id-select.el ('id-select): New.
* id-select.el (id-select):
* iswitchb.el:
* iswitchb.el ('iswitchb): New.
* iswitchb.el (iswitchb):
* lazy-lock.el:
* lazy-lock.el ('lazy-lock): New.
* lazy-lock.el (lazy-lock):
* page-ext.el:
* page-ext.el ('page-ext): New.
* page-ext.el (page-ext):
* paren.el:
* paren.el ('paren): New.
* paren.el (paren):
* permanent-buffers.el:
* permanent-buffers.el ('permanent-buffers): New.
* permanent-buffers.el (permanent-buffers):
* popper.el:
* popper.el ('popper): New.
* popper.el (popper):
* power-macros.el:
* power-macros.el ('power-macros): New.
* power-macros.el (power-macros):
* recent-files.el:
* recent-files.el ('recent-files): New.
* recent-files.el (recent-files):
* redo.el:
* redo.el ('redo): New.
* redo.el (redo):
* reportmail.el:
* reportmail.el ('reportmail): New.
* reportmail.el (reportmail):
* resume.el:
* resume.el ('resume): New.
* resume.el (resume):
* rsz-minibuf.el:
* rsz-minibuf.el ('resize-minibuffer): New.
* rsz-minibuf.el (resize-minibuffer):
* saveconf.el:
* saveconf.el ('save-context): New.
* saveconf.el (save-context):
* savehist.el:
* savehist.el ('save-history): New.
* savehist.el (save-history):
* scroll-in-place.el:
* scroll-in-place.el ('scroll-in-place): New.
* scroll-in-place.el (scroll-in-place):
* setnu.el:
* setnu.el ('setnu): New.
* toolbar-utils.el:
* toolbar-utils.el ('toolbar-utils): New.
* toolbar-utils.el (toolbar-utils):
* toolbar-utils.el ('toolbar-add-exec-macro): New.
* toolbar-utils.el (toolbar-add-exec-macro):
* uniquify.el:
* uniquify.el ('uniquify): New.
* vertical-mode.el:
* vertical-mode.el ('vertical-mode): New.
* where-was-i-db.el:
* where-was-i-db.el ('where-was-i-db): New.
* where-was-i-db.el (where-was-i-db):
* winring.el:
* winring.el ('winring): New.
* winring.el (winring):
Add define-behavior support.
* detached-minibuf.el:
* detached-minibuf.el (add-minibuf-options): Removed.
* detached-minibuf.el ('detached-minibuffer): New.
* detached-minibuf.el (toggle-minibuf): New.
Do not modify Options menu when define-behavior is set; not allowed.
Add define-behavior support. Delete `add-minibuf-options'.
Move minibuffer options to the behavior commands submenu.
* foldout.el:
* foldout.el (foldout-inhibit-key-bindings): Removed.
* foldout.el (foldout-install): New.
* foldout.el ('foldout): New.
* foldout.el (foldout):
Remove option to modify key bindings when loaded. Packages should
never do anything when loaded. Create an install function to do it
instead. Add define-behavior support and incorporate install function.
* lazy-shot.el:
* lazy-shot.el ('lazy-shot): New.
* lazy-shot.el (lazy-shot):
Add define-behavior support.
* live-icon.el:
* live-icon.el ('live-icon): New.
* saveplace.el:
* saveplace.el ('save-place): New.
* shell-font.el:
* shell-font.el (shell-font):
* shell-font.el ('shell-font): New.
Add define-behavior support.
Don't auto-install upon load.
xemacs-packages/efs/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* efs.el:
* efs.el ('efs): New.
* efs.el (efs):
Add define-behavior support.
xemacs-packages/eudc/ChangeLog addition:
2004-11-07 Ben Wing <ben(a)xemacs.org>
* eudc.el:
* eudc.el (eudc-menu): New.
* eudc.el (not):
* eudc.el ('eudc): New.
Add define-behavior support.
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
xemacs-packages/footnote/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* footnote.el:
* footnote.el (footnote-mode):
* footnote.el ('footnote): New.
xemacs-packages/games/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* gamegrid.el:
* gamegrid.el (gamegrid): New.
* snake.el:
* snake.el (snake): New.
* sokoban.el:
* sokoban.el (sokoban): New.
* tetris.el:
* tetris.el (tetris): New.
Define a custom group for each of these.
* sokoban.el ('sokoban): New.
* tetris.el ('tetris): New.
Add define-behavior support.
xemacs-packages/ispell/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* ispell.el:
* ispell.el ('ispell): New.
Add define-behavior support.
xemacs-packages/mh-e/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* mh-e.el:
* mh-e.el ('mh): New.
Add define-behavior support.
xemacs-packages/mine/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* xmine.el:
* xmine.el ('xmine): New.
Add define-behavior support.
xemacs-packages/misc-games/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* NeXTify.el:
* NeXTify.el (NeXTify): New.
* advocacy.el:
* advocacy.el (advocacy): New.
* blackbox.el:
* blackbox.el (blackbox): New.
* conx.el:
* conx.el (conx): New.
* decipher.el:
* decipher.el (decipher): New.
* dissociate.el:
* dissociate.el (dissociate): New.
* doctor.el:
* doctor.el (doctor): New.
* dunnet.el:
* dunnet.el (dunnet): New.
* flame.el:
* flame.el (flame): New.
* gomoku.el (gomoku): New.
* hanoi.el:
* hanoi.el (hanoi): New.
* life.el:
* life.el (life): New.
* morse.el:
* morse.el (morse): New.
* mpuz.el:
* mpuz.el (mpuz): New.
* rot13.el:
* rot13.el (rot13): New.
* studly.el:
* studly.el (studly): New.
Define a custom group for each of these.
* doctor.el ('doctor): New.
* dunnet.el ('dunnet): New.
* flame.el ('flame): New.
* hanoi.el ('hanoi): New.
* life.el ('life): New.
* mpuz.el ('mpuz): New.
Add define-behavior support.
xemacs-packages/os-utils/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* jka-compr.el:
* jka-compr.el ('jka-compr): New.
Add define-behavior support.
xemacs-packages/pcl-cvs/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* pcl-cvs-defs.el (progn):
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
* pcl-cvs.el:
* pcl-cvs.el ('pcl-cvs): New.
Add define-behavior support.
xemacs-packages/ps-print/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* ps-mule.el:
Add custom-define cookie for custom-defines.el support.
xemacs-packages/psgml/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* psgml-html.el (html-mode):
Clean up font-lock setup. XEmacs has done it the FSF way
for time immemorial.
xemacs-packages/text-modes/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* filladapt.el:
* filladapt.el ('filladapt): New.
* filladapt.el (filladapt):
Add define-behavior support.
* flyspell.el:
Add custom-define cookie for flyspell-emacs.
xemacs-packages/vc/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* vc-hooks.el:
* vc-hooks.el (featurep):
* vc-hooks.el ('vc): New.
Add autoload cookie for custom-defines.
Add define-behavior support.
Do not modify Tools menu when define-behavior is set; this is not
allowed, as the Behavior system controls the Tools menu completely.
Tools menu mods incorporated info define-behavior support.
xemacs-packages/vm/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* vm-version.el:
* vm-version.el ('vm): New.
Add define-behavior support.
xemacs-packages/w3/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* lisp/w3.el:
* lisp/w3.el ('w3): New.
Add define-behavior support.
xemacs-packages/xemacs-base/ChangeLog addition:
2004-11-08 Ben Wing <ben(a)xemacs.org>
* compile.el:
* compile.el ('grep): New.
* compile.el ('compile): New.
Add define-behavior support for compile and grep.
* shell.el:
* shell.el ('shell): New.
Add define-behavior support.
packages2 source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: xemacs-packages/xemacs-base/shell.el xemacs-packages/xemacs-base/compile.el xemacs-packages/w3/lisp/w3.el xemacs-packages/vm/vm-version.el xemacs-packages/vc/vc-hooks.el xemacs-packages/text-modes/flyspell.el xemacs-packages/text-modes/filladapt.el xemacs-packages/psgml/psgml-html.el xemacs-packages/ps-print/ps-mule.el xemacs-packages/pcl-cvs/pcl-cvs.el xemacs-packages/pcl-cvs/pcl-cvs-defs.el xemacs-packages/pc/pending-del.el xemacs-packages/os-utils/jka-compr.el xemacs-packages/misc-games/studly.el xemacs-packages/misc-games/rot13.el xemacs-packages/misc-games/mpuz.el xemacs-packages/misc-games/morse.el xemacs-packages/misc-games/life.el xemacs-packages/misc-games/hanoi.el xemacs-packages/misc-games/gomoku.el xemacs-packages/misc-games/flame.el xemacs-packages/misc-games/dunnet.el xemacs-packages/misc-games/doctor.el xemacs-packages/misc-games/dissociate.el xemacs-packages/misc-games/decipher.el xemacs-packages/misc-games/conx.el xemacs-packages/misc-games/b!
lackbox.el xemacs-packages/misc-games/advocacy.el xemacs-packages/misc-games/NeXTify.el xemacs-packages/mine/xmine.el xemacs-packages/mh-e/mh-e.el xemacs-packages/ispell/ispell.el xemacs-packages/games/tetris.el xemacs-packages/games/sokoban.el xemacs-packages/games/snake.el xemacs-packages/games/gamegrid.el xemacs-packages/footnote/footnote.el xemacs-packages/eudc/eudc.el xemacs-packages/efs/efs.el xemacs-packages/edit-utils/winring.el xemacs-packages/edit-utils/where-was-i-db.el xemacs-packages/edit-utils/vertical-mode.el xemacs-packages/edit-utils/uniquify.el xemacs-packages/edit-utils/toolbar-utils.el xemacs-packages/edit-utils/shell-font.el xemacs-packages/edit-utils/setnu.el xemacs-packages/edit-utils/scroll-in-place.el xemacs-packages/edit-utils/saveplace.el xemacs-packages/edit-utils/savehist.el xemacs-packages/edit-utils/saveconf.el xemacs-packages/edit-utils/rsz-minibuf.el xemacs-packages/edit-utils/resume.el xemacs-packages/edit-utils/reportmail.el xemacs-package!
s/edit-utils/redo.el xemacs-packages/edit-utils/recent-files.e!
l xemacs
-packages/edit-utils/power-macros.el xemacs-packages/edit-utils/popper.el xemacs-packages/edit-utils/permanent-buffers.el xemacs-packages/edit-utils/paren.el xemacs-packages/edit-utils/page-ext.el xemacs-packages/edit-utils/live-icon.el xemacs-packages/edit-utils/lazy-shot.el xemacs-packages/edit-utils/lazy-lock.el xemacs-packages/edit-utils/iswitchb.el xemacs-packages/edit-utils/id-select.el xemacs-packages/edit-utils/hippie-exp.el xemacs-packages/edit-utils/func-menu.el xemacs-packages/edit-utils/foldout.el xemacs-packages/edit-utils/flow-ctrl.el xemacs-packages/edit-utils/floating-toolbar.el xemacs-packages/edit-utils/file-part.el xemacs-packages/edit-utils/fast-lock.el xemacs-packages/edit-utils/edit-toolbar.el xemacs-packages/edit-utils/edit-faces.el xemacs-packages/edit-utils/detached-minibuf.el xemacs-packages/edit-utils/desktop.el xemacs-packages/edit-utils/dabbrev.el xemacs-packages/edit-utils/completion.el xemacs-packages/edit-utils/blink-paren.el xemacs-packages/e!
dit-utils/blink-cursor.el xemacs-packages/edit-utils/balloon-help.el xemacs-packages/edit-utils/avoid.el xemacs-packages/ediff/ediff-hook.el xemacs-packages/debug/gdb.el xemacs-packages/debug/dbx.el xemacs-packages/cookie/yow.el xemacs-packages/calendar/calendar.el mule-packages/skk/skk-foreword.el
cvs server: Diffing .
cvs server: Diffing mule-packages
cvs server: Diffing mule-packages/edict
cvs server: Diffing mule-packages/egg-its
cvs server: Diffing mule-packages/latin-unity
cvs server: Diffing mule-packages/leim
cvs server: Diffing mule-packages/leim/quail
cvs server: Diffing mule-packages/locale
cvs server: Diffing mule-packages/locale/app-defaults
cvs server: Diffing mule-packages/locale/app-defaults/de
cvs server: Diffing mule-packages/locale/app-defaults/fr
cvs server: Diffing mule-packages/locale/app-defaults/ja
cvs server: Diffing mule-packages/locale/app-defaults/ro
cvs server: Diffing mule-packages/locale/start-files
cvs server: Diffing mule-packages/locale/start-files/fr
cvs server: Diffing mule-packages/locale/start-files/ja
cvs server: Diffing mule-packages/locale/start-files/ro
cvs server: Diffing mule-packages/lookup
cvs server: Diffing mule-packages/lookup/etc
cvs server: Diffing mule-packages/lookup/lisp
cvs server: Diffing mule-packages/lookup/packages
cvs server: Diffing mule-packages/lookup/packages/dict-misc
cvs server: Diffing mule-packages/lookup/packages/jitenban97
cvs server: Diffing mule-packages/lookup/texi
cvs server: Diffing mule-packages/mule-base
Index: mule-packages/skk/skk-foreword.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/mule-packages/skk/skk-foreword.el,v
retrieving revision 1.5
diff -u -p -r1.5 skk-foreword.el
--- mule-packages/skk/skk-foreword.el 2002/04/28 07:12:27 1.5
+++ mule-packages/skk/skk-foreword.el 2005/01/31 20:55:38
＠＠ -453,6 +453,8 ＠＠
(define-obsolete-function-alias 'skk-isearch-backward 'isearch-backward)
(define-obsolete-function-alias 'skk-isearch-backward-regexp 'isearch-backward-regexp)
+;; XEmacs: this must autoload, for custom-defines
+;;;###autoload
(defconst skk-background-mode
;; from font-lock-make-faces of font-lock.el Welcome!
(cond
cvs server: Diffing mule-packages/skk/etc
cvs server: Diffing mule-packages/skk/texi
cvs server: Diffing unsupported
cvs server: Diffing unsupported/rendhalver
cvs server: Diffing unsupported/scop
cvs server: Diffing unsupported/scop/antlr-mode
cvs server: Diffing unsupported/scop/antlr-mode/lisp
cvs server: Diffing unsupported/scop/cogre
cvs server: Diffing unsupported/scop/ecb
cvs server: Diffing unsupported/scop/ede
cvs server: Diffing unsupported/scop/generic-modes
cvs server: Diffing unsupported/scop/vc
cvs server: Diffing unsupported/simon
cvs server: Diffing unsupported/simon/asn1
cvs server: Diffing unsupported/simon/epop3
cvs server: Diffing unsupported/simon/flim
cvs server: Diffing unsupported/simon/flim/tests
cvs server: Diffing unsupported/stephen
cvs server: Diffing unsupported/stephen/synfl
cvs server: Diffing unsupported/stephen/synfl/doc
cvs server: Diffing xemacs-packages
cvs server: Diffing xemacs-packages/Sun
cvs server: Diffing xemacs-packages/ada
cvs server: Diffing xemacs-packages/apel
cvs server: Diffing xemacs-packages/auctex
cvs server: Diffing xemacs-packages/auctex/etc
cvs server: Diffing xemacs-packages/auctex/images
cvs server: Diffing xemacs-packages/auctex/texi
cvs server: Diffing xemacs-packages/bbdb
cvs server: Diffing xemacs-packages/bbdb/lisp
cvs server: Diffing xemacs-packages/bbdb/misc
cvs server: Diffing xemacs-packages/bbdb/tex
cvs server: Diffing xemacs-packages/bbdb/texinfo
cvs server: Diffing xemacs-packages/bbdb/utils
cvs server: Diffing xemacs-packages/build
cvs server: Diffing xemacs-packages/c-support
cvs server: Diffing xemacs-packages/calc
cvs server: Diffing xemacs-packages/calendar
Index: xemacs-packages/calendar/calendar.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/calendar/calendar.el,v
retrieving revision 1.7
diff -u -p -r1.7 calendar.el
--- xemacs-packages/calendar/calendar.el 2003/08/28 06:57:28 1.7
+++ xemacs-packages/calendar/calendar.el 2005/01/31 20:55:39
＠＠ -2629,6 +2629,21 ＠＠ Defaults to today's date if DATE is not
(run-hooks 'calendar-load-hook)
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'calendar
+ "Not documented."
+:group 'editing ;; #### ?? Where does this go ??
+:commands
+ '(["%_3-Month Calendar" calendar]
+ ["%_Diary" diary]
+ ["%_Holidays" holidays]
+ ;; we're all pagans at heart ...
+ ["%_Phases of the Moon" phases-of-moon]
+ ["%_Sunrise/Sunset" sunrise-sunset])
+))
+
(provide 'calendar)
;;; Local variables:
cvs server: Diffing xemacs-packages/cc-mode
cvs server: Diffing xemacs-packages/clearcase
cvs server: Diffing xemacs-packages/cookie
Index: xemacs-packages/cookie/yow.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/cookie/yow.el,v
retrieving revision 1.2
diff -u -p -r1.2 yow.el
--- xemacs-packages/cookie/yow.el 2002/03/22 17:58:54 1.2
+++ xemacs-packages/cookie/yow.el 2005/01/31 20:55:40
＠＠ -134,6 +134,17 ＠＠ If called interactively, display a list
(doctor-ret-or-read 1)
(doctor-ret-or-read 1)))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'yow
+ "Not documented."
+:group 'games
+:commands
+ '(["Quote from %_Zippy" yow]
+ ["Ps%_ychoanalyze Zippy!" psychoanalyze-pinhead]))
+)
+
(provide 'yow)
;;; yow.el ends here
cvs server: Diffing xemacs-packages/crisp
cvs server: Diffing xemacs-packages/debug
Index: xemacs-packages/debug/dbx.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/debug/dbx.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 dbx.el
--- xemacs-packages/debug/dbx.el 1998/01/14 06:44:09 1.1.1.1
+++ xemacs-packages/debug/dbx.el 2005/01/31 20:55:40
＠＠ -168,6 +168,18 ＠＠ BEGIN bounds the search. If QUIET, just
(process-send-string dbx-process
(concat "stop at \"" file-name "\":" line "\n"))))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'dbx
+ "Not documented."
+:short-doc "DBX"
+:group 'programming
+:commands
+ '(["%_DBX..." dbx]))
+)
+
(provide 'dbx)
;;; dbx.el ends here
Index: xemacs-packages/debug/gdb.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/debug/gdb.el,v
retrieving revision 1.5
diff -u -p -r1.5 gdb.el
--- xemacs-packages/debug/gdb.el 2002/09/24 05:52:56 1.5
+++ xemacs-packages/debug/gdb.el 2005/01/31 20:55:40
＠＠ -711,6 +711,17 ＠＠ It is for customization by you.")
(set-buffer (find-file-noselect (car gdb-last-frame)))
(gdb-clear)))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'gdb
+ "Not documented."
+:short-doc "GDB"
+:group 'programming
+:commands
+ '(["%_GDB..." gdb]))
+)
+
(provide 'gdb)
;;; gdb.el ends here
cvs server: Diffing xemacs-packages/dictionary
cvs server: Diffing xemacs-packages/dictionary/debian
cvs server: Diffing xemacs-packages/dired
cvs server: Diffing xemacs-packages/docbookide
cvs server: Diffing xemacs-packages/ecb
cvs server: Diffing xemacs-packages/ecb/ecb-images
cvs server: Diffing xemacs-packages/ecb/ecb-images/default
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-10
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-14
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-15
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-16
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-17
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-18
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-19
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-20
cvs server: Diffing xemacs-packages/ecb/ecb-images/default/height-21
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-10
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-14
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-15
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-16
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-17
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-18
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-19
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-20
cvs server: Diffing xemacs-packages/ecb/ecb-images/directories/height-21
cvs server: Diffing xemacs-packages/ecb/ecb-images/methods
cvs server: Diffing xemacs-packages/ecb/ecb-images/methods/height-14_to_21
cvs server: Diffing xemacs-packages/ecb/ecb-images/sources
cvs server: Diffing xemacs-packages/ecb/ecb-images/sources/height-14_to_21
cvs server: Diffing xemacs-packages/ecrypto
cvs server: Diffing xemacs-packages/edebug
cvs server: Diffing xemacs-packages/ediff
Index: xemacs-packages/ediff/ediff-hook.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ediff/ediff-hook.el,v
retrieving revision 1.11
diff -u -p -r1.11 ediff-hook.el
--- xemacs-packages/ediff/ediff-hook.el 2003/05/18 17:49:46 1.11
+++ xemacs-packages/ediff/ediff-hook.el 2005/01/31 20:55:41
＠＠ -149,8 +149,10 ＠＠
))
;; put these menus before Object-Oriented-Browser in Tools menu
+ ;; Sorry, this is not allowed in 21.5.
(if (and (featurep 'menubar) (not (featurep 'infodock))
- (not (featurep 'ediff-hook)))
+ (not (featurep 'ediff-hook))
+ (not (fboundp 'define-behavior-group)))
(ediff-xemacs-init-menus)))
;; Emacs--only if menu-bar is loaded
＠＠ -367,6 +369,14 ＠＠
) ; if purify-flag
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'ediff
+"Not documented."
+:group 'files
+:commands (list ediff-menu ediff-merge-menu epatch-menu ediff-misc-menu))
+)
(provide 'ediff-hook)
cvs server: Diffing xemacs-packages/ediff/etc
cvs server: Diffing xemacs-packages/edit-utils
Index: xemacs-packages/edit-utils/avoid.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/avoid.el,v
retrieving revision 1.6
diff -u -p -r1.6 avoid.el
--- xemacs-packages/edit-utils/avoid.el 2002/04/10 23:35:37 1.6
+++ xemacs-packages/edit-utils/avoid.el 2005/01/31 20:55:41
＠＠ -404,4 +404,37 ＠＠ definition of \"random distance\".)"
;;;###autoload
(add-minor-mode 'mouse-avoidance-mode 'mouse-avoidance-mode-line-string)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'avoid
+"For those who are annoyed by the mouse pointer obscuring text,
+this mode moves the mouse pointer - either just a little out of
+the way, or all the way to the corner of the frame.
+
+Customize `mouse-avoidance-mode' to one of the symbols `banish',
+`exile', `jump', `animate', `cat-and-mouse', `proteus', or `none'.
+
+Effects of the different modes:
+ * banish: Move the mouse to the upper-right corner on any keypress.
+ * exile: Move the mouse to the corner only if the cursor gets too close,
+ and allow it to return once the cursor is out of the way.
+ * jump: If the cursor gets too close to the mouse, displace the mouse
+ a random distance & direction.
+ * animate: As `jump', but shows steps along the way for illusion of motion.
+ * cat-and-mouse: Same as `animate'.
+ * proteus: As `animate', but changes the shape of the mouse pointer too.
+
+Whenever the mouse is moved, the frame is also raised.
+
+\(see `mouse-avoidance-threshold' for definition of \"too close\",
+and `mouse-avoidance-nudge-dist' and `mouse-avoidance-nudge-var' for
+definition of \"random distance\".)"
+:short-doc "Keep mouse away from cursor"
+:enable #'(lambda ()
+ (mouse-avoidance-mode 'animate))
+:disable #'(lambda ()
+ (mouse-avoidance-mode 'none)))
+)
+
;;; avoid.el ends here
Index: xemacs-packages/edit-utils/balloon-help.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/balloon-help.el,v
retrieving revision 1.6
diff -u -p -r1.6 balloon-help.el
--- xemacs-packages/edit-utils/balloon-help.el 2002/01/22 14:22:56 1.6
+++ xemacs-packages/edit-utils/balloon-help.el 2005/01/31 20:55:42
＠＠ -586,3 +586,52 ＠＠ This command must be bound to a mouse ev
(add-hook 'pre-command-hook 'balloon-help-pre-command-hook)
(add-hook 'mouse-leave-frame-hook 'balloon-help-mouse-leave-frame-hook)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'balloon-help
+"With Balloon Help enabled, a small frame is displayed whenever
+the mouse rests on an object that has a help property of some
+kind. The text of that help property is displayed in the frame.
+
+If you want Balloon Help mode enabled in some buffers only, use
+`balloon-help-minor-mode' instead.
+
+For extents, the 'balloon-help' property is checked.
+
+For toolbar buttons, the help-string slot of the toolbar button
+is checked.
+
+If the value is a string, it is used as the help message.
+
+If the property's value is a symbol, it is assumed to be the name
+of a function and it will be called with one argument, the object
+under the mouse, and the return value of that function will be
+used as the help message.
+
+The balloon-help frame is a transient window that is not
+normally decorated by window managers, so the following
+window manager directives may not be needed. But if they
+are:
+
+For ol[v]wm use this in .Xdefaults:
+ olvwm.NoDecor: balloon-help
+ or
+ olwm.MinimalDecor: balloon-help
+
+For fvvm version 1 use this in your .fvwmrc:
+ NoTitle balloon-help
+or
+ Style \"balloon-help\" NoTitle, NoHandles, BorderWidth 0
+
+For twm use this in your .twmrc:
+ NoTitle { \"balloon-help\" }
+"
+:short-doc "Balloon help"
+:group 'display
+:enable #'(lambda ()
+ (balloon-help-mode 1))
+:disable #'(lambda ()
+ (balloon-help-mode 0)))
+)
Index: xemacs-packages/edit-utils/blink-cursor.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/blink-cursor.el,v
retrieving revision 1.4
diff -u -p -r1.4 blink-cursor.el
--- xemacs-packages/edit-utils/blink-cursor.el 2001/12/04 02:15:32 1.4
+++ xemacs-packages/edit-utils/blink-cursor.el 2005/01/31 20:55:42
＠＠ -134,6 +134,19 ＠＠ each TIMEOUT secs (can be a float)."
(if (not last-input-time)
(setq last-input-time (cons 0 0))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'blink-cursor
+"Enable or disable a blinking cursor."
+:short-doc "Make cursor blink"
+:group 'keyboard
+:enable #'(lambda ()
+ (blink-cursor-mode 1))
+:disable #'(lambda ()
+ (blink-cursor-mode 0)))
+)
+
(provide 'blink-cursor)
;;; blink-cursor.el ends here
Index: xemacs-packages/edit-utils/blink-paren.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/blink-paren.el,v
retrieving revision 1.2
diff -u -p -r1.2 blink-paren.el
--- xemacs-packages/edit-utils/blink-paren.el 2000/10/06 09:08:00 1.2
+++ xemacs-packages/edit-utils/blink-paren.el 2005/01/31 20:55:42
＠＠ -176,6 +176,19 ＠＠ With a non-positive argument, turns it o
(interactive)
(blink-paren 1))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'blink-paren
+"Blink the matching paren."
+:short-doc "Blink the matching paren"
+:group 'display
+:enable #'(lambda ()
+ (blink-paren 1))
+:disable #'(lambda ()
+ (blink-paren 0)))
+)
+
(provide 'blink-paren)
(blink-paren 1)
Index: xemacs-packages/edit-utils/completion.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/completion.el,v
retrieving revision 1.4
diff -u -p -r1.4 completion.el
--- xemacs-packages/edit-utils/completion.el 2004/06/18 05:43:55 1.4
+++ xemacs-packages/edit-utils/completion.el 2005/01/31 20:55:42
＠＠ -2722,6 +2722,180 ＠＠ TYPE is the type of the wrapper to be ad
(cmpl-statistics-block
(record-completion-file-loaded))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'completion
+"After you type a few characters, pressing the \"complete\" key inserts
+the rest of the word you are likely to type.
+
+This watches all the words that you type and remembers them. When
+typing a new word, pressing \"complete\" (meta-return) \"completes\" the
+word by inserting the most recently used word that begins with the
+same characters. If you press meta-return repeatedly, it cycles
+through all the words it knows about.
+
+ If you like the completion then just continue typing, it is as if you
+entered the text by hand. If you want the inserted extra characters
+to go away, type control-w or delete. More options are described below.
+
+ The guesses are made in the order of the most recently \"used\". Typing
+in a word and then typing a separator character (such as a space) \"uses\"
+the word. So does moving a cursor over the word. If no words are found,
+it uses an extended version of the dabbrev style completion.
+
+ You automatically save the completions you use to a file between
+sessions.
+
+ Completion enables programmers to enter longer, more descriptive
+variable names while typing fewer keystrokes than they normally would.
+
+
+Full documentation
+--------------------
+
+ A \"word\" is any string containing characters with either word or symbol
+syntax. [E.G. Any alphanumeric string with hyphens, underscores, etc.]
+Unless you change the constants, you must type at least three characters
+for the word to be recognized. Only words longer than 6 characters are
+saved.
+
+ When you load this file, completion will be on. I suggest you use the
+compiled version (because it is noticeably faster).
+
+ M-X completion-mode toggles whether or not new words are added to the
+database by changing the value of enable-completion.
+
+ SAVING/LOADING COMPLETIONS
+ Completions are automatically saved from one session to another
+(unless save-completions-flag or enable-completion is nil).
+Loading this file (or calling initialize-completions) causes EMACS
+to load a completions database for a saved completions file
+(default: ~/.completions). When you exit, EMACS saves a copy of the
+completions that you
+often use. When you next start, EMACS loads in the saved completion file.
+
+ The number of completions saved depends loosely on
+*saved-completions-decay-factor*. Completions that have never been
+inserted via \"complete\" are not saved. You are encouraged to experiment
+with different functions (see compute-completion-min-num-uses).
+
+ Some completions are permanent and are always saved out. These
+completions have their num-uses slot set to T. Use
+add-permanent-completion to do this
+
+ Completions are saved only if enable-completion is T. The number of old
+versions kept of the saved completions file is controlled by
+completions-file-versions-kept.
+
+COMPLETE KEY OPTIONS
+ The complete function takes a numeric arguments.
+ control-u :: leave the point at the beginning of the completion rather
+ than the middle.
+ a number :: rotate through the possible completions by that amount
+ `-' :: same as -1 (insert previous completion)
+
+HOW THE DATABASE IS MAINTAINED
+ <write>
+
+UPDATING THE DATABASE MANUALLY
+ m-x kill-completion
+ kills the completion at point.
+ m-x add-completion
+ m-x add-permanent-completion
+
+UPDATING THE DATABASE FROM A SOURCE CODE FILE
+ m-x add-completions-from-buffer
+ Parses all the definition names from a C or LISP mode buffer and
+ adds them to the completion database.
+
+ m-x add-completions-from-lisp-file
+ Parses all the definition names from a C or Lisp mode file and
+ adds them to the completion database.
+
+UPDATING THE DATABASE FROM A TAGS TABLE
+ m-x add-completions-from-tags-table
+ Adds completions from the current tags-table-buffer.
+
+HOW A COMPLETION IS FOUND
+ <write>
+
+STRING CASING
+ Completion is string case independent if case-fold-search has its
+ normal default of T. Also when the completion is inserted the case of the
+ entry is coerced appropriately.
+ [E.G. APP --> APPROPRIATELY app --> appropriately
+ App --> Appropriately]
+
+INITIALIZATION
+ The form `(initialize-completions)' initializes the completion system by
+trying to load in the user's completions. After the first cal, further
+calls have no effect so one should be careful not to put the form in a
+site's standard site-init file.
+
+--------------------------------------------------------------------------
+
+
+
+--------------------------------------------------------------------------
+Functions you might like to call
+--------------------------------------------------------------------------
+
+ add-completion string &optional num-uses
+ Adds a new string to the database
+
+ add-permanent-completion string
+ Adds a new string to the database with num-uses = T
+
+
+ kill-completion string
+ Kills the completion from the database.
+
+ clear-all-completions
+ Clears the database
+
+ list-all-completions
+ Returns a list of all completions.
+
+
+ next-completion string &optional index
+ Returns a completion entry that starts with string.
+
+ find-exact-completion string
+ Returns a completion entry that exactly matches string.
+
+ complete
+ Inserts a completion at point
+
+ initialize-completions
+ Loads the completions file and sets up so that exiting emacs will
+ save them.
+
+ save-completions-to-file &optional filename
+ load-completions-from-file &optional filename
+
+----------------------------------------------
+Other functions
+----------------------------------------------
+
+ get-completion-list string
+
+These things are for manipulating the structure
+ make-completion string num-uses
+ completion-num-uses completion
+ completion-string completion
+ set-completion-num-uses completion num-uses
+ set-completion-string completion string
+"
+:group 'editing
+:short-doc "Dynamic word completion"
+:require 'completion
+:enable #'(lambda ()
+ (initialize-completion))
+ ;; can't :disable
+ )
+)
+
(provide 'completion)
;;; completion.el ends here
Index: xemacs-packages/edit-utils/dabbrev.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/dabbrev.el,v
retrieving revision 1.4
diff -u -p -r1.4 dabbrev.el
--- xemacs-packages/edit-utils/dabbrev.el 2004/11/09 04:19:58 1.4
+++ xemacs-packages/edit-utils/dabbrev.el 2005/01/31 20:55:43
＠＠ -1055,6 +1055,61 ＠＠ Leaves point at the location of the star
"^No possible abbreviation preceding point$"))
(add-to-list 'debug-ignored-errors mess))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'dabbrev
+"The purpose with this package is to let you write just a few
+characters of words you've written earlier to be able to expand
+them.
+
+To expand a word, just put the point right after the word and press
+M-/ (dabbrev-expand) or M-C-/ (dabbrev-completion).
+
+Check out the customizable variables below to learn about all the
+features of this package.
+
+ Hints and tips for major modes writers:
+
+Recommended values C/Lisp etc text
+dabbrev-case-fold-search nil t
+dabbrev-case-replace nil t
+
+Set the variables you want special for your mode like this:
+(set (make-local-variable 'dabbrev-case-replace) nil)
+Then you don't interfere with other modes.
+
+If your mode handles buffers that refers to other buffers
+(i.e. compilation-mode, gud-mode), then try to set
+`dabbrev-select-buffers-function' or `dabbrev-friend-buffer-function'
+to a function that point out those buffers.
+
+Same goes for major-modes that are connected to other modes. There
+are for instance a number of mail-modes. One for reading, one for
+creating a new mail etc. Maybe those should be connected.
+
+Example for GNUS (when we write a reply, we want dabbrev to look in
+the article for expansion):
+(set (make-local-variable 'dabbrev-friend-buffer-function)
+ (lambda (buffer)
+ (save-excursion
+ (set-buffer buffer)
+ (memq major-mode '(news-reply-mode gnus-article-mode)))))
+
+
+Known bugs and limitations.
+- Possible to do several levels of `dabbrev-completion' in the
+ minibuffer.
+- dabbrev-completion doesn't handle resetting the globals variables
+ right. It resets them after finding the abbrev."
+:short-doc "dynamic abbreviation package"
+:group 'editing
+:commands '(["Expand previous word \"dynamically\"" dabbrev-expand])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
(provide 'dabbrev)
;; dabbrev.el ends here
Index: xemacs-packages/edit-utils/desktop.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/desktop.el,v
retrieving revision 1.8
diff -u -p -r1.8 desktop.el
--- xemacs-packages/edit-utils/desktop.el 2004/06/17 11:09:39 1.8
+++ xemacs-packages/edit-utils/desktop.el 2005/01/31 20:55:43
＠＠ -796,6 +796,77 ＠＠ to provide correct modes for autoloaded
(desktop-load-default)
(desktop-read))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'desktop
+"Save the Desktop, i.e.,
+ - some global variables
+ - the list of buffers with associated files. For each buffer also
+ - the major mode
+ - the default directory
+ - the point
+ - the mark & mark-active
+ - buffer-read-only
+ - some local variables
+
+To use this, first put these two lines in the bottom of your .emacs
+file (the later the better):
+
+ (desktop-load-default)
+ (desktop-read)
+
+Between these two lines you may wish to add something that updates the
+variables `desktop-globals-to-save' and/or `desktop-locals-to-save'. If
+for instance you want to save the local variable `foobar' for every buffer
+in which it is local, you could add the line
+
+ (setq desktop-locals-to-save (cons 'foobar desktop-locals-to-save))
+
+To avoid saving excessive amounts of data you may also wish to add
+something like the following
+
+ (add-hook 'kill-emacs-hook
+ '(lambda ()
+ (desktop-truncate search-ring 3)
+ (desktop-truncate regexp-search-ring 3)))
+
+which will make sure that no more than three search items are saved. You
+must place this line *after* the `(desktop-load-default)' line. See also
+the variable `desktop-save-hook'.
+
+Start Emacs in the root directory of your \"project\"
+. The desktop saver
+is inactive by default. You activate it by M-x desktop-save RET. When
+you exit the next time the above data will be saved. This ensures that
+all the files you were editing will be reloaded the next time you start
+Emacs from the same directory and that points will be set where you
+left them. If you save a desktop file in your home directory it will
+act as a default desktop when you start Emacs from a directory that
+doesn't have its own. I never do this, but you may want to.
+
+Some words on minor modes: Most minor modes are controlled by
+buffer-local variables, which have a standard save / restore
+mechanism. To handle all minor modes, we take the following
+approach: (1) check whether the variable name from
+`minor-mode-alist' is also a function; and (2) use translation
+table `desktop-minor-mode-table' in the case where the two names
+are not the same.
+
+By the way: don't use desktop.el to customize Emacs -- the file .emacs
+in your home directory is used for that. Saving global default values
+for buffers is an example of misuse.
+
+PLEASE NOTE: The kill ring can be saved as specified by the variable
+`desktop-globals-to-save' (by default it isn't). This may result in saving
+things you did not mean to keep. Use M-x desktop-clear RET."
+:short-doc "save partial status of Emacs when killed"
+:group 'editing
+;; #### Write the hooks correctly so they don't require manual modification
+;; of init.el.
+ )
+)
+
(provide 'desktop)
;;; desktop.el ends here
Index: xemacs-packages/edit-utils/detached-minibuf.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/detached-minibuf.el,v
retrieving revision 1.2
diff -u -p -r1.2 detached-minibuf.el
--- xemacs-packages/edit-utils/detached-minibuf.el 2001/01/15 05:54:31 1.2
+++ xemacs-packages/edit-utils/detached-minibuf.el 2005/01/31 20:55:43
＠＠ -42,11 +42,11 ＠＠
:group 'frames)
-(defcustom add-minibuf-options t
- "*If nil, prevent minibuffer options from being added to the Options menu.\
-This must be set before detached-minibuf is loaded."
-:type 'boolean
-:group 'detached-minibuf)
+; (defcustom add-minibuf-options t
+; "*If nil, prevent minibuffer options from being added to the Options menu.\
+; This must be set before detached-minibuf is loaded."
+;:type 'boolean
+;:group 'detached-minibuf)
(defcustom minibuf-frame-height 1
"*The height in lines of the minibuffer frame created by make-detached-minibuf"
:type 'integer
＠＠ -64,72 +64,31 ＠＠ This must be set before detached-minibuf
:type 'integer
:group 'detached-minibuf)
-;;
-;; Add minibuffer options to the Options menu
-(if add-minibuf-options
- (progn
- (defun toggle-minibuf ()
- (interactive)
- (if (equal (frame-property (selected-frame) 'minibuffer) t)
-
- ;; This frame already has a minibuffer, so remove the minibuffer.
- ;; Unfortunately, we must delete and redraw the frame
- (let ((fp (frame-properties (selected-frame)))
- (buf (current-buffer))
- (orig (selected-frame)))
-
- ;; Create and select the new frame;
- ;; we have to do this before we delete the old frame.
- (setq fp (plist-remprop fp 'window-id)
- fp (plist-remprop fp 'minibuffer))
- (select-frame
- (make-frame (plist-put fp 'minibuffer nil)))
- (switch-to-buffer buf)
-
- (set-frame-properties
- orig (list 'minibuffer default-minibuffer-frame))
- (delete-frame orig t))
-
- ;; This frame does not have a minibuffer, so add one
- (set-frame-property (selected-frame) 'minibuffer t)))
-
- ;; The menu structure is different before XEmacs 21.2.
- ;; Under 21.1 and previous, add menu items to
- ;; Options/Frame Appearance. Under 21.2+, add the
- ;; menu items to Options/Display.
- (let ((entry-name (if (fboundp 'purecopy-menubar)
- '("Options" "Frame Appearance")
- '("Options" "Display"))))
- (add-menu-button entry-name
- "------"
- nil)
- (add-menu-button entry-name
- ["Toggle minibuffer"
- (toggle-minibuf)
- :style toggle
- :active (not (equal (selected-frame)
- default-minibuffer-frame))
- :selected (equal
- (frame-property (selected-frame) 'minibuffer)
- t)]
- nil)
- (add-menu-button entry-name
- ["Default minibuffer here"
- (setq default-minibuffer-frame (selected-frame))
- :style toggle
- :active (let ((mbf (frame-property
- (selected-frame) 'minibuffer)))
- (or (equal mbf (selected-frame))
- (equal mbf t)))
- :selected (equal (selected-frame)
- default-minibuffer-frame)]
- nil)
- (add-menu-button entry-name
- ["Make a detached minibuffer"
- (make-detached-minibuf)
- :style nil]
- nil))))
+(defun toggle-minibuf ()
+ "Toggle whether the minibuffer exists in the current frame."
+ (interactive)
+ (if (equal (frame-property (selected-frame) 'minibuffer) t)
+ ;; This frame already has a minibuffer, so remove the minibuffer.
+ ;; Unfortunately, we must delete and redraw the frame
+ (let ((fp (frame-properties (selected-frame)))
+ (buf (current-buffer))
+ (orig (selected-frame)))
+
+ ;; Create and select the new frame;
+ ;; we have to do this before we delete the old frame.
+ (setq fp (plist-remprop fp 'window-id)
+ fp (plist-remprop fp 'minibuffer))
+ (select-frame
+ (make-frame (plist-put fp 'minibuffer nil)))
+ (switch-to-buffer buf)
+
+ (set-frame-properties
+ orig (list 'minibuffer default-minibuffer-frame))
+ (delete-frame orig t))
+
+ ;; This frame does not have a minibuffer, so add one
+ (set-frame-property (selected-frame) 'minibuffer t)))
;;
;; Create a minibuffer-only frame.
;;
＠＠ -163,6 +122,39 ＠＠ This must be set before detached-minibuf
;; Bogus! But it avoids annoying screen flash at startup
(if (not command-line-args-left)
(frame-notice-user-settings)))))
+
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'detached-minibuffer
+"Support a detached minibuffer"
+:short-doc "Support a detached minibuffer"
+:group 'buffers-and-windows
+:commands '(["Toggle minibuffer"
+ (toggle-minibuf)
+ :style toggle
+ :active (not (equal (selected-frame)
+ default-minibuffer-frame))
+ :selected (equal
+ (frame-property (selected-frame) 'minibuffer)
+ t)]
+ ["Default minibuffer here"
+ (setq default-minibuffer-frame (selected-frame))
+ :style toggle
+ :active (let ((mbf (frame-property
+ (selected-frame) 'minibuffer)))
+ (or (equal mbf (selected-frame))
+ (equal mbf t)))
+ :selected (equal (selected-frame)
+ default-minibuffer-frame)]
+ ["Make a detached minibuffer"
+ (make-detached-minibuf)
+ :style nil])
+ ;; no :enable
+ ;; no :disable
+ )
+)
(provide 'detached-minibuf)
Index: xemacs-packages/edit-utils/edit-faces.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/edit-faces.el,v
retrieving revision 1.4
diff -u -p -r1.4 edit-faces.el
--- xemacs-packages/edit-utils/edit-faces.el 1999/11/27 20:49:58 1.4
+++ xemacs-packages/edit-utils/edit-faces.el 2005/01/31 20:55:43
＠＠ -370,4 +370,21 ＠＠ M-x edit-faces."
(delete-window))
(kill-buffer "*Edit Faces*"))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'edit-faces
+"This is the file that won't die. Even though we have otherwise completely
+converted to custom, there is still apparently a need to view a lot of
+faces in one buffer."
+:short-doc "Interactive face editing mode"
+:group 'display
+:commands '(["Edit faces" edit-faces]
+ )
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
;;; edit-faces.el ends here
Index: xemacs-packages/edit-utils/edit-toolbar.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/edit-toolbar.el,v
retrieving revision 1.3
diff -u -p -r1.3 edit-toolbar.el
--- xemacs-packages/edit-utils/edit-toolbar.el 2000/07/16 11:22:46 1.3
+++ xemacs-packages/edit-utils/edit-toolbar.el 2005/01/31 20:55:44
＠＠ -542,6 +542,29 ＠＠ Alternatively, I can do this for you now
(or exists (edit-toolbar-prompt-for-initialization))))
(set-buffer-modified-p nil))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'edit-toolbar
+"To use edit-toolbar.el, simply type M-x edit-toolbar RET
+
+For help on the various commands you can type ? in a edit-toolbar
+buffer. To save a modified toolbar type C-x C-s in an edit-toolbar
+buffer. If you want to use a saved toolbar in your future XEmacs
+sessions, add the following line of code to your .emacs file:
+
+ (load \"~/.xemacs/.toolbar\")
+"
+:short-doc "Interactive toolbar editing mode"
+:group 'toolbars
+:commands '(["Edit toolbar" edit-toolbar]
+ )
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
(provide 'edit-toolbar)
;;; edit-toolbar.el ends here
Index: xemacs-packages/edit-utils/fast-lock.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/fast-lock.el,v
retrieving revision 1.3
diff -u -p -r1.3 fast-lock.el
--- xemacs-packages/edit-utils/fast-lock.el 2000/04/07 08:47:40 1.3
+++ xemacs-packages/edit-utils/fast-lock.el 2005/01/31 20:55:44
＠＠ -766,6 +766,55 ＠＠ See `fast-lock-get-face-properties' for
(unless (assq 'fast-lock-mode minor-mode-alist)
(setq minor-mode-alist (append minor-mode-alist '((fast-lock-mode nil)))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'fast-lock
+"Fast Lock mode is a Font Lock support mode.
+It makes visiting a file in Font Lock mode faster by restoring its face text
+properties from automatically saved associated Font Lock cache files.
+
+See also the lazy-lock package. (But don't use the two at the same time!)
+
+When you visit a file (which has `font-lock-mode' enabled) that has a
+corresponding Font Lock cache file associated with it, the Font Lock cache
+will be loaded from that file instead of being generated by Font Lock code.
+
+Caveats:
+
+A cache will be saved when visiting a compressed file using crypt++, but not
+be read. This is a \"feature\"/\"consequence\"/\"bug\" of crypt++.
+
+Version control packages are likely to stamp all over file modification
+times. Therefore the act of checking out may invalidate a cache.
+
+More specifically:
+
+If Fast Lock mode is enabled, and the current buffer does not contain any text
+properties, any associated Font Lock cache is used if its timestamp matches the
+buffer's file, and its `font-lock-keywords' match those that you are using.
+
+Font Lock caches may be saved:
+- When you save the file's buffer.
+- When you kill an unmodified file's buffer.
+- When you exit Emacs, for all unmodified or saved buffers.
+Depending on the value of `fast-lock-save-events'.
+See also the commands `fast-lock-read-cache' and `fast-lock-save-cache'.
+
+Use \\[font-lock-fontify-buffer] to fontify the buffer if the cache is bad.
+
+Various methods of control are provided for the Font Lock cache. In general,
+see variable `fast-lock-cache-directories' and function `fast-lock-cache-name'.
+For saving, see variables `fast-lock-minimum-size', `fast-lock-save-events',
+`fast-lock-save-others' and `fast-lock-save-faces'."
+:short-doc "Automagic text properties caching for fast Font Lock mode"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'font-lock-mode-hook 'turn-on-fast-lock))
+:disable #'(lambda ()
+ (remove-hook 'font-lock-mode-hook 'turn-on-fast-lock))
+ )
+)
;; Provide ourselves:
(provide 'fast-lock)
Index: xemacs-packages/edit-utils/file-part.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/file-part.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 file-part.el
--- xemacs-packages/edit-utils/file-part.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/file-part.el 2005/01/31 20:55:44
＠＠ -271,3 +271,28 ＠＠ Marks the master buffer as modified."
(set-buffer (extent-buffer x))
(set-buffer-modified-p t)))))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'file-part
+"Treat a section of a buffer as a separate file.
+
+Commands:
+
+`make-file-part'
+
+ Make a file part on buffer BUFFER out of the region. Call it NAME.
+This command creates a new buffer containing the contents of the
+region and marks the buffer as referring to the specified buffer,
+called the `master buffer'. When the file-part buffer is saved,
+its changes are integrated back into the master buffer. When the
+master buffer is deleted, all file parts are deleted with it.
+"
+:short-doc "treat a section of a buffer as a separate file"
+:group 'files
+:commands '(["Make file part" make-file-part])
+ ;; no :enable
+ ;; no :disable
+ )
+)
Index: xemacs-packages/edit-utils/floating-toolbar.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/floating-toolbar.el,v
retrieving revision 1.3
diff -u -p -r1.3 floating-toolbar.el
--- xemacs-packages/edit-utils/floating-toolbar.el 2000/10/06 09:08:01 1.3
+++ xemacs-packages/edit-utils/floating-toolbar.el 2005/01/31 20:55:44
＠＠ -382,4 +382,63 ＠＠ extent local toolbar."
(not (eq (device-type) 'x))
(setq floating-toolbar-frame (floating-toolbar-make-toolbar-frame 0 0)))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'floating-toolbar
+"The command `floating-toolbar' pops up a small frame
+containing a toolbar. The command should be bound to a
+button-press event. If the mouse press happens over an
+extent that has a non-nil 'floating-toolbar property, the
+value of that property is the toolbar instantiator that will
+be displayed. Otherwise the toolbar displayed is taken from
+the variable `floating-toolbar'. This variable can be made
+buffer local to produce buffer local floating toolbars.
+
+`floating-toolbar-or-popup-mode-menu' works like `floating-toolbar'
+except that if no toolbar is found, `popup-mode-menu' is called.
+
+`floating-toolbar-from-extent-or-popup-mode-menu' works like
+`floating-toolbar-or-popup-mode-menu' except only extent local
+toolbars are used; the value of floating-toolbar is not used.
+
+Installation:
+
+You will also need to bind a mouse click to `floating-toolbar' or to
+`floating-toolbar-or-popup-mode-menu'.
+
+For 19.12 users:
+ If you are using fvwm, [tv]twm or ol[v]wm, you can also add
+ the following lines to various configuration file to use
+ minimal decorations on the toolbar frame.
+
+ In .emacs:
+ (setq floating-toolbar-frame-name \"floating-toolbar\")
+
+ For ol[v]wm use this in .Xdefaults:
+ olvwm.NoDecor: floating-toolbar
+ or
+ olwm.MinimalDecor: floating-toolbar
+
+ For fvvm use this in your .fvwmrc:
+ NoTitle floating-toolbar
+ or
+ Style \"floating-toolbar\" NoTitle, NoHandles, BorderWidth 0
+
+ For twm use this in your .twmrc:
+ NoTitle { \"floating-toolbar\" }
+
+Under 19.13 and later versions the floating-toolbar frame uses a
+transient window that is not normally decorated by window
+managers. So the window manager directives should not be
+needed for XEmacs 19.13 and beyond."
+:short-doc "popup toolbar support for XEmacs"
+:group 'toolbars
+:commands '(["Pop up floating toolbar" floating-toolbar])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
;;; floating-toolbar.el ends here
Index: xemacs-packages/edit-utils/flow-ctrl.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/flow-ctrl.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 flow-ctrl.el
--- xemacs-packages/edit-utils/flow-ctrl.el 1998/01/14 06:36:15 1.1.1.1
+++ xemacs-packages/edit-utils/flow-ctrl.el 2005/01/31 20:55:44
＠＠ -115,6 +115,35 ＠＠ value of \"vt100-nam\" is treated the sa
(if term
(enable-flow-control))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'flow-control
+"Terminals that use XON/XOFF flow control can cause problems with
+GNU Emacs users. This file contains Emacs Lisp code that makes it
+easy for a user to deal with this problem, when using such a
+terminal.
+
+To invoke these adjustments, a user need only invoke the function
+enable-flow-control-on with a list of terminal types in his/her own
+.emacs file. As arguments, give it the names of one or more terminal
+types in use by that user which require flow control adjustments.
+Here's an example:
+
+ (enable-flow-control-on \"vt200\" \"vt300\" \"vt101\" \"vt131\")
+
+Portability note: This uses (getenv \"TERM\"), and therefore probably
+won't work outside of UNIX-like environments.
+"
+:short-doc "help for lusers on cu(1) or ttys with wired-in ^S/^Q flow control"
+:group 'tty
+:enable #'(lambda ()
+ (enable-flow-control 1))
+:disable #'(lambda ()
+ (enable-flow-control -1))
+ )
+)
+
(provide 'flow-ctrl)
;;; flow-ctrl.el ends here
Index: xemacs-packages/edit-utils/foldout.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/foldout.el,v
retrieving revision 1.2
diff -u -p -r1.2 foldout.el
--- xemacs-packages/edit-utils/foldout.el 2000/04/07 09:15:56 1.2
+++ xemacs-packages/edit-utils/foldout.el 2005/01/31 20:55:44
＠＠ -101,11 +101,11 ＠＠
;; To use foldout, put this in your .emacs:-
;;
-;; (require 'foldout)
+;; (foldout-install)
;;
;; If you don't want it loaded until you need it, try this instead:-
;;
-;; (eval-after-load "outline" '(require 'foldout))
+;; (eval-after-load "outline" '(foldout-install))
;;; Advertisements:
＠＠ -518,9 +518,6 ＠＠ if the event didn't occur on a heading."
;;; Keymaps:
-(defvar foldout-inhibit-key-bindings nil
- "Set non-NIL before loading foldout to inhibit key bindings.")
-
(defvar foldout-mouse-modifiers '(meta control)
"List of modifier keys to apply to foldout's mouse events.
＠＠ -544,8 +541,9 ＠＠ Valid modifiers are shift, control, meta
((eq button 3)
(funcall 'foldout-mouse-hide-or-exit event click-count))))))
-(if foldout-inhibit-key-bindings
- ()
+;;;###autoload
+(defun foldout-install ()
+ "Install foldout."
(define-key outline-mode-map "\C-c\C-z" 'foldout-zoom-subtree)
(define-key outline-mode-map "\C-c\C-x" 'foldout-exit-fold)
(define-key outline-minor-mode-map
＠＠ -574,6 +572,86 ＠＠ Valid modifiers are shift, control, meta
(define-key outline-minor-mode-map mouse-2 'mouse-track)
(define-key outline-minor-mode-map mouse-3 'mouse-track)
))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'foldout
+"This file provides folding editor extensions for outline-mode and
+outline-minor-mode buffers. What's a \"folding editor\"? Read on...
+
+Imagine you're in an outline-mode buffer and you've hidden all the text and
+subheadings under your level-1 headings. You now want to look at the stuff
+hidden under one of these headings. Normally you'd do C-c C-e (show-entry)
+to expose the body or C-c C-i to expose the child (level-2) headings.
+
+With foldout, you do C-c C-z (foldout-zoom-subtree). This exposes the body
+and child subheadings and narrows the buffer so that only the level-1
+heading, the body and the level-2 headings are visible. If you now want to
+look under one of the level-2 headings, position the cursor on it and do C-c
+C-z again. This exposes the level-2 body and its level-3 child subheadings
+and narrows the buffer again. You can keep on zooming in on successive
+subheadings as much as you like. A string in the modeline tells you how
+deep you've gone.
+
+When zooming in on a heading you might only want to see the child
+subheadings. You do this by specifying a numeric argument: C-u C-c C-z.
+You can specify the number of levels of children too (c.f. show-children):
+e.g. M-2 C-c C-z exposes two levels of child subheadings. Alternatively,
+you might only be interested in the body. You do this by specifying a
+negative argument: M-- C-c C-z. You can also cause the whole subtree to be
+expanded, similar to C-c C-s (show-subtree), by specifying a zero argument:
+M-0 C-c C-z.
+
+While you're zoomed in you can still use outline-mode's exposure and hiding
+functions. It won't upset foldout at all. Also, since the buffer is
+narrowed, \"global\" editing actions will only affect the stuff under the
+zoomed-in heading. This is useful for restricting changes to a particular
+chapter or section of your document.
+
+You unzoom (exit) a fold by doing C-c C-x (foldout-exit-fold). This hides
+all the text and subheadings under the top-level heading and returns you to
+the previous view of the buffer. Specifying a numeric argument exits that
+many folds. Specifying a zero argument exits *all* folds.
+
+You might want to exit a fold *without* hiding the text and subheadings.
+You do this by specifying a negative argument. For example, M--2 C-c C-x
+exits two folds and leaves the text and subheadings exposed.
+
+Foldout also provides mouse bindings for entering and exiting folds and for
+showing and hiding text. Hold down Meta and Control, then click a mouse
+button as follows:-
+
+ mouse-1 (foldout-mouse-zoom) zooms in on the heading clicked on:-
+
+ single click expose body
+ double click expose subheadings
+ triple click expose body and subheadings
+ quad click expose entire subtree
+
+ mouse-2 (foldout-mouse-show) exposes text under the heading clicked on:-
+
+ single click expose body
+ double click expose subheadings
+ triple click expose body and subheadings
+ quad click expose entire subtree
+
+ mouse-3 (foldout-mouse-hide-or-exit) hides text under the heading clicked
+ on or exits the fold:-
+
+ single click hide subtree
+ double click exit fold and hide text
+ triple click exit fold without hiding text
+ quad click exit all folds and hide text
+
+You can change the modifier keys used by setting `foldout-mouse-modifiers'.
+"
+:short-doc "Folding extensions for outline-mode"
+:group 'editing
+:require 'foldout
+:enable #'foldout-install
+ )
+)
(provide 'foldout)
Index: xemacs-packages/edit-utils/func-menu.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/func-menu.el,v
retrieving revision 1.28
diff -u -p -r1.28 func-menu.el
--- xemacs-packages/edit-utils/func-menu.el 2004/12/22 21:42:03 1.28
+++ xemacs-packages/edit-utils/func-menu.el 2005/01/31 20:55:45
＠＠ -2752,6 +2752,48 ＠＠ and then kill it will not be slowed down
(set-buffer buffer)
(turn-on-fume-mode)))))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'func-menu
+ "Suppose you have a file with a lot of functions in it. Well, this
+package makes it easy to jump to any of those functions. The names of
+the functions in the current buffer are automatically put into menubar
+menu, you select one of the function-names and the point is moved to
+that very function. The mark is pushed on the mark-ring, so you can
+easily go back to where you were. Alternatively, you can use enter the
+name of the desired function via the minibuffer which offers
+completing read input. In addition, the name of the function before
+point is optionally displayed in the modeline."
+:short-doc "Add a menu of defined functions"
+:require 'func-menu
+:group 'menus
+:enable #'(lambda ()
+ (add-hook 'find-file-hooks 'fume-add-menubar-entry)
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (setq fume-display-in-modeline-p t)
+ (fume-add-menubar-entry)))
+ (buffer-list)))
+:disable #'(lambda ()
+ (remove-hook 'find-file-hooks 'fume-add-menubar-entry)
+ (fset 'widen (symbol-function 'fume-widen))
+ (fset 'narrow-to-region (symbol-function 'narrow-to-region))
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (fume-remove-menubar-entry)
+ (setq fume-display-in-modeline-p nil)
+ (fume-remove-post-command-hook
+ 'fume-tickle-modeline)
+ (fume-remove-post-command-hook
+ 'fume-maybe-install-modeline-feature)
+ (fume-remove-post-command-hook
+ 'fume-rescan-buffer-trigger)))
+ (buffer-list))))
+
+)
+
(provide 'func-menu)
;;; func-menu.el ends here
Index: xemacs-packages/edit-utils/hippie-exp.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/hippie-exp.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 hippie-exp.el
--- xemacs-packages/edit-utils/hippie-exp.el 1998/01/14 06:36:15 1.1.1.1
+++ xemacs-packages/edit-utils/hippie-exp.el 2005/01/31 20:55:46
＠＠ -1124,6 +1124,138 ＠＠ string). It returns t if a new completi
(point)))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'hippie-expand
+"`hippie-expand' is a single function for a lot of different kinds
+of completions and expansions. Called repeatedly it tries all
+possible completions in succession.
+Which kinds of completions to try, and in which order, is
+determined by the contents of `hippie-expand-try-functions-list'.
+Much customization of `hippie-expand' can be made by changing the
+order of, removing, or inserting new functions in this list.
+Given a positive numeric argument, `hippie-expand' jumps directly
+ARG functions forward in this list. Given some other argument
+\(a negative argument or just Ctrl-U) it undoes the tried
+completion.
+
+If the variable `hippie-expand-verbose' is non-nil, `hippie-expand'
+outputs in a message which try-function in the list that is used
+currently (ie. was used currently and will be tried first the next
+time).
+The variable `hippie-expand-max-buffers' determines in how many
+buffers, apart from the current, to search for expansions in. It
+is used by the try-functions named \"-all-buffers\".
+The variable `hippie-expand-ignore-buffers' is a list of regexps
+matching buffer names (as strings) or major modes (as atoms) of
+buffers that should not be searched by the try-functions named
+\"-all-buffers\".
+See also the macro `make-hippie-expand-function' below.
+
+A short description of the current try-functions in this file:
+ `try-complete-file-name' : very convenient to have in any buffer,
+ and not just in the minibuffer or (some) shell-mode. It goes
+ through all possible completions instead of just completing as
+ much as is unique.
+ `try-complete-file-name-partially' : To insert in the list just
+ before `try-complete-file-name' for those who want first to get
+ a file name completed only as many characters as is unique.
+ `try-expand-all-abbrevs' : can be removed if you don't use abbrevs.
+ Otherwise it looks through all abbrev-tables, starting with
+ the local followed by the global.
+ `try-expand-line' : Searches the buffer for an entire line that
+ begins exactly as the current line. Convenient sometimes, for
+ example as a substitute for (or complement to) the history
+ list in shell-like buffers. At other times, only confusing.
+ `try-expand-line-all-buffers' : Like `try-expand-line' but searches
+ in all buffers (except the current). (This may be a little
+ slow, don't use it unless you are really fond of `hippie-expand'.)
+ `try-expand-list' : Tries to expand the text back to the nearest
+ open delimiter, to a whole list from the buffer. Convenient for
+ example when writing lisp or TeX.
+ `try-expand-list-all-buffers' : Like `try-expand-list' but searches
+ in all buffers (except the current).
+ `try-expand-dabbrev' : works exactly as dabbrev-expand (but of
+ course in a way compatible with the other try-functions).
+ `try-expand-dabbrev-all-buffers' : perhaps the most useful of them,
+ like `dabbrev-expand' but searches all Emacs buffers (except the
+ current) for matching words. (No, I don't find this one
+ particularly slow.)
+ `try-expand-dabbrev-visible': Searches the currently visible parts of
+ all windows. Can be put before `try-expand-dabbrev-all-buffers' to
+ first try the expansions you can see.
+ `try-expand-dabbrev-from-kill': Searches the kill ring for a suitable
+ completion of the word. Good to have, just in case the word was not
+ found elsewhere.
+ `try-expand-whole-kill' : Tries to complete text with a whole entry
+ from the kill ring. May be good if you don't know how far up in
+ the kill-ring the required entry is, and don't want to mess with
+ \"Choose Next Paste\".
+ `try-complete-lisp-symbol' : like `lisp-complete-symbol', but goes
+ through all possibilities instead of completing what is unique.
+ Might be tedious (usually a lot of possible completions) and
+ since its function is much like `lisp-complete-symbol', which
+ already has a key of its own, you might want to remove this.
+ `try-complete-lisp-symbol-partially' : To insert in the list just
+ before `try-complete-lisp-symbol' for those who first want to get
+ completion of what is unique in the name.
+
+Not all of the above functions are by default in
+`hippie-expand-try-functions-list'. This variable is better set
+in \".emacs\" to make `hippie-expand' behave maximally convenient
+according to personal taste. Also, instead of loading the
+variable with all kinds of try-functions above, it might be an
+idea to use `make-hippie-expand-function' to construct different
+`hippie-expand'-like functions, with different try-lists and bound
+to different keys. It is also possible to make
+`hippie-expand-try-functions-list' a buffer local variable, and
+let it depend on the mode (by setting it in the mode-hooks).
+
+To write new try-functions, consider the following:
+Each try-function takes one argument OLD which is nil the first
+time the function is called and true in succeeding calls for the
+same string to complete. The first time the function has to
+extract the string before point to complete, and substitute the
+first completion alternative for it. On following calls it has to
+substitute the next possible completion for the last tried string.
+The try-function is to return t as long as it finds new
+possible completions. When there are no more alternatives it has
+to restore the text before point to its original contents, and
+return nil (don't beep or message or anything).
+The try-function can (should) use the following functions:
+ `he-init-string' : Initializes the text to substitute to the
+ contents of the region BEGIN to END. Also sets the variable
+ `he-search-string' to the text to expand.
+ `he-substitute-string' : substitutes STR into the region
+ initialized with `he-init-string'. (An optional second argument
+ TRANS-CASE non-nil, means transfer of case from the abbreviation
+ to the expansion is ok if that is enabled in the buffer.)
+ `he-reset-string' : Resets the initialized region to its original
+ contents.
+There is also a variable: `he-tried-table' which is meant to contain
+all tried expansions so far. The try-function can check this
+variable to see whether an expansion has already been tried
+(hint: `he-string-member').
+
+Known bugs
+
+It may happen that some completion suggestion occurs twice, in
+spite of the use of `he-tried-table' to prevent that. This is
+because different try-functions may try to complete different
+lengths of text, and thus put different amounts of the
+text in `he-tried-table'. Anyway this seems to occur seldom enough
+not to be too disturbing. Also it should NOT be possible for the
+opposite situation to occur, that `hippie-expand' misses some
+suggestion because it thinks it has already tried it."
+:short-doc "expand text trying various ways to find its expansion"
+:group 'editing
+:commands '(["Hippie-expand text at point" hippie-expand])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
(provide 'hippie-exp)
;;; hippie-exp.el ends here
Index: xemacs-packages/edit-utils/id-select.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/id-select.el,v
retrieving revision 1.5
diff -u -p -r1.5 id-select.el
--- xemacs-packages/edit-utils/id-select.el 2001/04/21 23:25:47 1.5
+++ xemacs-packages/edit-utils/id-select.el 2005/01/31 20:55:46
＠＠ -1285,6 +1285,75 ＠＠ Ordering of entries is largely irrelevan
:type '(repeat (list (sexp :tag "Syntax-Char" function)))
:group 'id-select)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'id-select
+"This is a radically cool, drop in mouse and keyboard-based library for
+selecting successively bigger syntactical regions within a buffer.
+Simply load this library and you are ready to try it out by
+double-clicking on various kinds of characters in different buffer major
+modes. You'll quickly get the hang of it. (It also provides a command
+to jump between beginning and end tags within HTML and SGML buffers.)
+
+A great deal of smarts are built-in so that it does the right thing
+almost all of the time; many other attempts at similar behavior such as
+thing.el fail to deal with many file format complexities.
+
+Double clicks of the Selection Key (left mouse key) at the same point
+will select bigger and bigger regions with each successive use. The
+first double click selects a region based upon the character at the
+point of the click. For example, with the point over an opening or
+closing grouping character, such as { or }, the whole grouping is
+selected, e.g. a C function. When on an _ or - within a programming
+language variable name, the whole name is selected. The type of
+selection is displayed in the minibuffer as feedback. When using a
+language based mainly on indenting, like Bourne shell, a double click on
+the first alpha character of a line, such as an if statement, selects
+the whole statement.
+
+---------------
+
+This whole package is driven by a single function, available in mouse
+and keyboard forms, that first marks a region based on the syntax
+category of the character following point. Successive invocations mark
+larger and larger regions until the whole buffer is marked. See the
+documentation for the function, id-select-syntactical-region, for the
+kinds of syntax categories handled.
+
+Loading this package automatically installs its functionalty on
+double-clicks (or higher) of the left mouse key. (See the documentation
+for the variable, mouse-track-click-hook, for how this is done.) A
+single click of the left button will remove the region and reset point.
+
+The function, id-select-thing, may be bound to a key to provide the same
+syntax-driven region selection functionality. {C-c C-m} is a
+reasonable site-wide choice since this key is seldom used and it
+mnemonically indicates marking something. {C-c s} may be preferred as a
+personal binding.
+
+Use {C-g} to unmark the region when done. Use,
+id-select-thing-with-mouse, if you want to bind this to a mouse key and
+thereby use single clicks instead of double clicks.
+
+Three other commands are also provided:
+ id-select-and-copy-thing - mark and copy the syntactical unit to the
+ kill ring
+ id-select-and-kill-thing - kill the syntactical unit at point
+ id-select-goto-matching-tag - In HTML and SGML modes (actually any
+ listed in the variable, `id-select-markup-modes'), moves point to the
+ start of the tag paired with the closest tag that point is within or
+ which it precedes, so you can quickly jump back and forth between
+ open and close tags.
+"
+:short-doc "Syntactic region selection"
+:group 'editing
+:enable #'(lambda ()
+ (add-hook 'mouse-track-click-hook 'id-select-double-click-hook))
+:disable #'(lambda ()
+ (remove-hook 'mouse-track-click-hook 'id-select-double-click-hook))
+ )
+)
(provide 'id-select)
Index: xemacs-packages/edit-utils/iswitchb.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/iswitchb.el,v
retrieving revision 1.3
diff -u -p -r1.3 iswitchb.el
--- xemacs-packages/edit-utils/iswitchb.el 2001/07/20 14:09:12 1.3
+++ xemacs-packages/edit-utils/iswitchb.el 2005/01/31 20:55:47
＠＠ -1352,6 +1352,166 ＠＠ This is an example function which can be
;;; HOOKS
(add-hook 'minibuffer-setup-hook 'iswitchb-minibuffer-setup)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'iswitchb
+"As you type in a substring, the list of buffers currently matching
+the substring are displayed as you type. The list is ordered so
+that the most recent buffers visited come at the start of the list.
+The buffer at the start of the list will be the one visited when
+you press return. By typing more of the substring, the list is
+narrowed down so that gradually the buffer you want will be at the
+top of the list. Alternatively, you can use C-s an C-r to rotate
+buffer names in the list until the one you want is at the top of
+the list. Completion is also available so that you can see what is
+common to all of the matching buffers as you type.
+
+This code is similar to a couple of other packages. Michael R Cook
+<mcook(a)cognex.com> wrote a similar buffer switching package, but
+does exact matching rather than substring matching on buffer names.
+I also modified a couple of functions from icomplete.el to provide
+the completion feedback in the minibuffer.
+
+; Example
+
+If I have two buffers called \"123456\" and \"123\", with \"123456\" the
+most recent, when I use iswitchb, I first of all get presented with
+the list of all the buffers
+
+ iswitch {123456,123}
+
+ If I then press 2:
+ iswitch 2[3]{123456,123}
+
+ The list in {} are the matching buffers, most recent first (buffers
+ visible in the current frame are put at the end of the list by
+ default). At any time I can select the item at the head of the
+ list by pressing RET. I can also bring the put the first element
+ at the end of the list by pressing C-s, or put the last element at
+ the head of the list by pressing C-r. The item in [] indicates
+ what can be added to my input by pressing TAB. In this case, I
+ will get \"3\" added to my input. So, press TAB:
+ iswitch 23{123456,123}
+
+ At this point, I still have two matching buffers.
+ If I want the first buffer in the list, I simply press RET. If I
+ wanted the second in the list, I could press C-s to move it to the
+ top of the list and then RET to select it.
+
+However, If I type 4, I only have one match left:
+ iswitch 234[123456] [Matched]
+
+Since there is only one matching buffer left, it is given in [] and we
+see the text [Matched] afterwards. I can now press TAB or RET to go
+to that buffer.
+
+ If however, I now type \"a\":
+ iswitch 234a [No match]
+ There are no matching buffers. If I press RET or TAB, I can be
+ prompted to create a new buffer called \"234a\".
+
+ Of course, where this function comes in really useful is when you
+ can specify the buffer using only a few keystrokes. In the above
+ example, the quickest way to get to the \"123456\" buffer would be
+ just to type 4 and then RET (assuming there isn't any newer buffer
+ with 4 in its name).
+
+ To see a full list of all matching buffers in a separate buffer,
+ hit ? or press TAB when there are no further completions to the
+ substring. Repeated TAB presses will scroll you through this
+ separate buffer.
+
+ The buffer at the head of the list can be killed by pressing C-k.
+ If the buffer needs saving, you will be queried before the buffer
+ is killed.
+
+ If you find that the file you are after is not in a buffer, you can
+ press C-x C-f to immediately drop into find-file.
+
+
+ See the doc string of iswitchb for full keybindings and features.
+ (describe-function 'iswitchb)
+
+; Customisation
+
+ See the User Variables section below for easy ways to change the
+ functionality of the program. These are accessible using the
+ custom package.
+ To modify the keybindings, use the hook provided. For example:
+\(add-hook 'iswitchb-define-mode-map-hook
+ 'iswitchb-my-keys)
+
+\(defun iswitchb-my-keys ()
+ \"Add my keybindings for iswitchb.\"
+ (define-key iswitchb-mode-map \" \" 'iswitchb-next-match)
+ )
+
+ Seeing all the matching buffers
+
+ If you have many matching buffers, they may not all fit onto one
+ line of the minibuffer. In this case, you should use rsz-mini
+ (resize-minibuffer-mode). You can also limit iswitchb so that it
+ only shows a certain number of lines -- see the documentation for
+ `iswitchb-minibuffer-setup-hook'.
+
+
+ Changing the list of buffers
+
+ By default, the list of current buffers is most recent first,
+ oldest last, with the exception that the buffers visible in the
+ current frame are put at the end of the list. A hook exists to
+ allow other functions to order the list. For example, if you add:
+
+ (add-hook 'iswitchb-make-buflist-hook 'iswitchb-summaries-to-end)
+
+ then all buffers matching \"Summary\" are moved to the end of the
+ list. (I find this handy for keeping the INBOX Summary and so on
+ out of the way.) It also moves buffers matching \"output\*$\" to the
+ end of the list (these are created by AUC TeX when compiling.)
+ Other functions could be made available which alter the list of
+ matching buffers (either deleting or rearranging elements.)
+
+ Font-Lock
+
+ If you have font-lock loaded, the first matching buffer is
+ highlighted. To switch this off, set (setq iswitchb-use-fonts nil)
+ I don't use font-lock that much, so I've hardcoded the faces. If
+ this is too harsh, let me know. Colouring of the matching buffer
+ name was suggested by Carsten Dominik (dominik(a)strw.leidenuniv.nl)
+
+
+ Replacement for read-buffer
+
+ iswitchb-read-buffer has been written to be a drop in replacement
+ for the normal buffer selection routine `read-buffer'. To use
+ iswitch for all buffer selections in Emacs, add:
+ (setq read-buffer-function 'iswitchb-read-buffer)
+ (This variable should be present in Emacs 20.3+)
+ XEmacs users can get the same behaviour by doing:
+ (defalias 'read-buffer 'iswitchb-read-buffer)
+ since `read-buffer' is defined in lisp.
+
+ Regexp matching
+
+ There is limited provision for regexp matching within iswitchb,
+ enabled through `iswitchb-regexp'. This allows you to type `c$'
+ for example and see all buffer names ending in `c'. This facility
+ is quite limited though in two respects. First, you can't
+ currently type in expressions like `[0-9]' directly -- you have to
+ type them in when iswitchb-regexp is nil and then toggle on the
+ regexp functionality. Likewise, don't enter an expression
+ containing `\' in regexp mode. If you try, iswitchb gets confused,
+ so just hit C-g and try again. Secondly, no completion mechanism
+ is currently offered when regexp searching."
+:short-doc "Dynamic buffer switching"
+:group 'keyboard
+:enable #'(lambda ()
+ (iswitchb-default-keybindings))
+ ;; No :disable
+ )
+)
+
(provide 'iswitchb)
;;; iswitchb.el ends here
Index: xemacs-packages/edit-utils/lazy-lock.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/lazy-lock.el,v
retrieving revision 1.11
diff -u -p -r1.11 lazy-lock.el
--- xemacs-packages/edit-utils/lazy-lock.el 2004/11/08 02:38:42 1.11
+++ xemacs-packages/edit-utils/lazy-lock.el 2005/01/31 20:55:47
＠＠ -1070,6 +1070,76 ＠＠ will take place when text is fontified s
;;;###autoload
(add-minor-mode 'lazy-lock-mode 'lazy-lock-mode-line-string)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'lazy-lock
+
+"Make visiting buffers in `font-lock-mode' faster by making fontification
+be demand-driven and stealthy. Fontification only occurs when, and where,
+necessary. You can now use the so-called \"gaudier\" fontification regexps
+on big files without frustration.
+
+In a buffer (which has `font-lock-mode' enabled) which is at least
+`lazy-lock-minimum-size' characters long, only the visible portion of the
+buffer will be fontified. Motion around the buffer will fontify those
+visible portions that were not previous fontified.
+
+If stealth fontification is enabled, fontification will occur in invisible
+parts of the buffer after `lazy-lock-stealth-time' seconds of idle time.
+Caveats:
+
+Lazy Lock mode does not work efficiently with Outline mode. This is because
+when in Outline mode, although text may be hidden (not visible in the
+window), the text is visible to Emacs Lisp code (not surprisingly) and Lazy
+Lock fontifies it mercilessly. Hopefully this will be fixed one day.
+
+When Lazy Lock mode is enabled, fontification can be lazy in a number of ways:
+
+- Demand-driven buffer fontification if `lazy-lock-minimum-size' is non-nil.
+ This means initial fontification does not occur if the buffer is greater than
+ `lazy-lock-minimum-size' characters in length. Instead, fontification occurs
+ when necessary, such as when scrolling through the buffer would otherwise
+ reveal unfontified areas. This is useful if buffer fontification is too slow
+ for large buffers.
+
+- Deferred on-the-fly fontification if `lazy-lock-defer-on-the-fly' is non-nil.
+ This means on-the-fly fontification does not occur as you type. Instead,
+ fontification is deferred until after `lazy-lock-defer-time' seconds of Emacs
+ idle time, while Emacs remains idle. This is useful if fontification is too
+ slow to keep up with your typing.
+
+- Deferred context fontification if `lazy-lock-defer-contextually' is non-nil.
+ This means fontification updates the buffer corresponding to true syntactic
+ context, after `lazy-lock-defer-time' seconds of Emacs idle time, while Emacs
+ remains idle. Otherwise, fontification occurs on modified lines only, and
+ subsequent lines can remain fontified corresponding to previous syntactic
+ contexts. This is useful where strings or comments span lines.
+
+- Stealthy buffer fontification if `lazy-lock-stealth-time' is non-nil.
+ This means remaining unfontified areas of buffers are fontified if Emacs has
+ been idle for `lazy-lock-stealth-time' seconds, while Emacs remains idle.
+ This is useful if any buffer has any deferred fontification.
+
+Basic Font Lock mode on-the-fly fontification behaviour fontifies modified
+lines only. Thus, if `lazy-lock-defer-contextually' is non-nil, Lazy Lock mode
+on-the-fly fontification may fontify differently, albeit correctly. In any
+event, to refontify some lines you can use \\[font-lock-fontify-block].
+
+Stealth fontification only occurs while the system remains unloaded.
+If the system load rises above `lazy-lock-stealth-load' percent, stealth
+fontification is suspended. Stealth fontification intensity is controlled via
+the variable `lazy-lock-stealth-nice' and `lazy-lock-stealth-lines', and
+verbosity is controlled via the variable `lazy-lock-stealth-verbose'."
+:short-doc "Lazy demand-driven fontification for fast Font Lock mode"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock))
+:disable #'(lambda ()
+ (remove-hook 'font-lock-mode-hook 'turn-on-lazy-lock))
+ )
+)
+
;; Provide ourselves:
(provide 'lazy-lock)
Index: xemacs-packages/edit-utils/lazy-shot.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/lazy-shot.el,v
retrieving revision 1.6
diff -u -p -r1.6 lazy-shot.el
--- xemacs-packages/edit-utils/lazy-shot.el 2002/11/28 18:55:08 1.6
+++ xemacs-packages/edit-utils/lazy-shot.el 2005/01/31 20:55:47
＠＠ -321,6 +321,30 ＠＠ stealth locking functions."
(if font-lock-mode
(add-hook 'after-change-functions 'font-lock-after-change-function
nil t)))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'lazy-shot
+"This is an experimental demand based font-lock implemenation. It
+is almost equal in functionality and interface to lazy-lock 2.09
+Does somebody really need defer-locking?
+
+It is exprimental in the sense that it relies on C support from
+the redisplay engine, that is experimental. The code in this file
+is more or less finished. The C code support experimental because
+the current design is rumoured to be ugly. Secondly because
+XEmacs does actually display the \"un-font-locked\" parts of the
+buffer first, the user notices flashing as the buffer is repainted
+with color/fonts."
+:short-doc "Lazy font locking for XEmacs"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'font-lock-mode-hook 'turn-on-lazy-shot))
+:disable #'(lambda ()
+ (remove-hook 'font-lock-mode-hook 'turn-on-lazy-shot))
+ )
+)
(provide 'lazy-shot)
Index: xemacs-packages/edit-utils/live-icon.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/live-icon.el,v
retrieving revision 1.2
diff -u -p -r1.2 live-icon.el
--- xemacs-packages/edit-utils/live-icon.el 1999/11/27 20:49:59 1.2
+++ xemacs-packages/edit-utils/live-icon.el 2005/01/31 20:55:47
＠＠ -139,8 +139,23 ＠＠
;; fr))
;; (frame-list)))
-(add-hook 'unmap-frame-hook 'live-icon-one-frame)
;;(start-itimer "live-icon" 'live-icon-all-frames 120 120)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'live-icon
+"Make frame icons represent the current frame contents.
+Generates little pixmaps representing the contents of your frames."
+:short-doc "make frame icons represent the current frame contents"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'unmap-frame-hook 'live-icon-one-frame))
+:disable #'(lambda ()
+ (remove-hook 'unmap-frame-hook 'live-icon-one-frame))
+ )
+)
+
(provide 'live-icon)
;;; live-icon.el ends here
Index: xemacs-packages/edit-utils/page-ext.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/page-ext.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 page-ext.el
--- xemacs-packages/edit-utils/page-ext.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/page-ext.el 2005/01/31 20:55:48
＠＠ -785,6 +785,225 ＠＠ to the same line in the pages buffer."
(make-local-variable 'pages-pos-list)
(make-local-variable 'pages-directory-buffer-narrowing-p))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'page-ext
+"You may use these commands to handle an address list or other
+small data base.
+
+ Summary
+
+The current page commands are:
+
+ forward-page C-x ]
+ backward-page C-x [
+ narrow-to-page C-x p
+ count-lines-page C-x l
+ mark-page C-x C-p (change this to C-x C-p C-m)
+ sort-pages not bound
+ what-page not bound
+
+The new page handling commands all use `C-x C-p' as a prefix. This
+means that the key binding for `mark-page' must be changed.
+Otherwise, no other changes are made to the current commands or
+their bindings.
+
+New page handling commands:
+
+ next-page C-x C-p C-n
+ previous-page C-x C-p C-p
+ search-pages C-x C-p C-s
+ add-new-page C-x C-p C-a
+ sort-pages-buffer C-x C-p s
+ set-page-delimiter C-x C-p C-l
+ pages-directory C-x C-p C-d
+ pages-directory-for-addresses C-x C-p d
+ pages-directory-goto C-c C-c
+
+
+ Using the page commands
+
+The page commands are helpful in several different contexts. For
+example, programmers often divide source files into sections using the
+`page-delimiter'; you can use the `pages-directory' command to list
+the sections.
+
+You may change the buffer local value of the `page-delimiter' with
+the `set-page-delimiter' command. This command is bound to `C-x C-p
+C-l' The command prompts you for a new value for the page-delimiter.
+Called with a prefix-arg, the command resets the value of the
+page-delimiter to its original value.
+
+You may set several user options:
+
+ The `pages-directory-buffer-narrowing-p' variable causes the
+ `pages-directory-goto' command to narrow to the destination page.
+
+ The `pages-directory-for-adding-page-narrowing-p' variable, causes the
+ `add-new-page' command to narrow to the new entry.
+
+ The `pages-directory-for-adding-new-page-before-current-page-p' variable
+ causes the `add-new-page' command to insert a new page before current
+ page.
+
+These variables are true by default.
+
+Additional, addresses-related user options are described in the next page
+of this file.
+
+
+ Handling an address list or small data base
+
+You may use the page commands to handle an address list or other
+small data base. Put each address or entry on its own page. The
+first line of text in each page is a `header line' and is listed by
+the `pages-directory' or `pages-directory-for-addresses' command.
+
+Specifically:
+
+ 1. Begin each entry with a `page-delimiter' (which is, by default,
+ `^L' at the beginning of the line).
+
+ 2. The first line of text in each entry is the `heading line'; it
+ will appear in the pages-directory-buffer which is constructed
+ using the `C-x C-p C-d' (pages-directory) command or the `C-x
+ C-p d' (pages-directory-for-addresses) command.
+
+ The heading line may be on the same line as the page-delimiter
+ or it may follow after. It is the first non-blank line on the
+ page. Conventionally, the heading line is placed on the line
+ immediately following the line containing page-delimiter.
+
+ 3. Follow the heading line with the body of the entry. The body
+ extends up to the next `page-delimiter'. The body may be of any
+ length. It is conventional to place a blank line after the last
+ line of the body.
+
+For example, a file might look like this:
+
+ FSF
+ Free Software Foundation
+ 59 Temple Place - Suite 330
+ Boston, MA 02111-1307 USA.
+ (617) 542-5942
+ gnu(a)gnu.org
+
+
+ House Subcommittee on Intellectual Property,
+ U.S. House of Representatives,
+ Washington, DC 20515
+
+ Congressional committee concerned with permitting or preventing
+ monopolistic restrictions on the use of software technology.
+
+
+ George Lakoff
+ ``Women, Fire, and Dangerous Things:
+ What Categories Reveal about the Mind''
+ 1987, Univ. of Chicago Press
+
+ About philosophy, Whorfian effects, and linguistics.
+
+
+ OBI (On line text collection.)
+ Open Book Initiative
+ c/o Software Tool & Die
+ 1330 Beacon St, Brookline, MA 02146 USA
+ (617) 739-0202
+ obi(a)world.std.com
+
+In this example, the heading lines are:
+
+ FSF
+ House Subcommittee on Intellectual Property
+ George Lakoff
+ OBI (On line text collection.)
+
+The `C-x C-p s' (sort-pages-buffer) command sorts the entries in the
+buffer alphabetically.
+
+You may use any of the page commands, including the `next-page',
+`previous-page', `add-new-page', `mark-page', and `search-pages'
+commands.
+
+You may use either the `C-x C-p d' (pages-directory-for-addresses)
+or the `C-x C-p C-d' (pages-directory) command to construct and
+display a directory of all the heading lines.
+
+In the directory, you may position the cursor over a heading line
+and type `C-c C-c' (pages-directory-goto) to go to the entry to
+which it refers in the pages buffer.
+
+You can type `C-c C-p C-a' (add-new-page) to add a new entry in the
+pages buffer or address file. This is the same command you use to
+add a new entry when you are in the pages buffer or address file.
+
+If you wish, you may create several different directories,
+one for each different buffer.
+
+`pages-directory-for-addresses' in detail
+
+The `pages-directory-for-addresses' assumes a default addresses
+file. You do not need to specify the addresses file but merely type
+`C-x C-p d' from any buffer. The command finds the file, constructs
+a directory for it, and switches you to the directory. If you call
+the command with a prefix arg, `C-u C-x C-p d', it prompts you for a
+file name.
+
+You may customize the addresses commands:
+
+ The `pages-addresses-file-name' variable determines the name of
+ the addresses file; by default it is \"~/addresses\".
+
+ The `pages-directory-for-addresses-goto-narrowing-p' variable
+ determines whether `pages-directory-goto' narrows the addresses
+ buffer to the entry, which it does by default.
+
+ The `pages-directory-for-addresses-buffer-keep-windows-p' variable
+ determines whether `pages-directory-for-addresses' deletes other
+ windows to show as many lines as possible on the screen or works
+ in the usual Emacs manner and keeps other windows. Default is to
+ keep other windows.
+
+ The `pages-directory-for-adding-addresses-narrowing-p' variable
+ determines whether `pages-directory-for-addresses' narrows the
+ addresses buffer to a new entry when you are adding that entry.
+ Default is to narrow to new entry, which means you see a blank
+ screen before you write the new entry.
+
+`pages-directory' in detail
+
+Call the `pages-directory' command from the buffer for which you
+want a directory created; it creates a directory for the buffer and
+pops you to the directory.
+
+The `pages-directory' command has several options:
+
+ Called with a prefix arg, `C-u C-x C-p C-d', the `pages-directory'
+ prompts you for a regular expression and only lists only those
+ header lines that are part of pages that contain matches to the
+ regexp. In the example above, `C-u C-x C-p C-d 617 RET' would
+ match the telephone area code of the first and fourth entries, so
+ only the header lines of those two entries would appear in the
+ pages-directory-buffer.
+
+ Called with a numeric argument, the `pages-directory' command
+ lists the number of lines in each page. This is helpful when you
+ are printing hardcopy.
+
+ Called with a negative numeric argument, the `pages-directory'
+ command lists the lengths of pages whose contents match a regexp.
+"
+:short-doc "Extended page handling commands"
+:require 'page-ext
+:custom-group 'pages
+:group 'editing
+:enable #'ignore
+ ;; No :disable
+ )
+)
+
;;; Place `provide' at end of file.
(provide 'page-ext)
Index: xemacs-packages/edit-utils/paren.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/paren.el,v
retrieving revision 1.3
diff -u -p -r1.3 paren.el
--- xemacs-packages/edit-utils/paren.el 1998/10/10 13:59:43 1.3
+++ xemacs-packages/edit-utils/paren.el 2005/01/31 20:55:48
＠＠ -391,6 +391,50 ＠＠ See also `paren-mode' and `paren-highlig
(paren-set-mode (if (and (numberp arg) (> arg 0))
'blink-paren -1) t))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'paren
+"Purpose of this package:
+
+ This package highlights matching parens (or whole sexps) for easier
+ editing of source code, particularly lisp source code.
+
+The `paren-highlight' hook function runs after each command and
+checks to see if the cursor is at a parenthesis. If so, then it
+highlights, in one of several ways, the matching parenthesis.
+
+Priority is given to matching parentheses right before the cursor because
+that's what makes sense when you're typing a lot of closed parentheses.
+
+This is especially intuitive if you frequently use forward-sexp (M-C-f)
+and backward-sexp (M-C-b) to maneuver around in source code.
+
+Different faces are used for matching and mismatching parens so that it
+is easier to see mistakes as you type them. Audible feedback is optional.
+
+If a (mis)matching paren is offscreen, then a message is sent to the modeline.
+
+If paren-mode is `sexp', entire S-expressions are highlighted instead of
+just matching parens.
+"
+:short-doc "Highlight (un)matching parens and whole expressions"
+:custom-group 'paren-matching
+:group 'display
+:enable #'(lambda ()
+ (paren-set-mode (if (and (boundp 'highlight-paren-expression)
+ ;; bletcherous blink-paren no-naming-convention
+ highlight-paren-expression)
+ 'sexp
+ (if (device-on-window-system-p)
+ 'blink-paren
+ 'paren))
+ t))
+:disable #'(lambda ()
+ (paren-set-mode -1 t))
+ )
+)
+
(provide 'blink-paren)
(provide 'paren)
Index: xemacs-packages/edit-utils/permanent-buffers.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/permanent-buffers.el,v
retrieving revision 1.3
diff -u -p -r1.3 permanent-buffers.el
--- xemacs-packages/edit-utils/permanent-buffers.el 2000/10/06 09:08:01 1.3
+++ xemacs-packages/edit-utils/permanent-buffers.el 2005/01/31 20:55:48
＠＠ -223,6 +223,30 ＠＠ regenerated fresh and empty. See also th
(interactive)
(message "permanent-buffers version %s" permanent-buffers-version))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'permanent-buffers
+"A permanent buffer is a buffer that you don't want to kill, mainly used for
+testing or temporary stuff. The *scratch* buffer is the most famous example
+of what could be a permanent buffer. This package allows you to define
+several permanent buffers (the scratch buffer can be one of them) that
+will never disapear. If you kill them or save their contents, they will be
+regenerated. You can also specify a set of lisp forms to eval in the buffer
+when it is (re)generated.
+
+The package is implemented in a minor-mode fashion. You can customize the
+default value of `permanent-buffers-mode' or use
+`turn-on-permanent-buffers' at startup. Within an XEmacs session, use
+`permanent-buffers-mode' or `tun-o[n|ff]-oermanent-buffers'. You might also
+want to customize `permanent-buffers-alist'."
+:short-doc "Permanent buffers management package"
+:group 'buffers-and-windows
+:enable #'turn-on-permanent-buffers
+:disable #'turn-off-permanent-buffers
+ )
+)
+
(provide 'permanent-buffers)
;;; permanent-buffers.el ends here
Index: xemacs-packages/edit-utils/popper.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/popper.el,v
retrieving revision 1.3
diff -u -p -r1.3 popper.el
--- xemacs-packages/edit-utils/popper.el 1998/10/02 06:10:33 1.3
+++ xemacs-packages/edit-utils/popper.el 2005/01/31 20:55:49
＠＠ -1807,6 +1807,213 ＠＠ window is deleted, the display jump is a
(popper-install))
+;; XEmacs:
+
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'popper
+"\
+1. VERSION:
+
+This version of popper is based on version 2.40, which as far as I can
+tell is the last version distributed by Chris McConnell, the original
+author of popper. I have been unsuccessful at contacting him and so
+have decided to take over maintenance of the package for XEmacs. New
+versions distributed by me will be designated \"2.40 XEmacs X.Y\". This
+designation is not meant to imply that this is an XEmacs-specific
+version, only that it is the version distributed with XEmacs. This
+version incorporates significant bug fixes and changes with respect to
+the original. Overall it should work much better. Please let me know
+if you have any problems or suggestions.
+
+2. DESCRIPTION:
+
+This module provides a single shrink-wrapped window for displaying
+temporary text called the popper window. At any time there is at
+most one popper window on a given emacs frame. If there is an entry
+for the buffer being displayed on popper-min-heights, the size of
+the window will be from that entry. If the buffer is empty, the
+size of the window will be popper-empty-min. Otherwise its size
+will be the minimum of the number of lines of text being displayed
+and half the number of lines in the currently selected window when
+the popper window was created. It will work with any function that
+uses temporary windows or that has been wrapped with popper-wrap.
+The window can be scrolled or buried from any other window.
+
+When a buffer is displayed using the function
+with-output-to-temp-buffer, the text will be displayed in the
+popper window if the name of the buffer is in popper-pop-buffers
+or popper-pop-buffers is set to `t' and the name is not in
+popper-no-pop-buffers. If you have a buffer with a process, you
+can cause it to automatically scroll by setting
+popper-scroll-buffers to `t' or to a list of buffer names to
+scroll. Many kinds of completion and help information are
+displayed this way. In general any buffer with *'s around its
+name will be a temporary buffer. Some commands like shell-command
+do not use with-output-to-temp-buffer even though you might like
+to have their output be temporary. For commands like this, you
+can define a wrapper using the function popper-wrap.
+
+If popper-use-message-buffer is non-nil then popper output that is
+one line or less will be displayed in the minibuffer.
+
+The default binding for C-x o is changed so that when a buffer is
+displayed in a popper window, it will be skipped if it is in
+popper-buffers-to-skip or popper-buffers-to-skip is `t' and it is
+not in popper-buffers-no-skip.
+
+3. USAGE:
+
+Load this file, preferably after byte-compiling it. By default
+popper does not install itself unless the variable
+`popper-install-when-load' has been set non-nil before it is loaded.
+To manually install popper, type the command M-x popper-install. If
+you later decide popper is not your cup-o-tea, you may un-install it
+using the command M-x popper-unstall.
+
+Once installed, all temporary windows will be handled by popper by
+default. If you do not define custom key bindings using the
+popper-load-hook, the bindings for manipulating the popper temporary
+window will be:
+
+ * C-z C-z, C-z z, C-z 1 : popper-bury-output
+ Alternately hide or show the temporary pop-up window.
+
+ * C-z C-v, C-z v : popper-scroll-output
+ Scroll the popper output window.
+
+ * C-z M-v, C-z V : popper-scroll-output-back
+ Scroll the popper output window backwards.
+
+ * C-z < : popper-beginning-of-buffer
+ Scroll the popper output window to the beginning of the buffer.
+
+ * C-z > : popper-end-of-buffer
+ Scroll the popper output window to the end of the buffer.
+
+ * C-z C-j, C-z j, C-z C-o, C-z o : popper-jump-to-popper
+ Select the popper window, or jump back to the previous window
+ if the popper window is already selected. With a C-u argument,
+ show the popper window first if necessary.
+
+ * C-z C-s : popper-isearch-forward
+ Do incremental search forward in the popper buffer.
+
+ * C-z C-r : popper-isearch-backward
+ Do incremental search backward in the popper buffer.
+
+ * C-z C-M-s : popper-isearch-forward-regexp
+ Do regexp incremental search forward in the popper buffer.
+
+ * C-z C-M-r : popper-isearch-backward-regexp
+ Do regexp incremental search backward in the popper buffer.
+
+ * C-z g : popper-grow-output
+ Grow the popper output window.
+
+ * C-z G, C-z M-g : popper-shrink-output
+ Shrink the popper output window.
+
+ * C-z C-b, C-z b : popper-switch-buffer
+ Prompt for a different popper temporary buffer to show.
+
+ * C-z C-k, C-z k : popper-kill
+ Kill or bury the current popper buffer and drop it off of the
+ stack of popper buffers for this frame. If the stack of popper
+ buffers (for the selected frame) is not empty, show the new
+ top-most buffer. The buffer is killed if it has been saved with
+ `popper-save'; otherwise it is just buried.
+
+ * C-z C-x, C-z x : popper-cycle
+ Cycle through all popper buffers (for the selected frame) by
+ dropping the current popper buffer to bottom of the stack.
+
+ * C-z s : popper-save
+ Save the current popper buffer by renaming it so that it won't be
+ overwritten.
+
+ * C-x o : popper-other-window
+ Like other-window, but (by default) skips the popper window.
+ Use a C-u prefix to select the popper window. See the variables
+ `popper-buffers-to-skip' and `popper-buffers-no-skip'.
+
+ * C-x 0 : popper-delete-window
+ Like delete-window, but hides and re-shows the popper window
+ around the call to delete-window. Also, the variable
+ `popper-delete-window-can-delete-frame' can be set to nil to
+ prevent deletion of the frame if the user attempts to delete the
+ last window.
+
+Note that \"C-z\" is the popper-prefix, and that many bindings in the
+popper map are chosen by analogy to a similar command in the \"C-x\"
+map. If you have suggestions for more intuitive or easily typed
+bindings, or additional user commands that would be nice, please let
+me know.
+
+4. USER CUSTOMIZATION:
+
+See the section `Popper user variables' below for configurable
+variables. Here is a sample load hook for your .emacs:
+
+\(defun gk:popper-load-hook ()
+ (setq popper-install-when-load t) ; Hooray!
+ (setq popper-mode-line-text \" Popper\") ; I know the key bindings
+ (setq popper-no-pop-buffers '(\"^Man: \")) ; don't pop manual buffers
+ (setq popper-max-heights '((\".*\" . (40)))) ; use at most 40%
+ (setq popper-delete-window-can-delete-frame nil) ; extremely losing...
+ )
+\(add-hook 'popper-load-hook 'gk:popper-load-hook)
+\(require 'popper)
+
+Once popper is installed, you may wrap a command that does not use
+`with-output-to-temp-buffer' so that it will work with popper as
+follows:
+
+\(popper-wrap command \"*Command Output*\")
+
+This may not yet work in all cases. It is known not to work for
+M-x compile at this time (See the TODO list below).
+
+When loaded, popper checks the values of certain user variable for
+possible problems, unless `popper-inhibit-warnings' is non-nil. In
+addition, if `popper-fix-incompatible-settings' has been set non-nil,
+popper will set these variables to values known to work best.
+See also the variable `popper-suggested-settings'.
+
+5. WARNINGS:
+
+This package redefines the value of `temp-buffer-show-function'.
+It also advises the functions `split-window' and `pop-to-buffer'
+so that the popper window is buried before calling the old
+definition. The macro `popper-wrap' uses defadvice.
+"
+:short-doc "Shrink-wrapped temporary windows for Emacs"
+:group 'buffers-and-windows
+;;; (defun gk:popper-load-hook ()
+;;; (setq popper-install-when-load t) ; Hooray!
+;;; (setq popper-mode-line-text " Popper") ; I know the key bindings
+;;; (setq popper-no-pop-buffers '("^Man: ")) ; don't pop manual buffers
+;;; (setq popper-max-heights '((".*" . (40)))) ; use at most 40%
+;;; (setq popper-delete-window-can-delete-frame nil) ; extremely losing...
+;;; )
+
+:enable #'(lambda ()
+ (unless (fboundp 'behavior-popper-load-hook)
+ (defun behavior-popper-load-hook ()
+ ;; I know the key bindings
+ (setq popper-mode-line-text " Popper")
+ ;; don't pop manual buffers
+ (setq popper-no-pop-buffers '("^Man: "))
+ ;; use at most 40%
+ (setq popper-max-heights '((".*" . (40))))
+ ;; extremely losing...
+ (setq popper-delete-window-can-delete-frame nil)))
+ (add-hook 'popper-load-hook 'behavior-popper-load-hook)
+ (popper-install))
+:disable #'(lambda ()
+ (popper-unstall))
+ )
+)
;;;
;;; Finally, provide the feature
;;;
Index: xemacs-packages/edit-utils/power-macros.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/power-macros.el,v
retrieving revision 1.1
diff -u -p -r1.1 power-macros.el
--- xemacs-packages/edit-utils/power-macros.el 2000/10/18 17:54:30 1.1
+++ xemacs-packages/edit-utils/power-macros.el 2005/01/31 20:55:49
＠＠ -1926,6 +1926,37 ＠＠ The buffer is created if it doesn't exis
;;}}}
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'power-macros
+"Keyboard Macros are a very powerful tool, if you know how to use them
+the right way! Without this extension it is, however, a bit difficult in
+Emacs to define and maintain several macros at a time. This problem is
+solved with this package.
+
+When you have loaded this package Emacs will, upon completion of
+macro definition, ask you which key you want to assign this macro
+to and ask for a description of the macro.
+If something is already bound to this key, Emacs will ask you
+whether you want to override this binding. Furthermore, this
+package also takes care of saving the macro to your .emacs file
+for later Emacs sessions.
+
+The description for all the defined macros may be obtained with the
+function `pm-manage-macros'. Using this function you can also
+manage you power-macros. You execute this function by pressing `M-x' and
+typing `pm-manage-macros'."
+:short-doc "Easy multiple macro maintenance"
+:group 'editing
+:require 'power-macros
+:enable #'ignore
+ ;; no :disable
+ )
+)
+
+
(provide 'power-macros)
(message "Loading power-macros...done")
Index: xemacs-packages/edit-utils/recent-files.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/recent-files.el,v
retrieving revision 1.9
diff -u -p -r1.9 recent-files.el
--- xemacs-packages/edit-utils/recent-files.el 2004/11/08 02:38:42 1.9
+++ xemacs-packages/edit-utils/recent-files.el 2005/01/31 20:55:49
＠＠ -766,4 +766,162 ＠＠ with a prefix argument, you will be prom
(read-coding-system "Coding system: ")
nil)))
(find-file filename codesys))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'recent-files
+"Recent-files adds the menu \"Recent Files\" (or whatever name you
+choose, see \"Customization:\" below) to Emacs's menubar. Its
+entries are the files (and directories) that have recently been
+opened by Emacs. You can open one of these files again by
+selecting its entry in the \"Recent Files\" menu. The list of file
+entries in this menu is preserved from one Emacs session to
+another. You can prevent Emacs from saving this list by selecting
+\"Don't save recent-files list on exit\" from the menu. If you have
+disabled saving, you can re-enable it by selecting \"Save
+recent-files list on exit\".
+
+The menu has permanent and non-permanent entries. Permanent
+entries are marked with an asterisk in front of the filename. The
+non-permanent entries are hidden in a submenu.
+
+Each time you open a file in Emacs, it is added as a non-permanent
+entry to the menu. The value of `recent-files-number-of-entries'
+determines how many non-permanent entries are held in the
+menu. When the number of non-permanent entries reaches this value,
+the least recently added non-permanent entry is removed from the
+menu when another non-permanent entry is added. It is not removed
+from the list, though; it may reappear when entries are deleted
+from the list. The number of entries saved to disk is the value of
+the variable `recent-files-number-of-saved-entries'.
+
+Permanent entries are not removed from the menu. You can make a
+file entry permanent by selecting \"Make <buffer> permanent\" (where
+<buffer> is the name of the current buffer) when the current
+buffer holds this file. \"Make <buffer> non-permanent\" makes the
+file entry of the current buffer non-permanent.
+
+The command \"Kill buffer <buffer> and delete entry\" is handy when
+you have accidently opened a file but want to keep neither the
+buffer nor the entry.
+
+You can erase the list of non-permanent entries by selecting
+\"Erase non-permanent entries\" from the menu.
+
+Customization:
+
+There are lots of variables to control the behaviour of
+recent-files. You do not have to change any of them if you like it
+as it comes out of the box. However, you may want to look at these
+options to make it behave different.
+
+`recent-files-number-of-entries'
+ Controls how many non-permanent entries are shown in the
+ recent-files list. The default is 15.
+
+`recent-files-number-of-saved-entries'
+ Controls how many non-permanent entries are saved to disk when
+ Emacs exits or recent-files-save-the-list is called. The
+ default is 50.
+
+`recent-files-save-file'
+ The name of the file where the recent-files list is saved
+ between Emacs session. You probably don't need to change this.
+ The default is \".recent-files.el\" in your home directory.
+
+`recent-files-dont-include'
+ A list of regular expressions for files that should not be
+ included into the recent-files list. This list is empty by
+ default. For instance, a list to exclude all .newsrc
+ files, all auto-save-files, and all files in the /tmp
+ directory (but not the /tmp directory itself) would look
+ like this:
+ (setq recent-files-dont-include
+ '(\"/\\.newsrc\" \"~$\" \"^/tmp/.\"))
+ The default is empty.
+
+`recent-files-use-full-names'
+ If the value of this variable is non-nil, the full pathnames of
+ the files are shown in the recent-files menu. Otherwise only
+ the filename part (or the last name component if it is a
+ directory) is shown in the menu. The default it t, i.e. show
+ full names.
+
+`recent-files-filename-replacements'
+ This is a list of pairs of regular expressions and replacement
+ strings. If a filename matches one of the regular expressions,
+ the matching part is replaced by the replacement string for
+ display in the recent-files menu.
+ Example: My home directory is \"/users/mmc/nickel/\". I want to
+ replace it with \"~/\". I also want to replace the directory
+ \"/imports/teleservices/mmc/avc2/\", where I work a lot, with
+ \".../avc2/\". The list then looks like
+ (setq recent-files-filename-replacements
+ '((\"/users/mmc/nickel/\" . \"~/\")
+ (\"/imports/teleservices/mmc/avc2/\" . \".../avc2/\")))
+ Only the first match is replaced. So, if you have several
+ entries in this list that may match a filename simultaneously,
+ put the one you want to match (usually the most special) in
+ front of the others. The default is to replace the home
+ directory with \"~\".
+
+`recent-files-sort-function'
+ Contains a function symbol to sort the display of filenames in
+ the recent-files menu. Supplied are two functions,
+ 'recent-files-dont-sort and 'recent-files-sort-alphabetically.
+ The first, which is the default, preserves the order of \"most
+ recent on top\".
+
+`recent-files-permanent-submenu'
+ If this variable is non-nil, the permanent entries are put into
+ a separate submenu of the recent-files menu. The default is
+ nil.
+
+`recent-files-non-permanent-submenu'
+ If this variable is non-nil, the non-permanent entries are put
+ into a separate submenu of the recent-files menu. The default
+ is nil. (You can set both `recent-files-permanent-submenu' and
+ `recent-files-non-permanent-submenu' to t to have both lists in
+ separate submenus.)
+
+`recent-files-commands-submenu'
+ If this variable is non-nil, the commands if recent-files are
+ placed in a submenu of the recent-files menu. The default is
+ nil.
+
+`recent-files-commands-submenu-title'
+ If the commands are placed in a submenu, this string is used as
+ the title of the submenu. The default is \"Commands...\".
+
+`recent-files-actions-on-top'
+ If this variable is non-nil, the \"action\" menu entries (\"Make
+ <buffer> permanent\" etc.) are put on top of the menu. Otherwise
+ they appear below the file entries or submenus. The default is
+ nil.
+
+`recent-files-permanent-first'
+ If this variable is t, the permanent entries are put first in
+ the recent-files menu, i.e. above the non-permanent entries. If
+ the value is nil, non-permanent entries appear first. If the
+ value is neither t nor nil, the entries are sorted according to
+ recent-files-sort-function. The default is 'sort.
+
+`recent-files-find-file-command'
+ This variable contains to commandto execute when a file entry
+ is selected from the menu. Usually this will be `find-file',
+ which is the default.
+
+KNOWN BUG:
+ - recent-files overwrites the recent-files-save-file
+ unconditionally when Emacs exits. If you have two Emacs
+ processes running, the one exiting later will overwrite the
+ file without merging in the new entries from the other Emacs
+ process. This can be avoided by disabling the save on exit from
+ the menu."
+:short-doc "`Recent Files' menu"
+:group 'menus
+:enable 'recent-files-initialize)
+)
+
;;; EOF
Index: xemacs-packages/edit-utils/redo.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/redo.el,v
retrieving revision 1.2
diff -u -p -r1.2 redo.el
--- xemacs-packages/edit-utils/redo.el 2000/11/16 14:11:57 1.2
+++ xemacs-packages/edit-utils/redo.el 2005/01/31 20:55:50
＠＠ -200,4 +200,34 ＠＠ A numeric argument serves as a repeat co
(message "Undo!"))
(setq last-buffer-undo-list buffer-undo-list))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'redo
+"XEmacs' normal undo system allows you to undo an arbitrary
+number of buffer changes. These undos are recorded as ordinary
+buffer changes themselves. So when you break the chain of
+undos by issuing some other command, you can then undo all
+the undos. The chain of recorded buffer modifications
+therefore grows without bound, truncated only at garbage
+collection time.
+
+The redo/undo system is different in two ways:
+ 1. The undo/redo command chain is only broken by a buffer
+ modification. You can move around the buffer or switch
+ buffers and still come back and do more undos or redos.
+ 2. The `redo' command rescinds the most recent undo without
+ recording the change as a _new_ buffer change. It
+ completely reverses the effect of the undo, which
+ includes making the chain of buffer modification records
+ shorter by one, to counteract the effect of the undo
+ command making the record list longer by one."
+:short-doc "Standard undo/redo commands"
+:group 'editing
+:require 'redo
+:enable #'identity
+ ;; no :disable
+)
+)
+
;;; redo.el ends here
Index: xemacs-packages/edit-utils/reportmail.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/reportmail.el,v
retrieving revision 1.3
diff -u -p -r1.3 reportmail.el
--- xemacs-packages/edit-utils/reportmail.el 1999/12/01 08:30:51 1.3
+++ xemacs-packages/edit-utils/reportmail.el 2005/01/31 20:55:50
＠＠ -994,4 +994,97 ＠＠ non-nil, always match using regexps."
(progn (message "Reportmail: %s" mesg)
(sit-for display-time-debugging-delay)))))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'reportmail
+"When new mail arrives, a brief blurb about it will be displayed in the
+mode line, and a more verbose message will be printed in the echo area.
+But unlike most echo-area messages, this message will not go away at
+the next keystroke - it doesn't go away until the next extended-command
+is used. This is cool because that means you won't miss seeing the
+subject of the newly-arrived mail because you happened to be typing when
+it arrived.
+
+But if you set the variable `display-time-flush-echo-area' to t, then this
+message will be cleared every `display-time-interval' seconds. This means
+the message will be around for at most 30 seconds or so, which you may
+prefer.
+
+Site Configuration
+------------------
+
+The variables display-time-incoming-mail-file and
+display-time-message-separator identify the location and format of
+your waiting messages. If you are in the CMU SCS environment, or
+are on a generic BSD unix system, this code should work right away.
+Otherwise, you might need to modify the values of these to make things
+work.
+
+Junk Mail
+---------
+
+The reportmail package has a notion of \"junk mail,\" which can be used to
+reduce the frequency of irritating interruptions by reporting only the
+arrival of messages that seem to be interesting. If you're on a lot
+of high-volume mailing lists, this can be quite convenient. To use
+this facility, add something like the following to your .emacs file:
+
+ ;; The value of this variable is a list of lists, where the first
+ ;; element in each list is the name of a header field and the
+ ;; remaining elements are various elements of the value of this
+ ;; header field that signal the junkiness of a message.
+ (setq display-time-junk-mail-checklist
+ '((\"From\" \"bcp\" \"Benjamin Pierce\" \"Benjamin.Pierce\"
+ \"Mail Delivery Subsystem\" \"network\" \"daemon＠bartok\")
+ (\"To\" \"sml-request\" \"sml-redistribution-request\"
+ \"scheme\" \"TeXhax-Distribution-list\")
+ (\"Resent-From\" \"Benjamin.Pierce\")
+ (\"Sender\" \"WRITERS\" \"Haskell\" \"Electronic Music Digest\" \"NEW-LIST\")))
+
+By default, the entries in this list are matched exactly as
+substrings of the given header fields. If an entry begins with
+the character ^ it will be matched as a regular expression. If the
+variable display-time-match-using-regexps is set, then all entries
+will be matched as regular expressions.
+
+Note that elements of display-time-my-addresses are NOT automatically
+included in display-time-junk-mail-checklist. If you want mail from
+yourself to be considered junkmail, you must add your addresses to
+display-time-junk-mail-checklist too.
+
+
+Xbiff Interface
+---------------
+
+If you normally keep your emacs window iconified, reportmail can
+maintain an xbiff or xbiff++ display as well. The xbiff window will only
+be highlighted when non-junk mail is waiting to be read. For example:
+
+ (if window-system-version
+ (setq display-time-use-xbiff t))
+ (setq display-time-xbiff-arg-list '(\"-update\" \"30\" \"-geometry\" \"+0+0\"))
+ (setq display-time-xbiff-program \"xbiff++\")
+"
+:short-doc "Display time, load, new mail in mode line"
+:group 'display
+:require 'reportmail
+:enable #'(lambda ()
+ (setq display-time-my-addresses
+ (nconc
+ (and user-mail-address user-mail-address)
+ (and user-mail-address (string-match "^\\(.*\\)＠"
+ user-mail-address)
+ (match-string 1))
+ (list (user-full-name) (user-login-name))))
+
+ ;; By default, mail arrival is reported with a message but no
+ ;; beep
+ (setq display-time-mail-ring-bell t)
+
+ (display-time))
+ ;; no :disable
+ )
+)
+
(provide 'reportmail)
Index: xemacs-packages/edit-utils/resume.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/resume.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 resume.el
--- xemacs-packages/edit-utils/resume.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/resume.el 2005/01/31 20:55:50
＠＠ -126,6 +126,32 ＠＠
(write-region (point-min) (point-max) file nil 'quiet))
(set-buffer-modified-p nil)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'resume
+"The purpose of this library is to handle command line arguments
+when you resume an existing Emacs job.
+
+You can't get the benefit of this library by using the `xemacs' command,
+since that always starts a new Emacs job. Instead you must use a
+command called `edit' which knows how to resume an existing Emacs job
+if you have one, or start a new Emacs job if you don't have one.
+
+To define the `edit' command, run the script etc/emacs.csh (if you use CSH),
+or etc/emacs.bash if you use BASH. You would normally do this in your
+login script."
+:short-doc "Process command line args from within a suspended XEmacs job"
+:group 'processes
+:enable #'(lambda ()
+ (add-hook 'suspend-hook 'resume-suspend-hook)
+ (add-hook 'suspend-resume-hook 'resume-process-args))
+:disable #'(lambda ()
+ (remove-hook 'suspend-hook 'resume-suspend-hook)
+ (remove-hook 'suspend-resume-hook 'resume-process-args))
+ )
+)
+
(provide 'resume)
;;; resume.el ends here
Index: xemacs-packages/edit-utils/rsz-minibuf.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/rsz-minibuf.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 rsz-minibuf.el
--- xemacs-packages/edit-utils/rsz-minibuf.el 1998/01/14 06:36:14 1.1.1.1
+++ xemacs-packages/edit-utils/rsz-minibuf.el 2005/01/31 20:55:50
＠＠ -225,6 +225,55 ＠＠ respectively."
(set-frame-size (selected-frame) (frame-width)
(plist-get minibuffer-frame-plist 'height)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'resize-minibuffer
+"This package allows the entire contents (or as much as possible) of the
+minibuffer to be visible at once when typing. As the end of a line is
+reached, the minibuffer will resize itself. When the user is done
+typing, the minibuffer will return to its original size.
+
+In window systems where it is possible to have a frame in which the
+minibuffer is the only window, the frame itself can be resized.
+
+\[[ NOTE: The code to resize frames has not been tested under Lucid Emacs,
+because detached minibuffers are broken. ]] not accurate.
+
+Note that the minibuffer and echo area are not the same! They simply
+happen to occupy roughly the same place on the frame. Messages put in
+the echo area will not cause any resizing by this package.
+
+This package is considered a minor mode but it doesn't put anything in
+minor-mode-alist because this mode is specific to the minibuffer, which
+has no modeline.
+
+When this behavior is enabled, the minibuffer is dynamically resized to
+contain the entire region of text put in it as you type.
+
+The maximum height to which the minibuffer can grow is controlled by the
+variable `resize-minibuffer-window-max-height'.
+
+The variable `resize-minibuffer-window-exactly' determines whether the
+minibuffer window should ever be shrunk to make it no larger than needed to
+display its contents.
+
+When using a window system, it is possible for a minibuffer to be the sole
+window in a frame. Since that window is already its maximum size, the only
+way to make more text visible at once is to increase the size of the frame.
+The variable `resize-minibuffer-frame' controls whether this should be
+done. The variables `resize-minibuffer-frame-max-height' and
+`resize-minibuffer-frame-exactly' are analogous to their window
+counterparts."
+:short-doc "Dynamically resize minibuffer to display entire contents"
+:group 'buffers-and-windows
+:enable #'(lambda ()
+ (resize-minibuffer-mode 1))
+:disable #'(lambda ()
+ (resize-minibuffer-mode -1))
+ )
+)
+
(provide 'rsz-minibuf)
Index: xemacs-packages/edit-utils/saveconf.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/saveconf.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 saveconf.el
--- xemacs-packages/edit-utils/saveconf.el 1998/01/14 06:36:17 1.1.1.1
+++ xemacs-packages/edit-utils/saveconf.el 2005/01/31 20:55:50
＠＠ -282,3 +282,60 ＠＠ point is set in each window to what is w
(save-excursion
(set-buffer (get-buffer-create "*scratch*"))
default-directory))
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'save-context
+"This package of functions gives Emacs the ability to remember which
+files were being visited, the windows that were on them, and the
+value of point in their buffers the last Emacs session in the same
+directory. This is an emulation of an old Gosling Emacs feature.
+
+The relevant commands are save-context and recover-context.
+
+Most of the time you'll want an Emacs session's context saved even if
+you choose not to recover it later. To avoid having to manually
+M-x save-context at each emacs exit, put the line:
+ (setq auto-save-and-recover-context t)
+in your .emacs or in default.el in the lisp directory of the Emacs
+distribution. The context will then automatically be saved when
+Emacs exits.
+
+By default only the contexts of visible buffers (buffers with windows
+on them) are saved. Setting the variable save-buffer-context to t
+causes the contexts of all buffers to be saved.
+
+Put this file in the \"lisp\" directory of the emacs distribution in a
+file called saveconf.el. Byte-compile it.
+
+There are two ways to use this package.
+ 1) Put the line
+ (require 'saveconf)
+ in the file site-init.el in the lisp directory of the Emacs
+ directory and rebuild Emacs. If you get the \"Pure Lisp storage
+ exhausted\" error message when rebuilding Emacs, increase PURESIZE
+ in src/config.h by about 30000 bytes and try again. It's almost
+ certain that this will happen to you so you might as well increase
+ PURESIZE beforehand.
+
+ This is the preferred mode of operation because it allows the
+ package to become part of Emacs' startup sequence and automatically
+ restore context in a directory if Emacs is invoked without any
+ command line arguments.
+
+ 2) Put these lines
+ (require 'saveconf)
+ (if (null (cdr command-line-args))
+ (setq inihibit-startup-message (recover-context)))
+ at the end of your .emacs file or the default.el file in the
+ lisp directory of the Emacs distribution. This causes the
+ context saved in the current directory to be recovered whenever
+ Emacs is invoked without any arguments.
+"
+:short-doc "Save buffer and window configs between editing sessions"
+:group 'buffers-and-windows
+;; #### Write the hooks correctly so they don't require manual modification
+;; of init.el.
+ )
+)
Index: xemacs-packages/edit-utils/savehist.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/savehist.el,v
retrieving revision 1.2
diff -u -p -r1.2 savehist.el
--- xemacs-packages/edit-utils/savehist.el 1999/11/27 20:49:59 1.2
+++ xemacs-packages/edit-utils/savehist.el 2005/01/31 20:55:50
＠＠ -200,6 +200,33 ＠＠ A variable will be saved if it is bound
(subseq arg 0 n)
arg))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'save-history
+"Many editors (e.g. Vim) have the feature of saving minibuffer
+history to an external file after exit. This package provides the
+same feature in Emacs. When Emacs is about the exit,
+`savehist-save' will dump the contents of various minibuffer
+histories (as determined by `savehist-history-variables') to a save
+file (`~/.emacs-history' by default). Although the package was
+designed for saving the minibuffer histories, any variables can be
+saved that way.
+
+To use savehist, put the following to `~/.emacs':
+
+\(require 'savehist)
+\(savehist-load)
+
+Be sure to have `savehist.el' in a directory that is in your
+load-path, and byte-compile it."
+:short-doc "Save minibuffer history"
+:group 'editing
+;; #### Write the hooks correctly so they don't require manual modification
+;; of init.el.
+ )
+)
+
(provide 'savehist)
;;; savehist.el ends here
Index: xemacs-packages/edit-utils/saveplace.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/saveplace.el,v
retrieving revision 1.2
diff -u -p -r1.2 saveplace.el
--- xemacs-packages/edit-utils/saveplace.el 2002/10/19 20:18:07 1.2
+++ xemacs-packages/edit-utils/saveplace.el 2005/01/31 20:55:50
＠＠ -232,11 +232,28 ＠＠ To save places automatically in all file
(if save-place-loaded
(save-place-alist-to-file)))
-(add-hook 'find-file-hooks 'save-place-find-file-hook t)
-
-(add-hook 'kill-emacs-hook 'save-place-kill-emacs-hook)
-
-(add-hook 'kill-buffer-hook 'save-place-to-alist)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'save-place
+"Automatically save place in files, so that visiting them later
+\(even during a different Emacs session) automatically moves point
+to the saved position, when the file is first found. Uses the
+value of buffer-local variable save-place to determine whether to
+save position or not."
+:short-doc "Automatically save place in files"
+:require 'saveplace
+:group 'buffers-and-windows
+:enable #'(lambda ()
+ (add-hook 'find-file-hooks 'save-place-find-file-hook t)
+ (add-hook 'kill-emacs-hook 'save-place-kill-emacs-hook)
+ (add-hook 'kill-buffer-hook 'save-place-to-alist))
+:disable #'(lambda ()
+ (remove-hook 'find-file-hooks 'save-place-find-file-hook t)
+ (remove-hook 'kill-emacs-hook 'save-place-kill-emacs-hook)
+ (remove-hook 'kill-buffer-hook 'save-place-to-alist))
+ )
+)
(provide 'saveplace) ; why not...
Index: xemacs-packages/edit-utils/scroll-in-place.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/scroll-in-place.el,v
retrieving revision 1.4
diff -u -p -r1.4 scroll-in-place.el
--- xemacs-packages/edit-utils/scroll-in-place.el 2002/05/11 05:41:23 1.4
+++ xemacs-packages/edit-utils/scroll-in-place.el 2005/01/31 20:55:51
＠＠ -1575,6 +1575,156 ＠＠ call this function from other code."
;; This doesn't work with Red Gnus
;; (add-hook 'gnus-article-mode-hook 'turn-off-scroll-in-place)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'scroll-in-place
+"This package provides improved vertical scrolling commands for XEmacs.
+These new commands offer the following features:
+
++ When a scrolling command is executed, XEmacs tries to keep point as
+ close as possible to its original window position (window line and
+ column). This is what \"scroll in place\" means: point stays \"in place\"
+ within the window. (There are times when point must be moved from its
+ original window position in order to execute the scroll; see below.)
+
+ The variable `scroll-in-place', which is true by default, determines
+ whether or not the standard XEmacs scrolling commands (`scroll-down',
+ `scroll-up', `scroll-other-window-down', and `scroll-other-window') use
+ the \"in place\" features listed here. When `scroll-in-place' is `nil'
+ the standard XEmacs scrolling commands essentially just call the
+ original versions of themselves. (Note that even when `scroll-in-place'
+ is `nil' the new versions of `scroll-down' and `scroll-up' have slightly
+ different behavior when a minibuffer window is the selected window. See
+ below.)
+
+ It is possible to turn off (or turn on) \"in place\" scrolling for certain
+ buffers by making buffer-local bindings of the variable `scroll-in-
+ place' for those buffers. The variable `scroll-in-place' is not usually
+ buffer-local, but you can make it so if you desire.
+
++ Because the improved scrolling commands keep point at its original
+ window position, these scrolling commands are \"reversible.\" The
+ `scroll-up' command undoes the effect of the immediately previous
+ `scroll-down' command (if any) and vice versa. In other words, if you
+ scroll up and then immediately scroll back down, the window config-
+ uration is restored to its exact original state. This allows you to
+ browse through a buffer more easily, as you can always get back to the
+ original configuration.
+
+ Note, however, that the improved scrolling commands are guaranteed to be
+ reversible only if there are no intervening non-scrolling commands.
+ Also, if you give a prefix argument to a scrolling command (in order to
+ specify the number of lines to scroll by), previous scrolling commands
+ may no longer be reversible. More specifically, if the new prefix
+ argument has a different magnitude than the previous scrolling distance,
+ then any previous scrolling commands are not reversible. The new prefix
+ argument takes precedence.
+
+ You might find it useful to think of the scrolling commands as forming
+ \"chains.\" A scrolling command either starts or continues a chain. By
+ issuing a non-scrolling command or by changing the number of lines to be
+ scrolled, you break the chain. (Note that simply changing the scrolling
+ direction won't break the chain; changing the absolute number of lines
+ to be scrolled is what breaks the chain.) Scrolling commands are
+ guaranteed to be reversible only within the current chain. Hopefully
+ that's clear enough.
+
++ When a scrolling command is given a prefix argument (which specifies the
+ number of lines to scroll by), then that argument becomes the default
+ scrolling distance for all immediately subsequent scrolling commands.
+ This means that you can easily set the scrolling distance for a chain
+ of scrolling commands. Note that a new prefix argument or any non-
+ scrolling command breaks the chain (as described above), and any further
+ scrolling commands will use the usual defaults (or the prefix argument
+ you specify at that time, of course).
+
+ However, there are cases in which one doesn't want the current scrolling
+ command to use the default scrolling distance that was set by the
+ previous scrolling command. For example, suppose that you had special
+ commands that scrolled one line up and one line down. When you invoke
+ one of these commands, the \"in place\" scrolling routines set the default
+ scrolling distance to be just one line. Now suppose that you use one of
+ your special commands and then immediately invoke `scroll-up' (`C-v'),
+ expecting it to scroll by a near windowful of text. You would be
+ disappointed --- because the previous command set the default scrolling
+ distance to be just one line, `scroll-up' just scrolls by one line.
+
+ To solve this problem, \"scroll-in-place\" allows you to divide scrolling
+ commands into separate \"groups.\" Commands in a group can only form
+ chains with (and therefore, inherit defaults from) commands in the same
+ group. (Note that no command can be in more than one group.) If you
+ invoke a scrolling command that is not in the same group as that of the
+ immediately previous scrolling command, then the previous chain is
+ broken and you start a new chain --- with a new set of defaults.
+
+ So to solve the problem described above, you could put your one-line
+ scrolling commands in their own group. Once that is done, the standard
+ scrolling commands will not form chains with your one-line scrolling
+ commands, and therefore will not use the default scrolling distance set
+ by those commands. Problem solved!
+
+ By default, all \"in place\" scrolling commands are in a single group. If
+ you want to partition some commands into separate groups, you must do
+ that yourself *before* any \"in place\" commands are invoked. For more
+ information about grouping commands, see the documentation for the
+ variables `scroll-command-groups' and `scroll-default-command-group'.
+
++ The improved scrolling commands will avoid displaying empty lines past
+ the end of the buffer when possible. In other words, just as you can't
+ see \"dead space\" before the beginning of the buffer text, the new
+ scrolling commands try to avoid displaying \"dead space\" past the end of
+ the buffer text. This behavior is somewhat configurable; see the
+ documentation for the variable `scroll-allow-blank-lines-past-eob'.
+
+ Dead space will be displayed if it is necessary in order to make a
+ previous scrolling action reversible, however.
+
++ If the scrolling commands cannot keep point at its initial window
+ position (because a buffer boundary is on screen and the window can't be
+ scrolled as far as necessary to keep point at the right place), point is
+ allowed to temporarily stray from its initial window position. That is,
+ point moves the correct number of window lines, even if it means that it
+ has to stray from its desired window position. This straying is undone
+ when (and if) the scrolling action is reversed.
+
++ If a scrolling command tries to move point past a buffer boundary, point
+ is instead moved to the boundary (the beginning or the end of the buffer
+ as appropriate) and an appropriate message is displayed. This motion is
+ reversible, of course.
+
+ However, if point was already at the buffer boundary when the scrolling
+ command was invoked, the command signals an appropriate error instead.
+
++ When a minibuffer window is the selected window, the new versions of
+ `scroll-up' and `scroll-down' either scroll the window in the variable
+ `minibuffer-scroll-window' (which is usually the window of completions)
+ or the `next-window' if there is no `minibuffer-scroll-window'. This is
+ usually much more useful than scrolling the minibuffer itself. (Note
+ that this feature is available even when the variable `scroll-in-place'
+ is `nil'.)
+
++ When a scrolling command is scrolling a window other than the selected
+ window, it will signal an appropriate buffer boundary error if the
+ window cannot be scrolled (because the appropriate buffer boundary is
+ already visible). This means that an error is signalled even in cases
+ that would be allowed (by \"straying\" point or by moving it to the buffer
+ boundary) if the window were selected.
+
+ (If an error were not signalled in these cases, then there would be many
+ cases in which the last scroll in a particular direction would appear to
+ do nothing because only the point position would change --- the
+ displayed text would stay the same! To avoid these cases the scrolling
+ commands signal boundary errors \"prematurely\" when the window to be
+ scrolled is not selected.)"
+:short-doc "Keep cursor on same line when scrolling"
+:group 'editing
+:require 'scroll-in-place
+:enable #'turn-on-scroll-in-place
+:disable #'turn-off-scroll-in-place)
+)
+
+
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;
Index: xemacs-packages/edit-utils/setnu.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/setnu.el,v
retrieving revision 1.3
diff -u -p -r1.3 setnu.el
--- xemacs-packages/edit-utils/setnu.el 2002/07/24 18:36:50 1.3
+++ xemacs-packages/edit-utils/setnu.el 2005/01/31 20:55:51
＠＠ -447,3 +447,17 ＠＠ it is created based on where the extent
(add-hook 'before-change-functions 'setnu-before-change-function)
(add-hook 'after-change-functions 'setnu-after-change-function)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'setnu
+"vi-style line number mode for XEmacs"
+:short-doc "vi-style line number mode for XEmacs"
+:group 'display
+:enable #'(lambda ()
+ (setnu-mode 1))
+:disable #'(lambda ()
+ (setnu-mode -1))
+ )
+)
Index: xemacs-packages/edit-utils/shell-font.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/shell-font.el,v
retrieving revision 1.2
diff -u -p -r1.2 shell-font.el
--- xemacs-packages/edit-utils/shell-font.el 1998/04/23 11:12:00 1.2
+++ xemacs-packages/edit-utils/shell-font.el 2005/01/31 20:55:51
＠＠ -148,13 +148,31 ＠＠ face-manipulation functions."
(set-process-filter proc 'shell-font-process-filter))
nil)
-(add-hook 'shell-mode-hook 'install-shell-fonts)
-(add-hook 'telnet-mode-hook 'install-shell-fonts)
-(add-hook 'gdb-mode-hook 'install-shell-fonts)
-
;; for compatibility with the 19.8 version
;(fset 'install-shell-font-prompt 'install-shell-fonts)
(make-obsolete 'install-shell-font-prompt 'install-shell-fonts)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'shell-font
+"The prompt in your shell-buffers will appear bold-italic, process
+output will appear in normal face, and typein will appear in bold.
+
+The faces shell-prompt, shell-input and shell-output can be modified
+as desired, for example, (copy-face 'italic 'shell-prompt)."
+:short-doc "Decorate a shell buffer with fonts"
+:group 'display
+:enable #'(lambda ()
+ (add-hook 'shell-mode-hook 'install-shell-fonts)
+ (add-hook 'telnet-mode-hook 'install-shell-fonts)
+ (add-hook 'gdb-mode-hook 'install-shell-fonts))
+:disable #'(lambda ()
+ (remove-hook 'shell-mode-hook 'install-shell-fonts)
+ (remove-hook 'telnet-mode-hook 'install-shell-fonts)
+ (remove-hook 'gdb-mode-hook 'install-shell-fonts))
+ )
+)
(provide 'shell-font)
Index: xemacs-packages/edit-utils/toolbar-utils.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/toolbar-utils.el,v
retrieving revision 1.2
diff -u -p -r1.2 toolbar-utils.el
--- xemacs-packages/edit-utils/toolbar-utils.el 2002/12/12 03:28:33 1.2
+++ xemacs-packages/edit-utils/toolbar-utils.el 2005/01/31 20:55:52
＠＠ -479,6 +479,61 ＠＠ This function will not find spacers."
(setq pos (1+ pos)))
(if toolbar pos nil)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'toolbar-utils
+"This contains utilities for managing XEmacs toolbars.
+
+`restore-initial-toolbar'
+
+Restores the default toolbar defined by initial-toolbar-spec.
+There is also a cache of killed buttons in `button-palette'.
+
+`toolbar-add-button-on-the-fly'
+
+Add an button at POSITION to the default toolbar of the selected window.
+
+`toolbar-add-kbd-macro'
+
+Add a button invoking a keyboard macro to the toolbar of the current buffer.
+The button is added at the end of the left group.
+
+`toolbar-add-execute-macro-button'
+
+Add a button to the global toolbar to execute the last keyboard macro."
+:short-doc "Toolbar utility functions"
+:group 'toolbars
+:commands '(["Add toolbar button on-the-fly" toolbar-add-button-on-the-fly]
+ ["Add button for a macro to toolbar" toolbar-add-kbd-macro]
+ ["Add execute-last-macro button to toolbar" toolbar-add-execute-macro-button]
+ ["Restore initial toolbar" restore-initial-toolbar])
+ ;; no :enable
+ ;; no :disable
+ )
+)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'toolbar-add-exec-macro
+"Add a button to the global toolbar to execute the last keyboard macro.
+
+Unlike `toolbar-add-kbd-macro', this does not copy the macro. The macro
+executed will change with redefinitions.
+
+Due to a simple implementation, this button will not appear in buffers with
+local toolbars if invoked after the toolbar is installed. If you like this
+button, it's probably best to invoke this function in your init file.
+
+See also the `toolbar-utils' behavior."
+:short-doc "Add execute-macro button to the toolbar"
+:group 'toolbars
+:enable #'toolbar-add-execute-macro-button
+ ;; no :disable
+ )
+)
+
(provide 'toolbar-utils)
;;; toolbar-utils.el ends here
Index: xemacs-packages/edit-utils/uniquify.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/uniquify.el,v
retrieving revision 1.5
diff -u -p -r1.5 uniquify.el
--- xemacs-packages/edit-utils/uniquify.el 2001/12/27 00:47:21 1.5
+++ xemacs-packages/edit-utils/uniquify.el 2005/01/31 20:55:52
＠＠ -475,4 +475,27 ＠＠ Meant to be called from the `uniquify-ig
(add-hook 'kill-buffer-hook 'delay-uniquify-rationalize-file-buffer-names)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'uniquify
+"Emacs's standard method for making buffer names unique adds <2>, <3>,
+etc. to the end of (all but one of) the buffers. This file replaces
+that behavior, for buffers visiting files and dired buffers, with a
+uniquification that adds parts of the file name until the buffer names
+are unique. For instance, buffers visiting /u/mernst/tmp/Makefile and
+/usr/projects/zaphod/Makefile would be named Makefile|tmp and
+Makefile|zaphod, respectively (instead of Makefile and Makefile<2>).
+Other buffer name styles are also available."
+:short-doc "unique buffer names dependent on file name"
+:require 'uniquify
+:group 'buffers-and-windows
+:enable #'(lambda ()
+ (setq uniquify-buffer-name-style 'post-forward))
+:disable #'(lambda ()
+ (setq uniquify-buffer-name-style nil))
+ )
+)
+
+
;;; uniquify.el ends here
Index: xemacs-packages/edit-utils/vertical-mode.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/vertical-mode.el,v
retrieving revision 1.2
diff -u -p -r1.2 vertical-mode.el
--- xemacs-packages/edit-utils/vertical-mode.el 2002/03/24 20:52:50 1.2
+++ xemacs-packages/edit-utils/vertical-mode.el 2005/01/31 20:55:52
＠＠ -72,5 +72,23 ＠＠
minor-mode-alist (cons
'(vertical-mode " Vertical") minor-mode-alist))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'vertical-mode
+"This minor mode allows you to conviently edit things that are oriented
+vertically (like tables in computer programs): after each action, cursor
+moves down. Therefore, to move block of text to the right, you simply enter
+vertical mode and then hold spacebar, waiting for autorepeat to do the job
+for you."
+:short-doc "edit vertical tables"
+:group 'editing
+:enable #'(lambda ()
+ (vertical-mode 1))
+:disable #'(lambda ()
+ (vertical-mode -1))
+ )
+)
+
(provide 'vertical-mode)
;;; vertical-mode.el ends here
Index: xemacs-packages/edit-utils/where-was-i-db.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/where-was-i-db.el,v
retrieving revision 1.5
diff -u -p -r1.5 where-was-i-db.el
--- xemacs-packages/edit-utils/where-was-i-db.el 2000/10/06 09:08:02 1.5
+++ xemacs-packages/edit-utils/where-was-i-db.el 2005/01/31 20:55:52
＠＠ -358,6 +358,108 ＠＠ that, for obvious reasons. If it isn't
wwi-db))))
(put 'wwi-with-open-database 'lisp-indent-function 1)
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'where-was-i-db
+"This Good Thing will make XEmacs keep track of where you were last
+time you visited a file.
+
+It works by installing functions on the `find-file-hooks' and on
+the buffer-local `kill-buffer-hook'. When a buffer is killed, if
+it was visiting a file, and place saving has been enabled for it, a
+database entry is made, saving the location of `point'. When you
+visit a file, the database is queried, keyed on `buffer-file-name',
+and if an entry is found, point is set to the value retrieved, and
+place saving is enabled again for that buffer.
+
+There is a command, which is initially not bound to a keystroke in
+this incarnation; and may never be, since I think completion works
+well enough:
+
+`M-x toggle-where-was-i' aka `M-x tog[TAB]w[TAB]'
+
+... that will turn place saving on and off on a per-file, buffer-
+local basis. If `where-was-i-db' has been turned off in a buffer
+and then you kill it, or exit XEmacs, any record for that file will
+be purged from the database, and you'll start at the top of the
+file next time you open it, with place saving turned off there.
+
+Place saving is automatically still `on' when you visit a file you'd
+toggled it on for in a previous session or visitation. (That's the
+point of it, after all.)
+
+Toggling place saving on in a buffer visiting a file is all that is
+required to cause the `where-was-i-db' feature to be autoloaded, as
+`toggle-where-was-i' will call on `install-where-was-i' if the
+`wwi-ffh' has not yet been installed. That WILL NOT cause this
+feature to be automatically enabled in your next XEmacs invocation,
+however. For that, you must customize and save
+`wwi-auto-install-on-startup-flag'.
+There is more information about this in its docstring.
+
+ This feature can be unloaded with:
+
+`C-u M-x install-where-was-i'
+
+... this will call `unload-feature', as well as traverse the
+`buffer-list' removing the buffer-local `kill-buffer-hook'
+installed by this program. Note that any buffers that got place
+saving enabled by having had an entry in the database for them when
+they were first visited (thus restoring point to where it was the
+last time you had visited the file), will not have an updated entry
+made, nor the old entry removed (as would happen if you
+`toggle-where-was-i' to off in just that buffer), after you
+uninstall this feature like that.
+
+If you toggle it on again in a buffer visiting a file, then kill
+that buffer, the point will be saved for it. When you kill the
+other buffers that had place saving enabled before you uninstalled
+the feature with `C-u M-x install-where-was-i', no `where-was-i-db'
+database update will happen for them, since their buffer-local
+`kill-buffer-hook' will have been cleaned of the member
+`wwi-save-where-i-am', the function that writes the `point' entry
+to the database when a buffer is killed. If you then re-visit one
+of those files, point will get restored to the location it did the
+last time you visited that file with `where-was-i-db' installed.
+
+To remove a file from the place saving database, simply visit it,
+`M-x toggle-where-was-i' to switch `where-was-i-db' off, then kill
+that buffer. You can see how this works by looking at the
+definition of `wwi-save-where-i-am'. I dare you not to... (may as
+well use VI.)
+
+After a period of time, the database of saved file positions will
+become cluttered with the names of files that no longer exist. You
+may vacume out the crumbs using:
+
+`M-x wwi-vacume-where-was-i-db'
+
+... which will prompt you for an optional regular expression to
+match files you want records removed for. It will traverse the
+database and remove entries for file names that either match the
+regexp, or that are (not (file-exists-p file-name)). The main
+reason for this command is the removal of stale entries, for files
+that no longer exist on the filesystem.
+
+Note also that running `wwi-vacume-where-was-i-db' will cause EFS
+traffic, if you've saved your place in any remote files. Don't be
+surprised if your dialing daemon picks up the phone when you run
+the vacume function. You should be able to purge the database of
+all EFS entries with a simple regular expression passed to
+`wwi-vacume-where-was-i-db'. Of course, you might not want to do
+that, for obvious reasons. If it isn't obvious, use VI or PICO.
+"
+:short-doc "Keep persistent state in visited files"
+:group 'files
+:enable #'(lambda ()
+ (install-where-was-i 1))
+:enable #'(lambda ()
+ (install-where-was-i -1))
+ )
+)
+
(provide 'where-was-i-db)
Index: xemacs-packages/edit-utils/winring.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/winring.el,v
retrieving revision 1.2
diff -u -p -r1.2 winring.el
--- xemacs-packages/edit-utils/winring.el 2004/01/05 16:56:54 1.2
+++ xemacs-packages/edit-utils/winring.el 2005/01/31 20:55:52
＠＠ -588,6 +588,106 ＠＠ in a timely way.\n\n")
;; ...and the init fence
(setq winring-initialized t)))
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'winring
+"This package provides lightweight support for circular rings of
+window configurations. A window configuration is the layout of
+windows and associated buffers within a frame. There is always at
+least one configuration on the ring, the current configuration.
+You can create new configurations and cycle through the layouts in
+either direction. You can also delete configurations from the ring
+\(except the last one of course!). Window configurations are named,
+and you can jump to and delete named configurations. Display of
+the current window configuration name in the mode line is only
+supported as of Emacs 20.3 and XEmacs 21.0.
+
+Window configuration rings are frame specific. That is, each frame
+has its own ring which can be cycled through independently of other
+frames. This is the way I like it.
+
+You are always looking at the current window configuration for each
+frame, which consists of the windows in the frame, the buffers in
+those windows, and point in the current buffer. As you run
+commands such as \"C-x 4 b\", \"C-x 2\", and \"C-x 0\" you are modifying
+the current window configuration. When you jump to a new
+configuration, the layout that existed before the jump is captured,
+and the ring is rotated to the selected configuration. Window
+configurations are captured with `current-window-configuration',
+however winring also saves point for the current buffer.
+
+Note that by default, this binds the winring keymap to the C-x 7
+prefix, but you can change this by setting the value of
+`winring-keymap-prefix', before you call `winring-initialize'.
+Note that this is a change from previous versions of winring; the
+prefix used to be M-o but was changed on the suggestion of RMS.
+
+The following commands are defined:
+
+ C-x 7 n -- Create a new window configuration. The new
+ configuration will contain a single buffer, the one
+ named in the variable `winring-new-config-buffer-name'
+
+ With C-u, winring prompts for the name of the new
+ configuration. If you don't use C-u the function in
+ `winring-name-generator' will be called to get the
+ new configuration's name.
+
+ C-x 7 2 -- Create a duplicate of the current window
+ configuration. C-u has the same semantics as with
+ \"C-x 7 c\".
+
+ C-x 7 j -- Jump to a named configuration (prompts for the name).
+
+ C-x 7 0 -- Kill the current window configuration and rotate to the
+ previous layout on the ring. You cannot delete the
+ last configuration in the ring. With C-u, prompts
+ for the name of the configuration to kill.
+
+ C-x 7 o -- Go to the next configuration on the ring.
+
+ C-x 7 p -- Go to the previous configuration on the ring.
+
+ Note that the sequence `C-x 7 o C-x 7 p' is a no-op;
+ it leaves you in the same configuration you were in
+ before the sequence.
+
+ C-x 7 r -- Rename the current window configuration.
+
+ C-x 7 b -- Submit a bug report on winring.
+
+ C-x 7 v -- Echo the winring version.
+
+As mentioned, window configuration names can be displayed in the
+modeline, but this feature only works with Emacs 20.3 and XEmacs
+21.0. A patch for XEmacs 20.4 to support this feature is available
+at the URL below. Note that the default value of
+`winring-show-names' is currently nil by default because if your
+X/Emacs doesn't have the necessary support, ugly things can happen
+\(no you won't crash your X/Emacs -- it just won't do what you
+want).
+
+If your X/Emacs has the necessary support, you can turn on display
+of window configuration names by setting `winring-show-names' to
+t. If you don't like the position in the modeline where winring
+names are shown, you can change this by passing in your own
+modeline hacker function to `winring-initialize'.
+
+ Winring on the Web:
+
+The winring Web page (including the aforementioned XEmacs 20.4
+patch) is
+
+ http://www.python.org/emacs/winring/
+"
+:short-doc "Window configuration rings"
+:group 'buffers-and-windows
+:enable #'winring-initialize
+ ;; no :disable
+ )
+)
+
(provide 'winring)
cvs server: Diffing xemacs-packages/edt
cvs server: Diffing xemacs-packages/efs
Index: xemacs-packages/efs/efs.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/efs/efs.el,v
retrieving revision 1.22
diff -u -p -r1.22 efs.el
--- xemacs-packages/efs/efs.el 2004/10/02 14:06:04 1.22
+++ xemacs-packages/efs/efs.el 2005/01/31 20:55:56
＠＠ -10837,6 +10837,39 ＠＠ in file name expansion."
(put 'file-name-completion 'efs 'efs-file-name-completion)
(put 'file-name-all-completions 'efs 'efs-file-name-all-completions)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'efs
+"EFS is a system for transparent file-transfer between remote VMS, CMS,
+MTS, MVS, Twenex, Explorer (the last two are Lisp machines), TOPS-20,
+DOS (running the Distinct, Novell, FTP software, NCSA, Microsoft in both
+unix and DOS mode, Super TCP, and Hellsoft FTP servers), Windows NT
+\(running the Microsoft or Hummingbird ftp servers), Unix descriptive
+listings (dl), KA9Q, OS/2 hosts using FTP. This means that you can edit,
+copy and otherwise manipulate files on any machine you have access to
+from within Emacs as if it were a local file. EFS works by introducing
+an extended filename syntax, and overloading functions such as
+`insert-file-contents' so that accessing a remote file causes
+appropriate commands to be sent to an FTP process.
+
+The syntax to use is like this:
+
+\(for anonymous:) /ftp.xemacs.org:/pub/xemacs/
+\(for non-anonymous:) /ben＠gwyn.tux.org:/etc/mail/xemacs/aliases-xemacs
+
+You can specify either a file or a directory (in the latter case,
+Dired will be brought up). All operations in XEmacs on such files
+should work exactly as on any other files, modulo the additional
+slowness."
+:short-doc "Transparent file access over FTP"
+:group 'internet
+:require 'efs-auto
+:enable #'ignore
+ ;; can't :disable
+ )
+)
+
;;;; ------------------------------------------------------------
;;;; Finally run any load-hooks.
;;;; ------------------------------------------------------------
cvs server: Diffing xemacs-packages/eicq
cvs server: Diffing xemacs-packages/eieio
cvs server: Diffing xemacs-packages/elib
cvs server: Diffing xemacs-packages/emerge
cvs server: Diffing xemacs-packages/erc
cvs server: Diffing xemacs-packages/escreen
cvs server: Diffing xemacs-packages/eshell
cvs server: Diffing xemacs-packages/ess
cvs server: Diffing xemacs-packages/ess/etc
cvs server: Diffing xemacs-packages/ess/etc/icons
cvs server: Diffing xemacs-packages/ess/lisp
cvs server: Diffing xemacs-packages/ess/texi
cvs server: Diffing xemacs-packages/eterm
cvs server: Diffing xemacs-packages/eterm/etc
cvs server: Diffing xemacs-packages/eterm/etc/e
cvs server: Diffing xemacs-packages/eudc
Index: xemacs-packages/eudc/eudc.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/eudc/eudc.el,v
retrieving revision 1.22
diff -u -p -r1.22 eudc.el
--- xemacs-packages/eudc/eudc.el 2001/08/17 12:31:41 1.22
+++ xemacs-packages/eudc/eudc.el 2005/01/31 20:55:57
＠＠ -1363,6 +1363,18 ＠＠ This does nothing except loading eudc by
;;}}}
;;;###autoload
+(defvar eudc-menu
+ '("Directory Search"
+ ["Load Hotlist of Servers" eudc-load-eudc t]
+ ["New Server" eudc-set-server t]
+ "---"
+ ["Query with Form" eudc-query-form t]
+ ["Expand Inline Query" eudc-expand-inline t]
+ "---"
+ ["Get Email" eudc-get-email t]
+ ["Get Phone" eudc-get-phone t]))
+
+;;;###autoload
(cond ((not (string-match "XEmacs" emacs-version))
(defvar eudc-tools-menu (make-sparse-keymap "Directory Search"))
(fset 'eudc-tools-menu (symbol-value 'eudc-tools-menu))
＠＠ -1383,17 +1395,10 ＠＠ This does nothing except loading eudc by
'("New Server" . eudc-set-server))
(define-key eudc-tools-menu [load]
'("Load Hotlist of Servers" . eudc-load-eudc)))
-
- (t
- (let ((menu '("Directory Search"
- ["Load Hotlist of Servers" eudc-load-eudc t]
- ["New Server" eudc-set-server t]
- "---"
- ["Query with Form" eudc-query-form t]
- ["Expand Inline Query" eudc-expand-inline t]
- "---"
- ["Get Email" eudc-get-email t]
- ["Get Phone" eudc-get-phone t])))
+
+ ;; Packages under XEmacs 21.5+ may not directly modify the menubar.
+ ((not (fboundp 'define-behavior-group))
+ (let ((menu eudc-menu))
(if (not (featurep 'eudc-autoloads))
(if (string-match "XEmacs" emacs-version)
(if (and (featurep 'menubar)
＠＠ -1414,6 +1419,16 ＠＠ This does nothing except loading eudc by
(cdr menu)))))))))))
;;}}}
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'eudc
+"Not documented."
+:short-doc "Directory Search"
+:group 'internet
+:commands (cdr eudc-menu))
+)
(provide 'eudc)
cvs server: Diffing xemacs-packages/footnote
Index: xemacs-packages/footnote/footnote.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/footnote/footnote.el,v
retrieving revision 1.7
diff -u -p -r1.7 footnote.el
--- xemacs-packages/footnote/footnote.el 2002/04/23 20:35:26 1.7
+++ xemacs-packages/footnote/footnote.el 2005/01/31 20:55:58
＠＠ -788,22 +788,6 ＠＠ being set it is automatically widened."
(define-key global-map footnote-prefix footnote-mode-map))
;;;###autoload
-(if (progn (condition-case () (require 'easymenu) (error nil))
- (fboundp 'easy-menu-add-item))
- (easy-menu-add-item nil '("Cmds")
- '("Footnotes"
- ["Add Footnote" Footnote-add-footnote t]
- ["Delete Footnote" Footnote-delete-footnote t]
- ["Goto Footnote" Footnote-goto-footnote t]
- ["Back to Message" Footnote-back-to-message t]
- ["Renumber Footnotes" Footnote-renumber-footnotes t]
- "--"
- ["Set Footnote Style" Footnote-set-style t]
- ["Cycle Footnote Style" Footnote-cycle-style t]
- )))
-
-
-;;;###autoload
(defun footnote-mode (&optional arg)
"Toggle footnote minor mode.
\\<message-mode-map>
＠＠ -860,6 +844,26 ＠＠ key binding
(setq minor-mode-alist
(cons '(footnote-mode footnote-mode-line-string)
minor-mode-alist)))
+
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'footnote
+ "Not documented."
+:short-doc "Footnotes"
+:group 'editing
+:commands
+ '(["Add Footnote" Footnote-add-footnote]
+ ["Delete Footnote" Footnote-delete-footnote]
+ ["Goto Footnote" Footnote-goto-footnote]
+ ["Back to Message" Footnote-back-to-message]
+ ["Renumber Footnotes" Footnote-renumber-footnotes]
+ "--"
+ ["Set Footnote Style" Footnote-set-style]
+ ["Cycle Footnote Style" Footnote-cycle-style]
+ ))
+)
(provide 'footnote)
cvs server: Diffing xemacs-packages/forms
cvs server: Diffing xemacs-packages/fortran-modes
cvs server: Diffing xemacs-packages/frame-icon
cvs server: Diffing xemacs-packages/frame-icon/etc
cvs server: Diffing xemacs-packages/fsf-compat
cvs server: Diffing xemacs-packages/games
Index: xemacs-packages/games/gamegrid.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/gamegrid.el,v
retrieving revision 1.5
diff -u -p -r1.5 gamegrid.el
--- xemacs-packages/games/gamegrid.el 2003/06/14 18:48:26 1.5
+++ xemacs-packages/games/gamegrid.el 2005/01/31 20:55:58
＠＠ -1,4 +1,4 ＠＠
-;;; gamegrid.el -- Library for implementing grid-based games on Emacs.
+;;; gamegrid.el --- Library for implementing grid-based games on Emacs.
;; Copyright (C) 1998 Free Software Foundation, Inc.
＠＠ -34,6 +34,10 ＠＠
;; Modified: 2003-06-14, update email address, remove URL
;; Tested with XEmacs 20.3/4/5 and Emacs 19.34
+
+(defgroup gamegrid nil
+ "Library for implementing grid-based games on Emacs."
+:group 'games)
(eval-when-compile
(require 'cl))
Index: xemacs-packages/games/snake.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/snake.el,v
retrieving revision 1.4
diff -u -p -r1.4 snake.el
--- xemacs-packages/games/snake.el 2003/06/14 18:48:26 1.4
+++ xemacs-packages/games/snake.el 2005/01/31 20:55:58
＠＠ -40,6 +40,10 ＠＠
(require 'gamegrid)
+(defgroup snake nil
+ "Implementation of Snake for Emacs"
+:group 'games)
+
;; ;;;;;;;;;;;;; customization variables ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(defvar snake-use-glyphs t
Index: xemacs-packages/games/sokoban.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/sokoban.el,v
retrieving revision 1.7
diff -u -p -r1.7 sokoban.el
--- xemacs-packages/games/sokoban.el 2003/06/14 18:48:27 1.7
+++ xemacs-packages/games/sokoban.el 2005/01/31 20:55:58
＠＠ -1,4 +1,4 ＠＠
-;;; sokoban.el -- Implementation of Sokoban for Emacs.
+;;; sokoban.el --- Implementation of Sokoban for Emacs.
;; Copyright (C) 1998 Free Software Foundation, Inc.
＠＠ -50,6 +50,10 ＠＠
;; The levels and some of the pixmaps were
;; taken directly from XSokoban
+(defgroup sokoban nil
+ "Implementation of Sokoban for Emacs."
+:group 'games)
+
(eval-when-compile
(require 'cl))
＠＠ -754,6 +758,16 ＠＠ sokoban-mode keybindings:
(gamegrid-kill-timer)
(sokoban-mode)
(sokoban-start-game))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'sokoban
+ "Not documented."
+:group 'games
+:commands
+ '(["Sokoban" sokoban]))
+)
(provide 'sokoban)
Index: xemacs-packages/games/tetris.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/games/tetris.el,v
retrieving revision 1.4
diff -u -p -r1.4 tetris.el
--- xemacs-packages/games/tetris.el 2003/06/14 18:48:27 1.4
+++ xemacs-packages/games/tetris.el 2005/01/31 20:55:59
＠＠ -1,4 +1,4 ＠＠
-;;; tetris.el -- Implementation of Tetris for Emacs.
+;;; tetris.el --- Implementation of Tetris for Emacs.
;; Copyright (C) 1998 Free Software Foundation, Inc.
＠＠ -59,6 +59,10 ＠＠
;; Tested with XEmacs 20.3/4/5, 21.4.13 and Emacs 19.34
+(defgroup tetris nil
+ "Implementation of Tetris for Emacs."
+:group 'games)
+
(eval-when-compile
(require 'cl))
＠＠ -806,6 +810,16 ＠＠ tetris-mode keybindings:
(gamegrid-kill-timer)
(tetris-mode)
(tetris-start-game))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'tetris
+ "Not documented."
+:group 'games
+:commands
+ '(["Tetris" tetris]))
+)
(provide 'tetris)
cvs server: Diffing xemacs-packages/general-docs
cvs server: Diffing xemacs-packages/general-docs/texi
cvs server: Diffing xemacs-packages/general-docs/texi/packages
cvs server: Diffing xemacs-packages/general-docs/texi/xemacs
cvs server: Diffing xemacs-packages/gnats
cvs server: Diffing xemacs-packages/gnats/etc
cvs server: Diffing xemacs-packages/gnats/lib-src
cvs server: Diffing xemacs-packages/gnats/texi
cvs server: Diffing xemacs-packages/gnus
cvs server: Diffing xemacs-packages/gnus/etc
cvs server: Diffing xemacs-packages/gnus/etc/gnus
cvs server: Diffing xemacs-packages/gnus/etc/smilies
cvs server: Diffing xemacs-packages/gnus/etc/sounds
cvs server: Diffing xemacs-packages/gnus/gnus
cvs server: xemacs-packages/gnus/gnus/make.bat is a new entry, no comparison available
cvs server: Diffing xemacs-packages/gnus/gnus/lisp
cvs server: xemacs-packages/gnus/gnus/lisp/gnus.el is a new entry, no comparison available
cvs server: Diffing xemacs-packages/gnus/gnus/texi
cvs server: Diffing xemacs-packages/gnus/lisp
cvs server: Diffing xemacs-packages/gnus/texi
cvs server: Diffing xemacs-packages/gnus/texi/etc
cvs server: Diffing xemacs-packages/gnus/texi/herds
cvs server: Diffing xemacs-packages/gnus/texi/misc
cvs server: Diffing xemacs-packages/gnus/texi/picons
cvs server: Diffing xemacs-packages/gnus/texi/ps
cvs server: Diffing xemacs-packages/gnus/texi/screen
cvs server: Diffing xemacs-packages/gnus/texi/smilies
cvs server: Diffing xemacs-packages/gnus/texi/xface
cvs server: Diffing xemacs-packages/haskell-mode
cvs server: Diffing xemacs-packages/hm--html-menus
cvs server: Diffing xemacs-packages/hm--html-menus/etc
cvs server: Diffing xemacs-packages/hm--html-menus/etc/idd
cvs server: Diffing xemacs-packages/hm--html-menus/etc/templates
cvs server: Diffing xemacs-packages/hyperbole
cvs server: Diffing xemacs-packages/hyperbole/kotl
cvs server: Diffing xemacs-packages/hyperbole/man
cvs server: Diffing xemacs-packages/ibuffer
cvs server: Diffing xemacs-packages/idlwave
cvs server: Diffing xemacs-packages/igrep
cvs server: Diffing xemacs-packages/ilisp
cvs server: Diffing xemacs-packages/ilisp/docs
cvs server: Diffing xemacs-packages/ilisp/extra
cvs server: Diffing xemacs-packages/ilisp/pictures
cvs server: Diffing xemacs-packages/ispell
Index: xemacs-packages/ispell/ispell.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ispell/ispell.el,v
retrieving revision 1.21
diff -u -p -r1.21 ispell.el
--- xemacs-packages/ispell/ispell.el 2005/01/23 13:50:55 1.21
+++ xemacs-packages/ispell/ispell.el 2005/01/31 20:56:03
＠＠ -3530,6 +3530,22 ＠＠ Both should not be used to define a buff
(add-to-list 'debug-ignored-errors "^No word found to check!$")
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'ispell
+ "Not documented."
+:short-doc "Spell-Check"
+:group 'editing
+:commands
+ '(["%_Buffer" ispell-buffer]
+ "---"
+ ["%_Word" ispell-word]
+ ["%_Complete Word" ispell-complete-word]
+ ["%_Region" ispell-region :active (region-active-p)]
+ ))
+)
+
(provide 'ispell)
cvs server: Diffing xemacs-packages/jde
cvs server: Diffing xemacs-packages/jde/doc
cvs server: Diffing xemacs-packages/jde/doc/html
cvs server: Diffing xemacs-packages/jde/doc/html/bsh-ug
cvs server: Diffing xemacs-packages/jde/doc/html/bsh-ug/images
cvs server: Diffing xemacs-packages/jde/doc/html/css
cvs server: Diffing xemacs-packages/jde/doc/html/jdb-ug
cvs server: Diffing xemacs-packages/jde/doc/html/jdb-ug/images
cvs server: Diffing xemacs-packages/jde/doc/html/jde-ug
cvs server: Diffing xemacs-packages/jde/doc/html/jde-ug/images
cvs server: Diffing xemacs-packages/jde/doc/html/jdebug-ug
cvs server: Diffing xemacs-packages/jde/doc/html/jdebug-ug/images
cvs server: Diffing xemacs-packages/jde/doc/src
cvs server: Diffing xemacs-packages/jde/doc/src/css
cvs server: Diffing xemacs-packages/jde/doc/src/jde-ug
cvs server: Diffing xemacs-packages/jde/doc/src/jde-ug/images
cvs server: Diffing xemacs-packages/jde/doc/src/styles
cvs server: Diffing xemacs-packages/jde/doc/src/styles/html
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl/au
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl/img
cvs server: Diffing xemacs-packages/jde/doc/tli_rbl/txt
cvs server: Diffing xemacs-packages/jde/java
cvs server: Diffing xemacs-packages/jde/java/bsh-commands
cvs server: Diffing xemacs-packages/jde/java/bsh-commands/bsh
cvs server: Diffing xemacs-packages/jde/java/bsh-commands/bsh/commands
cvs server: Diffing xemacs-packages/jde/java/doc
cvs server: Diffing xemacs-packages/jde/java/doc/jde
cvs server: Diffing xemacs-packages/jde/java/doc/jde/debugger
cvs server: Diffing xemacs-packages/jde/java/lib
cvs server: Diffing xemacs-packages/jde/java/src
cvs server: Diffing xemacs-packages/jde/java/src/jde
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger/command
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger/expr
cvs server: Diffing xemacs-packages/jde/java/src/jde/debugger/spec
cvs server: Diffing xemacs-packages/jde/java/src/jde/parser
cvs server: Diffing xemacs-packages/jde/java/src/jde/util
cvs server: Diffing xemacs-packages/jde/java/src/jde/wizards
cvs server: Diffing xemacs-packages/jde/lisp
cvs server: Diffing xemacs-packages/liece
cvs server: Diffing xemacs-packages/liece/dcc
cvs server: Diffing xemacs-packages/liece/doc
cvs server: Diffing xemacs-packages/liece/etc
cvs server: Diffing xemacs-packages/liece/etc/icons
cvs server: Diffing xemacs-packages/liece/etc/po
cvs server: Diffing xemacs-packages/liece/etc/styles
cvs server: Diffing xemacs-packages/liece/lisp
cvs server: Diffing xemacs-packages/mail-lib
cvs server: Diffing xemacs-packages/mailcrypt
cvs server: Diffing xemacs-packages/mew
cvs server: Diffing xemacs-packages/mew/mew
cvs server: Diffing xemacs-packages/mew/mew/OS2
cvs server: Diffing xemacs-packages/mew/mew/Win32
cvs server: Diffing xemacs-packages/mew/mew/bin
cvs server: Diffing xemacs-packages/mew/mew/contrib
cvs server: Diffing xemacs-packages/mew/mew/etc
cvs server: Diffing xemacs-packages/mew/mew/etc/etc
cvs server: Diffing xemacs-packages/mew/mew/info
cvs server: Diffing xemacs-packages/mh-e
Index: xemacs-packages/mh-e/mh-e.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mh-e/mh-e.el,v
retrieving revision 1.7
diff -u -p -r1.7 mh-e.el
--- xemacs-packages/mh-e/mh-e.el 2003/09/02 23:39:26 1.7
+++ xemacs-packages/mh-e/mh-e.el 2005/01/31 20:56:04
＠＠ -2504,6 +2504,16 ＠＠ well.")
"^There is no other window$"))
(add-to-list 'debug-ignored-errors mess))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'mh
+ "Not documented."
+:group 'internet
+:commands
+ '(["Read Mail (MH)..." (mh-rmail t)]))
+)
+
;;; Local Variables:
;;; indent-tabs-mode: nil
;;; sentence-end-double-space: nil
cvs server: Diffing xemacs-packages/mine
Index: xemacs-packages/mine/xmine.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mine/xmine.el,v
retrieving revision 1.5
diff -u -p -r1.5 xmine.el
--- xemacs-packages/mine/xmine.el 2000/10/06 09:20:18 1.5
+++ xemacs-packages/mine/xmine.el 2005/01/31 20:56:04
＠＠ -865,5 +865,16 ＠＠ We set up the XMine buffer, set up the k
(if ext (xmine-select-button ext)
(xmine-select-button (xmine-field-button-at xmine-width y)))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'xmine
+ "Not documented."
+:short-doc "Mine game"
+:group 'games
+:commands
+ '(["Mine Game" xmine]))
+)
+
(provide 'xmine)
cvs server: Diffing xemacs-packages/mine/etc
cvs server: Diffing xemacs-packages/misc-games
Index: xemacs-packages/misc-games/NeXTify.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/NeXTify.el,v
retrieving revision 1.2
diff -u -p -r1.2 NeXTify.el
--- xemacs-packages/misc-games/NeXTify.el 1999/11/27 20:49:55 1.2
+++ xemacs-packages/misc-games/NeXTify.el 2005/01/31 20:56:04
＠＠ -28,6 +28,10 ＠＠
;;; Code:
+(defgroup NeXTify nil
+ "Character insertion variation"
+:group 'games)
+
(defun SeLF-insert-command (arg)
"Insert the character you TyPE.
Whichever character you TyPE to run ThIS command is inserted."
Index: xemacs-packages/misc-games/advocacy.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/advocacy.el,v
retrieving revision 1.4
diff -u -p -r1.4 advocacy.el
--- xemacs-packages/misc-games/advocacy.el 1999/11/27 20:49:55 1.4
+++ xemacs-packages/misc-games/advocacy.el 2005/01/31 20:56:04
＠＠ -1,4 +1,4 ＠＠
-;;; advocacy.el -- blatant XEmacs self promotion
+;;; advocacy.el --- blatant XEmacs self promotion
;; Copyright (C) 1996, 1997 Free Software Foundation, Inc.
;; Copyright (C) 1996 Chuck Thompson <cthomp(a)xemacs.org>
＠＠ -20,6 +20,10 ＠＠
;; along with XEmacs; see the file COPYING. If not, write to the
;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
;; Boston, MA 02111-1307, USA.
+
+(defgroup advocacy nil
+ "blatant XEmacs self promotion"
+:group 'games)
;;;###autoload
(defvar xemacs-praise-sound-file "im_so_happy"
Index: xemacs-packages/misc-games/blackbox.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/blackbox.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 blackbox.el
--- xemacs-packages/misc-games/blackbox.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/blackbox.el 2005/01/31 20:56:05
＠＠ -70,6 +70,10 ＠＠
;;; Code:
+(defgroup blackbox nil
+ "blackbox game in Emacs Lisp"
+:group 'games)
+
(defvar blackbox-mode-map nil "")
(if blackbox-mode-map
Index: xemacs-packages/misc-games/conx.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/conx.el,v
retrieving revision 1.2
diff -u -p -r1.2 conx.el
--- xemacs-packages/misc-games/conx.el 1999/11/27 20:49:55 1.2
+++ xemacs-packages/misc-games/conx.el 2005/01/31 20:56:05
＠＠ -70,6 +70,10 ＠＠
;;; o It could stand to be faster...
;;; Code:
+(defgroup conx nil
+ "Yet another dissociater"
+:group 'games)
+
(defconst conx-version "1.6, 6-may-94.")
(defvar conx-bounce 10) ; 1/x
Index: xemacs-packages/misc-games/decipher.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/decipher.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 decipher.el
--- xemacs-packages/misc-games/decipher.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/decipher.el 2005/01/31 20:56:05
＠＠ -93,6 +93,10 ＠＠
(eval-when-compile
(require 'cl))
+(defgroup decipher nil
+ "Cryptanalyze monoalphabetic substitution ciphers"
+:group 'games)
+
(defvar decipher-force-uppercase t
"*Non-nil means to convert ciphertext to uppercase.
Nil means the case of the ciphertext is preserved.
Index: xemacs-packages/misc-games/dissociate.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/dissociate.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 dissociate.el
--- xemacs-packages/misc-games/dissociate.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/dissociate.el 2005/01/31 20:56:05
＠＠ -31,6 +31,10 ＠＠
;;; Code:
+(defgroup dissociate nil
+ "scramble text amusingly for Emacs."
+:group 'games)
+
;;;###autoload
(defun dissociated-press (&optional arg)
"Dissociate the text of the current buffer.
Index: xemacs-packages/misc-games/doctor.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/doctor.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 doctor.el
--- xemacs-packages/misc-games/doctor.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/doctor.el 2005/01/31 20:56:06
＠＠ -44,6 +44,10 ＠＠
;;; Code:
+(defgroup doctor nil
+ "psychological help for frustrated users."
+:group 'games)
+
(defun doctor-cadr (x) (car (cdr x)))
(defun doctor-caddr (x) (car (cdr (cdr x))))
(defun doctor-cddr (x) (cdr (cdr x)))
＠＠ -1637,5 +1641,17 ＠＠ Hack on previous word, setting global va
(interactive)
(insert "Mein fuehrer!!\n")
(doctor-read-print))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'doctor
+ "Not documented."
+:group 'games
+:commands
+ '(["%_Psychoanalyst" doctor]))
+)
+
+
;;; doctor.el ends here
Index: xemacs-packages/misc-games/dunnet.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/dunnet.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 dunnet.el
--- xemacs-packages/misc-games/dunnet.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/dunnet.el 2005/01/31 20:56:07
＠＠ -36,6 +36,10 ＠＠
;;; be writable by all.
+(defgroup dunnet nil
+ "Text adventure for Emacs"
+:group 'games)
+
(defvar dun-log-file "/usr/local/dunnet.score"
"Name of file to store score information for dunnet.")
＠＠ -3336,5 +3340,15 ＠＠ File not found")))
(dun-mprinc "\n")
(setq dun-batch-mode t)
(dun-batch-loop))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'dunnet
+ "Not documented."
+:group 'games
+:commands
+ '(["Dunnet (Adventure)" dunnet]))
+)
;;; dunnet.el ends here
Index: xemacs-packages/misc-games/flame.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/flame.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 flame.el
--- xemacs-packages/misc-games/flame.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/flame.el 2005/01/31 20:56:07
＠＠ -40,6 +40,11 ＠＠
;;;
;;; Code:
+
+(defgroup flame nil
+ "Automated insults"
+:group 'games)
+
(random t)
(defvar sentence
＠＠ -338,5 +343,15 ＠＠
(flame2 (if (= (random 2) 0) 2 1))
(sit-for 0)
(doctor-ret-or-read 1)))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'flame
+ "Not documented."
+:group 'games
+:commands
+ '(["Random Flames" flame]))
+)
;;; flame.el ends here
Index: xemacs-packages/misc-games/gomoku.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/gomoku.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 gomoku.el
--- xemacs-packages/misc-games/gomoku.el 1998/01/14 06:30:53 1.1.1.1
+++ xemacs-packages/misc-games/gomoku.el 2005/01/31 20:56:07
＠＠ -74,6 +74,9 ＠＠
;;; Code:
+(defgroup gomoku nil
+ "Gomoku game between you and Emacs"
+:group 'games)
;;;
;;; GOMOKU MODE AND KEYMAP.
;;;
Index: xemacs-packages/misc-games/hanoi.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/hanoi.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 hanoi.el
--- xemacs-packages/misc-games/hanoi.el 1998/01/14 06:30:54 1.1.1.1
+++ xemacs-packages/misc-games/hanoi.el 2005/01/31 20:56:07
＠＠ -58,6 +58,10 ＠＠
;;; Code:
+(defgroup hanoi nil
+ "towers of hanoi in GNUmacs"
+:group 'games)
+
;;;
;;; hanoi-topos - direct cursor addressing
;;;
＠＠ -243,6 +247,16 ＠＠
(progn
(backward-char (/ (+ len 1) 2))
(delete-char 1) (insert ?\|))))))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'hanoi
+ "Not documented."
+:group 'games
+:commands
+ '(["Towers of Hanoi" hanoi]))
+)
(provide 'hanoi)
Index: xemacs-packages/misc-games/life.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/life.el,v
retrieving revision 1.2
diff -u -p -r1.2 life.el
--- xemacs-packages/misc-games/life.el 2000/11/18 04:27:37 1.2
+++ xemacs-packages/misc-games/life.el 2005/01/31 20:56:08
＠＠ -32,6 +32,10 ＠＠
;;; Code:
+(defgroup life nil
+ "John Horton Conway's `Life' game for GNU Emacs"
+:group 'games)
+
(defconst life-patterns
[("＠＠＠" " ＠＠" "＠＠＠")
("＠＠＠ ＠＠＠" "＠＠ ＠＠ " "＠＠＠ ＠＠＠")
＠＠ -283,6 +287,16 ＠＠ generations (this defaults to 1)."
;; XEmacs change
(define-error 'life-extinct "All life has perished" 'quit)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'life
+ "Not documented."
+:group 'games
+:commands
+ '(["Game of Life" life]))
+)
(provide 'life)
Index: xemacs-packages/misc-games/morse.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/morse.el,v
retrieving revision 1.2
diff -u -p -r1.2 morse.el
--- xemacs-packages/misc-games/morse.el 2002/11/18 22:11:45 1.2
+++ xemacs-packages/misc-games/morse.el 2005/01/31 20:56:08
＠＠ -24,10 +24,14 ＠＠
;;; Commentary:
-;; Converts text to Morse code and back with M-x morese-region and
+;; Converts text to Morse code and back with M-x morse-region and
;; M-x unmorse-region (though Morse code is no longer official :-().
;;; Code:
+
+(defgroup morse nil
+ "convert text to morse code and back"
+:group 'games)
(defvar morse-code '(("a" . ".-")
("b" . "-...")
Index: xemacs-packages/misc-games/mpuz.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/mpuz.el,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 mpuz.el
--- xemacs-packages/misc-games/mpuz.el 1998/01/14 06:30:54 1.1.1.1
+++ xemacs-packages/misc-games/mpuz.el 2005/01/31 20:56:08
＠＠ -33,6 +33,10 ＠＠
;;; Code:
+(defgroup mpuz nil
+ "multiplication puzzle for XEmacs"
+:group 'games)
+
(random t) ; randomize
(defvar mpuz-silent nil
＠＠ -441,5 +445,15 ＠＠ You may abort a game by typing \\<mpuz-m
(or (mpuz-digit-solved-p digit)
(setq list (cons digit list))))
(mapcar 'mpuz-correct-guess list)))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'mpuz
+ "Not documented."
+:group 'games
+:commands
+ '(["Multiplication Puzzle" mpuz]))
+)
;;; mpuz.el ends here
Index: xemacs-packages/misc-games/rot13.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/rot13.el,v
retrieving revision 1.2
diff -u -p -r1.2 rot13.el
--- xemacs-packages/misc-games/rot13.el 2000/09/25 03:16:51 1.2
+++ xemacs-packages/misc-games/rot13.el 2005/01/31 20:56:08
＠＠ -35,6 +35,10 ＠＠
;;; Code:
+(defgroup rot13 nil
+ "display a buffer in rot13."
+:group 'games)
+
(defvar rot13-display-table
(let ((i -1)
(a (char-to-int ?a))
Index: xemacs-packages/misc-games/studly.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/misc-games/studly.el,v
retrieving revision 1.2
diff -u -p -r1.2 studly.el
--- xemacs-packages/misc-games/studly.el 2003/09/20 20:26:31 1.2
+++ xemacs-packages/misc-games/studly.el 2005/01/31 20:56:08
＠＠ -32,6 +32,10 ＠＠
;;; Code:
+(defgroup studly nil
+ "StudlyCaps (tm)(r)(c)(xxx)"
+:group 'games)
+
(defun studlify-region (begin end)
"Studlify-case the region"
(interactive "*r")
cvs server: Diffing xemacs-packages/mmm-mode
cvs server: Diffing xemacs-packages/net-utils
cvs server: Diffing xemacs-packages/ocaml
cvs server: Diffing xemacs-packages/oo-browser
cvs server: Diffing xemacs-packages/oo-browser/man
cvs server: Diffing xemacs-packages/oo-browser/man/im
cvs server: Diffing xemacs-packages/oo-browser/tree-w32
cvs server: Diffing xemacs-packages/oo-browser/tree-x
cvs server: Diffing xemacs-packages/os-utils
Index: xemacs-packages/os-utils/jka-compr.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/os-utils/jka-compr.el,v
retrieving revision 1.9
diff -u -p -r1.9 jka-compr.el
--- xemacs-packages/os-utils/jka-compr.el 2003/05/30 12:55:07 1.9
+++ xemacs-packages/os-utils/jka-compr.el 2005/01/31 20:56:08
＠＠ -983,6 +983,22 ＠＠ The return value is the entry in `file-n
;; No no no no!
;(jka-compr-install)
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'jka-compr
+ "This package implements low-level support for reading, writing,
+and loading compressed files. It hooks into the low-level file
+I/O functions (including write-region and insert-file-contents) so
+that they automatically compress or uncompress a file if the file
+appears to need it (based on the extension of the file name).
+Packages like Rmail, VM, GNUS, and Info should be able to work
+with compressed files without modification."
+:short-doc "Transparently handle compressed files"
+:group 'files
+:enable #'jka-compr-install
+:disable #'jka-compr-uninstall)
+)
(provide 'jka-compr)
cvs server: Diffing xemacs-packages/pc
Index: xemacs-packages/pcl-cvs/pcl-cvs-defs.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/pcl-cvs/pcl-cvs-defs.el,v
retrieving revision 2.4
diff -u -p -r2.4 pcl-cvs-defs.el
--- xemacs-packages/pcl-cvs/pcl-cvs-defs.el 2002/06/24 22:06:46 2.4
+++ xemacs-packages/pcl-cvs/pcl-cvs-defs.el 2005/01/31 20:56:09
＠＠ -466,7 +466,10 ＠＠ It is expected to call the function.")
;;;###autoload
(if (progn (condition-case () (require 'easymenu) (error nil))
- (fboundp 'easy-menu-add-item))
+ (and (fboundp 'easy-menu-add-item)
+ ;; Packages under XEmacs 21.5+ may not directly modify the
+ ;; menubar.
+ (not (fboundp 'define-behavior-group))))
(easy-menu-add-item nil '("tools")
'("PCL CVS"
["Update Directory" cvs-update t]
Index: xemacs-packages/pcl-cvs/pcl-cvs.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/pcl-cvs/pcl-cvs.el,v
retrieving revision 2.41
diff -u -p -r2.41 pcl-cvs.el
--- xemacs-packages/pcl-cvs/pcl-cvs.el 2002/01/26 22:27:31 2.41
+++ xemacs-packages/pcl-cvs/pcl-cvs.el 2005/01/31 20:56:10
＠＠ -2112,6 +2112,20 ＠＠ Anything else means to do it only if the
(when (eq major-mode 'cvs-mode)
(setq ad-return-value list-buffers-directory)))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'pcl-cvs
+ "Not documented."
+:short-doc "PCL CVS"
+:group 'files
+:commands
+ '(["Update Directory" cvs-update t]
+ ["Examine Directory" cvs-examine t]
+ ["Status Directory" cvs-status t]
+ ["Checkout Module" cvs-checkout t]))
+)
+
;; provide this package
(run-hooks 'pcl-cvs-load-hook)
cvs server: Diffing xemacs-packages/pcomplete
cvs server: Diffing xemacs-packages/perl-modes
cvs server: Diffing xemacs-packages/pgg
cvs server: Diffing xemacs-packages/prog-modes
cvs server: Diffing xemacs-packages/ps-print
Index: xemacs-packages/ps-print/ps-mule.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/ps-print/ps-mule.el,v
retrieving revision 1.4
diff -u -p -r1.4 ps-mule.el
--- xemacs-packages/ps-print/ps-mule.el 2002/07/30 12:40:40 1.4
+++ xemacs-packages/ps-print/ps-mule.el 2005/01/31 20:56:10
＠＠ -298,6 +298,7 ＠＠ font family.
See also the variable `ps-font-info-database'.")
+;;;###custom-define
(defconst ps-mule-font-info-database-latin
'((latin-iso8859-1
(normal nil nil iso-8859-1)))
cvs server: Diffing xemacs-packages/ps-print/etc
cvs server: Diffing xemacs-packages/ps-print/etc/ps-print
cvs server: Diffing xemacs-packages/ps-print-nomule
cvs server: Diffing xemacs-packages/psgml
Index: xemacs-packages/psgml/psgml-html.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/psgml/psgml-html.el,v
retrieving revision 1.18
diff -u -p -r1.18 psgml-html.el
--- xemacs-packages/psgml/psgml-html.el 2003/08/29 08:19:58 1.18
+++ xemacs-packages/psgml/psgml-html.el 2005/01/31 20:56:12
＠＠ -265,24 +265,8 ＠＠ More specifically:
sgml-omittag t
sgml-shorttag t)
- ;; font-lock setup for various emacsen: XEmacs, Emacs 19.29+, Emacs <19.29.
- ;; By Ulrik Dickow <dickow(a)nbi.dk>. (Last update: 05-Sep-1995).
- (cond (running-xemacs ; XEmacs/Lucid
- (put major-mode 'font-lock-keywords-case-fold-search t))
- ;; XEmacs (19.13, at least) guesses the rest correctly.
- ;; If any older XEmacsen don't, then tell me.
- ;;
- ((string-lessp "19.28.89" emacs-version) ; Emacs 19.29 and later
- (make-local-variable 'font-lock-defaults)
- (setq font-lock-defaults '(html-font-lock-keywords t t)))
- ;;
- (t ; Emacs 19.28 and older
- (make-local-variable 'font-lock-keywords-case-fold-search)
- (make-local-variable 'font-lock-keywords)
- (make-local-variable 'font-lock-no-comments)
- (setq font-lock-keywords-case-fold-search t)
- (setq font-lock-keywords html-font-lock-keywords)
- (setq font-lock-no-comments t)))
+ (make-local-variable 'font-lock-defaults)
+ (setq font-lock-defaults '(html-font-lock-keywords t t))
(if html-helper-do-write-file-hooks
(add-hook 'local-write-file-hooks 'html-helper-update-timestamp))
cvs server: Diffing xemacs-packages/psgml-dtds
cvs server: Diffing xemacs-packages/psgml-dtds/etc
cvs server: Diffing xemacs-packages/psgml-dtds/etc/ISO_8879-1986
cvs server: Diffing xemacs-packages/psgml-dtds/etc/ISO_8879-1986/entities
cvs server: Diffing xemacs-packages/psgml-dtds/etc/cdtd
cvs server: Diffing xemacs-packages/python-modes
cvs server: Diffing xemacs-packages/reftex
cvs server: Diffing xemacs-packages/riece
cvs server: Diffing xemacs-packages/riece/doc
cvs server: Diffing xemacs-packages/riece/lisp
cvs server: Diffing xemacs-packages/riece/lisp/test
cvs server: Diffing xemacs-packages/rmail
cvs server: Diffing xemacs-packages/rmail/etc
cvs server: Diffing xemacs-packages/ruby-modes
cvs server: Diffing xemacs-packages/sasl
cvs server: Diffing xemacs-packages/scheme
cvs server: Diffing xemacs-packages/semantic
cvs server: Diffing xemacs-packages/sgml
cvs server: Diffing xemacs-packages/sh-script
cvs server: Diffing xemacs-packages/sieve
cvs server: Diffing xemacs-packages/slider
cvs server: Diffing xemacs-packages/slider/etc
cvs server: Diffing xemacs-packages/sml-mode
cvs server: Diffing xemacs-packages/sounds-au
cvs server: Diffing xemacs-packages/sounds-wav
cvs server: Diffing xemacs-packages/speedbar
cvs server: Diffing xemacs-packages/strokes
cvs server: Diffing xemacs-packages/supercite
cvs server: Diffing xemacs-packages/texinfo
cvs server: Diffing xemacs-packages/text-modes
Index: xemacs-packages/text-modes/filladapt.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/text-modes/filladapt.el,v
retrieving revision 1.5
diff -u -p -r1.5 filladapt.el
--- xemacs-packages/text-modes/filladapt.el 2002/10/29 12:27:58 1.5
+++ xemacs-packages/text-modes/filladapt.el 2005/01/31 20:56:13
＠＠ -986,3 +986,41 ＠＠ See filladapt-adapt."
(while ei-list
(filladapt-set-extent-endpoints (car ei-list) 1 1)
(setq ei-list (cdr ei-list))))))))))
+
+
+;; XEmacs:
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'filladapt
+ "These functions enhance the default behavior of Emacs' Auto Fill
+mode and the commands `fill-paragraph', `lisp-fill-paragraph',
+`fill-region-as-paragraph' and `fill-region'.
+
+The chief improvement is that the beginning of a line to be
+filled is examined and, based on information gathered, an
+appropriate value for fill-prefix is constructed. Also the
+boundaries of the current paragraph are located. This occurs
+only if the fill prefix is not already non-nil.
+
+The net result of this is that blurbs of text that are offset
+from left margin by asterisks, dashes, and/or spaces, numbered
+examples, included text from USENET news articles, etc. are
+generally filled correctly with no fuss."
+:short-doc "Adaptive (smart) filling"
+:require 'filladapt
+:group 'editing
+:enable #'(lambda ()
+ (setq-default filladapt-mode t)
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (unless filladapt-mode
+ (filladapt-mode 1))))
+ (buffer-list)))
+:disable #'(lambda ()
+ (setq-default filladapt-mode nil)
+ (mapc #'(lambda (buffer)
+ (with-current-buffer buffer
+ (when filladapt-mode
+ (filladapt-mode -1))))
+ (buffer-list))))
+)
\ No newline at end of file
Index: xemacs-packages/text-modes/flyspell.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/text-modes/flyspell.el,v
retrieving revision 1.14
diff -u -p -r1.14 flyspell.el
--- xemacs-packages/text-modes/flyspell.el 2003/01/03 21:15:12 1.14
+++ xemacs-packages/text-modes/flyspell.el 2005/01/31 20:56:13
＠＠ -57,6 +57,7 ＠＠
;*---------------------------------------------------------------------*/
;* Which emacs are we currently running */
;*---------------------------------------------------------------------*/
+;;;###custom-define
(defvar flyspell-emacs
(cond
((string-match "XEmacs" emacs-version)
cvs server: Diffing xemacs-packages/textools
cvs server: Diffing xemacs-packages/time
cvs server: Diffing xemacs-packages/time/etc
cvs server: Diffing xemacs-packages/tm
cvs server: Diffing xemacs-packages/tm/lib-src
cvs server: Diffing xemacs-packages/tm/texi
cvs server: Diffing xemacs-packages/tooltalk
cvs server: Diffing xemacs-packages/tpu
cvs server: Diffing xemacs-packages/tramp
cvs server: Diffing xemacs-packages/tramp/lisp
cvs server: Diffing xemacs-packages/tramp/test
cvs server: Diffing xemacs-packages/tramp/texi
cvs server: Diffing xemacs-packages/vc
Index: xemacs-packages/vc/vc-hooks.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/vc/vc-hooks.el,v
retrieving revision 1.12
diff -u -p -r1.12 vc-hooks.el
--- xemacs-packages/vc/vc-hooks.el 2003/10/27 15:09:55 1.12
+++ xemacs-packages/vc/vc-hooks.el 2005/01/31 20:56:14
＠＠ -1241,6 +1241,7 ＠＠ Returns t if checkout was successful, ni
;(put 'vc-toggle-read-only 'menu-enable 'vc-mode)
;(put 'vc-register 'menu-enable '(and buffer-file-name (not vc-mode)))
+;;;###autoload
(defconst vc-menu
'("VC"
:filter vc-menu-filter
＠＠ -1318,6 +1319,7 ＠＠ Returns t if checkout was successful, ni
result))
(and (featurep 'menubar)
+ (not (fboundp 'define-behavior-group))
current-menubar
(car (find-menu-item current-menubar '("Tools")))
(add-submenu '("Tools") vc-menu "Compare")
＠＠ -1338,7 +1340,8 ＠＠ Returns t if checkout was successful, ni
;;;###autoload
(and (featurep 'menubar)
(featurep 'xemacs)
- (not (or (featurep 'vc-hooks) (featurep 'infodock)))
+ (not (or (featurep 'vc-hooks) (featurep 'infodock)
+ (fboundp 'define-behavior-group)))
current-menubar
(car (find-menu-item current-menubar '("Tools")))
(add-submenu '("Tools")
＠＠ -1346,5 +1349,15 ＠＠ Returns t if checkout was successful, ni
["Load VC" vc-load-vc-hooks t])
"Compare"))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'vc
+ "Not documented."
+:short-doc "VC"
+:group 'files
+:enable 'vc-load-vc-hooks
+:commands (cdr vc-menu))
+)
;;; vc-hooks.el ends here
cvs server: Diffing xemacs-packages/vc-cc
cvs server: Diffing xemacs-packages/vhdl
cvs server: Diffing xemacs-packages/view-process
cvs server: Diffing xemacs-packages/viper
cvs server: Diffing xemacs-packages/viper/etc
cvs server: Diffing xemacs-packages/vm
Index: xemacs-packages/vm/vm-version.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/vm/vm-version.el,v
retrieving revision 1.28
diff -u -p -r1.28 vm-version.el
--- xemacs-packages/vm/vm-version.el 2003/09/03 00:43:45 1.28
+++ xemacs-packages/vm/vm-version.el 2005/01/31 20:56:14
＠＠ -106,5 +106,15 ＠＠
(image-type-available-p type)
(or (featurep type) (eq type 'xbm))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'vm
+ "Not documented."
+:group 'internet
+:commands
+ '(["Read Mail (VM)..." vm]))
+)
+
(provide 'vm)
(provide 'vm-version)
cvs server: Diffing xemacs-packages/vm/etc
cvs server: Diffing xemacs-packages/w3
Index: xemacs-packages/w3/lisp/w3.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/w3/lisp/w3.el,v
retrieving revision 1.7
diff -u -p -r1.7 w3.el
--- xemacs-packages/w3/lisp/w3.el 2000/10/06 09:15:23 1.7
+++ xemacs-packages/w3/lisp/w3.el 2005/01/31 20:56:17
＠＠ -2591,6 +2591,17 ＠＠ Current keymap is:
(run-hooks 'w3-mode-hook)
(widget-setup))))
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'w3
+ "Not documented."
+:group 'internet
+:commands
+ '(["Browse the Web" w3]))
+)
+
(require 'mm)
(require 'url)
(require 'w3-parse)
cvs server: Diffing xemacs-packages/w3/texi
cvs server: Diffing xemacs-packages/x-symbol
cvs server: Diffing xemacs-packages/x-symbol/etc
cvs server: Diffing xemacs-packages/x-symbol/fonts
cvs server: Diffing xemacs-packages/x-symbol/lisp
cvs server: Diffing xemacs-packages/x-symbol/man
cvs server: Diffing xemacs-packages/x-symbol/origfonts
cvs server: Diffing xemacs-packages/xemacs-base
Index: xemacs-packages/xemacs-base/compile.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/xemacs-base/compile.el,v
retrieving revision 1.32
diff -u -p -r1.32 compile.el
--- xemacs-packages/xemacs-base/compile.el 2004/06/28 20:19:43 1.32
+++ xemacs-packages/xemacs-base/compile.el 2005/01/31 20:56:19
＠＠ -2345,6 +2345,170 ＠＠ See variable `compilation-parse-errors-f
(substring dir (length parent-expanded)))))
dir)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'grep
+ "See the Emacs user's manual."
+:short-doc "%_Grep"
+:group nil
+:commands
+ '(:filter
+ (lambda (menu)
+ (if (or (not (boundp 'grep-history)) (null grep-history))
+ menu
+ (let ((items
+ (submenu-generate-accelerator-spec
+ (mapcar #'(lambda (label-value)
+ (vector (first label-value)
+ (list 'grep (second label-value))))
+ (Menubar-items-truncate-history
+ grep-history 10 50)))))
+ (append menu '("---") items))))
+ ["%_Grep..." grep :active (fboundp 'grep)]
+ ["%_Kill Grep" kill-compilation
+:active (and (fboundp 'kill-compilation)
+ (fboundp 'compilation-find-buffer)
+ (let ((buffer (condition-case nil
+ (compilation-find-buffer)
+ (error nil))))
+ (and buffer (get-buffer-process buffer))))]
+ "---"
+ ["Grep %_All Files in Current Directory..."
+ grep-all-files-in-current-directory
+:active (fboundp 'grep-all-files-in-current-directory)]
+ ["Grep All Files in Current Directory %_Recursively..."
+ grep-all-files-in-current-directory-and-below
+:active (fboundp 'grep-all-files-in-current-directory-and-below)]
+ "---"
+ ["Grep %_C and C Header Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.[chCH]"
+ ; i wanted to also use *.cc and *.hh.
+ ; see long comment below under Perl.
+ )
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep C Hea%_der Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.[hH]"
+ ; i wanted to also use *.hh.
+ ; see long comment below under Perl.
+ )
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep %_E-Lisp Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.el")
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep %_Perl Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.pl"
+ ; i wanted to use this:
+ ; " *.pl *.pm *.am"
+ ; but grep complains if it can't
+ ; match anything in a glob, and
+ ; that screws other things up.
+ ; perhaps we need to first scan
+ ; each separate glob in the directory
+ ; to see if there are any files in
+ ; that glob, and if not, omit it.
+ )
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ ["Grep %_HTML Files in Current Directory..."
+ (progn
+ (require 'compile)
+ (let ((grep-command
+ (cons (concat grep-command " *.*htm*")
+ (length grep-command))))
+ (call-interactively 'grep)))
+:active (fboundp 'grep)]
+ "---"
+ ["%_Next Match" next-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["Pre%_vious Match" previous-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["%_First Match" first-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["G%_oto Match" compile-goto-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ "---"
+ ["%_Set Grep Command..."
+ (progn
+ (require 'compile)
+ (customize-set-variable
+ 'grep-command
+ (read-shell-command "Default Grep Command: " grep-command)))
+:active (fboundp 'grep)
+ ]
+ ))
+)
+
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'compile
+ "See the Emacs user's manual."
+:short-doc "%_Compile"
+:group nil
+:commands
+ '(:filter
+ (lambda (menu)
+ (if (or (not (boundp 'compile-history)) (null compile-history))
+ menu
+ (let ((items
+ (submenu-generate-accelerator-spec
+ (mapcar #'(lambda (label-value)
+ (vector (first label-value)
+ (list 'compile (second label-value))))
+ (Menubar-items-truncate-history
+ compile-history 10 50)))))
+ (append menu '("---") items))))
+ ["%_Compile..." compile :active (fboundp 'compile)]
+ ["%_Repeat Compilation" recompile :active (fboundp 'recompile)]
+ ["%_Kill Compilation" kill-compilation
+:active (and (fboundp 'kill-compilation)
+ (fboundp 'compilation-find-buffer)
+ (let ((buffer (condition-case nil
+ (compilation-find-buffer)
+ (error nil))))
+ (and buffer (get-buffer-process buffer))))]
+ "---"
+ ["%_Next Error" next-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["Pre%_vious Error" previous-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["%_First Error" first-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ["G%_oto Error" compile-goto-error
+:active (and (fboundp 'compilation-errors-exist-p)
+ (compilation-errors-exist-p))]
+ ))
+)
+
+
(provide 'compile)
;;; compile.el ends here
Index: xemacs-packages/xemacs-base/shell.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/xemacs-base/shell.el,v
retrieving revision 1.12
diff -u -p -r1.12 shell.el
--- xemacs-packages/xemacs-base/shell.el 2004/11/23 04:10:54 1.12
+++ xemacs-packages/xemacs-base/shell.el 2005/01/31 20:56:19
＠＠ -1192,6 +1192,22 ＠＠ Returns t if successful."
(message "Directory item: %d" index)
t))))))
+;; XEmacs
+;;;###autoload
+(if (fboundp 'define-behavior-group)
+(define-behavior 'shell
+ "See the Emacs user's manual."
+:short-doc "Shell"
+:group 'processes
+:commands
+ '(["%_Shell" shell
+:active (fboundp 'shell)]
+ ["S%_hell Command..." shell-command
+:active (fboundp 'shell-command)]
+ ["Shell Command on %_Region..." shell-command-on-region
+:active (and (fboundp 'shell-command-on-region) (region-exists-p))]))
+)
+
(provide 'shell)
;;; shell.el ends here
cvs server: Diffing xemacs-packages/xemacs-base/etc
cvs server: Diffing xemacs-packages/xemacs-devel
- 1 participants
- 0 comments
[COMMIT] Use plain set-extent-property in lazy-shot
19 years, 10 months
Ben Wing
Ben Wing
NOTE: This patch has been committed.
xemacs-packages/edit-utils/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* lazy-shot.el (lazy-shot-install-extent):
Use plain set-extent-property as
set-extent-initial-redisplay-function is going away.
packages source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: xemacs-packages/edit-utils/lazy-shot.el
Index: xemacs-packages/edit-utils/lazy-shot.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/lazy-shot.el,v
retrieving revision 1.6
diff -u -p -r1.6 lazy-shot.el
--- xemacs-packages/edit-utils/lazy-shot.el 2002/11/28 18:55:08 1.6
+++ xemacs-packages/edit-utils/lazy-shot.el 2005/01/31 21:35:19
＠＠ -232,8 +232,8 ＠＠ stealth locking functions."
"Make an extent that will lazy-shot if it is displayed."
(let ((extent (make-extent spos epos buffer)))
(when extent
- (set-extent-initial-redisplay-function extent
- 'lazy-shot-redisplay-function))
+ (set-extent-property extent 'initial-redisplay-function
+ 'lazy-shot-redisplay-function))
extent))
- 1 participants
- 0 comments
[COMMIT] Add item to pending-del list
19 years, 10 months
Ben Wing
Ben Wing
NOTE: This patch has been committed.
xemacs-packages/pc/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* pending-del.el:
Add skeleton-pair-insert-maybe.
packages source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: xemacs-packages/pc/pending-del.el
Index: xemacs-packages/pc/pending-del.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/pc/pending-del.el,v
retrieving revision 1.10
diff -u -p -r1.10 pending-del.el
--- xemacs-packages/pc/pending-del.el 2002/05/23 04:41:58 1.10
+++ xemacs-packages/pc/pending-del.el 2005/01/31 21:29:55
＠＠ -134,6 +134,8 ＠＠ Set this to nil if you don't want a mode
cperl-electric-lbrace
cperl-electric-brace
+ skeleton-pair-insert-maybe
+
electric-c-sharp-sign
electric-c-terminator
electric-c-semi
- 1 participants
- 0 comments
[COMMIT] Update jobs links, win32 pointer
19 years, 10 months
Ben Wing
Ben Wing
NOTE: This patch has been committed.
Develop/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* jobs.content: Change links to point to People/ directory.
Download/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* optLibs.content: Point to win32/ directory rather than FTP site.
Document non-providing of SSH/CVS/patch.
xemacsweb source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: FAQ/xemacs-faq.html FAQ/xemacs-faq.html Download/optLibs.content Develop/jobs.content
cvs server: Diffing .
cvs server: Diffing About
cvs server: Diffing About/Screenshots
cvs server: Diffing Architecting-XEmacs
cvs server: Diffing Debug
cvs server: Diffing Develop
Index: Develop/jobs.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/jobs.content,v
retrieving revision 1.29
diff -u -p -r1.29 jobs.content
--- Develop/jobs.content 2005/01/31 02:37:58 1.29
+++ Develop/jobs.content 2005/01/31 20:46:22
＠＠ -8,10 +8,8 ＠＠ Ben Wing; html-ized by jsja
<h1>XEmacs Jobs</h1>
<h4>Current version: 30 January 2005<br />
- Maintainer: Ben Wing
- <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a><br />
- Maintainer: Stephen Turnbull
- <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></h4>
+ Maintainer: <a href="../People/ben">Ben Wing</a>,
+ <a href="../People/stephen">Stephen Turnbull</a></h4>
<h1>XEmacs Review Board Members</h1>
＠＠ -31,27 +29,28 ＠＠ Ben Wing; html-ized by jsja
<!-- APA: sorted by firstname (use M-x sort-lines) -->
<ul>
- <li>Adrian Aichner <a href="mailto:adrian＠xemacs.org"><adrian＠xemacs.org></a></li>
- <li>Andy Piper <a href="mailto:andy＠xemacs.org"><andy＠xemacs.org></a></li>
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
- <li>Didier Verna <a href="mailto:didier＠xemacs.org"><didier＠xemacs.org></a></li>
- <li>Jerry James <a href="mailto:james＠xemacs.org"><james＠xemacs.org></a></li>
- <li>Michael Sperber <a href="mailto:mike＠xemacs.org"><mike＠xemacs.org></a></li>
- <li>Norbert Koch <a href="mailto:viteno＠xemacs.org"><viteno＠xemacs.org></a></li>
- <li>Stephen Turnbull <a href="mailto:turnbull＠sk.tsukuba.ac.jp"><stephen＠xemacs.org></a></li>
- <li>Ville Skyttä <a href="mailto:scop＠xemacs.org"><scop＠xemacs.org></a></li>
- <li>Vin Shelton <a href="mailto:acs＠xemacs.org"><acs＠xemacs.org></a></li>
- <li>Gunnar Evermann (<em>inactive</em>) <a href="mailto:gunnar＠xemacs.org"><gunnar＠xemacs.org></a></li>
- <li>Hrvoje Niksic (<em>inactive</em>) <a href="mailto:hrvoje＠xemacs.org"><hrvoje＠xemacs.org></a></li>
- <li>Jan Vroonhof (<em>inactive</em>) <a href="mailto:jan＠xemacs.org"><jan＠xemacs.org></a></li>
- <li>Jareth Hein (<em>inactive</em>) <a href="mailto:jareth＠xemacs.org"><jareth＠xemacs.org></a></li>
- <li>Jonathan Harris (<em>inactive</em>) <a href="mailto:jonathan＠xemacs.org"><jonathan＠xemacs.org></a></li>
- <li>Kirill 'Big K' Katsnelson (<em>inactive</em>) <a href="mailto:kirill＠xemacs.org"><kirill＠xemacs.org></a></li>
- <li>Martin Buchholz (<em>inactive</em>)<a href="mailto:martin＠xemacs.org"><martin＠xemacs.org></a></li>
- <li>Olivier Galibert (<em>inactive</em>) <a href="mailto:galibert＠xemacs.org"><galibert＠xemacs.org></a></li>
- <li>Steve Baur (<em>inactive</em>)<a href="mailto:steve＠xemacs.org"><steve＠xemacs.org></a></li>
- <li>William M. Perry (<em>inactive</em>) <a href="mailto:wmperry＠xemacs.org"><wmperry＠xemacs.org></a></li>
- <li>Yoshiki Hayashi (<em>inactive</em>) <a href="mailto:yoshiki＠xemacs.org"><yoshiki＠xemacs.org></a></li>
+ <li><a href="../People/adrian">Adrian Aichner</a></li>
+ <li><a href="../People/andy">Andy Piper</a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
+ <li><a href="../People/didier">Didier Verna</a></li>
+ <li><a href="../People/james">Jerry James</a></li>
+ <li><a href="../People/malcolmp">Malcolm Purvis</a></li>
+ <li><a href="../People/mike">Michael Sperber</a></li>
+ <li><a href="../People/viteno">Norbert Koch</a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
+ <li><a href="../People/scop">Ville Skyttä</a></li>
+ <li><a href="../People/acs">Vin Shelton</a></li>
+ <li><a href="../People/gunnar">Gunnar Evermann (<em>inactive</em>)</a></li>
+ <li><a href="../People/hrvoje">Hrvoje Niksic (<em>inactive</em>)</a></li>
+ <li><a href="../People/jan">Jan Vroonhof (<em>inactive</em>)</a></li>
+ <li><a href="../People/jareth">Jareth Hein (<em>inactive</em>)</a></li>
+ <li><a href="../People/jonathan">Jonathan Harris (<em>inactive</em>)</a></li>
+ <li><a href="../People/kirill">Kirill 'Big K' Katsnelson (<em>inactive</em>)</a></li>
+ <li><a href="../People/martin">Martin Buchholz (<em>inactive</em></a></li>
+ <li><a href="../People/galibert">Olivier Galibert (<em>inactive</em>)</a></li>
+ <li><a href="../People/steve">Steve Baur (<em>inactive</em></a></li>
+ <li><a href="../People/wmperry">William M. Perry (<em>inactive</em>)</a></li>
+ <li><a href="../People/yoshiki">Yoshiki Hayashi (<em>inactive</em>)</a></li>
</ul>
＠＠ -75,7 +74,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1"></td>
＠＠ -88,7 +87,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Vin Shelton <a href="mailto:acs＠xemacs.org"><acs＠xemacs.org></a></li>
+ <li><a href="../People/acs">Vin Shelton</a></li>
</ul>
</td>
<td rowspan="1" colspan="1"></td>
＠＠ -100,7 +99,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
<td rowspan="1" colspan="1"></td>
＠＠ -112,7 +111,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
<td rowspan="1" colspan="1"></td>
＠＠ -124,15 +123,15 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Adrian Aichner <a href="mailto:adrian＠xemacs.org"><adrian＠xemacs.org></a></li>
+ <li><a href="../People/adrian">Adrian Aichner</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
- <li>John S Jacobs Anderson (<em>inactive</em>) <a href="mailto:jacobs＠xemacs.org"><jacobs＠xemacs.org></a></li>
- <li>Marcus Thiessel (<em>inactive</em>) <a href="mailto:marcus＠xemacs.org"><marcus＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
+ <li><a href="../People/jacobs">John S Jacobs Anderson (<em>inactive</em>)</a></li>
+ <li><a href="../People/marcus">Marcus Thiessel (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -143,13 +142,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull (<em>pro tem</em>) <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull (<em>pro tem</em>)</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
</tr>
＠＠ -158,13 +157,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Norbert Koch <a href="mailto:viteno＠xemacs.org"><viteno＠xemacs.org></a></li>
+ <li><a href="../People/viteno">Norbert Koch</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ville Skyttä <a href="mailto:scop＠xemacs.org"><scop＠xemacs.org></a></li>
+ <li><a href="../People/scop">Ville Skyttä</a></li>
</ul>
</td>
</tr>
＠＠ -177,7 +176,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
</tr>
＠＠ -188,13 +187,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull (<em>pro tem</em>) <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull (<em>pro tem</em>)</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Michael Sperber <a href="mailto:mike＠xemacs.org"><mike＠xemacs.org></a></li>
+ <li><a href="../People/mike">Michael Sperber</a></li>
</ul>
</td>
</tr>
＠＠ -205,13 +204,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull (<em>pro tem</em>) <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull (<em>pro tem</em>)</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Adrian Aichner <a href="mailto:adrian＠xemacs.org"><adrian＠xemacs.org></a></li>
+ <li><a href="../People/adrian">Adrian Aichner</a></li>
</ul>
</td>
</tr>
＠＠ -224,8 +223,8 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Fabrice Popineau <a href="mailto:fabrice＠xemacs.org"><fabrice＠xemacs.org></a></li>
- <li>Jason Mastaler (<em>inactive</em>) <a href="mailto:jason＠xemacs.org"><jason＠xemacs.org></a></li>
+ <li><a href="../People/fabrice">Fabrice Popineau</a></li>
+ <li><a href="../People/jason">Jason Mastaler (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -236,13 +235,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
</tr>
＠＠ -267,8 +266,8 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
</tr>
＠＠ -283,13 +282,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
</tr>
＠＠ -300,7 +299,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
</tr>
＠＠ -310,7 +309,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
</tr>
＠＠ -319,7 +318,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
＠＠ -332,7 +331,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Hrvoje Niksic (<em>inactive</em>) <a href="mailto:hrvoje＠xemacs.org"><hrvoje＠xemacs.org></a></li>
+ <li><a href="../People/hrvoje">Hrvoje Niksic (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -341,7 +340,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
＠＠ -352,7 +351,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
＠＠ -373,14 +372,14 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
- <li>Jerry James <a href="mailto:james＠xemacs.org"><james＠xemacs.org></a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
+ <li><a href="../People/james">Jerry James</a></li>
</ul>
</td>
</tr>
＠＠ -389,14 +388,14 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Aidan Kehoe <a href="mailto:aidan＠xemacs.org"><aidan＠xemacs.org></a></li>
+ <li><a href="../People/aidan">Aidan Kehoe</a></li>
</ul>
</td>
</tr>
＠＠ -405,13 +404,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Andy Piper (<em>inactive</em>) <a href="mailto:andy＠xemacs.org"><andy＠xemacs.org></a></li>
+ <li><a href="../People/andy">Andy Piper (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -422,7 +421,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
</tr>
＠＠ -431,16 +430,16 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Adrian Aichner <a href="mailto:adrian＠xemacs.org"><adrian＠xemacs.org></a></li>
- <li>Andy Piper (<em>inactive</em>) <a href="mailto:andy＠xemacs.org"><andy＠xemacs.org></a></li>
- <li>Jonathan Harris (<em>inactive</em>) <a href="mailto:jonathan＠xemacs.org"><jonathan＠xemacs.org></a></li>
- <li>Kirill 'Big K' Katsnelson (<em>inactive</em>) <a href="mailto:kkm＠dtmx.com"><kkm＠dtmx.com></a></li>
+ <li><a href="../People/adrian">Adrian Aichner</a></li>
+ <li><a href="../People/andy">Andy Piper (<em>inactive</em>)</a></li>
+ <li><a href="../People/jonathan">Jonathan Harris (<em>inactive</em>)</a></li>
+ <li><a href="../People/kkm">Kirill 'Big K' Katsnelson (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -449,13 +448,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Malcolm Purvis <a href="mailto:malcolmp＠xemacs.org"><malcolmp＠xemacs.org></a></li>
+ <li><a href="../People/malcolmp">Malcolm Purvis</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>William Perry (<em>inactive</em>) <a href="mailto:wmperry＠xemacs.org"><wmperry＠xemacs.org></a></li>
+ <li><a href="../People/wmperry">William Perry (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -464,13 +463,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Olivier Galibert (<em>inactive</em>) <a href="mailto:galibert＠xemacs.org"><galibert＠xemacs.org></a></li>
+ <li><a href="../People/galibert">Olivier Galibert (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -479,14 +478,14 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Michael Sperber <a href="mailto:mike＠xemacs.org"><mike＠xemacs.org></a></li>
- <li>Marcus Crestani <a href="mailto:crestani＠xemacs.org"><crestani＠xemacs.org></a></li>
+ <li><a href="../People/mike">Michael Sperber</a></li>
+ <li><a href="../People/crestani">Marcus Crestani</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
</tr>
＠＠ -495,7 +494,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Michael Sperber <a href="mailto:mike＠xemacs.org"><mike＠xemacs.org></a></li>
+ <li><a href="../People/mike">Michael Sperber</a></li>
</ul>
</td>
<td rowspan="1" colspan="1"></td>
＠＠ -505,7 +504,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Jerry James <a href="mailto:james＠xemacs.org"><james＠xemacs.org></a></li>
+ <li><a href="../People/james">Jerry James</a></li>
</ul>
</td>
<td rowspan="1" colspan="1"></td>
＠＠ -517,9 +516,9 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Jan Vroonhof (<em>inactive</em>) <a href="mailto:jan＠xemacs.org"><jan＠xemacs.org></a></li>
- <li>Hrvoje Niksic (<em>inactive</em>) <a href="mailto:hrvoje＠xemacs.org"><hrvoje＠xemacs.org></a></li>
- <li>Didier Verna <a href="mailto:didier＠xemacs.org"><didier＠xemacs.org></a></li>
+ <li><a href="../People/jan">Jan Vroonhof (<em>inactive</em>)</a></li>
+ <li><a href="../People/hrvoje">Hrvoje Niksic (<em>inactive</em>)</a></li>
+ <li><a href="../People/didier">Didier Verna</a></li>
</ul>
</td>
</tr>
＠＠ -530,10 +529,10 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
- <li>Jerry James <a href="mailto:james＠xemacs.org"><james＠xemacs.org></a></li>
- <li>Malcolm Purvis <a href="mailto:malcolmp＠xemacs.org"><malcolmp＠xemacs.org></a></li>
- <li>Stephen Turnbull <a href="mailto:stephen＠xemacs.org"><stephen＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
+ <li><a href="../People/james">Jerry James</a></li>
+ <li><a href="../People/malcolmp">Malcolm Purvis</a></li>
+ <li><a href="../People/stephen">Stephen Turnbull</a></li>
</ul>
</td>
</tr>
＠＠ -542,13 +541,13 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Ben Wing <a href="mailto:ben＠xemacs.org"><ben＠xemacs.org></a></li>
+ <li><a href="../People/ben">Ben Wing</a></li>
</ul>
</td>
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Andy Piper (<em>inactive</em>) <a href="mailto:andy＠xemacs.org"><andy＠xemacs.org></a></li>
+ <li><a href="../People/andy">Andy Piper (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -557,7 +556,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Jerry James <a href="mailto:james＠xemacs.org"><james＠xemacs.org></a></li>
+ <li><a href="../People/james">Jerry James</a></li>
</ul>
</td>
<td rowspan="1" colspan="1"></td>
＠＠ -568,7 +567,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>William Perry (<em>inactive</em>) <a href="mailto:wmperry＠xemacs.org"><wmperry＠xemacs.org></a></li>
+ <li><a href="../People/wmperry">William Perry (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -578,7 +577,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Oscar Figueiredo (<em>inactive</em>) <a href="mailto:oscar＠xemacs.org"><oscar＠xemacs.org></a></li>
+ <li><a href="../People/oscar">Oscar Figueiredo (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
＠＠ -588,7 +587,7 ＠＠ Ben Wing; html-ized by jsja
<td rowspan="1" colspan="1">
<ul>
<!-- one of (dd dt) -->
- <li>Steve Baur (<em>inactive</em>)<a href="mailto:steve＠xemacs.org"><steve＠xemacs.org></a></li>
+ <li><a href="../People/steve">Steve Baur (<em>inactive</em>)</a></li>
</ul>
</td>
</tr>
cvs server: Diffing Documentation
cvs server: Diffing Documentation/21.5
cvs server: Diffing Documentation/21.5/html
cvs server: Diffing Documentation/packages
cvs server: Diffing Documentation/packages/html
cvs server: Diffing Download
Index: Download/optLibs.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Download/optLibs.content,v
retrieving revision 1.33
diff -u -p -r1.33 optLibs.content
--- Download/optLibs.content 2005/01/24 02:40:59 1.33
+++ Download/optLibs.content 2005/01/31 20:46:23
＠＠ -30,11 +30,10 ＠＠ Ben Wing
<h1><a name="section-1.">Windows Binaries:</a></h1>
<p>
- The <a href="http://ftp.xemacs.org/pub/xemacs/aux/win32">win32</a>
+ The <a href="win32">win32</a>
directory contains binaries for common graphics libraries needed for
building XEmacs and for zlib, needed to support the PNG library.
- We recommend that you run
- <a href="http://ftp.xemacs.org/pub/xemacs/aux/win32/optional-libs.exe">
+ We recommend that you run <a href="win32/optional-libs.exe">
optional-libs.exe</a>, a self-extracting executable, which will
install pre-built binaries for all of the optional graphics libraries
needed by XEmacs, in the correct hierarchy as expected by XEmacs.
＠＠ -43,8 +42,11 ＠＠ Ben Wing
<tt>c:\src</tt>).</p>
<p>
- We no longer provide binaries for ssh or CVS. Just download Cygwin if you
- want them.</p>
+ We no longer provide binaries for CVS, SSH or patch. If you want these,
+ just install <a href="http://www.cygwin.com">Cygwin</a>, which provides
+ versions of these and all other common Unix utilities, has an easy
+ install program, and is frequently updated.
+ </p>
<h1><a name="section-2.">Cygwin, XFree86 Binaries:</a></h1>
<p>
cvs server: Diffing Download/win32
cvs server: Diffing FAQ
- 1 participants
- 0 comments
[COMMIT] Fix photos
19 years, 10 months
Ben Wing
Ben Wing
NOTE: This patch has been committed.
People/ChangeLog addition:
2005-01-31 Ben Wing <ben(a)xemacs.org>
* photos/{chr.png,chrm.png,james.png,jamesm.png}:
Fix.
* christian.nybo/index.content/:
Add photo.
xemacsweb source patch:
Diff command: bash -ci "cvs-diff --show-c-function -no-changelog "
Files affected: People/photos/jamesm.png People/photos/james.png People/christian.nybo/index.content
cvs server: I know nothing about People
cvs server: Diffing People
cvs server: Diffing People/adrian.aichner
cvs server: Diffing People/aidan.kehoe
cvs server: Diffing People/alastair.houghton
cvs server: Diffing People/alexey.mahotkin
cvs server: Diffing People/andreas.jaeger
cvs server: Diffing People/andrew.cosgriff
cvs server: Diffing People/andy.piper
cvs server: Diffing People/anthony.rossini
cvs server: Diffing People/barry.warsaw
cvs server: Diffing People/ben.wing
cvs server: Diffing People/bjorn.torkelsson
cvs server: Diffing People/bob.weiner
cvs server: Diffing People/carsten.dominik
cvs server: Diffing People/charles.waldman
cvs server: Diffing People/christian.nybo
Index: People/christian.nybo/index.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/People/christian.nybo/index.content,v
retrieving revision 1.1
diff -u -p -r1.1 index.content
--- People/christian.nybo/index.content 31 Jan 2005 02:43:10 -0000 1.1
+++ People/christian.nybo/index.content 31 Jan 2005 20:30:29 -0000
＠＠ -4,6 +4,8 ＠＠ XEmacs Home Page for Christian Nybo
Ben Wing, based on generic home page
%main%
+ <img src="../photos/chr.png" alt="(photo)" />
+
<h1>XEmacs Home Page for Christian Nybo</h1>
<p>
cvs server: Diffing People/chuck.thompson
cvs server: Diffing People/colin.rafferty
cvs server: Diffing People/craig.lanning
cvs server: Diffing People/daiki.ueno
cvs server: Diffing People/damon.lipparelli
cvs server: Diffing People/dan.holmsand
cvs server: Diffing People/daniel.pittman
cvs server: Diffing People/darrell.kindred
cvs server: Diffing People/darryl.okahata
cvs server: Diffing People/david.hobley
cvs server: Diffing People/david.moore
cvs server: Diffing People/didier.verna
cvs server: Diffing People/eduardo.pelegri-llopart
cvs server: Diffing People/eric.benson
cvs server: Diffing People/eric.knauel
cvs server: Diffing People/eric.ludlam
cvs server: Diffing People/evgeny.zajcev
cvs server: Diffing People/fabrice.popineau
cvs server: Diffing People/francisco.vides
cvs server: Diffing People/gary.foster
cvs server: Diffing People/glynn.clements
cvs server: Diffing People/greg.klanderman
cvs server: Diffing People/gunnar.evermann
cvs server: Diffing People/hans.muller
cvs server: Diffing People/harlan.sexton
cvs server: Diffing People/heiko.muenkel
cvs server: Diffing People/hisashi.miyashita
cvs server: Diffing People/hrvoje.niksic
cvs server: Diffing People/i.n.golubev
cvs server: Diffing People/jake.colman
cvs server: Diffing People/james.potts
cvs server: Diffing People/jamie.zawinski
cvs server: Diffing People/jan.rychter
cvs server: Diffing People/jan.vroonhof
cvs server: Diffing People/jareth.hein
cvs server: Diffing People/jari.aalto
cvs server: Diffing People/jason.mastaler
cvs server: Diffing People/jeff.miller
cvs server: Diffing People/jens-ulrik.petersen
cvs server: Diffing People/jens.lautenbacher
cvs server: Diffing People/jerry.james
cvs server: Diffing People/jesper.pedersen
cvs server: Diffing People/john.jacobs-anderson
cvs server: Diffing People/john.paul.wallington
cvs server: Diffing People/john.rose
cvs server: Diffing People/john.wiegley
cvs server: Diffing People/jonathan.harris
cvs server: Diffing People/jonathan.stigelman
cvs server: Diffing People/karl.hegbloom
cvs server: Diffing People/kazuo.oishi
cvs server: Diffing People/kazuyuki.ienaga
cvs server: Diffing People/kenny.stevens
cvs server: Diffing People/kevin.oberman
cvs server: Diffing People/kirill.katsnelson
cvs server: Diffing People/klaus.berndl
cvs server: Diffing People/kyle.jones
cvs server: Diffing People/lars.ingebrigtsen
cvs server: Diffing People/linda.arai
cvs server: Diffing People/malcolm.purvis
cvs server: Diffing People/marc.paquette
cvs server: Diffing People/marcus.crestani
cvs server: Diffing People/marcus.thiessel
cvs server: Diffing People/markus.kaltenbach
cvs server: Diffing People/martin.buchholz
cvs server: Diffing People/martin.schwenke
cvs server: Diffing People/martin.stjernholm
cvs server: Diffing People/mats.lidell
cvs server: Diffing People/matt.simmons
cvs server: Diffing People/matt.tucker
cvs server: Diffing People/matthieu.devin
cvs server: Diffing People/michael.albinus
cvs server: Diffing People/michael.cook
cvs server: Diffing People/michael.diers
cvs server: Diffing People/michael.kifer
cvs server: Diffing People/mike.alexander
cvs server: Diffing People/mike.sperber
cvs server: Diffing People/mike.woolley
cvs server: Diffing People/nick.pakoulin
cvs server: Diffing People/norbert.koch
cvs server: Diffing People/oliver.graf
cvs server: Diffing People/olivier.galibert
cvs server: Diffing People/oscar.figueiredo
cvs server: Diffing People/ovidiu.predescu
cvs server: Diffing People/paul.kinnucan
cvs server: Diffing People/per.abrahamsen
cvs server: Diffing People/peter.brown
cvs server: Diffing People/peter.osterlund
cvs server: Diffing People/peter.pezaris
cvs server: Diffing People/photos
cvs server: People/photos/chr.png is a new entry, no comparison available
cvs server: People/photos/chrm.png is a new entry, no comparison available
Index: People/photos/james.png
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/People/photos/james.png,v
retrieving revision 1.1
diff -u -p -r1.1 james.png
Binary files /tmp/cvseiaa6k and james.png differ
Index: People/photos/jamesm.png
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/People/photos/jamesm.png,v
retrieving revision 1.1
diff -u -p -r1.1 jamesm.png
Binary files /tmp/cvsfiaa6k and jamesm.png differ
cvs server: Diffing People/raymond.toy
cvs server: Diffing People/rebecca.ore
cvs server: Diffing People/richard.mlynarik
cvs server: Diffing People/richard.reingruber
cvs server: Diffing People/rick.campbell
cvs server: Diffing People/robin.socha
cvs server: Diffing People/rodney.sparapani
cvs server: Diffing People/sandy.wambold
cvs server: Diffing People/sean.maclennan
cvs server: Diffing People/simon.josefsson
cvs server: Diffing People/stefanie.teufel
cvs server: Diffing People/stephen.turnbull
cvs server: Diffing People/steve.baur
cvs server: Diffing People/steve.youngs
cvs server: Diffing People/stig.bjorlykke
cvs server: Diffing People/sven.grundmann
cvs server: Diffing People/tomohiko.morioka
cvs server: Diffing People/tomonori.ikeyama
cvs server: Diffing People/trey.abelew
cvs server: Diffing People/uwe.brauer
cvs server: Diffing People/ville.skytta
cvs server: Diffing People/vin.shelton
cvs server: Diffing People/vladimir.ivanovic
cvs server: Diffing People/will.deakin
cvs server: Diffing People/william.perry
cvs server: Diffing People/yoshiki.hayashi
- 1 participants
- 0 comments
[PATCH] Fix photos
19 years, 10 months
Ben Wing
Ben Wing
Added chr's photos back again.
- 1 participants
- 0 comments