INFO-DIR-SECTION XEmacs Editor
START-INFO-DIR-ENTRY
-* FAQ: (xemacs-faq). XEmacs FAQ.
+* FAQ: (xemacs-faq). XEmacs FAQ.
END-INFO-DIR-ENTRY
\1f
This is the guide to the XEmacs Frequently Asked Questions list--a
compendium of questions and answers pertaining to one of the finest
-programs ever written. It is much more than just a Text Editor.
+programs ever written. XEmacs is much more than just a Text Editor.
- This FAQ is freely redistributable. I take no liability for the
-correctness and safety of any procedures or advice given here. 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.
+ 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.
If you have a Web browser, the official hypertext version is at
-`http://www.xemacs.org/faq/xemacs-faq.html'.
-
- This version is somewhat nicer than the unofficial hypertext versions
-that are archived at Utrecht, Oxford, Smart Pages, and other FAQ
-archives.
+`http://www.xemacs.org/faq/xemacs-faq.html'
* Menu:
* Q1.0.4:: Why Another Version of Emacs?
* Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
* Q1.0.6:: Where can I get help?
-* Q1.0.7:: Where is the mailing list archived?
+* Q1.0.7:: Where are the mailing lists archived?
* Q1.0.8:: How do you pronounce XEmacs?
* Q1.0.9:: What does XEmacs look like?
* Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
* Q1.2.3:: Who contributed to the FAQ in the past?
Internationalization:
-* Q1.3.1:: What is the status of XEmacs v20?
-* Q1.3.2:: What is the status of Asian-language support, aka MULE?
+* Q1.3.1:: What is the status of internationalization support aka MULE (including Asian language support?
+* Q1.3.2:: How can I help with internationalization?
* Q1.3.3:: How do I type non-ASCII characters?
* Q1.3.4:: Can XEmacs messages come out in a different language?
-* Q1.3.5:: Please explain the various input methods in MULE/XEmacs 20.0
-* Q1.3.6:: How do I portably code for MULE/XEmacs 20.0?
+* Q1.3.5:: Please explain the various input methods in MULE/XEmacs
+* Q1.3.6:: How do I portably code for MULE/XEmacs?
* Q1.3.7:: How about Cyrillic Modes?
Getting Started:
-* Q1.4.1:: What is a `.emacs' and is there a sample one?
-* Q1.4.2:: Can I use the same `.emacs' with the other Emacs?
+* Q1.4.1:: What is an `init.el' or `.emacs' and is there a sample one?
+* Q1.4.2:: Can I use the same `init.el'/`.emacs' with the other Emacs?
* Q1.4.3:: Any good XEmacs tutorials around?
* Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
* Q1.4.5:: And how do I bind it to a key?
* Q2.0.10:: After I run configure I find a coredump, is something wrong?
* Q2.0.11:: XEmacs can't resolve host names.
* Q2.0.12:: Why can't I strip XEmacs?
+* Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
+* Q2.0.14:: How do I figure out which packages to install? (NEW)
Trouble Shooting:
* Q2.1.1:: XEmacs just crashed on me!
* Q2.1.22:: XEmacs seems to take a really long time to do some things.
* Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
* Q2.1.24:: XEmacs won't start without network. (NEW)
+* Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
Customization and Options
* Q3.1.8:: `-iconic' doesn't work.
Textual Fonts & Colors:
-* Q3.2.1:: How can I set color options from `.emacs'?
+* Q3.2.1:: How can I set color options from `init.el'/`.emacs'?
* 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.5.5:: Scrolling one line at a time.
* Q3.5.6:: How to map Help key alone on Sun type4 keyboard?
* Q3.5.7:: How can you type in special characters in XEmacs?
-* Q3.5.8:: Why does `(global-set-key [delete-forward] 'delete-char)' complain?
+* 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 "sticky" modifier keys?
* Q3.5.11:: How do I map the arrow keys?
* 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 get automatic horizontal scrolling?
+* 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?
* 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 `More' Syntax Highlighting on by default?
-* Q5.0.4:: How can I enable auto-indent?
+* Q5.0.4:: How can I enable auto-indent and/or Filladapt?
* Q5.0.5:: How can I get XEmacs 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:: How do I turn on filladapt for all buffers?
+* 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 XEmacs is a client?
* Q5.0.14:: Strange things are happening in Shell Mode.
* Q5.1.4:: What is the performance hit of `let'?
* Q5.1.5:: What is the recommended use of `setq'?
* Q5.1.6:: What is the typical misuse of `setq' ?
-* Q5.1.7:: I like the the `do' form of cl, does it slow things down?
+* Q5.1.7:: I like the `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:: `map-extents' won't traverse all of my extents!
Miscellaneous:
* Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
-* Q5.3.2:: Fontifying hangs when editing a postscript file.
+* Q5.3.2:: [This question intentionally left blank]
* Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
* Q5.3.4:: Getting M-x lpr to work with postscript printer.
* Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
XEmacs on MS Windows
General Info:
-* Q6.0.1:: What is the status of the XEmacs port to Windows?
-* Q6.0.2:: What flavors of MS Windows are supported?
-* Q6.0.3:: Are binary kits available?
-* Q6.0.4:: Does XEmacs on MS Windows require an X server to run?
+* Q6.0.1:: What is the status of the XEmacs port to Windows?
+* Q6.0.2:: What flavors of MS Windows are supported?
+* Q6.0.3:: Are binaries available?
+* Q6.0.4:: Can I build XEmacs on MS Windows with support for X or Cygwin?
Building XEmacs on MS Windows:
-* Q6.1.1:: I decided to run with X. Where do I get an X server?
-* Q6.1.2:: What compiler do I need to compile XEmacs?
-* Q6.1.3:: How do I compile for the native port?
-* Q6.1.4:: How do I compile for the X port?
-* Q6.1.5:: How do I compile for Cygnus' Cygwin?
-* Q6.1.6:: What do I need for Cygwin?
+* Q6.1.1:: I decided to run with X. Where do I get an X server?
+* Q6.1.2:: What compiler do I need to compile XEmacs?
+* Q6.1.3:: How do I compile for the native port?
+* Q6.1.4:: How do I compile for the X port?
+* Q6.1.5:: How do I compile for Cygnus' Cygwin?
+* Q6.1.6:: What do I need for Cygwin?
Customization and User Interface:
-* Q6.2.1:: How will the port cope with differences in the Windows user interface?
-* Q6.2.2:: How do I change fonts in XEmacs on MS Windows?
-* Q6.2.3:: Where do I put my `.emacs' file?
+* Q6.2.1:: How will the port cope with differences in the Windows user interface?
+* Q6.2.2:: How do I change fonts in XEmacs on MS Windows?
+* Q6.2.3:: Where do I put my `init.el'/`.emacs' file?
Miscellaneous:
-* Q6.3.1:: Will XEmacs rename all the win32-* symbols to w32-*?
-* Q6.3.2:: What are the differences between the various MS Windows emacsen?
-* Q6.3.3:: What is the porting team doing at the moment?
+* Q6.3.1:: Will XEmacs rename all the win32-* symbols to w32-*?
+* Q6.3.2:: What are the differences between the various MS Windows emacsen?
+* Q6.3.3:: What is the porting team doing at the moment?
+
+Troubleshooting:
+* Q6.4.1:: XEmacs won't start on Windows. (NEW)
Current Events:
* Q1.0.4:: Why Another Version of Emacs?
* Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
* Q1.0.6:: Where can I get help?
-* Q1.0.7:: Where is the mailing list archived?
+* Q1.0.7:: Where are the mailing lists archived?
* Q1.0.8:: How do you pronounce XEmacs?
* Q1.0.9:: What does XEmacs look like?
* Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
* Q1.2.3:: Who contributed to the FAQ in the past?
Internationalization:
-* Q1.3.1:: What is the status of XEmacs v20?
-* Q1.3.2:: What is the status of Asian-language support, aka MULE?
+* Q1.3.1:: What is the status of internationalization support aka MULE (including Asian language support?
+* Q1.3.2:: How can I help with internationalization?
* Q1.3.3:: How do I type non-ASCII characters?
* Q1.3.4:: Can XEmacs messages come out in a different language?
-* Q1.3.5:: Please explain the various input methods in MULE/XEmacs 20.0
-* Q1.3.6:: How do I portably code for MULE/XEmacs 20.0?
+* Q1.3.5:: Please explain the various input methods in MULE/XEmacs
+* Q1.3.6:: How do I portably code for MULE/XEmacs?
* Q1.3.7:: How about Cyrillic Modes?
Getting Started:
-* Q1.4.1:: What is a `.emacs' and is there a sample one?
-* Q1.4.2:: Can I use the same `.emacs' with the other Emacs?
+* Q1.4.1:: What is an `init.el' or `.emacs' and is there a sample one?
+* Q1.4.2:: Can I use the same `init.el'/`.emacs' with the other Emacs?
* Q1.4.3:: Any good XEmacs tutorials around?
* Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
* Q1.4.5:: And how do I bind it to a key?
Q1.0.1: What is XEmacs?
-----------------------
- An alternative to GNU Emacs, originally based on an early alpha
-version of FSF's version 19, and has diverged quite a bit since then.
-XEmacs was known as Lucid Emacs through version 19.10. Almost all
-features of GNU Emacs are supported in XEmacs. The maintainers of
-XEmacs actively track changes to GNU Emacs while also working to add
-new features.
+ XEmacs is a highly customizable open source text editor and
+application development system. It is protected under the GNU Public
+License and related to other versions of Emacs, in particular GNU
+Emacs. Its emphasis is on modern graphical user interface support and
+an open software development model, similar to Linux. XEmacs has an
+active development community numbering in the hundreds, and runs on
+Windows 95 and NT, Linux and nearly every other version of Unix in
+existence. Support for XEmacs has been supplied by Sun Microsystems,
+University of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
+Corporation, BeOpen, and others, as well as the unpaid time of a great
+number of individual developers.
\1f
File: xemacs-faq.info, Node: Q1.0.2, Next: Q1.0.3, Prev: Q1.0.1, Up: Introduction
Q1.0.2: What is the current version of XEmacs?
----------------------------------------------
- XEmacs 21.1.8 is the current stable version of XEmacs.
-
- XEmacs 20.4 is a minor upgrade from 20.3, containing many bugfixes.
-It was released in February 1998.
+ XEmacs versions 21.1.* are releases made from the current stable
+sources. XEmacs versions 21.2.* are releases made from the development
+sources. Check at `http://www.xemacs.org' for the current minor
+version.
XEmacs 19.16 was the last release of v19, released in November, 1997,
which was also the last version without international language support.
* The XEmacs maintainers are generally more receptive to suggestions
than the GNU Emacs maintainers.
- * Many more bundled packages than GNU Emacs
+ * Many more bundled packages than GNU Emacs.
* Binaries are available for many common operating systems.
* Better Motif compliance.
* Some internationalization support (including full MULE support, if
- compiled with it.)
+ compiled with it).
* Variable-width fonts.
* Completely compatible (at the C level) with the Xt-based toolkits.
- * First production Web Browser supporting Style Sheets.
\1f
File: xemacs-faq.info, Node: Q1.0.5, Next: Q1.0.6, Prev: Q1.0.4, Up: Introduction
-----------------------------
Probably the easiest way, if everything is installed, is to use
-Info, by pressing `C-h i', or selecting `Manuals->Info' from the Help
+Info, by pressing `C-h i', or looking for an Info item on the Help
Menu. `M-x apropos' can be used to look for particular commands.
For items not found in the manual, try reading this FAQ and reading
\1f
File: xemacs-faq.info, Node: Q1.0.7, Next: Q1.0.8, Prev: Q1.0.6, Up: Introduction
-Q1.0.7: Where is the mailing list archived?
--------------------------------------------
+Q1.0.7: Where are the mailing lists archived?
+---------------------------------------------
- The archives can be found at `http://www.xemacs.org/Lists/Archive'
+ The archives can be found at `http://list-archive.xemacs.org'
\1f
File: xemacs-faq.info, Node: Q1.0.8, Next: Q1.0.9, Prev: Q1.0.7, Up: Introduction
----------------------------------------------------
Yes, there is a port of XEmacs 19.14, tested on MacOS 7.6.1 and MacOS
-8.5.1 by Pitts Jarvis (pjarvis@ispchannel.com). It's available at
-http://my.ispchannel.com/~pjarvis/xemacs.html
-(http://my.ispchannel.com/~pjarvis/xemacs.html).
+8.5.1 by Pitts Jarvis <pjarvis@ispchannel.com>. It's available at
+`http://homepage.mac.com/pjarvis/xemacs.html'.
\1f
File: xemacs-faq.info, Node: Q1.0.12, Next: Q1.0.13, Prev: Q1.0.11, Up: Introduction
\1f
File: xemacs-faq.info, Node: Q1.0.14, Next: Q1.1.1, Prev: Q1.0.13, Up: Introduction
-Q1.0.14: Where can I obtain a printed copy of the XEmacs users manual?
-----------------------------------------------------------------------
+Q1.0.14: Where can I obtain a printed copy of the XEmacs User's Manual?
+-----------------------------------------------------------------------
Pre-printed manuals are not available. If you are familiar with
TeX, you can generate your own manual from the XEmacs sources.
HTML and Postscript versions of XEmacs manuals may be available from
-the XEmacs web site in the future.
+the XEmacs web site in the future. Send requests to <faq@xemacs.org>.
\1f
File: xemacs-faq.info, Node: Q1.1.1, Next: Q1.1.2, Prev: Q1.0.14, Up: Introduction
Please make sure that `XEmacs FAQ' appears on the Subject: line. 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. Questions and
-answers included into the FAQ will be edited for spelling and grammar,
+answers included into the FAQ will be edited for spelling and grammar
and will be attributed. Answers appearing without attribution are
-either from versions of the FAQ dated before May 1996, or are from one
-of the four people listed at the top of this document. Answers quoted
-from Usenet news articles will always be attributed, regardless of the
-author.
+either from versions of the FAQ dated before May 1996 or are from
+previous FAQ maintainers. Answers quoted from Usenet news articles will
+always be attributed, regardless of the author.
\1f
File: xemacs-faq.info, Node: Q1.1.2, Next: Q1.1.3, Prev: Q1.1.1, Up: Introduction
-------------------------
XEmacs is the result of the time and effort of many people. The
-developers responsible for the 19.16/20.x releases are:
+developers responsible for recent releases are:
* Martin Buchholz <martin@xemacs.org>
- * Steve Baur <steve@xemacs.org>
+ * Steven Turnbull <turnbull@sk.tsukuba.ac.jp>
+
+ * Ben Wing <ben@xemacs.org>
* Hrvoje Niksic <hniksic@xemacs.org>
- The developers responsible for the 19.14 release are:
+ The developers responsible for older releases were:
+
+ * Steve Baur <steve@xemacs.org>
* Chuck Thompson <cthomp@xemacs.org>
- Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible
- for XEmacs becoming a widely distributed program over the Internet.
+ * Jamie Zawinski <jwz@jwz.org>
- * Ben Wing <ben@xemacs.org>
+ * Richard Mlynarik <mly@adoc.xerox.com>
+ Steve Baur was the primary maintainer for 19.15 through 21.0.
- * Jamie Zawinski <jwz@jwz.org>
+ Chuck Thompson and Ben Wing were the maintainers for 19.11 through
+ 19.14 and heavy code contributors for 19.8 through 19.10.
- Jamie Zawinski was Mr. Lucid Emacs from 19.0 through 19.10, the
- last release actually named Lucid Emacs. Richard Mlynarik was
- crucial to most of those releases.
+ Jamie Zawinski was the maintainer for 19.0 through 19.10 (the
+ entire history of Lucid Emacs). Richard Mlynarik was a heavy code
+ contributor to 19.6 through 19.8.
- * Richard Mlynarik <mly@adoc.xerox.com>
Along with many other contributors, partially enumerated in the
`About XEmacs' option in the Help menu.
1.3: Internationalization
=========================
-Q1.3.1: What is the status of XEmacs v20?
------------------------------------------
+Q1.3.1: What is the status of internationalization support aka MULE (including Asian language support?
+------------------------------------------------------------------------------------------------------
- XEmacs v20 is the version of XEmacs that includes MULE
-(Asian-language) support. XEmacs 20.0 was released in February 1997,
-followed by XEmacs 20.2 in May, XEmacs 20.3 in November and XEmacs 20.4
-in February 1998. When compiled without MULE support, 20.4 is
-approximately as stable as 19.16, and probably faster (due to
-additional optimization work.)
-
- As of XEmacs 20.3, version 20 is _the_ supported version of XEmacs.
-This means that 19.16 will optionally receive stability fixes (if any),
-but that all the real development work will be done on the v20 tree.
-
- The incompatible changes in XEmacs 20 include the additional
-byte-codes, new primitive data types (`character', `char-table', and
-`range-table'). This means that the character-integer equivalence
-inherent to all the previous Emacs and XEmacs releases no longer
-applies.
-
- However, to avoid breaking old code, many functions that should
-normally accept characters work with integers, and vice versa. For more
-information, see the Lisp reference manual. Here is a relevant excerpt,
-for your convenience.
-
- In XEmacs version 19, and in all versions of FSF GNU Emacs, a
- "character" in XEmacs Lisp is nothing more than an integer. This
- is yet another holdover from XEmacs Lisp's derivation from
- vintage-1980 Lisps; modern versions of Lisp consider this
- equivalence a bad idea, and have separate character types. In
- XEmacs version 20, the modern convention is followed, and
- characters are their own primitive types. (This change was
- necessary in order for MULE, i.e. Asian-language, support to be
- correctly implemented.)
-
- Even in XEmacs version 20, remnants of the equivalence between
- characters and integers still exist; this is termed the "char-int
- confoundance disease". In particular, many functions such as `eq',
- `equal', and `memq' have equivalent functions (`old-eq',
- `old-equal', `old-memq', etc.) that pretend like characters are
- integers are the same. Byte code compiled under any version 19
- Emacs will have all such functions mapped to their `old-'
- equivalents when the byte code is read into XEmacs 20. This is to
- preserve compatibility - Emacs 19 converts all constant characters
- to the equivalent integer during byte-compilation, and thus there
- is no other way to preserve byte-code compatibility even if the
- code has specifically been written with the distinction between
- characters and integers in mind.
-
- Every character has an equivalent integer, called the "character
- code". For example, the character `A' is represented as the
- integer 65, following the standard ASCII representation of
- characters. If XEmacs was not compiled with MULE support, the
- range of this integer will always be 0 to 255 - eight bits, or one
- byte. (Integers outside this range are accepted but silently
- truncated; however, you should most decidedly _not_ rely on this,
- because it will not work under XEmacs with MULE support.) When
- MULE support is present, the range of character codes is much
- larger. (Currently, 19 bits are used.)
-
- FSF GNU Emacs uses kludgy character codes above 255 to represent
- keyboard input of ASCII characters in combination with certain
- modifiers. XEmacs does not use this (a more general mechanism is
- used that does not distinguish between ASCII keys and other keys),
- so you will never find character codes above 255 in a non-MULE
- XEmacs.
-
- Individual characters are not often used in programs. It is far
- more common to work with _strings_, which are sequences composed of
- characters.
+ Both the stable and development versions of XEmacs include
+internationalization support (aka MULE). MULE currently works on UNIX
+and Linux systems; work for supporting MULE on Windows operating systems
+is in progress. Binaries compiled without MULE support run faster than
+MULE capable XEmacsen.
\1f
File: xemacs-faq.info, Node: Q1.3.2, Next: Q1.3.3, Prev: Q1.3.1, Up: Introduction
-Q1.3.2: What is the status of Asian-language support, aka MULE?
----------------------------------------------------------------
-
- MULE support is now available for UNIX versions of XEmacs.
+Q1.3.2: How can I help with internationalization?
+-------------------------------------------------
If you would like to help, you may want to join the
<xemacs-mule@xemacs.org> mailing list. Especially needed are people
The message-catalog support has mostly been written but doesn't
currently work. The first release of XEmacs 20 will _not_ support it.
-However, menubar localization _does_ work, even in 19.14. To enable
-it, add to your `Emacs' file entries like this:
+However, menubar localization _does_ work. To enable it, add to your
+`Emacs' file entries like this:
- Emacs*XlwMenu.resourceLabels: True
- Emacs*XlwMenu.file.labelString: Fichier
- Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster offnen
+ Emacs*XlwMenu.resourceLabels: True
+ Emacs*XlwMenu.file.labelString: Fichier
+ Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
The name of the resource is derived from the non-localized entry by
removing punctuation and capitalizing as above.
\1f
File: xemacs-faq.info, Node: Q1.3.5, Next: Q1.3.6, Prev: Q1.3.4, Up: Introduction
-Q1.3.5: Please explain the various input methods in MULE/XEmacs 20.0
---------------------------------------------------------------------
+Q1.3.5: Please explain the various input methods in MULE/XEmacs
+---------------------------------------------------------------
MORIOKA Tomohiko <morioka@jaist.ac.jp> writes:
\1f
File: xemacs-faq.info, Node: Q1.3.6, Next: Q1.3.7, Prev: Q1.3.5, Up: Introduction
-Q1.3.6: How do I portably code for MULE/XEmacs 20?
---------------------------------------------------
+Q1.3.6: How do I portably code for MULE/XEmacs?
+-----------------------------------------------
MORIOKA Tomohiko <morioka@jaist.ac.jp> writes:
(cond ((boundp 'MULE)
;; for original Mule
)
- ((string-match "XEmacs" emacs-version)
- ;; for XEmacs with Mule
- )
- (t
- ;; for next version of Emacs
- ))
+ ((string-match "XEmacs" emacs-version)
+ ;; for XEmacs with Mule
+ )
+ (t
+ ;; for next version of Emacs
+ ))
;; for old emacs variants
)
1.4: Getting Started, Backing up & Recovery
===========================================
-Q1.4.1: What is a `.emacs' and is there a sample one?
------------------------------------------------------
-
- The `.emacs' file is used to customize XEmacs to your tastes. No
-two are alike, nor are they expected to be alike, but that's the point.
-The XEmacs distribution contains an excellent starter example in the etc
-directory called `sample.emacs'. Copy this file from there to your
-home directory and rename it `.emacs'. Then edit it to suit.
-
- Starting with 19.14, you may bring the `sample.emacs' into an XEmacs
-buffer by selecting `Help->Sample .emacs' from the menubar. To
-determine the location of the `etc' directory type the command `C-h v
+Q1.4.1: What is an `init.el' or `.emacs' and is there a sample one?
+-------------------------------------------------------------------
+
+ The `init.el' or `.emacs' file is used to customize XEmacs to your
+tastes. Starting in 21.4, the preferred location for the init file is
+`~/.xemacs/init.el'; in previous versions, it was `~/.emacs'. 21.4
+still accepts the old location, but the first time you run it, it will
+ask to migrate your file to the new location. If you answer yes, the
+file will be moved, and a "compatibility" `.emacs' file will be placed
+in the old location so that you can still run older versions of XEmacs,
+and versions of GNU Emacs, which expect the old location. The `.emacs'
+file present is just a stub that loads the real file in
+`~/.xemacs/init.el'.
+
+ No two init files are alike, nor are they expected to be alike, but
+that's the point. The XEmacs distribution contains an excellent starter
+example in the `etc/' directory called `sample.init.el' (starting in
+21.4) or `sample.emacs' in older versions. Copy this file from there
+to `~/.xemacs/init.el' (starting in 21.4) or `~/.emacs' in older
+versions, where `~' means your home directory, of course. Then edit it
+to suit.
+
+ You may bring the `sample.init.el' or `sample.emacs' file into an
+XEmacs buffer from the menubar. (The menu entry for it is always under
+the `Help' menu, but its location under that has changed in various
+versions. Recently, look under the `Samples' submenu.) To determine
+the location of the `etc/' directory type the command `C-h v
data-directory <RET>'.
\1f
File: xemacs-faq.info, Node: Q1.4.2, Next: Q1.4.3, Prev: Q1.4.1, Up: Introduction
-Q1.4.2: Can I use the same `.emacs' with the other Emacs?
----------------------------------------------------------
+Q1.4.2: Can I use the same `init.el'/`.emacs' with the other Emacs?
+-------------------------------------------------------------------
- Yes. The sample `.emacs' included in the XEmacs distribution will
-show you how to handle different versions and flavors of Emacs.
+ Yes. The sample `init.el'/`.emacs' included in the XEmacs
+distribution will show you how to handle different versions and flavors
+of Emacs.
\1f
File: xemacs-faq.info, Node: Q1.4.3, Next: Q1.4.4, Prev: Q1.4.2, Up: Introduction
* Q2.0.10:: After I run configure I find a coredump, is something wrong?
* Q2.0.11:: XEmacs can't resolve host names.
* Q2.0.12:: Why can't I strip XEmacs?
+* Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
+* Q2.0.14:: I don't want to install a million .els one at a time! (NEW)
Trouble Shooting:
* Q2.1.1:: XEmacs just crashed on me!
* Q2.1.22:: XEmacs seems to take a really long time to do some things.
* Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
* Q2.1.24:: XEmacs won't start without network. (NEW)
+* Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
\1f
File: xemacs-faq.info, Node: Q2.0.1, Next: Q2.0.2, Prev: Installation, Up: Installation
Q2.0.1: Running XEmacs without installing
-----------------------------------------
- The `INSTALL' file says that up to 108 MB of space is needed
-temporarily during installation! How can I just try it out?
+ How can I just try XEmacs without installing it?
XEmacs will run in place without requiring installation and copying
of the Lisp directories, and without having to specify a special
This will let you run XEmacs without massive copying.
+\1f
+File: xemacs-faq.info, Node: Q2.0.2, Next: Q2.0.3, Prev: Q2.0.1, Up: Installation
+
+Q2.0.2: XEmacs 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. _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.
+
+ Possible candidates for deletion include w3, games, hyperbole, mh-e,
+hm-html-menus, vm, viper, oobr, gnus, etc. Ask yourself, _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 XEmacs and do whatever it is
+you normally do. If nothing bad happens, then delete the directory. Be
+conservative about deleting directories, and it would be handy to have a
+backup around in case you get too zealous.
+
+ `prim', `modes', `packages', and `utils' are four directories you
+definitely do *not* want to delete, although certain packages can be
+removed from them if you do not use them.
+
+ Online texinfo sources in the `info' can either be compressed them
+or remove them. In either case, `C-h i' (info mode) will no longer
+work.
+
projects / chise / xemacs-chise.git / blobdiff