xemacs-beta: man/xemacs-faq.texi comparison

comparison man/xemacs-faq.texi @ 272:c5d627a313b1 r21-0b34

Import from CVS: tag r21-0b34

author	cvs
date	Mon, 13 Aug 2007 10:28:48 +0200
parents	0e522484dd2a
children	ca9a9ec9c1c1

comparison

equal deleted inserted replaced

-:c7b7086b0a39
+:c5d627a313b1
 * Q1.0.1::      What is XEmacs?
 * Q1.0.2::      What is the current version of XEmacs?
 * Q1.0.3::      Where can I find it?
 * 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.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.0.11::     Is there a port of XEmacs to the Macintosh?
 * Q1.0.12::     Is there a port of XEmacs to NextStep?
 * Q1.0.13::     Is there a port of XEmacs to OS/2?
 * Q1.0.14::     Where can I get a printed copy of the XEmacs users manual?
 * Q1.1.2::      How do I become a Beta Tester?
 * Q1.1.3::      How do I contribute to XEmacs itself?
 Credits:
 * Q1.2.1::      Who wrote XEmacs?
 * Q1.2.2::      Who contributed to this version of the FAQ?
 * 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 @var{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 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.1::      What is a @file{.emacs} and is there a sample one?
 * Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
 * Q1.4.3::      Any good XEmacs tutorials around?
 * 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.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::     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.2::      Cryptic Minibuffer messages.
 * Q2.1.3::      Translation Table Syntax messages at Startup.
 * 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.
 Customization 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.3::      @code{(set-screen-width)} worked in 19.6, but not in 19.13?
 * Q3.1.4::      Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
 * Q3.1.5::      How can I get the icon to just say @samp{XEmacs}?
 * Q3.1.6::      How can I have the window title area display the full path?
 * Q3.1.7::      @samp{xemacs -name junk} doesn't work?
-* Q3.1.8::      @samp{-iconic} it 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{.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.2.5::      My tty supports color, but XEmacs doesn't use them.
 The Modeline:
 * Q3.3.1::      How can I make the modeline go away?
 * Q3.3.2::      How do you have XEmacs display the line number in the modeline?
 * Q3.3.3::      How do I get XEmacs 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?
 3.4 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 XEmacs after calling up over a modem?  How?
 3.5 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 XEmacs?
 * Q3.5.8::      Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
 * Q3.5.9::      How do I make the Delete key delete forward?
 * Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
 * 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?
 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.
 * 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, 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.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:
 * 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::     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?
 * Q1.0.1::      What is XEmacs?
 * Q1.0.2::      What is the current version of XEmacs?
 * Q1.0.3::      Where can I find it?
 * 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.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.0.11::     Is there a port of XEmacs to the Macintosh?
 * Q1.0.12::     Is there a port of XEmacs to NextStep?
 * Q1.0.13::     Is there a port of XEmacs to OS/2?
 * Q1.0.14::     Where can I get a printed copy of the XEmacs users manual?
 * Q1.1.2::      How do I become a Beta Tester?
 * Q1.1.3::      How do I contribute to XEmacs itself?
 Credits:
 * Q1.2.1::      Who wrote XEmacs?
 * Q1.2.2::      Who contributed to this version of the FAQ?
 * 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 @var{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 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.1::      What is a @file{.emacs} and is there a sample one?
 * Q1.4.2::      Can I use the same @file{.emacs} with the other Emacs?
 * Q1.4.3::      Any good XEmacs tutorials around?
 and the XEmacs development team which provide little hope for a merge to
 take place in the short-term future.
 If you have a comment to add regarding the merge, it is a good idea to
 avoid posting to the newsgroups, because of the very heated flamewars
 that often result.  Mail your questions to <xemacs-beta@@xemacs.org> and
 <bug-gnu-emacs@@prep.ai.mit.edu>.
 @node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
 @section Where can I get help?
 Also, @kbd{M-x apropos} will look for commands for you.
 Try reading this FAQ, examining the regular GNU Emacs FAQ (which can be
 found with the Emacs 19 distribution) as well as at
 <URL: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 @strong{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
 with a subject of @samp{subscribe} to <xemacs-request@@xemacs.org>
 for subscription information and <xemacs@@xemacs.org> to send messages
 to the list.
 To cancel a subscription, you @strong{must} use the xemacs-request
 address.  Send a message with a subject of @samp{unsubscribe} to be
 removed.
 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
 @section How do I become a Beta Tester?
 Send an email message to <xemacs-beta-request@@xemacs.org> with a
 subject line of @samp{subscribe}.
 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
 XEmacs is the result of the time and effort of many people.  The
 developers responsible for the 19.16/20.x releases are:
 @itemize @bullet
-@item Martin Buchholz <mrb@@eng.sun.com>
+@item Martin Buchholz <martin@@xemacs.org>
 @item Steve Baur <steve@@altair.xemacs.org>
 @item Hrvoje Niksic <hniksic@@srce.hr>
 @end itemize
 support, 20.3 is approximately as stable as 19.16, and probably faster
 (due to additional optimization work.)
 As of XEmacs 20.3, version 20 is @emph{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 (@code{character}, @code{char-table}, and
 @code{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.
 @quotation
 In XEmacs version 19, and in all versions of FSF GNU Emacs, a
 @dfn{character} in XEmacs Lisp is nothing more than an integer.
 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.
-As the fundings on Mule have stopped, Mule part of XEmacs is currently
+As the funding on Mule have stopped, 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>.
 @xref{Q1.1.2}.
 Emacs*XlwMenu.file.labelString:	        	Fichier
 Emacs*XlwMenu.openInOtherWindow.labelString: 	In anderem Fenster offnen
 @end example
 The name of the resource is derived from the non-localized entry by
-removing punctuation and capitalizing as above.  Martin Buchholz
+removing punctuation and capitalizing as above.
-<Martin.Buchholz@@sun.com> is working on adding support for Asian
-language menubar localization to XEmacs 20.
 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
 @section Please explain the various input methods in MULE/XEmacs 20.0
 MORIOKA Tomohiko <morioka@@jaist.ac.jp> writes:
 @quotation
-Original Mule supports following input methods: Wnn4, Wnn6, Canna, SJ3
+Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
 and XIM. Interfaces for Wnn and SJ3 uses the @code{egg} user
 interface. Interface for Canna does not use @samp{egg}. I don't know
 about XIM. It is to support ATOK, of course, it may work for another
 servers.
 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::     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.2::      Cryptic Minibuffer messages.
 * Q2.1.3::      Translation Table Syntax messages at Startup.
 There are known difficulties linking with Gnu ld on Solaris.  A typical
 error message might look like:
 @example
 unexec(): dlopen(../dynodump/dynodump.so): ld.so.1: ./temacs:
 fatal: relocation error:
 symbol not found: main: referenced in ../dynodump/dynodump.so
 @end example
-Martin Buchholz <mrb@@eng.sun.com> writes:
+Martin Buchholz <martin@@xemacs.org> writes:
 @quotation
 You need to specify @samp{-fno-gnu-linker} as part of your flags to pass
 to ld.  Future releases of XEmacs will try to do this automatically.
 @end quotation
 @example
 xemacs*cursorColor:    black
 xemacs*pointerColor:   black
 @end example
-With the new colours installed the problem still occurs if the above
+With the new colors installed the problem still occurs if the above
 resources are not defined.
-If the new colours are not present then an additional error occurs on
+If the new colors are not present then an additional error occurs on
 XEmacs startup, which says @samp{Color Red3} not defined.
 @end quotation
 @node Q2.1.9, Q2.1.10, Q2.1.8, Installation
 @section XEmacs causes my OpenWindows 3.0 server to crash.
 expression handler.
 Douglas Kosovic <douglask@@dstc.edu.au> writes:
 @quotation
-Actually it's a DEC cc optimisation bug that screws up the regexp
+Actually it's a DEC cc optimization bug that screws up the regexp
 handling in XEmacs.
 Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
-different sort of optimisation) works fine.
+different sort of optimization) works fine.
 @end quotation
 See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
 build with the @samp{-migrate} flag:
 @end quotation
 @node Q2.1.15, Q2.1.16, Q2.1.14, Installation
 @section How to Debug an XEmacs problem with a debugger
-Ben Wing <ben@@666.com> writes:
-@quotation
 If XEmacs 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 XEmacs with debugging symbols, with no
-optimization, and with the configure options @samp{--debug=yes},
+optimization, and with the configure options @samp{--debug=yes} and
-@samp{--error-checking=all}, and @samp{--dynamic=no}.  This will make
+@samp{--error-checking=all}.  This will make your XEmacs run somewhat
-your XEmacs run somewhat slower but make it a lot more likely to catch
+slower but make it a lot more likely to catch the problem earlier
-the problem earlier (closer to its source), and a lot easier to
+(closer to its source), and a lot easier to determine what's going on
-determine what's going on with a debugger.
+with a debugger.
 @item
 If you're able to run XEmacs under a debugger and reproduce the crash
 (if it's inconvenient to do this because XEmacs is already running or is
 running in batch mode as part of a bunch of scripts, consider attaching
 @item
 Internally, you will probably see lots of variables that hold objects of
 type @code{Lisp_Object}.  These are exactly what they appear to be,
 i.e. references to Lisp objects.  Printing them out with the debugger
-probably won't be too useful---you'll just see a number.  To decode
+probably won't be too useful---you'll likely just see a number.  To
-them, do this:
+decode them, do this:
 @example
 call debug_print (OBJECT)
 @end example
 @example
 call debug_backtrace ()
 @end example
 @item
-If all you've got is a core dump, all is not lost.  You can still poke
+Using @code{debug_print} and @code{debug_backtrace} has two
-around somewhat, and if you're using GDB, there are some macros in the
+disadvantages - it can only be used with a running xemacs process, and
-file @file{gdbinit} in the @file{src} directory of the XEmacs
+it cannot display the internal C structure of a Lisp Object.  Even if
-distribution that should make it easier for you to decode Lisp objects.
+all you've got is a core dump, all is not lost.
-If you're using DBX, you may be able to get further help from Martin
+If you're using GDB, there are some macros in the file
-Buchholz, the engineer at Sun who works on XEmacs.  Write to him at
+@file{src/gdbinit} in the XEmacs source distribution that should make it
-<Martin.Buchholz@@sun.com>.
+easier for you to decode Lisp objects.  Copy this file to
+@file{~/.gdbinit}, or @code{source} it from @file{~/.gdbinit}, and use
+the macros defined therein.  In particular, use the @code{pobj} macro to
+print the internal C representation of a lisp object.  This will work
+with a core file or not-yet-run executable.  The aliases @code{ldp} and
+@code{lbt} are provided for conveniently calling @code{debug_print} and
+@code{debug_backtrace}.
+If you are using Sun's @file{dbx} debugger, there is an equivalent file
+@file{src/dbxrc} to copy to or source from @file{~/.dbxrc}.
 @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
 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
+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.
 @item
 If your stack trace has exactly one frame in it, with address 0x0, this
 use the narrowing-down process described above.
 @item
 If you compiled 19.14 with @samp{--debug} (or by default in later
 versions), you will get a Lisp backtrace output when XEmacs crashes, so
-you'll have something useful.  If you're in 19.13, you could try doing
+you'll have something useful.
-@code{call debug_backtrace()}---sometimes this works even after a fatal
-signal has been received.
 @end enumerate
+@item
+If you compile with the newer gcc variants gcc-2.8 or egcs, you will
+need gdb 4.17.  At the time of writing, this has not yet been released.
+Pre-releases are available at ftp://ftp.cygnus.com/private/gdb.
+@item
+The above information on using @file{src/gdbinit} works for XEmacs-21.0
+and above.  For older versions of XEmacs, there are different
+@file{gdbinit} files provided in the @file{src} directory.  Use the one
+corresponding to the configure options used when building XEmacs.
 @end itemize
-@end quotation
-Here's some more info about using gdbinit:
-Different version of @code{gdbinit} are provided for different
-platforms.  One of these should be installed as @file{.gdbinit} in your
-home directory.  If you're using XEmacs 19.14 or better, you should
-install the default @code{gdbinit} in the @file{src/} directory if you
-have GDB 4.14 or better.  With GDB 4.13 or earlier, install
-@file{gdbinit.pre-4.14}; however, this is noticeably harder to use.  If
-you're on a machine that uses a union type for Lisp_Objects (only the
-DEC Alpha, I think), you'll have to use @code{gdbinit.union}, which is
-of the pre-4.14 variety but should be easily upgradable.
-With XEmacs 19.13 and earlier, only one @code{gdbinit} is provided (I
-think); it's of the pre-4.14 variety and of the union-type
-variety. (Many more machines used the union type under 19.13).
-With the GDB 4.14+ gdbinit, you can print out a Lisp_Object using
-@code{p1 OBJECT} (which calls @code{debug_print()}, and hence only works
-if you have a running process) or @code{frob OBJECT} (which works even
-on core dumps, and does its own decoding of the object, but its output
-isn't always so convenient).
-With the pre-GDB 4.14 gdbinit, you have to do these steps:
-@example
-print OBJECT
-xtype
-<then type "xcons" or "xstring" or whatever, depending on the type>
-@end example
-If the object is a record type, you'll probably have to the following
-steps:
-@example
-print OBJECT
-xtype
-xrecord
-<remember what type is printed>
-print OBJECT
-<then type "xbuffer" or "xsymbol" or whatever>
-@end example
-Of course, if you know in advance what type the object is of, you can
-omit all but the last two steps.
 @node Q2.1.16, Q2.1.17, Q2.1.15, Installation
 @section XEmacs crashes in @code{strcat} on HP/UX 10
 >From the problems database (through
 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.22, Installation
 @section  Movemail on Linux does not work for XEmacs 19.15 and later.
 Movemail used to work fine in 19.14 but has stopped working in 19.15
 and 20.x.  I am using Linux.
 SL Baur <steve@@xemacs.org> writes:
 This is part 3 of the XEmacs Frequently Asked Questions list.  This
 section is devoted to Customization and screen settings.
 @menu
 Customization---Emacs Lisp and @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.3::      @code{(set-screen-width)} worked in 19.6, but not in 19.13?
 * Q3.1.4::      Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
 * Q3.1.5::      How can I get the icon to just say @samp{XEmacs}?
 * Q3.1.6::      How can I have the window title area display the full path?
 * Q3.1.7::      @samp{xemacs -name junk} doesn't work?
-* Q3.1.8::      @samp{-iconic} it 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{.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.2.5::      My tty supports color, but XEmacs doesn't use them.
 The Modeline:
 * Q3.3.1::      How can I make the modeline go away?
 * Q3.3.2::      How do you have XEmacs display the line number in the modeline?
 * Q3.3.3::      How do I get XEmacs 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?
 3.4 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 XEmacs after calling up over a modem?  How?
 3.5 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 XEmacs?
 * Q3.5.8::      Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
 * Q3.5.9::      How do I make the Delete key delete forward?
 * Q3.5.10::     Can I turn on @dfn{sticky} modifier keys?
 * 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?
 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.
 @end menu
 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 behavioural tests, eg.:
+@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
 when you save options.
 @end quotation
 For XEmacs 19.15 and later:
 Implement the above as well as set the following in your @file{.emacs}
 @lisp
 (setq options-save-faces t)
 @end lisp
 @lisp
 (set-face-background 'default      "bisque")     ; frame background
 (set-face-foreground 'default      "black")      ; normal text
 (set-face-background 'zmacs-region "red")        ; When selecting w/
 ; mouse
 (set-face-foreground 'zmacs-region "yellow")
 (set-face-font       'default      "*courier-bold-r*120-100-100*")
 (set-face-background 'highlight    "blue")       ; Ie when selecting buffers
 (set-face-foreground 'highlight    "yellow")
 (set-face-background 'modeline     "blue")       ; Line at bottom of buffer
 (set-face-foreground 'modeline     "white")
 (set-face-font       'modeline     "*bold-r-normal*140-100-100*")
 (set-face-background 'isearch      "yellow")     ; When highlighting while
 ; searching
 (set-face-foreground 'isearch      "red")
 (setq x-pointer-foreground-color   "black")      ; Adds to bg color,
 ; so keep black
 (setq x-pointer-background-color   "blue")       ; This is color you really
 ; want ptr/crsr
 setting face values.
 In @file{.Xdefaults}:
 @example
 Emacs.default.attributeFont:  -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
 Emacs*menubar*font:           fixed
 Emacs.modeline.attributeFont: fixed
 @end example
 This is confusing because modeline is a face, and can be found listed
 @end example
 or in your @file{.emacs}:
 @lisp
 (set-face-background 'zmacs-region "red")
 (set-face-foreground 'zmacs-region "yellow")
 @end lisp
 @node Q3.2.4, Q3.2.5, Q3.2.3, Customization
 @section How can I limit color map usage?
 @section How can one change the modeline color based on the mode used?
 You can use something like the following:
 @lisp
 (add-hook 'lisp-mode-hook
 (lambda ()
 (set-face-background 'modeline "red" (current-buffer))))
 @end lisp
 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
 There are redisplay bugs in 19.14 that may make the preceding result in
 a messed-up display, especially for frames with multiple windows.  You
 may need to resize the frame before XEmacs completely realizes the
 toolbar is really gone.
-Thanks to Martin Buchholz <Martin.Buchholz@@sun.com> for the correct
+Thanks to Martin Buchholz <martin@@xemacs.org> for the correct
 code.
 @node Q3.9.1, Q3.9.2, Q3.8.5, Customization
 @section How can I disable the scrollbar?
 @example
 Emacs.scrollBarWidth:  0
 @end example
-Or select from the @code{Options} menu @code{Frame Appearance->Scrolbars}.
+Or select from the @code{Options} menu @code{Frame Appearance->Scrollbars}.
 Remember to save options.
 To turn the scrollbar off on a per-frame basis, use the following
 function:
 * 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,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.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:
 Note that each string is a regular expression.
 @node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
 @section Is there a mailing list or FAQ for VM?
 A FAQ for VM exists at <URL:http://www.cyberpass.net/~gorkab/vmfaq.htm>.
 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
 @node Q4.0.8, Q4.0.9, Q4.0.7, Subsystems
 @section Remote mail reading with VM.
 @quotation
 rmail and VM get new mail from @file{/usr/spool/mail/$USER} using a
 program called @code{movemail}.  This program interlocks with
 @code{/bin/mail} using the protocol defined by @code{/bin/mail}.
 There are two different protocols in general use.  One of them uses the
 @code{flock} system call.  The other involves creating a lock file;
 @code{movemail} must be able to write in @file{/usr/spool/mail} in order
 to do this.  You control which one is used by defining, or not defining,
 the macro @code{MAIL_USE_FLOCK} in @file{config.h} or the m- or s- file
 Era stood for "Emacs Rewritten Again".  It was what we were calling the
 modified version of Lucid Emacs for Sun when I was dragged, er, allowed
 to work on this wonderful editor.
 @end quotation
-Martin Buchholz <Martin.Buchholz@@sun.com> writes:
+Martin Buchholz <martin@@xemacs.org> writes:
 @quotation
 EOS is being replaced with a new graphical development environment
 called Sun WorkShop, which is currently (07/96) in Alpha Test.  For more
 details, check out
 Emacs Manual.
 InfoDock menus are much more extensive and more mature than standard
 Emacs menus.  Each menu offers a @samp{Manual} item which displays
 documentation associated with the menu's functions.
 @noindent
 Four types of menubars are provided:
 @enumerate
 @item
 An extensive menubar providing access to global InfoDock commands.
 requests.
 InfoDock is available across the Internet via anonymous FTP.  To get
 it, first move to a directory into which you want the InfoDock archive
 files placed.  We will call this <DIST-DIR>.
 @example
 cd <DIST-DIR>
 @end example
 Ftp to ftp.xemacs.org  (Internet Host ID = 128.174.252.16):
 prompt> ftp ftp.xemacs.org
 @end example
 Login as @samp{anonymous} with your own <user-id>@@<site-name> as a password.
 @example
 Name (ftp.xemacs.org): anonymous
 331 Guest login ok, send your complete e-mail address as password.
 Password: -<your-user-id@@your-domain>
 230 Guest login ok, access restrictions apply.
 @end example
 @section Byte compiling AUC TeX on XEmacs 19.14.
 Georges Brun-Cottan <bruncott@@dormeur.inria.fr> writes:
 @quotation
-When byte compiling auxtex-9.4g, you must use the command:
+When byte compiling auctex-9.4g, you must use the command:
 @example
 xemacs -batch -l lpath.el
 @end example
 @end quotation
 * 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::     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?
 (makunbound 'c-mode-map)
 (fmakunbound 'c++-mode)
 (makunbound 'c++-mode-map)
 (makunbound 'c-style-alist)
 (load-library "old-c-mode")
 (load-library "old-c++-mode")
 @end lisp
 This must be done before any other reference is made to either c-mode or
 c++-mode.
 @node Q5.0.10, Q5.0.11, Q5.0.9, Miscellaneous
 @section [This question intentionally left blank]
 Obsolete question, left blank to avoid renumbering
 @node Q5.0.11, Q5.0.12, Q5.0.10, Miscellaneous
 @section Filladapt doesn't work in 19.15
 Filladapt 2.x is included in 19.15.  In it filladapt is now a minor
 mode and minor modes are traditionally off by default.  The following
 Use @code{turn-on-filladapt-mode} to turn Filladapt on in particular
 major modes, like this:
 @lisp
 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
 @end lisp
 @node Q5.0.12, Q5.0.13, Q5.0.11, Miscellaneous
 @section How do I disable gnuserv from opening a new frame?
 happens) when I'm typing into shell mode, I hit return and only a
 portion of the command is given to the shell, and a blank prompt is
 returned.  If I hit return again, the rest of the previous command is
 given to the shell.
-Martin Buchholz <Martin.Buchholz@@sun.com> writes:
+Martin Buchholz <martin@@xemacs.org> writes:
 @quotation
 There is a known problem with interaction between @code{csh} and the
 @code{filec} option and XEmacs.  You should add the following to your
 @file{.cshrc}:
 (point-min)
 'text
 (current-buffer))
 @end lisp
 Replace @samp{FORMAT} with an unquoted symbol representing the format of
 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
 Instead of @samp{FILE}, use the image file name
 (e.g. @file{/usr/local/lib/xemacs-20.2/etc/recycle.xpm}).
 You can turn this to a function (that optionally prompts you for a file
 @node Q5.1.10, Q5.2.1, Q5.1.9, Miscellaneous
 @section @code{map-extents} won't traverse all of my extents!
 I tried to use @code{map-extents} to do an operation on all the extents
 in a region.  However, it seems to quit after processing a random number
 of extents.  Is it buggy?
 No.  The documentation of @code{map-extents} states that it will iterate
 across the extents as long as @var{function} returns @code{nil}.
 Unexperienced programmers often forget to return @code{nil} explicitly,
 which results in buggy code.  For instance, the following code is
 supposed to delete all the extents in a buffer, and issue as many
 @samp{fubar!} messages.
 @lisp
 (setq bell-volume 0)
 (setq sound-alist nil)
 @end lisp
 That will make your XEmacs totally silent -- even the default ding sound
 (TTY beep on TTY-s) will be gone.
 Starting with XEmacs-20.2 you can also change these with Customize.
 Select from the @code{Options} menu
 @code{Customize->Emacs->Environment->Sound->Sound...} or type
 @lisp
 (let ((ext (make-extent (point-min) (point-max))))
 (set-extent-property ext 'start-closed t)
 (set-extent-property ext 'end-closed t)
 (set-extent-property ext 'detachable nil)
 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
 @end lisp
 Since this is XEmacs, you can specify an icon to be shown on
 window-system devices.  To do so, change the @code{make-glyph} call to
 @lisp
 (let ((ext (make-extent (point-min) (point-max))))
 (set-extent-property ext 'start-closed t)
 (set-extent-property ext 'end-closed t)
 (set-extent-property ext 'detachable nil)
 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
 /* XPM */
 static char* eye = @{
 \"20 11 7 2\",
 \"__ c None\"
 \"_a c #fefefe\",
 \"_b c #7f0000\",
 \"_c c #fefe00\",
 \"_d c #fe0000\",
 \"_e c #bfbfbf\",
 \"___________`_`_`___b_b_b_b_________`____\",
 \"_________`_`_`___b_c_c_c_b_b____________\",
 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
 \"___`_`_e_a___b_b_d___b___b___b___b______\",
 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
 @} ;"]
 [string :data "[END]"]))))
 @end lisp
 Note that you might want to make this a function, and put it to a hook.
 @item
 Then set up emacs to include the file as a mail header - there were a
 couple of suggestions here---either something like:
 @lisp
 (setq  mail-default-headers
 "X-Face:  <Ugly looking text string here>")
 @end lisp
 Or, alternatively, as:
 @lisp
 (defun mail-insert-x-face ()
 (save-excursion
 (goto-char (point-min))
 (search-forward mail-header-separator)
 (beginning-of-line)
 (insert "X-Face:")
 (insert-file-contents "~/.face")))
 conversion.  For convenience xbm2xface is available for anonymous FTP at
 <URL:ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl>.
 Contributors for this item:
 Paul Emsley,
 Ricardo Marek,
 Amir J. Katz,
 Glen McCort,
 Heinz Uphoff,
 Peter Arius,
 Paul Harrison, and
 Vegard Vesterheim
 @node Q5.3.11, Q5.3.12, Q5.3.10, Miscellaneous
 @section How do I add new Info directories?
 You use something like:
 @lisp
 (setq Info-directory-list (cons
 			    (expand-file-name "~/info")
 			    Info-default-directory-list))
 @end lisp
 David Masterson <davidm@@prism.kla.com> writes:

Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 272:c5d627a313b1 r21-0b34