Mercurial > emacs
view nt/README @ 71893:bb3316be643e
Require 'cl during byte-compilation/interactive load, for the `assert' macro.
(allout-mode-deactivate-hook): New hook, is run when allout mode deactivates.
(allout-developer): New allout customization subgroup.
(allout-run-unit-tests-on-load): New allout-developer
customization variable, when true allout unit tests are run towards end of file
load/eval.
(allout-inhibit-auto-fill): Disable auto-fill activity even during
auto-fill-mode.
(allout-resumptions): Removed, to be replaced by...
(allout-add-resumptions): Register variable settings to be reinstated by
`allout-do-resumptions'. The settings are made buffer-local, but the
locality/globality of the suspended setting is restored on resumption.
(allout-do-resumptions): Reinstate all settings suspended using
`allout-add-resumptions'.
(allout-test-resumptions): Unit tests (and intermediate variables) for
resumptions.
(allout-tests-globally-unbound, allout-tests-globally-true)
(allout-tests-locally-true): Intermediate variables for resumptions unit tests.
(allout-overlay-preparations): Replaces `allout-set-overlay-category'.
(allout-exposure-category): Replaces 'allout-overlay-category variable.
(allout-mode): Use `allout-add-resumptions' and `allout-do-resumptions'
instead of retired `allout-resumptions'. For hook functions, use `local'
parameter so hook settings are created and removed as
buffer-local settings. Revise (resumptions) setting auto-fill-function so it
is set only if already active. (The related fill-function settings are all
made in either case, so that activating auto-fill-mode activity will have the
custom allout-mode behaviors (hanging indent on topics, if configured for it).
Also, remove all allout-exposure-category overlays on mode deactivation.
(allout-hotspot-key-handler): New function extracted from
`allout-pre-command-business', so the functionality can be used for other
purposes, eg as a binding in an overlay.
(allout-pre-command-business): Use new `allout-hotspot-key-handler'.
(allout-auto-fill): Respect new `allout-inhibit-auto-fill' customization
variable.
(allout-run-unit-tests): Run the (currently quite small) repertoire of unit
tests. Called just before the provide iff user has customized
`allout-run-unit-tests-on-load' non-nil.
author | Eli Zaretskii <eliz@gnu.org> |
---|---|
date | Fri, 14 Jul 2006 11:24:56 +0000 |
parents | 067115a6e738 |
children | cf400b7936d2 |
line wrap: on
line source
Emacs for Windows NT/2000 and Windows 95/98/ME Copyright (C) 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. See the end of the INSTALL file in this directory for copying permissions. This directory contains support for compiling and running GNU Emacs on Windows NT, Windows 95, and their successors. This port supports all of the major functionality of the Unix version, including subprocesses, windowing features (fonts, colors, scroll bars, multiple frames, etc.), and networking support. Precompiled distributions are also available; ftp to ftp://ftp.gnu.org/gnu/windows/emacs/latest/ for the latest precompiled distributions. * Building and installing See the INSTALL file in this directory for detailed instructions on building and installing Emacs on your system. * Further information There is a web page that serves as a FAQ for the Windows port of Emacs (a.k.a. NTEmacs) at: http://www.gnu.org/software/emacs/windows/ntemacs.html There is also a mailing list for discussing issues related to this port of Emacs. For information about the list, see this Web page: http://mail.gnu.org/mailman/listinfo/help-emacs-windows To ask questions on the mailing list, send email to help-emacs-windows@gnu.org. (You don't need to subscribe for that.) To subscribe to the list or unsubscribe from it, fill the form you find at http://mail.gnu.org/mailman/listinfo/help-emacs-windows as explained there. Another valuable source of information and help which should not be overlooked is the various Usenet news groups dedicated to Emacs. These are particularly good for help with general issues which aren't specific to the Windows port of Emacs. The main news groups to use for seeking help are: gnu.emacs.help comp.emacs There are also fairly regular postings and announcements of new or updated Emacs packages on this group: gnu.emacs.sources * Reporting bugs If you encounter a bug in this port of Emacs, we would like to hear about it. First check the file etc/PROBLEMS and the FAQ on the web page above to see if the bug is already known and if there are any workarounds. If not, then check whether the bug has something to do with code in your .emacs file, e.g. by invoking Emacs with the "-q --no-site-file" options. If you decide that it is a bug in Emacs that might be specific to the Windows port, send a message to the help-emacs-windows@gnu.org mailing list describing the bug, the version of Emacs that you are using, and the operating system that you are running on (Windows NT, 95 or 98 including service pack level if known). If the bug is related to subprocesses, also specify which shell you are using (e.g., include the values of `shell-file-name' and `shell-explicit-file-name' in your message). If you think the bug is not specific to the Windows port of Emacs, then it is better to mail the bug report to bug-gnu-emacs@gnu.org so that it will be seen by the right people. If Emacs has been set up to send mail, you can use the command M-x report-emacs-bug to create and send the bug report, but in some cases there is a function to report bugs in a specific package; e.g. M-x gnus-bug for Gnus, M-x c-submit-bug-report for C/C++/Java mode, etc.