view nt/README @ 50357:e5a09c97e444

Include blockinput.h. (Vx_resource_name, Vx_resource_class, Qx_frame_parameter) (Qx_resource_name, Qface_set_after_frame_default): Define vars here. (Qauto_raise, Qauto_lower, ...): Define all frame parameter related vars here. (struct frame_parm_table, frame_parms): New table for describing frame parameters and their associated Q-variable. The order of the parameters corresponds to the sequence of the frame_parm_handlers table in redisplay_interface. (x_fullscreen_move, x_set_frame_parameters) (x_report_frame_params, x_set_fullscreen, x_set_line_spacing) (x_set_screen_gamma, x_set_font, x_set_fringe_width) (x_set_border_width, x_set_internal_border_width, x_set_visibility) (x_set_autoraise, x_set_autolower, x_set_unsplittable) (x_set_vertical_scroll_bars, x_set_scroll_bar_width, x_icon_type): Generic functions for processing of frame parameters. (validate_x_resource_name, xrdb_get_resource, Fx_get_resource) (display_x_get_resource, x_get_resource_string): Functions for generic access to X resources. (x_get_arg, x_frame_get_arg, x_frame_get_and_record_arg) (x_default_parameter, Fx_parse_geometry): Functions for generic access to frame parameters. (x_figure_window_size): Generic calculation of frame size. Fixed to add space needed for tool bar. Also setup size_hint_flags. (syms_of_frame): Intern and staticpro frame parameter variables. Defvar_lisp Vx_resource_class and Vx_resource_name here. Defsubr Sx_get_resource and Sx_parse_geometry.

	     Emacs for Windows NT/2000 and Windows 95/98/ME

  Copyright (c) 2001 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
  [e-mail].  (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 [e-mail]
  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 [e-mail] 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.