|
From: Earnie B. <ea...@us...> - 2005-05-22 10:13:35
|
Update of /cvsroot/mingw/msys/packages/bash/2.05b/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv10360/2.05b/doc Added Files: FAQ INTRO Makefile.in README article.ms bash.1 bashbug.1 bashref.info bashref.texi builtins.1 htmlpost.sh rbash.1 texinfo.tex Log Message: Pristine source --- NEW FILE: FAQ --- This is the Bash FAQ, version 3.20, for Bash version 2.05b. This document contains a set of frequently-asked questions concerning Bash, the GNU Bourne-Again Shell. Bash is a freely-available command interpreter with advanced features for both interactive use and shell programming. Another good source of basic information about shells is the collection of FAQ articles periodically posted to comp.unix.shell. Questions and comments concerning this document should be sent to ch...@po.... This document is available for anonymous FTP with the URL ftp://ftp.cwru.edu/pub/bash/FAQ The Bash home page is http://cnswww.cns.cwru.edu/~chet/bash/bashtop.html [...1671 lines suppressed...] a better loadable interface to perl with access to the shell builtins and variables (contributions gratefully accepted) ksh93-like `nameref' variables ksh93-like `+=' variable assignment operator ksh93-like `xx.yy' variables (including some of the .sh.* variables) and associated disipline functions Some of the new ksh93 pattern matching operators, like backreferencing H5) When will the next release appear? The next version will appear sometime in 2002. Never make predictions. This document is Copyright 1995-2002 by Chester Ramey. Permission is hereby granted, without written agreement and without license or royalty fees, to use, copy, and distribute this document for any purpose, provided that the above copyright notice appears in all copies of this document and that the contents of this document remain unaltered. --- NEW FILE: builtins.1 --- .\" This is a hack to force bash builtins into the whatis database .\" and to get the list of builtins to come up with the man command. .TH BASH_BUILTINS 1 "2001 November 27" "GNU Bash-2.05a" .SH NAME bash, :, ., [, alias, bg, bind, break, builtin, cd, command, compgen, complete, continue, declare, dirs, disown, echo, enable, eval, exec, exit, export, fc, fg, getopts, hash, help, history, jobs, kill, let, local, logout, popd, printf, pushd, pwd, read, readonly, return, set, shift, shopt, source, suspend, test, times, trap, type, typeset, ulimit, umask, unalias, unset, wait \- bash built-in commands, see \fBbash\fR(1) .SH BASH BUILTIN COMMANDS .nr zZ 1 .so bash.1 .SH SEE ALSO bash(1), sh(1) --- NEW FILE: Makefile.in --- # This Makefile is for the Bash/documentation directory -*- text -*-. # # Copyright (C) 1996 Free Software Foundation, Inc. # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2, or (at your option) # any later version. # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111 USA. # SHELL = @MAKE_SHELL@ RM = rm -f topdir = @top_srcdir@ srcdir = @srcdir@ VPATH = .:@srcdir@ prefix = @prefix@ exec_prefix = @exec_prefix@ infodir = @infodir@ # set this to a directory name to have the HTML files installed htmldir = @htmldir@ # Support an alternate destination root directory for package building DESTDIR = mandir = @mandir@ manpfx = man man1ext = .1 man1dir = $(mandir)/$(manpfx)1 man3ext = .3 man3dir = $(mandir)/$(manpfx)3 INSTALL = @INSTALL@ INSTALL_DATA = @INSTALL_DATA@ BUILD_DIR = @BUILD_DIR@ # bad style RL_LIBDIR = $(topdir)/lib/readline # unused TEXINDEX = texindex TEX = tex MAKEINFO = makeinfo TEXI2DVI = ${topdir}/support/texi2dvi TEXI2HTML = ${topdir}/support/texi2html MAN2HTML = ${BUILD_DIR}/support/man2html HTMLPOST = ${srcdir}/htmlpost.sh QUIETPS = #set this to -q to shut up dvips PAPERSIZE = letter # change to a4 for A4-size paper PSDPI = 300 # could be 600 if you like DVIPS = dvips -D ${PSDPI} $(QUIETPS) -t ${PAPERSIZE} -o $@ # tricky TEXINPUTDIR = $(RL_LIBDIR)/doc # These tools might not be available; they're not required DVIPDF = dvipdfm -o $@ -p ${PAPERSIZE} PSPDF = gs -sPAPERSIZE=${PAPERSIZE} -sDEVICE=pdfwrite -dNOPAUSE -dBATCH -sOutputFile=$@ MKDIRS = ${topdir}/support/mkdirs # This should be a program that converts troff to an ascii-readable format NROFF = groff -Tascii # This should be a program that converts troff to postscript GROFF = groff HSUSER = $(RL_LIBDIR)/doc/hsuser.texinfo RLUSER = $(RL_LIBDIR)/doc/rluser.texinfo .SUFFIXES: .0 .1 .3 .ms .ps .txt .dvi .html .pdf .1.ps: $(RM) $@ -${GROFF} -man $< > $@ .1.0: $(RM) $@ -${NROFF} -man $< > $@ .1.html: $(RM) $@ -${MAN2HTML} $< | ${HTMLPOST} > $@ .ms.ps: $(RM) $@ -${GROFF} -ms $< > $@ .ms.txt: $(RM) $@ -${NROFF} -ms $< > $@ .3.ps: $(RM) $@ -${GROFF} -man $< > $@ .3.0: $(RM) $@ -${NROFF} -man $< > $@ .3.html: $(RM) $@ -${MAN2HTML} $< > $@ .ps.pdf: $(RM) $@ -${PSPDF} $< .dvi.pdf: $(RM) $@ -${DVIPDF} $< all: ps info dvi text html nodvi: ps info text html PSFILES = bash.ps bashbug.ps article.ps builtins.ps rbash.ps DVIFILES = bashref.dvi bashref.ps INFOFILES = bashref.info MAN0FILES = bash.0 bashbug.0 builtins.0 rbash.0 HTMLFILES = bashref.html bash.html PDFFILES = bash.pdf bashref.pdf article.pdf rose94.pdf ps: ${PSFILES} dvi: ${DVIFILES} info: ${INFOFILES} text: ${MAN0FILES} html: ${HTMLFILES} pdf: ${PDFFILES} bashref.dvi: $(srcdir)/bashref.texi $(HSUSER) $(RLUSER) TEXINPUTS=.:$(TEXINPUTDIR):$$TEXINPUTS $(TEXI2DVI) $(srcdir)/bashref.texi bashref.ps: bashref.dvi $(RM) $@ $(DVIPS) bashref.dvi bashref.info: $(srcdir)/bashref.texi $(HSUSER) $(RLUSER) $(MAKEINFO) --no-split -I$(TEXINPUTDIR) $(srcdir)/bashref.texi bashref.html: bashref.texi $(HSUSER) $(RLUSER) $(TEXI2HTML) -menu -monolithic -I $(TEXINPUTDIR) $(srcdir)/bashref.texi new-bashref.dvi: $(srcdir)/new-bashref.texi $(HSUSER) $(RLUSER) TEXINPUTS=.:$(TEXINPUTDIR):$$TEXINPUTS $(TEXI2DVI) $(srcdir)/new-bashref.texi new-bashref.ps: new-bashref.dvi $(RM) $@ $(DVIPS) new-bashref.dvi new-bashref.info: $(srcdir)/new-bashref.texi $(HSUSER) $(RLUSER) $(MAKEINFO) --no-split -I$(TEXINPUTDIR) $(srcdir)/new-bashref.texi #bash.dvi: bash.texinfo $(HSUSER) $(RLUSER) # TEXINPUTS=.:$(TEXINPUTDIR):$$TEXINPUTS $(TEXI2DVI) bash.texinfo # #bashman.ps: bash.dvi # $(RM) $@ # $(DVIPS) bash.dvi bash.txt: bash.1 bash.ps: bash.1 bash.html: bash.1 $(MAN2HTML) bashbug.ps: bashbug.1 builtins.ps: builtins.1 bash.1 rbash.ps: rbash.1 bash.1 bash.0: bash.1 bashbug.0: bashbug.1 builtins.0: builtins.1 bash.1 rbash.0: rbash.1 bash.1 article.ps: article.ms article.pdf: article.ps bashref.pdf: bashref.dvi bash.pdf: bash.ps rose94.pdf: rose94.ps $(MAN2HTML): ${topdir}/support/man2html.c -( cd ${BUILD_DIR}/support ; ${MAKE} ${MFLAGS} man2html) clean: $(RM) *.aux *.bak *.cp *.fn *.ky *.log *.pg *.toc *.tp *.vr *.cps \ *.pgs *.bt *.bts *.rw *.rws *.fns *.kys *.tps *.vrs *.o ${RM} core *.core mostlyclean: clean $(RM) Makefile distclean: clean maybe-clean $(RM) Makefile maintainer-clean: clean ${RM} ${PSFILES} ${DVIFILES} ${INFOFILES} ${MAN0FILES} ${HTMLFILES} ${RM} ${CREATED_FAQ} $(RM) Makefile maybe-clean: -if test "X$(topdir)" != "X$(BUILD_DIR)"; then \ $(RM) ${PSFILES} ${DVIFILES} ${INFOFILES} ${MAN0FILES} ${HTMLFILES}; \ fi installdirs: -test -d $(man1dir) || $(SHELL) ${MKDIRS} $(DESTDIR)$(man1dir) -test -d $(infodir) || $(SHELL) ${MKDIRS} $(DESTDIR)$(infodir) -if test -n "$(htmldir)" ; then \ test -d $(htmldir) || $(SHELL) ${MKDIRS} $(DESTDIR)$(htmldir) ; \ fi install: info installdirs -$(INSTALL_DATA) $(srcdir)/bash.1 $(DESTDIR)$(man1dir)/bash${man1ext} -$(INSTALL_DATA) $(srcdir)/bashbug.1 $(DESTDIR)$(man1dir)/bashbug${man1ext} # uncomment the next line to install the builtins man page # -$(INSTALL_DATA) $(srcdir)/builtins.1 $(DESTDIR)$(man1dir)/bash_builtins${man1ext} -$(INSTALL_DATA) $(srcdir)/bashref.info $(DESTDIR)$(infodir)/bash.info # run install-info if it is present to update the info directory if $(SHELL) -c 'install-info --version' >/dev/null 2>&1; then \ install-info --dir-file=$(DESTDIR)$(infodir)/dir $(DESTDIR)$(infodir)/bash.info; \ else true; fi # if htmldir is set, install the html files into that directory -if test -n "${htmldir}" ; then \ $(INSTALL_DATA) $(srcdir)/bash.html $(DESTDIR)$(htmldir) ; \ $(INSTALL_DATA) $(srcdir)/bashref.html $(DESTDIR)$(htmldir) ; \ fi uninstall: -$(RM) $(DESTDIR)$(man1dir)/bash${man1ext} $(DESTDIR)$(man1dir)/bashbug${man1ext} $(RM) $(DESTDIR)$(infodir)/bash.info -if test -n "$(htmldir)" ; then \ $(RM) $(DESTDIR)$(htmldir)/bash.html ; \ $(RM) $(DESTDIR)$(htmldir)/bashref.html ; \ fi # for use by chet CREATED_FAQ = faq.news faq.news2 faq.mail faq.version faq: ${CREATED_FAQ} faq.version: FAQ.version FAQ sh mkfaqvers FAQ.version > $@ faq.headers.mail: FAQ.headers.mail FAQ sh mkfaqvers FAQ.headers.mail > $@ faq.headers.news: FAQ.headers.news FAQ sh mkfaqvers FAQ.headers.news > $@ faq.headers.news2: FAQ.headers.news2 FAQ sh mkfaqvers FAQ.headers.news2 > $@ faq.news: FAQ faq.headers.news faq.version $(RM) $@ cat faq.headers.news faq.version FAQ > $@ faq.news2: FAQ faq.headers.news2 faq.version $(RM) $@ cat faq.headers.news2 faq.version FAQ > $@ faq.mail: FAQ faq.headers.mail faq.version $(RM) $@ cat faq.headers.mail faq.version FAQ > $@ inst: bashref.texi $(SHELL) ./mkinstall cmp -s INSTALL ../INSTALL || mv INSTALL ../INSTALL $(RM) INSTALL posix: bashref.texi $(SHELL) ./mkposix cmp -s POSIX ../POSIX || mv POSIX ../POSIX $(RM) POSIX rbash: bashref.texi $(SH) ./mkrbash cmp -s RBASH ../RBASH || mv RBASH ../RBASH $(RM) RBASH xdist: inst posix rbash --- NEW FILE: texinfo.tex --- % texinfo.tex -- TeX macros to handle Texinfo files. % % Load plain if necessary, i.e., if running under initex. \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi % \def\texinfoversion{1999-09-25.10} % % Copyright (C) 1985, 86, 88, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99 % Free Software Foundation, Inc. % % This texinfo.tex file is free software; you can redistribute it and/or % modify it under the terms of the GNU General Public License as % published by the Free Software Foundation; either version 2, or (at % your option) any later version. % % This texinfo.tex file is distributed in the hope that it will be % useful, but WITHOUT ANY WARRANTY; without even the implied warranty % of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU % General Public License for more details. [...5953 lines suppressed...] % Say @foo, not \foo, in error messages. @escapechar = `@@ % These look ok in all fonts, so just make them not special. @catcode`@& = @other @catcode`@# = @other @catcode`@% = @other @c Set initial fonts. @textfonts @rm @c Local variables: @c eval: (add-hook 'write-file-hooks 'time-stamp) @c page-delimiter: "^\\\\message" @c time-stamp-start: "def\\\\texinfoversion{" @c time-stamp-format: "%:y-%02m-%02d.%02H" @c time-stamp-end: "}" @c End: --- NEW FILE: article.ms --- .de SE \" start example .sp .5 .RS .ft CR .nf .. .de EE \" end example .fi .sp .5 .RE .ft R .. .TL Bash \- The GNU shell* .AU Chet Ramey Case Western Reserve University ch...@po... .FS [...1075 lines suppressed...] are included, and a \*Qminimal\*U configuration, which omits job control, aliases, history and command line editing, the directory stack and .B pushd/popd/dirs, process substitution, prompt string special character decoding, and the .I select construct. This minimal version is designed to be a drop-in replacement for the traditional \s-1UNIX\s+1 /bin/sh, and is included as the Linux /bin/sh in several packagings. .NH 1 Conclusion .PP Bash is a worthy successor to sh. It is sufficiently portable to run on nearly every version of \s-1UNIX\s+1 from 4.3 BSD to SVR4.2, and several \s-1UNIX\s+1 workalikes. It is robust enough to replace sh on most of those systems, and provides more functionality. It has several thousand regular users, and their feedback has helped to make it as good as it is today \- a testament to the benefits of free software. --- NEW FILE: htmlpost.sh --- #! /bin/sh # # Some of these should really be done by man2html # # The ~/xxx links don't really work -- netscape doesn't expand the home # directory of the user running navigator # sed -e 's|<B>gnu.bash.bug</B>|<A HREF="news:gnu.bash.bug">gnu.bash.bug</A>|g' \ -e 's|<I>/bin/bash</I>|<A HREF="file:/bin/bash"><I>/bin/bash</I></A>|g' \ -e 's|<I>/etc/profile</I>|<A HREF="file:/etc/profile"><I>/etc/profile</I></A>|g' \ -e 's|<I>~/.bash_profile</I>|<A HREF="file:~/.bash_profile"><I>~/.bash_profile</I></A>|g' \ -e 's|<I>~/.bash_login</I>|<A HREF="file:~/.bash_login"><I>~/.bash_login</I></A>|g' \ -e 's|<I>~/.profile</I>|<A HREF="file:~/.profile"><I>~/.profile</I></A>|g' \ -e 's|<I>~/.bashrc</I>|<A HREF="file:~/.bashrc"><I>~/.bashrc</I></A>|g' \ -e 's|<I>~/.bash_logout</I>|<A HREF="file:~/.bash_logout"><I>~/.bash_logout</I></A>|g' \ -e 's|<I>~/.bash_history</I>|<A HREF="file:~/.bash_history"><I>~/.bash_history</I></A>|g' \ -e 's|<I>~/.inputrc</I>|<A HREF="file:~/.inputrc"><I>~/.inputrc</I></A>|g' \ -e 's|<I>/etc/inputrc</I>|<A HREF="file:/etc/inputrc"><I>/etc/inputrc</I></A>|g' --- NEW FILE: bashbug.1 --- .TH BASHBUG 1 "1998 July 30" GNU .SH NAME bashbug \- report a bug in bash .SH SYNOPSIS \fBbashbug\fP [\fIaddress\fP] .SH DESCRIPTION .B bashbug is a shell script to help the user compose and mail bug reports concerning bash in a standard format. .B bashbug invokes the editor specified by the environment variable .SM .B EDITOR on a temporary copy of the bug report format outline. The user must fill in the appropriate fields and exit the editor. .B bashbug then mails the completed report to \fIb...@gn...\fP, or \fIaddress\fP. If the report cannot be mailed, it is saved in the file \fIdead.bashbug\fP in the invoking user's home directory. .PP The bug report format outline consists of several sections. The first section provides information about the machine, operating system, the bash version, and the compilation environment. The second section should be filled in with a description of the bug. The third section should be a description of how to reproduce the bug. The optional fourth section is for a proposed fix. Fixes are encouraged. .SH ENVIRONMENT .B bashbug will utilize the following environment variables if they exist: .TP .B EDITOR Specifies the preferred editor. If .SM .B EDITOR is not set, .B bashbug defaults to .BR emacs . .TP .B HOME Directory in which the failed bug report is saved if the mail fails. --- NEW FILE: rbash.1 --- .TH RBASH 1 "1999 Nov 29" GNU .SH NAME rbash \- restricted bash, see \fBbash\fR(1) .SH RESTRICTED SHELL .nr zY 1 .so bash.1 .SH SEE ALSO bash(1) --- NEW FILE: bashref.info --- This is bashref.info, produced by makeinfo version 4.1 from /usr/homes/chet/src/bash/src/doc/bashref.texi. INFO-DIR-SECTION Utilities START-INFO-DIR-ENTRY * Bash: (bash). The GNU Bourne-Again SHell. END-INFO-DIR-ENTRY This text is a brief description of the features that are present in the Bash shell. This is Edition 2.5b, last updated 15 July 2002, of `The GNU Bash Reference Manual', for `Bash', Version 2.05b. Copyright (C) 1991-2002 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice [...8454 lines suppressed...] Node: Word Designators279653 Node: Modifiers281282 Node: Installing Bash282599 Node: Basic Installation283741 Node: Compilers and Options286426 Node: Compiling For Multiple Architectures287160 Node: Installation Names288817 Node: Specifying the System Type289628 Node: Sharing Defaults290337 Node: Operation Controls291002 Node: Optional Features291953 Node: Reporting Bugs299895 Node: Major Differences From The Bourne Shell300992 Node: Builtin Index315476 Node: Reserved Word Index319067 Node: Variable Index320543 Node: Function Index326841 Node: Concept Index331391 End Tag Table --- NEW FILE: INTRO --- BASH - The Bourne-Again Shell Bash is the shell, or command language interpreter, that will appear in the GNU operating system. Bash is an sh-compatible shell that incorporates useful features from the Korn shell (ksh) and C shell (csh). It is intended to conform to the IEEE POSIX P1003.2/ISO 9945.2 Shell and Tools standard. It offers functional improvements over sh for both programming and interactive use. In addition, most sh scripts can be run by Bash without modification. Bash is quite portable. It uses a configuration system that discovers characteristics of the compilation platform at build time, and may therefore be built on nearly every version of UNIX. Ports to UNIX-like systems such as QNX and Minix and to non-UNIX systems such as OS/2, Windows 95, and Windows NT are available. Bash includes the following features: Editing and Completion Bash offers a command-line editing facility which permits users to edit command lines using familiar emacs or vi-style editing commands. Editing allows corrections to be made without having to erase back to the point of error or start the command line anew. The editing facilities include a feature that allows users to complete command and file names. The Bash line editing library is fully customizable. Users may define their own key bindings -- the action taken when a key is pressed. A number of variables to fine-tune editing behavior are also available. History and Command Re-entry The Bash history feature remembers commands entered to the shell and allows them to be recalled and re-executed. The history list may be of unlimited size. Bash allows users to search for previous commands and reuse portions of those commands when composing new ones. The history list may be saved across shell sessions. Bash allows users to control which commands are saved on the history list. Job Control On systems that support it, Bash provides an interface to the operating system's job control facilities, which allow processes to be suspended and restarted, and moved between the foreground and background. Bash allows users to selectively `forget' about background jobs. Shell Functions and Aliases These mechanisms are available to bind a user-selected identifier to a list of commands that will be executed when the identifier is used as a command name. Functions allow local variables and recursion, and have access to the environment of the calling shell. Aliases may be used to create a mnemonic for a command name, expand a single word to a complex command, or ensure that a command is called with a basic set of options. Arrays Bash-2.0 supports indexed arrays of unlimited size. The subscript for an array is an arithmetic expression. Arrays may be assigned to with a new compound assignment syntax, and several builtins have options to operate on array variables. Bash includes a number of built-in array variables. Arithmetic Bash allows users to perform integer arithmetic in any base from two to sixty-four. Nearly all of the C language arithmetic operators are available with the same syntax and precedence as in C. Arithmetic expansion allows an arithmetic expression to be evaluated and the result substituted into the command line. Shell variables can be used as operands, and the value of an expression may be assigned to a variable. An arithmetic expression may be used as a command; the exit status of the command is the value of the expression. ANSI-C Quoting There is a new quoting syntax that allows backslash-escaped characters in strings to be expanded according to the ANSI C standard. Tilde Expansion Users' home directories may be expanded using this feature. Words beginning with a tilde may also be expanded to the current or previous working directory. Brace Expansion Brace expansion is a convenient way to generate a list of strings that share a common prefix or suffix. Substring Capabilities Bash allows new strings to be created by removing leading or trailing substrings from existing variable values, or by specifying a starting offset and length. Portions of variable values may be matched against shell patterns and the matching portion removed or a new value substituted. Indirect Variable Expansion Bash makes it easy to find the value of a shell variable whose name is the value of another variable. Expanded I/O Capabilities Bash provides several input and output features not available in sh, including the ability to: o specify a file or file descriptor for both input and output o read from or write to asynchronous processes using named pipes o read lines ending in backslash o display a prompt on the terminal before a read o format menus and interpret responses to them o echo lines exactly as input without escape processing Control of Builtin Commands Bash implements several builtin commands to give users more control over which commands are executed. The enable builtin allows other builtin commands to be selectively enabled or disabled. The command and builtin builtins change the order in which the shell searches for commands. On systems that provide dynamic loading, new builtins may be loaded into a running shell from a shared object file. These new builtins have access to all of the shell facilities. Help Bash includes a built-in help facility. Shell Optional Behavior There is a great deal of customizable shell behavior. The shopt builtin command provides a unified interface that allows users to alter shell defaults. Prompt Customization Bash allows the primary and secondary prompts to be customized by interpreting a number of backslash-escaped special characters. Parameter and variable expansion is also performed on the values of the primary and secondary prompt strings before they are displayed. Security Bash provides a restricted shell environment. It is also possible to control the execution of setuid/setgid scripts. Directory Stack Bash provides a `directory stack', to which directories may be added and removed. The current directory may be changed to any directory in the stack. It is easy to toggle between two directories in the stack. The directory stack may be saved and restored across different shell invocations. POSIX Mode Bash is nearly completely conformant to POSIX.2. POSIX mode changes those few areas where the Bash default behavior differs from the standard to match the standard. In POSIX mode, Bash is POSIX.2 compliant. Internationalization Bash provides a new quoting syntax that allows strings to be translated according to the current locale. The locale in which the shell itself runs may also be changed, so that the shell messages themselves may be language-specific. The command-line editing facilities allow the input of eight-bit characters, so most of the ISO-8859 family of character sets are supported. Command Timing Bash allows external commands, shell builtin commands and shell functions to be timed. The format used to display the timing information may be changed by the user. --- NEW FILE: bash.1 --- .\" .\" MAN PAGE COMMENTS to .\" .\" Chet Ramey .\" Information Network Services .\" Case Western Reserve University .\" ch...@in... .\" .\" Last Change: Mon Jul 15 15:20:56 EDT 2002 .\" .\" bash_builtins, strip all but Built-Ins section .if \n(zZ=1 .ig zZ .if \n(zY=1 .ig zY .TH BASH 1 "2002 July 15" "GNU Bash-2.05b" .\" .\" There's some problem with having a `@' .\" in a tagged paragraph with the BSD man macros. .\" It has to do with `@' appearing in the }1 macro. .\" This is a problem on 4.3 BSD and Ultrix, but Sun [...8323 lines suppressed...] .PP Aliases are confusing in some uses. .PP Shell builtin commands and functions are not stoppable/restartable. .PP Compound commands and command sequences of the form `a ; b ; c' are not handled gracefully when process suspension is attempted. When a process is stopped, the shell immediately executes the next command in the sequence. It suffices to place the sequence of commands between parentheses to force it into a subshell, which may be stopped as a unit. .PP Commands inside of \fB$(\fP...\fB)\fP command substitution are not parsed until substitution is attempted. This will delay error reporting until some time after the command is entered. .PP Array variables may not (yet) be exported. .zZ .zY --- NEW FILE: README --- This directory contains the bash documentation. FAQ - a set of frequently-asked questions about Bash with answers INTRO - a short introduction to bash article.ms - an article I wrote about bash for The Linux Journal bash.1 - the bash man page builtins.1 - a man page that documents the builtins, extracted from bash.1 bashref.texi - the `bash reference manual' bashref.info - the `bash reference manual' processed by `makeinfo' readline.3 - the readline man page The `.ps' files are postscript versions of the above. The `.html' files are HTML versions of the man page and reference manual. The `.0' files are formatted manual pages. The `.txt' versions are ascii -- the output of `groff -Tascii'. The rest of this file explains how to use the `builtins.1' man page. For each command in the list of builtins create a file in man/man1 called: ${command}.1 eg. for.1 type.1 alias.1 etc. All these files are identical as follows: jaws@jaws(264)$ cat alias.1 .so man1/builtins.1 jaws@jaws(265)$ Make sure you adjust the .so line in builtins.1 to reflect where you put it. --- NEW FILE: bashref.texi --- \input texinfo.tex @c -*- texinfo -*- @c %**start of header @setfilename bashref.info @settitle Bash Reference Manual @c %**end of header @ignore Last Change: Mon Jul 15 15:21:16 EDT 2002 @end ignore @set EDITION 2.5b @set VERSION 2.05b @set UPDATED 15 July 2002 @set UPDATE-MONTH July 2002 @iftex @finalout @end iftex [...6826 lines suppressed...] @printindex bt @node Reserved Word Index @unnumbered Index of Shell Reserved Words @printindex rw @node Variable Index @unnumbered Parameter and Variable Index @printindex vr @node Function Index @unnumbered Function Index @printindex fn @node Concept Index @unnumbered Concept Index @printindex cp @contents @bye |