@c download the faq} in info format, and install it in @file{<XEmacs
@c library directory>/info/}. For example in
@c @file{/usr/local/lib/xemacs-21.4/info/}.
-@c
+@c
@c @end itemize
-@c
+@c
@c @end html
-@c
+@c
@c @end ifset
-@c
+@c
@c end ifset points to CANONICAL
@menu
Sparcworks, EOS, and WorkShop:
* Q4.4.1:: What is SPARCworks, EOS, and WorkShop
-* Q4.4.2:: How do I start the Sun Workshop support in SXEmacs?
Energize:
* Q4.5.1:: What is/was Energize?
Here is a list of some of the reasons why we think you might
consider using it:
-
+
@itemize @bullet
@item
It looks nicer.
-
+
@item
The XEmacs and SXEmacs maintainers, especially the SXEmacs
maintainers, are generally more receptive to suggestions than the GNU
@item
Marginal annotations.
-@item
-ToolTalk support.
-
@item
XEmacs can be used as an Xt widget, and can be embedded within another
application.
@item
Better APIs (and performance) for attaching fonts, colors, and other
properties to text.
-
+
@c @c does not apply anymore
@c @item
@c The ability to embed arbitrary graphics in a buffer.
@unnumberedsec Q1.1.1: What is the FAQ editorial policy?
The FAQ is actively maintained and modified regularly. All links should
-be up to date.
+be up to date.
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.
@c @html
@c <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
@c @end html
-@c
-@c
+@c
+@c
@c @item @email{stephen@@xemacs.org, Stephen Turnbull}
-@c
-@c
+@c
+@c
@c @item @email{ben@@xemacs.org, Ben Wing}
@c @html
@c <br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
@c @end html
-@c
-@c
+@c
+@c
@c @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
-@c
+@c
@c @html
@c <br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
@c @end html
-@c
+@c
@c @end itemize
-@c
+@c
@c The developers responsible for older releases were:
-@c
+@c
@c @itemize @bullet
@c @item @email{steve@@xemacs.org, Steve Baur}
-@c
+@c
@c @html
@c <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
@c @end html
-@c
+@c
@c @item @email{cthomp@@xemacs.org, Chuck Thompson}
@c @html
@c <br><img src="cthomp.jpeg" alt="Portrait of Chuck Thompson"><br>
@c @end html
-@c
+@c
@c @item @email{jwz@@jwz.org, Jamie Zawinski}
@c @html
@c <br><img src="jwz.gif" alt="Portrait of Jamie Zawinski"><br>
@c @end html
-@c
+@c
@c @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
-@c
+@c
@c Steve Baur was the primary maintainer for 19.15 through 21.0.
-@c
+@c
@c Chuck Thompson and Ben Wing were the maintainers for 19.11 through 19.14
@c and heavy code contributors for 19.8 through 19.10.
-@c
+@c
@c Jamie Zawinski was the maintainer for 19.0 through 19.10 (the entire
@c history of Lucid Emacs). Richard Mlynarik was a heavy code contributor
@c to 19.6 through 19.8.
-@c
+@c
@c @end itemize
-@c
+@c
@c Along with many other contributors, partially enumerated in the
@c @samp{About XEmacs} option in the Help menu.
@c On Linux 1.3.98 with termcap 2.0.8 and the ncurses that came with libc
@c 5.2.18, XEmacs 20.0b20 is unable to open a tty device:
@c @c oh great
-@c
+@c
@c @example
@c src/xemacs -nw -q
@c Initialisation error:
@c @end iftex
@c Terminal type `xterm' undefined (or can't access database?)
@c @end example
-@c
+@c
@c @email{ben@@xemacs.org, Ben Wing} writes:
-@c
+@c
@c @quotation
@c Your ncurses configuration is messed up. Your /usr/lib/terminfo is a
@c bad pointer, perhaps to a CD-ROM that is not inserted.
@c @c WHOOOOOOOAT?!?!
@c Not necessarily. If you have GNU sed 3.0 you should downgrade it to
@c 2.05. From the @file{README} at prep.ai.mit.edu:
-@c
+@c
@c @quotation
@c sed 3.0 has been withdrawn from distribution. It has major revisions,
@c which mostly seem to be improvements; but it turns out to have bugs too
@c which cause trouble in some common cases.
-@c
+@c
@c Tom Lord won't be able to work fixing the bugs until May. So in the
@c mean time, we've decided to withdraw sed 3.0 from distribution and make
@c version 2.05 once again the recommended version.
@c @end quotation
-@c
+@c
@c It has also been observed that the vfork test on Solaris will leave a
@c core dump.
generated by redirecting the output of @code{make} and @code{make check}
to a file (@file{,,make-all.out} and @file{,,make-check.out} are the
default used by @code{build-report}), and executing @kbd{M-x
-build-rpt}.
+build-rpt}.
@node Q2.1.2
you have problems. To fix, set the environment variable
@code{XKEYSYMDB} to the location of the @file{XKeysymDB} file on your
system or to the location of the one included with SXEmacs which
-should be at
+should be at
@iftex
@*
@end iftex
@c would not run because it claimed the version number was incorrect
@c although it was indeed OK. I traced the problem to the regular
@c expression handler.
-@c
+@c
@c @email{douglask@@dstc.edu.au, Douglas Kosovic} writes:
-@c
+@c
@c @quotation
@c Actually it's a DEC cc optimisation bug that screws up the regexp
@c handling in XEmacs.
-@c
+@c
@c Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
@c different sort of optimisation) works fine.
@c @end quotation
-@c
+@c
@c See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
@c build with the @samp{-migrate} flag:
-@c
+@c
@c @example
@c @uref{http://www-digital.cern.ch/carney/emacs/emacs.html}
@c @c Link above, <URL:http://www-digital.cern.ch/carney/emacs/emacs.html> is
@c @c dead. And the directory `carney' is empty.
-@c
-@c
-@c
+@c
+@c
+@c
@c @end example
-@c
+@c
@c NOTE: There have been a variety of other problems reported that are
@c fixed in this fashion.
@unnumberedsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
@c @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
-@c
+@c
@c @quotation
@c With XEmacs 19.13 and HP/UX 10.10, anything that relies on the
@c @code{create_process} function fails. This breaks a lot of things
@c (shell-mode, compile, ange-ftp, to name a few).
@c @end quotation
-@c
+@c
@c @email{johnson@@dtc.hp.com, Phil Johnson} writes:
-@c
+@c
@c @quotation
@c This is a problem specific to HP-UX 10.10. It only occurs when XEmacs
@c is compiled for shared libraries (the default), so you can work around
@c it by compiling a statically-linked binary (run configure with
@c @samp{--dynamic=no}).
-@c
+@c
@c I'm not sure whether the problem is with a particular shared library or
@c if it's a kernel problem which crept into 10.10.
@c @end quotation
-@c
+@c
@c @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
-@c
+@c
@c @quotation
@c I had a few problems with 10.10. Apparently, some of them were solved by
@c forcing a static link of libc (manually).
If you'd like to write your own, this file provides as good a set of
examples as any to start from. The file is located in edit-utils
-package.
+package.
@node Q3.8.3
Sparcworks, EOS, and WorkShop:
* Q4.4.1:: What is SPARCworks, EOS, and WorkShop
-* Q4.4.2:: How do I start the Sun Workshop support in SXEmacs?
Energize:
* Q4.5.1:: What is/was Energize?
The Gnus numbering issues are not meant for mere mortals to know them.
@c If you feel you @emph{must} enter the muddy waters of Gnus, visit the
@c excellent FAQ, maintained by Justin Sheehy, at:
-@c
+@c
@c @example
@c @uref{http://www.ccs.neu.edu/software/contrib/gnus/}
@c @end example
@end quotation
-@node Q4.4.2
-@unnumberedsec Q4.4.2: How do I start the Sun Workshop support in SXEmacs?
-
-Add the switch ---with-workshop to the configure command when building
-SXEmacs and put the following in one of your startup files
-(e.g. site-start.el or init.el):
-
-@lisp
-(when (featurep 'tooltalk)
- (load "tooltalk-macros")
- (load "tooltalk-util")
- (load "tooltalk-init"))
-(when (featurep 'sparcworks)
- (load "sunpro-init")
- (load "ring")
- (load "comint")
- (load "annotations")
- (sunpro-startup))
-@end lisp
-
-
@node Q4.5.1
@unnumberedsec 4.5: Energize
@unnumberedsec Q4.5.1: What is/was Energize?
fi
@end example
-Note that there is a known problem when running SXEmacs and
+Note that there is a known problem when running SXEmacs and
@samp{gnuclient -nw} on the same TTY.
@end quotation
@unnumberedsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
@c @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
-@c
+@c
@c @quotation
@c Yes, abbrevs only expands word-syntax strings. While XEmacs does not
@c prevent you from defining (e.g. with @kbd{C-x a g} or @kbd{C-x a l})
@c them. So you need to ensure, that the abbreviation contains letters and
@c digits only. This means that @samp{xd}, @samp{d5}, and @samp{5d} are
@c valid abbrevs, but @samp{&d}, and @samp{x d} are not.
-@c
+@c
@c If this sounds confusing to you, (re-)read the online documentation for
@c abbrevs (@kbd{C-h i m XEmacs @key{RET} m Abbrevs @key{RET}}), and then come back and
@c read this question/answer again.
@c @end quotation
-@c
+@c
@c Starting with XEmacs 20.3 this restriction has been lifted.
Does not apply anymore.
Fix major bug in regex.c
This fixed a whole swag of crashes involving regexps and
-syntax-tables.
+syntax-tables.
@item
Sync up with XEmacs 21.4 -- Various Developers.
Features provided when all of the library demands are met:
@example
- (featurep 'bigz) and
+ (featurep 'bigz) and
(featurep 'bignum) <=> if MPZ from GMP or BSD MP is present
-
+
(featurep 'bigq) and
(featurep 'ratio) <=> if MPQ from GMP is present
-
+
(featurep 'bigf) and
(featurep 'bigfloat) <=> if MPF from GMP is present
-
+
(featurep 'bigfr) <=> if MPFR is present
-
+
(featurep 'bigc) <=> if MPC is present
-
+
(featurep 'number-types) <=> if one of the above features is
provided
@end example
SXEmacs tries to relieve backslashitis by implementing raw strings.
You'll imediately notice the benefit of raw strings when use them for
those hairy regexps. Consider the regular expression (from
-font-latex.el)...
+font-latex.el)...
@example
"\\(?:^\\|[^\\]\\)\\(?:\\\\\\\\\\)*\\(\\\\[@@A-Za-z]+\\)"
$ sxemacs -nw -vanilla
...and look at the modeline. Now open a .c file and turn on
-font-lock...
+font-lock...
C-x C-f /path/to/file.c RET
M-x font-lock-mode RET
projects / sxemacs / blobdiff