-This is Info file ../info/xemacs-faq.info, produced by Makeinfo version
-1.68 from the input file xemacs-faq.texi.
+This is ../info/xemacs-faq.info, produced by makeinfo version 4.0 from
+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
-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:: 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.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:: 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:: 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.
-
-\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
------------------------------------------
-
- The `INSTALL' file says that up to 108 MB of space is needed
-temporarily during installation! How can I just try it out?
-
- 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
--------------------------
-
- Although this entry has been written for XEmacs 19.13, most of it
-still stands true.
-
- Steve Baur <steve@altair.xemacs.org> writes:
-
- The 45MB of 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 (or even ones you do
- like the two obsolete mailcrypts and Gnus 4 in 19.13). 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. I'm not
- advocating any of these things, just pointing out ways to reduce
- the disk requirements if desired.
-
- Now examine the space used by directory:
-
- 0 /usr/local/bin/xemacs
- 2048 /usr/local/bin/xemacs-19.13
-
- 1546 /usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2
- 1158 /usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13
-
- You need to keep these. XEmacs isn't stripped by default in
- installation, you should consider stripping. That will save you
- about 5MB right there.
-
- 207 /usr/local/lib/xemacs-19.13/etc/w3
- 122 /usr/local/lib/xemacs-19.13/etc/sounds
- 18 /usr/local/lib/xemacs-19.13/etc/sparcworks
- 159 /usr/local/lib/xemacs-19.13/etc/vm
- 6 /usr/local/lib/xemacs-19.13/etc/e
- 21 /usr/local/lib/xemacs-19.13/etc/eos
- 172 /usr/local/lib/xemacs-19.13/etc/toolbar
- 61 /usr/local/lib/xemacs-19.13/etc/ns
- 43 /usr/local/lib/xemacs-19.13/etc/gnus
-
- These are support directories for various packages. In general
- they match a directory under
- ./xemacs-19.13/lib/xemacs-19.13/lisp/. If you do not require the
- package, you may delete or gzip the support too.
-
- 1959 /usr/local/lib/xemacs-19.13/etc
- 175 /usr/local/lib/xemacs-19.13/lisp/bytecomp
- 340 /usr/local/lib/xemacs-19.13/lisp/calendar
- 342 /usr/local/lib/xemacs-19.13/lisp/comint
- 517 /usr/local/lib/xemacs-19.13/lisp/dired
- 42 /usr/local/lib/xemacs-19.13/lisp/electric
- 212 /usr/local/lib/xemacs-19.13/lisp/emulators
- 238 /usr/local/lib/xemacs-19.13/lisp/energize
- 289 /usr/local/lib/xemacs-19.13/lisp/gnus
- 457 /usr/local/lib/xemacs-19.13/lisp/ilisp
- 1439 /usr/local/lib/xemacs-19.13/lisp/modes
- 2276 /usr/local/lib/xemacs-19.13/lisp/packages
- 1040 /usr/local/lib/xemacs-19.13/lisp/prim
- 176 /usr/local/lib/xemacs-19.13/lisp/pcl-cvs
- 154 /usr/local/lib/xemacs-19.13/lisp/rmail
- 3 /usr/local/lib/xemacs-19.13/lisp/epoch
- 45 /usr/local/lib/xemacs-19.13/lisp/term
- 860 /usr/local/lib/xemacs-19.13/lisp/utils
- 851 /usr/local/lib/xemacs-19.13/lisp/vm
- 13 /usr/local/lib/xemacs-19.13/lisp/vms
- 157 /usr/local/lib/xemacs-19.13/lisp/x11
- 19 /usr/local/lib/xemacs-19.13/lisp/tooltalk
- 14 /usr/local/lib/xemacs-19.13/lisp/sunpro
- 291 /usr/local/lib/xemacs-19.13/lisp/games
- 198 /usr/local/lib/xemacs-19.13/lisp/edebug
- 619 /usr/local/lib/xemacs-19.13/lisp/w3
- 229 /usr/local/lib/xemacs-19.13/lisp/eos
- 55 /usr/local/lib/xemacs-19.13/lisp/iso
- 59 /usr/local/lib/xemacs-19.13/lisp/mailcrypt
- 187 /usr/local/lib/xemacs-19.13/lisp/eterm
- 356 /usr/local/lib/xemacs-19.13/lisp/ediff
- 408 /usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl
- 1262 /usr/local/lib/xemacs-19.13/lisp/hyperbole
- 247 /usr/local/lib/xemacs-19.13/lisp/hm--html-menus
- 161 /usr/local/lib/xemacs-19.13/lisp/mh-e
- 299 /usr/local/lib/xemacs-19.13/lisp/viper
- 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-x
- 4 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/DocWindow.nib
- 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/InfoPanel.nib
- 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/TreeView.nib
- 11 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj
- 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx
- 466 /usr/local/lib/xemacs-19.13/lisp/oobr
- 14142 /usr/local/lib/xemacs-19.13/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 (newer versions exist,
- or you may just use Lynx or Netscape for web browsing), games,
- hyperbole, mh-e, hm-html-menus (better packages exist), vm, viper,
- oobr, gnus (new versions exist), 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 tape 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.
-
- 1972 /usr/local/lib/xemacs-19.13/info
-
- These are online texinfo sources. You may either gzip them or
- remove them. In either case, `C-h i' (info mode) will no longer
- work.
-
- 20778 /usr/local/lib/xemacs-19.13
-
- The 20MB achieved is less than half of what the full distribution
- takes up, *and* can be achieved without deleting a single file.
-
- Giacomo Boffi <boffi@hp735.stru.polimi.it> provides this procedure:
-
- Substitute `/usr/local/lib/' with the path where the xemacs tree is
- rooted, then use this script:
-
- #!/bin/sh
-
- r=/usr/local/lib/xemacs-19.13/lisp
-
- cd $r ; rm -f cmpr ; touch cmpr
-
- du -s .
-
- for d in * ; do
- if test -d $d ; then
- cd $d
- for f in *.el ; do
- # compress (remove) only (ONLY) the sources that have a
- # corresponding compiled file --- do not (DO NOT)
- # touch other sources
- if test -f ${f}c ; then gzip -v9 $f >> $r/cmpr ; fi
- done
- cd ..
- fi
- done
-
- du -s .
-
- A step beyond would be substituting `rm -f' for `gzip -v9', but
- you have to be desperate for removing the sources (remember that
- emacs can access compressed files transparently).
-
- Also, a good megabyte could easily be trimmed from the $r/../etc
- directory, e.g., the termcap files, some O+NEWS, others that I
- don't remember as well.
-
- XEmacs 21.0 will unbundle the lisp hierarchy and allow the
- installer to choose exactly how much support code gets installed.
-
-\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/'.
-
-\1f
-File: xemacs-faq.info, Node: Q2.0.4, Next: Q2.0.5, Prev: Q2.0.3, Up: Installation
-
-Q2.0.4: Problems with Linux and ncurses.
-----------------------------------------
-
- On Linux 1.3.98 with termcap 2.0.8 and the ncurses that came with
-libc 5.2.18, XEmacs 20.0b20 is unable to open a tty device:
-
- src/xemacs -nw -q
- Initialization error:
- Terminal type `xterm' undefined (or can't access database?)
-
- Ben Wing <ben@666.com> writes:
-
- Your ncurses configuration is messed up. Your /usr/lib/terminfo
- is a bad pointer, perhaps to a CD-ROM that is not inserted.
-
-\1f
File: xemacs-faq.info, Node: Q2.0.5, Next: Q2.0.6, Prev: Q2.0.4, Up: Installation
Q2.0.5: Do I need X11 to run XEmacs?
------------------------------------
No. The name "XEmacs" is unfortunate in the sense that it is *not*
-an X Window System-only version of Emacs. Starting with 19.14 XEmacs
-has full color support on a color-capable character terminal.
+an X Window System-only version of Emacs. XEmacs has full color
+support on a color-capable character terminal.
\1f
File: xemacs-faq.info, Node: Q2.0.6, Next: Q2.0.7, Prev: Q2.0.5, Up: Installation
`_h_errno^@' with `h_errno^@^@'. Any version of Emacs will
suffice. If you don't understand how to do this, don't do it.
- 3. Rebuild XEmacs yourself - any working ELF version of libc should be
+ 3. Rebuild XEmacs yourself--any working ELF version of libc should be
O.K.
- Hrvoje Niksic <hniksic@srce.hr> writes:
+ Hrvoje Niksic <hniksic@xemacs.org> writes:
Why not use a Perl one-liner for No. 2?
perl -pi -e 's/_h_errno\0/h_errno\0\0/g' \
/usr/local/bin/xemacs-19.14
- NB: You *must* patch `/usr/local/bin/xemacs-19.14', and not
+ NB: You _must_ patch `/usr/local/bin/xemacs-19.14', and not
`xemacs' because `xemacs' is a link to `xemacs-19.14'; the Perl
`-i' option will cause unwanted side-effects if applied to a
symbolic link.
Compface
`ftp://ftp.cs.indiana.edu/pub/faces/compface/'. This library has
been frozen for about 6 years, and is distributed without version
- numbers. *It should be compiled with the same options that X11 was
- compiled with on your system*. The version of this library at
+ numbers. _It should be compiled with the same options that X11 was
+ compiled with on your system_. The version of this library at
XEmacs.org includes the `xbm2xface.pl' script, written by
<stig@hackvan.com>, which may be useful when generating your own
xface.
then proceed to link against the DNS resolver library code.
\1f
-File: xemacs-faq.info, Node: Q2.0.12, Next: Q2.0.13, Prev: Q2.0.11, Up: Installation
+File: xemacs-faq.info, Node: Q2.0.12, Next: Q2.1.1, Prev: Q2.0.11, Up: Installation
Q2.0.12: Why can't I strip XEmacs?
----------------------------------
/usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
\1f
-File: xemacs-faq.info, Node: Q2.0.13, Next: Q2.0.14, Prev: Q2.0.12, Up: Installation
-
-Q2.0.13: Problems linking with Gcc on Solaris
----------------------------------------------
-
- There are known difficulties linking with Gnu ld on Solaris. A
-typical error message might look like:
-
- unexec(): dlopen(../dynodump/dynodump.so): ld.so.1: ./temacs:
- fatal: relocation error:
- symbol not found: main: referenced in ../dynodump/dynodump.so
-
- Martin Buchholz <martin@xemacs.org> writes:
-
- You need to specify `-fno-gnu-linker' as part of your flags to pass
- to ld. Future releases of XEmacs will try to do this
- automatically.
-
-\1f
-File: xemacs-faq.info, Node: Q2.0.14, Next: Q2.1.1, Prev: Q2.0.13, Up: Installation
-
-Q2.0.14: Make on HP/UX 9 fails after linking temacs
----------------------------------------------------
-
- Problem when building xemacs-19.16 on hpux 9:
-
- Richard Cognot <cognot@ensg.u-nancy.fr> writes:
-
- make on hpux fails after linking temacs with a message:
-
- "make: don't know how to make .y."
-
- Solution: This is a problem with HP make revision 70.X. Either
- use GNU make, or install PHCO_6552, which will bring make to
- revision 72.24.1.17.
-
-\1f
-File: xemacs-faq.info, Node: Q2.1.1, Next: Q2.1.2, Prev: Q2.0.14, Up: Installation
+File: xemacs-faq.info, Node: Q2.1.1, Next: Q2.1.2, Prev: Q2.0.12, Up: Installation
2.1: Trouble Shooting
=====================
color backgrounds and foregrounds into your
`.../app-defaults/Emacs' like:
- *Foreground: Black ;everything will be of black on grey95,
- *Background: Grey95 ;unless otherwise specified.
- *cursorColor: Red3 ;red3 cursor with grey95 border.
- *pointerColor: Red3 ;red3 pointer with grey95 border.
+ *Foreground: Black ;everything will be of black on grey95,
+ *Background: Grey95 ;unless otherwise specified.
+ *cursorColor: Red3 ;red3 cursor with grey95 border.
+ *pointerColor: Red3 ;red3 pointer with grey95 border.
Natalie Kershaw adds:
Q2.1.14: `C-g' doesn't work for me. Is it broken?
--------------------------------------------------
- Ben Wing <ben@666.com> writes:
+ Ben Wing <ben@xemacs.org> writes:
`C-g' does work for most people in most circumstances. If it
doesn't, there are only two explanations:
Morten Welinder <terra@diku.dk> writes:
- On some (but *not* all) machines a hung XEmacs can be revived by
+ On some (but _not_ all) machines a hung XEmacs can be revived by
`kill -FPE <pid>'. This is a hack, of course, not a solution.
This technique works on a Sun4 running 4.1.3_U1. To see if it
works for you, start another XEmacs and test with that first. If
you've got is a core dump, all is not lost.
If you're using GDB, there are some macros in the file
- `src/gdbinit' in the XEmacs source distribution that should make it
- easier for you to decode Lisp objects. Copy this file to
- `~/.gdbinit', or `source' it from `~/.gdbinit', and use the macros
- defined therein. In particular, use the `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 `ldp' and `lbt'
- are provided for conveniently calling `debug_print' and
- `debug_backtrace'.
+ `src/.gdbinit' in the XEmacs source distribution that should make
+ it easier for you to decode Lisp objects. This file is
+ automatically read by gdb if gdb is run in the directory where
+ xemacs was built, and contains these useful macros to inspect the
+ state of xemacs:
+
+ `pobj'
+ Usage: pobj lisp_object
+ Print the internal C representation of a lisp object.
+
+ `xtype'
+ Usage: xtype lisp_object
+ Print the Lisp type of a lisp object.
+
+ `lbt'
+ Usage: lbt
+ Print the current Lisp stack trace. Requires a running
+ xemacs process.
+
+ `ldp'
+ Usage: ldp lisp_object
+ Print a Lisp Object value using the Lisp printer. Requires a
+ running xemacs process.
+
+ `run-temacs'
+ Usage: run-temacs
+ Run temacs interactively, like xemacs. Use this with
+ debugging tools (like purify) that cannot deal with dumping,
+ or when temacs builds successfully, but xemacs does not.
+
+ `dump-temacs'
+ Usage: dump-temacs
+ Run the dumping part of the build procedure. Use when
+ debugging temacs, not xemacs! Use this when temacs builds
+ successfully, but xemacs does not.
+
+ `check-xemacs'
+ Usage: check-xemacs
+ Run the test suite. Equivalent to 'make check'.
+
+ `check-temacs'
+ Usage: check-temacs
+ Run the test suite on temacs. Equivalent to 'make
+ check-temacs'. Use this with debugging tools (like purify)
+ that cannot deal with dumping, or when temacs builds
+ successfully, but xemacs does not.
If you are using Sun's `dbx' debugger, there is an equivalent file
- `src/dbxrc' to copy to or source from `~/.dbxrc'.
+ `src/.dbxrc', which defines the same commands for dbx.
* 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
* If you compile with the newer gcc variants gcc-2.8 or egcs, you
- will also need gdb 4.17. Earlier releases of gdb can't handle the
- debug information generated by the newer compilers.
+ will also need gdb 4.17 or above. Earlier releases of gdb can't
+ handle the debug information generated by the newer compilers.
+
+ * In versions of XEmacs before 21.2.27, `src/.gdbinit' was named
+ `src/gdbinit'. This had the disadvantage of not being sourced
+ automatically by gdb, so you had to set that up yourself.
- * The above information on using `src/gdbinit' works for XEmacs-21.0
- and above. For older versions of XEmacs, there are different
- `gdbinit' files provided in the `src' directory. Use the one
- corresponding to the configure options used when building XEmacs.
\1f
File: xemacs-faq.info, Node: Q2.1.16, Next: Q2.1.17, Prev: Q2.1.15, Up: Installation
Q2.1.16: XEmacs crashes in `strcat' on HP/UX 10
-----------------------------------------------
- >From the problems database (through
-`http://support.mayfield.hp.com/'):
+ From the problems database (through the former address
+http://support.mayfield.hp.com/):
Problem Report: 5003302299
Status: Open
\1f
File: xemacs-faq.info, Node: Q2.1.18, Next: Q2.1.19, Prev: Q2.1.17, Up: Installation
-Q2.1.18: 19.14 hangs on HP/UX 10.10.
-------------------------------------
-
- Richard Cognot <cognot@ensg.u-nancy.fr> writes:
-
- For the record, compiling on hpux 10.10 leads to a hang in Gnus
- when compiled with optimization on.
-
- I've just discovered that my hpux 10.01 binary was working less
- well than expected. In fact, on a 10.10 system, `(while t)' was not
- interrupted by `C-g'. I defined `BROKEN_SIGIO' and recompiled on
- 10.10, and... the hang is now gone.
-
- As far as configure goes, this will be a bit tricky: `BROKEN_SIGIO'
- is needed on 10.10, but *not* on 10.01: if I run my 10.01 binary
- on a 10.01 machine, without `BROKEN_SIGIO' being defined, `C-g'
- works as expected.
-
- Richard Cognot <cognot@ensg.u-nancy.fr> adds:
-
- Apparently somebody has found the reason why there is this `poll:
- interrupted...' message for each event. For some reason, libcurses
- reimplements a `select()' system call, in a highly broken fashion.
- The fix is to add a -lc to the link line *before* the -lxcurses.
- XEmacs will then use the right version of `select()'.
-
- Alain Fauconnet <af@biomath.jussieu.fr> writes:
-
- The *real* solution is to *not* link -lcurses in! I just changed
- -lcurses to -ltermcap in the Makefile and it fixed:
-
- 1. The `poll: interrupted system call' message.
-
- 2. A more serious problem I had discovered in the meantime, that
- is the fact that subprocess handling was seriously broken:
- subprocesses e.g. started by AUC TeX for TeX compilation of a
- buffer would *hang*. Actually they would wait forever for
- emacs to read the socket which connects stdout...
+Q2.1.18: removed
+----------------
\1f
File: xemacs-faq.info, Node: Q2.1.19, Next: Q2.1.20, Prev: Q2.1.18, Up: Installation
\1f
File: xemacs-faq.info, Node: Q2.1.21, Next: Q2.1.22, Prev: Q2.1.20, Up: Installation
-Q2.1.21: Every so often the XEmacs frame freezes
-------------------------------------------------
-
- This problem has been fixed in 19.15, and was due to a not easily
-reproducible race condition.
+Q2.1.21: [This question intentionally left blank]
+-------------------------------------------------
\1f
File: xemacs-faq.info, Node: Q2.1.22, Next: Q2.1.23, Prev: Q2.1.21, Up: Installation
or in some other strange cases.
\1f
-File: xemacs-faq.info, Node: Q2.1.23, Prev: Q2.1.22, Up: Installation
+File: xemacs-faq.info, Node: Q2.1.23, Next: Q2.1.24, Prev: Q2.1.22, Up: Installation
Q2.1.23: Movemail on Linux does not work for XEmacs 19.15 and later.
---------------------------------------------------------------------
#define MAIL_USE_FLOCK
+\1f
+File: xemacs-faq.info, Node: Q2.1.24, Prev: Q2.1.23, Up: Installation
+
+Q2.1.24: XEmacs won't start without network. (NEW)
+---------------------------------------------------
+
+ If XEmacs starts when you're on the network, but fails when you're
+not on the network, you may be missing a "localhost" entry in your
+`/etc/hosts' file. The file should contain an entry like:
+
+ 127.0.0.1 localhost
+
+ Add that line, and XEmacs will be happy.
+
+\1f
+File: xemacs-faq.info, Node: Customization, Next: Subsystems, Prev: Installation, Up: Top
+
+3 Customization and Options
+***************************
+
+ 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 `.emacs':
+* Q3.0.1:: What version of Emacs am I running?
+* Q3.0.2:: How do I evaluate Elisp expressions?
+* Q3.0.3:: `(setq tab-width 6)' behaves oddly.
+* Q3.0.4:: How can I add directories to the `load-path'?
+* Q3.0.5:: How to check if a lisp function is defined?
+* Q3.0.6:: Can I force the output of `(face-list)' to a buffer?
+* Q3.0.7:: Font selections don't get saved after `Save Options'.
+* Q3.0.8:: How do I make a single minibuffer frame?
+* Q3.0.9:: What is `Customize'?
+
+X Window System & Resources:
+* Q3.1.1:: Where is a list of X resources?
+* Q3.1.2:: How can I detect a color display?
+* Q3.1.3:: [This question intentionally left blank]
+* Q3.1.4:: [This question intentionally left blank]
+* Q3.1.5:: How can I get the icon to just say `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.1.8:: `-iconic' doesn't work.
+
+Textual Fonts & Colors:
+* Q3.2.1:: How can I set color options from `.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.
+* Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
+
+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 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.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.5.10:: Can I turn on "sticky" modifier keys?
+* Q3.5.11:: How do I map the arrow keys?
+
+The Cursor:
+* Q3.6.1:: Is there a way to make the bar cursor thicker?
+* Q3.6.2:: Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
+* Q3.6.3:: Can I make the cursor blink?
+
+The Mouse and Highlighting:
+* Q3.7.1:: How can I turn off Mouse pasting?
+* Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
+* Q3.7.3:: Clicking the left button does not do anything in buffer list.
+* Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
+* Q3.7.5:: Why does cut-and-paste not work between 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?
+
+The Menubar and Toolbar:
+* Q3.8.1:: How do I get rid of the menu (or menubar)?
+* Q3.8.2:: Can I customize the basic menubar?
+* Q3.8.3:: How do I control how many buffers are listed in the menu `Buffers' list?
+* Q3.8.4:: Resources like `Emacs*menubar*font' are not working?
+* Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
+
+Scrollbars:
+* Q3.9.1:: How can I disable the scrollbar?
+* Q3.9.2:: How can one use resources to change scrollbar colors?
+* Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
+* Q3.9.4:: How can I 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 C-x C-p (mark-page)?
+* Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.1, Next: Q3.0.2, Prev: Customization, Up: Customization
+
+3.0: Customization - Emacs Lisp and .emacs
+==========================================
+
+Q3.0.1: What version of Emacs am I running?
+-------------------------------------------
+
+ How can `.emacs' determine which of the family of Emacsen I am using?
+
+ To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
+XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
+example given in `etc/sample.emacs'. There are other nifty things in
+there as well!
+
+ For all new code, all you really need to do is:
+
+ (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.2, Next: Q3.0.3, Prev: Q3.0.1, Up: Customization
+
+Q3.0.2: How can I evaluate Emacs-Lisp expressions?
+--------------------------------------------------
+
+ I know I can evaluate Elisp expressions from `*scratch*' buffer with
+`C-j' after the expression. How do I do it from another buffer?
+
+ Press `M-:' (the default binding of `eval-expression'), and enter
+the expression to the minibuffer. In XEmacs prior to 19.15
+`eval-expression' used to be a disabled command by default. If this is
+the case, upgrade your XEmacs.
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.3, Next: Q3.0.4, Prev: Q3.0.2, Up: Customization
+
+Q3.0.3: `(setq tab-width 6)' behaves oddly.
+-------------------------------------------
+
+ If you put `(setq tab-width 6)' in your `.emacs' file it does not
+work! Is there a reason for this? If you do it at the EVAL prompt it
+works fine!! How strange.
+
+ Use `setq-default' instead, since `tab-width' is all-buffer-local.
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.4, Next: Q3.0.5, Prev: Q3.0.3, Up: Customization
+
+Q3.0.4: How can I add directories to the `load-path'?
+-----------------------------------------------------
+
+ Here are two ways to do that, one that puts your directories at the
+front of the load-path, the other at the end:
+
+ ;;; Add things at the beginning of the load-path, do not add
+ ;;; duplicate directories:
+ (pushnew "bar" load-path :test 'equal)
+
+ (pushnew "foo" load-path :test 'equal)
+
+ ;;; Add things at the end, unconditionally
+ (setq load-path (nconc load-path '("foo" "bar")))
+
+ keith (k.p.) hanlan <keithh@nortel.ca> writes:
+
+ To add directories using Unix shell metacharacters use
+ `expand-file-name' like this:
+
+ (push (expand-file-name "~keithh/.emacsdir") load-path)
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.5, Next: Q3.0.6, Prev: Q3.0.4, Up: Customization
+
+Q3.0.5: How to check if a lisp function is defined?
+---------------------------------------------------
+
+ Use the following elisp:
+
+ (fboundp 'foo)
+
+ It's almost always a mistake to test `emacs-version' or any similar
+variables.
+
+ Instead, use feature-tests, such as `featurep', `boundp', `fboundp',
+or even simple behavioral tests, eg.:
+
+ (defvar foo-old-losing-code-p
+ (condition-case nil (progn (losing-code t) nil)
+ (wrong-number-of-arguments t)))
+
+ There is an incredible amount of broken code out there which could
+work much better more often in more places if it did the above instead
+of trying to divine its environment from the value of one variable.
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.6, Next: Q3.0.7, Prev: Q3.0.5, Up: Customization
+
+Q3.0.6: Can I force the output of `(face-list)' to a buffer?
+------------------------------------------------------------
+
+ It would be good having it in a buffer, as the output of
+`(face-list)' is too wide to fit to a minibuffer.
+
+ Evaluate the expression in the `*scratch*' buffer with point after
+the rightmost paren and typing `C-j'.
+
+ If the minibuffer smallness is the only problem you encounter, you
+can simply press `C-h l' to get the former minibuffer contents in a
+buffer.
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.7, Next: Q3.0.8, Prev: Q3.0.6, Up: Customization
+
+Q3.0.7: Font selections in don't get saved after `Save Options'.
+----------------------------------------------------------------
+
+ For XEmacs 19.14 and previous:
+
+ John Mann <mannj@ll.mit.edu> writes:
+
+ You have to go to Options->Frame Appearance and unselect
+ `Frame-Local Font Menu'. If this option is selected, font changes
+ are only applied to the _current_ frame and do _not_ get saved
+ when you save options.
+
+ For XEmacs 19.15 and later:
+
+ Implement the above as well as set the following in your `.emacs'
+
+ (setq options-save-faces t)
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.8, Next: Q3.0.9, Prev: Q3.0.7, Up: Customization
+
+Q3.0.8: How do I get a single minibuffer frame?
+-----------------------------------------------
+
+ Vin Shelton <acs@acm.org> writes:
+
+ (setq initial-frame-plist '(minibuffer nil))
+ (setq default-frame-plist '(minibuffer nil))
+ (setq default-minibuffer-frame
+ (make-frame
+ '(minibuffer only
+ width 86
+ height 1
+ menubar-visible-p nil
+ default-toolbar-visible-p nil
+ name "minibuffer"
+ top -2
+ left -2
+ has-modeline-p nil)))
+ (frame-notice-user-settings)
+
+ *Please note:* The single minibuffer frame may not be to everyone's
+taste, and there any number of other XEmacs options settings that may
+make it difficult or inconvenient to use.
+
+\1f
+File: xemacs-faq.info, Node: Q3.0.9, Next: Q3.1.1, Prev: Q3.0.8, Up: Customization
+
+Q3.0.9: What is `Customize'?
+----------------------------
+
+ Starting with XEmacs 20.2 there is new system 'Customize' for
+customizing XEmacs options.
+
+ You can access `Customize' from the `Options' menu or invoking one
+of customize commands by typing eg. `M-x customize', `M-x
+customize-face', `M-x customize-variable' or `M-x customize-apropos'.
+
+ Starting with XEmacs 20.3 there is also new `browser' mode for
+Customize. Try it out with `M-x customize-browse'
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.1, Next: Q3.1.2, Prev: Q3.0.9, Up: Customization
+
+3.1: X Window System & Resources
+================================
+
+Q3.1.1: Where is a list of X resources?
+---------------------------------------
+
+ Search through the `NEWS' file for `X Resources'. A fairly
+comprehensive list is given after it.
+
+ In addition, an `app-defaults' file is supplied, `etc/Emacs.ad'
+listing the defaults. The file `etc/sample.Xdefaults' gives a set of
+defaults that you might consider. It is essentially the same as
+`etc/Emacs.ad' but some entries are slightly altered. Be careful about
+installing the contents of this file into your `.Xdefaults' or
+`.Xresources' file if you use GNU Emacs under X11 as well.
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.2, Next: Q3.1.3, Prev: Q3.1.1, Up: Customization
+
+Q3.1.2: How can I detect a color display?
+-----------------------------------------
+
+ You can test the return value of the function `(device-class)', as
+in:
+
+ (when (eq (device-class) 'color)
+ (set-face-foreground 'font-lock-comment-face "Grey")
+ (set-face-foreground 'font-lock-string-face "Red")
+ ....
+ )
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.3, Next: Q3.1.4, Prev: Q3.1.2, Up: Customization
+
+Q3.1.3: [This question intentionally left blank]
+------------------------------------------------
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.4, Next: Q3.1.5, Prev: Q3.1.3, Up: Customization
+
+Q3.1.4: [This question intentionally left blank]
+------------------------------------------------
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.5, Next: Q3.1.6, Prev: Q3.1.4, Up: Customization
+
+Q3.1.5: How can I get the icon to just say `XEmacs'?
+----------------------------------------------------
+
+ I'd like the icon to just say `XEmacs', and not include the name of
+the current file in it.
+
+ Add the following line to your `.emacs':
+
+ (setq frame-icon-title-format "XEmacs")
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.6, Next: Q3.1.7, Prev: Q3.1.5, Up: Customization
+
+Q3.1.6: How can I have the window title area display the full path?
+-------------------------------------------------------------------
+
+ I'd like to have the window title area display the full
+directory/name of the current buffer file and not just the name.
+
+ Add the following line to your `.emacs':
+
+ (setq frame-title-format "%S: %f")
+
+ A more sophisticated title might be:
+
+ (setq frame-title-format
+ '("%S: " (buffer-file-name "%f"
+ (dired-directory dired-directory "%b"))))
+
+ That is, use the file name, or the dired-directory, or the buffer
+name.
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.7, Next: Q3.1.8, Prev: Q3.1.6, Up: Customization
+
+Q3.1.7: `xemacs -name junk' doesn't work?
+-----------------------------------------
+
+ When I run `xterm -name junk', I get an xterm whose class name
+according to xprop, is `junk'. This is the way it's supposed to work,
+I think. When I run `xemacs -name junk' the class name is not set to
+`junk'. It's still `emacs'. What does `xemacs -name' really do? The
+reason I ask is that my window manager (fvwm) will make a window sticky
+and I use XEmacs to read my mail. I want that XEmacs window to be
+sticky, without having to use the window manager's function to set the
+window sticky. What gives?
+
+ `xemacs -name' sets the application name for the program (that is,
+the thing which normally comes from `argv[0]'). Using `-name' is the
+same as making a copy of the executable with that new name. The
+`WM_CLASS' property on each frame is set to the frame-name, and the
+application-class. So, if you did `xemacs -name FOO' and then created
+a frame named BAR, you'd get an X window with WM_CLASS = `( "BAR",
+"Emacs")'. However, the resource hierarchy for this widget would be:
+
+ Name: FOO .shell .container .BAR
+ Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+
+ instead of the default
+
+ Name: xemacs.shell .container .emacs
+ Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+
+ It is arguable that the first element of WM_CLASS should be set to
+the application-name instead of the frame-name, but I think that's less
+flexible, since it does not give you the ability to have multiple frames
+with different WM_CLASS properties. Another possibility would be for
+the default frame name to come from the application name instead of
+simply being `emacs'. However, at this point, making that change would
+be troublesome: it would mean that many users would have to make yet
+another change to their resource files (since the default frame name
+would suddenly change from `emacs' to `xemacs', or whatever the
+executable happened to be named), so we'd rather avoid it.
+
+ To make a frame with a particular name use:
+
+ (make-frame '((name . "the-name")))
+
+\1f
+File: xemacs-faq.info, Node: Q3.1.8, Next: Q3.2.1, Prev: Q3.1.7, Up: Customization
+
+Q3.1.8: `-iconic' doesn't work.
+-------------------------------
+
+ When I start up XEmacs using `-iconic' it doesn't work right. Using
+`-unmapped' on the command line, and setting the `initiallyUnmapped' X
+Resource don't seem to help much either...
+
+ Ben Wing <ben@xemacs.org> writes:
+
+ Ugh, this stuff is such an incredible mess that I've about given up
+ getting it to work. The principal problem is numerous
+ window-manager bugs...
+
projects / chise / xemacs-chise.git.1 / blobdiff