Without seeing the actual change, I'm a little concerned that
this change might have an impact on GNU Emacs and subsequent
effort on our part to make them compatible. If your changes
were limited to the mh-xemacs.el file, they would have a 100%
chance of survival with 0% effort on our part. Can you try to do that?
Then please send mh-e-devel a patch with the actual MH-E changes.
Thanks for the heads-up.
This change would not break anything. Patch follows. If you think this is
better in one of the other files, you're welcome to put it there. Perhaps
you could modify the patch to fill in the documentation. An example of how
such documentation should look is shown in the second patch below.
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
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.
;;;; ------------------------------------------------------------