Mercurial > hg > xemacs-beta

view info/dir @ 4903:70089046adef

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
fix compile problems in intl-encap* under VS6 -------------------- ChangeLog entries follow: -------------------- lib-src/ChangeLog addition: 2010-01-30 Ben Wing <ben@xemacs.org> * make-mswin-unicode.pl: Make it possible to specify an overridden prototype in cases where either Cygwin or Visual Studio has errors in their headers that can be corrected by falling back to a less qualified type (typically without const). src/ChangeLog addition: 2010-01-30 Ben Wing <ben@xemacs.org> * intl-auto-encap-win32.c: * intl-auto-encap-win32.c (qxeExtractAssociatedIcon): * intl-auto-encap-win32.c (qxeExtractIconEx): * intl-auto-encap-win32.c (qxeCreateMDIWindow): * intl-auto-encap-win32.c (qxeCreateWindowStation): * intl-auto-encap-win32.c (qxeDdeCreateStringHandle): * intl-auto-encap-win32.c (qxeAbortSystemShutdown): * intl-auto-encap-win32.c (qxeRegConnectRegistry): * intl-auto-encap-win32.c (qxeGetICMProfile): * intl-auto-encap-win32.h: Rebuild. * intl-encap-win32.c: * intl-encap-win32.c (qxeUpdateICMRegKey): Delete manual definitions of functions with former errors in Cygwin headers but no longer. Use "override" with some functions where Cygwin or VS6 accidentally omits a const declaration or includes an extra one. Use "no" on SendMessageTimeout, which has an error in the VS6 prototype (you could manually fix this with an ifdef to split the Cygwin vs. VS6 calls, if we ever actually used this function).
author Ben Wing <ben@xemacs.org>
date Sat, 30 Jan 2010 20:34:23 -0600
parents c2580215c222
children
line wrap: on
line source

-*- Text -*-

This is the file .../info/dir, which contains the topmost node of the Info
hierarchy.  The first time you invoke Info you start off looking at that node,
which is (dir)Top.

Rather than adding new nodes to this directory (and this file) it is a better
idea to put them in a site-local directory, and then configure info to search
in that directory as well.  That way, you won't have to re-edit this file when
a new release of the editor comes out.

For example, you could add this code to .../lisp/site-start.el, which is
loaded before ~/.emacs each time the editor starts up:

  ;; find local info nodes
  (setq Info-directory-list
        (append Info-directory-list '("/private/info/")))

Then, when you enter info, a dir file like this one will be automatically
created and saved (provided you have write access to the directory).  The
contents of that file "/private/info/dir" will be appended to the contents of
this file.


File: dir	Node: Top	This is the top of the INFO tree

  This is Info, the online documentation browsing system.
  This page (the Directory node) gives a menu of major topics.

  button2 on a highlighted word follows that cross-reference.
  button3 anywhere brings up a menu of commands.
  ? lists additional keyboard commands.
  h invokes the Info tutorial.

* Menu:

XEmacs 21.5
===========
* XEmacs: (xemacs).          XEmacs Editor.
* Lispref: (lispref).        XEmacs Lisp Reference Manual.
* Intro: (new-users-guide).  Introduction to the XEmacs Editor.
* FAQ: (xemacs-faq).         XEmacs FAQ.
* Info: (info).              Documentation browsing system.
* Internals: (internals).    XEmacs Internals Manual.


Other Documentation:

* Common Lisp: (cl).                   XEmacs Common Lisp emulation package.
* Customizations: (custom).            Customization Library.
* Emodules: (emodules).                XEmacs dynamically loadable module support.
* External Widget: (external-widget).  External Client Widget.
* Standards: (standards).              GNU coding standards.
* Term mode: (term).                   XEmacs Terminal Emulator Mode.
* Termcap: (termcap).                  Termcap library of the GNU system.
* Texinfo: (texinfo).                  The GNU documentation format.
* Widgets: (widget).                   The Emacs Widget Library.