-This is ../info/xemacs-faq.info, produced by makeinfo version 4.0 from
-xemacs-faq.texi.
+This is Info file ../info/xemacs-faq.info, produced by Makeinfo version
+1.68 from the input file xemacs-faq.texi.
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. XEmacs is much more than just a Text Editor.
+programs ever written. It is much more than just a Text Editor.
- 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.
+ 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.
If you have a Web browser, the official hypertext version is at
-`http://www.xemacs.org/faq/xemacs-faq.html'
+`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.
* Menu:
* Customization:: Customization and Options.
* Subsystems:: Major Subsystems.
* Miscellaneous:: The Miscellaneous Stuff.
-* MS Windows:: XEmacs on Microsoft Windows.
* Current Events:: What the Future Holds.
- --- The Detailed Node Listing ---
+ -- The Detailed Node Listing --
Introduction, Policy, Credits
* 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 are the mailing lists archived?
+* Q1.0.7:: Where is the mailing list 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 internationalization support aka MULE (including Asian language support?
-* Q1.3.2:: How can I help with 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.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
-* Q1.3.6:: How do I portably code for MULE/XEmacs?
+* 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.7:: How about Cyrillic Modes?
Getting Started:
* 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.4.6:: What's the difference between a macro and a function?
+* Q1.4.7:: Why options saved with 19.13 don't work with 19.14 or later?
Installation and Trouble Shooting
* 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)
+* Q2.0.13:: Can't link XEmacs on Solaris with Gcc.
+* Q2.0.14:: Make on HP/UX 9 fails after linking temacs
Trouble Shooting:
* Q2.1.1:: XEmacs just crashed on me!
* 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 `create_process' failure
-* Q2.1.14:: C-g doesn't work for me. Is it broken?
+* Q2.1.14:: `C-g' doesn't work for me. Is it broken?
* Q2.1.15:: How to debug an XEmacs problem with a debugger.
* Q2.1.16:: XEmacs crashes in `strcat' on HP/UX 10.
* Q2.1.17:: `Marker does not point anywhere'.
-* Q2.1.18:: [This question intentionally left blank]
+* Q2.1.18:: 19.14 hangs on HP/UX 10.10.
* Q2.1.19:: XEmacs does not follow the local timezone.
* Q2.1.20:: `Symbol's function definition is void: hkey-help-show.'
-* Q2.1.21:: [This question intentionally left blank]
+* Q2.1.21:: Every so often the XEmacs frame freezes.
* 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
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.3:: `(set-screen-width)' worked in 19.6, but not in 19.13?
+* Q3.1.4:: Specifying `Emacs*EmacsScreen.geometry' in `.emacs' does not work in 19.15?
* Q3.1.5:: How can I get the icon to just say `XEmacs'?
* Q3.1.6:: How can I have the window title area display the full path?
* Q3.1.7:: `xemacs -name junk' doesn't work?
* 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 Delete?
+* Q3.5.4:: Globally binding `Delete'?
* Q3.5.5:: Scrolling one line at a time.
-* Q3.5.6:: How to map Help key alone on Sun type4 keyboard?
+* 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.9:: How do I make the Delete key delete forward?
* Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
* Q3.7.6:: How I can set XEmacs 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 M-w take so long?
+* Q3.7.8:: Why does `M-w' take so long?
The Menubar and Toolbar:
* Q3.8.1:: How do I get rid of the menu (or menubar)?
* 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 C-x C-p (mark-page)?
+* Q3.10.4:: How do I turn off highlighting after `C-x C-p' (mark-page)?
* Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
Major Subsystems
Sparcworks, EOS, and WorkShop:
* Q4.4.1:: What is SPARCworks, EOS, and WorkShop
-* Q4.4.2:: How do I start the Sun Workshop support in XEmacs 21?
Energize:
* Q4.5.1:: What is/was Energize?
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.3:: Byte compiling AUC TeX on XEmacs 19.14
* Q4.7.4:: Problems installing AUC TeX
* Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
* Q4.7.6:: Is there a MatLab mode?
* 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:: Filladapt doesn't work in 19.15?
* 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.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.18:: I upgraded to XEmacs 19.14 and gnuserv stopped working
* Q5.0.19:: Is there something better than LaTeX mode?
* Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
* 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 `do' form of cl, does it slow things down?
+* Q5.1.7:: I like the 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!
* 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.3:: How can I print WYSIWYG a font-locked buffer?
-* Q5.3.4:: Getting M-x lpr to work with postscript printer.
+* 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?
* 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.11:: How do I add new Info directories?
* Q5.3.12:: What do I need to change to make printing work?
-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?
-
-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?
-
-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?
-
-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?
-
-Troubleshooting:
-* Q6.4.1:: XEmacs won't start on Windows. (NEW)
-
-Current Events:
+What the Future Holds
-* Q7.0.1:: What is new in 20.2?
-* Q7.0.2:: What is new in 20.3?
-* Q7.0.3:: What is new in 20.4?
-* Q7.0.4:: Procedural changes in XEmacs development.
+* Q6.0.1:: What is new in 20.2?
+* Q6.0.2:: What is new in 20.3?
+* Q6.0.3:: What is new in 20.4?
+* Q6.0.4:: Procedural changes in XEmacs development.
\1f
File: xemacs-faq.info, Node: Introduction, Next: Installation, Prev: Top, Up: Top
wondering what to do next. It is also useful as a reference to
available resources.
- The previous maintainer of the FAQ was Anthony Rossini
-<rossini@biostat.washington.edu>, who started it, after getting tired
-of hearing JWZ complain about repeatedly having to answer questions.
-Ben Wing <ben@xemacs.org> and Chuck Thompson <cthomp@xemacs.org>, the
-principal authors of XEmacs, then took over and Ben did a massive
-update reorganizing the whole thing. At which point Anthony took back
-over, but then had to give it up again. Some of the other contributors
-to this FAQ are listed later in this document.
+ The previous maintainer of the FAQ was Anthony Rossini <rossini@stat.sc.edu>, who started it, after getting tired of hearing JWZ complain
+about repeatedly having to answer questions. Ben Wing <ben@666.com>
+and Chuck Thompson <cthomp@xemacs.org>, the principal authors of
+XEmacs, then took over and Ben did a massive update reorganizing the
+whole thing. At which point Anthony took back over, but then had to
+give it up again. Some of the other contributors to this FAQ are
+listed later in this document.
The previous version was converted to hypertext format, and edited by
-Steven L. Baur <steve@xemacs.org>. It was converted back to texinfo by
-Hrvoje Niksic <hniksic@xemacs.org>. The FAQ was then maintained by
-Andreas Kaempf <andreas@sccon.com>, who passed it on to ChristianNyb/o.
+Steven L. Baur <steve@altair.xemacs.org>. It was converted back to
+texinfo by Hrvoje Niksic <hniksic@srce.hr>.
+
+ The FAQ was then maintained by Andreas Kaempf <andreas@sccon.com>,
+who passed it on to Christian Nybo/ <faq@xemacs.org>, the current FAQ
+maintainer.
If you notice any errors or items which should be added or amended to
-this FAQ please send email to Sandra Wambold <faq@xemacs.org>. Include
+this FAQ please send email to Christian Nybo/ <faq@xemacs.org>. Include
`XEmacs FAQ' on the Subject: line.
* 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 are the mailing lists archived?
+* Q1.0.7:: Where is the mailing list 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 internationalization support aka MULE (including Asian language support?
-* Q1.3.2:: How can I help with 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.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
-* Q1.3.6:: How do I portably code for MULE/XEmacs?
+* 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.7:: How about Cyrillic Modes?
Getting Started:
* 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.4.6:: What's the difference between a macro and a function?
+* Q1.4.7:: Why options saved with 19.13 don't work with 19.14 or later?
\1f
File: xemacs-faq.info, Node: Q1.0.1, Next: Q1.0.2, Prev: Introduction, Up: Introduction
Q1.0.2: What is the current version of XEmacs?
----------------------------------------------
- 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 20.4 is a minor upgrade from 20.3, containing many bugfixes.
+It was released in February 1998.
XEmacs 19.16 was the last release of v19, released in November, 1997,
which was also the last version without international language support.
Q1.0.3: Where can I find it?
----------------------------
- The canonical source and binaries can be found via anonymous FTP at:
+ The canonical source and binaries is found via anonymous FTP at:
`ftp://ftp.xemacs.org/pub/xemacs/'
For a detailed description of the differences between GNU Emacs and
XEmacs and a detailed history of XEmacs, check out the
- NEWS file (http://www.xemacs.org/About/XEmacsVsGNUemacs.html)
+ NEWS file (http://www.xemacs.org/NEWS.html)
However, here is a list of some of the reasons why we think you might
consider using it:
-----------------------------
Probably the easiest way, if everything is installed, is to use
-Info, by pressing `C-h i', or selecting `Manuals->Info' from the Help
-Menu. `M-x apropos' can be used to look for particular commands.
+info, by pressing `C-h i', or selecting `Manuals->Info' from the Help
+Menu.
- For items not found in the manual, try reading this FAQ and reading
-the Usenet group comp.emacs.xemacs.
+ Also, `M-x apropos' will look for commands for you.
- If you choose to post to a newsgroup, *please use
-comp.emacs.xemacs*. Please do not post XEmacs related questions to
+ Try reading this FAQ, examining the regular GNU Emacs FAQ (which can
+be found with the Emacs 19 distribution) as well as at
+`http://www.eecs.nwu.edu/emacs/faq/' and reading the Usenet group
+comp.emacs.xemacs.
+
+ If that does not help, try posting your question to
+comp.emacs.xemacs. Please *do not* post XEmacs related questions to
gnu.emacs.help.
If you cannot post or read Usenet news, there is a corresponding
mailing list which is available. It can be subscribed to by sending a
-message to <xemacs-request@xemacs.org> with `subscribe' in the body of
-the message. Send to the list at <xemacs@xemacs.org>. list. To
-cancel a subscription, you *must* use the xemacs-request address. Send
-a message with a subject of `unsubscribe' to be removed.
+message with a subject of `subscribe' to <xemacs-request@xemacs.org>
+for subscription information and <xemacs@xemacs.org> to send messages
+to the list.
+
+ To cancel a subscription, you *must* use the xemacs-request address.
+Send a message with a subject of `unsubscribe' to be removed.
\1f
File: xemacs-faq.info, Node: Q1.0.7, Next: Q1.0.8, Prev: Q1.0.6, Up: Introduction
-Q1.0.7: Where are the mailing lists archived?
----------------------------------------------
+Q1.0.7: Where is the mailing list archived?
+-------------------------------------------
+
+ The mailing list was archived in the directory
+ `ftp://ftp.xemacs.org/pub/mlists/'.
- The archives can be found at `http://www.xemacs.org/Lists/Archive'
+ However, this archive is out of date. The current mailing list
+server supports an `archive' feature, which may be utilized.
\1f
File: xemacs-faq.info, Node: Q1.0.8, Next: Q1.0.9, Prev: Q1.0.7, Up: Introduction
Q1.0.8: How do you pronounce XEmacs?
------------------------------------
- The most common pronounciation is `Eks eemax'.
+ I pronounce it `Eks eemax'.
\1f
File: xemacs-faq.info, Node: Q1.0.9, Next: Q1.0.10, Prev: Q1.0.8, Up: Introduction
Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
------------------------------------------------------------
- Yes, *Note MS Windows::.
+ Thanks to efforts of many people, coordinated by David Hobley <davidh@wr.com.au> and Marc Paquette <marcpa@cam.org>, beta versions of
+XEmacs now run on 32-bit Windows platforms (NT and 95). The current
+betas require having an X server to run XEmacs; however, a native NT/95
+port is in alpha, thanks to Jonathan Harris <jhar@tardis.ed.ac.uk>.
+
+ Although some features are still unimplemented, XEmacs 21.0 will
+support MS-Windows.
+
+ The NT development is now coordinated by a mailing list at
+<xemacs-nt@xemacs.org>.
+
+ If you are willing to contribute or want to follow the progress,
+mail to <xemacs-nt-request@xemacs.org> to subscribe.
+
+ Furthermore, Altrasoft is seeking corporate and government sponsors
+to help fund a fully native port of XEmacs to Windows 95 and NT using
+full-time, senior-level staff working under a professionally managed
+project structure. See the Altrasoft web site (http://www.altrasoft.com/) for more details or contact Altrasoft directly at 1-888-ALTSOFT.
+
+ The closest existing port is "Win-Emacs", which is based on Lucid
+Emacs 19.6. Available from `http://www.pearlsoft.com/'.
+
+ There's a port of GNU Emacs (not XEmacs) at
+ `http://www.cs.washington.edu/homes/voelker/ntemacs.html'.
\1f
File: xemacs-faq.info, Node: Q1.0.11, Next: Q1.0.12, Prev: Q1.0.10, Up: Introduction
Q1.0.11: Is there a port of XEmacs to the Macintosh?
----------------------------------------------------
- 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'.
+ There has been a port to the MachTen environment of XEmacs 19.13,
+but no patches have been submitted to the maintainers to get this in the
+mainstream distribution.
+
+ For the MacOS, there is a port of
+Emacs 18.59 (ftp://ftp.cs.cornell.edu/pub/parmet/).
\1f
File: xemacs-faq.info, Node: Q1.0.12, Next: Q1.0.13, Prev: Q1.0.11, Up: Introduction
Q1.0.13: Is there a port of XEmacs to OS/2?
-------------------------------------------
- No, but Alexander Nikolaev <avn_1251@mail.ru> is working on it.
+ No, and there is no news of anyone working on it.
\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?
----------------------------------------------------------------------
- Pre-printed manuals are not available. If you are familiar with
-TeX, you can generate your own manual from the XEmacs sources.
+ Altrasoft Associates, a firm specializing in Emacs-related support
+and development, will be maintaining the XEmacs user manual. The firm
+plans to begin publishing printed copies of the manual soon.
- HTML and Postscript versions of XEmacs manuals may be available from
-the XEmacs web site in the future. Send requests to <faq@xemacs.org>.
+ Web: `http://www.xemacs.com'
+ E-mail: <info@xemacs.com>
+ Tel: +1 408 243 3300
\1f
File: xemacs-faq.info, Node: Q1.1.1, Next: Q1.1.2, Prev: Q1.0.14, Up: Introduction
-----------------------------------------
The FAQ is actively maintained and modified regularly. All links
-should be up to date. Unfortunately, some of the information is out of
-date - a situation which the FAQ maintainer is working on. All
-submissions are welcome, please e-mail submissions to XEmacs FAQ
-maintainers <faq@xemacs.org>.
+should be up to date.
+
+ Changes are displayed on a monthly basis. "Months", for this
+purpose are defined as the 5th of the month through the 5th of the
+month. Preexisting questions that have been changed are marked as such.
+Brand new questions are tagged.
+
+ All submissions are welcome. E-mail submissions to Christian Nybo/ <faq@xemacs.org>.
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
+question should be included, I'd like to hear about it. Questions and
+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
-previous FAQ maintainers. 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 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.
\1f
File: xemacs-faq.info, Node: Q1.1.2, Next: Q1.1.3, Prev: Q1.1.1, Up: Introduction
Q1.1.2: How do I become a Beta Tester?
--------------------------------------
- Send an email message to <xemacs-beta-request@xemacs.org> with the
-line `subscribe' in the body of the message.
+ Send an email message to <xemacs-beta-request@xemacs.org> with a
+subject line of `subscribe'.
Be prepared to get your hands dirty, as beta testers are expected to
identify problems as best they can.
Q1.1.3: How do I contribute to XEmacs itself?
---------------------------------------------
- Ben Wing <ben@xemacs.org> writes:
+ Ben Wing <ben@666.com> writes:
BTW if you have a wish list of things that you want added, you
have to speak up about it! More specifically, you can do the
* Martin Buchholz <martin@xemacs.org>
- * Steve Baur <steve@xemacs.org>
-
- * Hrvoje Niksic <hniksic@xemacs.org>
+ * Steve Baur <steve@altair.xemacs.org>
+ * Hrvoje Niksic <hniksic@srce.hr>
The developers responsible for the 19.14 release are:
Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible
for XEmacs becoming a widely distributed program over the Internet.
- * Ben Wing <ben@xemacs.org>
+ * Ben Wing <ben@666.com>
-
- * Jamie Zawinski <jwz@jwz.org>
+ * Jamie Zawinski <jwz@netscape.com>
Jamie Zawinski was Mr. Lucid Emacs from 19.0 through 19.10, the
last release actually named Lucid Emacs. Richard Mlynarik was
* SL Baur <steve@xemacs.org>
- * Hrvoje Niksic <hniksic@xemacs.org>
+ * Hrvoje Niksic <hniksic@srce.hr>
* Aki Vehtari <Aki.Vehtari@hut.fi>
-
\1f
File: xemacs-faq.info, Node: Q1.2.3, Next: Q1.3.1, Prev: Q1.2.2, Up: Introduction
* Curtis.N.Bingham <binge@aloft.att.com>
- * Georges Brun-Cottan <bruncott@dormeur.inria.fr>
-
* Richard Caley <rjc@cogsci.ed.ac.uk>
* Richard Cognot <cognot@ensg.u-nancy.fr>
- * Mark Daku <daku@nortel.ca>
-
* William G. Dubuque <wgd@martigny.ai.mit.edu>
* Eric Eide <eeide@cs.utah.edu>
- * Alain Fauconnet <af@biomath.jussieu.fr>
-
* Chris Flatters <cflatter@nrao.edu>
* Evelyn Ginsparg <ginsparg@adra.com>
1.3: Internationalization
=========================
-Q1.3.1: What is the status of internationalization support aka MULE (including Asian language support?
-------------------------------------------------------------------------------------------------------
+Q1.3.1: What is the status of XEmacs v20?
+-----------------------------------------
- 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.
+ 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.
\1f
File: xemacs-faq.info, Node: Q1.3.2, Next: Q1.3.3, Prev: Q1.3.1, Up: Introduction
-Q1.3.2: How can I help with internationalization?
--------------------------------------------------
+Q1.3.2: What is the status of Asian-language support, aka MULE?
+---------------------------------------------------------------
+
+ The MULE support works OK but still needs a fair amount of work
+before it's really solid. We could definitely use some help here, esp.
+people who speak Japanese and will use XEmacs/MULE to work with
+Japanese and have some experience with E-Lisp.
- If you would like to help, you may want to join the
-<xemacs-mule@xemacs.org> mailing list. Especially needed are people
-who speak/write languages other than English, who are willing to use
-XEmacs/MULE regularly, and have some experience with Elisp.
+ As the fundings on Mule have stopped, the Mule part of XEmacs is
+currently looking for a full-time maintainer. If you can provide help
+here, or are willing to fund the work, please mail to
+<xemacs-beta@xemacs.org>.
*Note Q1.1.2::.
Q1.3.3: How do I type non-ASCII characters?
-------------------------------------------
- See question 3.5.7 (*note Q3.5.7::) in part 3 of this FAQ.
+ See question 3.5.7 (*note Q3.5.7::.) in part 3 of this FAQ.
\1f
File: xemacs-faq.info, Node: Q1.3.4, Next: Q1.3.5, Prev: Q1.3.3, Up: Introduction
-------------------------------------------------------------
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. To enable it, add to your
-`Emacs' file entries like this:
+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:
- Emacs*XlwMenu.resourceLabels: True
- Emacs*XlwMenu.file.labelString: Fichier
- Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
+ Emacs*XlwMenu.resourceLabels: True
+ Emacs*XlwMenu.file.labelString: Fichier
+ Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster offnen
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
----------------------------------------------------------------
+Q1.3.5: Please explain the various input methods in MULE/XEmacs 20.0
+--------------------------------------------------------------------
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?
------------------------------------------------
+Q1.3.6: How do I portably code for MULE/XEmacs 20?
+--------------------------------------------------
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
)
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
-data-directory <RET>'.
+buffer by selecting `Help->Samples->Sample .emacs' from the menubar.
+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
available in a non-english language, type `C-u C-h t TAB', type the
first letters of your preferred language, then type <RET>.
+ There's an Emacs Lisp tutorial at
+
+ `ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz'.
+
+ Erik Sundermann <erik@petaxp.rug.ac.be> has made a tutorial web page
+at `http://petaxp.rug.ac.be/~erik/xemacs/'.
+
\1f
File: xemacs-faq.info, Node: Q1.4.4, Next: Q1.4.5, Prev: Q1.4.3, Up: Introduction
Or interactively, `M-x global-set-key' and follow the prompts.
\1f
-File: xemacs-faq.info, Node: Q1.4.6, Prev: Q1.4.5, Up: Introduction
+File: xemacs-faq.info, Node: Q1.4.6, Next: Q1.4.7, Prev: Q1.4.5, Up: Introduction
Q1.4.6: What's the difference between a macro and a function?
-------------------------------------------------------------
other keys. Refer to manual for details.
\1f
-File: xemacs-faq.info, Node: Installation, Next: Customization, Prev: Introduction, Up: Top
-
-2 Installation and Trouble Shooting
-***********************************
-
- This is part 2 of the XEmacs Frequently Asked Questions list. This
-section is devoted to Installation, Maintenance and Trouble Shooting.
-
-* Menu:
-
-Installation:
-* Q2.0.1:: Running XEmacs without installing.
-* Q2.0.2:: XEmacs is too big.
-* Q2.0.3:: Compiling XEmacs with Netaudio.
-* Q2.0.4:: Problems with Linux and ncurses.
-* Q2.0.5:: Do I need X11 to run XEmacs?
-* 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:: 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.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:: XEmacs cannot connect to my X Terminal.
-* Q2.1.6:: XEmacs 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:: XEmacs 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 `create_process' failure
-* Q2.1.14:: C-g doesn't work for me. Is it broken?
-* Q2.1.15:: How to debug an XEmacs problem with a debugger.
-* Q2.1.16:: XEmacs crashes in `strcat' on HP/UX 10.
-* Q2.1.17:: `Marker does not point anywhere'.
-* Q2.1.18:: [This question intentionally left blank]
-* Q2.1.19:: XEmacs does not follow the local timezone.
-* Q2.1.20:: `Symbol's function definition is void: hkey-help-show.'
-* Q2.1.21:: [This question intentionally left blank]
-* 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
-
-2.0: Installation
-=================
-
-Q2.0.1: Running XEmacs without installing
------------------------------------------
-
- 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
-build-time flag. It's the copying of the Lisp directories that
-requires so much space. XEmacs is largely written in Lisp.
-
- A good method is to make a shell alias for xemacs:
-
- alias xemacs=/i/xemacs-20.2/src/xemacs
-
- (You will obviously use whatever directory you downloaded the source
-tree to instead of `/i/xemacs-20.2').
-
- 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.
-
-\1f
-File: xemacs-faq.info, Node: Q2.0.3, Next: Q2.0.4, Prev: Q2.0.2, Up: Installation
-
-Q2.0.3: Compiling XEmacs with Netaudio.
----------------------------------------
-
- What is the best way to compile XEmacs 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.
-To tell it to compile in netaudio support: `--with-sound=both', or
-`--with-sound=nas' if you don't want native sound support for some
-reason.) To tell it where to find the netaudio includes and libraries:
-
- --site-libraries=WHATEVER
- --site-includes=WHATEVER
-
- 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 XEmacs starts. If the netaudio server goes
-away and another is run, XEmacs 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
-`ftp://ftp.x.org/contrib/audio/nas/'.
+File: xemacs-faq.info, Node: Q1.4.7, Prev: Q1.4.6, Up: Introduction
+
+Q1.4.7: How come options saved with 19.13 don't work with 19.14 or later?
+-------------------------------------------------------------------------
+
+ There's a problem with options of the form:
+
+ (add-spec-list-to-specifier (face-property 'searchm-field 'font)
+ '((global (nil))))
+
+ saved by a 19.13 XEmacs that causes a 19.14 XEmacs grief. You must
+delete these options. XEmacs 19.14 and later no longer write the
+options directly to `.emacs' which should allow us to deal with version
+incompatibilities better in the future.
+
+ Options saved under XEmacs 19.13 are protected by code that
+specifically requires a version 19 XEmacs. This won't be a problem
+unless you're using XEmacs v20. You should consider changing the code
+to read:
+
+ (cond
+ ((and (string-match "XEmacs" emacs-version)
+ (boundp 'emacs-major-version)
+ (or (and (= emacs-major-version 19)
+ (>= emacs-minor-version 12))
+ (>= emacs-major-version 20)))
+ ...
+ ))
projects / chise / xemacs-chise.git.1 / blobdiff