Build Fix -- compatibility issue with newer autoconf

[sxemacs] / info / sxemacs-faq.texi

\input texinfo.tex      @c -*- mode: texinfo; coding: utf-8 -*-
@c %**start of header
@documentencoding UTF-8
@setfilename sxemacs-faq.info
@settitle Frequently asked questions about SXEmacs
@setchapternewpage off
@c %**end of header
@finalout
@titlepage
@title SXEmacs FAQ
@subtitle Frequently Asked Questions about SXEmacs @inlineraw{tex,\hfill Edition 22.1.15}
@sp 1
@author Sebastian Freundt <hroptatyr@@sxemacs.org
@author Tony Rossini <rossini@@u.washington.edu>
@author Ben Wing <ben@@xemacs.org>
@author Chuck Thompson <cthomp@@xemacs.org>
@author Steve Baur <steve@@xemacs.org>
@author Andreas Kaempf <andreas@@sccon.com>
@author Christian Nybø <chr@@mediascience.no>
@author Sandra Wambold <wambold@@xemacs.org>
@page
@end titlepage

@ifinfo
@dircategory SXEmacs Editor
@direntry
* FAQ: (sxemacs-faq).            SXEmacs FAQ.
@end direntry
@end ifinfo

@node Top, Introduction, (dir), (dir)
@top SXEmacs FAQ

This is the guide to the SXEmacs Frequently Asked Questions list---a
compendium of questions and answers pertaining to one of the finest
programs ever written.  SXEmacs is much more than just a Text Editor.

SXEmacs Note:  Currently, this is the FAQ from XEmacs.  It will be
overhauled and updated in the very near future.  If you are reading this
note, @emph{please} remind us to do so.

This FAQ is freely redistributable.  This FAQ is distributed in the hope
that it will be useful, but WITHOUT ANY WARRANTY; without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

In the near future this assortment of questions will be automatically
generated from a database.  We are currently evaluating the design
specifications, a general classification and technical necessities.

@c If you have a Web browser, the official hypertext version is at
@c @iftex
@c @*
@c @end iftex
@c @uref{http://www.xemacs.org/FAQ/xemacs-faq.html}

@c @ifset CANONICAL
@c @html
@c This document is available in several different formats:
@c @itemize @bullet
@c @item
@c @uref{xemacs-faq.txt, As a single ASCII file}, produced by
@c @code{makeinfo --no-headers}
@c @item
@c @uref{xemacs-faq.dvi, As a .dvi file}, as used with
@c @uref{http://www.tug.org, TeX.}
@c @item
@c As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
@c as well as in @uref{xemacs-faq-letter.ps, letter format}
@c @item
@c In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
@c @uref{xemacs-faq.html, one monolithic} document.
@c @item
@c The canonical version of the FAQ is the texinfo document
@c @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
@c @item
@c If you do not have makeinfo installed, you may @uref{xemacs-faq.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/}.
@c
@c @end itemize
@c
@c @end html
@c
@c @end ifset
@c
@c end ifset points to CANONICAL

@menu
* Introduction::        Introduction, Policy, Credits.
* Installation::        Installation and Trouble Shooting.
* Customisation::       Customisation and Options.
* Subsystems::          Major Subsystems.
* Miscellaneous::       The Miscellaneous Stuff.
* MS Windows::          SXEmacs on Microsoft Windows.
* Current Events::      What the Future Holds.

@detailmenu

 --- The Detailed Node Listing ---

Introduction, Policy, Credits

* Q1.0.1::      What is SXEmacs?
* Q1.0.2::      What is the current version of SXEmacs?
* Q1.0.3::      Where can I find it?
* Q1.0.4::      Why another version of Emacs?
* Q1.0.5::      Why haven't XEmacs/SXEmacs and GNU Emacs merged?
* Q1.0.6::      Where can I get help?
* Q1.0.7::      Where are the mailing lists archived?
* Q1.0.8::      How do you pronounce SXEmacs?
* Q1.0.9::      What does SXEmacs look like?
* Q1.0.10::     Is there a port of SXEmacs to Microsoft ('95 or NT)?
* Q1.0.11::     Is there a port of SXEmacs to the Macintosh?
* Q1.0.12::     Is there a port of SXEmacs to NextStep?
* Q1.0.13::     Is there a port of SXEmacs to OS/2?
* Q1.0.14::     Where can I get a printed copy of the SXEmacs users manual?

Policies:
* Q1.1.1::      What is the FAQ editorial policy?
* Q1.1.2::      How do I become a beta tester?
* Q1.1.3::      How do I contribute to SXEmacs itself?

Credits:
* Q1.2.1::      Who wrote XEmacs? Who wrote SXEmacs?
* Q1.2.2::      Who contributed to this version of the FAQ?
* Q1.2.3::      Who contributed to the FAQ in the past?

Internationalisation:
* Q1.3.1::      What is the status of internationalisation support aka MULE (including Asian language support?
* Q1.3.2::      How can I help with internationalisation?
* Q1.3.3::      How do I type non-ASCII characters?
* Q1.3.4::      Can SXEmacs messages come out in a different language?
* Q1.3.5::      Please explain the various input methods in MULE/SXEmacs
* Q1.3.6::      How do I portably code for MULE/XEmacs/SXEmacs?
* Q1.3.7::      How about Cyrillic Modes?
* Q1.3.8::      Does SXEmacs support Unicode?
* Q1.3.9::      How does SXEmacs display Unicode?

Getting Started:
* Q1.4.1::      What is an @file{init.el} or @file{.emacs} and is there a sample one?
* Q1.4.2::      Can I use the same @file{init.el}/@file{.emacs} with other Emacsen?
* Q1.4.3::      Any good SXEmacs tutorials around?
* Q1.4.4::      May I see an example of a useful SXEmacs Lisp function?
* Q1.4.5::      And how do I bind it to a key?
* Q1.4.6::      What's the difference between a macro and a function?

Installation and Trouble Shooting

* Q2.0.1::      Running SXEmacs without installing.
* Q2.0.2::      SXEmacs is too big.
* Q2.0.3::      Compiling SXEmacs with Netaudio. @c what?!
* Q2.0.4::      Problems with Linux and ncurses.
* Q2.0.5::      Do I need X11 to run SXEmacs?
* Q2.0.6::      I'm having strange crashes.  What do I do?
* Q2.0.7::      Libraries in non-standard locations.
* Q2.0.8::      can't resolve symbol _h_errno
* Q2.0.9::      Where do I find external libraries?
* Q2.0.10::     After I run configure I find a coredump, is something wrong?
* Q2.0.11::     SXEmacs can't resolve host names.
* Q2.0.12::     Why can't I strip SXEmacs?
* Q2.0.13::     I don't need no steenkin' packages.  Do I?
* Q2.0.14::     How do I figure out which packages to install?
* Q2.0.15::     EFS fails with "500 AUTH not understood" (NEW)

Trouble Shooting:
* Q2.1.1::      SXEmacs just crashed on me!
* Q2.1.2::      Cryptic Minibuffer messages.
* Q2.1.3::      Translation Table Syntax messages at Startup.
* Q2.1.4::      Startup warnings about deducing proper fonts?
* Q2.1.5::      SXEmacs cannot connect to my X Terminal.
* Q2.1.6::      SXEmacs just locked up my Linux X server.
* Q2.1.7::      HP Alt key as Meta.
* Q2.1.8::      got (wrong-type-argument color-instance-p nil)!
* Q2.1.9::      SXEmacs causes my OpenWindows 3.0 server to crash.
* Q2.1.10::     Warnings from incorrect key modifiers.
* Q2.1.11::     Can't instantiate image error... in toolbar
* Q2.1.12::     Regular Expression Problems on DEC OSF1.
* Q2.1.13::     HP/UX 10.10 and @code{create_process} failure
* Q2.1.14::     @kbd{C-g} doesn't work for me.  Is it broken?
* Q2.1.15::     How to debug a SXEmacs problem with a debugger.
* Q2.1.16::     SXEmacs crashes in @code{strcat} on HP/UX 10.
* Q2.1.17::     @samp{Marker does not point anywhere}.
* Q2.1.18::     SXEmacs is outputting lots of X errors.
* Q2.1.19::     SXEmacs does not follow the local timezone.
* Q2.1.20::     @samp{Symbol's function definition is void: hkey-help-show.}
* Q2.1.21::     [This question intentionally left blank]
* Q2.1.22::     SXEmacs seems to take a really long time to do some things.
* Q2.1.23::     Movemail on Linux does not work for SXEmacs.
* Q2.1.24::     SXEmacs won't start without network.
* Q2.1.25::     After upgrading, SXEmacs won't do `foo' any more!

Customisation and Options

* Q3.0.1::      What version of Emacs am I running?
* Q3.0.2::      How do I evaluate Elisp expressions?
* Q3.0.3::      @code{(setq tab-width 6)} behaves oddly.
* Q3.0.4::      How can I add directories to the @code{load-path}?
* Q3.0.5::      How to check if a lisp function is defined?
* Q3.0.6::      Can I force the output of @code{(face-list)} to a buffer?
* Q3.0.7::      Font selections don't get saved after @code{Save Options}.
* Q3.0.8::      How do I make a single minibuffer frame?
* Q3.0.9::      What is @code{Customize}?

X Window System & Resources:
* Q3.1.1::      Where is a list of X resources?
* Q3.1.2::      How can I detect a color display?
* Q3.1.3::      [This question intentionally left blank]
* Q3.1.4::      [This question intentionally left blank]
* Q3.1.5::      How can I get the icon to just say @samp{SXEmacs}?
* Q3.1.6::      How can I have the window title area display the full path?
* Q3.1.7::      @samp{sxemacs -name junk} doesn't work?
* Q3.1.8::      @samp{-iconic} doesn't work.

Textual Fonts & Colors:
* Q3.2.1::      How can I set color options from @file{init.el}?
* Q3.2.2::      How do I set the text, menu and modeline fonts?
* Q3.2.3::      How can I set the colors when highlighting a region?
* Q3.2.4::      How can I limit color map usage?
* Q3.2.5::      My tty supports color, but SXEmacs doesn't use them.
* Q3.2.6::      Can I have pixmap backgrounds in SXEmacs?
* Q3.2.7::      How do I display non-ASCII characters?

The Modeline:
* Q3.3.1::      How can I make the modeline go away?
* Q3.3.2::      How do you have SXEmacs display the line number in the modeline?
* Q3.3.3::      How do I get SXEmacs to put the time of day on the modeline?
* Q3.3.4::      How do I turn off current chapter from AUC TeX modeline?
* Q3.3.5::      How can one change the modeline color based on the mode used?

Multiple Device Support:
* Q3.4.1::      How do I open a frame on another screen of my multi-headed display?
* Q3.4.2::      Can I really connect to a running SXEmacs after calling up over a modem?  How?

The Keyboard:
* Q3.5.1::      How can I bind complex functions (or macros) to keys?
* Q3.5.2::      How can I stop down-arrow from adding empty lines to the bottom of my buffers?
* Q3.5.3::      How do I bind C-. and C-; to scroll one line up and down?
* Q3.5.4::      Globally binding @kbd{Delete}?
* Q3.5.5::      Scrolling one line at a time.
* Q3.5.6::      How to map @kbd{Help} key alone on Sun type4 keyboard?
* Q3.5.7::      How can you type in special characters in SXEmacs?
* Q3.5.8::      [This question intentionally left blank]
* Q3.5.9::      How do I make the Delete key delete forward?
* Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
* Q3.5.11::     How do I map the arrow keys?

The Cursor:
* Q3.6.1::      Is there a way to make the bar cursor thicker?
* Q3.6.2::      Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
* Q3.6.3::      Can I make the cursor blink?

The Mouse and Highlighting:
* Q3.7.1::      How can I turn off Mouse pasting?
* Q3.7.2::      How do I set control/meta/etc modifiers on mouse buttons?
* Q3.7.3::      Clicking the left button does not do anything in buffer list.
* Q3.7.4::      How can I get a list of buffers when I hit mouse button 3?
* Q3.7.5::      Why does cut-and-paste not work between SXEmacs and a cmdtool?
* Q3.7.6::      How I can set SXEmacs up so that it pastes where the text cursor is?
* Q3.7.7::      How do I select a rectangular region?
* Q3.7.8::      Why does @kbd{M-w} take so long?

The Menubar and Toolbar:
* Q3.8.1::      How do I get rid of the menu (or menubar)?
* Q3.8.2::      Can I customise the basic menubar?
* Q3.8.3::      How do I control how many buffers are listed in the menu @code{Buffers} list?
* Q3.8.4::      Resources like @code{Emacs*menubar*font} are not working?
* Q3.8.5::      How can I bind a key to a function to toggle the toolbar?

Scrollbars:
* Q3.9.1::      How can I disable the scrollbar?
* Q3.9.2::      How can one use resources to change scrollbar colors?
* Q3.9.3::      Moving the scrollbar can move the point; can I disable this?
* Q3.9.4::      How can I turn off automatic horizontal scrolling in specific modes?

Text Selections:
* Q3.10.1::     How can I turn off or change highlighted selections?
* Q3.10.2::     How do I get that typing on an active region removes it?
* Q3.10.3::     Can I turn off the highlight during isearch?
* Q3.10.4::     How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
* Q3.10.5::     The region disappears when I hit the end of buffer while scrolling.
* Q3.10.6::     Why is killing so slow?

Major Subsystems

* Q4.0.1::      How do I set up VM to retrieve remote mail using POP?
* Q4.0.2::      How do I get VM to filter mail for me?
* Q4.0.3::      How can I get VM to automatically check for new mail?
* Q4.0.4::      [This question intentionally left blank]
* Q4.0.5::      How do I get my outgoing mail archived?
* Q4.0.6::      I have various addresses at which I receive mail.  How can I
                  tell VM to ignore them when doing a "reply-all"?
* Q4.0.7::      Is there a mailing list or FAQ for VM?
* Q4.0.8::      Remote mail reading with VM.
* Q4.0.9::      rmail or VM gets an error incorporating new mail.
* Q4.0.10::     How do I make VM stay in a single frame?
* Q4.0.11::     How do I make VM or mh-e display graphical smilies?
* Q4.0.12::     Customisation of VM not covered in the manual or here.

Web browsing with W3:
* Q4.1.1::      What is W3?
* Q4.1.2::      How do I run W3 from behind a firewall?
* Q4.1.3::      Is it true that W3 supports style sheets and tables?

Reading Netnews and Mail with Gnus:
* Q4.2.1::      GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus,
                  Quassia Gnus, Pterodactyl Gnus, Oort Gnus, argh!
* Q4.2.2::      [This question intentionally left blank]
* Q4.2.3::      How do I make Gnus stay within a single frame?
* Q4.2.4::      How do I customize the From: line?

Other Mail & News:
* Q4.3.1::      How can I read and/or compose MIME messages?
* Q4.3.2::      What is TM and where do I get it?
* Q4.3.3::      Why isn't this @code{movemail} program working?
* Q4.3.4::      Movemail is also distributed by Netscape?  Can that cause problems?
* Q4.3.5::      Where do I find pstogif (required by tm)?

Sparcworks, EOS, and WorkShop:
* Q4.4.1::      What is SPARCworks, EOS, and WorkShop

Energize:
* Q4.5.1::      What is/was Energize?

Infodock:
* Q4.6.1::      What is Infodock?

Other Unbundled Packages:
* Q4.7.1::      What is AUC TeX?  Where do you get it?
* Q4.7.2::      Are there any Emacs Lisp Spreadsheets?
* Q4.7.3::      [This question intentionally left blank]
* Q4.7.4::      Problems installing AUC TeX
* Q4.7.5::      Is there a reason for an Emacs package not to be included in SXEmacs?
* Q4.7.6::      Is there a MatLab mode?
* Q4.7.7::      Can I edit files on other hosts?

The Miscellaneous Stuff

* Q5.0.1::      How can I do source code highlighting using font-lock?
* Q5.0.2::      I do not like cc-mode.  How do I use the old c-mode?
* Q5.0.3::      How do I get @samp{More} Syntax Highlighting on by default?
* Q5.0.4::      How can I enable auto-indent and/or Filladapt?
* Q5.0.5::      How can I get SXEmacs to come up in text/auto-fill mode by default?
* Q5.0.6::      How do I start up a second shell buffer?
* Q5.0.7::      Telnet from shell filters too much.
* Q5.0.8::      Why does edt emulation not work?
* Q5.0.9::      How can I emulate VI and use it as my default mode?
* Q5.0.10::     [This question intentionally left blank]
* Q5.0.11::     [This question intentionally left blank]
* Q5.0.12::     How do I disable gnuserv from opening a new frame?
* Q5.0.13::     How do I start gnuserv so that each subsequent SXEmacs is a client?
* Q5.0.14::     Strange things are happening in Shell Mode.
* Q5.0.15::     Where do I get the latest CC Mode?
* Q5.0.16::     I find auto-show-mode disconcerting.  How do I turn it off?
* Q5.0.17::     How can I get two instances of info?
* Q5.0.18::     [This question intentionally left blank]
* Q5.0.19::     Is there something better than LaTeX mode?
* Q5.0.20::     Is there a way to start a new SXEmacs if there's no
                  gnuserv running, and otherwise use gnuclient?

Emacs Lisp Programming Techniques:
* Q5.1.1::      The difference in key sequences between XEmacs/SXEmacs and GNU Emacs?
* Q5.1.2::      Can I generate "fake" keyboard events?
* Q5.1.3::      Could you explain @code{read-kbd-macro} in more detail?
* Q5.1.4::      What is the performance hit of @code{let}?
* Q5.1.5::      What is the recommended use of @code{setq}?
* Q5.1.6::      What is the typical misuse of @code{setq} ?
* Q5.1.7::      I like the @code{do} form of cl, does it slow things down?
* Q5.1.8::      I like recursion, does it slow things down?
* Q5.1.9::      How do I put a glyph as annotation in a buffer?
* Q5.1.10::     @code{map-extents} won't traverse all of my extents!
* Q5.1.11::     My elisp program is horribly slow.  Is there an easy way to
                  find out where it spends time?

Sound:
* Q5.2.1::      How do I turn off the sound?
* Q5.2.2::      How do I get funky sounds instead of a boring beep?
* Q5.2.3::      What's NAS, how do I get it?
* Q5.2.4::      Sunsite sounds don't play.
@c extend me

Miscellaneous:
* Q5.3.1::      How do you make SXEmacs indent CL if-clauses correctly?
* Q5.3.2::      [This question intentionally left blank]
* Q5.3.3::      How can I print WYSIWYG a font-locked buffer?
* Q5.3.4::      Getting @kbd{M-x lpr} to work with postscript printer.
* Q5.3.5::      How do I specify the paths that SXEmacs uses for finding files?
* Q5.3.6::      [This question intentionally left blank]
* Q5.3.7::      Can I have the end of the buffer delimited in some way?
* Q5.3.8::      How do I insert today's date into a buffer?
* Q5.3.9::      Are only certain syntactic character classes available for abbrevs?
* Q5.3.10::     How can I get those oh-so-neat X-Face lines?
* Q5.3.11::     How do I add new Info directories?
* Q5.3.12::     What do I need to change to make printing work?

SXEmacs on MS Windows

General Info:
* Q6.0.1::      Why did SXEmacs cut all support for Windows?

What the Future Holds

* Q7.0.1::      What new features will be in SXEmacs soon?
* Q7.0.2::      What's new in SXEmacs 22.1.0?
* Q7.0.3::      What's new in SXEmacs 22.1.1?
* Q7.0.4::      What's new in SXEmacs 22.1.2?
* Q7.0.5::      What's new in SXEmacs 22.1.3?
* Q7.0.6::      What's new in SXEmacs 22.1.4?

@end detailmenu
@end menu

@c missing FAQs:
@c - Where is the RedHat/Fedora/Slackware/Debian/SuSE/Mandrake/foobar
@c   package?
@c - What is this tla thingy?


@node Introduction, Installation, Top, Top
@unnumbered 1 Introduction, Policy, Credits

Learning SXEmacs is a lifelong activity.  Even people who have used Emacs
for years keep discovering new features.  Therefore this document cannot
be complete.  Instead it is aimed at the person who is either
considering SXEmacs for their own use, or has just obtained it and is
wondering what to do next.  It is also useful as a reference to
available resources.

The origin of this FAQ is well beyond SXEmacs-times and stems from the
XEmacs crew.  The initiator was @email{rossini@@biostat.washington.edu,
Anthony Rossini}.  The tale goes he got tired of hearing JWZ complain
about repeatedly having to answer questions.  @email{ben@@xemacs.org,
Ben Wing} and @email{cthomp@@xemacs.org, Chuck Thompson}, the principal
authors of XEmacs, then took over and Ben did a massive update
reorganising the whole thing.

The previous version was converted to hypertext format, and edited by
@email{steve@@xemacs.org, Steven L. Baur}.  It was converted back to
texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}.  The FAQ was then
maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
on to Christian Nybø.

If you notice any errors or items which should be added or amended to
this FAQ please send email to @email{sxemacs-devel@@sxemacs.org}.
Include @samp{SXEmacs FAQ} on the Subject: line.

@menu
Introduction:
* Q1.0.1::      What is SXEmacs?
* Q1.0.2::      What is the current version of SXEmacs?
* Q1.0.3::      Where can I find it?
* Q1.0.4::      Why another version of Emacs?
* Q1.0.5::      Why haven't XEmacs/SXEmacs and GNU Emacs merged?
* Q1.0.6::      Where can I get help?
* Q1.0.7::      Where are the mailing lists archived?
* Q1.0.8::      How do you pronounce SXEmacs?
* Q1.0.9::      What does SXEmacs look like?
* Q1.0.10::     Is there a port of SXEmacs to Microsoft ('95 or NT)?
* Q1.0.11::     Is there a port of SXEmacs to the Macintosh?
* Q1.0.12::     Is there a port of SXEmacs to NextStep?
* Q1.0.13::     Is there a port of SXEmacs to OS/2?
* Q1.0.14::     Where can I get a printed copy of the SXEmacs users manual?

Policies:
* Q1.1.1::      What is the FAQ editorial policy?
* Q1.1.2::      How do I become a beta tester?
* Q1.1.3::      How do I contribute to SXEmacs itself?

Credits:
* Q1.2.1::      Who wrote XEmacs? Who wrote SXEmacs?
* Q1.2.2::      Who contributed to this version of the FAQ?
* Q1.2.3::      Who contributed to the FAQ in the past?

Internationalisation:
* Q1.3.1::      What is the status of internationalisation support aka MULE (including Asian language support?
* Q1.3.2::      How can I help with internationalisation?
* Q1.3.3::      How do I type non-ASCII characters?
* Q1.3.4::      Can SXEmacs messages come out in a different language?
* Q1.3.5::      Please explain the various input methods in MULE/SXEmacs
* Q1.3.6::      How do I portably code for MULE/XEmacs/SXEmacs?
* Q1.3.7::      How about Cyrillic Modes?
* Q1.3.8::      Does SXEmacs support Unicode?
* Q1.3.9::      How does SXEmacs display Unicode?

Getting Started:
* Q1.4.1::      What is an @file{init.el} or @file{.emacs} and is there a sample one?
* Q1.4.2::      Can I use the same @file{init.el}/@file{.emacs} with other Emacsen?
* Q1.4.3::      Any good SXEmacs tutorials around?
* Q1.4.4::      May I see an example of a useful SXEmacs Lisp function?
* Q1.4.5::      And how do I bind it to a key?
* Q1.4.6::      What's the difference between a macro and a function?
@end menu

@unnumberedsec 1.0: Introduction

@node Q1.0.1, Q1.0.2, Introduction, Introduction
@unnumberedsec Q1.0.1: What is SXEmacs?

SXEmacs is a powerful, highly customisable open source text editor and
application development system, with full GUI support.  It is protected
under the GNU Public License and related to other versions of Emacs, in
particular XEmacs and GNU Emacs.  Its emphasis is on modern graphical
user interface support and an open software development model, similar
to Linux.

SXEmacs is a recent fork of the popular XEmacs and runs on nearly all
versions of Unix in existence.


@node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
@unnumberedsec Q1.0.2: What is the current version of SXEmacs?

SXEmacs 22.1.15 is the latest released version.
The current development line will become 22.1.16.


@node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
@unnumberedsec Q1.0.3: Where can I find it?

The canonical source can be found on the web at:

@example
@uref{https://downloads.sxemacs.org/}
@end example

Occasionally there are also snapshots of the current development line
available.  These can be found at:

@example
@uref{https://downloads.sxemacs.org/snapshots/}
@end example


@node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
@unnumberedsec Q1.0.4: Why another version of Emacs?

First of all, the situation got a little complicated.  With SXEmacs
regarded as a featurised, cleaned-up XEmacs, there are only two major
Emacs flavours.  Disregarding that, we have three.  Thus let us compare
GNU Emacs to SXEmacs/XEmacs in the first place, and afterwards do the
comparison SXEmacs vs. XEmacs.


@unnumberedsubsec Q1.0.4.1 GNU Emacs vs. SXEmacs/XEmacs

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
Emacs maintainers.

@item
Many, many more bundled packages than GNU Emacs.

@item
Packages at all.

@c @c does not apply anymore
@c @item
@c Face support on TTY's.

@c @c does not apply anymore
@c @item
@c A built-in toolbar.

@c @c does not apply anymore
@c @item
@c Some internationalisation support (including full MULE support, if
@c compiled with it).

@c @c does not apply anymore
@c @item
@c Variable-width fonts.

@c @c does not apply anymore
@c @item
@c Variable-height lines.

@item
Marginal annotations.

@item
XEmacs can be used as an Xt widget, and can be embedded within another
application.

@c @c does not apply anymore
@c @item
@c Horizontal and vertical scrollbars (using real toolkit scrollbars).

@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.

@item
Completely compatible (at the C level) with the Xt-based toolkits.

@item
Native support for PostgreSQL databases, LDAP servers and Berkeley DB.

@item
Support for GMP numbers (multi-precision integers, quotients and
floats).

@item
Support for multiple tty connections.

@c the FSF guys' implementation is a disease!
@item
Sound support.

@end itemize


@unnumberedsubsec Q1.0.4.2 SXEmacs vs. XEmacs

SXEmacs' strengths are clearly its feature list and its performance.
Also, these were the main reasons to fork.  XEmacs maintainers became
more and more uninterested in useful additions, reductions and
optimisations on the C-level.

@itemize
@item
Foreign Function Interface (FFI).

@item
PostgreSQL notify support.

@item
Native OpenSSL support.

@item
Support for mpfr floats, Gaussian and complex numbers, quaternions and
residue class rings.

@item
Support for raw strings.

@item
Much faster hashing functions.

@item
Support for internal URL access via cURL.

@item
Support for various image formats: Any format that ImageMagick is able
to handle.

@item
Support for modern sound libraries and sound servers: ESD, Polyp,
Jack, ALSA, and ao

@item
Support for various media formats (provided by external libraries):
Any format that FFmpeg, sndfile, SoX, MAD and gstreamer can handle.

@item
Support for the implementation network services through the use of
network server stream.

@end itemize



@node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
@unnumberedsec Q1.0.5: Why haven't XEmacs/SXEmacs and GNU Emacs Merged?

There are currently irreconcilable differences in the views about
technical, programming, design and organisational matters between RMS
and the SXEmacs/XEmacs development team which provide little hope for a
merge to take place in the short-term future.


@node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
@unnumberedsec Q1.0.6: 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 SXEmacs/XEmacs related questions
to gnu.emacs.help.

SXEmacs is an official group at the Freenode IRC network (formerly
OPN).  Join us at @uref{irc://irc.freenode.net/sxemacs}.

If you cannot post, nor read Usenet news, nor want to join us at IRC,
there is a mailing at @email{sxemacs-devel@@sxemacs.org} for general
and developing issues.


@node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
@unnumberedsec Q1.0.7: Where are the mailing lists archived?

The archives can be found at
@uref{https://www.sxemacs.org/list-archives/html/sxemacs-devel/}.

Subscription can be done via
@uref{https://www.sxemacs.org/mailman/listinfo}


@node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
@unnumberedsec Q1.0.8: How do you pronounce SXEmacs?

The most common pronounciation is @samp{sexy macs}.


@node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
@unnumberedsec Q1.0.9: What does SXEmacs look like?

Look at the screenshot section at @uref{https://www.sxemacs.org}.


@node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
@unnumberedsec Q1.0.10: Is there a port of SXEmacs to Microsoft ('95 or NT)?

Of course not!  The SXEmacs developers have so much fun stripping all of
the erroneous code and workaround-hacks related to Microsoft Windows.


@node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
@unnumberedsec Q1.0.11: Is there a port of SXEmacs to the Macintosh?

Good question. Is there?


@node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
@unnumberedsec Q1.0.12: Is there a port of SXEmacs to NextStep?

@c Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
@c the port of GNU Emacs to NeXTstep and expressed interest in doing the
@c XEmacs port, but never went any farther.

A what?


@node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
@unnumberedsec Q1.0.13: Is there a port of SXEmacs to OS/2?

@c No, but Alexander Nikolaev <avn_1251@@mail.ru> is working on it.

Aaaaargh. You could have also asked: Is there a port of SXEmacs to my
hamster.


@node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
@unnumberedsec Q1.0.14: Where can I obtain a printed copy of the SXEmacs User's Manual?

Pre-printed manuals are not available.  If you are familiar with
TeX, you can generate your own manual from the SXEmacs sources.

HTML and Postscript versions of SXEmacs manuals are available from the
SXEmacs web site at @uref{https://www.sxemacs.org}.
@c are they?
@c HTML are, but they may be a little out of date. --SY

@node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
@unnumberedsec 1.1: Policies
@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.

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.
Please make sure that @samp{SXEmacs FAQ} appears on the Subject: line
if you prefer to send us a mail.  If you would like to use IRC
instead, please make sure that someone actively responds to your
request.  We usually stay in the channel while we are asleep, but
if you join, post the request and leave again, we have no means to
get into contact with you again.

Questions and answers included into the FAQ will be edited for
spelling and grammar and will be attributed.


@node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
@unnumberedsec Q1.1.2: How do I become a beta tester?

We have no formal way.  Also there are no presumptions.  Just
subscribe to the mailing list @email{sxemacs-devel@@sxemacs.org} and
say hello or join us at IRC.

Be prepared to get your hands dirty, as beta testers are expected to
identify problems as best they can.


@node Q1.1.3, Q1.2.1, Q1.1.2, Introduction
@unnumberedsec Q1.1.3: How do I contribute to SXEmacs itself?

Quoting a famous developer:

I know the answer exactly.
Gotta run.


@node Q1.2.1, Q1.2.2, Q1.1.3, Introduction
@unnumberedsec 1.2: Credits
@unnumberedsec Q1.2.1: Who wrote SXEmacs?

SXEmacs is the result of the time and effort of many people.  The
developers responsible for recent releases can be viewed by
@kbd{M-x about-sxemacs} or the @samp{About SXEmacs} item in the Help
menu.

@c @itemize @bullet
@c @item @email{martin@@xemacs.org, Martin Buchholz}
@c @html
@c <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
@c @end html
@c
@c
@c @item @email{stephen@@xemacs.org, Stephen Turnbull}
@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 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
@c
@c @html
@c <br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
@c @end html
@c
@c @end itemize
@c
@c The developers responsible for older releases were:
@c
@c @itemize @bullet
@c @item @email{steve@@xemacs.org, Steve Baur}
@c
@c @html
@c <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
@c @end html
@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 @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 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
@c
@c Steve Baur was the primary maintainer for 19.15 through 21.0.
@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 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 @end itemize
@c
@c Along with many other contributors, partially enumerated in the
@c @samp{About XEmacs} option in the Help menu.


@node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
@unnumberedsec Q1.2.2: Who contributed to this version of the FAQ?

The following people contributed valuable suggestions to building this
version of the FAQ (listed in alphabetical order):

@itemize @bullet
@item @email{steve@@xemacs.org, SL Baur}

@item @email{hroptatyr@@sxemacs.org, Sebastian Freundt}

@item @email{hniksic@@xemacs.org, Hrvoje Niksic}

@item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}

@end itemize


@node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
@unnumberedsec Q1.2.3: Who contributed to the FAQ in the past?

This is only a partial list, as many names were lost in a hard disk
crash some time ago.

@itemize @bullet
@item @email{binge@@aloft.att.com, Curtis.N.Bingham}

@item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}

@item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}

@item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}

@item @email{daku@@nortel.ca, Mark Daku}

@item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}

@item @email{eeide@@cs.utah.edu, Eric Eide}

@item @email{af@@biomath.jussieu.fr, Alain Fauconnet}

@item @email{cflatter@@nrao.edu, Chris Flatters}

@item @email{ginsparg@@adra.com, Evelyn Ginsparg}

@item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}

@item @email{dkindred@@cmu.edu, Darrell Kindred}

@item @email{dmoore@@ucsd.edu, David Moore}

@item @email{arup+@@cmu.edu, Arup Mukherjee}

@item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}

@item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}

@item @email{dworkin@@ccs.neu.edu, Justin Sheehy}

@item @email{stig@@hackvan.com, Stig}

@item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
@end itemize


@node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
@unnumberedsec 1.3: Internationalisation
@unnumberedsec Q1.3.1: What is the status of internationalisation support aka MULE (including Asian language support?

Both the stable and development versions of SXEmacs include
internationalisation support (aka MULE).  MULE currently works on
Unix and Linux systems.  Binaries compiled without MULE support run
faster than MULE capable SXEmacsen.


@node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
@unnumberedsec Q1.3.2: How can I help with internationalisation?

If you would like to help, you can use the usual ways to get into
contact with us, that is join the mailing list
@email{sxemacs-devel@@sxemacs.org} or join us at
@uref{irc://irc.freenode.net/sxemacs}.

Especially needed are people who speak/write languages other than
English, who are willing to use SXEmacs/MULE regularly, and have some
experience with Elisp.

Translations of the TUTORIAL and man page are welcome, and SXEmacs
does support multilingual menus, but we have few current translations.

@xref{Q1.1.2}.


@node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
@unnumberedsec Q1.3.3: How do I type non-ASCII characters?

See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ for some
simple methods that also work in non-MULE builds of SXEmacs (but only for
one-octet coded character sets, and mostly for ISO 8859/1).  Many of the
methods available for Cyrillic (@pxref{Q1.3.7}) work without MULE.
MULE has more general capabilities.  @xref{Q1.3.5}.

@xref{Q3.2.7}, which covers display of non-ASCII characters.

@node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
@unnumberedsec Q1.3.4: Can SXEmacs messages come out in a different language?

The message-catalog support was written but is badly bit-rotted.
SXEmacs 22.2 may do so, but it is not of high priority currently.
Again, if you are willing to help, contact us.

However, menubar localisation @emph{does} work.  To enable it, add to
your @file{Emacs} file entries like this:

@example
Emacs*XlwMenu.resourceLabels:                   True
Emacs*XlwMenu.file.labelString:                 Fichier
Emacs*XlwMenu.openInOtherWindow.labelString:    In anderem Fenster oeffnen
@end example

The name of the resource is derived from the non-localised entry by
removing punctuation and capitalizing as above.


@node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
@unnumberedsec Q1.3.5: Please explain the various input methods in MULE/SXEmacs

Mule supports a wide variety of input methods.  There are three basic
classes: Lisp implementations, generic platform support, and library
interfaces.

@emph{Lisp implementations} include Quail, which provides table-driven
input methods for almost all the character sets that Mule supports
(including all of the ISO 8859 family, the Indic languages, Thai, and
so on), and SKK, for Japanese.  (SKK also supports an interface to an
external "dictionary server" process.)  Quail supports both typical
"dead-key" methods (eg, in the "latin-1-prefix" method, @kbd{" a}
produces ä, LATIN SMALL LETTER A WITH DIAERESIS), and the complex
dictionary-based phonetic methods used for Asian ideographic languages
like Chinese.

Lisp implementations can be less powerful (but they are not perceptibly
inefficient), and of course are not portable to non-Emacs applications.
The incompatibility can be very annoying.  On the other hand, they
require no special platform support or external libraries, so if you can
display the characters, Mule can input them for you and you can edit,
anywhere.

@emph{Generic platform support} is currently limited to the X Input
Method (XIM) framework, but IIIMF (Sun's Internet-Intranet Input
Method Framework) support is extremely desirable.  XIM is enabled at
build time by use of the @samp{--with-xim} flag to @code{configure}.
For use of XIM, see your platform documentation.  However, normally
the input method you use is specified via the @samp{LANG} and
@samp{XMODIFIERS} environment variables.

Of course, input skills are portable across most applications.  However,
especially in modern GUI systems the habit of using bucky bits has
fallen into sad disuse, and many XIM systems are poorly configured for
use with Emacs.  For example, the kinput2 input manager (a separate
process providing an interface between Japanese dictionary servers such
as Canna and Wnn, and the application) tends to gobble up keystrokes
generating Meta characters.  This means that to edit while using an XIM
input method, you must toggle the input method off every time you want
to use @kbd{M-f}.  Your mileage may vary.

@emph{Library interfaces} are most common for Japanese, although Wnn
supports Chinese (traditional and simplified) and Korean.  There are
Chinese and Korean input servers available, but we do not know of any
patches for SXEmacs to use them directly.  You can use them via
IM-enabled terminals, by manipulating the terminal coding systems.  We
describe only the Japanese-oriented systems here.  The advantage of
these systems is that they are very powerful, and on platforms where
they are available there is typically a wide range of applications that
support them.  Thus your input skills are portable across applications.

Mule provides built-in interfaces to the following input methods: Wnn4,
Wnn6, Canna, and SJ3.  These can be configured at build time.  There are
patches available (no URL, sorry) to support the SKK server, as well.
Wnn and SJ3 use the @code{egg} user interface.  The interface for Canna
is specialized to Canna.

Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
University. It is a powerful and complex system.  Wnn4 is free and Wnn6
is not.  Wnn uses grammatical hints and probability of word association,
so in principle Wnn can be cleverer than other methods.

Canna, made by NEC, supports only Japanese.  It is a simple and powerful
system. Canna uses only grammar, but its grammar and dictionary are
quite sophisticated.  So for standard modern Japanese, Canna seems
cleverer than Wnn4. In addition, the UNIX version of Canna is free.

SJ3, by Sony, supports only Japanese.

Egg consists of following parts:

@enumerate
@item
Input character Translation System (ITS) layer.
It translates ASCII inputs to Kana/PinYin/Hangul characters.

@item
Kana/PinYin/Hangul to Kanji transfer layer.
The interface layer to network Kana-Kanji server (Wnn and Sj3).
@end enumerate

These input methods are modal.  They have a raw (alphabet) mode, a
phonetic input mode, and Kana-Kanji transfer mode.  However there are
mode-less input methods for Egg and Canna.  @samp{boiled-egg} is a
mode-less input method running on Egg.  For Canna, @samp{canna.el} has a
tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
boiled-egg-like utilities.

Much of this information was provided by @email{morioka@@jaist.ac.jp,
MORIOKA Tomohiko}.

@node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
@unnumberedsec Q1.3.6: How do I portably code for MULE/SXEmacs?

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
different implementations.  The APIs also vary although recent versions
of XEmacs have tended to converge to the GNU Emacs standard.

MULE implementations are going to continue to evolve.  Both GNU Emacs
and XEmacs are working hard on Unicode support, which will involve new
APIs and probably variations on old ones.  For XEmacs 22, the old ISO
2022-based system for recognizing encodings will be replaced by a much
more flexible system, which should improve accuracy of automatic coding
detections, but will also involve new APIs.

@email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:

@quotation
The application implementor must write separate code for these mule
variants.  [Please don't hesitate to report these variants to us; they
are not, strictly speaking, bugs, but they give third-party developers
the same kind of creepy-crawly feeling.  We'll do what we can. -- Ed.]

MULE and the next version of Emacs are similar but the symbols are very
different---requiring separate code as well.

Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
@code{emu} to provide a common interface.  [There is an XEmacs package
of APEL which provides much more comprehensive coverage.  Be careful,
however; APEL has problems of its own. -- Ed.]

I have the following suggestions about dealing with mule variants:

@itemize @bullet
@item
@code{(featurep 'mule)} @code{t} on all mule variants

@item
@code{(boundp 'MULE)} is @code{t} on only MULE.  Maybe the next version
of Emacs will not have this symbol.

@item
MULE has a variable @code{mule-version}.  Perhaps the next version of
Emacs will have this variable as well.
@end itemize

Following is a sample to distinguish mule variants:

@lisp
(if (featurep 'mule)
    (cond ((boundp 'MULE)
           ;; for original Mule
           )
          ((string-match "XEmacs" emacs-version)
           ;; for XEmacs with Mule
           )
          (t
           ;; for next version of Emacs
           ))
  ;; for old emacs variants
  )
@end lisp
@end quotation


@node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
@unnumberedsec Q1.3.7: How about Cyrillic Modes?

@email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:

@quotation
There is a cyrillic mode in the file @file{mysetup.zip} in
@iftex
@*
@end iftex
@uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}.  This is a
modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
which can be obtained from
@end quotation

@uref{http://www.math.uga.edu/~valery/russian.el}.

@email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:

@quotation
There is another cyrillic mode for both GNU Emacs and XEmacs by
@email{manin@@camelot.mssm.edu, Dmitrii
(Mitya) Manin} at
@iftex

@end iftex
@uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
@c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
@c Changed to russian host instead
@end quotation

@email{rebecca.ore@@op.net, Rebecca Ore} writes:

@quotation
The fullest resource I found on Russian language use (in and out of
SXEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
@end quotation


@node Q1.3.8, Q1.3.9, Q1.3.7, Introduction
@unnumberedsec Q1.3.8: Does SXEmacs support Unicode?

Partially, as an external encoding for files, processes, and terminals.
It does not yet support Unicode fonts, see @ref{Q1.3.9}.

To get Unicode support, you need a Mule-enabled SXEmacs.  Install
Mule-UCS from packages in the usual way.  Put

@example
(require 'un-define)
(set-coding-priority-list '(utf-8))
(set-coding-category-system 'utf-8 'utf-8)
@end example

in your init file to enable the UTF-8 coding system.  You may wish to
view the documentation of @code{set-coding-priority-list} if you find
that files that are not UTF-8 are being mis-recognised as UTF-8.

Install standard national fonts (not Unicode fonts) for all
character sets you use.  See @ref{Q1.3.9}.

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.3.9, Q1.4.1, Q1.3.8, Introduction
@unnumberedsec Q1.3.9: How does SXEmacs 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,
either, because Unicode is not ISO 2022-compatible.  You'd have to
translate it to multiple 96x96 pages.

This means that Mule-UCS uses ordinary national fonts for display.  This
is not really a problem, except for those languages that use the Unified
Han characters.  The problem here is that Mule-UCS maps from Unicode
code points to national character sets in a deterministic way.  By
default, this means that Japanese fonts are tried first, then Chinese,
then Korean.  To change the priority ordering, use the command
`un-define-change-charset-order'.

It also means you can't use Unicode fonts directly, at least not without
extreme hackery.  You can run -nw with (set-terminal-coding-system
'utf-8) if you really want a Unicode font for some reason.

Real Unicode support will be introduced in SXEmacs 22.2.
@c will it?


@node Q1.4.1, Q1.4.2, Q1.3.9, Introduction
@unnumberedsec 1.4: Getting Started, Backing up & Recovery
@unnumberedsec Q1.4.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?

The @file{init.el} file is used to customise SXEmacs to your tastes.
The preferred location for the init file is
@file{$XDG_CONFIG_HOME/sxemacs/init.el} (@pxref{Init File,,,lispref,SXEmacs
Lisp Reference Manual}).

No two init files are alike, nor are they expected to be alike, but
that's the point.  The SXEmacs distribution contains an excellent
starter example in the @file{etc/} directory called
@file{sample.init.el}.  Copy this file from there to
@file{$XDG_CONFIG_HOME/sxemacs/init.el}, then edit it to suit.

You may bring the @file{sample.init.el} file into a SXEmacs buffer
from the menubar.  The menu entry is always under the @samp{Samples}
submenu in the @samp{Help} menu.  To determine the location of the
@file{etc/} directory type the command @kbd{C-h v data-directory
@key{RET}}.


@node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
@unnumberedsec Q1.4.2: Can I use the same @file{init.el}/@file{.emacs} with XEmacs or GNU Emacs?

Yes.  The sample @file{init.el} included in the SXEmacs
distribution will show you how to handle different versions and flavours
of Emacs.


@node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
@unnumberedsec Q1.4.3: Any good tutorials around?

There's the SXEmacs tutorial available from the Help Menu under
@samp{Basics->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}.


@node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
@unnumberedsec Q1.4.4: May I see an example of a useful SXEmacs 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 SXEmacs tell you.
Put the code into an SXEmacs 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.4.5, Q1.4.6, Q1.4.4, Introduction
@unnumberedsec Q1.4.5: 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.4.6,  , Q1.4.5, Introduction
@unnumberedsec Q1.4.6: 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 Installation, Customisation, Introduction, Top
@unnumbered 2 Installation and Trouble Shooting

This is part 2 of the SXEmacs Frequently Asked Questions list.  This
section is devoted to Installation, Maintenance and Trouble Shooting.

@menu
Installation:
* Q2.0.1::      Running SXEmacs without installing.
* Q2.0.2::      SXEmacs is too big.
* Q2.0.3::      Compiling SXEmacs with Netaudio. @c what?!
* Q2.0.4::      Problems with Linux and ncurses.
* Q2.0.5::      Do I need X11 to run SXEmacs?
* Q2.0.6::      I'm having strange crashes.  What do I do?
* Q2.0.7::      Libraries in non-standard locations.
* Q2.0.8::      can't resolve symbol _h_errno
* Q2.0.9::      Where do I find external libraries?
* Q2.0.10::     After I run configure I find a coredump, is something wrong?
* Q2.0.11::     SXEmacs can't resolve host names.
* Q2.0.12::     Why can't I strip SXEmacs?
* Q2.0.13::     I don't need no steenkin' packages.  Do I?
* Q2.0.14::     How do I figure out which packages to install?
* Q2.0.15::     EFS fails with "500 AUTH not understood" (NEW)

Trouble Shooting:
* Q2.1.1::      SXEmacs just crashed on me!
* Q2.1.2::      Cryptic Minibuffer messages.
* Q2.1.3::      Translation Table Syntax messages at Startup.
* Q2.1.4::      Startup warnings about deducing proper fonts?
* Q2.1.5::      SXEmacs cannot connect to my X Terminal.
* Q2.1.6::      SXEmacs just locked up my Linux X server.
* Q2.1.7::      HP Alt key as Meta.
* Q2.1.8::      got (wrong-type-argument color-instance-p nil)!
* Q2.1.9::      SXEmacs causes my OpenWindows 3.0 server to crash.
* Q2.1.10::     Warnings from incorrect key modifiers.
* Q2.1.11::     Can't instantiate image error... in toolbar
* Q2.1.12::     Regular Expression Problems on DEC OSF1.
* Q2.1.13::     HP/UX 10.10 and @code{create_process} failure
* Q2.1.14::     @kbd{C-g} doesn't work for me.  Is it broken?
* Q2.1.15::     How to debug a SXEmacs problem with a debugger.
* Q2.1.16::     SXEmacs crashes in @code{strcat} on HP/UX 10.
* Q2.1.17::     @samp{Marker does not point anywhere}.
* Q2.1.18::     SXEmacs is outputting lots of X errors.
* Q2.1.19::     SXEmacs does not follow the local timezone.
* Q2.1.20::     @samp{Symbol's function definition is void: hkey-help-show.}
* Q2.1.21::     [This question intentionally left blank]
* Q2.1.22::     SXEmacs seems to take a really long time to do some things.
* Q2.1.23::     Movemail on Linux does not work for SXEmacs.
* Q2.1.24::     SXEmacs won't start without network.
* Q2.1.25::     After upgrading, SXEmacs won't do `foo' any more!
@end menu


@node Q2.0.1, Q2.0.2, Installation, Installation
@unnumberedsec 2.0: Installation
@unnumberedsec Q2.0.1: Running SXEmacs without installing

How can I just try SXEmacs without installing it?

SXEmacs will run in place without requiring installation and copying of
the Lisp directories, and without having to specify a special build-time
flag.  It's the copying of the Lisp directories that requires so much
space.  SXEmacs is largely written in Lisp.


@node Q2.0.2, Q2.0.3, Q2.0.1, Installation
@unnumberedsec Q2.0.2: SXEmacs is too big

The space required by the installation directories can be
reduced dramatically if desired.  Gzip all the .el files.  Remove all
the packages you'll never want to use.  Remove the TexInfo manuals.
Remove the Info (and use just hardcopy versions of the manual).  Remove
most of the stuff in etc.  Remove or gzip all the source code.  Gzip or
remove the C source code.  Configure it so that copies are not made of
the support lisp.

These are all Emacs Lisp source code and bytecompiled object code.
You may safely gzip everything named *.el here.  You may remove any
package you don't use.  @emph{Nothing bad will happen if you delete a
package that you do not use}.  You must be sure you do not use it
though, so be conservative at first.

Any package with the possible exceptions of xemacs-base, and EFS are
candidates for removal.  Ask yourself, @emph{Do I ever want to use this
package?}  If the answer is no, then it is a candidate for removal.

First, gzip all the .el files.  Then go about package by package and
start gzipping the .elc files.  Then run SXEmacs and do whatever it is
you normally do.  If nothing bad happens, then remove the package.
You can remove a package via the PUI interface (@kbd{M-x
pui-list-packages}, then press @kbd{d} to mark the packages you wish
to delete, and then @kbd{x} to delete them.

Another method is to do @kbd{M-x package-get-delete-package}.

@node Q2.0.3, Q2.0.4, Q2.0.2, Installation
@unnumberedsec Q2.0.3: Compiling SXEmacs with Netaudio.

What is the best way to compile SXEmacs with the netaudio system,
since I have got the netaudio system compiled but installed at a weird
place, I am not root.  Also in the READMEs it does not say anything
about compiling with the audioserver?

You should only need to add some stuff to the configure command line.
@c To tell it to compile in netaudio support: @samp{--with-sound=both}, or
@c @samp{--with-sound=nas} if you don't want native sound support for some
@c reason.) To tell it where to find the netaudio includes and libraries:

@example
--site-libraries=WHATEVER
--site-includes=WHATEVER
@end example

Then (fingers crossed) it should compile and it will use netaudio if
you have a server running corresponding to the X server. The netaudio
server has to be there when SXEmacs starts. If the netaudio server
goes away and another is run, SXEmacs should cope (fingers crossed,
error handling in netaudio isn't perfect).

BTW, netaudio has been renamed as it has a name clash with something
else, so if you see references to NAS or Network Audio System, it's the
same thing.  It also might be found at
@uref{ftp://ftp.x.org/contrib/audio/nas/}.


@node Q2.0.4, Q2.0.5, Q2.0.3, Installation
@unnumberedsec Q2.0.4: Problems with Linux and ncurses.

@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 @example
@c src/xemacs -nw -q
@c Initialisation error:
@c @iftex
@c @*
@c @end iftex
@c Terminal type `xterm' undefined (or can't access database?)
@c @end example
@c
@c @email{ben@@xemacs.org, Ben Wing} writes:
@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 @end quotation

There are none!


@node Q2.0.5, Q2.0.6, Q2.0.4, Installation
@unnumberedsec Q2.0.5: Do I need X11 to run SXEmacs?

No.


@node Q2.0.6, Q2.0.7, Q2.0.5, Installation
@unnumberedsec Q2.0.6: I'm having strange crashes.  What do I do?

There have been a variety of reports of crashes due to compilers with
buggy optimisers.  Please see the @file{PROBLEMS} file that comes with
SXEmacs to read what it says about your platform.


@node Q2.0.7, Q2.0.8, Q2.0.6, Installation
@unnumberedsec Q2.0.7: Libraries in non-standard locations

I have x-faces, jpeg, xpm etc. all in different places.  I've tried
space-separated, comma-separated, several --site-libraries, all to no
avail.

@example
--with-site-prefixes=/path/to/site1::/path/to/site2::/path/to/site3
@end example


@node Q2.0.8, Q2.0.9, Q2.0.7, Installation
@unnumberedsec Q2.0.8: can't resolve symbol _h_errno

Does not apply anymore.


@node Q2.0.9, Q2.0.10, Q2.0.8, Installation
@unnumberedsec Q2.0.9: Where do I find external libraries?

Oh well ... we support far too many external libraries to list them
here.  Have a glance at INSTALL to check if there are special
instructions for some of the libraries you intend to use.


@node Q2.0.10, Q2.0.11, Q2.0.9, Installation
@unnumberedsec Q2.0.10: After I run configure I find a core dump, is something wrong?

@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 @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 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 It has also been observed that the vfork test on Solaris will leave a
@c core dump.

Send a build report.


@node Q2.0.11, Q2.0.12, Q2.0.10, Installation
@unnumberedsec Q2.0.11: SXEmacs doesn't resolve hostnames.

This is the result of a long-standing problem with SunOS and the fact
that stock SunOS systems do not ship with DNS resolver code in libc.

@email{ckd@@loiosh.kei.com, Christopher Davis} writes:

@quotation
That's correct [The SunOS 4.1.3 precompiled binaries don't do name
lookup].  Since Sun figured that everyone used NIS to do name lookups
(that DNS thing was apparently only a passing fad, right?), the stock
SunOS 4.x systems don't have DNS-based name lookups in libc.

This is also why Netscape ships two binaries for SunOS 4.1.x.

The best solution is to compile it yourself; the configure script will
check to see if you've put DNS in the shared libc and will then proceed
to link against the DNS resolver library code.
@end quotation


@node Q2.0.12, Q2.0.13, Q2.0.11, Installation
@unnumberedsec Q2.0.12: Why can't I strip SXEmacs?

@email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:

@quotation
Because of the way SXEmacs (and every other Emacsen, AFAIK) is
built. The link gives you a bare-boned emacs (called temacs). temacs
is then run, preloading some of the lisp files. The result is then
dumped into a new executable, named xemacs, which will contain all of
the preloaded lisp functions and data.

Now, during the dump itself, the executable (code+data+symbols) is
written on disk using a special unexec() function. This function is
obviously heavily system dependent. And on some systems, it leads to an
executable which, although valid, cannot be stripped without damage. If
memory serves, this is especially the case for AIX binaries. On other
architectures it might work OK.

The Right Way to strip the emacs binary is to strip temacs prior to
dumping xemacs. This will always work, although you can do that only if
you install from sources (as temacs is @file{not} part of the binary
kits).
@end quotation

@email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:

@quotation
Here is the trick:

@enumerate
@item
[ ./configure; make ]

@item
rm src/sxemacs

@item
strip src/temacs

@item
make

@item
cp src/sxemacs /usr/local/bin/sxemacs

@end enumerate
@end quotation


@node Q2.0.13, Q2.0.14, Q2.0.12, Installation
@unnumberedsec Q2.0.13: I don't need no steenkin' packages.  Do I?

Strictly speaking, no.  SXEmacs will build and install just fine
without any packages installed.  However, only the most basic editing
functions will be available with no packages installed, so installing
packages is an essential part of making your installed SXEmacs
_useful_.


@node Q2.0.14, Q2.0.15, Q2.0.13, Installation
@unnumberedsec Q2.0.14: How do I figure out which packages to install?

Many people really liked the old way that packages were bundled and do
not want to mess with packages at all.  You can grab all the packages at
once like you used to with old SXEmacs versions.  Download the file

@file{xemacs-sumo.tar.gz}

For a SXEmacs compiled with Mule you also need

@file{xemacs-mule-sumo.tar.gz}

from the @file{packages} directory on your XEmacs mirror archive.
N.B. They are called 'Sumo Tarballs' for good reason. They are
currently about 15MB and 2.3MB (gzipped) respectively.
@c mwhahahahaha, that'd load within a second here I think :P

Install them by

@code{cd $prefix/lib/sxemacs ; gunzip -c <tarballname> | tar xf -}

See README.packages for more detailed installation instructions.

As the Sumo tarballs are not regenerated as often as the individual
packages, it is recommended that you use the automatic package tools
afterwards to pick up any recent updates.


@node Q2.0.15, Q2.1.1, Q2.0.14, Installation
@unnumberedsec Q2.0.15: EFS fails with "500 AUTH not understood"

A typical error: FTP Error: USER request failed; 500 AUTH not understood.

Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
on comp.emacs.xemacs:

   tell your ftp client to not attempt AUTH authentication (or do not
   use FTP servers that don't understand AUTH)

and notes that you need to add an element (often "-u") to
@code{efs-ftp-program-args}.  Use @kbd{M-x customize-variable}, and
verify the needed flag with @code{man ftp} or other local
documentation.


@node Q2.1.1, Q2.1.2, Q2.0.15, Installation
@unnumberedsec 2.1: Trouble Shooting
@unnumberedsec Q2.1.1: Help!  SXEmacs just crashed on me!

First of all, don't panic.  Whenever SXEmacs crashes, it tries
extremely hard to auto-save all of your files before dying.  The main
time that this will not happen is if the machine physically lost power
or if you killed the SXEmacs process using @code{kill -9}.  The next
time you try to edit those files, you will be informed that a more
recent auto-save file exists.  You can use @kbd{M-x recover-file} to
retrieve the auto-saved version of the file.

You can use the command @kbd{M-x recover-session} after a crash to pick
up where you left off.

Now, SXEmacs is not perfect, and there may occasionally be times, or
particular sequences of actions, that cause it to crash.  If you can
come up with a reproducible way of doing this (or even if you have a
pretty good memory of exactly what you were doing at the time), the
maintainers would be very interested in knowing about it.  The best
way to report a bug is using @kbd{M-x report-sxemacs-bug} (or by
selecting @samp{Send Bug Report...} from the Help menu).  If that
won't work (e.g. you can't get SXEmacs working at all), send ordinary
mail to @email{sxemacs-devel@@sxemacs.org}. @emph{MAKE SURE} to
include the output from the crash, especially including the Lisp
backtrace, as well as the SXEmacs configuration from @kbd{M-x
describe-installation} (or equivalently, the file @file{Installation}
in the top of the build tree).

If at all possible, include a C stack backtrace of the core dump that
was produced.  This shows where exactly things went wrong, and makes it
much easier to diagnose problems.  To do this under Unix, you need to
locate the core file (it's called @file{core}, and is usually sitting in
the directory that you started SXEmacs from, or your home directory if
that other directory was not writable).  Then, go to that directory and
execute a command like:

@example
gdb `which sxemacs` core
@end example

and then issue the command @samp{where} to get the stack backtrace.  You
might have to use @code{dbx} or some similar debugger in place of
@code{gdb}.  If you don't have any such debugger available, complain to
your system administrator.

It's possible that a core file didn't get produced, in which case you're
out of luck.  Go complain to your system administrator and tell him not
to disable core files by default.  Also see @ref{Q2.1.15}, for tips and
techniques for dealing with a debugger.

When making a problem report make sure that:

@enumerate
@item
Report @strong{all} of the information output by SXEmacs during the
crash.

@item
You mention what OS & Hardware you are running SXEmacs on.

@item
What version of SXEmacs you are running.  Equivalently, if you are
using your own tla-branch of SXEmacs either tell where it is
available or include to which degree your version resembles the
mainline.

@item
What build options you are using.

@item
What are the versions of your libc and external libraries you use.

@item
If the problem is related to graphics and you are running Unix, we will
also need to know what version of the X Window System you are running,
and what window manager you are using.

@item
If the problem happened on a TTY, please include the terminal type.
@end enumerate

Much of the information above is automatically generated by @kbd{M-x
report-sxemacs-bug}.  Even more, and often useful, information can be
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}.


@node Q2.1.2, Q2.1.3, Q2.1.1, Installation
@unnumberedsec Q2.1.2: Cryptic Minibuffer messages.

When I try to use some particular option of some particular package, I
get a cryptic error in the minibuffer.

If you can't figure out what's going on, select Options/General
Options/Debug on Error from the Menubar and then try and make the error
happen again.  This will give you a backtrace that may be enlightening.
If not, try reading through this FAQ; if that fails, you could try
posting to comp.emacs.xemacs (making sure to include the backtrace) and
someone may be able to help.  If you can identify which Emacs lisp
source file the error is coming from you can get a more detailed stack
backtrace by doing the following:

@enumerate
@item
Visit the .el file in a SXEmacs buffer.

@item
Issue the command @kbd{M-x eval-current-buffer}.

@item
Reproduce the error.
@end enumerate

Depending on the version of SXEmacs, you may either select View->Show
Message Log (recent versions)from the menubar to see the most recent
messages.  This command is bound to @kbd{C-h l} by default.


@node Q2.1.3, Q2.1.4, Q2.1.2, Installation
@unnumberedsec Q2.1.3: Translation Table Syntax messages at Startup

I get tons of translation table syntax error messages during startup.
How do I get rid of them?

There are two causes of this problem.  The first usually only strikes
people using the prebuilt binaries.  The culprit in both cases is the
file @file{XKeysymDB}.

@itemize @bullet
@item
The binary cannot find the @file{XKeysymDB} file.  The location is
hardcoded at compile time so if the system the binary was built on
another machin and puts it a different place than your system does,
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
@iftex
@*
@end iftex
@file{<sxemacs_prefix>/lib/sxemacs-22.1.<x>/etc/XKeysymDB}.

@item
The binary is finding the XKeysymDB but it is out-of-date on your
system and does not contain the necessary lines.  Either ask your
system administrator to replace it with the one which comes with
SXEmacs (which is the stock R6 version and is backwards compatible) or
set your @code{XKEYSYMDB} variable to the location of SXEmacs's
described above.
@end itemize


@node Q2.1.4, Q2.1.5, Q2.1.3, Installation
@unnumberedsec Q2.1.4: Startup warnings about deducing proper fonts?

How can I avoid the startup warnings about deducing proper fonts?

This is highly dependent on your installation, but try with the
following font as your base font for SXEmacs and see what it does:

@format
-adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
@end format

More precisely, do the following in your resource file:

@format
Emacs.default.attributeFont: \
-adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
@end format

If you just don't want to see the @samp{*Warnings*} buffer at startup
time, you can set this:

@lisp
(setq display-warning-minimum-level 'error)
@end lisp

The buffer still exists; it just isn't in your face.


@node Q2.1.5, Q2.1.6, Q2.1.4, Installation
@unnumberedsec Q2.1.5: SXEmacs cannot connect to my X Terminal!

Help!  I can not get SXEmacs to display on my Envizex X-terminal!

Try setting the @code{DISPLAY} variable using the numeric IP address of
the host you are running SXEmacs from.


@node Q2.1.6, Q2.1.7, Q2.1.5, Installation
@unnumberedsec Q2.1.6: SXEmacs just locked up my Linux X server!

There have been several reports of the X server locking up under
Linux.  In all reported cases removing speedo and scaled fonts from
the font path corrected the problem.  This can be done with the
command @code{xset}.

It is possible that using a font server may also solve the problem.


@node Q2.1.7, Q2.1.8, Q2.1.6, Installation
@unnumberedsec Q2.1.7: HP Alt key as Meta.

How can I make SXEmacs recognize the Alt key of my HP workstation as a
Meta key?

Put the following line into a file and load it with xmodmap(1) before
starting SXEmacs:

@example
remove Mod1 = Mode_switch
@end example


@node Q2.1.8, Q2.1.9, Q2.1.7, Installation
@unnumberedsec Q2.1.8: got (wrong-type-argument color-instance-p nil)

@email{nataliek@@rd.scitec.com.au, Natalie Kershaw} writes:

@quotation
I am trying to run xemacs 19.13 under X11R4. Whenever I move the mouse I
get the following error. Has anyone seen anything like this? This
doesn't occur on X11R5.

@lisp
Signalling:
(error "got (wrong-type-argument color-instance-p nil)
and I don't know why!")
@end lisp
@end quotation

@email{map01kd@@gold.ac.uk, dinos} writes:

@quotation
I think this is due to undefined resources; You need to define color
backgrounds and foregrounds into your @file{.../app-defaults/Emacs}
like:

@example
*Foreground:    Black   ;everything will be of black on grey95,
*Background:    Grey95  ;unless otherwise specified.
*cursorColor:   Red3    ;red3 cursor with grey95 border.
*pointerColor:  Red3    ;red3 pointer with grey95 border.
@end example
@end quotation

Natalie Kershaw adds:

@quotation
What fixed the problem was adding some more colors to the X color
database (copying the X11R5 colors over), and also defining the
following resources:

@example
xemacs*cursorColor:    black
xemacs*pointerColor:   black
@end example

With the new colors installed the problem still occurs if the above
resources are not defined.

If the new colors are not present then an additional error occurs on
SXEmacs startup, which says @samp{Color Red3} not defined.
@end quotation


@node Q2.1.9, Q2.1.10, Q2.1.8, Installation
@unnumberedsec Q2.1.9: SXEmacs causes my OpenWindows 3.0 server to crash.

The OpenWindows 3.0 server is incredibly buggy.  Your best bet is to
replace it with one from the generic MIT X11 release.  You might also
try disabling parts of your @file{init.el}, like those that enable
background pixmaps.


@node Q2.1.10, Q2.1.11, Q2.1.9, Installation
@unnumberedsec Q2.1.10: Warnings from incorrect key modifiers.

The following information comes from the @file{PROBLEMS} file that comes
with SXEmacs.

If you're having troubles with HP/UX it is because HP/UX defines the
modifiers wrong in X.  Here is a shell script to fix the problem; be
sure that it is run after VUE configures the X server.

@example
#! /bin/sh
xmodmap 2> /dev/null - << EOF
keysym Alt_L = Meta_L
keysym Alt_R = Meta_R
EOF

xmodmap - << EOF
clear mod1
keysym Mode_switch = NoSymbol
add mod1 = Meta_L
keysym Meta_R = Mode_switch
add mod2 = Mode_switch
EOF
@end example


@node Q2.1.11, Q2.1.12, Q2.1.10, Installation
@unnumberedsec Q2.1.11: @samp{Can't instantiate image error...} in toolbar
@c New

@email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:

I just installed the XEmacs (20.4-2) RPMS that I downloaded from
@uref{http://www.xemacs.org/}.  Everything works fine, except that when
I place my mouse over the toolbar, it beeps and gives me this message:

@example
 Can't instantiate image (probably cached):
 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
 (16 16 <strange control characters> ...
@end example

@email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
@quotation
This is problem specific to some Chips and Technologies video
chips, when running XFree86.  Putting

@code{Option "sw_cursor"}

in @file{XF86Config} gets rid of the problem.
@end quotation


@node Q2.1.12, Q2.1.13, Q2.1.11, Installation
@unnumberedsec Q2.1.12: Problems with Regular Expressions on DEC OSF1.

@c I have xemacs 19.13 running on an alpha running OSF1 V3.2 148 and ispell
@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 @email{douglask@@dstc.edu.au, Douglas Kosovic} writes:
@c
@c @quotation
@c Actually it's a DEC cc optimisation bug that screws up the regexp
@c handling in XEmacs.
@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 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 @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 @end example
@c
@c NOTE: There have been a variety of other problems reported that are
@c fixed in this fashion.

Does not apply anymore.


@node Q2.1.13, Q2.1.14, Q2.1.12, Installation
@unnumberedsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.

@c @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
@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 @email{johnson@@dtc.hp.com, Phil Johnson} writes:
@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 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 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
@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).
@c @end quotation

Does not apply anymore.


@node Q2.1.14, Q2.1.15, Q2.1.13, Installation
@unnumberedsec Q2.1.14: @kbd{C-g} doesn't work for me.  Is it broken?

@email{ben@@xemacs.org, Ben Wing} writes:

@quotation
@kbd{C-g} does work for most people in most circumstances.  If it
doesn't, there are only two explanations:

@enumerate
@item
The code is wrapped with a binding of @code{inhibit-quit} to
@code{t}.  @kbd{Ctrl-Shift-G} should still work, I think.

@item
SIGIO is broken on your system, but BROKEN_SIGIO isn't defined.
@end enumerate

To test #2, try executing @code{(while t)} from the @samp{*scratch*}
buffer.  If @kbd{C-g} doesn't interrupt, then you're seeing #2.
@end quotation

@email{terra@@diku.dk, Morten Welinder} writes:

@quotation
On some (but @emph{not} all) machines a hung SXEmacsen can be revived
by @code{kill -FPE <pid>}.  This is a hack, of course, not a solution.
This technique works on a Sun4 running 4.1.3_U1.  To see if it works
for you, start another SXEmacs and test with that first.  If you get a
core dump the method doesn't work and if you get @samp{Arithmetic
error} then it does.
@end quotation


@node Q2.1.15, Q2.1.16, Q2.1.14, Installation
@unnumberedsec Q2.1.15: How to debug a SXEmacs problem with a debugger

If SXEmacs does crash on you, one of the most productive things you
can do to help get the bug fixed is to poke around a bit with the
debugger.  Here are some hints:

@itemize @bullet
@item
First of all, if the crash is at all reproducible, consider very
strongly recompiling your SXEmacs with debugging symbols and with no
optimisation (e.g. with GCC use the compiler flags @samp{-g -O0} --
that's an "oh" followed by a zero), and with the configure options
@samp{--debug=yes} and @samp{--error-checking=all}.  This will make
your SXEmacs run somewhat slower, but you are a lot more likely to
catch the problem earlier (closer to its source).  It makes it a lot
easier to determine what's going on with a debugger.

@item
If it's not a true crash (@emph{i.e.}, SXEmacs is hung, or a zombie
process), or it's inconvenient to run SXEmacs again because SXEmacs is
already running or is running in batch mode as part of a bunch of
scripts, you may be able to attach to the existing process with your
debugger.  Most debuggers let you do this by substituting the process ID
for the core file when you invoke the debugger from the command line, or
by using the @code{attach} command or something similar.

@item
If you're able to run SXEmacs under a debugger and reproduce the crash,
here are some things you can do:

@item
If SXEmacs is hitting an assertion failure, put a breakpoint on
@code{assert_failed()}.

@item
If SXEmacs is hitting some weird Lisp error that's causing it to crash
(e.g. during startup), put a breakpoint on @code{signal_1()}---this is
declared static in eval.c.

@item
If SXEmacs is outputting lots of X errors, put a breakpoint on
@code{x_error_handler()}; that will tell you which call is causing them.

@item
Internally, you will probably see lots of variables that hold objects of
type @code{Lisp_Object}.  These are references to Lisp objects.
Printing them out with the debugger probably won't be too
useful---you'll likely just see a number.  To decode them, do this:

@example
call dp (OBJECT)
@end example

where @var{OBJECT} is whatever you want to decode (it can be a variable,
a function call, etc.).  This uses the Lisp printing routines to out a
readable representation on the TTY from which the sxemacs process was
invoked.

@item
If you want to get a Lisp backtrace showing the Lisp call
stack, do this:

@example
call db ()
@end example

@item
Using @code{dp} and @code{db} has two disadvantages - they can only be
used with a running (including hung or zombie) sxemacs process, and they
do not display the internal C structure of a Lisp Object.  Even if all
you've got is a core dump, all is not lost.

If you're using GDB, there are some macros in the file
@file{src/.gdbinit} in the SXEmacs source distribution that should
make it easier for you to decode Lisp objects.  This file is
automatically read by gdb if gdb is run in the directory where sxemacs
was built, and contains these useful macros to inspect the state of
sxemacs:

@table @code
@item pobj
Usage: pobj lisp_object @*
Print the internal C representation of a lisp object.

@item xtype
Usage: xtype lisp_object @*
Print the Lisp type of a lisp object.

@item lbt
Usage: lbt @*
Print the current Lisp stack trace.
Requires a running sxemacs process.  (It works by calling the db
routine described above.)

@item ldp
Usage: ldp lisp_object @*
Print a Lisp Object value using the Lisp printer.
Requires a running sxemacs process.  (It works by calling the dp
routine described above.)

@item run-temacs
Usage: run-temacs @*
Run temacs interactively, like sxemacs.
Use this with debugging tools (like purify) that cannot deal with
dumping, or when temacs builds successfully, but sxemacs does not.

@item dump-temacs
Usage: dump-temacs @*
Run the dumping part of the build procedure.
Use when debugging temacs, not sxemacs!
Use this when temacs builds successfully, but sxemacs does not.

@item check-sxemacs
Usage: check-sxemacs @*
Run the test suite.  Equivalent to 'make check'.

@item check-temacs
Usage: check-temacs @*
Run the test suite on temacs.  Equivalent to 'make check-temacs'.
Use this with debugging tools (like purify) that cannot deal with dumping,
or when temacs builds successfully, but sxemacs does not.
@end table

If you are using Sun's @file{dbx} debugger, there is an equivalent file
@file{src/.dbxrc}, which defines the same commands for dbx.

@item
If you're using a debugger to get a C stack backtrace and you're seeing
stack traces with some of the innermost frames mangled, it may be due to
dynamic linking. (This happens especially under Linux.) Consider
reconfiguring with @samp{--dynamic=no}.  Also, sometimes (again under
Linux), stack backtraces of core dumps will have the frame where the
fatal signal occurred mangled; if you can obtain a stack trace while
running the SXEmacs process under a debugger, the stack trace should
be clean.

@c @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
@c version 1.8 if dynamic linking and debugging is a problem on Linux.

@item
If you're using a debugger to get a C stack backtrace and you're
getting a completely mangled and bogus stack trace, it's probably due to
one of the following:

@enumerate a
@item
Your executable has been stripped.  Bad news.  Tell your sysadmin not to
do this---it doesn't accomplish anything except to save a bit of disk
space, and makes debugging much much harder.

@item
Your stack is getting trashed.  Debugging this is hard; you have to do a
binary-search type of narrowing down where the crash occurs, until you
figure out exactly which line is causing the problem.  Of course, this
only works if the bug is highly reproducible.  Also, in many cases if
you run SXEmacs from the debugger, the debugger can protect the stack
somewhat.  However, if the stack is being smashed, it is typically the
case that there is a wild pointer somewhere in the program, often
quite far from where the crash occurs.

@item
If your stack trace has exactly one frame in it, with address 0x0, this
could simply mean that SXEmacs attempted to execute code at that
address, e.g. through jumping to a null function pointer.
Unfortunately, under those circumstances, GDB under Linux doesn't know
how to get a stack trace.
Yes, this is the fourth Linux-related problem I've mentioned.  I
have no idea why GDB under Linux is so bogus.  Complain to the GDB
authors, or to comp.os.linux.development.system.  Again, you'll have
to use the narrowing-down process described above.

@item
You will get a Lisp backtrace output when SXEmacs crashes, so you'll have
something useful.

@end enumerate
@end itemize


@node Q2.1.16, Q2.1.17, Q2.1.15, Installation
@unnumberedsec Q2.1.16: SXEmacs crashes in @code{strcat} on HP/UX 10

From the problems database (through
the former address http://support.mayfield.hp.com/):

@example
Problem Report: 5003302299
Status:         Open

System/Model:   9000/700
Product Name:   HPUX S800 10.0X
Product Vers:   9245XB.10.00

Description: strcat(3C) may read beyond
end of source string, can cause SIGSEGV


*** PROBLEM TEXT ***
strcat(3C) may read beyond the source string onto an unmapped page,
causing a segmentation violation.
@end example


@node Q2.1.17, Q2.1.18, Q2.1.16, Installation
@unnumberedsec Q2.1.17: @samp{Marker does not point anywhere}

As with other errors, set @code{debug-on-error} to @code{t} to get the
backtrace when the error occurs.


@node Q2.1.18, Q2.1.19, Q2.1.17, Installation
@unnumberedsec Q2.1.18: SXEmacs is outputting lots of X errors.

If this is happening, we would very much like to know what's causing
them.  To find this out, see @ref{Q2.1.15}.  Try to get both a C and Lisp
backtrace, and send them to @email{sxemacs-devel@@sxemacs.org}.


@node Q2.1.19, Q2.1.20, Q2.1.18, Installation
@unnumberedsec Q2.1.19: SXEmacs does not follow the local timezone.

When using one of the prebuilt binaries many users have observed that
SXEmacs uses the timezone under which it was built, but not the
timezone under which it is running.  The solution is to add:

@lisp
(set-time-zone-rule "MET")
@end lisp

to your @file{init.el} or the @file{site-start.el} file if you can.
Replace @code{MET} with your local timezone.


@node Q2.1.20, Q2.1.21, Q2.1.19, Installation
@unnumberedsec Q2.1.20: @samp{Symbol's function definition is void: hkey-help-show.}

This is a problem with a partially loaded hyperbole.  Try adding:

@lisp
(require 'hmouse-drv)
@end lisp

where you load hyperbole and the problem should go away.


@node Q2.1.21, Q2.1.22, Q2.1.20, Installation
@unnumberedsec Q2.1.21: [This question intentionally left blank]


@node Q2.1.22, Q2.1.23, Q2.1.21, Installation
@unnumberedsec Q2.1.22: SXEmacs seems to take a really long time to do some things

@email{dmoore@@ucsd.edu, David Moore} writes:

@quotation
Two things you can do:

1) C level:

When you see it going mad like this, you might want to use gdb from an
'xterm' to attach to the running process and get a stack trace.  To do
this just run:

@example
gdb /path/to/sxemacs/sxemacs ####
@end example

Where @code{####} is the process id of your sxemacs, instead of
specifying the core.  When gdb attaches, the sxemacs will stop [1] and
you can type `where' in gdb to get a stack trace as usual.  To get
things moving again, you can just type `quit' in gdb.  It'll tell you
the program is running and ask if you want to quit anyways.  Say 'y' and
it'll quit and have your emacs continue from where it was at.

2) Lisp level:

Turn on debug-on-quit early on.  When you think things are going slow
hit C-g and it may pop you in the debugger so you can see what routine
is running.  Press `c' to get going again.

debug-on-quit doesn't work if something's turned on inhibit-quit or in
some other strange cases.
@end quotation


@node Q2.1.23, Q2.1.24, Q2.1.22, Installation
@unnumberedsec Q2.1.23:  Movemail on Linux does not work for SXEmacs

@email{steve@@xemacs.org, SL Baur} writes:

@quotation
Movemail on Linux used to default to using flock file locking.  It now
defaults to using @code{.lock} file locking.  If this is not
appropriate for your system, edit src/s/linux.h and uncomment the line
that reads:

@example
#define MAIL_USE_FLOCK
@end example
@end quotation


@node Q2.1.24, Q2.1.25, Q2.1.23, Installation
@unnumberedsec Q2.1.24:  SXEmacs won't start without network.

If SXEmacs starts when you're on the network, but fails when you're not
on the network, you may be missing a "localhost" entry in your
@file{/etc/hosts} file.  The file should contain an entry like:

@example
127.0.0.1        localhost
@end example

Add that line, and SXEmacs will be happy.


@node Q2.1.25,  , Q2.1.24, Installation
@unnumberedsec Q2.1.25::  After upgrading, SXEmacs won't do `foo' any more!

You have been used to doing `foo', but now when you invoke it (or click
the toolbar button or select the menu item), nothing (or an error)
happens.  The simplest explanation is that you are missing a package
that is essential to you.  You can either track it down and install it
(there is a list of packages and brief descriptions of their contents in
@file{etc/PACKAGES}), or install the `Sumo Tarball' (@pxref{Q2.0.14}).

@c #### should xref to XEmacs manual here


@node Customisation, Subsystems, Installation, Top
@unnumbered 3 Customisation and Options

This is part 3 of the SXEmacs Frequently Asked Questions list.  This
section is devoted to Customisation and screen settings.

@menu
Customisation---Emacs Lisp and @file{init.el}/@file{.emacs}:
* Q3.0.1::      What version of Emacs am I running?
* Q3.0.2::      How do I evaluate Elisp expressions?
* Q3.0.3::      @code{(setq tab-width 6)} behaves oddly.
* Q3.0.4::      How can I add directories to the @code{load-path}?
* Q3.0.5::      How to check if a lisp function is defined?
* Q3.0.6::      Can I force the output of @code{(face-list)} to a buffer?
* Q3.0.7::      Font selections don't get saved after @code{Save Options}.
* Q3.0.8::      How do I make a single minibuffer frame?
* Q3.0.9::      What is @code{Customize}?

X Window System & Resources:
* Q3.1.1::      Where is a list of X resources?
* Q3.1.2::      How can I detect a color display?
* Q3.1.3::      [This question intentionally left blank]
* Q3.1.4::      [This question intentionally left blank]
* Q3.1.5::      How can I get the icon to just say @samp{SXEmacs}?
* Q3.1.6::      How can I have the window title area display the full path?
* Q3.1.7::      @samp{sxemacs -name junk} doesn't work?
* Q3.1.8::      @samp{-iconic} doesn't work.

Textual Fonts & Colors:
* Q3.2.1::      How can I set color options from @file{init.el}?
* Q3.2.2::      How do I set the text, menu and modeline fonts?
* Q3.2.3::      How can I set the colors when highlighting a region?
* Q3.2.4::      How can I limit color map usage?
* Q3.2.5::      My tty supports color, but SXEmacs doesn't use them.
* Q3.2.6::      Can I have pixmap backgrounds in SXEmacs?
* Q3.2.7::      How do I display non-ASCII characters?

The Modeline:
* Q3.3.1::      How can I make the modeline go away?
* Q3.3.2::      How do you have SXEmacs display the line number in the modeline?
* Q3.3.3::      How do I get SXEmacs to put the time of day on the modeline?
* Q3.3.4::      How do I turn off current chapter from AUC TeX modeline?
* Q3.3.5::      How can one change the modeline color based on the mode used?

Multiple Device Support:
* Q3.4.1::      How do I open a frame on another screen of my multi-headed display?
* Q3.4.2::      Can I really connect to a running SXEmacs after calling up over a modem?  How?

The Keyboard:
* Q3.5.1::      How can I bind complex functions (or macros) to keys?
* Q3.5.2::      How can I stop down-arrow from adding empty lines to the bottom of my buffers?
* Q3.5.3::      How do I bind C-. and C-; to scroll one line up and down?
* Q3.5.4::      Globally binding @kbd{Delete}?
* Q3.5.5::      Scrolling one line at a time.
* Q3.5.6::      How to map @kbd{Help} key alone on Sun type4 keyboard?
* Q3.5.7::      How can you type in special characters in SXEmacs?
* Q3.5.8::      [This question intentionally left blank]
* Q3.5.9::      How do I make the Delete key delete forward?
* Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
* Q3.5.11::     How do I map the arrow keys?

The Cursor:
* Q3.6.1::      Is there a way to make the bar cursor thicker?
* Q3.6.2::      Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
* Q3.6.3::      Can I make the cursor blink?

The Mouse and Highlighting:
* Q3.7.1::      How can I turn off Mouse pasting?
* Q3.7.2::      How do I set control/meta/etc modifiers on mouse buttons?
* Q3.7.3::      Clicking the left button does not do anything in buffer list.
* Q3.7.4::      How can I get a list of buffers when I hit mouse button 3?
* Q3.7.5::      Why does cut-and-paste not work between SXEmacs and a cmdtool?
* Q3.7.6::      How I can set SXEmacs up so that it pastes where the text cursor is?
* Q3.7.7::      How do I select a rectangular region?
* Q3.7.8::      Why does @kbd{M-w} take so long?

The Menubar and Toolbar:
* Q3.8.1::      How do I get rid of the menu (or menubar)?
* Q3.8.2::      Can I customise the basic menubar?
* Q3.8.3::      How do I control how many buffers are listed in the menu @code{Buffers} list?
* Q3.8.4::      Resources like @code{Emacs*menubar*font} are not working?
* Q3.8.5::      How can I bind a key to a function to toggle the toolbar?

Scrollbars:
* Q3.9.1::      How can I disable the scrollbar?
* Q3.9.2::      How can one use resources to change scrollbar colors?
* Q3.9.3::      Moving the scrollbar can move the point; can I disable this?
* Q3.9.4::      How can I turn off automatic horizontal scrolling in specific modes?

Text Selections:
* Q3.10.1::     How can I turn off or change highlighted selections?
* Q3.10.2::     How do I get that typing on an active region removes it?
* Q3.10.3::     Can I turn off the highlight during isearch?
* Q3.10.4::     How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
* Q3.10.5::     The region disappears when I hit the end of buffer while scrolling.
* Q3.10.6::     Why is killing so slow?
@end menu

@node Q3.0.1, Q3.0.2, Customisation, Customisation
@unnumberedsec 3.0: Customisation -- Emacs Lisp and @file{init.el}
@unnumberedsec Q3.0.1: What version of Emacs am I running?

How can @file{init.el} determine which of the family of
Emacsen I am using?

To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
example given in @file{etc/sample.init.el}.  There are other nifty
things in there as well!

For all new code, you can use the variables @code{running-xemacs} and
@code{running-sxemacs} or something like

@lisp
(when (featurep 'sxemacs)
  ...)
(when (featurep 'xemacs)
  ...)
@end lisp
@noindent
as well.

Please note, that you should double check these values, if you intend
to use xemacs-exclusive features.  Both, the variable
@code{running-xemacs} and the form @code{(featurep 'xemacs)} evaluate
to @code{t} within SXEmacs.  This is due to compatibility reasons.


@node Q3.0.2, Q3.0.3, Q3.0.1, Customisation
@unnumberedsec Q3.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
buffer?

Press @kbd{M-:} (the default binding of @code{eval-expression}), and
enter the expression to the minibuffer.


@node Q3.0.3, Q3.0.4, Q3.0.2, Customisation
@unnumberedsec Q3.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 for this?  If you do it at the EVAL
prompt it works fine!! How strange.

Use @code{setq-default} instead, since @code{tab-width} is
all-buffer-local.


@node Q3.0.4, Q3.0.5, Q3.0.3, Customisation
@unnumberedsec Q3.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:

@lisp
;;; Add things at the beginning of the load-path, do not add
;;; duplicate directories:
(pushnew "bar" load-path :test 'equal)

(pushnew "foo" load-path :test 'equal)

;;; Add things at the end, unconditionally
(setq load-path (nconc load-path '("foo" "bar")))
@end lisp

@email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:

@quotation
To add directories using Unix shell metacharacters use
@file{expand-file-name} like this:

@lisp
(push (expand-file-name "~keithh/.emacsdir") load-path)
@end lisp
@end quotation


@node Q3.0.5, Q3.0.6, Q3.0.4, Customisation
@unnumberedsec Q3.0.5: How to check if a lisp function is defined?

Use the following elisp:

@lisp
(fboundp 'foo)
@end lisp

It's almost always a mistake to test @code{emacs-version} or any similar
variables.

Instead, use feature-tests, such as @code{featurep}, @code{boundp},
@code{fboundp}, or even simple behavioral tests, eg.:

@lisp
(defvar foo-old-losing-code-p
  (condition-case nil (progn (losing-code t) nil)
    (wrong-number-of-arguments t)))
@end lisp

There is an incredible amount of broken code out there which could work
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 Q3.0.6, Q3.0.7, Q3.0.5, Customisation
@unnumberedsec Q3.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.

Evaluate the expression in the @samp{*scratch*} buffer with point after
the rightmost paren and typing @kbd{C-j}.

If the minibuffer smallness is the only problem you encounter, you can
simply press @kbd{C-h l} to get the former minibuffer contents in a
buffer.


@node Q3.0.7, Q3.0.8, Q3.0.6, Customisation
@unnumberedsec Q3.0.7: Font selections in don't get saved after @code{Save Options}.

@email{mannj@@ll.mit.edu, John Mann} writes:

@quotation
You have to go to Options->Frame Appearance and unselect
@samp{Frame-Local Font Menu}.  If this option is selected, font changes
are only applied to the @emph{current} frame and do @emph{not} get saved
when you save options.
@end quotation

Also, set the following in your @file{init.el}:

@lisp
(setq options-save-faces t)
@end lisp


@node Q3.0.8, Q3.0.9, Q3.0.7, Customisation
@unnumberedsec Q3.0.8: How do I get a single minibuffer frame?

@email{acs@@acm.org, Vin Shelton} writes:

@lisp
(setq initial-frame-plist '(minibuffer nil))
(setq default-frame-plist '(minibuffer nil))
(setq default-minibuffer-frame
      (make-frame
       '(minibuffer only
                    width 86
                    height 1
                    menubar-visible-p nil
                    default-toolbar-visible-p nil
                    name "minibuffer"
                    top -2
                    left -2
                    has-modeline-p nil)))
(frame-notice-user-settings)
@end lisp

@strong{Please note:} The single minibuffer frame may not be to everyone's
taste, and there any number of other SXEmacs options settings that may
make it difficult or inconvenient to use.


@node Q3.0.9, Q3.1.1, Q3.0.8, Customisation
@unnumberedsec Q3.0.9: What is @code{Customize}?

Starting with XEmacs 20.2 there is new system 'Customize' for customising
SXEmacs options.

You can access @code{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}.

Also try out with @kbd{M-x customize-browse}


@node Q3.1.1, Q3.1.2, Q3.0.9, Customisation
@unnumberedsec 3.1: X Window System & Resources
@unnumberedsec Q3.1.1: Where is a list of X resources?

Search through the @file{NEWS} file for @samp{X Resources}.  A fairly
comprehensive list is given after it.

In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
supplied, listing the defaults.  The file @file{etc/sample.Xresources}
gives a different set of defaults that you might consider for
installation in your @file{~/.Xresources} file.  It is nearly the same
as @file{etc/Emacs.ad}, but a few entries are altered.  Be careful about
installing the contents of this file into your @file{.Xresources} (or
legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.


@node Q3.1.2, Q3.1.3, Q3.1.1, Customisation
@unnumberedsec Q3.1.2: How can I detect a color display?

You can test the return value of the function @code{(device-class)}, as
in:

@lisp
(when (eq (device-class) 'color)
  (set-face-foreground  'font-lock-comment-face "Grey")
  (set-face-foreground  'font-lock-string-face  "Red")
  ....
  )
@end lisp


@node Q3.1.3, Q3.1.4, Q3.1.2, Customisation
@unnumberedsec Q3.1.3: [This question intentionally left blank]

@node Q3.1.4, Q3.1.5, Q3.1.3, Customisation
@unnumberedsec Q3.1.4: [This question intentionally left blank]


@node Q3.1.5, Q3.1.6, Q3.1.4, Customisation
@unnumberedsec Q3.1.5: How can I get the icon to just say @samp{SXEmacs}?

I'd like the icon to just say @samp{SXEmacs}, and not include the name of
the current file in it.

Add the following line to your @file{init.el}:

@lisp
(setq frame-icon-title-format "SXEmacs")
@end lisp


@node Q3.1.6, Q3.1.7, Q3.1.5, Customisation
@unnumberedsec Q3.1.6: How can I have the window title area display the full path?

I'd like to have the window title area display the full directory/name
of the current buffer file and not just the name.

Add the following line to your @file{init.el}:

@lisp
(setq frame-title-format "%S: %f")
@end lisp

A more sophisticated title might be:

@lisp
(setq frame-title-format
      '("%S: " (buffer-file-name "%f"
                                 (dired-directory dired-directory "%b"))))
@end lisp

That is, use the file name, or the dired-directory, or the buffer name.


@node Q3.1.7, Q3.1.8, Q3.1.6, Customisation
@unnumberedsec Q3.1.7: @samp{sxemacs -name junk} doesn't work?

When I run @samp{xterm -name junk}, I get an xterm whose class name
according to xprop, is @samp{junk}.  This is the way it's supposed to
work, I think.  When I run @samp{sxemacs -name junk} the class name is
not set to @samp{junk}.  It's still @samp{emacs}.  What does
@samp{sxemacs -name} really do?  The reason I ask is that my window
manager (fvwm) will make a window sticky and I use SXEmacs to read my
mail.  I want that SXEmacs window to be sticky, without having to use the
window manager's function to set the window sticky.  What gives?

@samp{sxemacs -name} sets the application name for the program (that is,
the thing which normally comes from @samp{argv[0]}).  Using @samp{-name}
is the same as making a copy of the executable with that new name.  The
@code{WM_CLASS} property on each frame is set to the frame-name, and the
application-class.  So, if you did @samp{sxemacs -name FOO} and then
created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
@code{( "BAR", "Emacs")}.  However, the resource hierarchy for this
widget would be:

@example
Name:    FOO   .shell             .container   .BAR
Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
@end example

instead of the default

@example
Name:    sxemacs.shell            .container   .emacs
Class:   Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
@end example


It is arguable that the first element of WM_CLASS should be set to the
application-name instead of the frame-name, but I think that's less
flexible, since it does not give you the ability to have multiple frames
with different WM_CLASS properties.  Another possibility would be for
the default frame name to come from the application name instead of
simply being @samp{emacs}.  However, at this point, making that change
would be troublesome: it would mean that many users would have to make
yet another change to their resource files (since the default frame name
would suddenly change from @samp{emacs} to @samp{sxemacs}, or whatever
the executable happened to be named), so we'd rather avoid it.

To make a frame with a particular name use:

@lisp
(make-frame '((name . "the-name")))
@end lisp


@node Q3.1.8, Q3.2.1, Q3.1.7, Customisation
@unnumberedsec Q3.1.8: @samp{-iconic} doesn't work.

When I start up SXEmacs using @samp{-iconic} it doesn't work right.
Using @samp{-unmapped} on the command line, and setting the
@code{initiallyUnmapped} X Resource don't seem to help much either...

@email{ben@@xemacs.org, Ben Wing} writes:

@quotation
Ugh, this stuff is such an incredible mess that I've about given up
getting it to work.  The principal problem is numerous window-manager
bugs...
@end quotation


@node Q3.2.1, Q3.2.2, Q3.1.8, Customisation
@unnumberedsec 3.2: Textual Fonts & Colors
@unnumberedsec Q3.2.1: How can I set color options from @file{init.el}?

How can I set the most commonly used color options from my
@file{init.el} instead of from my @file{.Xresources}?

Like this: