* FAQ 1-5:: I sometimes read references to No Gnus and Oort Gnus,
what are those?
* FAQ 1-6:: Which version of Emacs do I need?
-* FAQ 1-7:: How do I run Gnus on both Emacs and XEmacs?
@end menu
@node FAQ 1-1
@subsubheading Answer
-Gnus is released independent from releases of Emacs and XEmacs.
-Therefore, the version bundled with Emacs or the version in XEmacs's
-package system might not be up to date (e.g., Gnus 5.9 bundled with Emacs
-21 is outdated).
+Gnus is released independent from releases of Emacs. Therefore, the
+version bundled with Emacs might not be up to date (e.g., Gnus 5.9
+bundled with Emacs 21 is outdated).
You can get the latest released version of Gnus from
@uref{http://www.gnus.org/dist/gnus.tar.gz}
or from
and use the batch-file make.bat included in the tarball to install
Gnus.) If you don't want to (or aren't allowed to) install Gnus
system-wide, you can install it in your home directory and add the
-following lines to your ~/.xemacs/init.el or ~/.emacs:
+following lines to your ~/.emacs:
@example
(add-to-list 'load-path "/path/to/gnus/lisp")
-(if (featurep 'xemacs)
- (add-to-list 'Info-directory-list "/path/to/gnus/texi/")
- (add-to-list 'Info-default-directory-list "/path/to/gnus/texi/"))
+(add-to-list 'Info-default-directory-list "/path/to/gnus/texi/")
@end example
@noindent
@subsubheading Answer
Gnus 5.13 requires an Emacs version that is greater than or equal
-to Emacs 23.1 or XEmacs 21.1, although there are some features that
+to Emacs 23.1, although there are some features that
only work on Emacs 24.
-@node FAQ 1-7
-@subsubheading Question 1.7
-
-How do I run Gnus on both Emacs and XEmacs?
-
-@subsubheading Answer
-
-You can't use the same copy of Gnus in both as the Lisp
-files are byte-compiled to a format which is different
-depending on which Emacs did the compilation. Get one copy
-of Gnus for Emacs and one for XEmacs.
-
@node FAQ 2 - Startup / Group buffer
@subsection Startup / Group buffer
@uref{http://www.kdstevens.com/~stevens/ispell-page.html, ispell.el}
and for on-the-fly spell-checking
@uref{http://www-sop.inria.fr/members/Manuel.Serrano/flyspell/flyspell.html, flyspell.el}.
-Ispell.el is shipped with Emacs and available through the XEmacs package system,
-flyspell.el is shipped with Emacs and part of XEmacs text-modes package which is
-available through the package system, so there should be no need to install them
+Ispell.el is shipped with Emacs,
+flyspell.el is shipped with Emacs, so there should be no need to install them
manually.
Ispell.el assumes you use ispell, if you choose aspell say
details.
However, what you really want is the Insidious Big Brother
-Database bbdb. Get it through the XEmacs package system or from
+Database bbdb. Get it from
@uref{http://bbdb.sourceforge.net/, bbdb's homepage}.
Now place the following in @file{~/.gnus.el}, to activate bbdb for Gnus:
(let ((archive-name
(format
"nnml:1.%s"
- (if (featurep 'xemacs)
- (replace-in-string gnus-newsgroup-name "^.*:" "")
- (replace-regexp-in-string "^.*:" "" gnus-newsgroup-name)))))
+ (replace-in-string gnus-newsgroup-name "^.*:" ""))))
(gnus-summary-copy-article n archive-name)))
@end example
@noindent
to functions like "get message", "get Headers" etc.
@item Emacs
-When the term Emacs is used in this FAQ, it means either GNU
-Emacs or XEmacs.
+When the term Emacs is used in this FAQ, it means GNU
+Emacs.
@item Message
In this FAQ message means either a mail or a posting to a
* Undo:: Some actions can be undone.
* Predicate Specifiers:: Specifying predicates.
* Moderation:: What to do if you're a moderator.
-* Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
+* Image Enhancements:: Modern versions of Emacs can display images.
* Fuzzy Matching:: What's the big fuzz?
* Thwarting Email Spam:: Simple ways to avoid unsolicited commercial email.
* Spam Package:: A package for filtering and processing spam.
Appendices
-* XEmacs:: Requirements for installing under XEmacs.
* History:: How Gnus got where it is today.
* On Writing Manuals:: Why this is not a beginner's guide.
* Terminology:: We use really difficult, like, words here.
* Ranges:: A handy format for storing mucho numbers.
* Group Info:: The group info format.
* Extended Interactive:: Symbolic prefixes and stuff.
-* Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
* Various File Formats:: Formats of files that Gnus use.
Back End Interface
@item nnmail-pathname-coding-system
@vindex nnmail-pathname-coding-system
The value of this variable should be a coding system or @code{nil}. The
-default is @code{nil} in Emacs, or is the aliasee of the coding system
-named @code{file-name} (a certain coding system of which an alias is
-@code{file-name}) in XEmacs.
+default is @code{nil} in Emacs.
The @code{nnml} back end, the @code{nnrss} back end, the agent, and
the cache use non-@acronym{ASCII} group names in those files and
@code{file-name-coding-system} which specifies the coding system used
when encoding and decoding those file names and directory names.
-In XEmacs (with the @code{mule} feature), @code{file-name-coding-system}
-is the only means to specify the coding system used to encode and decode
-file names. On the other hand, Emacs uses the value of
-@code{default-file-name-coding-system} if @code{file-name-coding-system}
-is @code{nil} or it is bound to the value of
-@code{nnmail-pathname-coding-system} which is @code{nil}.
+Emacs uses the value of @code{default-file-name-coding-system} if
+@code{file-name-coding-system} is @code{nil} or it is bound to the
+value of @code{nnmail-pathname-coding-system} which is @code{nil}.
-Normally the value of @code{default-file-name-coding-system} in Emacs or
-@code{nnmail-pathname-coding-system} in XEmacs is initialized according
-to the locale, so you will need to do nothing if the value is suitable
-to encode and decode non-@acronym{ASCII} group names.
+Normally the value of @code{default-file-name-coding-system} is
+initialized according to the locale, so you will need to do nothing if
+the value is suitable to encode and decode non-@acronym{ASCII} group
+names.
The value of this variable (or @code{default-file-name-coding-system})
does not necessarily need to be the same value that is determined by
This variable controls which information should be exposed in the
User-Agent header. It can be a list of symbols or a string. Valid
-symbols are @code{gnus} (show Gnus version) and @code{emacs} (show Emacs
-version). In addition to the Emacs version, you can add @code{codename}
-(show (S)XEmacs codename) or either @code{config} (show system
-configuration) or @code{type} (show system type). If you set it to a
-string, be sure to use a valid format, see RFC 2616.
+symbols are @code{gnus} (show Gnus version) and @code{emacs} (show
+Emacs version). In addition to the Emacs version, you can add
+@code{config} (show system configuration) or @code{type} (show system
+type). If you set it to a string, be sure to use a valid format, see
+RFC 2616.
@end table
@vindex nnrss-file-coding-system
The coding system used when reading and writing the @code{nnrss} groups
data files. The default is the value of
-@code{mm-universal-coding-system} (which defaults to @code{emacs-mule}
-in Emacs or @code{escape-quoted} in XEmacs).
+@code{mm-universal-coding-system} (which defaults to @code{emacs-mule}).
@item nnrss-ignore-article-fields
@vindex nnrss-ignore-article-fields
(max gnus-score-decay-constant
(* (abs score)
gnus-score-decay-scale)))))))
- (if (and (featurep 'xemacs)
- ;; XEmacs's floor can handle only the floating point
- ;; number below the half of the maximum integer.
- (> (abs n) (lsh -1 -2)))
- (string-to-number
- (car (split-string (number-to-string n) "\\.")))
- (floor n))))
+ (floor n)))
@end lisp
@vindex gnus-score-decay-scale
* Predicate Specifiers:: Specifying predicates.
* Moderation:: What to do if you're a moderator.
* Fetching a Group:: Starting Gnus just to read a group.
-* Image Enhancements:: Modern versions of Emacs/XEmacs can display images.
+* Image Enhancements:: Modern versions of Emacs can display images.
* Fuzzy Matching:: What's the big fuzz?
* Thwarting Email Spam:: Simple ways to avoid unsolicited commercial email.
* Spam Package:: A package for filtering and processing spam.
variables should be either strings or symbols naming functions that
return a string. When the mouse passes over text with this property
set, a balloon window will appear and display the string. Please
-refer to @ref{Tooltips, ,Tooltips, emacs, The Emacs Manual},
-(in Emacs) or the doc string of @code{balloon-help-mode} (in
-XEmacs) for more information on this. (For technical reasons, the
-guillemets have been approximated as @samp{<<} and @samp{>>} in this
-paragraph.)
+refer to @ref{Tooltips, ,Tooltips, emacs, The Emacs Manual} for more
+information on this. (For technical reasons, the guillemets have been
+approximated as @samp{<<} and @samp{>>} in this paragraph.)
Here's an alternative recipe for the group buffer:
@vindex gnus-use-correct-string-widths
To help fix this, you can set @code{gnus-use-correct-string-widths} to
@code{t}. This makes buffer generation slower, but the results will be
-prettier. The default value under XEmacs is @code{t} but @code{nil}
-for Emacs.
+prettier. The default value is @code{nil}.
@node Window Layout
instead of the normal @code{1.0} top-level spec, each additional split
should have a frame parameter alist as the size spec.
@xref{Frame Parameters, , Frame Parameters, elisp, The GNU Emacs Lisp
-Reference Manual}. Under XEmacs, a frame property list will be
-accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
-is such a plist.
+Reference Manual}.
The list of all possible keys for @code{gnus-buffer-configuration} can
be found in its default value.
@node Image Enhancements
@section Image Enhancements
-XEmacs, as well as Emacs 21@footnote{Emacs 21 on MS Windows doesn't
-support images, Emacs 22 does.} and up, are able to display pictures and
+Emacs 21@footnote{Emacs 21 on MS Windows doesn't
+support images, Emacs 22 does.} and up are able to display pictures and
stuff, so Gnus has taken advantage of that.
@menu
@c @anchor{X-Face}
Viewing an @code{X-Face} header either requires an Emacs that has
-@samp{compface} support (which most XEmacs versions have), or that you
+@samp{compface} support, or that you
have suitable conversion or display programs installed. If your Emacs
has image support the default action is to display the face before the
@code{From} header. If there's no native @code{X-Face} support, Gnus
will try to convert the @code{X-Face} header using external programs
-from the @code{pbmplus} package and friends, see below. For XEmacs it's
-faster if XEmacs has been compiled with @code{X-Face} support. The
+from the @code{pbmplus} package and friends, see below. The
default action under Emacs without image support is to fork off the
@code{display} program.
@vindex gnus-face-properties-alist
Alist of image types and properties applied to Face (@pxref{Face}) and
X-Face images. The default value is @code{((pbm . (:face gnus-x-face))
-(png . nil))} for Emacs or @code{((xface . (:face gnus-x-face)))} for
-XEmacs. Here are examples:
+(png . nil))}. Here are examples:
@lisp
;; Specify the altitude of Face and X-Face images in the From header.
@xref{Image Descriptors,,, elisp, The Emacs Lisp Reference Manual},
for the valid properties for various image types. Currently,
@code{pbm} is used for X-Face images and @code{png} is used for Face
-images in Emacs. Only the @code{:face} property is effective on the
-@code{xface} image type in XEmacs if it is built with the
-@samp{libcompface} library.
+images in Emacs.
@end table
If you use posting styles, you can use an @code{x-face-file} entry in
Viewing a @code{Face} header requires an Emacs that is able to display
PNG images.
-@c Maybe add this:
-@c (if (featurep 'xemacs)
-@c (featurep 'png)
-@c (image-type-available-p 'png))
Gnus provides a few convenience functions and variables to allow
easier insertion of Face headers in outgoing messages.
controlled by @code{gnus-verbose} and @code{gnus-verbose-backends} and
are issued. The default value is @code{nil} which means never to add
timestamp. If it is @code{log}, add timestamps to only the messages
-that go into the @file{*Messages*} buffer (in XEmacs, it is the
-@w{@file{ *Message-Log*}} buffer). If it is neither @code{nil} nor
+that go into the @file{*Messages*} buffer. If it is neither @code{nil} nor
@code{log}, add timestamps not only to log messages but also to the ones
displayed in the echo area.
@chapter Appendices
@menu
-* XEmacs:: Requirements for installing under XEmacs.
* History:: How Gnus got where it is today.
* On Writing Manuals:: Why this is not a beginner's guide.
* Terminology:: We use really difficult, like, words here.
@end menu
-@node XEmacs
-@section XEmacs
-@cindex XEmacs
-@cindex installing under XEmacs
-
-XEmacs is distributed as a collection of packages. You should install
-whatever packages the Gnus XEmacs package requires. The current
-requirements are @samp{gnus}, @samp{mail-lib}, @samp{xemacs-base},
-@samp{eterm}, @samp{sh-script}, @samp{net-utils}, @samp{os-utils},
-@samp{dired}, @samp{mh-e}, @samp{sieve}, @samp{ps-print},
-@samp{pgg}, @samp{mailcrypt}, @samp{ecrypto}, and @samp{sasl}.
-
-
@node History
@section History
everywhere I could imagine it being useful. By doing so, I'm inviting
every one of you to explore and invent.
-May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs} and
-@kbd{C-u 100 M-x all-hail-xemacs}.
+May Gnus never be complete. @kbd{C-u 100 M-x all-hail-emacs}.
@node Compatibility
@node Emacsen
@subsection Emacsen
@cindex Emacsen
-@cindex XEmacs
@cindex Mule
@cindex Emacs
@item
Emacs 23.1 and up.
-@item
-XEmacs 21.4 and up.
-
@end itemize
This Gnus version will absolutely not work on any Emacsen older than
that. Not reliably, at least. Older versions of Gnus may work on older
Emacs versions. Particularly, Gnus 5.10.8 should also work on Emacs
-20.7 and XEmacs 21.1.
+20.7.
@c No-merge comment: The paragraph added in v5-10 here must not be
@c synced here!
Gnus can make use of GroupLens predictions.
@item
-Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
+Picons (personal icons) can be displayed (@pxref{Picons}).
@item
A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
shadows manually or remove them using @code{make
remove-installed-shadows}.
-@item
-New @file{make.bat} for compiling and installing Gnus under MS Windows
-
-Use @file{make.bat} if you want to install Gnus under MS Windows, the
-first argument to the batch-program should be the directory where
-@file{xemacs.exe} respectively @file{emacs.exe} is located, if you want
-to install Gnus after compiling it, give @file{make.bat} @code{/copy} as
-the second parameter.
-
-@file{make.bat} has been rewritten from scratch, it now features
-automatic recognition of XEmacs and Emacs, generates
-@file{gnus-load.el}, checks if errors occur while compilation and
-generation of info files and reports them at the end of the build
-process. It now uses @code{makeinfo} if it is available and falls
-back to @file{infohack.el} otherwise. @file{make.bat} should now
-install all files which are necessary to run Gnus and be generally a
-complete replacement for the @code{configure; make; make install}
-cycle used under Unix systems.
-
-The new @file{make.bat} makes @file{make-x.bat} and @file{xemacs.mak}
-superfluous, so they have been removed.
-
@item
@file{~/News/overview/} not used.
The tool bars have been updated to use GNOME icons in Group, Summary and
Message mode. You can also customize the tool bars: @kbd{M-x
customize-apropos @key{RET} -tool-bar$} should get you started. This is a new
-feature in Gnus 5.10.10. (Only for Emacs, not in XEmacs.)
+feature in Gnus 5.10.10.
@item The tool bar icons are now (de)activated correctly
in the group buffer, see the variable @code{gnus-group-update-tool-bar}.
@itemize @bullet
@item Emacs 22 and up
-@item XEmacs 21.4
-@item XEmacs 21.5
-@item SXEmacs
@end itemize
@item The tool bar has been updated to use GNOME icons.
You can also customize the tool bars: @kbd{M-x customize-apropos @key{RET}
--tool-bar$} should get you started. (Only for Emacs, not in XEmacs.)
+-tool-bar$} should get you started.
@c FIXME: Document this in the manual
@item The tool bar icons are now (de)activated correctly
Its default value depends on your Emacs version.
@c FIXME: Document this in the manual
-@item You can change the location of XEmacs's toolbars in Gnus buffers.
-See @code{gnus-use-toolbar} and @code{message-use-toolbar}.
-
@end itemize
@item Miscellaneous changes
* Ranges:: A handy format for storing mucho numbers.
* Group Info:: The group info format.
* Extended Interactive:: Symbolic prefixes and stuff.
-* Emacs/XEmacs Code:: Gnus can be run under all modern Emacsen.
* Various File Formats:: Formats of files that Gnus use.
@end menu
@end table
-@node Emacs/XEmacs Code
-@subsection Emacs/XEmacs Code
-@cindex XEmacs
-@cindex Emacsen
-
-While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
-platforms must be the primary one. I chose Emacs. Not because I don't
-like XEmacs or Mule, but because it comes first alphabetically.
-
-This means that Gnus will byte-compile under Emacs with nary a warning,
-while XEmacs will pump out gigabytes of warnings while byte-compiling.
-As I use byte-compilation warnings to help me root out trivial errors in
-Gnus, that's very useful.
-
-I've also consistently used Emacs function interfaces, but have used
-Gnusey aliases for the functions. To take an example: Emacs defines a
-@code{run-at-time} function while XEmacs defines a @code{start-itimer}
-function. I then define a function called @code{gnus-run-at-time} that
-takes the same parameters as the Emacs @code{run-at-time}. When running
-Gnus under Emacs, the former function is just an alias for the latter.
-However, when running under XEmacs, the former is an alias for the
-following function:
-
-@lisp
-(defun gnus-xmas-run-at-time (time repeat function &rest args)
- (start-itimer
- "gnus-run-at-time"
- `(lambda ()
- (,function ,@@args))
- time repeat))
-@end lisp
-
-This sort of thing has been done for bunches of functions. Gnus does
-not redefine any native Emacs functions while running under XEmacs---it
-does this @code{defalias} thing with Gnus equivalents instead. Cleaner
-all over.
-
-In the cases where the XEmacs function interface was obviously cleaner,
-I used it instead. For example @code{gnus-region-active-p} is an alias
-for @code{region-active-p} in XEmacs, whereas in Emacs it is a function.
-
-Of course, I could have chosen XEmacs as my native platform and done
-mapping functions the other way around. But I didn't. The performance
-hit these indirections impose on Gnus under XEmacs should be slight.
-
-
@node Various File Formats
@subsection Various File Formats
projects / emacs.git / commitdiff