				OEMACS
		       Release 4.1 (BETA RELEASE)
			    August 22, 1993


This file was last updated: August 22, 1993

     This file contains a list of bugs and frequently-asked questions,
regarding OEmacs Release 4.1.


***** KNOWN BUGS:

* The Meta-{, Meta-/, etc. keys do not work.  Meta keys that use
  alphabetic characters work, but the non-alphabetic characters do not.
  Unfortunately, the ROM BIOS is supressing these keys, and so there is
  no easy way of getting these keys to work.


***** Frequently-Asked Questions:

* The "info" facility doesn't work.  I get the error, "Wrong type
  argument: stringp, nil", when I try to use it.

  This error occurs because Emacs cannot find its Info files, and is
  usually caused by having old environment variables, such as:

	EMACSLOADPATH
	EMACSEXECPATH
	EMACSPATH
	EMACSDATA
	INFOPATH

  Another possibility is that the Info files were not installed or were
  installed in the wrong location (they should be installed in
  "emacs-19.19/info").

  Yet another possibility is that you did not properly follow the
  instructions on installing OEmacs, and improperly set the value for
  "EMACSTOPDIR" in one of the "emacs.bat" files.


* Why doesn't the mouse work?

  Before the mouse can be used, an MSDOS mouse driver must be loaded
  (even if Windows is being used), and this must be done BEFORE starting
  Emacs.  For MSDOS 5.0 and 6.0, a mouse driver can be found as
  C:\DOS\MOUSE.COM (see the MSDOS documentation for instructions on how
  to load it).  With Windows, note that the mouse will always work for
  graphical/native Windows 3.1 applications, regardless of whether or
  not the mouse driver is loaded, but will only work within a Windows
  MSDOS window if a mouse driver was loaded *BEFORE* windows was
  started.

  Once the mouse driver has been loaded, you need to enable the mouse by
  placing the following line into your ~/_emacs file:

	(emacs-pc-enable-mouse)

  You can also execute this function via M-x.

  The mouse is not enabled by default because, the first time the mouse
  is enabled within OEmacs, a hardware mouse reset is done, and this can
  take a couple of seconds (some people don't use a mouse, and do not
  want to incur this "slowdown" when starting Emacs).


* Why doesn't C-@ work?

  The C-@ key (accessed via Ctrl-Space) should work in this release (it
  did not work right in earlier releases).

  If it does not work, chances are that you are using an old ~/_emacs
  file, and it contains a command that attempts to redefine some keys,
  using C-@ as a prefix character.  Examples of this are:

	(global-set-key "\C-@G" 'beginning-of-buffer)
	(define-key function-key-map "\C-@G" [home])


* How do I rebind the function keys or keypad keys?

  GNU Emacs V19 changed the way keys are defined.  In addition, the
  various function keys now send different escape sequences to OEmacs
  Release 4.0 and later (different escape sequences were sent with
  earlier releases); this was done to remove a conflict with C-@.

  With V19, the following can be used to define keys (for example):

	(global-set-key [home] 'beginning-of-buffer)	; home
	(global-set-key [C-home] 'beginning-of-line)	; Ctrl-home
	(global-set-key [left] 'previous-char)		; left arrow
	(global-set-key [f1] 'help-for-help)		; F1

  Note that the PC keyboard is incapable of redefining some keys, such
  as any shifted numeric keypad key, or Alt-keypad keys, or C-up or
  C-down, to name a few.  For a vague idea of what function keys can be
  rebound (assuming that you are familiar with Emacs-lisp), see the file
  "emacs-19.19/lisp/term/ibmpc.el".

  See the V19 documentation for more details.
