@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 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/}.
@item
The XEmacs and SXEmacs maintainers, especially the SXEmacs
maintainers, are generally more receptive to suggestions than the GNU
@item
The XEmacs and SXEmacs maintainers, especially the SXEmacs
maintainers, are generally more receptive to suggestions than the GNU
@unnumberedsec Q1.1.1: What is the FAQ editorial policy?
The FAQ is actively maintained and modified regularly. All links should
@unnumberedsec Q1.1.1: What is the FAQ editorial policy?
The FAQ is actively maintained and modified regularly. All links should
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.
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 @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 @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 @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 @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 @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 @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 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 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 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 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 Along with many other contributors, partially enumerated in the
@c @samp{About XEmacs} option in the Help menu.
@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 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 @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 @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 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 @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 @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 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 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
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
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
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
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
@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 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 Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
@c different sort of optimisation) works fine.
@c @end quotation
@c Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
@c different sort of optimisation) works fine.
@c @end quotation
@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 See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
@c build with the @samp{-migrate} flag:
@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 @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.
@unnumberedsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
@c @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
@unnumberedsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
@c @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
@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 @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 @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 @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 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 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 @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).
@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
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
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:
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:
@unnumberedsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
@c @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
@unnumberedsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
@c @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
@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 @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 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 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 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
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
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
projects / sxemacs / blobdiff