xemacs-beta: man/lispref/files.texi comparison

comparison man/lispref/files.texi @ 5791:9fae6227ede5

Silence texinfo 5.2 warnings, primarily by adding next, prev, and up pointers to all nodes. See xemacs-patches message with ID <5315f7bf.sHpFD7lXYR05GH6E%james@xemacs.org>.

author	Jerry James <james@xemacs.org>
date	Thu, 27 Mar 2014 08:59:03 -0600
parents	576fb035e263
children

comparison

equal deleted inserted replaced

-:dcf9067f26bb
+:9fae6227ede5
 * Partial Files::            Treating a section of a buffer as a file.
 * Format Conversion::        Conversion to and from various file formats.
 * Files and MS-DOS::         Distinguishing text and binary files on MS-DOS.
 @end menu
-@node Visiting Files
+@node Visiting Files, Saving Buffers, Files, Files
 @section Visiting Files
 @cindex finding files
 @cindex visiting files
 Visiting a file means reading a file into a buffer.  Once this is
 @menu
 * Visiting Functions::         The usual interface functions for visiting.
 * Subroutines of Visiting::    Lower-level subroutines that they use.
 @end menu
-@node Visiting Functions
+@node Visiting Functions, Subroutines of Visiting, Visiting Files, Visiting Files
 @subsection Functions for Visiting Files
 This section describes the functions normally used to visit files.
 For historical reasons, these functions have names starting with
 @samp{find-} rather than @samp{visit-}.  @xref{Buffer File Name}, for
 This is not a normal hook because the values of the functions are
 used and they may not all be called.
 @end defvar
-@node Subroutines of Visiting
+@node Subroutines of Visiting,  , Visiting Functions, Visiting Files
 @subsection Subroutines of Visiting
 The @code{find-file-noselect} function uses the
 @code{create-file-buffer} and @code{after-find-file} functions as
 subroutines.  Sometimes it is useful to call them directly.
 The last thing @code{after-find-file} does is call all the functions
 in @code{find-file-hooks}.
 @end defun
-@node Saving Buffers
+@node Saving Buffers, Reading from Files, Visiting Files, Files
 @section Saving Buffers
 When you edit a file in XEmacs, you are actually working on a buffer
 that is visiting that file---that is, the contents of the file are
 copied into the buffer and the copy is what you edit.  Changes to the
 If the value of the variable is @code{nil}, then @code{save-buffer}
 doesn't add newlines at all.  @code{nil} is the default value, but a few
 major modes set it to @code{t} in particular buffers.
 @end defopt
-@node Reading from Files
+@node Reading from Files, Writing to Files, Saving Buffers, Files
 @section Reading from Files
 You can copy a file from the disk and insert it into a buffer
 using the @code{insert-file-contents} function.  Don't use the user-level
 command @code{insert-file} in a Lisp program, as that sets the mark.
 If you want to pass a file name to another process so that another
 program can read the file, use the function @code{file-local-copy}; see
 @ref{Magic File Names}.
-@node Writing to Files
+@node Writing to Files, File Locks, Reading from Files, Files
 @section Writing to Files
 You can write the contents of a buffer, or part of a buffer, directly
 to a file on disk using the @code{append-to-file} and
 @code{write-region} functions.  Don't use these functions to write to
 nor @code{nil} nor a string, then this message is inhibited.  This
 feature is useful for programs that use files for internal purposes,
 files that the user does not need to know about.
 @end deffn
-@node File Locks
+@node File Locks, Information about Files, Writing to Files, Files
 @section File Locks
 @cindex file locks
 When two users edit the same file at the same time, they are likely to
 interfere with each other.  XEmacs tries to prevent this situation from
 to do.  If you wish, you can replace the @code{ask-user-about-lock}
 function with your own version that decides in another way.  The code
 for its usual definition is in @file{userlock.el}.
 @end defun
-@node Information about Files
+@node Information about Files, Changing File Attributes, File Locks, Files
 @section Information about Files
 The functions described in this section all operate on strings that
 designate file names.  All the functions have names that begin with the
 word @samp{file}.  These functions all return information about actual
 * Kinds of Files::          Is it a directory?  A symbolic link?
 * Truenames::		    Eliminating symbolic links from a file name.
 * File Attributes::         How large is it?  Any other names?  Etc.
 @end menu
-@node Testing Accessibility
+@node Testing Accessibility, Kinds of Files, Information about Files, Information about Files
 @subsection Testing Accessibility
 @cindex accessibility of a file
 @cindex file accessibility
 These functions test for permission to access a file in specific ways.
 You can use @code{file-attributes} to get a file's last modification
 time as a list of two numbers.  @xref{File Attributes}.
 @end defun
-@node Kinds of Files
+@node Kinds of Files, Truenames, Testing Accessibility, Information about Files
 @subsection Distinguishing Kinds of Files
 This section describes how to distinguish various kinds of files, such
 as directories, symbolic links, and ordinary files.
 This function returns @code{t} if the file @var{filename} exists and is
 a regular file (not a directory, symbolic link, named pipe, terminal, or
 other I/O device).
 @end defun
-@node Truenames
+@node Truenames, File Attributes, Kinds of Files, Information about Files
 @subsection Truenames
 @cindex truename (of file)
 @c Emacs 19 features
 The @dfn{truename} of a file is the name that you get by following
 value of @code{default-directory} is used.
 @end defun
 @xref{Buffer File Name}, for related information.
-@node File Attributes
+@node File Attributes,  , Truenames, Information about Files
 @subsection Other Information about Files
 This section describes the functions for getting detailed information
 about a file, other than its contents.  This information includes the
 mode bits that control access permission, the owner and group numbers,
 @item -32252
 is on file system number -32252.
 @end table
 @end defun
-@node Changing File Attributes
+@node Changing File Attributes, File Names, Information about Files, Files
 @section Changing File Names and Attributes
 @cindex renaming files
 @cindex copying files
 @cindex deleting files
 @cindex linking files
 On MS-DOS, there is no such thing as an ``executable'' file mode bit.
 So Emacs considers a file executable if its name ends in @samp{.com},
 @samp{.bat} or @samp{.exe}.  This is reflected in the values returned
 by @code{file-modes} and @code{file-attributes}.
-@node File Names
+@node File Names, Contents of Directories, Changing File Attributes, Files
 @section File Names
 @cindex file names
 Files are generally referred to by their names, in XEmacs as elsewhere.
 File names in XEmacs are represented as strings.  The functions that
 * Unique File Names::     Generating names for temporary files.
 * File Name Completion::  Finding the completions for a given file name.
 * User Name Completion::  Finding the completions for a given user name.
 @end menu
-@node File Name Components
+@node File Name Components, Directory Names, File Names, File Names
 @subsection File Name Components
 @cindex directory part (of file name)
 @cindex nondirectory part (of file name)
 @cindex version number (in file name)
 (file-name-sans-extension "big.hack/foo")
 @result{} "big.hack/foo"
 @end example
 @end defun
-@node Directory Names
+@node Directory Names, Relative File Names, File Name Components, File Names
 @subsection Directory Names
 @cindex directory name
 @cindex file name of directory
 A @dfn{directory name} is the name of a directory.  A directory is a
 @c This function applies abbreviations from @code{directory-abbrev-alist}
 @c to its argument, and substitutes @samp{~} for the user's home
 @c directory.
 @c @end defun
-@node Relative File Names
+@node Relative File Names, File Name Expansion, Directory Names, File Names
 @subsection Absolute and Relative File Names
 @cindex absolute file name
 @cindex relative file name
 All the directories in the file system form a tree starting at the
 @result{} t
 @end group
 @end example
 @end defun
-@node File Name Expansion
+@node File Name Expansion, Unique File Names, Relative File Names, File Names
 @subsection Functions that Expand Filenames
 @cindex expansion of file names
 @dfn{Expansion} of a file name means converting a relative file name
 to an absolute one.  Since this is done relative to a default directory,
 @result{} "/xcssun/users/rms/foo"
 @end group
 @end example
 @end defun
-@node Unique File Names
+@node Unique File Names, File Name Completion, File Name Expansion, File Names
 @subsection Generating Unique File Names
 Some programs need to write temporary files.  Here is the usual way to
 construct a name for such a file:
 To avoid confusion, each Lisp application should preferably use a unique
 @var{prefix} to @code{make-temp-name}.
 @end defun
-@node File Name Completion
+@node File Name Completion, User Name Completion, Unique File Names, File Names
 @subsection File Name Completion
 @cindex file name completion subroutines
 @cindex completion, file name
 This section describes low-level subroutines for completing a file
 @result{} (".o" ".elc" "~" ".dvi")
 @end group
 @end example
 @end defopt
-@node User Name Completion
+@node User Name Completion,  , File Name Completion, File Names
 @subsection User Name Completion
 @cindex user name completion subroutines
 @cindex completion, user name
 This section describes low-level subroutines for completing a user
 @code{user-name-completion}, and a boolean indicating whether that
 completion was unique.
 @end defun
-@node Contents of Directories
+@node Contents of Directories, Create/Delete Dirs, File Names, Files
 @section Contents of Directories
 @cindex directory-oriented functions
 @cindex file names in directory
 A directory is a kind of file that contains other files entered under
 @defvar insert-directory-program
 This variable's value is the program to run to generate a directory listing
 for the function @code{insert-directory}.
 @end defvar
-@node Create/Delete Dirs
+@node Create/Delete Dirs, Magic File Names, Contents of Directories, Files
 @section Creating and Deleting Directories
 @c Emacs 19 features
 Most XEmacs Lisp file-manipulation functions get errors when used on
 files that are directories.  For example, you cannot delete a directory
 This function deletes the directory named @var{dirname}.  The function
 @code{delete-file} does not work for files that are directories; you
 must use @code{delete-directory} in that case.
 @end deffn
-@node Magic File Names
+@node Magic File Names, Partial Files, Create/Delete Dirs, Files
 @section Making Certain File Names ``Magic''
 @cindex magic file names
 @c Emacs 19 feature
 You can implement special handling for certain file names.  This is
 This is useful for running a subprocess; every subprocess must have a
 non-magic directory to serve as its current directory, and this function
 is a good way to come up with one.
 @end defun
-@node Partial Files
+@node Partial Files, Format Conversion, Magic File Names, Files
 @section Partial Files
 @cindex partial files
 @menu
 * Intro to Partial Files::
 * Creating a Partial File::
 * Detached Partial Files::
 @end menu
-@node Intro to Partial Files
+@node Intro to Partial Files, Creating a Partial File, Partial Files, Partial Files
 @subsection Intro to Partial Files
 A @dfn{partial file} is a section of a buffer (called the @dfn{master
 buffer}) that is placed in its own buffer and treated as its own file.
 Changes made to the partial file are not reflected in the master buffer
 When a partial file buffer is first modified, the master buffer is
 automatically marked as modified so that saving the master buffer will
 work correctly.
-@node Creating a Partial File
+@node Creating a Partial File, Detached Partial Files, Intro to Partial Files, Partial Files
 @subsection Creating a Partial File
 @deffn Command make-file-part &optional start end name buffer
 Make a file part on buffer @var{buffer} out of the region.  Call it
 @var{name}.  This command creates a new buffer containing the contents
 default to the beginning of @var{buffer}, the end of @var{buffer}, a
 name generated from @var{buffer}'s name, and the current buffer,
 respectively.
 @end deffn
-@node Detached Partial Files
+@node Detached Partial Files,  , Creating a Partial File, Partial Files
 @subsection Detached Partial Files
 Every partial file has an extent in the master buffer associated with it
 (called the @dfn{master extent}), marking where in the master buffer the
 partial file begins and ends.  If the text in master buffer that is
 this is the case, XEmacs warns the user of this and the master extent is
 deleted out of the master buffer, disconnecting the file part.  The file
 part's filename is cleared and thus must be explicitly specified if the
 detached file part is to be saved.
-@node Format Conversion
+@node Format Conversion, Files and MS-DOS, Partial Files, Files
 @section File Format Conversion
 @cindex file format conversion
 @cindex encoding file formats
 @cindex decoding file formats
 @code{buffer-file-format}; but it is used instead of
 @code{buffer-file-format} for writing auto-save files.  This variable
 is always local in all buffers.
 @end defvar
-@node Files and MS-DOS
+@node Files and MS-DOS,  , Format Conversion, Files
 @section Files and MS-DOS
 @cindex MS-DOS file types
 @cindex file types on MS-DOS
 @cindex text files and binary files
 @cindex binary files and text files

Mercurial > hg > xemacs-beta

comparison man/lispref/files.texi @ 5791:9fae6227ede5