In 2003, Dmitry Rutsky joined
./X/org.texi.out:Richard @@texinfo:@sc{@@Stallman@@texinfo:}@@ commence' GNU.
./X/viper.texi.out:dm@scs.cs.nyu.edu (David Mazieres),
./X/reftex.texi.info:dominik@science.uva.nl, with contributions by Stephen
./coreutils/coreutils.texi:To specify a tab (@sc{ascii} 0x09) character instead of whitespace, use
./quagga/install.texi:Force to enable @sc{gnu}/Linux netlink interface. Quagga configure
./quagga/install.texi:There are several options available only to @sc{gnu}/Linux systems:
./quagga/install.texi:@footnote{@sc{gnu}/Linux has very flexible kernel configuration features}. If
./quagga/install.texi:you use @sc{gnu}/Linux, make sure that the current kernel configuration is
./quagga/install.texi:IPv6 support has been added in @sc{gnu}/Linux kernel version 2.2. If you
./quagga/install.texi:try to use the Quagga IPv6 feature on a @sc{gnu}/Linux kernel, please
./quagga/install.texi:these libraries will not be needed when you uses @sc{gnu} C library 2.1
./quagga/overview.texi: Quagga is distributed under the @sc{gnu} General Public License.
./quagga/overview.texi:which comes with @sc{gnu}/Linux or FreeBSD has some problems with running
./quagga/overview.texi:Currently Quagga supports @sc{gnu}/Linux and BSD. Porting Quagga
./quagga/overview.texi:@sc{gnu}/Linux
./quagga/overview.texi:of their original release (in case of @sc{gnu}/Linux, this is since the kernel's
./quagga/overview.texi:@sc{gnu}'s GCC
./foliot/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./g-golf/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gtypist/gtypist.cs.texi:Simon Baldwin @email{simonb@@sco.com} přepsal verzi D. Jason Penneyho,
./gtypist/gtypist.texi:@email{simonb@@sco.com, Simon Baldwin} rewrote the version of D. Jason
./gtypist/gtypist.texi:In 2003, @email{rutsky@@school.ioffe.rssi.ru, Dmitry Rutsky} joined
./gtypist/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gtypist/gtypist.es.texi:@email{simonb@@sco.com, Simon Baldwin} re-escribió la versión de
./gtypist/gtypist.es.texi:En 2003, @email{rutsky@@school.ioffe.rssi.ru, Dmitry Rutsky} se unió
./preview-latex/auctex.texi:Insert @sc{small caps} @samp{\textsc@{@point{}@}} text.
./preview-latex/auctex.texi:Insert @sc{swash} @samp{\textsw@{@point{}@}} text.
./preview-latex/quickstart.texi:Insert @sc{small caps} @samp{\textsc@{@point{}@}} text.
./preview-latex/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./preview-latex/history.texi:@samp{}, Uffe Kjaerulff
./preview-latex/history.texi:@samp{}.@refill
./preview-latex/macros.texi:@sc{\text\}
./preview-latex/preview-readme.texi:@cindex @sc{git} access
./idutils/idutils.texi:@sc{gnu} @command{find}, using its @option{-print0} predicate. Do not
./idutils/idutils.texi:virtual address space. A typical @sc{unix}-like operating system with
./idutils/idutils.texi:took over an hour on a @sc{vax 11/750} to build a database for a
./idutils/idutils.texi:@sc{4.1bsd} derived kernel. The first version of @file{lid} used the
./idutils/idutils.texi:@sc{unix} system utility @code{look}, modified to handle very long
./mdk/mdk_emacs.texi:@sc{mdk} adds support to Emacs for both writing and debugging MIX
./mdk/mdk_emacs.texi:This chapter shows how to use the Elisp modules included in @sc{mdk},
./mdk/mdk_emacs.texi:initiate an @sc{mdk}/@acronym{GUD} session inside Emacs with the command
./mdk/mdk_gstart.texi:using the @sc{mdk} utilities. Familiarity with the MIX mythical computer
./mdk/mdk_gstart.texi:when used with the @sc{mdk} utilities. As you can see in the above
./mdk/mdk_gstart.texi:fixed pre-defined column number, the @sc{mdk} assembler loosens this
./mdk/mdk_gstart.texi:and @code{mixguile}, are included in the @sc{mdk} tools. They are able to
./mdk/mdk_gstart.texi:favorite hardware provider. @sc{mdk} provides three software simulators of
./mdk/mdk_ack.texi:Many people have further contributed to @sc{mdk} by reporting problems,
./mdk/mdk_ack.texi:provided MIXAL test programs pinpointing bugs in the first @sc{mdk}
./mdk/mdk_ack.texi:has been following @sc{mdk}'s development for many years, indefatigably
./mdk/mdk_ack.texi:is the author of the German translation of @sc{mdk}'s user interface.
./mdk/mdk_ack.texi:kindly and thoroughly reviewed the @sc{mdk} documentation, providing
./mdk/mdk_ack.texi:has tested @sc{mdk} in a lot of Unix platforms, suggesting portability
./mdk/mdk_ack.texi:ported @sc{mdk} to different platforms, and created and/or maintain
./mdk/mdk_ack.texi:tested @sc{mdk} on different platforms, and helped fixing the configuration
./mdk/mdk_ack.texi:kept an eye on each @sc{mdk} release.
./mdk/mdk_ack.texi:@item @sc{mdk} was inspired by Darius Bacon's
./mdk/mdk_mixvm.texi:compiled @sc{mdk} with readline support, i.e., if GNU readline is
./mdk/mdk_mixvm.texi:@sc{mdk} configuration directory (@file{~/.mdk}).
./mdk/mdk_mixvm.texi:machine behaviour. This configuration is stored in the @sc{mdk}
./mdk/mdk_mixvm.texi:If you have compiled @sc{mdk} with @code{libguile} support
./mdk/mdk_mixasm.texi:form by @code{mixasm}, the MIXAL assembler included in @sc{mdk}. In this
./mdk/mdk_install.texi:@chapter Installing @sc{mdk}
./mdk/mdk_install.texi:GNU @sc{mdk} is distributed as a source tarball available for download in
./mdk/mdk_install.texi:The above sites contain the latest stable releases of @sc{mdk}. The
./mdk/mdk_install.texi:@uref{https://savannah.gnu.org/git/?group=mdk, @sc{mdk}'s Git page} for
./mdk/mdk_install.texi:In order to build and install @sc{mdk}, you will need the following
./mdk/mdk_install.texi:libguile is found, the @sc{mdk} utilities will be compiled with Guile
./mdk/mdk_install.texi:@sc{mdk} uses GNU Autoconf and Automake tools, and, therefore, should
./mdk/mdk_install.texi:The next command, @code{make}, will actually build the @sc{mdk} programs
./mdk/mdk_install.texi:@sc{mdk} includes extensive support for Emacs. Upon installation, all
./mdk/mdk_install.texi:@sc{mdk}'s @code{mixvm} and Emacs, via @acronym{GUD}. Place this file
./mdk/mdk_install.texi:@sc{mdk} will probably work on any GNU/Linux or BSD platform. If you
./mdk/mdk_bugs.texi:If you find a bug in @sc{mdk}, please send electronic mail to
./mdk/mdk_bugs.texi:@email{bug-mdk@@gnu.org, the @sc{mdk} bug list}.
./mdk/mdk.texi:@subtitle Edition @value{EDITION}, for GNU @sc{mdk} Version @value{VERSION}
./mdk/mdk.texi:@value{MIKE} is the author of the German translation of @sc{mdk}'s
./mdk/mdk.texi:* Getting started:: Basic usage of the @sc{mdk} tools.
./mdk/mdk.texi:* Copying:: @sc{mdk} licensing terms.
./mdk/mdk.texi:Installing @sc{mdk}
./mdk/mdk_mixguile.texi:@sc{mdk} emulators (@code{mixguile}, @code{mixvm} and @code{gmixvm}). See
./mdk/mdk_mixguile.texi:@sc{mdk} MIX virtual machines.
./mdk/mdk_mixguile.texi:it looks for a file named @file{mixguile.scm} in the user's @sc{mdk}
./mdk/mdk_mixguile.texi:language, Scheme, to extend the @sc{mdk} virtual machine emulators (see
./mdk/mdk_copying.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./mdk/mdk_gmixvm.texi:shipped with @sc{mdk}. In addition to having all the command-oriented
./mdk/mdk_gmixvm.texi:If you have built @sc{mdk} with GTK+ support (@pxref{Installing MDK}), a
./mdk/mdk_tut.texi:@cindex @sc{ov}
./mdk/mdk_tut.texi:@cindex @sc{cm}
./mdk/mdk_tut.texi:@dfn{off}). In this manual, this toggle is denoted @sc{ov}.
./mdk/mdk_tut.texi:@sc{cm}, and its possible values are abbreviated as @dfn{E}, @dfn{G} and
./mdk/mdk_tut.texi:set the @sc{cm} indicator to the result of the comparison (i.e. to
./mdk/mdk_tut.texi:we do in @sc{mdk} simulator). For the same reason, @sc{mdk} devices are
./mdk/mdk_tut.texi:provided by @sc{mdk} are described later on (@pxref{Getting started}).
./mdk/mdk_tut.texi:MIXAL assembler included in @sc{mdk}, @code{mixasm}, does not impose
./mdk/mdk_intro.texi:The @sc{mdk} package aims at providing such virtual development
./mdk/mdk_intro.texi:environment on a GNU box. Thus, @sc{mdk} offers you a set of utilities
./mdk/mdk_intro.texi:programs. As of version @value{VERSION}, @sc{mdk} includes
./mdk/mdk_intro.texi:description of the use of the @sc{mdk} utilities.
./tar/tar.texi:* Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
./tar/tar.texi:12:56:31 @sc{utc}, you will have to chose between @acronym{GNU} and
./proxyknife/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./proxyknife/proxyknife.texi:This manual documents @sc{gnu} Proxyknife(version @value{VERSION}, @value{UPDATED}), the customizable proxyhunter.
./proxyknife/proxyknife.texi:@sc{gnu} Proxyknife is a customizable multithread @dfn{proxy hunter}. Tt can help users behind strict firewall find suitable free proxies.
./proxyknife/proxyknife.texi:@sc{gnu} Proxyknife reads @dfn{proxylist}@footnote{The list of free proxies.} from the file, stdin or the web, then validates the free proxies and prints the good ones. Time intervals and the others which are userful to estimate the speed or capability of every proxy are also printed. The whole processing can be customized by the user, which is different from the other hunters.
./proxyknife/proxyknife.texi:In @sc{url} mode, Proxyknife can read a large number of proxies on machines with little memory. Tt works on GNU/Linux, SunOS, OSF1 or more.
./proxyknife/proxyknife.texi:1 (HTTP_CONNECT - @sc{http} proxy without authentication),
./proxyknife/proxyknife.texi:2 (SOCKS5_CONNECT - @sc{socks5} proxy without authentication),
./proxyknife/proxyknife.texi:5 (SOCKS4_CONNECT - @sc{socks4} proxy without authentication),
./proxyknife/proxyknife.texi:11 (HTTP_CONNECT_AUTH - @sc{http} proxy with basic authentication),
./proxyknife/proxyknife.texi:12 (SOCKS5_CONNECT_AUTH - @sc{socks5} proxy with username/password authentication),
./proxyknife/proxyknife.texi:If you have a @sc{http} proxy (@var{myproxy.com:8080}) without authentication, do it like this:
./proxyknife/proxyknife.texi:If your @dfn{myproxy} is a @sc{socks4} tunnel with host name @samp{myproxy.com}, port @samp{1080} and you can reach @uref{http://proxylist.kmip.net/list.html} via it:
./proxyknife/proxyknife.texi:If your @dfn{myproxy} is a @sc{socks5} tunnel with host name @var{myproxy.com}, port @var{1080}. You hope proxyknife reads proxylist from the local file named @samp{proxylist} and validates via @dfn{myproxy}:
./proxyknife/proxyknife.texi:If your @dfn{myproxy} (@var{myproxy.com:1080}, @var{userabc:pass123}) is a @sc{socks5} tunnel based on username/password authentication with host name @samp{myproxy.com}, port @samp{1080}, you can invoke proxyknife like this to do the same thing:
./proxyknife/proxyknife.texi:Free @sc{http} proxy supporting CONNECT method, free @sc{socks5} or @sc{socks4} proxy supporting CONNECT command.
./proxyknife/proxyknife.texi:A @sc{http} proxy(@samp{www.myhttptunnel.com:8080},supporting CONNECT method) with basic authentication . The username is @samp{abc}, the password is @samp{123}. A connection to @uref{http://youth.bupt.edu.cn/proxy/} or free proxies can be done via this @sc{http} proxy.
./proxyknife/proxyknife.texi:Free @sc{http}, @sc{socks5} or @sc{socks4} proxy that can be used as @dfn{MSN tunnel}.
./proxyknife/proxyknife.texi:A @sc{http} proxy(@samp{www.somehttpproxy.com:8080}) without authentication. A connection to free proxies can be done via this @sc{http} proxy. A file named @samp{proxylist} including the list of free proxies is in the current directory.
./proxyknife/proxyknife.texi:Free @sc{http} proxy with common GET method, @sc{socks5} or @sc{socks4} proxy with CONNECT command.
./proxyknife/proxyknife.texi:A @sc{socks5} proxy (@samp{socks.you.com}) with username/password authentication. The port of socks5 service is @var{1080}, the username is @samp{phc}, the password is @samp{'678'}. The connection to @uref{http://youth.bupt.edu.cn/proxy/} or free proxies can be done via this @sc{socks5} tunnel.
./proxyknife/proxyknife.texi:Common free @sc{http} proxy, free socks5 or socks4 proxy which support connect command.
./proxyknife/proxyknife.texi:If there is no @@ or other chars after the port in the line,proto is regarded as @sc{http} by default.
./proxyknife/proxyknife.texi:If you need a testproxy through which you can get the quickest response from the single @dfn{checksite} (@pxref{Startup Options}), please sort by @dfn{pcon} if possible. If include the @sc{service} response but not @sc{connect} response only, use @dfn{get} or @dfn{pget} instead. Certainly, you can guess the distribution of route from @dfn{testproxy} to @dfn{checksite} by comparing @dfn{pcon - estab, etc.}
./hurd/hurd.texi:@scindex halt
./hurd/hurd.texi:@scindex reboot
./hurd/hurd.texi:@scindex libthreads
./hurd/hurd.texi:@scindex cthreads.h
./hurd/hurd.texi:@scindex libports
./hurd/hurd.texi:@scindex ports.h
./hurd/hurd.texi:@scindex libihash
./hurd/hurd.texi:@scindex ihash.h
./hurd/hurd.texi:@scindex libshouldbeinlibc
./hurd/hurd.texi:@scindex libhurdbugaddr
./hurd/hurd.texi:@scindex libiohelp
./hurd/hurd.texi:@scindex iohelp.h
./hurd/hurd.texi:@scindex libpager
./hurd/hurd.texi:@scindex pager.h
./hurd/hurd.texi:@scindex io.defs
./hurd/hurd.texi:@scindex libtrivfs
./hurd/hurd.texi:@scindex trivfs.h
./hurd/hurd.texi:@scindex libfshelp
./hurd/hurd.texi:@scindex fshelp.h
./hurd/hurd.texi:@scindex fs.defs
./hurd/hurd.texi:@scindex fsys.defs
./hurd/hurd.texi:@scindex libstore
./hurd/hurd.texi:@scindex store.h
./hurd/hurd.texi:@scindex ufs
./hurd/hurd.texi:@scindex libdiskfs
./hurd/hurd.texi:@scindex diskfs.h
./hurd/hurd.texi:@scindex libstorefs
./hurd/hurd.texi:@scindex libftpconn
./hurd/hurd.texi:@scindex ftpconn.h
./hurd/hurd.texi:@scindex socket.defs
./hurd/hurd.texi:@scindex auth.defs
./gnun/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./misc/emacs-mime.texi:* Charset Translation:: How charsets are mapped from @sc{mule} to @acronym{MIME}.
./misc/emacs-mime.texi:If you are running a non-@sc{mule} Emacs, this process is simple: If the
./misc/emacs-mime.texi:Things are slightly more complicated when running Emacs with @sc{mule}
./misc/emacs-mime.texi:support. In this case, a list of the @sc{mule} charsets used in the
./misc/emacs-mime.texi:part is obtained, and the @sc{mule} charsets are translated to
./misc/emacs-mime.texi:When running Emacs with @sc{mule} support, the preferences for which
./misc/org.texi:Richard @@@@texinfo:@@sc@{@@@@Stallman@@@@texinfo:@}@@@@ commence' GNU.
./misc/cl.texi:form is a regular Lisp variable. But the @sc{car}s and @sc{cdr}s of lists,
./misc/cl.texi:It searches for an element of the list whose @sc{car} equals
./misc/cl.texi:then on the @sc{cdr}s of those lists, and so on, until the
./misc/cl.texi:@sc{car}s of the advancing pointers.
./misc/cl.texi:rearranging the @sc{cdr} pointers in suitable fashion.
./misc/cl.texi:list (where the @sc{cdr}-chain forms a loop rather than terminating
./misc/cl.texi:argument becomes the @sc{cdr} of the last cell constructed.
./misc/cl.texi:@var{y} are both cons cells, their @sc{car}s and @sc{cdr}s are
./misc/cl.texi:on, and compares against @var{old}, both @sc{car}s and @sc{cdr}s
./misc/cl.texi:function, if any), is compared with the @sc{car}s of
./misc/cl.texi:@sc{cdr}.
./misc/cl.texi:If a match is found, it returns the cons cell whose @sc{car} was
./misc/cl.texi:any of its @sc{cdr}s.
./misc/cl.texi:element whose @sc{car} matches (in the sense of @code{:test},
./misc/cl.texi:This function searches for an element whose @sc{cdr} matches
./misc/widget.texi:A list whose @sc{car} is the widget representing the currently chosen
./misc/widget.texi:List whose @sc{car} is the type of the list elements.
./misc/widget.texi:The value of a @code{cons} widget must be a cons-cell whose @sc{car}
./misc/widget.texi:and @sc{cdr} have two specified types. It uses this syntax:
./misc/widget.texi:and @kbd{C-o} (suggested by @sc{rms}).
./misc/widget.texi:whether you want to add or delete an item (@sc{rms} wanted to git rid of
./misc/sieve.texi:for talking to a server with the @sc{managesieve} protocol.
./misc/ede.texi:@scindex ede-sourcecode
./misc/message.texi:Each list element should be a cons, where the @sc{car} should be the
./misc/message.texi:name of a header (e.g., @code{CC}) and the @sc{cdr} should be the header
./misc/message.texi:In addition, you can enter conses into this list. The @sc{car} of this cons
./misc/message.texi:the @sc{cdr} can either be a string to be entered verbatim as the value of
./misc/message.texi:If the list contains a cons where the @sc{car} of the cons is
./misc/message.texi:@code{optional}, the @sc{cdr} of this cons will only be inserted if it is
./misc/message.texi:is @code{iso-8859-1} on non-@sc{mule} Emacsen; otherwise @code{nil},
./misc/message.texi:which means ask the user. (This variable is used only on non-@sc{mule}
./misc/message.texi:Emacs MIME Manual}, for details on the @sc{mule}-to-@acronym{MIME}
./misc/message.texi:@sc{car} is a function and the @sc{cdr} is the list of arguments, or
./misc/autotype.texi:@code{auto-insert-alist}. The @sc{car}s of this list are each either
./misc/autotype.texi:the same mode in Emacs can be distinguished. The @sc{car}s may also
./misc/autotype.texi: When a matching element is found, the @sc{cdr} says what to do. It may
./misc/trampver.texi:@set tramp @sc{Tramp}
./misc/viper.texi:dm@@scs.cs.nyu.edu (David Mazieres),
./misc/sasl.texi:@sc{sasl} is short for @dfn{Simple Authentication and Security Layer}.
./misc/sasl.texi:The toplevel interface of this library is inspired by Java @sc{sasl}
./misc/sasl.texi:A mechanism (@code{sasl-mechanism} object) is a schema of the @sc{sasl}
./misc/reftex.texi:@c dominik@@science.uva.nl
./misc/dbus.texi:A D-Bus compound type is always represented as a list. The @sc{car}
./misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./misc/gnus.texi:Things got a bit more complicated with @sc{gnus}. In addition to
./misc/gnus.texi:the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
./misc/gnus.texi:@sc{gnus} and other newsreaders.
./misc/gnus.texi:@sc{gnus 4.1}, where you had explicit keystrokes for everything under
./misc/gnus.texi:correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
./misc/gnus.texi:even with @sc{xover} by registering the @code{Xref} lines of all
./misc/gnus.texi:@cindex @sc{mode reader}
./misc/gnus.texi:not easy. People who prefer proper mail readers should try @sc{vm}
./misc/gnus.texi:where the @sc{car} of a cell contains the key, and the @sc{cdr}
./misc/gnus.texi:Two summary functions for editing a @sc{gnus} kill file:
./misc/gnus.texi:@sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
./misc/gnus.texi:pronounced ``news'' as @sc{Umeda} intended, which makes it a more
./misc/gnus.texi:``@sc{gnus}''. New vs. old.
./misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./misc/gnus.texi:reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
./misc/gnus.texi:Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
./misc/gnus.texi:All code that relies on knowledge of @sc{gnus} internals will probably
./misc/gnus.texi:fact, you should probably remove all old @sc{gnus} packages (and other
./misc/gnus.texi:does what you have written code to make @sc{gnus} do. (Snicker.)
./misc/gnus.texi:Gnus understands all @sc{gnus} startup files.
./misc/gnus.texi:@sc{gnus} internals should suffer no problems. If problems occur,
./misc/gnus.texi:Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
./misc/gnus.texi:Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
./misc/gnus.texi:of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
./misc/gnus.texi:controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
./misc/gnus.texi:normal @sc{head} format.
./misc/gnus.texi:been running @sc{gnus}, you need to exit Emacs and start it up again before
./misc/gnus.texi:@sc{gnus} introduced a concept that I found so useful that I've started
./misc/url.texi:@cindex @sc{socks}
./misc/url.texi:Use if the firewall has a @sc{socks} gateway running on it. The
./misc/url.texi:@sc{socks} v5 protocol is defined in RFC 1928.
./misc/url.texi:the @sc{socks} server.
./misc/url.texi:@sc{socks} server. By default this is your login name.
./misc/url.texi:@sc{socks} server; it is 5 by default.
./misc/url.texi:@c @sc{ip} addresses which specify a range of @sc{ip} addresses, an @sc{ip}
./misc/url.texi:@c address and a netmask, a domain name or a unique hostname or @sc{ip}
./misc/mh-e.texi:MH has the ability to display @dfn{@sc{mime}} (Multipurpose Internet
./misc/mh-e.texi:the MH book.} from the shell to read @sc{mime} messages@footnote{You
./misc/mh-e.texi:be on. Otherwise, you'll see the @sc{mime} body parts rather than text
./misc/mh-e.texi:text (including @sc{html}) and images.
./misc/mh-e.texi:in the MH book.} is compiled with the @sc{berk} option (which many
./misc/mh-e.texi:Compose @sc{mime} message from MH-style directives
./misc/mh-e.texi:Compose @sc{mime} message from MML tags (@code{mh-mml-to-mime}).
./misc/mh-e.texi:Type of @sc{mime} message tags in messages (default: @samp{MML} if
./misc/mh-e.texi:@sc{mime} (Multipurpose Internet Mail Extensions)
./misc/mh-e.texi:protocol@footnote{@sc{mime} is defined in
./misc/mh-e.texi:@sc{mime} protocol allows you to incorporate images, sound, video,
./misc/mh-e.texi:In addition to MH-style directives, MH-E also supports MML (@sc{mime}
./misc/mh-e.texi:The MH-E @sc{mime} commands require a @dfn{media type} for each body
./misc/mh-e.texi:You can also create your own @sc{mime} body parts. In the following
./misc/mh-e.texi:Mail may be forwarded with @sc{mime} using the command @kbd{C-c C-m
./misc/mh-e.texi:When you are finished editing a @sc{mime} message, it might look like this:
./misc/mh-e.texi:@i{MH-E @sc{mime} draft}
./misc/mh-e.texi:However, you may take a sneak preview of the @sc{mime} encoding if you
./misc/mh-e.texi:The following screen shows the @sc{mime} encoding specified by the
./misc/mh-e.texi:@i{MH-E @sc{mime} draft ready to send}
./misc/mh-e.texi:collection and support for composing @sc{mime} messages. (Reading
./misc/mh-e.texi:@sc{mime} messages remains to be done, alas.) While writing this book,
./misc/ChangeLog.1: * widget.texi, woman.texi: Replace @sc{ascii} and ASCII with
./liquidwar6/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./anubis/anubis.texi:@subsection Support for @sc{rot-13}
./anubis/anubis.texi:The @sc{rot-13} transformation is a simple form of encryption where the
./anubis/anubis.texi:GNU Anubis supports @sc{rot}-13 via a loadable Guile function. To enable
./anubis/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./auctex/auctex.texi:Insert @sc{small caps} @samp{\textsc@{@point{}@}} text.
./auctex/auctex.texi:Insert @sc{swash} @samp{\textsw@{@point{}@}} text.
./auctex/quickstart.texi:Insert @sc{small caps} @samp{\textsc@{@point{}@}} text.
./auctex/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./auctex/history.texi:@samp{}, Uffe Kjaerulff
./auctex/history.texi:@samp{}.@refill
./auctex/macros.texi:@sc{\text\}
./auctex/preview-readme.texi:@cindex @sc{git} access
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:number. The argument used by @samp{%c} must be an @sc{ascii} code
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:number; it will be printed as the character with that @sc{ascii} code.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:The @sc{car} of a list is, quite simply, the first item in the list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:Thus the @sc{car} of the list @code{(rose violet daisy buttercup)} is
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:The @sc{cdr} of a list is the rest of the list, that is, the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:first item. Thus, while the @sc{car} of the list @code{'(rose violet
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:list. However, the @sc{cdr} of the list is a list itself, @code{(fir
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:In this example, the first element or @sc{car} of the list is the list of
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:What it does is take the @sc{cdr} of a list repeatedly.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:If you take the @sc{cdr} of the list @code{(pine fir
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@code{(oak maple)}. (Of course, repeated @sc{cdr}ing on the original
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:list will just give you the original @sc{cdr} since the function does
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:not change the list. You need to evaluate the @sc{cdr} of the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cdr} and so on.) If you continue this, eventually you will be
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:For review, here is a series of repeated @sc{cdr}s, the text following
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:You can also do several @sc{cdr}s without printing the values in
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:The @code{nthcdr} function takes the @sc{cdr} of a list repeatedly.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:The @code{nth} function takes the @sc{car} of the result returned by
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:say, the first element of a list, its @sc{car} is the zeroth element.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:functions set the @sc{car} or the @sc{cdr} of a list to a new value.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cdr} of the first list will be set;
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@code{(horse cat dog)}. The @sc{cdr} of the list is changed from
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:with the text already in the first element (the @sc{car}) of the kill
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:the @sc{car} of the kill ring. Whether it prepends or appends the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:It sets the @sc{cdr} of a list, just as @code{setcar} sets the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{car} of a list. In this case, however, @code{setcdr} will not be
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:setting the @sc{cdr} of the whole kill ring; the @code{nthcdr}
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:function is used to cause it to set the @sc{cdr} of the next to last
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:element of the kill ring---this means that since the @sc{cdr} of the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:The @code{nthcdr} function works by repeatedly taking the @sc{cdr} of a
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:list---it takes the @sc{cdr} of the @sc{cdr} of the @sc{cdr}
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:elements long, we could set the @sc{cdr} of the next to last element
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:birch)}, then set the @sc{cdr} of its second @sc{cdr} to @code{nil}
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:that is what the @sc{cdr} is set to.)
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cdr} a number of times that is one less than the maximum permitted
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:size of the kill ring and @code{setcdr} sets the @sc{cdr} of that
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:Return the result of taking @sc{cdr} @var{n} times on a list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:If a symbol is set to the @sc{cdr} of a list, the list itself is not
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:the jargon, @sc{car} and @sc{cdr} are ``non-destructive''.) Thus,
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:Thus, in Lisp, to get the @sc{cdr} of a list, you just get the address
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:of the next cons cell in the series; to get the @sc{car} of a list,
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@code{more-flowers}. Set the @sc{car} of @code{flowers} to a fish.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:of the kill ring of which the first element (the @sc{car}) will be
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:expression set the value of the list to be the @sc{cdr} of the list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:can be set to be the @sc{cdr} of the original list with the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@code{dolist} works like a @code{while} loop that @sc{cdr}s down a
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:loops---takes the @sc{cdr} of the list---and binds the @sc{car} of
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cdr}s down the list on its own---and it automatically binds
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:the @sc{car} of each shorter version of the list to the first of its
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:In the example, the @sc{car} of each shorter version of the list is
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:The @code{dolist} expression binds the @sc{car} of each shorter
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:first element of the list, the @sc{car} of the list. Then the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cdr} of the list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:list). Then the function calls itself with the @sc{cdr} of the list
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:it is invoked with, which (the second time around) is the @sc{cdr} of
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:the @sc{cdr} of the original list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:evaluates the first element (the @sc{car} or true-or-false-test) of
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list)
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi: @sc{cdr}) of the list,
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi: act on the beginning of the list (the @sc{car} of the list),
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi: and make a recursive call on the rest (the @sc{cdr}) of the list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list),
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:Else, if the beginning of the list (the @sc{car} of the list) passes
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:Otherwise, if the beginning of the list (the @sc{car} of the list) fails
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi: and, recursively call the function on the rest (the @sc{cdr}) of the list.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:technique is to set the value of the list to the value of the @sc{cdr}
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cdr} of itself, so eventually the list will be empty; and the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:should not be too hard to write a function that @sc{cdr}s down the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:(cdr numbers-list))} expression, the @sc{car} of each instance of the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:non-@sc{ascii} characters are written within square brackets, without
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:hexadecimal three, and @sc{ascii} Control-C (the third letter of the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:set to be equal to some @sc{cdr} of the kill ring, using the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:works by repeatedly taking the @sc{cdr} of a list---it takes the
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cdr} of the @sc{cdr} of the @sc{cdr} @dots{}
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:the @code{mod} function to determine which @sc{cdr} to select.
./eintr/emacs-lispintro-27.1/emacs-lisp-intro.texi:@sc{cons} rather than a number or nothing, it puts point at beginning
./emacs-manual/mule.texi:The special character @code{RIGHT-TO-LEFT MARK}, or @sc{rlm}, forces
./emacs-manual/mule.texi:@code{LEFT-TO-RIGHT MARK}, or @sc{lrm} forces the left-to-right
./emacs-manual/mule.texi:In a GUI session, the @sc{lrm} and @sc{rlm} characters display as very
./emacs-manual/msdog.texi:come with such a program, although several ports of @sc{gnu} @code{ls}
./emacs-manual/msdog.texi:Emulate @sc{gnu} systems; this is the default. This sets
./emacs-manual/msdog.texi:@sc{gnu} defaults.
./emacs-manual/texinfo.tex-SAVE:% Explicit font changes: @r, @sc, undocumented @ii.
./g-wrap/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./texinfo/texinfo-tex-test.texi:@sansserif{`sans serif'} @sc{`small caps'} {@ensuremath@clubsuit}
./texinfo/refcard/txirefcard.tex:\txicmd{@sc}{\ttbraced{text}}{Set \var{text} in a small caps font in printed output, and uppercase in Info. No other font command has any effect in Info.}
./texinfo/texinfo.texi:acronym. Use @code{@@sc} instead (@pxref{Smallcaps}).
./texinfo/texinfo.texi:@subsection @code{@@sc}@{@var{text}@}: The Small Caps Font
./texinfo/texinfo.texi:Use the @samp{@@sc} command to set text in @sc{a small caps font}
./texinfo/texinfo.texi:Richard @@sc@{Stallman@} a commenc@'{e} le projet GNU.
./texinfo/texinfo.texi:Richard @sc{Stallman} a commenc@'{e} le projet GNU.
./texinfo/texinfo.texi:As shown here, we recommend reserving @code{@@sc} for special cases
./texinfo/texinfo.texi:@code{@@sc} command in full-size capitals; only lowercase letters are
./texinfo/texinfo.texi:@code{@@sc} is printed in all uppercase. In HTML, the argument is
./texinfo/texinfo.texi:@sc{car} and the @sc{cdr}. Here is how you would write the first line
./texinfo/texinfo.texi:@@samp @@sansserif @@sc @@slanted @@strong @@sub @@sup
./texinfo/texinfo.texi:@noindent For @code{@@sc}, any letters are capitalized.
./texinfo/texinfo.texi:@item @@sc@{@var{text}@}
./texinfo/texinfo.texi:@code{@@sc}, @code{@@asis}) may contain raw formatter commands such as
./texinfo/texi2oldapi.texi:is in @code{@@sc}. The function should also take care of protecting
./texinfo/texi2oldapi.texi:@code{@@sc}. Special characters (@samp{&}, @samp{"}, @samp{<} and
./prime/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./plotutils/plotutils.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./teseq/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./teseq/teseq.texi:(@sc{bs} for @sc{backspace}), and its control-key representation
./teseq/teseq.texi:translated and written out. The exception is that when an @sc{escape}
./teseq/teseq.texi:@sc{del}). It is based on the information from Table 1 of
./teseq/teseq.texi:of characters beginning with @sc{esc}, with a
./teseq/teseq.texi:@item @mjcth{xX0} @tab @sc{spc} @tab 0 @tab @@ @tab P
./teseq/teseq.texi:@item @mjcth{xXF} @tab / @tab ? @tab O @tab _ @tab o @tab @sc{del}
./teseq/teseq.texi:@cindex @sc{csi}
./teseq/teseq.texi:(@sc{csi}). The @sc{csi} control
./teseq/teseq.texi:A control sequence starts with the two-character @sc{csi} escape
./teseq/teseq.texi:and final byte; both invoke the @sc{sgr} control function. But the
./teseq/teseq.texi:@fortyeight{} describes an alternate representation for @sc{csi}; the
./teseq/teseq.texi:@sc{csi} control will probably be rendered like:
./teseq/teseq.texi:instance, the @sc{insert line} function is described as follows:
./teseq/teseq.texi:@sc{line editing mode}, the actual behavior might be to shift the
./teseq/teseq.texi:for @sc{insert line} should really read ``shift the current line and
./teseq/teseq.texi:invocations of @sc{select editing extent}. A conscious decision has
./teseq/teseq.texi:values corresponding to the ASCII control characters @sc{nul},
./teseq/teseq.texi:@sc{cr}, or @sc{lf} (hexadecimal @samp{x00}, @samp{x0D},
./teseq/teseq.texi:ASCII functions (in no case will @sc{nul}s be present in the
./teseq/teseq.texi:invocation of @sc{select graphic rendition} to set underlined text,
./gettext/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./grub/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./grub/grub.texi:@item Detect all installed @sc{ram}
./grub/grub.texi:GRUB can generally find all the installed @sc{ram} on a PC-compatible
./grub/grub.texi:@sc{pc} slice number in the BSD terminology). The partition numbers are
./grub/grub.texi:This means the BSD @samp{a} partition on first @sc{pc} slice number
./grub/grub.texi:as @sc{gnu}), invoke the program @command{grub-install} (@pxref{Invoking
./parted/parted-pt_BR.texi:@sc{tm}.
./ratpoison/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./libmicrohttpd/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gnuchess/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gawkinet/gawkinet.texi:@headitem @sc{protocol} @tab @sc{local port} @tab @sc{host name}
./gawkinet/gawkinet.texi:@tab @sc{remote port} @tab @sc{Resulting connection-level behavior}
./gawkinet/gawkinet.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gawkinet/gawk.texi:@samp{.} does not match the @sc{nul}
./gawkinet/gawk.texi:Otherwise, @sc{nul} is just another character. Other versions of @command{awk}
./gawkinet/gawk.texi:may not be able to match the @sc{nul} character.
./gawkinet/gawk.texi:You might think that for text files, the @sc{nul} character, which
./gawkinet/gawk.texi:@command{gawk} in fact accepts this, and uses the @sc{nul}
./gawkinet/gawk.texi:GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
./gawkinet/gawk.texi:@sc{nul} character as the string terminator. In effect, this means that
./gawkinet/gawk.texi:It happens that recent versions of @command{mawk} can use the @sc{nul}
./gawkinet/gawk.texi:@command{mawk} does not allow embedded @sc{nul} characters in strings.
./gawkinet/gawk.texi:You might think that for text files, the @sc{nul} character, which
./gawkinet/gawk.texi:@command{gawk} in fact accepts this, and uses the @sc{nul}
./gawkinet/gawk.texi:GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
./gawkinet/gawk.texi:@sc{nul} character as the string terminator. In effect, this means that
./gawkinet/gawk.texi:It happens that recent versions of @command{mawk} can use the @sc{nul}
./gawkinet/gawk.texi:@command{mawk} does not allow embedded @sc{nul} characters in strings.
./gawkinet/gawk.texi:eight-bit ASCII characters, including ASCII @sc{nul} (character code zero).
./gawkinet/gawk.texi:String values maintain both pointer and length, because embedded @sc{nul}
./gawkinet/gawk.texi:@sc{nul}-terminated. Thus it is safe to pass such string values to
./gawkinet/gawk.texi:allows embedded @sc{nul} characters in string data, before using the data
./gawkinet/gawk.texi:require more work. Because @command{gawk} allows embedded @sc{nul} bytes
./gawkinet/gawk.texi:Message-Id: <9510311732.AA28472@scalpel.netlabs.com>
./gawkinet/gawk.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gnupod/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./muesli/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./3dldf/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./3dldf/old_doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./remotecontrol/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./grip/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./mpria/mpria.texi:either the one digit version number @sc{MAJOR},
./mpria/mpria.texi:the two digit dotted version number @sc{MAJOR.Minor}
./mpria/mpria.texi:or the three digit dotted version number @sc{MAJOR.Minor.micro}
./bash/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library
./bash/hsuser.texi:For information on using the @sc{gnu} History Library in other programs,
./bash/hsuser.texi:see the @sc{gnu} Readline Library Manual.
./bash/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library interactively,
./bash/hsuser.texi:information on using the @sc{gnu} History Library in your own programs,
./bash/bash.texi:for the @sc{gnu} operating system.
./bash/bash.texi:It is intended to be a conformant implementation of the @sc{ieee}
./bash/bash.texi:@sc{posix} Shell and Tools portion of the @sc{ieee} @sc{posix}
./bash/bash.texi:specification (@sc{ieee} Standard 1003.1).
./bash/bash.texi:While the @sc{gnu} operating system provides other shells, including
./bash/bash.texi:Like other @sc{gnu} software, Bash is quite portable. It currently runs
./bash/bash.texi:independently-supported ports exist for @sc{ms-dos}, @sc{os/2},
./bash/bash.texi:interface to the rich set of @sc{gnu} utilities. The programming
./bash/bash.texi:A shell allows execution of @sc{gnu} commands, both synchronously and
./bash/bash.texi:@sc{posix} 1003.1 standard.
./bash/bash.texi:group @sc{id}.
./bash/bash.texi:@sc{posix} standard.
./bash/bash.texi:The rules for evaluation and quoting are taken from the @sc{posix}
./bash/bash.texi:@sc{posix} mode (@pxref{Bash POSIX Mode}),
./bash/bash.texi:by the @sc{posix} 1003.1 @code{waitpid} function, or 128+@var{n} if
./bash/bash.texi:by @sc{posix}.
./bash/bash.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}),
./bash/bash.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}), @code{time}
./bash/bash.texi:@sc{and} and @sc{or} lists are sequences of one or more pipelines
./bash/bash.texi:respectively. @sc{and} and @sc{or} lists are executed with left
./bash/bash.texi:An @sc{and} list has the form
./bash/bash.texi:An @sc{or} list has the form
./bash/bash.texi:@sc{and} and @sc{or} lists is the exit status of the last command
./bash/bash.texi:a @sc{posix} extended regular expression and matched accordingly
./bash/bash.texi:(using the @sc{posix} @code{regcomp} and @code{regexec} interfaces
./bash/bash.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}),
./bash/bash.texi:When in @sc{posix} mode (@pxref{Bash POSIX Mode}), these builtins may appear
./bash/bash.texi:($$) Expands to the process @sc{id} of the shell. In a @code{()} subshell, it
./bash/bash.texi:expands to the process @sc{id} of the invoking shell, not the subshell.
./bash/bash.texi:($!) Expands to the process @sc{id} of the job most recently placed into the
./bash/bash.texi:above, when in @sc{posix} mode.
./bash/bash.texi:pipes (@sc{fifo}s) or the @file{/dev/fd} method of naming open files.
./bash/bash.texi:The @sc{nul} character may not occur in a pattern.
./bash/bash.texi:following classes defined in the @sc{posix} standard:
./bash/bash.texi:various process @sc{id}s, including those of background jobs
./bash/bash.texi:the @option{-e} option from the parent shell. When not in @sc{posix} mode,
./bash/bash.texi:Many of the builtins have been extended by @sc{posix} or Bash.
./bash/bash.texi:These commands are implemented as specified by the @sc{posix} standard.
./bash/bash.texi:When Bash is not in @sc{posix} mode, the current directory is searched
./bash/bash.texi:Some of these commands are specified in the @sc{posix} standard.
./bash/bash.texi:The @option{-s} option restricts @code{enable} to the @sc{posix} special
./bash/bash.texi:The maximum number of bytes in @sc{posix} message queues.
./bash/bash.texi:and, when in @sc{posix} Mode (@pxref{Bash POSIX Mode}),
./bash/bash.texi:In @sc{posix} mode, only shell variables are listed.
./bash/bash.texi:from the @sc{posix} standard to match the standard
./bash/bash.texi:If set, shell error messages are written in the standard @sc{gnu} error
./bash/bash.texi:This option is enabled when @sc{posix} mode is enabled.
./bash/bash.texi:For historical reasons, the @sc{posix} standard has classified
./bash/bash.texi:When Bash is executing in @sc{posix} mode, the special builtins
./bash/bash.texi:When Bash is not executing in @sc{posix} mode, these builtins behave no
./bash/bash.texi:The Bash @sc{posix} mode is described in @ref{Bash POSIX Mode}.
./bash/bash.texi:These are the @sc{posix} special builtins:
./bash/bash.texi:Bash will not allow this value to be decreased below a @sc{posix}-mandated
./bash/bash.texi:@sc{posix} Mode (@pxref{Bash POSIX Mode}).
./bash/bash.texi:is executing, in the standard @sc{gnu} @var{cpu-company-system} format.
./bash/bash.texi:enters @sc{posix} mode (@pxref{Bash POSIX Mode}) before reading the
./bash/bash.texi:If it is set while the shell is running, Bash enables @sc{posix} mode,
./bash/bash.texi:When the shell enters @sc{posix} mode, it sets this variable if it was
./bash/bash.texi:The process @sc{id} of the shell's parent process. This variable
./bash/bash.texi:in the @sc{gnu} @code{gettext} PO (portable object) file format.
./bash/bash.texi:Do not use the @sc{gnu} Readline library (@pxref{Command Line Editing})
./bash/bash.texi:from the @sc{posix} standard to match the standard. This
./bash/bash.texi:@sc{posix} mode.
./bash/bash.texi:possible, while conforming to the @sc{posix} standard as well.
./bash/bash.texi:When invoked as @code{sh}, Bash enters @sc{posix} mode after
./bash/bash.texi:@subsubheading Invoked in @sc{posix} mode
./bash/bash.texi:When Bash is started in @sc{posix} mode, as with the
./bash/bash.texi:@option{--posix} command line option, it follows the @sc{posix} standard
./bash/bash.texi:@subsubheading Invoked with unequal effective and real @sc{uid/gid}s
./bash/bash.texi:When running in @sc{posix} mode, a special builtin returning an error
./bash/bash.texi:@samp{=} should be used with the @code{test} command for @sc{posix} conformance.
./bash/bash.texi:closely to the @sc{posix} standard by changing the behavior to
./bash/bash.texi:match that specified by @sc{posix} in areas where the Bash default differs.
./bash/bash.texi:When invoked as @code{sh}, Bash enters @sc{posix} mode after reading the
./bash/bash.texi:The following list is what's changed when `@sc{posix} mode' is in effect:
./bash/bash.texi:The @sc{posix} @env{PS1} and @env{PS2} expansions of @samp{!} to
./bash/bash.texi:The @sc{posix} startup files are executed (@env{$ENV}) rather than
./bash/bash.texi:Function names may not be the same as one of the @sc{posix} special
./bash/bash.texi:@sc{posix} special builtins are found before shell functions
./bash/bash.texi:If a @sc{posix} special builtin returns an error status, a
./bash/bash.texi:the @sc{posix} standard, and include things like passing incorrect options,
./bash/bash.texi:Assignment statements preceding @sc{posix} special builtins
./bash/bash.texi:when not in @sc{posix} mode, assignment builtins lose their assignment
./bash/bash.texi:output in the format required by @sc{posix}.
./bash/bash.texi:Enabling @sc{posix} mode has the effect of setting the
./bash/bash.texi:Enabling @sc{posix} mode has the effect of setting the
./bash/bash.texi:There is other @sc{posix} behavior that Bash does not implement by
./bash/bash.texi:default even when in @sc{posix} mode.
./bash/bash.texi:Bash can be configured to be @sc{posix}-conformant by default, by specifying
./bash/bash.texi:recognized as a reserved word (this is @sc{posix} interpretation 267)
./bash/bash.texi:(this is @sc{posix} interpretation 221)
./bash/bash.texi:(this is part of @sc{posix} interpretation 221);
./bash/bash.texi:indicating that this job is job number 1 and that the process @sc{id}
./bash/bash.texi:process group @sc{id}. Members of this process group (processes whose
./bash/bash.texi:process group @sc{id} is equal to the current terminal process group
./bash/bash.texi:@sc{id}) receive keyboard-generated signals such as @code{SIGINT}.
./bash/bash.texi:processes are those whose process group @sc{id} differs from the
./bash/bash.texi:List process @sc{id}s in addition to the normal information.
./bash/bash.texi:List only the process @sc{id} of the job's process group leader.
./bash/bash.texi:corresponding process group @sc{id}, and executes @var{command},
./bash/bash.texi:named by job specification @var{jobspec} or process @sc{id} @var{pid}.
./bash/bash.texi:Wait until the child process specified by each process @sc{id} @var{pid}
./bash/bash.texi:supplied process @sc{id}s.
./bash/bash.texi:analogous to the @samp{%?} job @sc{id} (@pxref{Job Control Basics}).
./bash/bash.texi:analogous to the @samp{%} job @sc{id}.
./bash/bash.texi:@sc{gnu} operating systems, nearly every version of Unix, and several
./bash/bash.texi:@sc{ms-dos}, @sc{os/2}, and Windows platforms.
./bash/bash.texi:@code{malloc} that appears in @sc{gnu} libc, but an older version
./bash/bash.texi:originally derived from the 4.2 @sc{bsd} @code{malloc}. This @code{malloc}
./bash/bash.texi:Include support for matching @sc{posix} regular expressions using the
./bash/bash.texi:Make Bash @sc{posix}-conformant by default (@pxref{Bash POSIX Mode}).
./bash/bash.texi:Bash uses the @sc{posix} standard as the specification of
./bash/bash.texi:Bash is @sc{posix}-conformant, even where the @sc{posix} specification
./bash/bash.texi:Bash includes the @sc{posix} pattern removal @samp{%}, @samp{#}, @samp{%%}
./bash/bash.texi:The @sc{posix} @code{$()} form of command substitution
./bash/bash.texi:Bash implements the full set of @sc{posix} filename expansion operators,
./bash/bash.texi:is slightly different, as it implements the @sc{posix} algorithm,
./bash/bash.texi:and effective @sc{uid} and @sc{gid} if they are less than some
./bash/bash.texi:a script only if one of the @sc{posix} special builtins fails, and
./bash/bash.texi:only for certain failures, as enumerated in the @sc{posix} standard.
./bash/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./bash/rluser.texi:This chapter describes the basic features of the @sc{gnu}
./bash/rluser.texi:eighth bit set to an @sc{ascii} key sequence by stripping the eighth
./bash/rluser.texi:the key sequence in double quotes. Some @sc{gnu} Emacs style key
./bash/rluser.texi:The following @sc{gnu} Emacs style escape sequences are available when
./bash/rluser.texi:In addition to the @sc{gnu} Emacs style escape sequences, a second
./bash/rluser.texi:interprets it as the end of input and returns @sc{eof}.
./bash/rluser.texi:same character as the tty @sc{eof} character, as @kbd{C-d}
./bash/rluser.texi:the @sc{posix} standard.
./bash/bashref.texi:for the @sc{gnu} operating system.
./bash/bashref.texi:It is intended to be a conformant implementation of the @sc{ieee}
./bash/bashref.texi:@sc{posix} Shell and Tools portion of the @sc{ieee} @sc{posix}
./bash/bashref.texi:specification (@sc{ieee} Standard 1003.1).
./bash/bashref.texi:While the @sc{gnu} operating system provides other shells, including
./bash/bashref.texi:Like other @sc{gnu} software, Bash is quite portable. It currently runs
./bash/bashref.texi:independently-supported ports exist for @sc{ms-dos}, @sc{os/2},
./bash/bashref.texi:interface to the rich set of @sc{gnu} utilities. The programming
./bash/bashref.texi:A shell allows execution of @sc{gnu} commands, both synchronously and
./bash/bashref.texi:@sc{posix} 1003.1 standard.
./bash/bashref.texi:group @sc{id}.
./bash/bashref.texi:@sc{posix} standard.
./bash/bashref.texi:The rules for evaluation and quoting are taken from the @sc{posix}
./bash/bashref.texi:@sc{posix} mode (@pxref{Bash POSIX Mode}),
./bash/bashref.texi:by the @sc{posix} 1003.1 @code{waitpid} function, or 128+@var{n} if
./bash/bashref.texi:by @sc{posix}.
./bash/bashref.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}),
./bash/bashref.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}), @code{time}
./bash/bashref.texi:@sc{and} and @sc{or} lists are sequences of one or more pipelines
./bash/bashref.texi:respectively. @sc{and} and @sc{or} lists are executed with left
./bash/bashref.texi:An @sc{and} list has the form
./bash/bashref.texi:An @sc{or} list has the form
./bash/bashref.texi:@sc{and} and @sc{or} lists is the exit status of the last command
./bash/bashref.texi:a @sc{posix} extended regular expression and matched accordingly
./bash/bashref.texi:(using the @sc{posix} @code{regcomp} and @code{regexec} interfaces
./bash/bashref.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}),
./bash/bashref.texi:When in @sc{posix} mode (@pxref{Bash POSIX Mode}), these builtins may appear
./bash/bashref.texi:($$) Expands to the process @sc{id} of the shell. In a @code{()} subshell, it
./bash/bashref.texi:expands to the process @sc{id} of the invoking shell, not the subshell.
./bash/bashref.texi:($!) Expands to the process @sc{id} of the job most recently placed into the
./bash/bashref.texi:above, when in @sc{posix} mode.
./bash/bashref.texi:pipes (@sc{fifo}s) or the @file{/dev/fd} method of naming open files.
./bash/bashref.texi:The @sc{nul} character may not occur in a pattern.
./bash/bashref.texi:following classes defined in the @sc{posix} standard:
./bash/bashref.texi:various process @sc{id}s, including those of background jobs
./bash/bashref.texi:the @option{-e} option from the parent shell. When not in @sc{posix} mode,
./bash/bashref.texi:Many of the builtins have been extended by @sc{posix} or Bash.
./bash/bashref.texi:These commands are implemented as specified by the @sc{posix} standard.
./bash/bashref.texi:When Bash is not in @sc{posix} mode, the current directory is searched
./bash/bashref.texi:Some of these commands are specified in the @sc{posix} standard.
./bash/bashref.texi:The @option{-s} option restricts @code{enable} to the @sc{posix} special
./bash/bashref.texi:The maximum number of bytes in @sc{posix} message queues.
./bash/bashref.texi:and, when in @sc{posix} Mode (@pxref{Bash POSIX Mode}),
./bash/bashref.texi:In @sc{posix} mode, only shell variables are listed.
./bash/bashref.texi:from the @sc{posix} standard to match the standard
./bash/bashref.texi:If set, shell error messages are written in the standard @sc{gnu} error
./bash/bashref.texi:This option is enabled when @sc{posix} mode is enabled.
./bash/bashref.texi:For historical reasons, the @sc{posix} standard has classified
./bash/bashref.texi:When Bash is executing in @sc{posix} mode, the special builtins
./bash/bashref.texi:When Bash is not executing in @sc{posix} mode, these builtins behave no
./bash/bashref.texi:The Bash @sc{posix} mode is described in @ref{Bash POSIX Mode}.
./bash/bashref.texi:These are the @sc{posix} special builtins:
./bash/bashref.texi:Bash will not allow this value to be decreased below a @sc{posix}-mandated
./bash/bashref.texi:@sc{posix} Mode (@pxref{Bash POSIX Mode}).
./bash/bashref.texi:is executing, in the standard @sc{gnu} @var{cpu-company-system} format.
./bash/bashref.texi:enters @sc{posix} mode (@pxref{Bash POSIX Mode}) before reading the
./bash/bashref.texi:If it is set while the shell is running, Bash enables @sc{posix} mode,
./bash/bashref.texi:When the shell enters @sc{posix} mode, it sets this variable if it was
./bash/bashref.texi:The process @sc{id} of the shell's parent process. This variable
./bash/bashref.texi:in the @sc{gnu} @code{gettext} PO (portable object) file format.
./bash/bashref.texi:Do not use the @sc{gnu} Readline library (@pxref{Command Line Editing})
./bash/bashref.texi:from the @sc{posix} standard to match the standard. This
./bash/bashref.texi:@sc{posix} mode.
./bash/bashref.texi:possible, while conforming to the @sc{posix} standard as well.
./bash/bashref.texi:When invoked as @code{sh}, Bash enters @sc{posix} mode after
./bash/bashref.texi:@subsubheading Invoked in @sc{posix} mode
./bash/bashref.texi:When Bash is started in @sc{posix} mode, as with the
./bash/bashref.texi:@option{--posix} command line option, it follows the @sc{posix} standard
./bash/bashref.texi:@subsubheading Invoked with unequal effective and real @sc{uid/gid}s
./bash/bashref.texi:When running in @sc{posix} mode, a special builtin returning an error
./bash/bashref.texi:@samp{=} should be used with the @code{test} command for @sc{posix} conformance.
./bash/bashref.texi:closely to the @sc{posix} standard by changing the behavior to
./bash/bashref.texi:match that specified by @sc{posix} in areas where the Bash default differs.
./bash/bashref.texi:When invoked as @code{sh}, Bash enters @sc{posix} mode after reading the
./bash/bashref.texi:The following list is what's changed when `@sc{posix} mode' is in effect:
./bash/bashref.texi:The @sc{posix} @env{PS1} and @env{PS2} expansions of @samp{!} to
./bash/bashref.texi:The @sc{posix} startup files are executed (@env{$ENV}) rather than
./bash/bashref.texi:Function names may not be the same as one of the @sc{posix} special
./bash/bashref.texi:@sc{posix} special builtins are found before shell functions
./bash/bashref.texi:If a @sc{posix} special builtin returns an error status, a
./bash/bashref.texi:the @sc{posix} standard, and include things like passing incorrect options,
./bash/bashref.texi:Assignment statements preceding @sc{posix} special builtins
./bash/bashref.texi:when not in @sc{posix} mode, assignment builtins lose their assignment
./bash/bashref.texi:output in the format required by @sc{posix}.
./bash/bashref.texi:Enabling @sc{posix} mode has the effect of setting the
./bash/bashref.texi:Enabling @sc{posix} mode has the effect of setting the
./bash/bashref.texi:There is other @sc{posix} behavior that Bash does not implement by
./bash/bashref.texi:default even when in @sc{posix} mode.
./bash/bashref.texi:Bash can be configured to be @sc{posix}-conformant by default, by specifying
./bash/bashref.texi:recognized as a reserved word (this is @sc{posix} interpretation 267)
./bash/bashref.texi:(this is @sc{posix} interpretation 221)
./bash/bashref.texi:(this is part of @sc{posix} interpretation 221);
./bash/bashref.texi:indicating that this job is job number 1 and that the process @sc{id}
./bash/bashref.texi:process group @sc{id}. Members of this process group (processes whose
./bash/bashref.texi:process group @sc{id} is equal to the current terminal process group
./bash/bashref.texi:@sc{id}) receive keyboard-generated signals such as @code{SIGINT}.
./bash/bashref.texi:processes are those whose process group @sc{id} differs from the
./bash/bashref.texi:List process @sc{id}s in addition to the normal information.
./bash/bashref.texi:List only the process @sc{id} of the job's process group leader.
./bash/bashref.texi:corresponding process group @sc{id}, and executes @var{command},
./bash/bashref.texi:named by job specification @var{jobspec} or process @sc{id} @var{pid}.
./bash/bashref.texi:Wait until the child process specified by each process @sc{id} @var{pid}
./bash/bashref.texi:supplied process @sc{id}s.
./bash/bashref.texi:analogous to the @samp{%?} job @sc{id} (@pxref{Job Control Basics}).
./bash/bashref.texi:analogous to the @samp{%} job @sc{id}.
./bash/bashref.texi:@sc{gnu} operating systems, nearly every version of Unix, and several
./bash/bashref.texi:@sc{ms-dos}, @sc{os/2}, and Windows platforms.
./bash/bashref.texi:@code{malloc} that appears in @sc{gnu} libc, but an older version
./bash/bashref.texi:originally derived from the 4.2 @sc{bsd} @code{malloc}. This @code{malloc}
./bash/bashref.texi:Include support for matching @sc{posix} regular expressions using the
./bash/bashref.texi:Make Bash @sc{posix}-conformant by default (@pxref{Bash POSIX Mode}).
./bash/bashref.texi:Bash uses the @sc{posix} standard as the specification of
./bash/bashref.texi:Bash is @sc{posix}-conformant, even where the @sc{posix} specification
./bash/bashref.texi:Bash includes the @sc{posix} pattern removal @samp{%}, @samp{#}, @samp{%%}
./bash/bashref.texi:The @sc{posix} @code{$()} form of command substitution
./bash/bashref.texi:Bash implements the full set of @sc{posix} filename expansion operators,
./bash/bashref.texi:is slightly different, as it implements the @sc{posix} algorithm,
./bash/bashref.texi:and effective @sc{uid} and @sc{gid} if they are less than some
./bash/bashref.texi:a script only if one of the @sc{posix} special builtins fails, and
./bash/bashref.texi:only for certain failures, as enumerated in the @sc{posix} standard.
./gama/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./web-trans/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./radius/radius.texi:@cindex @sc{nas}
./radius/radius.texi:@item Session @sc{id}
./radius/radlast.texi:@item Session @sc{id}
./radius/radlast.texi:@item Caller @sc{id}
./radius/radlast.texi:If multiple arguments are given, the logical @sc{or} operation between them
./radius/radlast.texi:always combined with the rest of command line by logical @sc{and}.
./radius/radwho.texi:Unique session @sc{id} assigned by the terminal server.
./radius/radwho.texi:Caller station @sc{id} ad reported by the @NAS{}.
./radius/radwho.texi:Display the calling station @sc{id} in the second column. Equivalent to
./radius/radwho.texi:Display session @sc{id} instead of @sc{gecos} in the second column.
./radius/radwho.texi:The @sc{gecos} field from the local @file{/etc/passwd} corresponding
./radius/radwho.texi:are: login name, @sc{gecos} name, connection protocol, port number, time when
./radius/radtest.texi:@sc{ip}v4 addresses. These can be input either as decimal numbers or
./radius/client.texi:Set the session @sc{id} (@attr{Acct-Session-Id} attribute).
./radius/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./radius/attributes.texi:physical connection on the @NAS{}, not in the sense of a @sc{tcp} or
./radius/attributes.texi:@sc{udp} port number.
./radius/attributes.texi:attribute value. For example, the @sc{max a}scend terminal server constructs
./radius/attributes.texi:A rewrite function for @sc{max a}scend servers is provided in the
./radius/attributes.texi:value is @sc{xor}ed with the first 16 octet segment of the password and
./radius/attributes.texi:is @sc{xor}ed with the second 16 octet segment of the password and
./radius/attributes.texi:If necessary, this operation is repeated, with each @sc{xor} result
./radius/attributes.texi:to @sc{xor} the next segment of the password, up to no more than 128
./radius/attributes.texi:This attribute is a unique accounting @sc{id} to make it easy to match
./radius/attributes.texi:The MD5-encrypted user's password is queried from the @sc{sql} database
./radius/attributes.texi:his calling station @sc{id} followed by a newline will be sent to the
./radius/attributes.texi:of the user's entry. The values of these attributes @sc{or}ed together
./radius/attributes.texi:form a mask, which is applied via an @sc{xor} operation to the current log
./radius/attributes.texi:Now, user @samp{johns}, having a valid account in the @sc{sql} database,
./radius/config.texi:@sc{radius}
./radius/config.texi:@sc{nas}
./radius/config.texi:@sc{a/v} pair
./radius/config.texi:@sc{lhs}
./radius/config.texi:@sc{rhs}
./radius/config.texi:@sc{ip} address
./radius/config.texi:@sc{unix}
./radius/extensions.texi:Cisco @sc{as5300} terminal server used as a voice-over IP router packs
./radius/extensions.texi:it obtains the form prescribed by @sc{rfc}s and its further processing
./radius/extensions.texi:For example, in the case of the @sc{as5300} router, a corresponding Rewrite
./radius/extensions.texi:@subheading 1. Port rewriting for @sc{max a}scend terminal servers
./radius/extensions.texi:Some @sc{max a}scend terminal servers pack additional information
./radius/extensions.texi:@subheading 2. Session @sc{id} parsing for Cisco AS 5300 series
./radius/extensions.texi:Cisco @sc{voip ios} encodes a lot of other information into its
./radius/extensions.texi:@samp{/} character is the actual session @sc{id}.
./radius/extensions.texi:(vendor @sc{pec} 9), which is a string in the form @samp{ISDN 9:D:999}
./radius/extensions.texi:@subheading 3. User-name rewriting for @sc{nt} machines
./radius/extensions.texi:Users coming from Windows @sc{nt} machines often authenticate themselves as
./radius/extensions.texi:Port @sc{id} of the session.
./radius/extensions.texi:Session @sc{id}.
./radius/extensions.texi:@c{tty} number (port @sc{id}); and the seventh field, the session @sc{id}.
./radius/extensions.texi:user name and port and session @sc{id}s:
./radius/extensions.texi:can be coerced to an integer if it contains a valid @sc{ascii} representation
./radius/extensions.texi:to a string, the result of such coercion being the @sc{ascii} string
./radius/extensions.texi:an @sc{ascii} character itself or of its value, enclosed in a pair of
./radius/extensions.texi:@tab If the string value of the variable is a valid @sc{ascii} representation
./radius/extensions.texi:@tab The @sc{ascii} representation (in decimal) of the integer number.
./radius/extensions.texi:Returns the source @sc{udp} port.
./radius/extensions.texi:The session @sc{id}
./radius/radzap.texi:joined by the logical @sc{and} operation.
./radius/configure.texi:Contains the configuration for the @sc{sql} system. This includes the
./radius/configure.texi:type of @sc{sql} interface used, the IP and port number of the server
./radius/configure.texi:and the definition of the @sc{sql} requests used by @command{radiusd}.
./radius/configure.texi:Add the process @sc{id} of the process generating the logging information.
./radius/configure.texi:Sets the number of which @sc{udp} port to listen on for the
./radius/configure.texi:as well, unless you supply an alternative @sc{mlc} method (currently
./radius/configure.texi:@sc{sql}, @xref{Multiple Login Checking}, for the detailed discussion
./radius/configure.texi:will use @sc{sql} database.
./radius/configure.texi:method specified by @sc{rfc 2865}. However some @NAS{}es, most notably
./radius/configure.texi:@sc{max a}scend series, implement a broken method of encoding long
./radius/configure.texi:This type suits for @sc{unix} boxes running finger service able to return information
./radius/configure.texi:The @file{raddb/sqlserver} file configures the connection to @sc{sql} server.
./radius/configure.texi:connection between @sc{sql} client and the server, @dfn{Authentication
./radius/configure.texi:@sc{sql} client and the server.
./radius/configure.texi:Specifies the @sc{sql} interface to use. Currently supported values
./radius/configure.texi:Specifies the hostname or @IP{} of the @sc{sql} server.
./radius/configure.texi:Sets the @sc{sql} communication port number. It can be omitted if your
./radius/configure.texi:Sets the @sc{sql} user login name.
./radius/configure.texi:Sets the @sc{sql} user password.
./radius/configure.texi:Set idle timeout in seconds for an open @sc{sql} connection.
./radius/configure.texi:These parameters configure the @sc{sql} authentication. The general
./radius/configure.texi:When set to @code{yes}, enables authentication via @sc{sql}. All @code{auth_}
./radius/configure.texi:Specifies the @sc{sql} query to be used to obtain user's password from the
./radius/configure.texi:information from the @sc{sql} database. All the queries refer to
./radius/configure.texi:Suppose your attribute information is stored in a @sc{sql} table of
./radius/configure.texi:these conditions, he is allowed to use @sc{ppp} service, and is
./radius/configure.texi:To perform the @sc{sql} accounting @command{radiusd} needs to know the
./radius/configure.texi:When set to @code{yes} enables @sc{sql} accounting. All @code{acct_}
./radius/configure.texi:types (@pxref{Accounting Requests}) has a @sc{sql} query associated with
./radius/configure.texi:Specifies the @sc{sql} query to be used when @dfn{Session Start Packet}
./radius/configure.texi:Specifies the @sc{sql} query to be used when @dfn{Session Stop Packet}
./radius/configure.texi:Specifies the @sc{sql} query to be executed upon arrival of a
./radius/configure.texi:Specifies the @sc{sql} query to be used upon arrival of an
./radius/configure.texi:Specifies the @sc{sql} query to be used when a @NAS{} sends
./radius/configure.texi:@item @sc{sql} query templates in @file{sqlserver}
./radius/operation.texi:@cindex @sc{nas}
./radius/operation.texi:original Access-Request with a new request @sc{id} and request
./radius/radping.texi:@sc{id} to indicate the user.
./radius/radscm.texi:@item @var{id-str} @tab Server @sc{id}
./radius/radscm.texi:server @sc{id} and IP.
./radius/radscm.texi:Returns the @sc{id} of the currently selected server.
./radius/radscm.texi:@item @var{id-str} @tab Server @sc{id}
./radius/radscm.texi:@item @var{id-str} @tab Server @sc{id}
./radius/radscm.texi:For each server from @code{rad-server-list}, print its @sc{id} and hostname
./radius/invoke.texi:Listen the @sc{udp} port PORTNO. The accounting port is computed as @var{PORTNO} + 1.
./mino/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./rush/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./inetutils/inetutils.texi:@settitle @sc{gnu} Inetutils
./inetutils/inetutils.texi:This manual documents version @value{VERSION} of the @sc{gnu} networking
./inetutils/inetutils.texi:@title @sc{gnu} @code{inetutils}
./inetutils/inetutils.texi:entire @sc{gnu} community will benefit.
./inetutils/inetutils.texi:described here. (In fact, every @sc{gnu} program accepts, or should
./sed/sed.texi:Note: the @sc{posix} standard does not specify what should happen
./sed/sed.texi:a @sc{nul} character. This is a @value{SSED} extension.
./sed/sed.texi:some implementations of @command{sed} (which are not @sc{posix}
./sed/sed.texi:executed contains a @sc{nul} character.
./sed/sed.texi:in the input stream. @sc{posix} mandates that such sequences
./sed/sed.texi:Produces or matches a @sc{bel} character, that is an ``alert'' (@sc{ascii} 7).
./sed/sed.texi:Produces or matches a form feed (@sc{ascii} 12).
./sed/sed.texi:Produces or matches a newline (@sc{ascii} 10).
./sed/sed.texi:Produces or matches a carriage return (@sc{ascii} 13).
./sed/sed.texi:Produces or matches a horizontal tab (@sc{ascii} 9).
./sed/sed.texi:Produces or matches a so called ``vertical tab'' (@sc{ascii} 11).
./sed/sed.texi:Produces or matches @kbd{@sc{Control}-@var{x}}, where @var{x} is
./sed/sed.texi:Produces or matches a character whose decimal @sc{ascii} value is @var{xxx}.
./sed/sed.texi:Produces or matches a character whose octal @sc{ascii} value is @var{xxx}.
./sed/sed.texi:Produces or matches a character whose hexadecimal @sc{ascii} value is @var{xx}.
./sed/sed.texi:(@samp{0x5e} is the hexadecimal @sc{ascii} value of the character @samp{^}):
./sed/sed.texi:@sc{ascii} values of @samp{[},@samp{]}, respectively):
./sed/sed.texi:Ubben wrote an implementation of the @command{dc} @sc{rpn} calculator!
./sed/sed.texi:The @sc{posix} standard specifies that conforming @command{sed}
./sed/sed.texi:@command{sed} uses the @sc{posix} basic regular expression syntax. According to
./sed/sed.texi:As in all GNU programs that use @sc{posix} basic regular
./sed/sed.texi:sequences. @sc{posix} mandates that such sequences
./bbdb/doclicense.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./pretest/pretest.texi:convert the image from @sc{RAW} format to @sc{qcow2} format.
./pretest/pretest.texi:run script (@file{pretest-run.sh}) use @sc{IDE} for disk emulation,
./pretest/pretest.texi:and @sc{rtl8139} for network emulation.
./fontopia/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gnats/gnats.texi:This manual is for @sc{gnu gnats}
./gnats/gnats.texi:the @sc{gnu} Bug Tracking System.
./gnats/gnats.texi:@subtitle Managing Messages With @sc{gnats}
./gnats/gnats.texi:@subtitle The @sc{gnu} Problem Report Management System
./gnats/gnats.texi:This manual documents @sc{gnats}, the @sc{gnu} Problem Report Management
./gnats/gnats.texi:System, version @value{VERSION}. @sc{gnats} is a bug-tracking tool
./gnats/gnats.texi:with the @sc{gnats} network daemon running at the support site or direct
./gnats/gnats.texi:at that Support Site. @sc{gnats} partially automates the tracking of
./gnats/gnats.texi:@sc{gnats} offers many of the same features offered by more generalized
./gnats/gnats.texi:@sc{gnats} database itself is an ordered repository for problem reports;
./gnats/gnats.texi:adopted by @sc{gnats}, see @ref{Paradigm,,The database paradigm}.
./gnats/gnats.texi:@sc{gnats} from within @sc{gnu} Emacs. @xref{GNATS user tools,,The
./gnats/gnats.texi:@sc{gnats} user tools}.
./gnats/gnats.texi:@chapter Introducing @sc{gnats}
./gnats/gnats.texi:electronic mail. @sc{gnats} addresses the problem of organizing this
./gnats/gnats.texi:@sc{gnats} was designed as a tool for software maintainers. It consists
./gnats/gnats.texi:fashion. Essentially, @sc{gnats} acts as an active archive for
./gnats/gnats.texi:@sc{gnats} makes this easy by automatically filing incoming problem
./gnats/gnats.texi:Reports accessible to queries and easily editable. @sc{gnats} is a
./gnats/gnats.texi:@sc{gnats} was designed for use at a Support Site that handles a high
./gnats/gnats.texi:(@pxref{Fields,,@sc{gnats} data fields}). The location of the database,
./gnats/gnats.texi:@xref{Management,,@sc{gnats} administration}.
./gnats/gnats.texi:(@pxref{Locations,,Where @sc{gnats} lives}). Editing access to the
./gnats/gnats.texi:Other interfaces to @sc{gnats} include Gnatsweb, a web-based tool which
./gnats/gnats.texi:distributed together with @sc{gnats}.
./gnats/gnats.texi:At the Support Site, a @sc{gnats} @dfn{administrator} is charged with the
./gnats/gnats.texi:duty of maintaining @sc{gnats}. These duties are discussed in detail in
./gnats/gnats.texi:@ref{Management,,@sc{gnats} Administration}, and generally include
./gnats/gnats.texi:configuring @sc{gnats} for the Support Site, editing PRs that @sc{gnats}
./gnats/gnats.texi:@sc{gnats} configuration}.
./gnats/gnats.texi:@cindex incoming PRs that @sc{gnats} cannot parse
./gnats/gnats.texi:@sc{gnats} does not have the ability to decipher random text.
./gnats/gnats.texi:problem reports which arrive in a format @sc{gnats} does not recognize
./gnats/gnats.texi:@sc{gnats} administrator (@pxref{Management,,@sc{gnats} Administration}).
./gnats/gnats.texi:feature has been switched on in the @sc{gnats} configuration).
./gnats/gnats.texi:@sc{gnats} forwards copies of the report to the party responsible for
./gnats/gnats.texi:@sc{gnats} may be configured so that each time the state of a PR
./gnats/gnats.texi:that @sc{gnats} works, but as of version 4, @sc{gnats} is extremely
./gnats/gnats.texi:@section Flowchart of @sc{gnats} activities
./gnats/gnats.texi:This informal flowchart shows the relationships of the @sc{gnats} tools
./gnats/gnats.texi:@chapter Installing @sc{gnats}
./gnats/gnats.texi:@appendix Where @sc{gnats} lives
./gnats/gnats.texi:@cindex where @sc{gnats} lives
./gnats/gnats.texi:@sc{gnats} uses. These values are adjustable when you build and install
./gnats/gnats.texi:@sc{gnats} (@pxref{Installation,,Installing @sc{gnats}}).
./gnats/gnats.texi:@item @sc{gnats} user tools
./gnats/gnats.texi:customized installations, but fairly ordinary @sc{gnats} installations
./gnats/gnats.texi:Each @sc{gnats} database located on a server has its own directory, as
./gnats/gnats.texi:files generated and maintained by @sc{gnats}, @file{index} and
./gnats/gnats.texi:@sc{gnats} installs tools, utilities, and files into the following
./gnats/gnats.texi:The @sc{gnats} daemon.
./gnats/gnats.texi:The @sc{gnu} @code{libiberty} library.
./gnats/gnats.texi:@xref{GNATS configuration,,Overview of @sc{gnats} configuration}.
./gnats/gnats.texi:@sc{gnats} user tools}. To change this directory you must change the
./gnats/gnats.texi:The @sc{gnats} manuals, in a form readable by @code{info} (the @sc{gnu}
./gnats/gnats.texi:@item @code{man} pages for all the @sc{gnats} tools and utilities.
./gnats/gnats.texi:@xref{GNATS user tools,,The @sc{gnats} user tools}.
./gnats/gnats.texi:(@emph{This file is created by @sc{gnats}.})
./gnats/gnats.texi:(@emph{This file is created by @sc{gnats}.})
./gnats/gnats.texi:intervention by @sc{gnats} administrators.
./gnats/gnats.texi:@xref{Management,,@sc{gnats} administration}.
./gnats/gnats.texi:@appendix The @sc{gnats} network server -- @code{gnatsd}
./gnats/gnats.texi:This section describes in details how the @sc{gnats} network daemon
./gnats/gnats.texi:of @sc{gnats} client software.
./gnats/gnats.texi:The @code{gnatsd} network daemon is used to service remote @sc{gnats}
./gnats/gnats.texi:All of the @sc{gnats} clients are capable of communicating via the @sc{gnats}
./gnats/gnats.texi:resolve the problem. Fortunately, most @sc{gnats} transactions are
./gnats/gnats.texi:Note that the set of @sc{gnats} commands and their responses is somewhat
./gnats/gnats.texi:inconsistent and is very much in flux. At present the @sc{gnats}
./gnats/gnats.texi:It is thus suggested that any clients that use the @sc{gnats} protocol
./gnats/gnats.texi:Locks the main @sc{gnats} database. No subsequent database locks will
./gnats/gnats.texi:provides a way for a site to secure its @sc{gnats} databases while still
./gnats/gnats.texi:@xref{Environment}, in almost the same way as the @sc{gnats} tools do.
./gnats/gnats.texi:@sc{gnats} supports granting various levels of access to the @sc{gnats}
./gnats/gnats.texi:@sc{gnats} access can be controlled at these levels:
./gnats/gnats.texi:above. This restricts any access to the @sc{gnats} daemon to levels up
./gnats/gnats.texi:The discussion below assumes that the pre-build configure of @sc{gnats}
./gnats/gnats.texi:that when @sc{gnats} authenticates hosts, it reads the entries in this
./gnats/gnats.texi:@sc{gnats} currently doesn't make use of the third field. Remember to
./gnats/gnats.texi:such a case they should be owned by the @sc{gnats} user with file
./gnats/gnats.texi:@samp{?} matches any one character. Note that when @sc{gnats}
./gnats/gnats.texi:supports MD5. Among others, this currently includes @sc{gnu} Linux and
./gnats/gnats.texi:Blowfish encoding. @sc{gnats} will happily accept any encryption that
./gnats/gnats.texi:distributed with @sc{gnats} 4. @xref{gnats-pwconv,,Converting old
./gnats/gnats.texi:lock the main @sc{gnats} database.
./gnats/gnats.texi:unlock the main @sc{gnats} database.
./gnats/gnats.texi:@sc{gnats} User Tools}.
./gnats/gnats.texi:to @sc{gnu} regular expression syntax. This matches all values of
./gnats/gnats.texi:Report in default @sc{gnats} installations.
./gnats/gnats.texi:file}) is the heart of any @sc{gnats} installation. It contains some
./gnats/gnats.texi:person is used instead of the @sc{gnats} user name.
./gnats/gnats.texi:@subsubheading Supporting @sc{gnats} ``release-based'' fields
./gnats/gnats.texi:When installing @sc{gnats} version 3.x, it was possible to choose
./gnats/gnats.texi:The default @file{dbconfig} shipped with @sc{gnats} version 4 or newer
./gnats/gnats.texi:A side note: Pre-release versions of @sc{gnats} 4 also had a field
./gnats/gnats.texi:@appendix @sc{gnats} support
./gnats/gnats.texi:@cindex @sc{gnats} support
./gnats/gnats.texi:The @sc{gnats} home page is located at
./gnats/gnats.texi:important references to the available information about @sc{gnats} and
./gnats/gnats.texi:There is also a special page dedicated to the @sc{gnats} development
./gnats/gnats.texi:There are several @sc{gnats} mailing lists. The most important ones
./gnats/gnats.texi:Announcements and other important information about @sc{gnats} and the
./gnats/gnats.texi:The bug reporting mailing list on the @sc{gnats} itself. Please note
./gnats/gnats.texi:that the preferred way to report @sc{gnats} bugs is to submit them via
./gnats/gnats.texi:General discussion about @sc{gnats}. Anything related to @sc{gnats}
./gnats/gnats.texi:The complete list of @sc{gnats} related mailing lists is available
./gnats/gnats.texi:When you report problems concerning @sc{gnats} itself, please do not
./gnats/gnats.texi:The @sc{gnats} version you are using.
./gnats/gnats.texi:a problem. A @dfn{record} in the @sc{gnats} database.
./gnats/gnats.texi:location where @sc{gnats} is installed and functional.
./gnats/gnats.texi:@item @sc{gnats}
./gnats/gnats.texi:The @sc{gnu} Problem Report Management System.
./gnats/getdate.texi:This section describes the textual date representations that @sc{gnu}
./gnats/getdate.texi:* Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
./gnats/getdate.texi:1972-09-24 # @sc{iso} 8601.
./gnats/getdate.texi:@cindex @sc{iso} 8601 date format
./gnats/getdate.texi:@cindex date format, @sc{iso} 8601
./gnats/getdate.texi:For numeric months, the @sc{iso} 8601 format
./gnats/getdate.texi:20:02-0500 # In @sc{est} (U.S. Eastern Standard Time).
./gnats/getdate.texi:Coordinated Universal Time (@sc{utc}), overriding any previous
./gnats/getdate.texi:ahead of @sc{utc} (e.g., India).
./gnats/getdate.texi:@acronym{POSIX} systems, the epoch is 1970-01-01 00:00:00 @sc{utc}, so
./gnats/getdate.texi:00:00:01 @sc{utc}, and so forth. @acronym{GNU} and most other
./gnats/getdate.texi:represents 1969-12-31 23:59:59 @sc{utc}.
./gnats/getdate.texi:2038-01-19 03:14:07 @sc{utc}. More modern systems use 64-bit counts
./gnats/getdate.texi:23:59:59 @sc{utc}, @samp{@@915148800} represents 1999-01-01 00:00:00
./gnats/getdate.texi:@sc{utc}, and there is no way to represent the intervening leap second
./gnats/getdate.texi:1998-12-31 23:59:60 @sc{utc}.
./gnats/getdate.texi:revisions for the @sc{gnu} system were made by David MacKenzie, Jim Meyering,
./gnats/fields.texi:The format of a PR is designed to reflect the nature of @sc{gnats} as a
./gnats/fields.texi:reference}. As of version 4 of @sc{gnats} all characteristics of
./gnats/fields.texi:present in a standard @sc{gnats} configuration. Mail headers are at the
./gnats/fields.texi:top, followed by @sc{gnats} fields, which begin with @samp{>} and end
./gnats/fields.texi:separate file on the @sc{gnats} server.
./gnats/fields.texi:directly to the @code{gnatsd} network daemon on the @sc{gnats} server.
./gnats/fields.texi:One of the configurable options for @sc{gnats} is whether or not to
./gnats/fields.texi:In a standard @sc{gnats} installation, certain fields will always be
./gnats/fields.texi:these fields, @sc{gnats} will add them, and if they have default
./gnats/fields.texi:in the @file{categories} file of the @sc{gnats} database.
./gnats/fields.texi:@sc{gnats} installation can be one of the following:
./gnats/fields.texi:@sc{gnats} adds the following fields when the PR arrives at the Support
./gnats/fields.texi:feature of @sc{gnats} is activated; @pxref{dbconfig file,,The
./gnats/fields.texi:in subsequent email messages. This is @sc{gnats}' way of tracking
./gnats/fields.texi:(@code{enumerated}) The current state of the PR. In default @sc{gnats}
./gnats/fields.texi:@sc{gnats} retrieves this information from the @file{categories} file
./gnats/fields.texi:(@code{date}) The time that this PR was received by @sc{gnats}. The
./gnats/fields.texi:date is provided automatically by @sc{gnats}.
./gnats/fields.texi:@sc{gnats} related to this PR, in the order received. @sc{gnats} needs
./gnats/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gnats/p-inst.texi:install @sc{gnats} on your system. You need @code{root} access in order
./gnats/p-inst.texi:to create a new account for @code{gnats} and to install the @sc{gnats}
./gnats/p-inst.texi:If you are updating an older version of @sc{gnats} rather than installing
./gnats/p-inst.texi:@sc{gnats} installation relies on two other freely available software
./gnats/p-inst.texi:build @sc{gnats}. These are @sc{gnu} @code{make} and @code{Texinfo}
./gnats/p-inst.texi:(version 4.2 or higher). Both are available from the @sc{gnu} FTP site at
./gnats/p-inst.texi:To build and install @sc{gnats}, you must:
./gnats/p-inst.texi:@ref{Locations,,Where @sc{gnats} lives}.
./gnats/p-inst.texi:Compile the @sc{gnats} programs on your system. @xref{Configure and
./gnats/p-inst.texi:Set up mail aliases for @sc{gnats}. @xref{Aliases,,Setting up mail
./gnats/p-inst.texi:Install the @sc{gnats} tools and utilities locally, and install the user
./gnats/p-inst.texi:Install the @sc{gnats} daemon @file{gnatsd}. @xref{Installing the
./gnats/p-inst.texi:need to instruct them to obtain and build the @sc{gnats} tools
./gnats/p-inst.texi:@sc{gnats}, such as Gnatsweb is a better solution since this requires
./gnats/p-inst.texi:directory, or @dfn{srcdir}. The sources for the @sc{gnats} tools are in
./gnats/p-inst.texi:As of @sc{gnats} version 4, having Emacs installed on the @sc{gnats}
./gnats/p-inst.texi:@cindex creating an account for the @sc{gnats} user
./gnats/p-inst.texi:@sc{gnats} is configured in the same directory you unpacked it in;
./gnats/p-inst.texi:when built, @sc{gnats} runs on the machine you're building it on;
./gnats/p-inst.texi:(@pxref{Locations,,Where @sc{gnats} lives}).
./gnats/p-inst.texi:all @sc{gnats} utilities operate on the @dfn{default database}, assumed
./gnats/p-inst.texi:@w{@file{/usr/local}}. @xref{Locations,,Where @sc{gnats} lives}.
./gnats/p-inst.texi:@xref{Locations,,Where @sc{gnats} lives}.
./gnats/p-inst.texi:Set @var{service-name} to be the @sc{gnats} network service. Default
./gnats/p-inst.texi:Set @var{username} to be the user name for @sc{gnats}. Default username
./gnats/p-inst.texi:Specify the default database to use when @sc{gnats} tools are invoked
./gnats/p-inst.texi:You can build @sc{gnats} in a different directory (@var{objdir}) from the
./gnats/p-inst.texi:Make sure you have @sc{gnu} @code{make}, then run
./gnats/p-inst.texi:(@pxref{Locations,,Where @sc{gnats} lives}).
./gnats/p-inst.texi:(@pxref{Locations,,Where @sc{gnats} lives}).
./gnats/p-inst.texi:After you have installed @sc{gnats}, you can remove the object files with
./gnats/p-inst.texi:If you do not have Emacs installed on your @sc{gnats} server, this step
./gnats/p-inst.texi:If you want people who are logged into the @sc{gnats} server itself to
./gnats/p-inst.texi:We are now going to initialize the default @sc{gnats} database. Run the
./gnats/p-inst.texi:older versions of @sc{gnats} should note that category directories are
./gnats/p-inst.texi:@item A directory for the mandatory @sc{gnats} category @var{pending}.
./gnats/p-inst.texi:@sc{gnats} before they are processed by @code{file-pr}.
./gnats/p-inst.texi:good basis for many @sc{gnats} databases. The default file causes
./gnats/p-inst.texi:similar behaviour to the 3.x versions of @sc{gnats}. However, even if
./gnats/p-inst.texi:of the @sc{gnats} user during configure, remember to substitute as
./gnats/p-inst.texi:@sc{gnats} server is installed. The instructions below are for Sendmail
./gnats/p-inst.texi:Create an alias for the @sc{gnats} administrator. This address should
./gnats/p-inst.texi:@sc{gnats}:
./gnats/p-inst.texi:pruned regularly; @pxref{Management,, @sc{gnats} Administration}.) In
./gnats/p-inst.texi:@sc{gnats} database.
./gnats/p-inst.texi:@cindex using @sc{gnats} over a network
./gnats/p-inst.texi:name, configure @sc{gnats} with
./gnats/p-inst.texi:@sc{gnats} daemon when connected on that port, send it a hangup signal
./gnats/p-inst.texi:across all the databases on a @sc{gnats} server). The location and name
./gnats/p-inst.texi:If you run a @sc{gnats} web interface or similar tool on the same
./gnats/p-inst.texi:@cindex using @sc{gnats} over a network
./gnats/p-inst.texi:@cindex configuring @sc{gnats} on a network
./gnats/p-inst.texi:When you install the @sc{gnats} utilities, the user tools
./gnats/p-inst.texi:machines with the @sc{gnats} user tools installed are referred to as
./gnats/p-inst.texi:client that a @sc{gnats} server may have to cater for:
./gnats/p-inst.texi:@sc{gnats} server, i.e. machines that are under the same
./gnats/p-inst.texi:over the network to the @sc{gnats} server.
./gnats/p-inst.texi:@cindex using @sc{gnats} over a local network
./gnats/p-inst.texi:@cindex configuring @sc{gnats} on a local network
./gnats/p-inst.texi:@sc{gnats} server, you can simply share out the directories on the
./gnats/p-inst.texi:create several shared @sc{gnats} installations, one for each platform.
./gnats/p-inst.texi:@cindex using @sc{gnats} remotely
./gnats/p-inst.texi:@cindex configuring @sc{gnats} for remote users
./gnats/p-inst.texi:installation of the @sc{gnats} tools. In this case, you may choose to
./gnats/p-inst.texi:clients that need the @sc{gnats} tools, the following needs to be
./gnats/p-inst.texi:@item Configure and build @sc{gnats} on the client machine
./gnats/p-inst.texi:e-mail instead of speaking directly over the network to the @sc{gnats}
./gnats/p-inst.texi:server, you need to create a problem report template on the @sc{gnats}
./gnats/p-inst.texi:@sc{gnats} server, use the command
./gnats/p-inst.texi:For clients that have no direct network access to your @sc{gnats}
./gnats/p-inst.texi:The following procedure covers an upgrade from all @sc{gnats} 3 versions
./gnats/p-inst.texi:@file{UPGRADING.old} file in the @sc{gnats} distribution before carrying
./gnats/p-inst.texi:Although almost all of the @sc{gnats} internals have been redesigned and
./gnats/p-inst.texi:rewritten for @sc{gnats} 4, little has changed in the format and
./gnats/p-inst.texi:is binary in a default installation of @sc{gnats} 4. Thus, you will
./gnats/p-inst.texi:tool. In addition, if your old @sc{gnats} installation was so-called
./gnats/p-inst.texi:@sc{gnats} 3.11x's defaults, you still need to migrate any changes you
./gnats/p-inst.texi:installed copies of the @sc{gnats} user tools (@code{send-pr},
./gnats/p-inst.texi:Since the @sc{gnats} network daemon has been completely reworked, with
./gnats/p-inst.texi:@sc{gnats} 4. The @file{contrib} directory of this distribution
./gnats/p-inst.texi:This document only deals with upgrading @sc{gnats} itself. Third-party
./gnats/p-inst.texi:Before you begin, make a backup of your entire @sc{gnats} database
./gnats/p-inst.texi:directory hierarchy, the @sc{gnats} executables directory and the
./gnats/p-inst.texi:@sc{gnats} user tools (@code{send-pr}, @code{query-pr} etc.) The
./gnats/p-inst.texi:locations of these may vary, but in a default @sc{gnats} 3 installation,
./gnats/p-inst.texi:remove the old @sc{gnats} 3 executables and tools, escpecially if you
./gnats/p-inst.texi:plan to install @sc{gnats} 4 in a different location than version 3.
./gnats/p-inst.texi:Build and install @sc{gnats} 4. @xref{Installation,, Installing
./gnats/p-inst.texi:@sc{gnats}}. It is recommended that you use the
./gnats/p-inst.texi:@sc{gnats} 3 databases.
./gnats/p-inst.texi:Edit the @sc{gnats} @file{databases} file and add entries for all your
./gnats/p-inst.texi:old @sc{gnats} 3 databases. In a default @sc{gnats} 4 installation
./gnats/p-inst.texi:In @sc{gnats} 3, the file @file{gnatsd.conf} specifies minimum access
./gnats/p-inst.texi:levels for the different hosts accessing the @sc{gnats} daemon,
./gnats/p-inst.texi:@sc{gnats} 4, these files have been replaced by a single file named
./gnats/p-inst.texi:settings from all your @sc{gnats} 3 databases and add them to the
./gnats/p-inst.texi:access to @sc{gnats} databases}.
./gnats/p-inst.texi:field definitions etc. which makes this version of @sc{gnats} behave
./gnats/p-inst.texi:@w{@file{gnats-adm}} directories of any other @sc{gnats} databases that
./gnats/p-inst.texi:@sc{gnats} 4.
./gnats/p-inst.texi:This setting has no counterpart in @sc{gnats} 4, since @sc{gnats} no
./gnats/p-inst.texi:@sc{gnats} 4 has no concept of a named `site', so this directive is
./gnats/p-inst.texi:The @sc{gnats} 4 @file{dbconfig} file has separate configuration
./gnats/p-inst.texi:settings available in the @sc{gnats} 4 @file{dbconfig} file, you should
./gnats/p-inst.texi:If your old @sc{gnats} installations was release-based, i.e. it included
./gnats/p-inst.texi:@ref{release-based support,,Supporting old @sc{gnats} ``release-based''
./gnats/p-inst.texi:Furthermore, @sc{gnats} 4 uses a different password format in the
./gnats/p-inst.texi:access to @sc{gnats} databases}). You need to translate your old
./gnats/p-inst.texi:Sit back and enjoy your new @sc{gnats} 4 setup...
./gnats/states.texi:@sc{gnats} uses these states:
./gnats/p-admin.texi:@chapter @sc{gnats} Administration
./gnats/p-admin.texi:@cindex administering @sc{gnats}
./gnats/p-admin.texi:@cindex managing @sc{gnats}
./gnats/p-admin.texi:In daily usage, @sc{gnats} is self-maintaining. However, there are
./gnats/p-admin.texi:make changes to the @sc{gnats} configuration at some point:
./gnats/p-admin.texi:@sc{gnats} places the PR in the @w{@file{pending}} directory
./gnats/p-admin.texi:(@pxref{Locations,,Where @sc{gnats} lives}). PRs
./gnats/p-admin.texi:@w{@file{pending}} directory. If so configured, @sc{gnats} sends a
./gnats/p-admin.texi:@sc{gnats} tool such as @code{edit-pr} to set the correct category of
./gnats/p-admin.texi:should arrange to have all mail that is sent to the @sc{gnats} database
./gnats/p-admin.texi:@sc{gnats} supports multiple databases. If you find at some point that
./gnats/p-admin.texi:Most installations of @sc{gnats} will only require you to add a new line
./gnats/p-admin.texi:@xref{Locations,,Where @sc{gnats} lives}.
./gnats/p-admin.texi:@section Overview of @sc{gnats} configuration
./gnats/p-admin.texi:@cindex @sc{gnats} configuration
./gnats/p-admin.texi:@cindex Overview of @sc{gnats} configuration
./gnats/p-admin.texi:@xref{Locations,,Where @sc{gnats} lives}.
./gnats/p-admin.texi:@sc{gnats} has two, well, actually three, different kinds of
./gnats/p-admin.texi:@dfn{database-specific} configuration files determine how @sc{gnats}
./gnats/p-admin.texi:time a @sc{gnats} tool is invoked, the new parameters will take
./gnats/p-admin.texi:These are the site-wide configuration files used by @sc{gnats}:
./gnats/p-admin.texi:which directory they are located. This file is used by the @sc{gnats}
./gnats/p-admin.texi:in the databases on this machine. @xref{Access Control,,@sc{gnats}
./gnats/p-admin.texi:user access level file). @xref{Access Control,,@sc{gnats} access
./gnats/p-admin.texi:Controls most aspects of how @sc{gnats} behaves when dealing with your
./gnats/p-admin.texi:The list of categories that @sc{gnats} accepts as valid for the
./gnats/p-admin.texi:through this file whenever mail is sent from @sc{gnats}.
./gnats/p-admin.texi:Lists sites from whom @sc{gnats} accepts Problem Reports. The existence
./gnats/p-admin.texi:@code{Submitter} field is not filled in, @sc{gnats} will use entries in
./gnats/p-admin.texi:@xref{Access Control,,@sc{gnats} access control}.
./gnats/p-admin.texi:file containing the list of @sc{gnats} databases that are available
./gnats/p-admin.texi:empty field), the fourth field is the hostname of the remote @sc{gnats}
./gnats/p-admin.texi:@sc{gnats} is running on.
./gnats/p-admin.texi:If @sc{gnats} was built with default options, the @file{databases} file
./gnats/p-admin.texi:of @sc{gnats}, the @file{databases} file has the name and location given
./gnats/p-admin.texi:with @sc{gnats}.
./gnats/p-admin.texi:@sc{gnats} database. Each database has its own individual copy of this
./gnats/p-admin.texi:the new values take effect for all subsequent iterations of @sc{gnats}
./gnats/p-admin.texi:@sc{gnats}.
./gnats/p-admin.texi:Specifies the directory where the @sc{gnats} administrative executables
./gnats/p-admin.texi:them. @sc{gnats} uses these values to determine whether the required
./gnats/p-admin.texi:be given with a dash separating them. @sc{gnats} uses these values to
./gnats/p-admin.texi:if you have local users on the @sc{gnats} server itself, running for
./gnats/p-admin.texi:and @code{:} are used internally as field markers by @sc{gnats}, so they must
./gnats/p-admin.texi:text. There is no required order, unlike previous versions of @sc{gnats}
./gnats/p-admin.texi:Indicates that this field corresponds to one of the @sc{gnats} built-in
./gnats/p-admin.texi:@sc{gnats} has several fields which are required to be present in a PR,
./gnats/p-admin.texi:@sc{gnats} clients and @code{gnatsd}. We also recommend that you
./gnats/p-admin.texi:During the life of a PR, @sc{gnats} can be configured to send out a
./gnats/p-admin.texi:sent out to the various parties, and if a PR is deleted, @sc{gnats} may
./gnats/p-admin.texi:given, @sc{gnats} will attempt to extract an email address from the
./gnats/p-admin.texi:separated by @samp{|} characters, @sc{gnats} will try to extract an address
./gnats/p-admin.texi:will contain the email address of the @sc{gnats} administrator, as
./gnats/p-admin.texi:To fill in the @code{To:} header, @sc{gnats} will first look for the
./gnats/p-admin.texi:it will look for the @sc{gnats} @code{Submitter-Id} field and use the
./gnats/p-admin.texi:Other email headers to be included in messages sent out by @sc{gnats}
./gnats/p-admin.texi:For some of the formats that @sc{gnats} recognizes, special variables
./gnats/p-admin.texi:specific to the database, which @sc{gnats} tracks. This file also
./gnats/p-admin.texi:@sc{gnats} is configured to create directories on disk for valid
./gnats/p-admin.texi:configuration,,Overall database configuration}). If @sc{gnats} isn't set
./gnats/p-admin.texi:To create a new category, log in as @sc{gnats}, add a line to this file,
./gnats/p-admin.texi:Only one category @emph{must} be present for @sc{gnats} to function:
./gnats/p-admin.texi:@noindent The following entry @emph{must} be present for @sc{gnats} to function:
./gnats/p-admin.texi:@code{gnats-admin} is usually defined as a mail alias when @sc{gnats} is
./gnats/p-admin.texi:@sc{gnats} administrator, by adding the desired address at the end of
./gnats/p-admin.texi:configuration,,Overall database configuration}, @sc{gnats} will use
./gnats/p-admin.texi:To disable the feature of @sc{gnats} which tracks the
./gnats/p-admin.texi:@sc{gnats} itself does not currently use the description for anything,
./gnats/p-admin.texi:different name has been chosen for this state, @sc{gnats} will force
./gnats/p-admin.texi:e-mail to the PR submission email address), @sc{gnats} will try to
./gnats/p-admin.texi:@sc{gnats} checks each line in the @code{addresses} file, comparing
./gnats/p-admin.texi:a match. If no match is found, @sc{gnats} uses the default submitter ID.
./gnats/p-admin.texi:@sc{gnats} can match addresses in three e-mail formats:
./gnats/p-admin.texi:If @sc{gnats} sees other e-mail address formats, it uses the default
./gnats/p-admin.texi:implementation of @sc{gnats}, so it may be left blank. The @code{class}
./gnats/p-admin.texi:description of the class. @sc{gnats} itself does not use the class
./gnats/p-admin.texi:If @sc{gnats} was built with default options, the @file{send-pr.conf}
./gnats/p-admin.texi:@sc{gnats}, the @file{send-pr.conf} file resides at the location
./gnats/p-admin.texi:If the @sc{gnats} server can't be reached directly over the network,
./gnats/p-admin.texi:with the @sc{gnats} server to determine what fields to include in a
./gnats/p-admin.texi:with a template. If the @sc{gnats} server can't be reached directly
./gnats/p-admin.texi:@sc{gnats} server by using the command @command{send-pr -p}.
./gnats/p-admin.texi:@cindex files used for @sc{gnats} administration
./gnats/p-admin.texi:are maintained by @sc{gnats}; you should never need to touch them.
./gnats/p-admin.texi:first PR comes in. It is then kept up to date by @sc{gnats}; you should
./gnats/p-admin.texi:It is used internally by @sc{gnats}; you need never touch this file.
./gnats/p-admin.texi:These tools are used by the @sc{gnats} administrator as part of the
./gnats/p-admin.texi:periodic maintenance and configuration of @sc{gnats}.
./gnats/p-admin.texi:@xref{Management,,@sc{gnats} Administration}.
./gnats/p-admin.texi:To initialize a new @sc{gnats} database:
./gnats/p-admin.texi:(@pxref{Locations,,Where @sc{gnats} lives}.
./gnats/p-admin.texi:default database, as set when @sc{gnats} was built (usually
./gnats/p-admin.texi:Check all @sc{gnats} databases on the system. This option takes
./gnats/p-admin.texi:Older versions of @sc{gnats}, up to and including version 3.x, stored
./gnats/p-admin.texi:old password files to a new format when upgrading to @sc{gnats} version
./gnats/p-admin.texi:These tools are used internally by @sc{gnats}. You should never need to
./gnats/p-admin.texi:problems with the @sc{gnats} tools or with your local implementation.
./gnats/p-admin.texi:The program @code{queue-pr} handles traffic coming into @sc{gnats}.
./gnats/p-admin.texi:@sc{gnats} database. @xref{Installation,,Installing @sc{gnats}}.
./gnats/p-admin.texi:(@pxref{Locations,,Where @sc{gnats} lives}).
./gnats/p-admin.texi:undefined, the default database name set when @sc{gnats} was built is
./gnats/p-admin.texi:@sc{gnats} administrator is notified of the unplaceable PR.
./gnats/p-admin.texi:files it in the @sc{gnats} database (under the default, if the
./gnats/p-admin.texi:acknowledgments to appropriate parties. For the default @sc{gnats}
./gnats/p-admin.texi:configuration,,Changing your @sc{gnats} configuration}).
./gnats/p-admin.texi:that is undefined, the default database name set when @sc{gnats} was
./gnats/p-admin.texi:Hostname of the @sc{gnats} server.
./gnats/p-admin.texi:The port that the @sc{gnats} server runs on.
./gnats/p-admin.texi:Username used to log into the @sc{gnats} server.
./gnats/p-admin.texi:Password used to log into the @sc{gnats} server.
./gnats/p-admin.texi:has passed, @code{at-pr} sends a reminder to the @sc{gnats}
./gnats/p-admin.texi:specified instead of @emph{gnats} during the building of @sc{gnats}) is
./gnats/p-admin.texi:specified, the default database name set when @sc{gnats} was built is
./gnats/p-admin.texi:Hostname of the @sc{gnats} server.
./gnats/p-admin.texi:The port that the @sc{gnats} server runs on.
./gnats/p-admin.texi:Username used to log into the @sc{gnats} server.
./gnats/p-admin.texi:Password used to log into the @sc{gnats} server.
./gnats/gnats-faq.texi:@settitle @sc{gnats} Frequently Asked Questions
./gnats/gnats-faq.texi:entitled ``Copying'' and ``@sc{gnu} General Public License''
./gnats/gnats-faq.texi:@title @sc{gnats} Frequently Asked Questions
./gnats/gnats-faq.texi: entitled ``Copying'' and ``@sc{gnu} General Public License''
./gnats/gnats-faq.texi:@top @sc{gnats} Frequently Asked Questions
./gnats/gnats-faq.texi:@sc{gnats}, the @sc{gnu} problem report management system, and related
./gnats/gnats-faq.texi:using the help-gnats mailing list and the @sc{gnats} documentation as
./gnats/gnats-faq.texi:* Configuration:: Problems with @sc{gnats} configuration
./gnats/gnats-faq.texi:* Clients:: Ways to access a @sc{gnats} system
./gnats/gnats-faq.texi:* Get it:: Where to get @sc{gnats}
./gnats/gnats-faq.texi:@section What is @sc{gnats}?
./gnats/gnats-faq.texi:@sc{gnats} is the @sc{gnu} problem report management system. Problem
./gnats/gnats-faq.texi:@sc{gnats} stores all information about the problem reports at a central
./gnats/gnats-faq.texi:@sc{gnats} is widely customizable: Of course you can define report
./gnats/gnats-faq.texi:Starting with @sc{gnats} 4.0, you can define your own custom fields, and
./gnats/gnats-faq.texi:front-end either directly contacts the @sc{gnats} server, or sends the
./gnats/gnats-faq.texi:of @sc{gnats}). For an incomplete list of front-ends see @ref{Clients}.
./gnats/gnats-faq.texi:contacting several @sc{gnats} servers, or several problem report
./gnats/gnats-faq.texi:databases managed by the same @sc{gnats} server.
./gnats/gnats-faq.texi:@section How is "@sc{gnats}" pronounced?
./gnats/gnats-faq.texi:Q: So, How can I pronounce "@sc{gnats}?" Should I pronounce "G"?
./gnats/gnats-faq.texi:See the @sc{gnats} home page at @uref{http://www.gnu.org/software/gnats/}.
./gnats/gnats-faq.texi:@uref{http://savannah.gnu.org/projects/gnats,@sc{gnu} savannah
./gnats/gnats-faq.texi:@sc{gnats} project page} for the instructions how to get it.
./gnats/gnats-faq.texi:The version numbers of @sc{gnats} 3.x is somewhat confusing, because
./gnats/gnats-faq.texi:@sc{gnats} 4.0 was released in August 2003, and 4.1 was released in March 2005.
./gnats/gnats-faq.texi:Currently, the following @sc{gnats} mailing lists exist:
./gnats/gnats-faq.texi:This is a low volume moderated mailing lists for @sc{gnats} related
./gnats/gnats-faq.texi:A low-to-middle volume mailing list where anything related to @sc{gnats}
./gnats/gnats-faq.texi:Lists that are of interest mainly for the @sc{gnats} developers:
./gnats/gnats-faq.texi:the follow-ups (Whatever goes into @sc{gnats}' @code{>Audit-Trail:} field).
./gnats/gnats-faq.texi:This is a common bug database for @sc{gnats}, Gnatsweb and TkGnats.
./gnats/gnats-faq.texi:(And, yes, of course: It uses @sc{gnats} and Gnatsweb.)
./gnats/gnats-faq.texi:When you report problems concerning @sc{gnats} itself, please do not
./gnats/gnats-faq.texi:The @sc{gnats} version you are using. If your problem involves
./gnats/gnats-faq.texi:developers (keep in mind that they are working on @sc{gnats} and
./gnats/gnats-faq.texi:with 4.0. Furthermore, the @sc{gnats} 3 branch is not maintained
./gnats/gnats-faq.texi:@emph{directory} of the @sc{gnats} database in 3.1xx, and now takes its
./gnats/gnats-faq.texi:@sc{gnats} admin, or even to @code{nobody} (usually aliased to
./gnats/gnats-faq.texi:# On the @sc{gnats} 3 server:
./gnats/gnats-faq.texi:# If the @sc{gnats} 4 server is different:
./gnats/gnats-faq.texi:# On the @sc{gnats} 4 server:
./gnats/gnats-faq.texi:* Gnatsweb and GNATS:: Cooperation problems between @sc{gnats} and Gnatsweb
./gnats/gnats-faq.texi:@section Gnatsweb and @sc{gnats} do not like each other.
./gnats/gnats-faq.texi:@b{Q:} I have installed @sc{gnats} 3.999.x and Gnatsweb 2.9.x, and I
./gnats/gnats-faq.texi:nevertheless, it hangs when trying to login into the @sc{gnats} server.
./gnats/gnats-faq.texi:Gnatsweb 2.9.x is for use with @sc{gnats} 3.113.1.
./gnats/gnats-faq.texi:With @sc{gnats} 3.999.x, you must use Gnatsweb 3.99.x; it is in the
./gnats/gnats-faq.texi:contrib subdirectory of the @sc{gnats} distribution.
./gnats/gnats-faq.texi:(@sc{gnats} 3.999.x/Gnatsweb 3.99.x were pre-releases of the 4.0
./gnats/gnats-faq.texi:For @sc{gnats} 4.x, use Gnatsweb 4.0 or greater.
./gnats/gnats-faq.texi:* General configuration:: General questions about @sc{gnats} configuration
./gnats/gnats-faq.texi:* Gnatsd:: Configuration of the @sc{gnats} daemon
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 3.1xx)}
./gnats/gnats-faq.texi:(Please consider upgrading to @sc{gnats} 4.0 or greater.)
./gnats/gnats-faq.texi:@sc{gnats} user.
./gnats/gnats-faq.texi:and make sure they is owned by the @sc{gnats} user.
./gnats/gnats-faq.texi:As the @sc{gnats} user,
./gnats/gnats-faq.texi:If your @sc{gnats} sits behind a firewall and needs to exchange mails
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 4.x)} With version 4, this has become much easier
./gnats/gnats-faq.texi:Then, as the @sc{gnats} user, run @samp{mkdb GreatNewDB} to create the
./gnats/gnats-faq.texi:@w{@file{/usr/local/gnats/db2}}) can be created by the @sc{gnats} user.
./gnats/gnats-faq.texi:Now, as the @sc{gnats} user, edit the files in directory
./gnats/gnats-faq.texi:create new category directories in your database---@sc{gnats} 4
./gnats/gnats-faq.texi:If you are updating from @sc{gnats} 3.1xx, note that the @samp{-d}
./gnats/gnats-faq.texi:If your @sc{gnats} sits behind a firewall and needs to exchange mails
./gnats/gnats-faq.texi:This can be done with any @sc{gnats} client; check the archives
./gnats/gnats-faq.texi:of the @sc{help-gnats} mailing list for hints about automating
./gnats/gnats-faq.texi:If you are using @sc{gnats} 4 (or planning to upgrade soon), you
./gnats/gnats-faq.texi:existing PR arrives via e-mail, @sc{gnats} 4.x checks that both
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 3.1xx)} The fields and their names are fixed in
./gnats/gnats-faq.texi:@sc{gnats} 3.1xx, so this is not possible.
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 4.x)} Edit the file @file{dbconfig} to reflect your
./gnats/gnats-faq.texi:@section Gnatsd, the @sc{gnats} Daemon
./gnats/gnats-faq.texi:@cindex @sc{gnats} server, see gnatsd
./gnats/gnats-faq.texi:This is also described in the @sc{gnats} manual; see @ref{Installing the
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 3.1xx)}
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 4.0)}
./gnats/gnats-faq.texi:(If you are still using @sc{gnats} 3.xxx, the file is named
./gnats/gnats-faq.texi:@subsubheading Mail from @sc{gnats} bounces
./gnats/gnats-faq.texi:Probably your @sc{gnats} sits behind a firewall, but it needs to
./gnats/gnats-faq.texi:To solve this problem, get an "official" address for your @sc{gnats}
./gnats/gnats-faq.texi:@samp{--directory} option (@samp{--database} for @sc{gnats} 4.x)
./gnats/gnats-faq.texi:(e.g., @code{Responsible}) which is normally assigned by @sc{gnats}.
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 3.1xx)}
./gnats/gnats-faq.texi:This is not possible in @sc{gnats} 3.1xx.
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 4.x)} This is done by adding the field name (in this
./gnats/gnats-faq.texi:Several client applications can be found in the @sc{gnats} distribution.
./gnats/gnats-faq.texi:The most important are Gnatsweb (a WWW interface to @sc{gnats}), TkGnats (a
./gnats/gnats-faq.texi:Tcl/Tk based interface), a @sc{gnats} mode for Emacs and XEmacs, and send-pr
./gnats/gnats-faq.texi:* Gnatsweb:: a WWW interface to @sc{gnats}
./gnats/gnats-faq.texi:@code{gnatsweb-global} to store the @sc{gnats} database you are working on,
./gnats/gnats-faq.texi:@section @sc{gnats} Mode for Emacs
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 3.1xx)} Yes.
./gnats/gnats-faq.texi:@b{A: (@sc{gnats} 4.x)} Still to be tested.
./gnats/gnats-faq.texi:This is not contributed software, but part of @sc{gnats} itself.
./gnats/gnats-faq.texi:@sc{gnats} mode for (X)Emacs.
./gnats/gnats-faq.texi:The @sc{gnats} daemon (server program).
./gnats/gnats-faq.texi:A WWW interface to @sc{gnats}.
./gnats/gnats-faq.texi:Short for ``Problem Report''. An entry in a @sc{gnats} database.
./gnats/gnats-faq.texi:A Tcl/Tk based interface to @sc{gnats}.
./gnats/emacs.texi:@section The Emacs interface to @sc{gnats}
./gnats/emacs.texi:Emacs interface to @sc{gnats} provides basic access to @sc{gnats}
./gnats/emacs.texi:This section provides an overview of using @sc{gnats} with Emacs. It
./gnats/emacs.texi:installation instructions of the @sc{gnats} Emacs mode, see
./gnats/emacs.texi:@w{@sc{gnats} 3} and @w{@sc{gnats} 4}. It now uses @code{gnatsd},
./gnats/emacs.texi:send your suggestions and patches to the appropriate @sc{gnats}
./gnats/emacs.texi:Similarly to other @sc{gnats} Emacs modes, there is a hook available
./gnats/emacs.texi:function is useful if connection to a @sc{gnats} server was
./gnats/emacs.texi:Unlock the whole @sc{gnats} database. This function is useful in
./gnats/emacs.texi:can view the Emacs communication with @sc{gnatsd} in it. This is
./gnats/p-usage.texi:@chapter The @sc{gnats} User Tools
./gnats/p-usage.texi:@cindex usage for the @sc{gnats} user tools
./gnats/p-usage.texi:@cindex invoking the @sc{gnats} user tools
./gnats/p-usage.texi:This chapter describes the user tools distributed with @sc{gnats}. The
./gnats/p-usage.texi:@sc{gnats} administrative and internal tools are described in
./gnats/p-usage.texi:@ref{Management,,@sc{gnats} Administration}. The user tools provide
./gnats/p-usage.texi:Used to query the @sc{gnats} database (@pxref{query-pr,,Querying the
./gnats/p-usage.texi:@section Environment variables and @sc{gnats} tools
./gnats/p-usage.texi:All the @sc{gnats} user tools honor the @code{GNATSDB} environment
./gnats/p-usage.texi:you avoid deleting any information in the @sc{Text} and @sc{MultiText}
./gnats/p-usage.texi:@sc{gnats} may have differently named fields, and sites using such
./gnats/p-usage.texi:@sc{gnats} as relating to an existing PR is also appended to the
./gnats/p-usage.texi:with older versions of @sc{gnats} and are likely to be deleted in the next
./gnats/p-usage.texi:of @sc{gnats} is configured for this. To use this feature, simply send
./gnats/p-usage.texi:@sc{gnats} replies to your mail with the results of your query. The
./gnats/p-usage.texi:future releases of @sc{gnats}; their functionality can be replaced with
./gnats/p-usage.texi:@code{%D}: For date fields, the date is written in a standard @sc{gnats}
./gnats/p-usage.texi:yields all PRs whose @sc{Text} fields contain the text @samp{The quick}
./gnats/s-usage.texi:@sc{gnu} Emacs using @w{@samp{M-x send-pr}} (@pxref{Emacs
./gnats/s-usage.texi:submit to the local @sc{gnats} database named @var{default} and calls
./gnats/s-usage.texi:in @ref{Environment,,Environment variables and @sc{gnats} tools}.
./gnats/s-usage.texi:You can use an interactive @code{send-pr} interface from within @sc{gnu}
./gnats/s-usage.texi:interface to @sc{gnats}}.
./gnats/s-usage.texi:@item @sc{gnats} fields
./gnats/s-usage.texi:to submit PRs by e-mail or by speaking directly to the @sc{gnats}
./gnats/s-usage.texi:The @strong{@sc{gnats} fields} below the mail header form the bulk of a
./gnats/s-usage.texi:@sc{gnats} Problem Report.
./gnats/s-usage.texi:@sc{gnats} server or submits it by mail to the address named in the
./gnats/s-usage.texi:When you send unformatted e-mail to this address, @sc{gnats} processes
./gnats/s-usage.texi:@sc{gnats} will try to derive the @code{Submitter} field from the address
./gnats/s-usage.texi:etc. are set to default values as defined by the @sc{gnats} administrator.
./gnats/s-usage.texi:@cindex Using and Porting @sc{gnu} CC
./gnats/s-usage.texi:@sc{gnu} @code{gcc} in @ref{Bugs, , Reporting Bugs, gcc, Using and
./vrtater/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/emacs/emacs/text.texi:The curved single quote characters are U+2018 @sc{left single quotation
./SOME/emacs/emacs/text.texi:mark} and U+2019 @sc{right single quotation mark}; the curved double quotes
./SOME/emacs/emacs/text.texi:are U+201C @sc{left double quotation mark} and U+201D @sc{right double
./SOME/emacs/emacs/mule.texi:The special character @code{RIGHT-TO-LEFT MARK}, or @sc{rlm}, forces
./SOME/emacs/emacs/mule.texi:@code{LEFT-TO-RIGHT MARK}, or @sc{lrm} forces the left-to-right
./SOME/emacs/emacs/mule.texi:In a GUI session, the @sc{lrm} and @sc{rlm} characters display as very
./SOME/emacs/emacs/msdos.texi:come with such a program, although several ports of @sc{gnu} @code{ls}
./SOME/emacs/emacs/msdos.texi:Emulate @sc{gnu} systems; this is the default. This sets
./SOME/emacs/emacs/msdos.texi:platforms prefer the @sc{gnu} defaults.
./SOME/emacs/emacs/msdos.texi:displaying a given non-@sc{ascii} character might fail for some rare
./SOME/emacs/emacs/search.texi:such as U+249C @sc{parenthesized latin small letter a} and U+2100
./SOME/emacs/emacs/search.texi:@sc{account of} (which looks like a small @code{a} over @code{c}).
./SOME/emacs/emacs/search.texi:@sc{latin small ligature ff}. Character sequences that are not identical,
./SOME/emacs/emacs/basic.texi:which is Unicode code-point U+2018 @sc{left single quotation mark},
./SOME/emacs/misc/emacs-mime.texi:* Charset Translation:: How charsets are mapped from @sc{mule} to @acronym{MIME}.
./SOME/emacs/misc/emacs-mime.texi:If you are running a non-@sc{mule} Emacs, this process is simple: If the
./SOME/emacs/misc/emacs-mime.texi:Things are slightly more complicated when running Emacs with @sc{mule}
./SOME/emacs/misc/emacs-mime.texi:support. In this case, a list of the @sc{mule} charsets used in the
./SOME/emacs/misc/emacs-mime.texi:part is obtained, and the @sc{mule} charsets are translated to
./SOME/emacs/misc/emacs-mime.texi:When running Emacs with @sc{mule} support, the preferences for which
./SOME/emacs/misc/org.texi:Richard @@@@texinfo:@@sc@{@@@@Stallman@@@@texinfo:@}@@@@ commence' GNU.
./SOME/emacs/misc/cl.texi:form is a regular Lisp variable. But the @sc{car}s and @sc{cdr}s of lists,
./SOME/emacs/misc/cl.texi:It searches for an element of the list whose @sc{car} equals
./SOME/emacs/misc/cl.texi:then on the @sc{cdr}s of those lists, and so on, until the
./SOME/emacs/misc/cl.texi:@sc{car}s of the advancing pointers.
./SOME/emacs/misc/cl.texi:rearranging the @sc{cdr} pointers in suitable fashion.
./SOME/emacs/misc/cl.texi:list (where the @sc{cdr}-chain forms a loop rather than terminating
./SOME/emacs/misc/cl.texi:argument becomes the @sc{cdr} of the last cell constructed.
./SOME/emacs/misc/cl.texi:@var{y} are both cons cells, their @sc{car}s and @sc{cdr}s are
./SOME/emacs/misc/cl.texi:on, and compares against @var{old}, both @sc{car}s and @sc{cdr}s
./SOME/emacs/misc/cl.texi:function, if any), is compared with the @sc{car}s of
./SOME/emacs/misc/cl.texi:@sc{cdr}.
./SOME/emacs/misc/cl.texi:If a match is found, it returns the cons cell whose @sc{car} was
./SOME/emacs/misc/cl.texi:any of its @sc{cdr}s.
./SOME/emacs/misc/cl.texi:element whose @sc{car} matches (in the sense of @code{:test},
./SOME/emacs/misc/cl.texi:This function searches for an element whose @sc{cdr} matches
./SOME/emacs/misc/widget.texi:A list whose @sc{car} is the widget representing the currently chosen
./SOME/emacs/misc/widget.texi:List whose @sc{car} is the type of the list elements.
./SOME/emacs/misc/widget.texi:The value of a @code{cons} widget must be a cons-cell whose @sc{car}
./SOME/emacs/misc/widget.texi:and @sc{cdr} have two specified types. It uses this syntax:
./SOME/emacs/misc/widget.texi:and @kbd{C-o} (suggested by @sc{rms}).
./SOME/emacs/misc/widget.texi:whether you want to add or delete an item (@sc{rms} wanted to git rid of
./SOME/emacs/misc/sieve.texi:for talking to a server with the @sc{managesieve} protocol.
./SOME/emacs/misc/ede.texi:@scindex ede-sourcecode
./SOME/emacs/misc/message.texi:Each list element should be a cons, where the @sc{car} should be the
./SOME/emacs/misc/message.texi:name of a header (e.g., @code{CC}) and the @sc{cdr} should be the header
./SOME/emacs/misc/message.texi:In addition, you can enter conses into this list. The @sc{car} of this cons
./SOME/emacs/misc/message.texi:the @sc{cdr} can either be a string to be entered verbatim as the value of
./SOME/emacs/misc/message.texi:If the list contains a cons where the @sc{car} of the cons is
./SOME/emacs/misc/message.texi:@code{optional}, the @sc{cdr} of this cons will only be inserted if it is
./SOME/emacs/misc/message.texi:is @code{iso-8859-1} on non-@sc{mule} Emacsen; otherwise @code{nil},
./SOME/emacs/misc/message.texi:which means ask the user. (This variable is used only on non-@sc{mule}
./SOME/emacs/misc/message.texi:Emacs MIME Manual}, for details on the @sc{mule}-to-@acronym{MIME}
./SOME/emacs/misc/message.texi:@sc{car} is a function and the @sc{cdr} is the list of arguments, or
./SOME/emacs/misc/autotype.texi:@code{auto-insert-alist}. The @sc{car}s of this list are each either
./SOME/emacs/misc/autotype.texi:the same mode in Emacs can be distinguished. The @sc{car}s may also
./SOME/emacs/misc/autotype.texi: When a matching element is found, the @sc{cdr} says what to do. It may
./SOME/emacs/misc/trampver.texi:@set tramp @sc{Tramp}
./SOME/emacs/misc/viper.texi:dm@@scs.cs.nyu.edu (David Mazieres),
./SOME/emacs/misc/sasl.texi:@sc{sasl} is short for @dfn{Simple Authentication and Security Layer}.
./SOME/emacs/misc/sasl.texi:The toplevel interface of this library is inspired by Java @sc{sasl}
./SOME/emacs/misc/sasl.texi:A mechanism (@code{sasl-mechanism} object) is a schema of the @sc{sasl}
./SOME/emacs/misc/reftex.texi:@c dominik@@science.uva.nl
./SOME/emacs/misc/dbus.texi:A D-Bus compound type is always represented as a list. The @sc{car}
./SOME/emacs/misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./SOME/emacs/misc/gnus.texi:Things got a bit more complicated with @sc{gnus}. In addition to
./SOME/emacs/misc/gnus.texi:the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
./SOME/emacs/misc/gnus.texi:@sc{gnus} and other newsreaders.
./SOME/emacs/misc/gnus.texi:@sc{gnus 4.1}, where you had explicit keystrokes for everything under
./SOME/emacs/misc/gnus.texi:correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
./SOME/emacs/misc/gnus.texi:even with @sc{xover} by registering the @code{Xref} lines of all
./SOME/emacs/misc/gnus.texi:@cindex @sc{mode reader}
./SOME/emacs/misc/gnus.texi:not easy. People who prefer proper mail readers should try @sc{vm}
./SOME/emacs/misc/gnus.texi:where the @sc{car} of a cell contains the key, and the @sc{cdr}
./SOME/emacs/misc/gnus.texi:Two summary functions for editing a @sc{gnus} kill file:
./SOME/emacs/misc/gnus.texi:@sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
./SOME/emacs/misc/gnus.texi:pronounced ``news'' as @sc{Umeda} intended, which makes it a more
./SOME/emacs/misc/gnus.texi:``@sc{gnus}''. New vs. old.
./SOME/emacs/misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./SOME/emacs/misc/gnus.texi:reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
./SOME/emacs/misc/gnus.texi:Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
./SOME/emacs/misc/gnus.texi:All code that relies on knowledge of @sc{gnus} internals will probably
./SOME/emacs/misc/gnus.texi:fact, you should probably remove all old @sc{gnus} packages (and other
./SOME/emacs/misc/gnus.texi:does what you have written code to make @sc{gnus} do. (Snicker.)
./SOME/emacs/misc/gnus.texi:Gnus understands all @sc{gnus} startup files.
./SOME/emacs/misc/gnus.texi:@sc{gnus} internals should suffer no problems. If problems occur,
./SOME/emacs/misc/gnus.texi:Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
./SOME/emacs/misc/gnus.texi:Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
./SOME/emacs/misc/gnus.texi:of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
./SOME/emacs/misc/gnus.texi:controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
./SOME/emacs/misc/gnus.texi:normal @sc{head} format.
./SOME/emacs/misc/gnus.texi:been running @sc{gnus}, you need to exit Emacs and start it up again before
./SOME/emacs/misc/gnus.texi:@sc{gnus} introduced a concept that I found so useful that I've started
./SOME/emacs/misc/url.texi:@cindex @sc{socks}
./SOME/emacs/misc/url.texi:Use if the firewall has a @sc{socks} gateway running on it. The
./SOME/emacs/misc/url.texi:@sc{socks} v5 protocol is defined in RFC 1928.
./SOME/emacs/misc/url.texi:the @sc{socks} server.
./SOME/emacs/misc/url.texi:@sc{socks} server. By default this is your login name.
./SOME/emacs/misc/url.texi:@sc{socks} server; it is 5 by default.
./SOME/emacs/misc/url.texi:@c @sc{ip} addresses which specify a range of @sc{ip} addresses, an @sc{ip}
./SOME/emacs/misc/url.texi:@c address and a netmask, a domain name or a unique hostname or @sc{ip}
./SOME/emacs/misc/mh-e.texi:MH has the ability to display @dfn{@sc{mime}} (Multipurpose Internet
./SOME/emacs/misc/mh-e.texi:the MH book.} from the shell to read @sc{mime} messages@footnote{You
./SOME/emacs/misc/mh-e.texi:be on. Otherwise, you'll see the @sc{mime} body parts rather than text
./SOME/emacs/misc/mh-e.texi:text (including @sc{html}) and images.
./SOME/emacs/misc/mh-e.texi:in the MH book.} is compiled with the @sc{berk} option (which many
./SOME/emacs/misc/mh-e.texi:Compose @sc{mime} message from MH-style directives
./SOME/emacs/misc/mh-e.texi:Compose @sc{mime} message from MML tags (@code{mh-mml-to-mime}).
./SOME/emacs/misc/mh-e.texi:Type of @sc{mime} message tags in messages (default: @samp{MML} if
./SOME/emacs/misc/mh-e.texi:@sc{mime} (Multipurpose Internet Mail Extensions)
./SOME/emacs/misc/mh-e.texi:protocol@footnote{@sc{mime} is defined in
./SOME/emacs/misc/mh-e.texi:@sc{mime} protocol allows you to incorporate images, sound, video,
./SOME/emacs/misc/mh-e.texi:In addition to MH-style directives, MH-E also supports MML (@sc{mime}
./SOME/emacs/misc/mh-e.texi:The MH-E @sc{mime} commands require a @dfn{media type} for each body
./SOME/emacs/misc/mh-e.texi:You can also create your own @sc{mime} body parts. In the following
./SOME/emacs/misc/mh-e.texi:Mail may be forwarded with @sc{mime} using the command @kbd{C-c C-m
./SOME/emacs/misc/mh-e.texi:When you are finished editing a @sc{mime} message, it might look like this:
./SOME/emacs/misc/mh-e.texi:@i{MH-E @sc{mime} draft}
./SOME/emacs/misc/mh-e.texi:However, you may take a sneak preview of the @sc{mime} encoding if you
./SOME/emacs/misc/mh-e.texi:The following screen shows the @sc{mime} encoding specified by the
./SOME/emacs/misc/mh-e.texi:@i{MH-E @sc{mime} draft ready to send}
./SOME/emacs/misc/mh-e.texi:collection and support for composing @sc{mime} messages. (Reading
./SOME/emacs/misc/mh-e.texi:@sc{mime} messages remains to be done, alas.) While writing this book,
./SOME/emacs/misc/ChangeLog.1: * widget.texi, woman.texi: Replace @sc{ascii} and ASCII with
./SOME/emacs/doc/emacs/text.texi:The curved single quote characters are U+2018 @sc{left single quotation
./SOME/emacs/doc/emacs/text.texi:mark} and U+2019 @sc{right single quotation mark}; the curved double quotes
./SOME/emacs/doc/emacs/text.texi:are U+201C @sc{left double quotation mark} and U+201D @sc{right double
./SOME/emacs/doc/emacs/mule.texi:The special character @code{RIGHT-TO-LEFT MARK}, or @sc{rlm}, forces
./SOME/emacs/doc/emacs/mule.texi:@code{LEFT-TO-RIGHT MARK}, or @sc{lrm} forces the left-to-right
./SOME/emacs/doc/emacs/mule.texi:In a GUI session, the @sc{lrm} and @sc{rlm} characters display as very
./SOME/emacs/doc/emacs/msdos.texi:come with such a program, although several ports of @sc{gnu} @code{ls}
./SOME/emacs/doc/emacs/msdos.texi:Emulate @sc{gnu} systems; this is the default. This sets
./SOME/emacs/doc/emacs/msdos.texi:platforms prefer the @sc{gnu} defaults.
./SOME/emacs/doc/emacs/msdos.texi:displaying a given non-@sc{ascii} character might fail for some rare
./SOME/emacs/doc/emacs/search.texi:such as U+249C @sc{parenthesized latin small letter a} and U+2100
./SOME/emacs/doc/emacs/search.texi:@sc{account of} (which looks like a small @code{a} over @code{c}).
./SOME/emacs/doc/emacs/search.texi:@sc{latin small ligature ff}. Character sequences that are not identical,
./SOME/emacs/doc/emacs/basic.texi:which is Unicode code-point U+2018 @sc{left single quotation mark},
./SOME/emacs/doc/misc/emacs-mime.texi:* Charset Translation:: How charsets are mapped from @sc{mule} to @acronym{MIME}.
./SOME/emacs/doc/misc/emacs-mime.texi:If you are running a non-@sc{mule} Emacs, this process is simple: If the
./SOME/emacs/doc/misc/emacs-mime.texi:Things are slightly more complicated when running Emacs with @sc{mule}
./SOME/emacs/doc/misc/emacs-mime.texi:support. In this case, a list of the @sc{mule} charsets used in the
./SOME/emacs/doc/misc/emacs-mime.texi:part is obtained, and the @sc{mule} charsets are translated to
./SOME/emacs/doc/misc/emacs-mime.texi:When running Emacs with @sc{mule} support, the preferences for which
./SOME/emacs/doc/misc/org.texi:Richard @@@@texinfo:@@sc@{@@@@Stallman@@@@texinfo:@}@@@@ commence' GNU.
./SOME/emacs/doc/misc/cl.texi:form is a regular Lisp variable. But the @sc{car}s and @sc{cdr}s of lists,
./SOME/emacs/doc/misc/cl.texi:It searches for an element of the list whose @sc{car} equals
./SOME/emacs/doc/misc/cl.texi:then on the @sc{cdr}s of those lists, and so on, until the
./SOME/emacs/doc/misc/cl.texi:@sc{car}s of the advancing pointers.
./SOME/emacs/doc/misc/cl.texi:rearranging the @sc{cdr} pointers in suitable fashion.
./SOME/emacs/doc/misc/cl.texi:list (where the @sc{cdr}-chain forms a loop rather than terminating
./SOME/emacs/doc/misc/cl.texi:argument becomes the @sc{cdr} of the last cell constructed.
./SOME/emacs/doc/misc/cl.texi:@var{y} are both cons cells, their @sc{car}s and @sc{cdr}s are
./SOME/emacs/doc/misc/cl.texi:on, and compares against @var{old}, both @sc{car}s and @sc{cdr}s
./SOME/emacs/doc/misc/cl.texi:function, if any), is compared with the @sc{car}s of
./SOME/emacs/doc/misc/cl.texi:@sc{cdr}.
./SOME/emacs/doc/misc/cl.texi:If a match is found, it returns the cons cell whose @sc{car} was
./SOME/emacs/doc/misc/cl.texi:any of its @sc{cdr}s.
./SOME/emacs/doc/misc/cl.texi:element whose @sc{car} matches (in the sense of @code{:test},
./SOME/emacs/doc/misc/cl.texi:This function searches for an element whose @sc{cdr} matches
./SOME/emacs/doc/misc/widget.texi:A list whose @sc{car} is the widget representing the currently chosen
./SOME/emacs/doc/misc/widget.texi:List whose @sc{car} is the type of the list elements.
./SOME/emacs/doc/misc/widget.texi:The value of a @code{cons} widget must be a cons-cell whose @sc{car}
./SOME/emacs/doc/misc/widget.texi:and @sc{cdr} have two specified types. It uses this syntax:
./SOME/emacs/doc/misc/widget.texi:and @kbd{C-o} (suggested by @sc{rms}).
./SOME/emacs/doc/misc/widget.texi:whether you want to add or delete an item (@sc{rms} wanted to git rid of
./SOME/emacs/doc/misc/sieve.texi:for talking to a server with the @sc{managesieve} protocol.
./SOME/emacs/doc/misc/ede.texi:@scindex ede-sourcecode
./SOME/emacs/doc/misc/message.texi:Each list element should be a cons, where the @sc{car} should be the
./SOME/emacs/doc/misc/message.texi:name of a header (e.g., @code{CC}) and the @sc{cdr} should be the header
./SOME/emacs/doc/misc/message.texi:In addition, you can enter conses into this list. The @sc{car} of this cons
./SOME/emacs/doc/misc/message.texi:the @sc{cdr} can either be a string to be entered verbatim as the value of
./SOME/emacs/doc/misc/message.texi:If the list contains a cons where the @sc{car} of the cons is
./SOME/emacs/doc/misc/message.texi:@code{optional}, the @sc{cdr} of this cons will only be inserted if it is
./SOME/emacs/doc/misc/message.texi:is @code{iso-8859-1} on non-@sc{mule} Emacsen; otherwise @code{nil},
./SOME/emacs/doc/misc/message.texi:which means ask the user. (This variable is used only on non-@sc{mule}
./SOME/emacs/doc/misc/message.texi:Emacs MIME Manual}, for details on the @sc{mule}-to-@acronym{MIME}
./SOME/emacs/doc/misc/message.texi:@sc{car} is a function and the @sc{cdr} is the list of arguments, or
./SOME/emacs/doc/misc/autotype.texi:@code{auto-insert-alist}. The @sc{car}s of this list are each either
./SOME/emacs/doc/misc/autotype.texi:the same mode in Emacs can be distinguished. The @sc{car}s may also
./SOME/emacs/doc/misc/autotype.texi: When a matching element is found, the @sc{cdr} says what to do. It may
./SOME/emacs/doc/misc/trampver.texi:@set tramp @sc{Tramp}
./SOME/emacs/doc/misc/viper.texi:dm@@scs.cs.nyu.edu (David Mazieres),
./SOME/emacs/doc/misc/sasl.texi:@sc{sasl} is short for @dfn{Simple Authentication and Security Layer}.
./SOME/emacs/doc/misc/sasl.texi:The toplevel interface of this library is inspired by Java @sc{sasl}
./SOME/emacs/doc/misc/sasl.texi:A mechanism (@code{sasl-mechanism} object) is a schema of the @sc{sasl}
./SOME/emacs/doc/misc/reftex.texi:@c dominik@@science.uva.nl
./SOME/emacs/doc/misc/dbus.texi:A D-Bus compound type is always represented as a list. The @sc{car}
./SOME/emacs/doc/misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./SOME/emacs/doc/misc/gnus.texi:Things got a bit more complicated with @sc{gnus}. In addition to
./SOME/emacs/doc/misc/gnus.texi:the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
./SOME/emacs/doc/misc/gnus.texi:@sc{gnus} and other newsreaders.
./SOME/emacs/doc/misc/gnus.texi:@sc{gnus 4.1}, where you had explicit keystrokes for everything under
./SOME/emacs/doc/misc/gnus.texi:correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
./SOME/emacs/doc/misc/gnus.texi:even with @sc{xover} by registering the @code{Xref} lines of all
./SOME/emacs/doc/misc/gnus.texi:@cindex @sc{mode reader}
./SOME/emacs/doc/misc/gnus.texi:not easy. People who prefer proper mail readers should try @sc{vm}
./SOME/emacs/doc/misc/gnus.texi:where the @sc{car} of a cell contains the key, and the @sc{cdr}
./SOME/emacs/doc/misc/gnus.texi:Two summary functions for editing a @sc{gnus} kill file:
./SOME/emacs/doc/misc/gnus.texi:@sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
./SOME/emacs/doc/misc/gnus.texi:pronounced ``news'' as @sc{Umeda} intended, which makes it a more
./SOME/emacs/doc/misc/gnus.texi:``@sc{gnus}''. New vs. old.
./SOME/emacs/doc/misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./SOME/emacs/doc/misc/gnus.texi:reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
./SOME/emacs/doc/misc/gnus.texi:Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
./SOME/emacs/doc/misc/gnus.texi:All code that relies on knowledge of @sc{gnus} internals will probably
./SOME/emacs/doc/misc/gnus.texi:fact, you should probably remove all old @sc{gnus} packages (and other
./SOME/emacs/doc/misc/gnus.texi:does what you have written code to make @sc{gnus} do. (Snicker.)
./SOME/emacs/doc/misc/gnus.texi:Gnus understands all @sc{gnus} startup files.
./SOME/emacs/doc/misc/gnus.texi:@sc{gnus} internals should suffer no problems. If problems occur,
./SOME/emacs/doc/misc/gnus.texi:Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
./SOME/emacs/doc/misc/gnus.texi:Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
./SOME/emacs/doc/misc/gnus.texi:of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
./SOME/emacs/doc/misc/gnus.texi:controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
./SOME/emacs/doc/misc/gnus.texi:normal @sc{head} format.
./SOME/emacs/doc/misc/gnus.texi:been running @sc{gnus}, you need to exit Emacs and start it up again before
./SOME/emacs/doc/misc/gnus.texi:@sc{gnus} introduced a concept that I found so useful that I've started
./SOME/emacs/doc/misc/url.texi:@cindex @sc{socks}
./SOME/emacs/doc/misc/url.texi:Use if the firewall has a @sc{socks} gateway running on it. The
./SOME/emacs/doc/misc/url.texi:@sc{socks} v5 protocol is defined in RFC 1928.
./SOME/emacs/doc/misc/url.texi:the @sc{socks} server.
./SOME/emacs/doc/misc/url.texi:@sc{socks} server. By default this is your login name.
./SOME/emacs/doc/misc/url.texi:@sc{socks} server; it is 5 by default.
./SOME/emacs/doc/misc/url.texi:@c @sc{ip} addresses which specify a range of @sc{ip} addresses, an @sc{ip}
./SOME/emacs/doc/misc/url.texi:@c address and a netmask, a domain name or a unique hostname or @sc{ip}
./SOME/emacs/doc/misc/mh-e.texi:MH has the ability to display @dfn{@sc{mime}} (Multipurpose Internet
./SOME/emacs/doc/misc/mh-e.texi:the MH book.} from the shell to read @sc{mime} messages@footnote{You
./SOME/emacs/doc/misc/mh-e.texi:be on. Otherwise, you'll see the @sc{mime} body parts rather than text
./SOME/emacs/doc/misc/mh-e.texi:text (including @sc{html}) and images.
./SOME/emacs/doc/misc/mh-e.texi:in the MH book.} is compiled with the @sc{berk} option (which many
./SOME/emacs/doc/misc/mh-e.texi:Compose @sc{mime} message from MH-style directives
./SOME/emacs/doc/misc/mh-e.texi:Compose @sc{mime} message from MML tags (@code{mh-mml-to-mime}).
./SOME/emacs/doc/misc/mh-e.texi:Type of @sc{mime} message tags in messages (default: @samp{MML} if
./SOME/emacs/doc/misc/mh-e.texi:@sc{mime} (Multipurpose Internet Mail Extensions)
./SOME/emacs/doc/misc/mh-e.texi:protocol@footnote{@sc{mime} is defined in
./SOME/emacs/doc/misc/mh-e.texi:@sc{mime} protocol allows you to incorporate images, sound, video,
./SOME/emacs/doc/misc/mh-e.texi:In addition to MH-style directives, MH-E also supports MML (@sc{mime}
./SOME/emacs/doc/misc/mh-e.texi:The MH-E @sc{mime} commands require a @dfn{media type} for each body
./SOME/emacs/doc/misc/mh-e.texi:You can also create your own @sc{mime} body parts. In the following
./SOME/emacs/doc/misc/mh-e.texi:Mail may be forwarded with @sc{mime} using the command @kbd{C-c C-m
./SOME/emacs/doc/misc/mh-e.texi:When you are finished editing a @sc{mime} message, it might look like this:
./SOME/emacs/doc/misc/mh-e.texi:@i{MH-E @sc{mime} draft}
./SOME/emacs/doc/misc/mh-e.texi:However, you may take a sneak preview of the @sc{mime} encoding if you
./SOME/emacs/doc/misc/mh-e.texi:The following screen shows the @sc{mime} encoding specified by the
./SOME/emacs/doc/misc/mh-e.texi:@i{MH-E @sc{mime} draft ready to send}
./SOME/emacs/doc/misc/mh-e.texi:collection and support for composing @sc{mime} messages. (Reading
./SOME/emacs/doc/misc/mh-e.texi:@sc{mime} messages remains to be done, alas.) While writing this book,
./SOME/emacs/doc/misc/ChangeLog.1: * widget.texi, woman.texi: Replace @sc{ascii} and ASCII with
./SOME/emacs/doc/lispref/objects.texi:the @sc{car} slot and the @sc{cdr} slot. Each slot can @dfn{hold} any
./SOME/emacs/doc/lispref/objects.texi:Lisp object. We also say that the @sc{car} of this cons cell is
./SOME/emacs/doc/lispref/objects.texi:whatever object its @sc{car} slot currently holds, and likewise for
./SOME/emacs/doc/lispref/objects.texi:the @sc{cdr}.
./SOME/emacs/doc/lispref/objects.texi:@sc{cdr} slot of each cons cell holds either the next cons cell or the
./SOME/emacs/doc/lispref/objects.texi:@sc{car} slot of the cons cell holds the element, and its @sc{cdr}
./SOME/emacs/doc/lispref/objects.texi:element in the list. The @sc{cdr} slot of the last cons cell is set to
./SOME/emacs/doc/lispref/objects.texi: The names @sc{car} and @sc{cdr} derive from the history of Lisp. The
./SOME/emacs/doc/lispref/objects.texi:decrement; @sc{car} was an instruction to extract the contents of
./SOME/emacs/doc/lispref/objects.texi:the address part of a register, and @sc{cdr} an instruction to extract
./SOME/emacs/doc/lispref/objects.texi: In this example, the first box, which holds the @sc{car} of the first
./SOME/emacs/doc/lispref/objects.texi:box, holding the @sc{cdr} of the first cons cell, refers to the next
./SOME/emacs/doc/lispref/objects.texi:pair of boxes, the second cons cell. The @sc{car} of the second cons
./SOME/emacs/doc/lispref/objects.texi:cell is @code{violet}, and its @sc{cdr} is the third cons cell. The
./SOME/emacs/doc/lispref/objects.texi:@sc{cdr} of the third (and last) cons cell is @code{nil}.
./SOME/emacs/doc/lispref/objects.texi:represents the @sc{car} and @sc{cdr} explicitly. In this syntax,
./SOME/emacs/doc/lispref/objects.texi:@code{(@var{a} .@: @var{b})} stands for a cons cell whose @sc{car} is
./SOME/emacs/doc/lispref/objects.texi:the object @var{a} and whose @sc{cdr} is the object @var{b}. Dotted
./SOME/emacs/doc/lispref/objects.texi:pair notation is more general than list syntax because the @sc{cdr}
./SOME/emacs/doc/lispref/objects.texi:list, the dotted pair notation is only used if the @sc{cdr} of a cons
./SOME/emacs/doc/lispref/objects.texi:conveniently a chain of cons cells with a non-@code{nil} final @sc{cdr}.
./SOME/emacs/doc/lispref/objects.texi:@sc{cdr} of the final cons cell. For example, @code{(rose violet
./SOME/emacs/doc/lispref/objects.texi:@code{buttercup} in the @sc{cdr} of a cons cell whose @sc{cdr} is already
./SOME/emacs/doc/lispref/objects.texi:list whose elements are cons cells. In each element, the @sc{car} is
./SOME/emacs/doc/lispref/objects.texi:considered a @dfn{key}, and the @sc{cdr} is considered an
./SOME/emacs/doc/lispref/objects.texi:in the @sc{car} of the @sc{cdr}.) Association lists are often used as
./SOME/emacs/doc/lispref/objects.texi:list whose first element is the symbol @code{macro} and whose @sc{cdr}
./SOME/emacs/doc/lispref/objects.texi:primitive type---it is actually a list whose @sc{car} is
./SOME/emacs/doc/lispref/objects.texi:@code{frame-configuration} and whose @sc{cdr} is an alist. Each alist
./SOME/emacs/doc/lispref/objects.texi:element describes one frame, which appears as the @sc{car} of that
./SOME/emacs/doc/lispref/objects.texi:a list whose @sc{car} is the symbol @code{keymap}.
./SOME/emacs/doc/lispref/text.texi:kill ring list, whose @sc{car} is the text to yank next. We say it
./SOME/emacs/doc/lispref/text.texi:@sc{car} of that link. Kill commands, which change the kill ring, also
./SOME/emacs/doc/lispref/text.texi:of the value of @code{kill-ring}, and its @sc{car} is the kill string
./SOME/emacs/doc/lispref/text.texi:Its value is a cons cell whose @sc{car} is the property value, the
./SOME/emacs/doc/lispref/text.texi:arguments. Its @sc{cdr} is the overlay in which the property was
./SOME/emacs/doc/lispref/text.texi:If @var{position} is at the end of @var{object}, both the @sc{car} and
./SOME/emacs/doc/lispref/text.texi:the @sc{cdr} of the value are @code{nil}.
./SOME/emacs/doc/lispref/debugging.texi:@sc{car} of the evaluated list, or a @code{lambda} expression in the
./SOME/emacs/doc/lispref/nonascii.texi:this property for the character U+2155 @sc{vulgar fraction one
./SOME/emacs/doc/lispref/nonascii.texi:example mapping for U+00DF @sc{latin small letter sharp s} is
./SOME/emacs/doc/lispref/nonascii.texi:be empty). For example mapping for U+0130 @sc{latin capital letter i
./SOME/emacs/doc/lispref/nonascii.texi:consisting of @sc{latin small letter i} followed by U+0307
./SOME/emacs/doc/lispref/nonascii.texi:@sc{combining dot above}). For characters with no special mapping,
./SOME/emacs/doc/lispref/nonascii.texi:U+FB01 @sc{latin small ligature fi} the value is @code{"Fi"}. For
./SOME/emacs/doc/lispref/nonascii.texi:The @sc{cdr} of the element, @var{coding}, should be either a coding
./SOME/emacs/doc/lispref/nonascii.texi:@var{coding} is a cons cell containing two coding systems, its @sc{car}
./SOME/emacs/doc/lispref/nonascii.texi:specifies the coding system for decoding, and its @sc{cdr} specifies the
./SOME/emacs/doc/lispref/backups.texi:deletion. @code{find-backup-file-name} returns a list whose @sc{car} is
./SOME/emacs/doc/lispref/backups.texi:the name for the new backup file and whose @sc{cdr} is a list of backup
./SOME/emacs/doc/lispref/backups.texi:those versions by excluding them from the @sc{cdr} of the value.
./SOME/emacs/doc/lispref/functions.texi:as its @sc{car} to make local variables and give them values. In the
./SOME/emacs/doc/lispref/functions.texi: ;; @r{apply function to @sc{car}s.}
./SOME/emacs/doc/lispref/functions.texi:forms self-quoting: evaluating a form whose @sc{car} is @code{lambda}
./SOME/emacs/doc/lispref/keymaps.texi: Each keymap is a list whose @sc{car} is the symbol @code{keymap}. The
./SOME/emacs/doc/lispref/keymaps.texi:@sc{car} is @code{keymap}, or for a symbol whose function definition
./SOME/emacs/doc/lispref/keymaps.texi:@sc{cdr} of the element; a list with the map as the second element will
./SOME/emacs/doc/lispref/keymaps.texi:not do. The @sc{cdr} can be either a keymap (a list) or a symbol whose
./SOME/emacs/doc/lispref/keymaps.texi:If the @sc{car} of @var{list} is the symbol @code{keymap}, then the list
./SOME/emacs/doc/lispref/keymaps.texi:If the @sc{car} of @var{list} is @code{lambda}, then the list is a
./SOME/emacs/doc/lispref/keymaps.texi:The @sc{car}, @var{item-string}, is the string to be displayed in the
./SOME/emacs/doc/lispref/keymaps.texi:The @sc{car}, @var{type}, says which: it should be @code{:toggle} or
./SOME/emacs/doc/lispref/keymaps.texi:@code{:radio}. The @sc{cdr}, @var{selected}, should be a form; the
./SOME/emacs/doc/lispref/windows.texi:specifies the number of rectangles to return and whose @sc{cdr}, if
./SOME/emacs/doc/lispref/windows.texi:whose @sc{car} specifies the uppermost and whose @sc{cdr} specifies the
./SOME/emacs/doc/lispref/windows.texi:The @sc{car} of each entry of this alist is a symbol specifying the
./SOME/emacs/doc/lispref/windows.texi:parameter. The @sc{cdr} should be one of the following:
./SOME/emacs/doc/lispref/windows.texi:The value of this parameter is a cons cell whose @sc{car} and
./SOME/emacs/doc/lispref/windows.texi:@sc{cdr}, if non-@code{nil}, specify the minimum values (in columns)
./SOME/emacs/doc/lispref/lists.texi:slot is known as the @sc{car}, and the other is known as the @sc{cdr}.
./SOME/emacs/doc/lispref/lists.texi:(These names are traditional; see @ref{Cons Cell Type}.) @sc{cdr} is
./SOME/emacs/doc/lispref/lists.texi: We say that ``the @sc{car} of this cons cell is'' whatever object
./SOME/emacs/doc/lispref/lists.texi:its @sc{car} slot currently holds, and likewise for the @sc{cdr}.
./SOME/emacs/doc/lispref/lists.texi:of the list. By convention, the @sc{car}s of the cons cells hold the
./SOME/emacs/doc/lispref/lists.texi:elements of the list, and the @sc{cdr}s are used to chain the list
./SOME/emacs/doc/lispref/lists.texi:(this asymmetry between @sc{car} and @sc{cdr} is entirely a matter of
./SOME/emacs/doc/lispref/lists.texi:convention; at the level of cons cells, the @sc{car} and @sc{cdr}
./SOME/emacs/doc/lispref/lists.texi:slots have similar properties). Hence, the @sc{cdr} slot of each cons
./SOME/emacs/doc/lispref/lists.texi: Also by convention, the @sc{cdr} of the last cons cell in a list is
./SOME/emacs/doc/lispref/lists.texi:considered to have @code{nil} as its @sc{cdr} (and also as its
./SOME/emacs/doc/lispref/lists.texi:@sc{car}).
./SOME/emacs/doc/lispref/lists.texi: Hence, the @sc{cdr} of a proper list is always a proper list. The
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr} of a nonempty proper list is a proper list containing all the
./SOME/emacs/doc/lispref/lists.texi: If the @sc{cdr} of a list's last cons cell is some value other than
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr} could point to one of the previous cons cells in the list.
./SOME/emacs/doc/lispref/lists.texi:list to see the @sc{cdr} of the final cons cell, it won't care.
./SOME/emacs/doc/lispref/lists.texi:cons cell @var{cons-cell}. In other words, it returns the @sc{car} of
./SOME/emacs/doc/lispref/lists.texi:cons cell @var{cons-cell}. In other words, it returns the @sc{cdr} of
./SOME/emacs/doc/lispref/lists.texi:This function lets you take the @sc{car} of a cons cell while avoiding
./SOME/emacs/doc/lispref/lists.texi:errors for other data types. It returns the @sc{car} of @var{object} if
./SOME/emacs/doc/lispref/lists.texi:This function lets you take the @sc{cdr} of a cons cell while
./SOME/emacs/doc/lispref/lists.texi:avoiding errors for other data types. It returns the @sc{cdr} of
./SOME/emacs/doc/lispref/lists.texi:This macro provides a convenient way to examine the @sc{car} of a
./SOME/emacs/doc/lispref/lists.texi:saves the @sc{cdr} into @var{listname}, then returns the removed
./SOME/emacs/doc/lispref/lists.texi:are numbered starting with zero, so the @sc{car} of @var{list} is
./SOME/emacs/doc/lispref/lists.texi:This function returns the @var{n}th @sc{cdr} of @var{list}. In other
./SOME/emacs/doc/lispref/lists.texi:@sc{car}, and @var{object2} the @sc{cdr}. It then returns the new
./SOME/emacs/doc/lispref/lists.texi:by following all the @sc{cdr}s and then replacing the terminating
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr} of the last cons cell in the new list. If the final argument
./SOME/emacs/doc/lispref/lists.texi:dotted list since its final @sc{cdr} is not @code{nil} as required
./SOME/emacs/doc/lispref/lists.texi:resulting list. Instead, the sequence becomes the final @sc{cdr}, like
./SOME/emacs/doc/lispref/lists.texi:cons cell, this makes a new cons cell with the same @sc{car} and
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr}, then recursively copies the @sc{car} and @sc{cdr} in the
./SOME/emacs/doc/lispref/lists.texi:This macro creates a new list whose @sc{car} is @var{element} and
./SOME/emacs/doc/lispref/lists.texi:whose @sc{cdr} is the list specified by @var{listname}, and saves that
./SOME/emacs/doc/lispref/lists.texi: You can modify the @sc{car} and @sc{cdr} contents of a cons cell with the
./SOME/emacs/doc/lispref/lists.texi:new @sc{car} or @sc{cdr}.
./SOME/emacs/doc/lispref/lists.texi: Changing the @sc{car} of a cons cell is done with @code{setcar}. When
./SOME/emacs/doc/lispref/lists.texi:This function stores @var{object} as the new @sc{car} of @var{cons},
./SOME/emacs/doc/lispref/lists.texi:replacing its previous @sc{car}. In other words, it changes the
./SOME/emacs/doc/lispref/lists.texi:@sc{car} slot of @var{cons} to refer to @var{object}. It returns the
./SOME/emacs/doc/lispref/lists.texi:storing a new @sc{car} into the cons changes one element of each of
./SOME/emacs/doc/lispref/lists.texi:;; @r{Replace the @sc{car} of a shared link.}
./SOME/emacs/doc/lispref/lists.texi:;; @r{Replace the @sc{car} of a link that is not shared.}
./SOME/emacs/doc/lispref/lists.texi: The lowest-level primitive for modifying a @sc{cdr} is @code{setcdr}:
./SOME/emacs/doc/lispref/lists.texi:This function stores @var{object} as the new @sc{cdr} of @var{cons},
./SOME/emacs/doc/lispref/lists.texi:replacing its previous @sc{cdr}. In other words, it changes the
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr} slot of @var{cons} to refer to @var{object}. It returns the
./SOME/emacs/doc/lispref/lists.texi: Here is an example of replacing the @sc{cdr} of a list with a
./SOME/emacs/doc/lispref/lists.texi:unchanged, because it resides in the @sc{car} of the list, and is not
./SOME/emacs/doc/lispref/lists.texi:reached via the @sc{cdr}.
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr}s of the cons cells in the list. For example, here we delete
./SOME/emacs/doc/lispref/lists.texi:the @sc{cdr} of the first cons cell:
./SOME/emacs/doc/lispref/lists.texi:exists and its @sc{car} is still @code{b}, but it no longer forms part
./SOME/emacs/doc/lispref/lists.texi: It is equally easy to insert a new element by changing @sc{cdr}s:
./SOME/emacs/doc/lispref/lists.texi:modifying the @sc{cdr}s of their component cons cells. These functions
./SOME/emacs/doc/lispref/lists.texi:@emph{not} copied. Instead, the last @sc{cdr} of each of the
./SOME/emacs/doc/lispref/lists.texi:removing it involves changing the @sc{cdr}s (@pxref{Setcdr}).
./SOME/emacs/doc/lispref/lists.texi:@dfn{associations}: the @sc{car} of each cons cell is the @dfn{key}, and the
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr} is the @dfn{associated value}.@footnote{This usage of ``key''
./SOME/emacs/doc/lispref/lists.texi:associated with the @emph{list} @code{(2 3)}, which is the @sc{cdr} of
./SOME/emacs/doc/lispref/lists.texi:value in the @sc{car} of the @sc{cdr} of the element. Here is an
./SOME/emacs/doc/lispref/lists.texi:information---even a list of other items---in the @sc{cdr} of the
./SOME/emacs/doc/lispref/lists.texi:@sc{cdr}. One disadvantage is that you cannot use @code{rassq} (see
./SOME/emacs/doc/lispref/lists.texi:associated value in the @sc{cdr} of the element; the value associated
./SOME/emacs/doc/lispref/lists.texi:association in @var{alist} has a @sc{car} equal to @var{key}. For
./SOME/emacs/doc/lispref/lists.texi:a @sc{cdr} @code{equal} to @var{value}.
./SOME/emacs/doc/lispref/lists.texi:@code{rassoc} is like @code{assoc} except that it compares the @sc{cdr} of
./SOME/emacs/doc/lispref/lists.texi:each @var{alist} association instead of the @sc{car}. You can think of
./SOME/emacs/doc/lispref/lists.texi:@var{alist} has a @sc{car} @code{eq} to @var{key}. This function is
./SOME/emacs/doc/lispref/lists.texi:a @sc{cdr} @code{eq} to @var{value}.
./SOME/emacs/doc/lispref/lists.texi:@code{rassq} is like @code{assq} except that it compares the @sc{cdr} of
./SOME/emacs/doc/lispref/lists.texi:each @var{alist} association instead of the @sc{car}. You can think of
./SOME/emacs/doc/lispref/lists.texi:@code{rassq} cannot search for a value stored in the @sc{car}
./SOME/emacs/doc/lispref/lists.texi:of the @sc{cdr} of an element:
./SOME/emacs/doc/lispref/lists.texi:In this case, the @sc{cdr} of the association @code{(lily white)} is not
./SOME/emacs/doc/lispref/lists.texi:the element's @sc{car} (if it is a cons) against @var{key}, by calling
./SOME/emacs/doc/lispref/lists.texi:@var{test} with two arguments: the element or its @sc{car}, and
./SOME/emacs/doc/lispref/lists.texi:If the element is a cons, then the value is the element's @sc{cdr}.
./SOME/emacs/doc/lispref/lists.texi:This function deletes from @var{alist} all the elements whose @sc{car}
./SOME/emacs/doc/lispref/lists.texi:This function deletes from @var{alist} all the elements whose @sc{cdr}
./SOME/emacs/doc/lispref/lists.texi:compares the @sc{cdr} of each @var{alist} association instead of the
./SOME/emacs/doc/lispref/lists.texi:@sc{car}.
./SOME/emacs/doc/lispref/files.texi:@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
./SOME/emacs/doc/lispref/files.texi:@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
./SOME/emacs/doc/lispref/files.texi:@sc{gnu} @code{Coreutils} Manual}, for a description of file mode
./SOME/emacs/doc/lispref/control.texi:@var{clause} in the @code{cond} must be a list. The @sc{car} of this
./SOME/emacs/doc/lispref/control.texi:@sc{car} of an integer or move forward a character at the end of the
./SOME/emacs/doc/lispref/control.texi:error message is the @sc{car} of @var{data} (that must be a string).
./SOME/emacs/doc/lispref/loading.texi:libraries that are preloaded at startup). It is a list whose @sc{car}
./SOME/emacs/doc/lispref/loading.texi:The value of @code{load-history} may have one element whose @sc{car} is
./SOME/emacs/doc/lispref/sequences.texi:cons cells forming @var{sequence} by changing @sc{cdr}s. A nondestructive
./SOME/emacs/doc/lispref/sequences.texi:Sorting does not change the @sc{car}s of the cons cells in @var{sequence};
./SOME/emacs/doc/lispref/sequences.texi:@var{sequence} still has @code{a} in its @sc{car} after sorting, but it now
./SOME/emacs/doc/lispref/sequences.texi:@sc{cdr}s. For example:
./SOME/emacs/doc/lispref/edebug.texi:argument may then be a dotted list. Alternatively, the last @sc{cdr} of a
./SOME/emacs/doc/lispref/commands.texi:@sc{ascii} control characters such as @kbd{C-a} have special basic
./SOME/emacs/doc/lispref/commands.texi:as lists. The @sc{car} of the list is the event type; this says which
./SOME/emacs/doc/lispref/commands.texi:events that are lists, the event type is the symbol in the @sc{car} of
./SOME/emacs/doc/lispref/commands.texi:if it is a list, the @sc{car} of that list (which should be a number) is
./SOME/emacs/doc/lispref/macros.texi: A Lisp macro object is a list whose @sc{car} is @code{macro}, and
./SOME/emacs/doc/lispref/macros.texi:whose @sc{cdr} is a function. Expansion of the macro works
./SOME/emacs/doc/lispref/macros.texi:(Note that the @sc{cdr} of this list is a lambda expression.) This
./SOME/emacs/doc/lispref/display.texi:non-@code{nil}, the string with the single character @sc{U+2026
./SOME/emacs/doc/lispref/display.texi:additional elements describing the @sc{gsub} and @sc{gpos} features
./SOME/emacs/doc/lispref/display.texi:additional elements describing the @sc{gsub} and @sc{gpos} features
./SOME/emacs/doc/lispref/display.texi:@sc{left-to-right mark}, but excluding characters that have graphic
./SOME/emacs/doc/lispref/display.texi:images, such as U+00AD @sc{soft hyphen}.
./SOME/emacs/doc/lispref/display.texi:their parent buffer is reordered. This is because plain-@sc{ascii}
./SOME/emacs/doc/lispref/display.texi:or overlay string includes non-@sc{ascii} characters, these characters
./SOME/emacs/doc/lispref/display.texi:Append the special character U+200E @sc{left-to-right mark}, or
./SOME/emacs/doc/lispref/display.texi:U+200F @sc{right-to-left mark}, or @acronym{RLM}, instead.) This
./SOME/emacs/doc/lispref/ChangeLog.1: * syntax.texi, text.texi: Replace @sc{foo} with @acronym{FOO}.
./SOME/emacs/doc/lispref/os.texi:The @sc{car}, @var{option}, is a string, the name of a command-line
./SOME/emacs/doc/lispref/os.texi:If it is @code{nil}, then it uses @sc{cbreak} mode. The default
./SOME/emacs/doc/lispref/os.texi:setting is system-dependent. Some systems always use @sc{cbreak} mode
./SOME/emacs/doc/lispref/os.texi:If @var{flow} is non-@code{nil}, then Emacs uses @sc{xon/xoff}
./SOME/emacs/doc/lispref/os.texi:has no effect except in @sc{cbreak} mode.
./SOME/emacs/doc/lispref/os.texi:@code{nil}, Emacs is using @sc{cbreak} mode.
./SOME/emacs/doc/lispref/os.texi:is non-@code{nil} if Emacs uses @sc{xon/xoff} (@kbd{C-q}, @kbd{C-s})
./SOME/emacs/doc/lispref/frames.texi:@sc{car}, the @sc{cdr} of that cell specifies the width of the frame's
./SOME/emacs/doc/lispref/frames.texi:the frame's width ratio is preserved if the @sc{car} of the cell is
./SOME/emacs/doc/lispref/frames.texi:the @sc{car} of the cell is either @code{t} or @code{height-only}. The
./SOME/emacs/doc/lispref/frames.texi:left position ratio is preserved if the @sc{cdr} of the cell is either
./SOME/emacs/doc/lispref/frames.texi:the @sc{cdr} of the cell is either @code{t} or @code{top-only}.
./SOME/emacs/doc/lispref/streams.texi:is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
./SOME/emacs/doc/lispref/streams.texi:@sc{cdr} is the number 5.
./SOME/emacs/doc/lispref/streams.texi:@var{string}. It returns a cons cell whose @sc{car} is that expression,
./SOME/emacs/doc/lispref/streams.texi:and whose @sc{cdr} is an integer giving the position of the next
./SOME/emacs/doc/lispref/minibuf.texi:a string, or a cons cell whose @sc{car} is either a string or a symbol
./SOME/emacs/doc/lispref/minibuf.texi:@var{predicate} is either a string or a cons cell (the @sc{car} of
./SOME/emacs/doc/lispref/minibuf.texi:matched by three of the alist @sc{car}s. All of the matches begin with
./SOME/emacs/doc/lispref/help.texi:symbol in the @sc{car} of the list, inside angle brackets.
./SOME/emacs/doc/lispref/variables.texi:Note that storing new values into the @sc{cdr}s of cons cells in this
./SOME/emacs/doc/lispref/variables.texi:form is a regular Lisp variable. But the @sc{car}s and @sc{cdr}s of
./SOME/emacs/doc/lispref/customize.texi:The value must be a cons cell, its @sc{car} must fit @var{car-type}, and
./SOME/emacs/doc/lispref/customize.texi:its @sc{cdr} must fit @var{cdr-type}. For example, @code{(cons string
./SOME/emacs/doc/lispref/customize.texi:In the customization buffer, the @sc{car} and @sc{cdr} are displayed
./SOME/emacs/doc/lispref/customize.texi:The value must be a list of cons-cells, the @sc{car} of each cell
./SOME/emacs/doc/lispref/customize.texi:@sc{cdr} of the same cell representing a value of customization type
./SOME/emacs/doc/lispref/modes.texi:comment starter. If the entry is a cons cell, the @sc{car} is set
./SOME/emacs/doc/lispref/modes.texi:up as a comment starter and the @sc{cdr} as a comment ender.
./SOME/emacs/doc/lispref/modes.texi:The @sc{car}, @var{characters}, can be either a character or a string.
./SOME/emacs/doc/lispref/modes.texi:expression or a function, as described above. The @sc{cdr},
./SOME/emacs/doc/lispref/modes.texi:The @sc{car}, @var{subexp}, is an integer specifying which subexpression
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:number. The argument used by @samp{%c} must be an @sc{ascii} code
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:number; it will be printed as the character with that @sc{ascii} code.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:The @sc{car} of a list is, quite simply, the first item in the list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:Thus the @sc{car} of the list @code{(rose violet daisy buttercup)} is
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:The @sc{cdr} of a list is the rest of the list, that is, the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:first item. Thus, while the @sc{car} of the list @code{'(rose violet
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:list. However, the @sc{cdr} of the list is a list itself, @code{(fir
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:In this example, the first element or @sc{car} of the list is the list of
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:What it does is take the @sc{cdr} of a list repeatedly.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:If you take the @sc{cdr} of the list @code{(pine fir
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{(oak maple)}. (Of course, repeated @sc{cdr}ing on the original
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:list will just give you the original @sc{cdr} since the function does
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:not change the list. You need to evaluate the @sc{cdr} of the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} and so on.) If you continue this, eventually you will be
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:For review, here is a series of repeated @sc{cdr}s, the text following
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:You can also do several @sc{cdr}s without printing the values in
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{nthcdr} function takes the @sc{cdr} of a list repeatedly.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{nth} function takes the @sc{car} of the result returned by
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:say, the first element of a list, its @sc{car} is the zeroth element.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:functions set the @sc{car} or the @sc{cdr} of a list to a new value.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the first list will be set;
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{(horse cat dog)}. The @sc{cdr} of the list is changed from
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:with the text already in the first element (the @sc{car}) of the kill
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:the @sc{car} of the kill ring. Whether it prepends or appends the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:It sets the @sc{cdr} of a list, just as @code{setcar} sets the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{car} of a list. In this case, however, @code{setcdr} will not be
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:setting the @sc{cdr} of the whole kill ring; the @code{nthcdr}
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:function is used to cause it to set the @sc{cdr} of the next to last
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:element of the kill ring---this means that since the @sc{cdr} of the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{nthcdr} function works by repeatedly taking the @sc{cdr} of a
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:list---it takes the @sc{cdr} of the @sc{cdr} of the @sc{cdr}
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:elements long, we could set the @sc{cdr} of the next to last element
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:birch)}, then set the @sc{cdr} of its second @sc{cdr} to @code{nil}
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:that is what the @sc{cdr} is set to.)
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} a number of times that is one less than the maximum permitted
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:size of the kill ring and @code{setcdr} sets the @sc{cdr} of that
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:Return the result of taking @sc{cdr} @var{n} times on a list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:If a symbol is set to the @sc{cdr} of a list, the list itself is not
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:the jargon, @sc{car} and @sc{cdr} are ``non-destructive''.) Thus,
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:Thus, in Lisp, to get the @sc{cdr} of a list, you just get the address
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:of the next cons cell in the series; to get the @sc{car} of a list,
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{more-flowers}. Set the @sc{car} of @code{flowers} to a fish.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:of the kill ring of which the first element (the @sc{car}) will be
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:expression set the value of the list to be the @sc{cdr} of the list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:can be set to be the @sc{cdr} of the original list with the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{dolist} works like a @code{while} loop that @sc{cdr}s down a
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:loops---takes the @sc{cdr} of the list---and binds the @sc{car} of
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr}s down the list on its own---and it automatically binds
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:the @sc{car} of each shorter version of the list to the first of its
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:In the example, the @sc{car} of each shorter version of the list is
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{dolist} expression binds the @sc{car} of each shorter
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:first element of the list, the @sc{car} of the list. Then the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:list). Then the function calls itself with the @sc{cdr} of the list
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:it is invoked with, which (the second time around) is the @sc{cdr} of
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:the @sc{cdr} of the original list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:evaluates the first element (the @sc{car} or true-or-false-test) of
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list)
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi: @sc{cdr}) of the list,
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi: act on the beginning of the list (the @sc{car} of the list),
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi: and make a recursive call on the rest (the @sc{cdr}) of the list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list),
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:Else, if the beginning of the list (the @sc{car} of the list) passes
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:Otherwise, if the beginning of the list (the @sc{car} of the list) fails
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi: and, recursively call the function on the rest (the @sc{cdr}) of the list.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:technique is to set the value of the list to the value of the @sc{cdr}
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of itself, so eventually the list will be empty; and the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:should not be too hard to write a function that @sc{cdr}s down the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:(cdr numbers-list))} expression, the @sc{car} of each instance of the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:non-@sc{ascii} characters are written within square brackets, without
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:hexadecimal three, and @sc{ascii} Control-C (the third letter of the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:set to be equal to some @sc{cdr} of the kill ring, using the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:works by repeatedly taking the @sc{cdr} of a list---it takes the
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the @sc{cdr} of the @sc{cdr} @dots{}
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:the @code{mod} function to determine which @sc{cdr} to select.
./SOME/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cons} rather than a number or nothing, it puts point at beginning
./SOME/emacs/lispref/objects.texi:the @sc{car} slot and the @sc{cdr} slot. Each slot can @dfn{hold} any
./SOME/emacs/lispref/objects.texi:Lisp object. We also say that the @sc{car} of this cons cell is
./SOME/emacs/lispref/objects.texi:whatever object its @sc{car} slot currently holds, and likewise for
./SOME/emacs/lispref/objects.texi:the @sc{cdr}.
./SOME/emacs/lispref/objects.texi:@sc{cdr} slot of each cons cell holds either the next cons cell or the
./SOME/emacs/lispref/objects.texi:@sc{car} slot of the cons cell holds the element, and its @sc{cdr}
./SOME/emacs/lispref/objects.texi:element in the list. The @sc{cdr} slot of the last cons cell is set to
./SOME/emacs/lispref/objects.texi: The names @sc{car} and @sc{cdr} derive from the history of Lisp. The
./SOME/emacs/lispref/objects.texi:decrement; @sc{car} was an instruction to extract the contents of
./SOME/emacs/lispref/objects.texi:the address part of a register, and @sc{cdr} an instruction to extract
./SOME/emacs/lispref/objects.texi: In this example, the first box, which holds the @sc{car} of the first
./SOME/emacs/lispref/objects.texi:box, holding the @sc{cdr} of the first cons cell, refers to the next
./SOME/emacs/lispref/objects.texi:pair of boxes, the second cons cell. The @sc{car} of the second cons
./SOME/emacs/lispref/objects.texi:cell is @code{violet}, and its @sc{cdr} is the third cons cell. The
./SOME/emacs/lispref/objects.texi:@sc{cdr} of the third (and last) cons cell is @code{nil}.
./SOME/emacs/lispref/objects.texi:represents the @sc{car} and @sc{cdr} explicitly. In this syntax,
./SOME/emacs/lispref/objects.texi:@code{(@var{a} .@: @var{b})} stands for a cons cell whose @sc{car} is
./SOME/emacs/lispref/objects.texi:the object @var{a} and whose @sc{cdr} is the object @var{b}. Dotted
./SOME/emacs/lispref/objects.texi:pair notation is more general than list syntax because the @sc{cdr}
./SOME/emacs/lispref/objects.texi:list, the dotted pair notation is only used if the @sc{cdr} of a cons
./SOME/emacs/lispref/objects.texi:conveniently a chain of cons cells with a non-@code{nil} final @sc{cdr}.
./SOME/emacs/lispref/objects.texi:@sc{cdr} of the final cons cell. For example, @code{(rose violet
./SOME/emacs/lispref/objects.texi:@code{buttercup} in the @sc{cdr} of a cons cell whose @sc{cdr} is already
./SOME/emacs/lispref/objects.texi:list whose elements are cons cells. In each element, the @sc{car} is
./SOME/emacs/lispref/objects.texi:considered a @dfn{key}, and the @sc{cdr} is considered an
./SOME/emacs/lispref/objects.texi:in the @sc{car} of the @sc{cdr}.) Association lists are often used as
./SOME/emacs/lispref/objects.texi:list whose first element is the symbol @code{macro} and whose @sc{cdr}
./SOME/emacs/lispref/objects.texi:primitive type---it is actually a list whose @sc{car} is
./SOME/emacs/lispref/objects.texi:@code{frame-configuration} and whose @sc{cdr} is an alist. Each alist
./SOME/emacs/lispref/objects.texi:element describes one frame, which appears as the @sc{car} of that
./SOME/emacs/lispref/objects.texi:a list whose @sc{car} is the symbol @code{keymap}.
./SOME/emacs/lispref/text.texi:kill ring list, whose @sc{car} is the text to yank next. We say it
./SOME/emacs/lispref/text.texi:@sc{car} of that link. Kill commands, which change the kill ring, also
./SOME/emacs/lispref/text.texi:of the value of @code{kill-ring}, and its @sc{car} is the kill string
./SOME/emacs/lispref/text.texi:Its value is a cons cell whose @sc{car} is the property value, the
./SOME/emacs/lispref/text.texi:arguments. Its @sc{cdr} is the overlay in which the property was
./SOME/emacs/lispref/text.texi:If @var{position} is at the end of @var{object}, both the @sc{car} and
./SOME/emacs/lispref/text.texi:the @sc{cdr} of the value are @code{nil}.
./SOME/emacs/lispref/debugging.texi:@sc{car} of the evaluated list, or a @code{lambda} expression in the
./SOME/emacs/lispref/nonascii.texi:this property for the character U+2155 @sc{vulgar fraction one
./SOME/emacs/lispref/nonascii.texi:example mapping for U+00DF @sc{latin small letter sharp s} is
./SOME/emacs/lispref/nonascii.texi:be empty). For example mapping for U+0130 @sc{latin capital letter i
./SOME/emacs/lispref/nonascii.texi:consisting of @sc{latin small letter i} followed by U+0307
./SOME/emacs/lispref/nonascii.texi:@sc{combining dot above}). For characters with no special mapping,
./SOME/emacs/lispref/nonascii.texi:U+FB01 @sc{latin small ligature fi} the value is @code{"Fi"}. For
./SOME/emacs/lispref/nonascii.texi:The @sc{cdr} of the element, @var{coding}, should be either a coding
./SOME/emacs/lispref/nonascii.texi:@var{coding} is a cons cell containing two coding systems, its @sc{car}
./SOME/emacs/lispref/nonascii.texi:specifies the coding system for decoding, and its @sc{cdr} specifies the
./SOME/emacs/lispref/backups.texi:deletion. @code{find-backup-file-name} returns a list whose @sc{car} is
./SOME/emacs/lispref/backups.texi:the name for the new backup file and whose @sc{cdr} is a list of backup
./SOME/emacs/lispref/backups.texi:those versions by excluding them from the @sc{cdr} of the value.
./SOME/emacs/lispref/functions.texi:as its @sc{car} to make local variables and give them values. In the
./SOME/emacs/lispref/functions.texi: ;; @r{apply function to @sc{car}s.}
./SOME/emacs/lispref/functions.texi:forms self-quoting: evaluating a form whose @sc{car} is @code{lambda}
./SOME/emacs/lispref/keymaps.texi: Each keymap is a list whose @sc{car} is the symbol @code{keymap}. The
./SOME/emacs/lispref/keymaps.texi:@sc{car} is @code{keymap}, or for a symbol whose function definition
./SOME/emacs/lispref/keymaps.texi:@sc{cdr} of the element; a list with the map as the second element will
./SOME/emacs/lispref/keymaps.texi:not do. The @sc{cdr} can be either a keymap (a list) or a symbol whose
./SOME/emacs/lispref/keymaps.texi:If the @sc{car} of @var{list} is the symbol @code{keymap}, then the list
./SOME/emacs/lispref/keymaps.texi:If the @sc{car} of @var{list} is @code{lambda}, then the list is a
./SOME/emacs/lispref/keymaps.texi:The @sc{car}, @var{item-string}, is the string to be displayed in the
./SOME/emacs/lispref/keymaps.texi:The @sc{car}, @var{type}, says which: it should be @code{:toggle} or
./SOME/emacs/lispref/keymaps.texi:@code{:radio}. The @sc{cdr}, @var{selected}, should be a form; the
./SOME/emacs/lispref/windows.texi:specifies the number of rectangles to return and whose @sc{cdr}, if
./SOME/emacs/lispref/windows.texi:whose @sc{car} specifies the uppermost and whose @sc{cdr} specifies the
./SOME/emacs/lispref/windows.texi:The @sc{car} of each entry of this alist is a symbol specifying the
./SOME/emacs/lispref/windows.texi:parameter. The @sc{cdr} should be one of the following:
./SOME/emacs/lispref/windows.texi:The value of this parameter is a cons cell whose @sc{car} and
./SOME/emacs/lispref/windows.texi:@sc{cdr}, if non-@code{nil}, specify the minimum values (in columns)
./SOME/emacs/lispref/lists.texi:slot is known as the @sc{car}, and the other is known as the @sc{cdr}.
./SOME/emacs/lispref/lists.texi:(These names are traditional; see @ref{Cons Cell Type}.) @sc{cdr} is
./SOME/emacs/lispref/lists.texi: We say that ``the @sc{car} of this cons cell is'' whatever object
./SOME/emacs/lispref/lists.texi:its @sc{car} slot currently holds, and likewise for the @sc{cdr}.
./SOME/emacs/lispref/lists.texi:of the list. By convention, the @sc{car}s of the cons cells hold the
./SOME/emacs/lispref/lists.texi:elements of the list, and the @sc{cdr}s are used to chain the list
./SOME/emacs/lispref/lists.texi:(this asymmetry between @sc{car} and @sc{cdr} is entirely a matter of
./SOME/emacs/lispref/lists.texi:convention; at the level of cons cells, the @sc{car} and @sc{cdr}
./SOME/emacs/lispref/lists.texi:slots have similar properties). Hence, the @sc{cdr} slot of each cons
./SOME/emacs/lispref/lists.texi: Also by convention, the @sc{cdr} of the last cons cell in a list is
./SOME/emacs/lispref/lists.texi:considered to have @code{nil} as its @sc{cdr} (and also as its
./SOME/emacs/lispref/lists.texi:@sc{car}).
./SOME/emacs/lispref/lists.texi: Hence, the @sc{cdr} of a proper list is always a proper list. The
./SOME/emacs/lispref/lists.texi:@sc{cdr} of a nonempty proper list is a proper list containing all the
./SOME/emacs/lispref/lists.texi: If the @sc{cdr} of a list's last cons cell is some value other than
./SOME/emacs/lispref/lists.texi:@sc{cdr} could point to one of the previous cons cells in the list.
./SOME/emacs/lispref/lists.texi:list to see the @sc{cdr} of the final cons cell, it won't care.
./SOME/emacs/lispref/lists.texi:cons cell @var{cons-cell}. In other words, it returns the @sc{car} of
./SOME/emacs/lispref/lists.texi:cons cell @var{cons-cell}. In other words, it returns the @sc{cdr} of
./SOME/emacs/lispref/lists.texi:This function lets you take the @sc{car} of a cons cell while avoiding
./SOME/emacs/lispref/lists.texi:errors for other data types. It returns the @sc{car} of @var{object} if
./SOME/emacs/lispref/lists.texi:This function lets you take the @sc{cdr} of a cons cell while
./SOME/emacs/lispref/lists.texi:avoiding errors for other data types. It returns the @sc{cdr} of
./SOME/emacs/lispref/lists.texi:This macro provides a convenient way to examine the @sc{car} of a
./SOME/emacs/lispref/lists.texi:saves the @sc{cdr} into @var{listname}, then returns the removed
./SOME/emacs/lispref/lists.texi:are numbered starting with zero, so the @sc{car} of @var{list} is
./SOME/emacs/lispref/lists.texi:This function returns the @var{n}th @sc{cdr} of @var{list}. In other
./SOME/emacs/lispref/lists.texi:@sc{car}, and @var{object2} the @sc{cdr}. It then returns the new
./SOME/emacs/lispref/lists.texi:by following all the @sc{cdr}s and then replacing the terminating
./SOME/emacs/lispref/lists.texi:@sc{cdr} of the last cons cell in the new list. If the final argument
./SOME/emacs/lispref/lists.texi:dotted list since its final @sc{cdr} is not @code{nil} as required
./SOME/emacs/lispref/lists.texi:resulting list. Instead, the sequence becomes the final @sc{cdr}, like
./SOME/emacs/lispref/lists.texi:cons cell, this makes a new cons cell with the same @sc{car} and
./SOME/emacs/lispref/lists.texi:@sc{cdr}, then recursively copies the @sc{car} and @sc{cdr} in the
./SOME/emacs/lispref/lists.texi:This macro creates a new list whose @sc{car} is @var{element} and
./SOME/emacs/lispref/lists.texi:whose @sc{cdr} is the list specified by @var{listname}, and saves that
./SOME/emacs/lispref/lists.texi: You can modify the @sc{car} and @sc{cdr} contents of a cons cell with the
./SOME/emacs/lispref/lists.texi:new @sc{car} or @sc{cdr}.
./SOME/emacs/lispref/lists.texi: Changing the @sc{car} of a cons cell is done with @code{setcar}. When
./SOME/emacs/lispref/lists.texi:This function stores @var{object} as the new @sc{car} of @var{cons},
./SOME/emacs/lispref/lists.texi:replacing its previous @sc{car}. In other words, it changes the
./SOME/emacs/lispref/lists.texi:@sc{car} slot of @var{cons} to refer to @var{object}. It returns the
./SOME/emacs/lispref/lists.texi:storing a new @sc{car} into the cons changes one element of each of
./SOME/emacs/lispref/lists.texi:;; @r{Replace the @sc{car} of a shared link.}
./SOME/emacs/lispref/lists.texi:;; @r{Replace the @sc{car} of a link that is not shared.}
./SOME/emacs/lispref/lists.texi: The lowest-level primitive for modifying a @sc{cdr} is @code{setcdr}:
./SOME/emacs/lispref/lists.texi:This function stores @var{object} as the new @sc{cdr} of @var{cons},
./SOME/emacs/lispref/lists.texi:replacing its previous @sc{cdr}. In other words, it changes the
./SOME/emacs/lispref/lists.texi:@sc{cdr} slot of @var{cons} to refer to @var{object}. It returns the
./SOME/emacs/lispref/lists.texi: Here is an example of replacing the @sc{cdr} of a list with a
./SOME/emacs/lispref/lists.texi:unchanged, because it resides in the @sc{car} of the list, and is not
./SOME/emacs/lispref/lists.texi:reached via the @sc{cdr}.
./SOME/emacs/lispref/lists.texi:@sc{cdr}s of the cons cells in the list. For example, here we delete
./SOME/emacs/lispref/lists.texi:the @sc{cdr} of the first cons cell:
./SOME/emacs/lispref/lists.texi:exists and its @sc{car} is still @code{b}, but it no longer forms part
./SOME/emacs/lispref/lists.texi: It is equally easy to insert a new element by changing @sc{cdr}s:
./SOME/emacs/lispref/lists.texi:modifying the @sc{cdr}s of their component cons cells. These functions
./SOME/emacs/lispref/lists.texi:@emph{not} copied. Instead, the last @sc{cdr} of each of the
./SOME/emacs/lispref/lists.texi:removing it involves changing the @sc{cdr}s (@pxref{Setcdr}).
./SOME/emacs/lispref/lists.texi:@dfn{associations}: the @sc{car} of each cons cell is the @dfn{key}, and the
./SOME/emacs/lispref/lists.texi:@sc{cdr} is the @dfn{associated value}.@footnote{This usage of ``key''
./SOME/emacs/lispref/lists.texi:associated with the @emph{list} @code{(2 3)}, which is the @sc{cdr} of
./SOME/emacs/lispref/lists.texi:value in the @sc{car} of the @sc{cdr} of the element. Here is an
./SOME/emacs/lispref/lists.texi:information---even a list of other items---in the @sc{cdr} of the
./SOME/emacs/lispref/lists.texi:@sc{cdr}. One disadvantage is that you cannot use @code{rassq} (see
./SOME/emacs/lispref/lists.texi:associated value in the @sc{cdr} of the element; the value associated
./SOME/emacs/lispref/lists.texi:association in @var{alist} has a @sc{car} equal to @var{key}. For
./SOME/emacs/lispref/lists.texi:a @sc{cdr} @code{equal} to @var{value}.
./SOME/emacs/lispref/lists.texi:@code{rassoc} is like @code{assoc} except that it compares the @sc{cdr} of
./SOME/emacs/lispref/lists.texi:each @var{alist} association instead of the @sc{car}. You can think of
./SOME/emacs/lispref/lists.texi:@var{alist} has a @sc{car} @code{eq} to @var{key}. This function is
./SOME/emacs/lispref/lists.texi:a @sc{cdr} @code{eq} to @var{value}.
./SOME/emacs/lispref/lists.texi:@code{rassq} is like @code{assq} except that it compares the @sc{cdr} of
./SOME/emacs/lispref/lists.texi:each @var{alist} association instead of the @sc{car}. You can think of
./SOME/emacs/lispref/lists.texi:@code{rassq} cannot search for a value stored in the @sc{car}
./SOME/emacs/lispref/lists.texi:of the @sc{cdr} of an element:
./SOME/emacs/lispref/lists.texi:In this case, the @sc{cdr} of the association @code{(lily white)} is not
./SOME/emacs/lispref/lists.texi:the element's @sc{car} (if it is a cons) against @var{key}, by calling
./SOME/emacs/lispref/lists.texi:@var{test} with two arguments: the element or its @sc{car}, and
./SOME/emacs/lispref/lists.texi:If the element is a cons, then the value is the element's @sc{cdr}.
./SOME/emacs/lispref/lists.texi:This function deletes from @var{alist} all the elements whose @sc{car}
./SOME/emacs/lispref/lists.texi:This function deletes from @var{alist} all the elements whose @sc{cdr}
./SOME/emacs/lispref/lists.texi:compares the @sc{cdr} of each @var{alist} association instead of the
./SOME/emacs/lispref/lists.texi:@sc{car}.
./SOME/emacs/lispref/files.texi:@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
./SOME/emacs/lispref/files.texi:@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
./SOME/emacs/lispref/files.texi:@sc{gnu} @code{Coreutils} Manual}, for a description of file mode
./SOME/emacs/lispref/control.texi:@var{clause} in the @code{cond} must be a list. The @sc{car} of this
./SOME/emacs/lispref/control.texi:@sc{car} of an integer or move forward a character at the end of the
./SOME/emacs/lispref/control.texi:error message is the @sc{car} of @var{data} (that must be a string).
./SOME/emacs/lispref/loading.texi:libraries that are preloaded at startup). It is a list whose @sc{car}
./SOME/emacs/lispref/loading.texi:The value of @code{load-history} may have one element whose @sc{car} is
./SOME/emacs/lispref/sequences.texi:cons cells forming @var{sequence} by changing @sc{cdr}s. A nondestructive
./SOME/emacs/lispref/sequences.texi:Sorting does not change the @sc{car}s of the cons cells in @var{sequence};
./SOME/emacs/lispref/sequences.texi:@var{sequence} still has @code{a} in its @sc{car} after sorting, but it now
./SOME/emacs/lispref/sequences.texi:@sc{cdr}s. For example:
./SOME/emacs/lispref/edebug.texi:argument may then be a dotted list. Alternatively, the last @sc{cdr} of a
./SOME/emacs/lispref/commands.texi:@sc{ascii} control characters such as @kbd{C-a} have special basic
./SOME/emacs/lispref/commands.texi:as lists. The @sc{car} of the list is the event type; this says which
./SOME/emacs/lispref/commands.texi:events that are lists, the event type is the symbol in the @sc{car} of
./SOME/emacs/lispref/commands.texi:if it is a list, the @sc{car} of that list (which should be a number) is
./SOME/emacs/lispref/macros.texi: A Lisp macro object is a list whose @sc{car} is @code{macro}, and
./SOME/emacs/lispref/macros.texi:whose @sc{cdr} is a function. Expansion of the macro works
./SOME/emacs/lispref/macros.texi:(Note that the @sc{cdr} of this list is a lambda expression.) This
./SOME/emacs/lispref/display.texi:non-@code{nil}, the string with the single character @sc{U+2026
./SOME/emacs/lispref/display.texi:additional elements describing the @sc{gsub} and @sc{gpos} features
./SOME/emacs/lispref/display.texi:additional elements describing the @sc{gsub} and @sc{gpos} features
./SOME/emacs/lispref/display.texi:@sc{left-to-right mark}, but excluding characters that have graphic
./SOME/emacs/lispref/display.texi:images, such as U+00AD @sc{soft hyphen}.
./SOME/emacs/lispref/display.texi:their parent buffer is reordered. This is because plain-@sc{ascii}
./SOME/emacs/lispref/display.texi:or overlay string includes non-@sc{ascii} characters, these characters
./SOME/emacs/lispref/display.texi:Append the special character U+200E @sc{left-to-right mark}, or
./SOME/emacs/lispref/display.texi:U+200F @sc{right-to-left mark}, or @acronym{RLM}, instead.) This
./SOME/emacs/lispref/ChangeLog.1: * syntax.texi, text.texi: Replace @sc{foo} with @acronym{FOO}.
./SOME/emacs/lispref/os.texi:The @sc{car}, @var{option}, is a string, the name of a command-line
./SOME/emacs/lispref/os.texi:If it is @code{nil}, then it uses @sc{cbreak} mode. The default
./SOME/emacs/lispref/os.texi:setting is system-dependent. Some systems always use @sc{cbreak} mode
./SOME/emacs/lispref/os.texi:If @var{flow} is non-@code{nil}, then Emacs uses @sc{xon/xoff}
./SOME/emacs/lispref/os.texi:has no effect except in @sc{cbreak} mode.
./SOME/emacs/lispref/os.texi:@code{nil}, Emacs is using @sc{cbreak} mode.
./SOME/emacs/lispref/os.texi:is non-@code{nil} if Emacs uses @sc{xon/xoff} (@kbd{C-q}, @kbd{C-s})
./SOME/emacs/lispref/frames.texi:@sc{car}, the @sc{cdr} of that cell specifies the width of the frame's
./SOME/emacs/lispref/frames.texi:the frame's width ratio is preserved if the @sc{car} of the cell is
./SOME/emacs/lispref/frames.texi:the @sc{car} of the cell is either @code{t} or @code{height-only}. The
./SOME/emacs/lispref/frames.texi:left position ratio is preserved if the @sc{cdr} of the cell is either
./SOME/emacs/lispref/frames.texi:the @sc{cdr} of the cell is either @code{t} or @code{top-only}.
./SOME/emacs/lispref/streams.texi:is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
./SOME/emacs/lispref/streams.texi:@sc{cdr} is the number 5.
./SOME/emacs/lispref/streams.texi:@var{string}. It returns a cons cell whose @sc{car} is that expression,
./SOME/emacs/lispref/streams.texi:and whose @sc{cdr} is an integer giving the position of the next
./SOME/emacs/lispref/minibuf.texi:a string, or a cons cell whose @sc{car} is either a string or a symbol
./SOME/emacs/lispref/minibuf.texi:@var{predicate} is either a string or a cons cell (the @sc{car} of
./SOME/emacs/lispref/minibuf.texi:matched by three of the alist @sc{car}s. All of the matches begin with
./SOME/emacs/lispref/help.texi:symbol in the @sc{car} of the list, inside angle brackets.
./SOME/emacs/lispref/variables.texi:Note that storing new values into the @sc{cdr}s of cons cells in this
./SOME/emacs/lispref/variables.texi:form is a regular Lisp variable. But the @sc{car}s and @sc{cdr}s of
./SOME/emacs/lispref/customize.texi:The value must be a cons cell, its @sc{car} must fit @var{car-type}, and
./SOME/emacs/lispref/customize.texi:its @sc{cdr} must fit @var{cdr-type}. For example, @code{(cons string
./SOME/emacs/lispref/customize.texi:In the customization buffer, the @sc{car} and @sc{cdr} are displayed
./SOME/emacs/lispref/customize.texi:The value must be a list of cons-cells, the @sc{car} of each cell
./SOME/emacs/lispref/customize.texi:@sc{cdr} of the same cell representing a value of customization type
./SOME/emacs/lispref/modes.texi:comment starter. If the entry is a cons cell, the @sc{car} is set
./SOME/emacs/lispref/modes.texi:up as a comment starter and the @sc{cdr} as a comment ender.
./SOME/emacs/lispref/modes.texi:The @sc{car}, @var{characters}, can be either a character or a string.
./SOME/emacs/lispref/modes.texi:expression or a function, as described above. The @sc{cdr},
./SOME/emacs/lispref/modes.texi:The @sc{car}, @var{subexp}, is an integer specifying which subexpression
./SOME/emacs/lispintro/emacs-lisp-intro.texi:number. The argument used by @samp{%c} must be an @sc{ascii} code
./SOME/emacs/lispintro/emacs-lisp-intro.texi:number; it will be printed as the character with that @sc{ascii} code.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:The @sc{car} of a list is, quite simply, the first item in the list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:Thus the @sc{car} of the list @code{(rose violet daisy buttercup)} is
./SOME/emacs/lispintro/emacs-lisp-intro.texi:The @sc{cdr} of a list is the rest of the list, that is, the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:first item. Thus, while the @sc{car} of the list @code{'(rose violet
./SOME/emacs/lispintro/emacs-lisp-intro.texi:list. However, the @sc{cdr} of the list is a list itself, @code{(fir
./SOME/emacs/lispintro/emacs-lisp-intro.texi:In this example, the first element or @sc{car} of the list is the list of
./SOME/emacs/lispintro/emacs-lisp-intro.texi:What it does is take the @sc{cdr} of a list repeatedly.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:If you take the @sc{cdr} of the list @code{(pine fir
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@code{(oak maple)}. (Of course, repeated @sc{cdr}ing on the original
./SOME/emacs/lispintro/emacs-lisp-intro.texi:list will just give you the original @sc{cdr} since the function does
./SOME/emacs/lispintro/emacs-lisp-intro.texi:not change the list. You need to evaluate the @sc{cdr} of the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cdr} and so on.) If you continue this, eventually you will be
./SOME/emacs/lispintro/emacs-lisp-intro.texi:For review, here is a series of repeated @sc{cdr}s, the text following
./SOME/emacs/lispintro/emacs-lisp-intro.texi:You can also do several @sc{cdr}s without printing the values in
./SOME/emacs/lispintro/emacs-lisp-intro.texi:The @code{nthcdr} function takes the @sc{cdr} of a list repeatedly.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:The @code{nth} function takes the @sc{car} of the result returned by
./SOME/emacs/lispintro/emacs-lisp-intro.texi:say, the first element of a list, its @sc{car} is the zeroth element.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:functions set the @sc{car} or the @sc{cdr} of a list to a new value.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the first list will be set;
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@code{(horse cat dog)}. The @sc{cdr} of the list is changed from
./SOME/emacs/lispintro/emacs-lisp-intro.texi:with the text already in the first element (the @sc{car}) of the kill
./SOME/emacs/lispintro/emacs-lisp-intro.texi:the @sc{car} of the kill ring. Whether it prepends or appends the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:It sets the @sc{cdr} of a list, just as @code{setcar} sets the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{car} of a list. In this case, however, @code{setcdr} will not be
./SOME/emacs/lispintro/emacs-lisp-intro.texi:setting the @sc{cdr} of the whole kill ring; the @code{nthcdr}
./SOME/emacs/lispintro/emacs-lisp-intro.texi:function is used to cause it to set the @sc{cdr} of the next to last
./SOME/emacs/lispintro/emacs-lisp-intro.texi:element of the kill ring---this means that since the @sc{cdr} of the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:The @code{nthcdr} function works by repeatedly taking the @sc{cdr} of a
./SOME/emacs/lispintro/emacs-lisp-intro.texi:list---it takes the @sc{cdr} of the @sc{cdr} of the @sc{cdr}
./SOME/emacs/lispintro/emacs-lisp-intro.texi:elements long, we could set the @sc{cdr} of the next to last element
./SOME/emacs/lispintro/emacs-lisp-intro.texi:birch)}, then set the @sc{cdr} of its second @sc{cdr} to @code{nil}
./SOME/emacs/lispintro/emacs-lisp-intro.texi:that is what the @sc{cdr} is set to.)
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cdr} a number of times that is one less than the maximum permitted
./SOME/emacs/lispintro/emacs-lisp-intro.texi:size of the kill ring and @code{setcdr} sets the @sc{cdr} of that
./SOME/emacs/lispintro/emacs-lisp-intro.texi:Return the result of taking @sc{cdr} @var{n} times on a list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:If a symbol is set to the @sc{cdr} of a list, the list itself is not
./SOME/emacs/lispintro/emacs-lisp-intro.texi:the jargon, @sc{car} and @sc{cdr} are ``non-destructive''.) Thus,
./SOME/emacs/lispintro/emacs-lisp-intro.texi:Thus, in Lisp, to get the @sc{cdr} of a list, you just get the address
./SOME/emacs/lispintro/emacs-lisp-intro.texi:of the next cons cell in the series; to get the @sc{car} of a list,
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@code{more-flowers}. Set the @sc{car} of @code{flowers} to a fish.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:of the kill ring of which the first element (the @sc{car}) will be
./SOME/emacs/lispintro/emacs-lisp-intro.texi:expression set the value of the list to be the @sc{cdr} of the list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:can be set to be the @sc{cdr} of the original list with the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@code{dolist} works like a @code{while} loop that @sc{cdr}s down a
./SOME/emacs/lispintro/emacs-lisp-intro.texi:loops---takes the @sc{cdr} of the list---and binds the @sc{car} of
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cdr}s down the list on its own---and it automatically binds
./SOME/emacs/lispintro/emacs-lisp-intro.texi:the @sc{car} of each shorter version of the list to the first of its
./SOME/emacs/lispintro/emacs-lisp-intro.texi:In the example, the @sc{car} of each shorter version of the list is
./SOME/emacs/lispintro/emacs-lisp-intro.texi:The @code{dolist} expression binds the @sc{car} of each shorter
./SOME/emacs/lispintro/emacs-lisp-intro.texi:first element of the list, the @sc{car} of the list. Then the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:list). Then the function calls itself with the @sc{cdr} of the list
./SOME/emacs/lispintro/emacs-lisp-intro.texi:it is invoked with, which (the second time around) is the @sc{cdr} of
./SOME/emacs/lispintro/emacs-lisp-intro.texi:the @sc{cdr} of the original list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:evaluates the first element (the @sc{car} or true-or-false-test) of
./SOME/emacs/lispintro/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list)
./SOME/emacs/lispintro/emacs-lisp-intro.texi: @sc{cdr}) of the list,
./SOME/emacs/lispintro/emacs-lisp-intro.texi: act on the beginning of the list (the @sc{car} of the list),
./SOME/emacs/lispintro/emacs-lisp-intro.texi: and make a recursive call on the rest (the @sc{cdr}) of the list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list),
./SOME/emacs/lispintro/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:Else, if the beginning of the list (the @sc{car} of the list) passes
./SOME/emacs/lispintro/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:Otherwise, if the beginning of the list (the @sc{car} of the list) fails
./SOME/emacs/lispintro/emacs-lisp-intro.texi: and, recursively call the function on the rest (the @sc{cdr}) of the list.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:technique is to set the value of the list to the value of the @sc{cdr}
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cdr} of itself, so eventually the list will be empty; and the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:should not be too hard to write a function that @sc{cdr}s down the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:(cdr numbers-list))} expression, the @sc{car} of each instance of the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:non-@sc{ascii} characters are written within square brackets, without
./SOME/emacs/lispintro/emacs-lisp-intro.texi:hexadecimal three, and @sc{ascii} Control-C (the third letter of the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:set to be equal to some @sc{cdr} of the kill ring, using the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:works by repeatedly taking the @sc{cdr} of a list---it takes the
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the @sc{cdr} of the @sc{cdr} @dots{}
./SOME/emacs/lispintro/emacs-lisp-intro.texi:the @code{mod} function to determine which @sc{cdr} to select.
./SOME/emacs/lispintro/emacs-lisp-intro.texi:@sc{cons} rather than a number or nothing, it puts point at beginning
./SOME/gcal/de/texi/gcal.texi:Eine Gcal Ressourcendatei ist zun@"achst einmal eine reine @sc{ascii}
./SOME/gcal/de/texi/gcal.texi:lassen sich auf Nicht-@sc{ascii} Zeichens@"atze anwenden, welche einzelne
./SOME/gcal/de/texi/gcal.texi:Diese l@"a@ss{} sich auf Nicht-@sc{ascii} Zeichens@"atze anwenden, welche
./SOME/gcal/en/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/gcal/en/gcal.texi:First of all, a Gcal resource file is a plain @sc{ascii} text file.
./SOME/gcal/en/gcal.texi:These apply to non-@sc{ascii} character sets, which can have single symbols
./SOME/gcal/en/gcal.texi:expression. This apply to non-@sc{ascii} character sets, which can
./SOME/libredwg/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/smalltalk/gst-libs.texi:@sc{gnu} Smalltalk
./SOME/smalltalk/gst-libs.texi:@sc{gnu}
./SOME/smalltalk/gst-libs.texi:@title @sc{gnu} Smalltalk Library Reference
./SOME/smalltalk/gst-base.texi:@sc{gnu} Smalltalk
./SOME/smalltalk/gst-base.texi:@sc{gnu}
./SOME/smalltalk/gst-base.texi:@title @sc{gnu} Smalltalk Library Reference
./SOME/smalltalk/gst.texi:@sc{gnu} Smalltalk
./SOME/smalltalk/gst.texi:@sc{gnu}
./SOME/smalltalk/gst.texi:@title @sc{gnu} Smalltalk User's Guide
./SOME/smalltalk/gst.texi:languages}. Therefore, even though we have a @sc{gui} environment based
./SOME/smalltalk/gst.texi:@multitable {@option{--verbose -aq -c}} {Options seen by @sc{gnu} Smalltalk} {@code{Smalltalk arguments}}
./SOME/smalltalk/gst.texi:operations to @code{stdout}. If you load the VisualGST @sc{gui}, instead,
./SOME/smalltalk/gst.texi:@gst{} inherits from @sc{iso} C the concept of a @dfn{locale}, that is, a
./SOME/smalltalk/gst.texi:Format a monetary value together with its @sc{iso} currency symbol.
./SOME/smalltalk/gst.texi:@sc{mo} file format adopted by the @gnu{} @code{gettext} library.
./SOME/smalltalk/gst.texi:engine which is now superseded by Swazoo. It is based on the @sc{gpl}'ed
./SOME/smalltalk/gst.texi:authentication support, virtual hosting, and @sc{http} 1.1 compliance.
./SOME/smalltalk/gst.texi:@gst{} includes an almost complete abstraction of the @sc{tcp}, @sc{udp}
./SOME/smalltalk/gst.texi:and @sc{ip} protocols. Although based on the standard @sc{bsd} sockets,
./SOME/smalltalk/gst.texi:@sc{ftp}, @sc{http}, @sc{nntp}, @sc{smtp}, @sc{pop3} and @sc{imap}.
./SOME/smalltalk/gst.texi:The @sc{xml} parser library for Smalltalk, loaded as package @code{XML}
./SOME/smalltalk/gst.texi:includes a validating @sc{xml} parser and Document Object Model.
./SOME/smalltalk/gst.texi:and a @sc{xslr} interpreter based on it is bundled with @gst{} as
./SOME/smalltalk/gst.texi:@item @sc{gdbm}
./SOME/smalltalk/gst.texi:with the library at run-time using @sc{dld}, using either
./SOME/smalltalk/gst.texi:run-time; but since some@footnote{The most notable are @sc{aix} and
./SOME/smalltalk/tutorial.texi: @gst{} supports completion in the same way as Bash or @sc{gdb}.
./SOME/mit-scheme/sos/sos.texinfo:@sc{sos} is a Scheme @dfn{object system} derived from Tiny @sc{clos}
./SOME/mit-scheme/sos/sos.texinfo:@footnote{Tiny @sc{clos} was written by Gregor Kiczales of Xerox
./SOME/mit-scheme/sos/sos.texinfo:@sc{parc}; @sc{sos} is derived from version 1.2 of Tiny @sc{clos}.},
./SOME/mit-scheme/sos/sos.texinfo:which in turn was loosely derived from @sc{clos}, the Common Lisp Object
./SOME/mit-scheme/sos/sos.texinfo:@sc{clos}, but there are differences in naming and interface.
./SOME/mit-scheme/sos/sos.texinfo:you already have a passing familiarity with @sc{clos} and with Scheme.
./SOME/mit-scheme/sos/sos.texinfo:@dfn{instance} objects. Instances are special because @sc{sos} has
./SOME/mit-scheme/sos/sos.texinfo:pair whose @sc{car} is a symbol and whose @sc{cdr} is an alist. The
./SOME/mit-scheme/sos/sos.texinfo:@sc{sos} provides a rich set of predefined classes that can be used to
./SOME/mit-scheme/sos/sos.texinfo:@sc{sos} allows generic procedures to discriminate on record types.
./SOME/mit-scheme/sos/sos.texinfo:In order to support this, @sc{sos} accepts record type descriptors in
./SOME/mit-scheme/sos/sos.texinfo:descriptor has an associated @sc{sos} class; either the class or the
./SOME/mit-scheme/sos/sos.texinfo:accepted; the @sc{cdr} may be @code{#f} indicating no upper bound.
./SOME/mit-scheme/sos/sos.texinfo:an @dfn{effective method procedure}, or @sc{emp}, then tail-recursively
./SOME/mit-scheme/sos/sos.texinfo:invoking the @sc{emp}. @code{compute-effective-method-procedure} is the
./SOME/mit-scheme/sos/sos.texinfo:them into an @sc{emp}.
./SOME/mit-scheme/sos/sos.texinfo:returns that @sc{emp}.
./SOME/mit-scheme/sos/sos.texinfo:Note that computed methods and computed @sc{emp}s both satisfy the
./SOME/mit-scheme/sos/sos.texinfo:A @dfn{computed @sc{emp}} takes the computed-method mechanism one step
./SOME/mit-scheme/sos/sos.texinfo:further. A computed @sc{emp} is like a computed method, except that it
./SOME/mit-scheme/sos/sos.texinfo:computed @sc{emp}s, and if exactly one of them returns an @sc{emp}, that
./SOME/mit-scheme/sos/sos.texinfo:Create and return a computed @sc{emp}. @var{Procedure} will be called
./SOME/mit-scheme/sos/sos.texinfo:arguments as its arguments. It must return either an @sc{emp} or
./SOME/mit-scheme/sos/sos.texinfo:@sc{emp}. The @var{key} is used by @code{add-method} and
./SOME/mit-scheme/sos/sos.texinfo:@code{delete-method} to decide whether two computed @sc{emp}s are
./SOME/mit-scheme/sos/sos.texinfo:@sc{emp} with the same specializers.
./SOME/mit-scheme/sos/sos.texinfo:Returns @code{#t} if @var{object} is a computed @sc{emp}, otherwise
./SOME/mit-scheme/sos/sos.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/mit-scheme/ffi/ffi.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/mit-scheme/user-manual/user.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/mit-scheme/ref-manual/graphics.texi:bitmaps (@sc{dib}s).
./SOME/mit-scheme/ref-manual/numbers.texi:used to implement all inexact reals; on machines that support @sc{ieee}
./SOME/mit-scheme/ref-manual/numbers.texi:but does not require, that the @sc{ieee} 32-bit and 64-bit floating
./SOME/mit-scheme/ref-manual/numbers.texi:modes required by the @sc{ieee} floating point standard.
./SOME/mit-scheme/ref-manual/io.texi:unix this procedure can be used to open terminal device files, @sc{pty}
./SOME/mit-scheme/ref-manual/special-forms.texi:values are only useful with a @sc{boa} constructor with argument list or
./SOME/mit-scheme/ref-manual/special-forms.texi:constructor procedures are called ``@sc{boa} constructors'', for ``By
./SOME/mit-scheme/ref-manual/special-forms.texi:@sc{boa} constructors are described using Scheme lambda lists. Since there
./SOME/mit-scheme/ref-manual/os-interface.texi:@sc{pty} devices; if true, @sc{pty}s will be used, otherwise pipes will
./SOME/mit-scheme/ref-manual/os-interface.texi:inter-process communication. @sc{tcp} stream sockets are supported,
./SOME/mit-scheme/ref-manual/os-interface.texi:which communicate between computers over a @sc{tcp/ip} network.
./SOME/mit-scheme/ref-manual/os-interface.texi:@sc{tcp} sockets are supported on all operating systems.
./SOME/mit-scheme/ref-manual/os-interface.texi:@sc{tcp} sockets have two distinct interfaces: one interface to
./SOME/mit-scheme/ref-manual/os-interface.texi:Next we will treat setting up a @sc{tcp} server, which is slightly more
./SOME/mit-scheme/ref-manual/os-interface.texi:terminated by @sc{cr-lf}, which is the standard for most internet
./SOME/mit-scheme/ref-manual/error.texi:stopping the computation and putting the user in an error @sc{repl}.
./SOME/mit-scheme/ref-manual/error.texi:and stops the computation, entering an error @sc{repl}. Under normal
./SOME/mit-scheme/ref-manual/error.texi:breakpoint @sc{repl} is initiated. Otherwise (or when that @sc{repl}
./SOME/mit-scheme/ref-manual/error.texi:creates a new @sc{repl} prior to its normal operation when its argument
./SOME/mit-scheme/ref-manual/error.texi:Arranges for @code{signal-condition} to create an interactive @sc{repl}
./SOME/mit-scheme/ref-manual/error.texi:In order to create a @sc{repl} when @emph{any} condition type is
./SOME/mit-scheme/ref-manual/error.texi:@code{signal-condition}. Normally creates a new @sc{repl} with
./SOME/mit-scheme/ref-manual/error.texi:@sc{repl}. It is passed one argument, the condition being signalled.
./SOME/mit-scheme/ref-manual/error.texi:of computation. This is the restart provided by Scheme's @sc{repl}.
./SOME/mit-scheme/ref-manual/gfdl.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/gforth/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/netutils/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/rpge/fdl.texi~:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/emms/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/guile-lib/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/riece/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SOME/femlisp/femlisp.texinfo:@sc{Femlisp}
./SOME/readline/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library
./SOME/readline/hsuser.texi:For information on using the @sc{gnu} History Library in other programs,
./SOME/readline/hsuser.texi:see the @sc{gnu} Readline Library Manual.
./SOME/readline/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library interactively,
./SOME/readline/hsuser.texi:information on using the @sc{gnu} History Library in your own programs,
./SOME/readline/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/readline/rluser.texi:This chapter describes the basic features of the @sc{gnu}
./SOME/readline/rluser.texi:eighth bit set to an @sc{ascii} key sequence by stripping the eighth
./SOME/readline/rluser.texi:the key sequence in double quotes. Some @sc{gnu} Emacs style key
./SOME/readline/rluser.texi:The following @sc{gnu} Emacs style escape sequences are available when
./SOME/readline/rluser.texi:In addition to the @sc{gnu} Emacs style escape sequences, a second
./SOME/readline/rluser.texi:interprets it as the end of input and returns @sc{eof}.
./SOME/readline/rluser.texi:same character as the tty @sc{eof} character, as @kbd{C-d}
./SOME/readline/rluser.texi:the @sc{posix} standard.
./SOME/readline/rltech.texi:This chapter describes the interface between the @sc{gnu} Readline Library and
./SOME/readline/rltech.texi:features found in @sc{gnu} Readline
./SOME/readline/rltech.texi:Always set to 1, denoting that this is @sc{gnu} readline rather than some
./SOME/readline/hstech.texi:with the @sc{gnu} History Library.
./SOME/readline/hstech.texi:For information on the interactive use of @sc{gnu} History, @pxref{Using
./SOME/readline/hstech.texi:Many programs read input from the user a line at a time. The @sc{gnu}
./SOME/readline/hstech.texi:exported by the @sc{gnu} History library.
./SOME/readline/hstech.texi:the @sc{gnu} History Library.
./SOME/readline/hstech.texi:The following program demonstrates simple use of the @sc{gnu} History Library.
./SOME/gnumach/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/gnumach/mach.texi:@sc{carnegie mellon allows free use of this software in its ``as is''
./SOME/rtliber/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/nyacc/nyacc-c99-ug.texi:Manual. It is included with the @sc{nyacc} source as COPYING.DOC.
./SOME/nyacc/nyacc-c99-hg.texi:Manual. It is included with the @sc{nyacc} source as COPYING.DOC.
./SOME/nyacc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/nyacc/nyacc-ug.texi:@sc{NYACC}
./SOME/nyacc/nyacc-ug.texi:@c @alias NYACC = @sc{NYACC}
./SOME/nyacc/nyacc-hg.texi:@xref{References}. In the application of @sc{nyacc} one writes out a
./SOME/nyacc/nyacc-hg.texi:represented by a set of items. In @sc{nyacc} we use a pair (a cons
./SOME/nyacc/nyacc-hg.texi:In @sc{nyacc} we denote a la-item with a cons cell where the car is
./SOME/nyacc/nyacc-hg.texi:It is an important function used by @sc{nyacc} in generating a parser.
./SOME/nyacc/nyacc-hg.texi:In @sc{nyacc} the canonical grammer will always include the following
./SOME/nyacc/nyacc-hg.texi:parsers having one additional state with respect to @sc{nyacc} parsers.)
./SOME/nyacc/nyacc-hg.texi:The generation of the automaton (aka the @dfn{machine}) in @sc{nyacc}
./SOME/nyacc/nyacc-hg.texi:@chapter The @sc{NYACC} Module ::
./SOME/nyacc/nyacc-hg.texi:Manual. It is included with the @sc{nyacc} source as COPYING.DOC.
./SOME/nyacc/nyacc-fh-ug.texi:which are included in the @uref{https://www.nongnu.org/nyacc,@sc{NYACC}}
./SOME/nyacc/nyacc-fh-ug.texi:@sc{NYACC} distribution, the relevant modules can be found under the
./SOME/nyacc/nyacc-fh-ug.texi:guile)} are required. No other code from the @sc{NYACC} distribution
./SOME/arc/fdl.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/sed-history/sed-in.texi:some implementations of @command{sed} (which are not @sc{posix}
./SOME/sed-history/sed-in.texi:Note: the @sc{posix} standard does not specify what should happen
./SOME/sed-history/sed-in.texi:a @sc{nul} character. This is a @value{SSED} extension.
./SOME/sed-history/sed-in.texi:executed contains a @sc{nul} character.
./SOME/sed-history/sed-in.texi:Produces or matches a @sc{bel} character, that is an ``alert'' (@sc{ascii} 7).
./SOME/sed-history/sed-in.texi:Produces or matches a form feed (@sc{ascii} 12).
./SOME/sed-history/sed-in.texi:Produces or matches a newline (@sc{ascii} 10).
./SOME/sed-history/sed-in.texi:Produces or matches a carriage return (@sc{ascii} 13).
./SOME/sed-history/sed-in.texi:Produces or matches a horizontal tab (@sc{ascii} 9).
./SOME/sed-history/sed-in.texi:Produces or matches a so called ``vertical tab'' (@sc{ascii} 11).
./SOME/sed-history/sed-in.texi:Produces or matches @kbd{@sc{Control}-@var{x}}, where @var{x} is
./SOME/sed-history/sed-in.texi:Produces or matches a character whose decimal @sc{ascii} value is @var{xxx}.
./SOME/sed-history/sed-in.texi:Produces or matches a character whose octal @sc{ascii} value is @var{xxx}.
./SOME/sed-history/sed-in.texi:with the @code{o} is active in the normal or extended @sc{posix} regular
./SOME/sed-history/sed-in.texi:Produces or matches a character whose hexadecimal @sc{ascii} value is @var{xx}.
./SOME/sed-history/sed-in.texi:Ubben wrote an implementation of the @command{dc} @sc{rpn} calculator!
./SOME/sed-history/sed-in.texi:The @sc{posix} standard specifies that conforming @command{sed}
./SOME/sed-history/sed-in.texi:Also, @value{SSED} recognizes the @sc{posix} syntax
./SOME/sed-history/sed-in.texi:@command{sed} uses the @sc{posix} basic regular expression syntax. According to
./SOME/sed-history/sed-in.texi:As in all GNU programs that use @sc{posix} basic regular expressions, @command{sed}
./SOME/sed-history/sed-in.texi:with the free @sc{pcre} regular expression matcher; it was written by Philip Hazel.}
./SOME/sed-history/sed-in.texi:@sc{ascii} values for characters can be specified in octal
./SOME/sed-history/sed-in.texi:for @var{xxx}. For example @code{\07} is a @sc{bel} character
./SOME/sed-history/sed-in.texi:rather than a @sc{nul} and a literal @code{7} (this sequence is
./SOME/sed-history/sed-in.texi: \377 @i{is a byte consisting entirely of 1 bits (@sc{ascii} 255)}
./SOME/sed-history/sed-in.texi:outside character classes. Instead, in @sc{posix} mode these sequences
./SOME/sed-history/sed-in.texi:@code{\<} and @code{\>} achieve this purpose in @sc{posix} mode
./SOME/sed-history/sed-in.texi:@code{\`} and @code{\'} that are active in @sc{posix} mode.
./SOME/sed-history/sed-in.texi:Ranges operate in @sc{ascii} collating sequence. They can also be
./SOME/sed-history/sed-in.texi:Unlike in @sc{posix} mode, the character types @code{\d},
./SOME/sed-history/sed-in.texi:Perl 5.6 supports the @sc{posix} notation for character classes, which
./SOME/sed-history/sed-in.texi:By default, the quantifiers are @dfn{greedy} like in @sc{posix}
./SOME/sed-history/sed-in.texi:in @sc{posix} mode. If the pattern continues with a digit
./SOME/sed-history/sed.texi:some implementations of @command{sed} (which are not @sc{posix}
./SOME/sed-history/sed.texi:Note: the @sc{posix} standard does not specify what should happen
./SOME/sed-history/sed.texi:a @sc{nul} character. This is a @value{SSED} extension.
./SOME/sed-history/sed.texi:executed contains a @sc{nul} character.
./SOME/sed-history/sed.texi:Produces or matches a @sc{bel} character, that is an ``alert'' (@sc{ascii} 7).
./SOME/sed-history/sed.texi:Produces or matches a form feed (@sc{ascii} 12).
./SOME/sed-history/sed.texi:Produces or matches a newline (@sc{ascii} 10).
./SOME/sed-history/sed.texi:Produces or matches a carriage return (@sc{ascii} 13).
./SOME/sed-history/sed.texi:Produces or matches a horizontal tab (@sc{ascii} 9).
./SOME/sed-history/sed.texi:Produces or matches a so called ``vertical tab'' (@sc{ascii} 11).
./SOME/sed-history/sed.texi:Produces or matches @kbd{@sc{Control}-@var{x}}, where @var{x} is
./SOME/sed-history/sed.texi:Produces or matches a character whose decimal @sc{ascii} value is @var{xxx}.
./SOME/sed-history/sed.texi:Produces or matches a character whose octal @sc{ascii} value is @var{xxx}.
./SOME/sed-history/sed.texi:with the @code{o} is active in the normal or extended @sc{posix} regular
./SOME/sed-history/sed.texi:Produces or matches a character whose hexadecimal @sc{ascii} value is @var{xx}.
./SOME/sed-history/sed.texi:Ubben wrote an implementation of the @command{dc} @sc{rpn} calculator!
./SOME/sed-history/sed.texi:The @sc{posix} standard specifies that conforming @command{sed}
./SOME/sed-history/sed.texi:Also, @value{SSED} recognizes the @sc{posix} syntax
./SOME/sed-history/sed.texi:@command{sed} uses the @sc{posix} basic regular expression syntax. According to
./SOME/sed-history/sed.texi:As in all GNU programs that use @sc{posix} basic regular expressions, @command{sed}
./SOME/sed-history/sed.texi:with the free @sc{pcre} regular expression matcher; it was written by Philip Hazel.}
./SOME/sed-history/sed.texi:@sc{ascii} values for characters can be specified in octal
./SOME/sed-history/sed.texi:for @var{xxx}. For example @code{\07} is a @sc{bel} character
./SOME/sed-history/sed.texi:rather than a @sc{nul} and a literal @code{7} (this sequence is
./SOME/sed-history/sed.texi: \377 @i{is a byte consisting entirely of 1 bits (@sc{ascii} 255)}
./SOME/sed-history/sed.texi:outside character classes. Instead, in @sc{posix} mode these sequences
./SOME/sed-history/sed.texi:@code{\<} and @code{\>} achieve this purpose in @sc{posix} mode
./SOME/sed-history/sed.texi:@code{\`} and @code{\'} that are active in @sc{posix} mode.
./SOME/sed-history/sed.texi:Ranges operate in @sc{ascii} collating sequence. They can also be
./SOME/sed-history/sed.texi:Unlike in @sc{posix} mode, the character types @code{\d},
./SOME/sed-history/sed.texi:Perl 5.6 supports the @sc{posix} notation for character classes, which
./SOME/sed-history/sed.texi:By default, the quantifiers are @dfn{greedy} like in @sc{posix}
./SOME/sed-history/sed.texi:in @sc{posix} mode. If the pattern continues with a digit
./SOME/gluster/user-guide/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/guile/ref/api-regex.texi:Or matching a @sc{yyyymmdd} format date such as @samp{20020828} and
./SOME/guile/ref/api-data.texi:Return the bitwise @sc{and} of the integer arguments.
./SOME/guile/ref/api-data.texi:Return the bitwise @sc{or} of the integer arguments.
./SOME/guile/ref/api-data.texi:Return the bitwise @sc{xor} of the integer arguments. A bit is
./SOME/guile/ref/api-data.texi:common @sc{unix} command of the same name.
./SOME/guile/ref/srfi-modules.texi:Return two values, the @sc{car} and the @sc{cdr} of @var{pair}.
./SOME/guile/ref/srfi-modules.texi:Return the first pair of @var{lst} whose @sc{car} satisfies the
./SOME/guile/ref/srfi-modules.texi:Return the first sublist of @var{lst} whose @sc{car} is equal to
./SOME/guile/ref/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/guile/ref/texinfo.texi:The returned index is a list of pairs, the @sc{car} of which is the
./SOME/guile/ref/texinfo.texi:entry (a string) and the @sc{cdr} of which is a node name (a string).
./SOME/guile/ref/data-rep.texi:the @sc{car} and @sc{cdr}. Is there any way to represent pairs using
./SOME/guile/ref/api-binding.texi:@sc{Algol 60}. Readers familiar to languages like C or Java should
./SOME/guile/r5rs/r5rs.texi:@author R@sc{ICHARD} K@sc{ELSEY}, W@sc{ILLIAM} C@sc{LINGER, AND} J@sc{ONATHAN} R@sc{EES} (@i{Editors})
./SOME/guile/r5rs/r5rs.texi:@author H. A@sc{BELSON}
./SOME/guile/r5rs/r5rs.texi:@author R. K. D@sc{YBVIG}
./SOME/guile/r5rs/r5rs.texi:@author C. T. H@sc{AYNES}
./SOME/guile/r5rs/r5rs.texi:@author G. J. R@sc{OZAS}
./SOME/guile/r5rs/r5rs.texi:@author N. I. A@sc{DAMS IV}
./SOME/guile/r5rs/r5rs.texi:@author D. P. F@sc{RIEDMAN}
./SOME/guile/r5rs/r5rs.texi:@author E. K@sc{OHLBECKER}
./SOME/guile/r5rs/r5rs.texi:@author G. L. S@sc{TEELE} J@sc{R}.
./SOME/guile/r5rs/r5rs.texi:@author D. H. B@sc{ARTLEY}
./SOME/guile/r5rs/r5rs.texi:@author R. H@sc{ALSTEAD}
./SOME/guile/r5rs/r5rs.texi:@author D. O@sc{XLEY}
./SOME/guile/r5rs/r5rs.texi:@author G. J. S@sc{USSMAN}
./SOME/guile/r5rs/r5rs.texi:@author G. B@sc{ROOKS}
./SOME/guile/r5rs/r5rs.texi:@author C. H@sc{ANSON}
./SOME/guile/r5rs/r5rs.texi:@author K. M. P@sc{ITMAN}
./SOME/guile/r5rs/r5rs.texi:@author M. W@sc{AND}
./SOME/guile/r5rs/r5rs.texi:R@sc{ichard} K@sc{elsey}, W@sc{illiam} C@sc{linger, and} J@sc{onathan} R@sc{ees} (@i{Editors})
./SOME/guile/r5rs/r5rs.texi:@item H. A@sc{belson} @tab R. K. D@sc{ybvig} @tab C. T. H@sc{aynes} @tab G. J. R@sc{ozas}
./SOME/guile/r5rs/r5rs.texi:@item N. I. A@sc{dams IV} @tab D. P. F@sc{riedman} @tab E. K@sc{ohlbecker} @tab G. L. S@sc{teele} J@sc{r}.
./SOME/guile/r5rs/r5rs.texi:@item D. H. B@sc{artley} @tab R. H@sc{alstead} @tab D. O@sc{xley} @tab G. J. S@sc{ussman}
./SOME/guile/r5rs/r5rs.texi:@item G. B@sc{rooks} @tab C. H@sc{anson} @tab K. M. P@sc{itman} @tab M. W@sc{and}
./SOME/guile/r5rs/r5rs.texi:and notation used here are described in @sc{[Stoy77]}.
./SOME/qpimd/install.texi:Force to enable @sc{gnu}/Linux netlink interface. Quagga configure
./SOME/qpimd/install.texi:There are several options available only to @sc{gnu}/Linux systems:
./SOME/qpimd/install.texi:@footnote{@sc{gnu}/Linux has very flexible kernel configuration features}. If
./SOME/qpimd/install.texi:you use @sc{gnu}/Linux, make sure that the current kernel configuration is
./SOME/qpimd/install.texi:IPv6 support has been added in @sc{gnu}/Linux kernel version 2.2. If you
./SOME/qpimd/install.texi:try to use the Quagga IPv6 feature on a @sc{gnu}/Linux kernel, please
./SOME/qpimd/install.texi:these libraries will not be needed when you uses @sc{gnu} C library 2.1
./SOME/qpimd/overview.texi: Quagga is distributed under the @sc{gnu} General Public License.
./SOME/qpimd/overview.texi:which comes with @sc{gnu}/Linux or FreeBSD has some problems with running
./SOME/qpimd/overview.texi:Currently Quagga supports @sc{gnu}/Linux, BSD and Solaris. Porting Quagga
./SOME/qpimd/overview.texi:@sc{gnu}/Linux 2.4.x and higher
./SOME/classpath/texi2pod.pl: s/\@sc\{([^\}]*)\}/\U$1/g;
./SOME/libtmcg/libTMCG.texi: @sc{Christian Schindelhauer}.
./SOME/libtmcg/libTMCG.texi: @sc{Adam Barnett} and @sc{Nigel P. Smart}.
./SOME/libtmcg/libTMCG.texi: @sc{Jens Groth}.
./SOME/libtmcg/libTMCG.texi: @sc{Jens Groth}.
./SOME/libtmcg/libTMCG.texi: @sc{Sebastiaan de Hoogh}, @sc{Berry Schoenmakers}, @sc{Boris Skoric}, and @sc{Jose Villegas}.
./SOME/libtmcg/libTMCG.texi: @sc{Heiko Stamer}.
./SOME/libtmcg/libTMCG.texi: @sc{Heiko Stamer}.
./SOME/libtmcg/libTMCG.texi: @sc{Amos Fiat} and @sc{Adi Shamir}.
./SOME/libtmcg/libTMCG.texi: @sc{Mihir Bellare} and @sc{Phillip Rogaway}.
./SOME/libtmcg/libTMCG.texi: @sc{Mihir Bellare} and @sc{Phillip Rogaway}.
./SOME/libtmcg/libTMCG.texi: @sc{Dan Boneh}.
./SOME/libtmcg/libTMCG.texi: @sc{Rosario Gennaro}, @sc{Daniele Micciancio}, and @sc{Tal Rabin}.
./SOME/libtmcg/libTMCG.texi: @sc{Stanislaw Jarecki} and @sc{Anna Lysyanskaya}.
./SOME/libtmcg/libTMCG.texi: @sc{Christian Cachin}, @sc{Klaus Kursawe}, @sc{Frank Petzold}, and @sc{Victor Shoup}.
./SOME/libtmcg/libTMCG.texi: @sc{Christian Cachin}, @sc{Rachid Guerraoui}, and @sc{Luis Rodrigues}.
./SOME/pdf/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SOME/gnu-social-mode/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./standards/make-stds.texi:@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf,
./standards/make-stds.texi:shell and the @sc{posix} shell), not @code{csh}. Don't use any
./standards/make-stds.texi:special features of @code{ksh} or @code{bash}, or @sc{posix} features
./standards/make-stds.texi:@sc{posix}-specified) options and features of these programs. For
./gnudos/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./groff/groff.texi:Postprocessors for character devices, @sc{PostScript}, @TeX{} DVI, and
./groff/groff.texi:Currently, @code{groff} has postprocessors for @sc{PostScript} devices,
./groff/groff.texi:For @sc{PostScript} printers and previewers.
./groff/groff.texi:comes with a @sc{PostScript} font called @file{freeeuro.pfa}, which
./groff/groff.texi:If you process this with the @sc{PostScript} device (@code{-Tps}),
./groff/groff.texi:for @sc{PostScript}, etc.)@: which interprets the intermediate output of
./groff/groff.texi:rather than fonts. For example, the default setting for @sc{PostScript}
./groff/groff.texi:In the following example, we want to access the @sc{PostScript} font
./groff/groff.texi:The default font position at start-up is@tie{}1; for the @sc{PostScript}
./groff/groff.texi:ordered list of @dfn{special fonts}. By default, the @sc{PostScript}
./groff/groff.texi:since U+00CA (@sc{latin capital letter e with circumflex}) can be
./groff/groff.texi:further decomposed into U+0045 (@sc{latin capital letter e}) and U+0302
./groff/groff.texi:(@sc{combining circumflex accent}). @code{u0045_0302_0301} is thus the
./groff/groff.texi:glyph name for U+1EBE, @sc{latin capital letter e with circumflex and
./groff/groff.texi:names that are composites itself. For example, @code{u0100} (@sc{latin
./groff/groff.texi:Most @sc{PostScript} fonts support the fi and fl ligatures. The C/A/T
./groff/groff.texi:related to its type size! For example, the standard @sc{PostScript}
./groff/groff.texi:@sc{PostScript} into the final document.
./groff/groff.texi:Retrieve the bounding box of the @sc{PostScript} image found in
./groff/groff.texi:@command{troff} into a form suitable for Adobe @sc{PostScript}
./groff/groff.texi:@subsection Embedding @sc{PostScript}
./groff/groff.texi:@sc{PostScript} drawing from file @var{file} bound by the box from
./groff/groff.texi:@var{llx} @var{lly} to @var{urx} @var{ury} (in @sc{PostScript}
./groff/groff.texi:The @sc{PostScript} device is used to create all the image files (for
./groff/groff.texi:@sc{PostScript} file.
./groff/groff.texi:@sc{PostScript} device is called @code{post} and has a resolution of
./groff/groff.texi:PNG images from @sc{PostScript} input. Under GNU/Linux this is
./fog/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./direvent/direvent.texi:compatibility with the @sc{c} preprocessor.
./direvent/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./guile-rpc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./libchop/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./jwhois/jwhois.texi:@sc{jwhois} is an Internet Whois client that contains an extensible
./jwhois/jwhois.texi:Upon execution, @sc{jwhois} searches through its configuration
./jwhois/jwhois.texi:reply from that whois server, @sc{jwhois} can assume the query was
./jwhois/jwhois.texi:@sc{jwhois} uses the following command-line options:
./jwhois/jwhois.texi:@sc{jwhois} is configurable via its configuration file, normally
./jwhois/jwhois.texi:If no configuration file can be found, @sc{jwhois} will default all queries
./jwhois/jwhois.texi:The global options of @sc{jwhois} configure some basic facilities
./jwhois/jwhois.texi:@sc{jwhois} would look for an address @url{se.whois-servers.net}
./jwhois/jwhois.texi:These options control the HTTP support on @sc{jwhois}.
./jwhois/jwhois.texi:program such as @sc{lynx} or @sc{curl}.
./jwhois/jwhois.texi:options to the standard output. @sc{jwhois} catches
./jwhois/jwhois.texi:the browser. If set to @sc{true}, @sc{lynx}-style processing
./jwhois/jwhois.texi:If set to @sc{false}, @sc{w3m}-style processing is enabled,
./jwhois/jwhois.texi:When making a query, @sc{jwhois} looks at the @option{whois-servers}
./jwhois/jwhois.texi:rwhois protocol, this option makes @sc{jwhois} send all
./jwhois/jwhois.texi:are therefore not directly incorporated into the @sc{jwhois} client.
./jwhois/jwhois.texi:It is possible to use these options together with @sc{jwhois} by changing
./gst-libs/gst-libs.texi:@sc{gnu} Smalltalk
./gst-libs/gst-libs.texi:@sc{gnu}
./gst-libs/gst-libs.texi:@title @sc{gnu} Smalltalk Library Reference
./gst-libs/gst-base.texi:@sc{gnu} Smalltalk
./gst-libs/gst-base.texi:@sc{gnu}
./gst-libs/gst-base.texi:@title @sc{gnu} Smalltalk Library Reference
./gst-libs/gst.texi:@sc{gnu} Smalltalk
./gst-libs/gst.texi:@sc{gnu}
./gst-libs/gst.texi:@title @sc{gnu} Smalltalk User's Guide
./gst-libs/gst.texi:languages}. Therefore, even though we have a @sc{gui} environment based
./gst-libs/gst.texi:@multitable {@option{--verbose -aq -c}} {Options seen by @sc{gnu} Smalltalk} {@code{Smalltalk arguments}}
./gst-libs/gst.texi:operations to @code{stdout}. If you load the VisualGST @sc{gui}, instead,
./gst-libs/gst.texi:@gst{} inherits from @sc{iso} C the concept of a @dfn{locale}, that is, a
./gst-libs/gst.texi:Format a monetary value together with its @sc{iso} currency symbol.
./gst-libs/gst.texi:@sc{mo} file format adopted by the @gnu{} @code{gettext} library.
./gst-libs/gst.texi:engine which is now superseded by Swazoo. It is based on the @sc{gpl}'ed
./gst-libs/gst.texi:authentication support, virtual hosting, and @sc{http} 1.1 compliance.
./gst-libs/gst.texi:@gst{} includes an almost complete abstraction of the @sc{tcp}, @sc{udp}
./gst-libs/gst.texi:and @sc{ip} protocols. Although based on the standard @sc{bsd} sockets,
./gst-libs/gst.texi:@sc{ftp}, @sc{http}, @sc{nntp}, @sc{smtp}, @sc{pop3} and @sc{imap}.
./gst-libs/gst.texi:The @sc{xml} parser library for Smalltalk, loaded as package @code{XML}
./gst-libs/gst.texi:includes a validating @sc{xml} parser and Document Object Model.
./gst-libs/gst.texi:and a @sc{xslr} interpreter based on it is bundled with @gst{} as
./gst-libs/gst.texi:@item @sc{gdbm}
./gst-libs/gst.texi:with the library at run-time using @sc{dld}, using either
./gst-libs/gst.texi:run-time; but since some@footnote{The most notable are @sc{aix} and
./gst-libs/tutorial.texi: @gst{} supports completion in the same way as Bash or @sc{gdb}.
./maintain/make-stds.texi:@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf,
./maintain/make-stds.texi:shell and the @sc{posix} shell), not @code{csh}. Don't use any
./maintain/make-stds.texi:special features of @code{ksh} or @code{bash}, or @sc{posix} features
./maintain/make-stds.texi:@sc{posix}-specified) options and features of these programs. For
./fc2d/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./libextractor/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./a2ps/regex.texi:regular expressions. One group---the @sc{gnu} group---is more powerful
./a2ps/regex.texi:but not completely compatible with the other two, namely the @sc{posix}
./a2ps/regex.texi:and Berkeley @sc{unix} groups; its interface was designed specifically
./a2ps/regex.texi:for @sc{gnu}. The other groups have the same interfaces as do the
./a2ps/regex.texi:regular expression functions in @sc{posix} and Berkeley
./a2ps/regex.texi:@sc{unix}.
./a2ps/regex.texi:programs---@sc{gnu} Emacs,
./a2ps/regex.texi:@sc{posix} Awk,
./a2ps/regex.texi:Egrep---in addition to syntaxes for @sc{posix} basic and extended
./a2ps/regex.texi:@sc{posix} generalizes the notion of a character to that of a
./a2ps/regex.texi:Since @sc{posix}'s ``collating element'' preserves the essential idea of
./a2ps/regex.texi:@sc{posix}; @sc{gnu} also uses these. Most operators have more than one
./a2ps/regex.texi:representations, while @sc{posix} dictates others.
./a2ps/regex.texi:system-dependent; for @sc{gnu}, a space or tab
./a2ps/regex.texi:control characters (in the @sc{ascii} encoding, code 0177 and codes
./a2ps/regex.texi:printable characters (in the @sc{ascii} encoding, space
./a2ps/regex.texi:another @samp{-}. For example, in the @sc{ascii} encoding, @samp{)},
./a2ps/regex.texi:English, in @sc{ascii}).
./a2ps/regex.texi:Following are operators that @sc{gnu} defines (and @sc{posix} doesn't).
./a2ps/regex.texi:character set. In the @sc{ascii} encoding, therefore, a syntax table
./a2ps/regex.texi:Following are operators that @sc{gnu} defines (and @sc{posix} doesn't)
./a2ps/regex.texi:character set. In the @sc{ascii} encoding, therefore, a syntax table
./a2ps/regex.texi:C programs. Regex has three interfaces: one designed for @sc{gnu}, one
./a2ps/regex.texi:compatible with @sc{posix} and one compatible with Berkeley @sc{unix}.
./a2ps/regex.texi:@sc{posix} or Berkeley @sc{unix}, you can use these functions. They
./a2ps/regex.texi:In @sc{gnu}, you can both match and search for a given regular
./a2ps/regex.texi:compiled; with @sc{gnu}, you indicate what syntax you want by setting
./a2ps/regex.texi:Matching the @sc{gnu} way means trying to match as much of a string as
./a2ps/regex.texi:your character set. Under the @sc{ascii} encoding, therefore, a fastmap
./a2ps/regex.texi:table, then the @sc{gnu} Regex functions to which you've passed that
./a2ps/regex.texi:character set. Under the @sc{ascii} encoding, therefore, a translate
./a2ps/regex.texi:ones. Under the @sc{ascii} encoding, here's how you could initialize
./a2ps/regex.texi:@sc{gnu} matching or searching function (@pxref{GNU Matching} and
./a2ps/regex.texi:@sc{posix}, on the other hand, requires a different interface: the
./a2ps/regex.texi:@sc{posix} function described in @ref{Freeing POSIX Pattern Buffers},
./a2ps/regex.texi:since the type @code{regex_t}---the type for @sc{posix} pattern
./a2ps/regex.texi:If you're writing code that has to be @sc{posix} compatible, you'll need
./a2ps/regex.texi:to use these functions. Their interfaces are as specified by @sc{posix},
./a2ps/regex.texi:To compile or match a given regular expression the @sc{posix} way, you
./a2ps/regex.texi:must supply a pattern buffer exactly the way you do for @sc{gnu}
./a2ps/regex.texi:(@pxref{GNU Pattern Buffers}). @sc{posix} pattern buffers have type
./a2ps/regex.texi:@code{regex_t}, which is equivalent to the @sc{gnu} pattern buffer
./a2ps/regex.texi:With @sc{posix}, you can only search for a given regular expression; you
./a2ps/regex.texi:as you do for @sc{gnu} (@pxref{GNU Regular Expression Compiling}). See
./a2ps/regex.texi:says to use @sc{posix} Extended Regular Expression syntax; if this isn't
./a2ps/regex.texi:set, then says to use @sc{posix} Basic Regular Expression syntax.
./a2ps/regex.texi:also sets the same fields the same way as does the @sc{gnu} compiling
./a2ps/regex.texi:Matching the @sc{posix} way means trying to match a null-terminated
./a2ps/regex.texi:In @sc{posix}, variables of type @code{regmatch_t} hold analogous
./a2ps/regex.texi:information, but are not identical to, @sc{gnu}'s registers (@pxref{Using
./a2ps/regex.texi:Registers}). To get information about registers in @sc{posix}, pass to
./a2ps/regex.texi:If you're writing code that has to be Berkeley @sc{unix} compatible,
./a2ps/regex.texi:in Berkeley @sc{unix}.
./a2ps/regex.texi:With Berkeley @sc{unix}, you can only search for a given regular
./a2ps/regex.texi:Searching the Berkeley @sc{unix} way means searching in a string
./a2ps/regex.texi:automatically uses a @sc{gnu} fastmap (@pxref{Searching with Fastmaps}).
./m4/m4.texi:encoding, such as @sc{ISO-8859-1}, you will not notice a difference).
./m4/m4.texi:use non-@sc{ascii} characters in quoted strings (@pxref{Changequote}),
./m4/m4.texi:exception of the @sc{nul} character (the zero byte @samp{'\0'}).
./m4/m4.texi:In the @sc{ascii} encoding, the first example deletes all uppercase
./m4/m4.texi:portable to @sc{ebcdic} or other encodings. The fourth example shows a
./guile-cv/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./sqltutor/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gawk/gawkinet.texi:@headitem @sc{protocol} @tab @sc{local port} @tab @sc{host name}
./gawk/gawkinet.texi:@tab @sc{remote port} @tab @sc{Resulting connection-level behavior}
./gawk/gawkinet.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gawk/gawk.texi:@samp{.} does not match the @sc{nul}
./gawk/gawk.texi:Otherwise, @sc{nul} is just another character. Other versions of @command{awk}
./gawk/gawk.texi:may not be able to match the @sc{nul} character.
./gawk/gawk.texi:You might think that for text files, the @sc{nul} character, which
./gawk/gawk.texi:@command{gawk} in fact accepts this, and uses the @sc{nul}
./gawk/gawk.texi:GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
./gawk/gawk.texi:@sc{nul} character as the string terminator. In effect, this means that
./gawk/gawk.texi:It happens that recent versions of @command{mawk} can use the @sc{nul}
./gawk/gawk.texi:@command{mawk} does not allow embedded @sc{nul} characters in strings.
./gawk/gawk.texi:You might think that for text files, the @sc{nul} character, which
./gawk/gawk.texi:@command{gawk} in fact accepts this, and uses the @sc{nul}
./gawk/gawk.texi:GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
./gawk/gawk.texi:@sc{nul} character as the string terminator. In effect, this means that
./gawk/gawk.texi:It happens that recent versions of @command{mawk} can use the @sc{nul}
./gawk/gawk.texi:@command{mawk} does not allow embedded @sc{nul} characters in strings.
./gawk/gawk.texi:eight-bit ASCII characters, including ASCII @sc{nul} (character code zero).
./gawk/gawk.texi:String values maintain both pointer and length, because embedded @sc{nul}
./gawk/gawk.texi:@sc{nul}-terminated. Thus it is safe to pass such string values to
./gawk/gawk.texi:allows embedded @sc{nul} characters in string data, before using the data
./gawk/gawk.texi:require more work. Because @command{gawk} allows embedded @sc{nul} bytes
./gawk/gawk.texi:Message-Id: <9510311732.AA28472@scalpel.netlabs.com>
./gawk/gawk.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./txinfsnp/texinfo/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./multiboot/multiboot.texi:This specification is primarily targeted at @sc{pc}, since they are the
./multiboot/multiboot.texi:even among free Unix-like @sc{pc}-based operating systems --- generally
./multiboot/multiboot.texi:to @sc{elf}. It is highly desirable for boot loaders not to have to be
./multiboot/multiboot.texi:@sc{pc}'s I/O region or other reserved areas, and of course it should
./multiboot/multiboot.texi:provided if the kernel image is in @sc{elf} format, but it @emph{must}
./multiboot/multiboot.texi:are in @sc{elf} format or contain the load address information embedded
./multiboot/multiboot.texi:@dfn{normal working order}, i.e. as initialized by the @sc{bios} (or
./multiboot/multiboot.texi:operating system should be able to make @sc{bios} calls and such after
./multiboot/multiboot.texi:being loaded, as long as it does not overwrite the @sc{bios} data
./multiboot/multiboot.texi:@sc{pic} programmed with the normal @sc{bios}/DOS values, even if it
./multiboot/multiboot.texi:field is valid, and indicates which @sc{bios} disk device the boot
./multiboot/multiboot.texi:@sc{bios} disk, then this field must not be present (bit 3 must be
./multiboot/multiboot.texi:The most significant byte contains the @sc{bios} drive number
./multiboot/multiboot.texi:@sc{bios} INT 0x13 low-level disk interface: e.g. 0x00 for the first
./multiboot/multiboot.texi:a set of zero-terminated @sc{ascii} strings (plus sizeof(unsigned long) in
./multiboot/multiboot.texi:(@samp{shdr_num}, etc.) in the Executable and Linkable Format (@sc{elf})
./multiboot/multiboot.texi:physical address fields of the @sc{elf} section header then refer to where
./multiboot/multiboot.texi:the sections are in memory (refer to the i386 @sc{elf} documentation for
./multiboot/multiboot.texi:memory map of the machine provided by the @sc{bios}. @samp{mmap_addr} is
./multiboot/multiboot.texi:value of 1 indicates available @sc{ram}, value of 3 indicates usable memory
./multiboot/multiboot.texi:The map provided is guaranteed to list all standard @sc{ram} that should
./multiboot/multiboot.texi:@sc{bios}. @samp{drive_cylinders} contains the number of the
./multiboot/multiboot.texi:for the drive in the @sc{bios} code. The array consists of zero or more
./multiboot/multiboot.texi:drive actually (such as @sc{dma} controller's ports).
./multiboot/multiboot.texi:is valid, and indicates the address of the @sc{rom} configuration table
./multiboot/multiboot.texi:returned by the @dfn{GET CONFIGURATION} @sc{bios} call. If the @sc{bios}
./multiboot/multiboot.texi:valid, and contains the physical address of an @sc{apm} table defined as
./multiboot/multiboot.texi:If bit 11 in the @samp{flags} is set, the @sc{vbe} table is available.
./multiboot/multiboot.texi:the physical addresses of @sc{vbe} control information returned by the
./multiboot/multiboot.texi:@sc{vbe} Function 00h and @sc{vbe} mode information returned by the
./multiboot/multiboot.texi:@sc{vbe} Function 01h, respectively.
./multiboot/multiboot.texi:specified in @sc{vbe} 3.0.
./multiboot/multiboot.texi:defined in @sc{vbe} 2.0+. If this information is not available, those
./multiboot/multiboot.texi:fields contain zero. Note that @sc{vbe} 3.0 defines another protected
./multiboot/multiboot.texi:The fields for the graphics table are designed for @sc{vbe}, but
./multiboot/multiboot.texi:Multiboot boot loaders may simulate @sc{vbe} on non-@sc{vbe} modes, as
./multiboot/multiboot.texi:if they were @sc{vbe} modes.
./multiboot/multiboot.texi:If bit 12 in the @samp{flags} is set, the @sc{Framebuffer} table is available.
./multiboot/multiboot.texi:@sc{bios} interfaces, or the newest ones are not available (see
./multiboot/multiboot.texi:@sc{bios} drive maps to which device driver in an operating system is
./multiboot/multiboot.texi:this problem, there are 2 @sc{bios} device mapping techniques
./multiboot/multiboot.texi:@sc{bios} interface, passing along any extra data to be interpreted by
./multiboot/multiboot.texi:remaining @sc{bios} devices when not all of them have operating system
./multiboot/multiboot.texi:The data on some @sc{bios} devices might be identical (so the part
./multiboot/multiboot.texi:reading the drives from the @sc{bios} should have some mechanism to give
./multiboot/multiboot.texi:There might be extra drives not accessible from the @sc{bios} which are
./multiboot/multiboot.texi:identical to some drive used by the @sc{bios} (so it should be capable
./multiboot/multiboot.texi:mappings for the device drivers writing into @sc{pc} @sc{ram}. Keep the
./multiboot/multiboot.texi:original copies for the @dfn{clean @sc{bios} virtual machine} to be
./multiboot/multiboot.texi:For each device driver brought online, determine which @sc{bios} devices
./multiboot/multiboot.texi:Create a @dfn{clean @sc{bios} virtual machine}.
./multiboot/multiboot.texi:For each device driver, given how many of the @sc{bios} devices were
./multiboot/multiboot.texi:@sc{bios} numbers, but they pretty much always count from the lowest
./rawtools/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./libcdio/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/emacs/doc/emacs/text.texi:The curved single quote characters are U+2018 @sc{left single quotation
./SAVANNAH-crawl/emacs/doc/emacs/text.texi:mark} and U+2019 @sc{right single quotation mark}; the curved double quotes
./SAVANNAH-crawl/emacs/doc/emacs/text.texi:are U+201C @sc{left double quotation mark} and U+201D @sc{right double
./SAVANNAH-crawl/emacs/doc/emacs/mule.texi:The special character @code{RIGHT-TO-LEFT MARK}, or @sc{rlm}, forces
./SAVANNAH-crawl/emacs/doc/emacs/mule.texi:@code{LEFT-TO-RIGHT MARK}, or @sc{lrm} forces the left-to-right
./SAVANNAH-crawl/emacs/doc/emacs/mule.texi:In a GUI session, the @sc{lrm} and @sc{rlm} characters display as very
./SAVANNAH-crawl/emacs/doc/emacs/msdos.texi:come with such a program, although several ports of @sc{gnu} @code{ls}
./SAVANNAH-crawl/emacs/doc/emacs/msdos.texi:Emulate @sc{gnu} systems; this is the default. This sets
./SAVANNAH-crawl/emacs/doc/emacs/msdos.texi:platforms prefer the @sc{gnu} defaults.
./SAVANNAH-crawl/emacs/doc/emacs/msdos.texi:displaying a given non-@sc{ascii} character might fail for some rare
./SAVANNAH-crawl/emacs/doc/emacs/search.texi:such as U+249C @sc{parenthesized latin small letter a} and U+2100
./SAVANNAH-crawl/emacs/doc/emacs/search.texi:@sc{account of} (which looks like a small @code{a} over @code{c}).
./SAVANNAH-crawl/emacs/doc/emacs/search.texi:@sc{latin small ligature ff}. Character sequences that are not identical,
./SAVANNAH-crawl/emacs/doc/emacs/basic.texi:which is Unicode code-point U+2018 @sc{left single quotation mark},
./SAVANNAH-crawl/emacs/doc/misc/emacs-mime.texi:* Charset Translation:: How charsets are mapped from @sc{mule} to @acronym{MIME}.
./SAVANNAH-crawl/emacs/doc/misc/emacs-mime.texi:If you are running a non-@sc{mule} Emacs, this process is simple: If the
./SAVANNAH-crawl/emacs/doc/misc/emacs-mime.texi:Things are slightly more complicated when running Emacs with @sc{mule}
./SAVANNAH-crawl/emacs/doc/misc/emacs-mime.texi:support. In this case, a list of the @sc{mule} charsets used in the
./SAVANNAH-crawl/emacs/doc/misc/emacs-mime.texi:part is obtained, and the @sc{mule} charsets are translated to
./SAVANNAH-crawl/emacs/doc/misc/emacs-mime.texi:When running Emacs with @sc{mule} support, the preferences for which
./SAVANNAH-crawl/emacs/doc/misc/org.texi:Richard @@@@texinfo:@@sc@{@@@@Stallman@@@@texinfo:@}@@@@ commence' GNU.
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:form is a regular Lisp variable. But the @sc{car}s and @sc{cdr}s of lists,
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:It searches for an element of the list whose @sc{car} equals
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:then on the @sc{cdr}s of those lists, and so on, until the
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:@sc{car}s of the advancing pointers.
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:rearranging the @sc{cdr} pointers in suitable fashion.
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:list (where the @sc{cdr}-chain forms a loop rather than terminating
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:argument becomes the @sc{cdr} of the last cell constructed.
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:@var{y} are both cons cells, their @sc{car}s and @sc{cdr}s are
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:on, and compares against @var{old}, both @sc{car}s and @sc{cdr}s
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:function, if any), is compared with the @sc{car}s of
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:@sc{cdr}.
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:If a match is found, it returns the cons cell whose @sc{car} was
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:any of its @sc{cdr}s.
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:element whose @sc{car} matches (in the sense of @code{:test},
./SAVANNAH-crawl/emacs/doc/misc/cl.texi:This function searches for an element whose @sc{cdr} matches
./SAVANNAH-crawl/emacs/doc/misc/widget.texi:A list whose @sc{car} is the widget representing the currently chosen
./SAVANNAH-crawl/emacs/doc/misc/widget.texi:List whose @sc{car} is the type of the list elements.
./SAVANNAH-crawl/emacs/doc/misc/widget.texi:The value of a @code{cons} widget must be a cons-cell whose @sc{car}
./SAVANNAH-crawl/emacs/doc/misc/widget.texi:and @sc{cdr} have two specified types. It uses this syntax:
./SAVANNAH-crawl/emacs/doc/misc/widget.texi:and @kbd{C-o} (suggested by @sc{rms}).
./SAVANNAH-crawl/emacs/doc/misc/widget.texi:whether you want to add or delete an item (@sc{rms} wanted to git rid of
./SAVANNAH-crawl/emacs/doc/misc/sieve.texi:for talking to a server with the @sc{managesieve} protocol.
./SAVANNAH-crawl/emacs/doc/misc/ede.texi:@scindex ede-sourcecode
./SAVANNAH-crawl/emacs/doc/misc/message.texi:Each list element should be a cons, where the @sc{car} should be the
./SAVANNAH-crawl/emacs/doc/misc/message.texi:name of a header (e.g., @code{CC}) and the @sc{cdr} should be the header
./SAVANNAH-crawl/emacs/doc/misc/message.texi:In addition, you can enter conses into this list. The @sc{car} of this cons
./SAVANNAH-crawl/emacs/doc/misc/message.texi:the @sc{cdr} can either be a string to be entered verbatim as the value of
./SAVANNAH-crawl/emacs/doc/misc/message.texi:If the list contains a cons where the @sc{car} of the cons is
./SAVANNAH-crawl/emacs/doc/misc/message.texi:@code{optional}, the @sc{cdr} of this cons will only be inserted if it is
./SAVANNAH-crawl/emacs/doc/misc/message.texi:is @code{iso-8859-1} on non-@sc{mule} Emacsen; otherwise @code{nil},
./SAVANNAH-crawl/emacs/doc/misc/message.texi:which means ask the user. (This variable is used only on non-@sc{mule}
./SAVANNAH-crawl/emacs/doc/misc/message.texi:Emacs MIME Manual}, for details on the @sc{mule}-to-@acronym{MIME}
./SAVANNAH-crawl/emacs/doc/misc/message.texi:@sc{car} is a function and the @sc{cdr} is the list of arguments, or
./SAVANNAH-crawl/emacs/doc/misc/autotype.texi:@code{auto-insert-alist}. The @sc{car}s of this list are each either
./SAVANNAH-crawl/emacs/doc/misc/autotype.texi:the same mode in Emacs can be distinguished. The @sc{car}s may also
./SAVANNAH-crawl/emacs/doc/misc/autotype.texi: When a matching element is found, the @sc{cdr} says what to do. It may
./SAVANNAH-crawl/emacs/doc/misc/trampver.texi:@set tramp @sc{Tramp}
./SAVANNAH-crawl/emacs/doc/misc/viper.texi:dm@@scs.cs.nyu.edu (David Mazieres),
./SAVANNAH-crawl/emacs/doc/misc/sasl.texi:@sc{sasl} is short for @dfn{Simple Authentication and Security Layer}.
./SAVANNAH-crawl/emacs/doc/misc/sasl.texi:The toplevel interface of this library is inspired by Java @sc{sasl}
./SAVANNAH-crawl/emacs/doc/misc/sasl.texi:A mechanism (@code{sasl-mechanism} object) is a schema of the @sc{sasl}
./SAVANNAH-crawl/emacs/doc/misc/reftex.texi:@c dominik@@science.uva.nl
./SAVANNAH-crawl/emacs/doc/misc/dbus.texi:A D-Bus compound type is always represented as a list. The @sc{car}
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:Things got a bit more complicated with @sc{gnus}. In addition to
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:the @file{.newsrc} file.) @sc{gnus} would read whichever one of these
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:@sc{gnus} and other newsreaders.
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:@sc{gnus 4.1}, where you had explicit keystrokes for everything under
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:correctly is if you use an @acronym{NNTP} server that supports @sc{xover}
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:even with @sc{xover} by registering the @code{Xref} lines of all
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:@cindex @sc{mode reader}
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:not easy. People who prefer proper mail readers should try @sc{vm}
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:where the @sc{car} of a cell contains the key, and the @sc{cdr}
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:Two summary functions for editing a @sc{gnus} kill file:
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:@sc{gnus} was written by Masanobu @sc{Umeda}. When autumn crept up in
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:pronounced ``news'' as @sc{Umeda} intended, which makes it a more
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:``@sc{gnus}''. New vs. old.
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:reading and fetching news. Expanding on @sc{Umeda}-san's wise decision
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:Gnus was designed to be fully compatible with @sc{gnus}. Almost all key
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:All code that relies on knowledge of @sc{gnus} internals will probably
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:fact, you should probably remove all old @sc{gnus} packages (and other
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:does what you have written code to make @sc{gnus} do. (Snicker.)
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:Gnus understands all @sc{gnus} startup files.
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:@sc{gnus} internals should suffer no problems. If problems occur,
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:controlling where and how to send @sc{authinfo} to @acronym{NNTP} servers.
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:normal @sc{head} format.
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:been running @sc{gnus}, you need to exit Emacs and start it up again before
./SAVANNAH-crawl/emacs/doc/misc/gnus.texi:@sc{gnus} introduced a concept that I found so useful that I've started
./SAVANNAH-crawl/emacs/doc/misc/url.texi:@cindex @sc{socks}
./SAVANNAH-crawl/emacs/doc/misc/url.texi:Use if the firewall has a @sc{socks} gateway running on it. The
./SAVANNAH-crawl/emacs/doc/misc/url.texi:@sc{socks} v5 protocol is defined in RFC 1928.
./SAVANNAH-crawl/emacs/doc/misc/url.texi:the @sc{socks} server.
./SAVANNAH-crawl/emacs/doc/misc/url.texi:@sc{socks} server. By default this is your login name.
./SAVANNAH-crawl/emacs/doc/misc/url.texi:@sc{socks} server; it is 5 by default.
./SAVANNAH-crawl/emacs/doc/misc/url.texi:@c @sc{ip} addresses which specify a range of @sc{ip} addresses, an @sc{ip}
./SAVANNAH-crawl/emacs/doc/misc/url.texi:@c address and a netmask, a domain name or a unique hostname or @sc{ip}
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:MH has the ability to display @dfn{@sc{mime}} (Multipurpose Internet
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:the MH book.} from the shell to read @sc{mime} messages@footnote{You
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:be on. Otherwise, you'll see the @sc{mime} body parts rather than text
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:text (including @sc{html}) and images.
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:in the MH book.} is compiled with the @sc{berk} option (which many
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:Compose @sc{mime} message from MH-style directives
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:Compose @sc{mime} message from MML tags (@code{mh-mml-to-mime}).
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:Type of @sc{mime} message tags in messages (default: @samp{MML} if
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:@sc{mime} (Multipurpose Internet Mail Extensions)
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:protocol@footnote{@sc{mime} is defined in
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:@sc{mime} protocol allows you to incorporate images, sound, video,
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:In addition to MH-style directives, MH-E also supports MML (@sc{mime}
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:The MH-E @sc{mime} commands require a @dfn{media type} for each body
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:You can also create your own @sc{mime} body parts. In the following
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:Mail may be forwarded with @sc{mime} using the command @kbd{C-c C-m
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:When you are finished editing a @sc{mime} message, it might look like this:
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:@i{MH-E @sc{mime} draft}
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:However, you may take a sneak preview of the @sc{mime} encoding if you
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:The following screen shows the @sc{mime} encoding specified by the
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:@i{MH-E @sc{mime} draft ready to send}
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:collection and support for composing @sc{mime} messages. (Reading
./SAVANNAH-crawl/emacs/doc/misc/mh-e.texi:@sc{mime} messages remains to be done, alas.) While writing this book,
./SAVANNAH-crawl/emacs/doc/misc/ChangeLog.1: * widget.texi, woman.texi: Replace @sc{ascii} and ASCII with
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:the @sc{car} slot and the @sc{cdr} slot. Each slot can @dfn{hold} any
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:Lisp object. We also say that the @sc{car} of this cons cell is
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:whatever object its @sc{car} slot currently holds, and likewise for
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:the @sc{cdr}.
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:@sc{cdr} slot of each cons cell holds either the next cons cell or the
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:@sc{car} slot of the cons cell holds the element, and its @sc{cdr}
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:element in the list. The @sc{cdr} slot of the last cons cell is set to
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi: The names @sc{car} and @sc{cdr} derive from the history of Lisp. The
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:decrement; @sc{car} was an instruction to extract the contents of
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:the address part of a register, and @sc{cdr} an instruction to extract
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi: In this example, the first box, which holds the @sc{car} of the first
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:box, holding the @sc{cdr} of the first cons cell, refers to the next
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:pair of boxes, the second cons cell. The @sc{car} of the second cons
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:cell is @code{violet}, and its @sc{cdr} is the third cons cell. The
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:@sc{cdr} of the third (and last) cons cell is @code{nil}.
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:represents the @sc{car} and @sc{cdr} explicitly. In this syntax,
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:@code{(@var{a} .@: @var{b})} stands for a cons cell whose @sc{car} is
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:the object @var{a} and whose @sc{cdr} is the object @var{b}. Dotted
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:pair notation is more general than list syntax because the @sc{cdr}
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:list, the dotted pair notation is only used if the @sc{cdr} of a cons
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:conveniently a chain of cons cells with a non-@code{nil} final @sc{cdr}.
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:@sc{cdr} of the final cons cell. For example, @code{(rose violet
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:@code{buttercup} in the @sc{cdr} of a cons cell whose @sc{cdr} is already
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:list whose elements are cons cells. In each element, the @sc{car} is
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:considered a @dfn{key}, and the @sc{cdr} is considered an
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:in the @sc{car} of the @sc{cdr}.) Association lists are often used as
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:list whose first element is the symbol @code{macro} and whose @sc{cdr}
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:primitive type---it is actually a list whose @sc{car} is
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:@code{frame-configuration} and whose @sc{cdr} is an alist. Each alist
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:element describes one frame, which appears as the @sc{car} of that
./SAVANNAH-crawl/emacs/doc/lispref/objects.texi:a list whose @sc{car} is the symbol @code{keymap}.
./SAVANNAH-crawl/emacs/doc/lispref/text.texi:kill ring list, whose @sc{car} is the text to yank next. We say it
./SAVANNAH-crawl/emacs/doc/lispref/text.texi:@sc{car} of that link. Kill commands, which change the kill ring, also
./SAVANNAH-crawl/emacs/doc/lispref/text.texi:of the value of @code{kill-ring}, and its @sc{car} is the kill string
./SAVANNAH-crawl/emacs/doc/lispref/text.texi:Its value is a cons cell whose @sc{car} is the property value, the
./SAVANNAH-crawl/emacs/doc/lispref/text.texi:arguments. Its @sc{cdr} is the overlay in which the property was
./SAVANNAH-crawl/emacs/doc/lispref/text.texi:If @var{position} is at the end of @var{object}, both the @sc{car} and
./SAVANNAH-crawl/emacs/doc/lispref/text.texi:the @sc{cdr} of the value are @code{nil}.
./SAVANNAH-crawl/emacs/doc/lispref/debugging.texi:@sc{car} of the evaluated list, or a @code{lambda} expression in the
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:this property for the character U+2155 @sc{vulgar fraction one
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:example mapping for U+00DF @sc{latin small letter sharp s} is
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:be empty). For example mapping for U+0130 @sc{latin capital letter i
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:consisting of @sc{latin small letter i} followed by U+0307
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:@sc{combining dot above}). For characters with no special mapping,
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:U+FB01 @sc{latin small ligature fi} the value is @code{"Fi"}. For
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:The @sc{cdr} of the element, @var{coding}, should be either a coding
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:@var{coding} is a cons cell containing two coding systems, its @sc{car}
./SAVANNAH-crawl/emacs/doc/lispref/nonascii.texi:specifies the coding system for decoding, and its @sc{cdr} specifies the
./SAVANNAH-crawl/emacs/doc/lispref/backups.texi:deletion. @code{find-backup-file-name} returns a list whose @sc{car} is
./SAVANNAH-crawl/emacs/doc/lispref/backups.texi:the name for the new backup file and whose @sc{cdr} is a list of backup
./SAVANNAH-crawl/emacs/doc/lispref/backups.texi:those versions by excluding them from the @sc{cdr} of the value.
./SAVANNAH-crawl/emacs/doc/lispref/functions.texi:as its @sc{car} to make local variables and give them values. In the
./SAVANNAH-crawl/emacs/doc/lispref/functions.texi: ;; @r{apply function to @sc{car}s.}
./SAVANNAH-crawl/emacs/doc/lispref/functions.texi:forms self-quoting: evaluating a form whose @sc{car} is @code{lambda}
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi: Each keymap is a list whose @sc{car} is the symbol @code{keymap}. The
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:@sc{car} is @code{keymap}, or for a symbol whose function definition
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:@sc{cdr} of the element; a list with the map as the second element will
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:not do. The @sc{cdr} can be either a keymap (a list) or a symbol whose
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:If the @sc{car} of @var{list} is the symbol @code{keymap}, then the list
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:If the @sc{car} of @var{list} is @code{lambda}, then the list is a
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:The @sc{car}, @var{item-string}, is the string to be displayed in the
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:The @sc{car}, @var{type}, says which: it should be @code{:toggle} or
./SAVANNAH-crawl/emacs/doc/lispref/keymaps.texi:@code{:radio}. The @sc{cdr}, @var{selected}, should be a form; the
./SAVANNAH-crawl/emacs/doc/lispref/windows.texi:specifies the number of rectangles to return and whose @sc{cdr}, if
./SAVANNAH-crawl/emacs/doc/lispref/windows.texi:whose @sc{car} specifies the uppermost and whose @sc{cdr} specifies the
./SAVANNAH-crawl/emacs/doc/lispref/windows.texi:The @sc{car} of each entry of this alist is a symbol specifying the
./SAVANNAH-crawl/emacs/doc/lispref/windows.texi:parameter. The @sc{cdr} should be one of the following:
./SAVANNAH-crawl/emacs/doc/lispref/windows.texi:The value of this parameter is a cons cell whose @sc{car} and
./SAVANNAH-crawl/emacs/doc/lispref/windows.texi:@sc{cdr}, if non-@code{nil}, specify the minimum values (in columns)
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:slot is known as the @sc{car}, and the other is known as the @sc{cdr}.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:(These names are traditional; see @ref{Cons Cell Type}.) @sc{cdr} is
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: We say that ``the @sc{car} of this cons cell is'' whatever object
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:its @sc{car} slot currently holds, and likewise for the @sc{cdr}.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:of the list. By convention, the @sc{car}s of the cons cells hold the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:elements of the list, and the @sc{cdr}s are used to chain the list
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:(this asymmetry between @sc{car} and @sc{cdr} is entirely a matter of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:convention; at the level of cons cells, the @sc{car} and @sc{cdr}
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:slots have similar properties). Hence, the @sc{cdr} slot of each cons
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: Also by convention, the @sc{cdr} of the last cons cell in a list is
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:considered to have @code{nil} as its @sc{cdr} (and also as its
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{car}).
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: Hence, the @sc{cdr} of a proper list is always a proper list. The
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr} of a nonempty proper list is a proper list containing all the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: If the @sc{cdr} of a list's last cons cell is some value other than
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr} could point to one of the previous cons cells in the list.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:list to see the @sc{cdr} of the final cons cell, it won't care.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:cons cell @var{cons-cell}. In other words, it returns the @sc{car} of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:cons cell @var{cons-cell}. In other words, it returns the @sc{cdr} of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This function lets you take the @sc{car} of a cons cell while avoiding
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:errors for other data types. It returns the @sc{car} of @var{object} if
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This function lets you take the @sc{cdr} of a cons cell while
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:avoiding errors for other data types. It returns the @sc{cdr} of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This macro provides a convenient way to examine the @sc{car} of a
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:saves the @sc{cdr} into @var{listname}, then returns the removed
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:are numbered starting with zero, so the @sc{car} of @var{list} is
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This function returns the @var{n}th @sc{cdr} of @var{list}. In other
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{car}, and @var{object2} the @sc{cdr}. It then returns the new
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:by following all the @sc{cdr}s and then replacing the terminating
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr} of the last cons cell in the new list. If the final argument
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:dotted list since its final @sc{cdr} is not @code{nil} as required
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:resulting list. Instead, the sequence becomes the final @sc{cdr}, like
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:cons cell, this makes a new cons cell with the same @sc{car} and
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr}, then recursively copies the @sc{car} and @sc{cdr} in the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This macro creates a new list whose @sc{car} is @var{element} and
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:whose @sc{cdr} is the list specified by @var{listname}, and saves that
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: You can modify the @sc{car} and @sc{cdr} contents of a cons cell with the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:new @sc{car} or @sc{cdr}.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: Changing the @sc{car} of a cons cell is done with @code{setcar}. When
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This function stores @var{object} as the new @sc{car} of @var{cons},
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:replacing its previous @sc{car}. In other words, it changes the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{car} slot of @var{cons} to refer to @var{object}. It returns the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:storing a new @sc{car} into the cons changes one element of each of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:;; @r{Replace the @sc{car} of a shared link.}
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:;; @r{Replace the @sc{car} of a link that is not shared.}
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: The lowest-level primitive for modifying a @sc{cdr} is @code{setcdr}:
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This function stores @var{object} as the new @sc{cdr} of @var{cons},
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:replacing its previous @sc{cdr}. In other words, it changes the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr} slot of @var{cons} to refer to @var{object}. It returns the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: Here is an example of replacing the @sc{cdr} of a list with a
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:unchanged, because it resides in the @sc{car} of the list, and is not
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:reached via the @sc{cdr}.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr}s of the cons cells in the list. For example, here we delete
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:the @sc{cdr} of the first cons cell:
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:exists and its @sc{car} is still @code{b}, but it no longer forms part
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi: It is equally easy to insert a new element by changing @sc{cdr}s:
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:modifying the @sc{cdr}s of their component cons cells. These functions
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@emph{not} copied. Instead, the last @sc{cdr} of each of the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:removing it involves changing the @sc{cdr}s (@pxref{Setcdr}).
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@dfn{associations}: the @sc{car} of each cons cell is the @dfn{key}, and the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr} is the @dfn{associated value}.@footnote{This usage of ``key''
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:associated with the @emph{list} @code{(2 3)}, which is the @sc{cdr} of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:value in the @sc{car} of the @sc{cdr} of the element. Here is an
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:information---even a list of other items---in the @sc{cdr} of the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{cdr}. One disadvantage is that you cannot use @code{rassq} (see
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:associated value in the @sc{cdr} of the element; the value associated
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:association in @var{alist} has a @sc{car} equal to @var{key}. For
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:a @sc{cdr} @code{equal} to @var{value}.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@code{rassoc} is like @code{assoc} except that it compares the @sc{cdr} of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:each @var{alist} association instead of the @sc{car}. You can think of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@var{alist} has a @sc{car} @code{eq} to @var{key}. This function is
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:a @sc{cdr} @code{eq} to @var{value}.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@code{rassq} is like @code{assq} except that it compares the @sc{cdr} of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:each @var{alist} association instead of the @sc{car}. You can think of
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@code{rassq} cannot search for a value stored in the @sc{car}
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:of the @sc{cdr} of an element:
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:In this case, the @sc{cdr} of the association @code{(lily white)} is not
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:the element's @sc{car} (if it is a cons) against @var{key}, by calling
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@var{test} with two arguments: the element or its @sc{car}, and
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:If the element is a cons, then the value is the element's @sc{cdr}.
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This function deletes from @var{alist} all the elements whose @sc{car}
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:This function deletes from @var{alist} all the elements whose @sc{cdr}
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:compares the @sc{cdr} of each @var{alist} association instead of the
./SAVANNAH-crawl/emacs/doc/lispref/lists.texi:@sc{car}.
./SAVANNAH-crawl/emacs/doc/lispref/files.texi:@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
./SAVANNAH-crawl/emacs/doc/lispref/files.texi:@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
./SAVANNAH-crawl/emacs/doc/lispref/files.texi:@sc{gnu} @code{Coreutils} Manual}, for a description of file mode
./SAVANNAH-crawl/emacs/doc/lispref/control.texi:@var{clause} in the @code{cond} must be a list. The @sc{car} of this
./SAVANNAH-crawl/emacs/doc/lispref/control.texi:@sc{car} of an integer or move forward a character at the end of the
./SAVANNAH-crawl/emacs/doc/lispref/control.texi:error message is the @sc{car} of @var{data} (that must be a string).
./SAVANNAH-crawl/emacs/doc/lispref/loading.texi:libraries that are preloaded at startup). It is a list whose @sc{car}
./SAVANNAH-crawl/emacs/doc/lispref/loading.texi:The value of @code{load-history} may have one element whose @sc{car} is
./SAVANNAH-crawl/emacs/doc/lispref/sequences.texi:cons cells forming @var{sequence} by changing @sc{cdr}s. A nondestructive
./SAVANNAH-crawl/emacs/doc/lispref/sequences.texi:Sorting does not change the @sc{car}s of the cons cells in @var{sequence};
./SAVANNAH-crawl/emacs/doc/lispref/sequences.texi:@var{sequence} still has @code{a} in its @sc{car} after sorting, but it now
./SAVANNAH-crawl/emacs/doc/lispref/sequences.texi:@sc{cdr}s. For example:
./SAVANNAH-crawl/emacs/doc/lispref/edebug.texi:argument may then be a dotted list. Alternatively, the last @sc{cdr} of a
./SAVANNAH-crawl/emacs/doc/lispref/commands.texi:@sc{ascii} control characters such as @kbd{C-a} have special basic
./SAVANNAH-crawl/emacs/doc/lispref/commands.texi:as lists. The @sc{car} of the list is the event type; this says which
./SAVANNAH-crawl/emacs/doc/lispref/commands.texi:events that are lists, the event type is the symbol in the @sc{car} of
./SAVANNAH-crawl/emacs/doc/lispref/commands.texi:if it is a list, the @sc{car} of that list (which should be a number) is
./SAVANNAH-crawl/emacs/doc/lispref/macros.texi: A Lisp macro object is a list whose @sc{car} is @code{macro}, and
./SAVANNAH-crawl/emacs/doc/lispref/macros.texi:whose @sc{cdr} is a function. Expansion of the macro works
./SAVANNAH-crawl/emacs/doc/lispref/macros.texi:(Note that the @sc{cdr} of this list is a lambda expression.) This
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:non-@code{nil}, the string with the single character @sc{U+2026
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:additional elements describing the @sc{gsub} and @sc{gpos} features
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:additional elements describing the @sc{gsub} and @sc{gpos} features
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:@sc{left-to-right mark}, but excluding characters that have graphic
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:images, such as U+00AD @sc{soft hyphen}.
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:their parent buffer is reordered. This is because plain-@sc{ascii}
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:or overlay string includes non-@sc{ascii} characters, these characters
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:Append the special character U+200E @sc{left-to-right mark}, or
./SAVANNAH-crawl/emacs/doc/lispref/display.texi:U+200F @sc{right-to-left mark}, or @acronym{RLM}, instead.) This
./SAVANNAH-crawl/emacs/doc/lispref/ChangeLog.1: * syntax.texi, text.texi: Replace @sc{foo} with @acronym{FOO}.
./SAVANNAH-crawl/emacs/doc/lispref/os.texi:The @sc{car}, @var{option}, is a string, the name of a command-line
./SAVANNAH-crawl/emacs/doc/lispref/os.texi:If it is @code{nil}, then it uses @sc{cbreak} mode. The default
./SAVANNAH-crawl/emacs/doc/lispref/os.texi:setting is system-dependent. Some systems always use @sc{cbreak} mode
./SAVANNAH-crawl/emacs/doc/lispref/os.texi:If @var{flow} is non-@code{nil}, then Emacs uses @sc{xon/xoff}
./SAVANNAH-crawl/emacs/doc/lispref/os.texi:has no effect except in @sc{cbreak} mode.
./SAVANNAH-crawl/emacs/doc/lispref/os.texi:@code{nil}, Emacs is using @sc{cbreak} mode.
./SAVANNAH-crawl/emacs/doc/lispref/os.texi:is non-@code{nil} if Emacs uses @sc{xon/xoff} (@kbd{C-q}, @kbd{C-s})
./SAVANNAH-crawl/emacs/doc/lispref/frames.texi:@sc{car}, the @sc{cdr} of that cell specifies the width of the frame's
./SAVANNAH-crawl/emacs/doc/lispref/frames.texi:the frame's width ratio is preserved if the @sc{car} of the cell is
./SAVANNAH-crawl/emacs/doc/lispref/frames.texi:the @sc{car} of the cell is either @code{t} or @code{height-only}. The
./SAVANNAH-crawl/emacs/doc/lispref/frames.texi:left position ratio is preserved if the @sc{cdr} of the cell is either
./SAVANNAH-crawl/emacs/doc/lispref/frames.texi:the @sc{cdr} of the cell is either @code{t} or @code{top-only}.
./SAVANNAH-crawl/emacs/doc/lispref/streams.texi:is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
./SAVANNAH-crawl/emacs/doc/lispref/streams.texi:@sc{cdr} is the number 5.
./SAVANNAH-crawl/emacs/doc/lispref/streams.texi:@var{string}. It returns a cons cell whose @sc{car} is that expression,
./SAVANNAH-crawl/emacs/doc/lispref/streams.texi:and whose @sc{cdr} is an integer giving the position of the next
./SAVANNAH-crawl/emacs/doc/lispref/minibuf.texi:a string, or a cons cell whose @sc{car} is either a string or a symbol
./SAVANNAH-crawl/emacs/doc/lispref/minibuf.texi:@var{predicate} is either a string or a cons cell (the @sc{car} of
./SAVANNAH-crawl/emacs/doc/lispref/minibuf.texi:matched by three of the alist @sc{car}s. All of the matches begin with
./SAVANNAH-crawl/emacs/doc/lispref/help.texi:symbol in the @sc{car} of the list, inside angle brackets.
./SAVANNAH-crawl/emacs/doc/lispref/variables.texi:Note that storing new values into the @sc{cdr}s of cons cells in this
./SAVANNAH-crawl/emacs/doc/lispref/variables.texi:form is a regular Lisp variable. But the @sc{car}s and @sc{cdr}s of
./SAVANNAH-crawl/emacs/doc/lispref/customize.texi:The value must be a cons cell, its @sc{car} must fit @var{car-type}, and
./SAVANNAH-crawl/emacs/doc/lispref/customize.texi:its @sc{cdr} must fit @var{cdr-type}. For example, @code{(cons string
./SAVANNAH-crawl/emacs/doc/lispref/customize.texi:In the customization buffer, the @sc{car} and @sc{cdr} are displayed
./SAVANNAH-crawl/emacs/doc/lispref/customize.texi:The value must be a list of cons-cells, the @sc{car} of each cell
./SAVANNAH-crawl/emacs/doc/lispref/customize.texi:@sc{cdr} of the same cell representing a value of customization type
./SAVANNAH-crawl/emacs/doc/lispref/modes.texi:comment starter. If the entry is a cons cell, the @sc{car} is set
./SAVANNAH-crawl/emacs/doc/lispref/modes.texi:up as a comment starter and the @sc{cdr} as a comment ender.
./SAVANNAH-crawl/emacs/doc/lispref/modes.texi:The @sc{car}, @var{characters}, can be either a character or a string.
./SAVANNAH-crawl/emacs/doc/lispref/modes.texi:expression or a function, as described above. The @sc{cdr},
./SAVANNAH-crawl/emacs/doc/lispref/modes.texi:The @sc{car}, @var{subexp}, is an integer specifying which subexpression
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:number. The argument used by @samp{%c} must be an @sc{ascii} code
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:number; it will be printed as the character with that @sc{ascii} code.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:The @sc{car} of a list is, quite simply, the first item in the list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:Thus the @sc{car} of the list @code{(rose violet daisy buttercup)} is
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:The @sc{cdr} of a list is the rest of the list, that is, the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:first item. Thus, while the @sc{car} of the list @code{'(rose violet
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:list. However, the @sc{cdr} of the list is a list itself, @code{(fir
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:In this example, the first element or @sc{car} of the list is the list of
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:What it does is take the @sc{cdr} of a list repeatedly.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:If you take the @sc{cdr} of the list @code{(pine fir
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{(oak maple)}. (Of course, repeated @sc{cdr}ing on the original
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:list will just give you the original @sc{cdr} since the function does
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:not change the list. You need to evaluate the @sc{cdr} of the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} and so on.) If you continue this, eventually you will be
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:For review, here is a series of repeated @sc{cdr}s, the text following
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:You can also do several @sc{cdr}s without printing the values in
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{nthcdr} function takes the @sc{cdr} of a list repeatedly.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{nth} function takes the @sc{car} of the result returned by
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:say, the first element of a list, its @sc{car} is the zeroth element.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:functions set the @sc{car} or the @sc{cdr} of a list to a new value.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the first list will be set;
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{(horse cat dog)}. The @sc{cdr} of the list is changed from
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:with the text already in the first element (the @sc{car}) of the kill
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:the @sc{car} of the kill ring. Whether it prepends or appends the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:It sets the @sc{cdr} of a list, just as @code{setcar} sets the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{car} of a list. In this case, however, @code{setcdr} will not be
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:setting the @sc{cdr} of the whole kill ring; the @code{nthcdr}
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:function is used to cause it to set the @sc{cdr} of the next to last
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:element of the kill ring---this means that since the @sc{cdr} of the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{nthcdr} function works by repeatedly taking the @sc{cdr} of a
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:list---it takes the @sc{cdr} of the @sc{cdr} of the @sc{cdr}
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:elements long, we could set the @sc{cdr} of the next to last element
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:birch)}, then set the @sc{cdr} of its second @sc{cdr} to @code{nil}
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:that is what the @sc{cdr} is set to.)
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} a number of times that is one less than the maximum permitted
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:size of the kill ring and @code{setcdr} sets the @sc{cdr} of that
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:Return the result of taking @sc{cdr} @var{n} times on a list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:If a symbol is set to the @sc{cdr} of a list, the list itself is not
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:the jargon, @sc{car} and @sc{cdr} are ``non-destructive''.) Thus,
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:Thus, in Lisp, to get the @sc{cdr} of a list, you just get the address
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:of the next cons cell in the series; to get the @sc{car} of a list,
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{more-flowers}. Set the @sc{car} of @code{flowers} to a fish.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:of the kill ring of which the first element (the @sc{car}) will be
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:expression set the value of the list to be the @sc{cdr} of the list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:can be set to be the @sc{cdr} of the original list with the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@code{dolist} works like a @code{while} loop that @sc{cdr}s down a
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:loops---takes the @sc{cdr} of the list---and binds the @sc{car} of
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr}s down the list on its own---and it automatically binds
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:the @sc{car} of each shorter version of the list to the first of its
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:In the example, the @sc{car} of each shorter version of the list is
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:The @code{dolist} expression binds the @sc{car} of each shorter
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:first element of the list, the @sc{car} of the list. Then the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:list). Then the function calls itself with the @sc{cdr} of the list
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:it is invoked with, which (the second time around) is the @sc{cdr} of
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:the @sc{cdr} of the original list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:evaluates the first element (the @sc{car} or true-or-false-test) of
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list)
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi: @sc{cdr}) of the list,
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi: act on the beginning of the list (the @sc{car} of the list),
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi: and make a recursive call on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list),
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:Else, if the beginning of the list (the @sc{car} of the list) passes
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:Otherwise, if the beginning of the list (the @sc{car} of the list) fails
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi: and, recursively call the function on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:technique is to set the value of the list to the value of the @sc{cdr}
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of itself, so eventually the list will be empty; and the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:should not be too hard to write a function that @sc{cdr}s down the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:(cdr numbers-list))} expression, the @sc{car} of each instance of the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:non-@sc{ascii} characters are written within square brackets, without
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:hexadecimal three, and @sc{ascii} Control-C (the third letter of the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:set to be equal to some @sc{cdr} of the kill ring, using the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:works by repeatedly taking the @sc{cdr} of a list---it takes the
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cdr} of the @sc{cdr} of the @sc{cdr} @dots{}
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:the @code{mod} function to determine which @sc{cdr} to select.
./SAVANNAH-crawl/emacs/doc/lispintro/emacs-lisp-intro.texi:@sc{cons} rather than a number or nothing, it puts point at beginning
./SAVANNAH-crawl/emacs/lisp/textmodes/texinfmt.el:;; @sc a small caps font for TeX; formatted as `var' in Info
./SAVANNAH-crawl/gdbm/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gnuit/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/dragora-handbook/qi-content.texi:@sc{Output}
./SAVANNAH-crawl/dragora-handbook/qi-content.texi:@sc{Example}
./SAVANNAH-crawl/dragora-handbook/qi-content.texi:@sc{Example}
./SAVANNAH-crawl/gcal/doc/de/texi/gcal.texi:Eine Gcal Ressourcendatei ist zun@"achst einmal eine reine @sc{ascii}
./SAVANNAH-crawl/gcal/doc/de/texi/gcal.texi:lassen sich auf Nicht-@sc{ascii} Zeichens@"atze anwenden, welche einzelne
./SAVANNAH-crawl/gcal/doc/de/texi/gcal.texi:Diese l@"a@ss{} sich auf Nicht-@sc{ascii} Zeichens@"atze anwenden, welche
./SAVANNAH-crawl/gcal/doc/en/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gcal/doc/en/gcal.texi:First of all, a Gcal resource file is a plain @sc{ascii} text file.
./SAVANNAH-crawl/gcal/doc/en/gcal.texi:These apply to non-@sc{ascii} character sets, which can have single symbols
./SAVANNAH-crawl/gcal/doc/en/gcal.texi:expression. This apply to non-@sc{ascii} character sets, which can
./SAVANNAH-crawl/coreutils/doc/coreutils.texi:To specify a tab (@sc{ascii} 0x09) character instead of whitespace, use
./SAVANNAH-crawl/gsl/doc_texinfo/interp.texi:The output is designed to be used with the @sc{gnu} plotutils
./SAVANNAH-crawl/gsl/doc_texinfo/interp.texi:The output can be plotted with @sc{gnu} @code{graph}.
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:The Basic Linear Algebra Subprograms (@sc{blas}) define a set of fundamental
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:C-language @sc{blas} standard, referred to here as ``@sc{cblas}'', and a
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:interface only includes the corresponding dense-storage @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:functions. The full @sc{blas} functionality for band-format and
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:packed-format matrices is available through the low-level @sc{cblas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:whereas the low-level @sc{cblas} interface supports negative
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:strides as specified in the @sc{blas} standard.@footnote{In the low-level
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:@sc{cblas} interface, a negative stride accesses the vector elements
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:@file{gsl_cblas.h}. This interface corresponds to the @sc{blas} Technical
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:Forum's standard for the C interface to legacy @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:implementations. Users who have access to other conforming @sc{cblas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:library. Note that users who have only a Fortran @sc{blas} library can
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:use a @sc{cblas} conformant wrapper to convert it into a @sc{cblas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:library. A reference @sc{cblas} wrapper for legacy Fortran
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:implementations exists as part of the @sc{cblas} standard and can
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:be obtained from Netlib. The complete set of @sc{cblas} functions is
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:There are three levels of @sc{blas} operations,
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:Thus, for example, the name @sc{sgemm} stands for ``single-precision
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:general matrix-matrix multiply'' and @sc{zgemm} stands for
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:built-in types. The library provides an interface to the @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:Givens transformation is defined in the original Level-1 @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:Level-3 @sc{blas} function @sc{dgemm},
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:Information on the @sc{blas} standards, including both the legacy and
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:updated interface standards, is available online from the @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:Homepage and @sc{blas} Technical Forum web-site.
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:Level 3 @sc{blas}.
./SAVANNAH-crawl/gsl/doc_texinfo/blas.texi:@uref{http://www.netlib.org/blas/}. A @sc{cblas} wrapper for Fortran @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/ntuple.texi:documentation for the @sc{cern} packages @sc{paw} and @sc{hbook}
./SAVANNAH-crawl/gsl/doc_texinfo/dwt.texi:The output can be used with the @sc{gnu} plotutils @code{graph} program,
./SAVANNAH-crawl/gsl/doc_texinfo/ode-initval.texi:The same error control heuristic is used by the Matlab @sc{ode} suite.
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:@sc{fftpack} library of Paul Swarztrauber. Fortran code for @sc{fftpack} is
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:available on Netlib (@sc{fftpack} also includes some routines for sine and
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:same convention as @sc{fftpack}, using a negative exponential for the forward
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:reimplementation of Paul Swarztrauber's Fortran @sc{fftpack} library.
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:indexing scheme and basic algorithms as @sc{fftpack}.
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:reimplementation of the real-FFT routines in the Fortran @sc{fftpack} library
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:algorithms as @sc{fftpack}.
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:The functions use the @sc{fftpack} storage convention for half-complex
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:The mixed-radix algorithm at the heart of the @sc{fftpack} routines is
./SAVANNAH-crawl/gsl/doc_texinfo/fft.texi:The source code for @sc{fftpack} is available from Netlib,
./SAVANNAH-crawl/gsl/doc_texinfo/gsl-ref.texi:histograms, statistics, ieee-utils, revised @sc{cblas} Level 2 & 3,
./SAVANNAH-crawl/gsl/doc_texinfo/gsl-ref.texi:Wrote the @sc{cquad} integration routines.
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty:\def\calc@pre@scan#1{%
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty: \calc@pre@scan}
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty:\def\calc@numeric{\afterassignment\calc@post@scan \global\calc@A}
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty:\def\calc@post@scan#1{%
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty: \calc@pre@scan}
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty: \aftergroup#1\calc@pre@scan}
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty: \calc@post@scan}
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty: \calc@post@scan}
./SAVANNAH-crawl/gsl/doc_texinfo/calc.sty: \calc@post@scan}
./SAVANNAH-crawl/gsl/doc_texinfo/ieee754.texi:@sc{inexact} exception. The @sc{inexact} exception is generated
./SAVANNAH-crawl/gsl/doc_texinfo/ieee754.texi:original x87 mode and the newer @sc{mxcsr} mode, which controls SSE
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:adaptive algorithms such as @sc{vegas} and @sc{miser} which use
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{miser} algorithm of Press and Farrar is based on recursive
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{miser} algorithm proceeds by bisecting the integration region
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:This routines uses the @sc{miser} Monte Carlo algorithm to integrate the
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{miser} algorithm has several configurable parameters which can
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:this behavior the @sc{miser} algorithm allows the total variance to
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The authors of the original paper describing @sc{miser} recommend the
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{vegas} algorithm of Lepage is based on importance sampling. It
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{vegas} algorithm approximates the exact distribution by making a
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:of @sc{vegas} depends on the validity of this assumption. It is most
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:this will increase the efficiency of integration with @sc{vegas}.
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:@sc{vegas} incorporates a number of additional features, and combines both
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:This routines uses the @sc{vegas} Monte Carlo algorithm to integrate the
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{vegas} algorithm computes a number of independent estimates of the
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:@sc{vegas} the error estimate is made non-zero by substituting a small
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{vegas} algorithm is highly configurable. Several parameters
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:average. Calling @sc{vegas} with @code{stage = 1} retains the grid from the
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:This determines whether @sc{vegas} will use importance sampling or
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:dimensions @sc{vegas} uses strict stratified sampling (more precisely,
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:These parameters set the level of information printed by @sc{vegas}. All
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{miser} algorithm reduces the error by a factor of four, and also
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:In the case of the @sc{vegas} algorithm the program uses an initial
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:error. The final estimate from @sc{vegas} (using a similar number of
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{miser} algorithm is described in the following article by Press
./SAVANNAH-crawl/gsl/doc_texinfo/montecarlo.texi:The @sc{vegas} algorithm is described in the following papers,
./SAVANNAH-crawl/gsl/doc_texinfo/cblas.texi:The prototypes for the low-level @sc{cblas} functions are declared in
./SAVANNAH-crawl/gsl/doc_texinfo/cblas.texi:Level-3 @sc{blas} function @sc{sgemm},
./SAVANNAH-crawl/gsl/doc_texinfo/cblas.texi:case as the @sc{cblas} library is an independent unit. Here is the output
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:second-generation @sc{ranlux} generators have the strongest proof of
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:equi-distributed in 623 dimensions. It has passed the @sc{diehard}
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:@sc{ranlux} algorithm of L@"uscher, which produces ``luxury random
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:@sc{ranlxs} generator. The library provides two luxury levels
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:@sc{ranlxs} and @sc{ranlxd} described above provide floating-point
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:This is Park and Miller's ``minimal standard'' @sc{minstd} generator, a
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:based on the @sc{ranlux} algorithm.
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:The source code for the @sc{diehard} random number generator tests is also
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:@sc{nist},
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:L@"uscher for providing notes and source code for the @sc{ranlxs} and
./SAVANNAH-crawl/gsl/doc_texinfo/rng.texi:@sc{ranlxd} generators.
./SAVANNAH-crawl/gsl/doc_texinfo/debug.texi:debugging numerical programs with @sc{gcc} and @sc{gdb}.
./SAVANNAH-crawl/gsl/doc_texinfo/multimin.texi:In addition, the size of simplex is calculated as the @sc{rms}
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:both the main library and a supporting @sc{cblas} library, which
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:@sc{cblas} implementation is provided in the library
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:with an alternative @sc{cblas} library @file{libcblas.a},
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:For the best performance an optimized platform-specific @sc{cblas}
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:the @sc{cblas} standard. The @sc{atlas} package provides a portable
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:high-performance @sc{blas} library with a @sc{cblas} interface. It is
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:@sc{atlas} library and its @sc{cblas} interface,
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:If the @sc{atlas} library is installed in a non-standard directory use
./SAVANNAH-crawl/gsl/doc_texinfo/usage.texi:For more information about @sc{blas} functions see @ref{BLAS Support}.
./SAVANNAH-crawl/gsl/doc_texinfo/bspline.texi:The output can be plotted with @sc{gnu} @code{graph}.
./SAVANNAH-crawl/gsl/doc_texinfo/bspline.texi:@sc{pppack} library available at @uref{http://www.netlib.org/pppack},
./SAVANNAH-crawl/gsl/doc_texinfo/bspline.texi:which is also part of @sc{slatec}.
./SAVANNAH-crawl/gsl/doc_texinfo/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gsl/doc_texinfo/multiroots.texi:library @sc{minpack}.
./SAVANNAH-crawl/gsl/doc_texinfo/multiroots.texi:the @sc{hybrj} algorithm in @sc{minpack}. Minpack was written by Jorge
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:are compatible with the vector and matrix formats used by @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:Unlike @sc{fortran} compilers, C compilers do not usually provide
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:computes the norm of the odd elements of @code{v} using the @sc{blas}
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:routine @sc{dnrm2},
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:available in the @sc{blas} part of the library (@pxref{BLAS
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:functions which do not require the full @sc{blas} code. The following
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:``C-language ordering'' of two-dimensional arrays. Note that @sc{fortran}
./SAVANNAH-crawl/gsl/doc_texinfo/vectors.texi:The results can be confirmed using @sc{gnu octave},
./SAVANNAH-crawl/gsl/doc_texinfo/sum.texi:@sc{hurry}: An acceleration algorithm for scalar sequences and series
./SAVANNAH-crawl/gsl/doc_texinfo/eigen.texi:This can be compared with the corresponding output from @sc{gnu octave},
./SAVANNAH-crawl/gsl/doc_texinfo/eigen.texi:This can be compared with the corresponding output from @sc{gnu octave},
./SAVANNAH-crawl/gsl/doc_texinfo/eigen.texi:Fortran library @sc{lapack}. The @sc{lapack} library is described in,
./SAVANNAH-crawl/gsl/doc_texinfo/eigen.texi:The @sc{lapack} source code can be found at the website above along with
./SAVANNAH-crawl/gsl/doc_texinfo/err.texi:@sc{posix} Threads library. Functions return a non-zero error code to
./SAVANNAH-crawl/gsl/doc_texinfo/fitting.texi:and display it using the @sc{gnu} plotutils @code{graph} utility,
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:as used by @sc{lapack}.
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:as used by @sc{lapack}. The vector @var{norm} is a workspace of length
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:singular value decomposition (@sc{svd}) into the product of an
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:@math{Q}. This storage scheme is the same as used by @sc{lapack}. The
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:@math{U}. This storage scheme is the same as used by @sc{lapack}. The
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:original matrix @math{A} using @sc{gnu octave},
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:The @sc{lapack} library is described in the following manual,
./SAVANNAH-crawl/gsl/doc_texinfo/linalg.texi:The @sc{lapack} source code can be found at the website above, along
./SAVANNAH-crawl/gsl/doc_texinfo/intro.texi:copying it from a friend, purchasing it on @sc{cdrom} or downloading it
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:@sc{quadpack}, a numerical integration package written by Piessens,
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:de Doncker-Kapenga, Ueberhuber and Kahaner. Fortran code for @sc{quadpack} is
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:The algorithms in @sc{quadpack} use a naming convention based on the
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:Clenshaw-Curtis rules used in @sc{quadpack} separate out several common
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:@sc{cquad} is a new doubly-adaptive general-purpose quadrature
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:@sc{quadpack}, yet fails less often for difficult integrands.
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:and @var{epsrel} using the @sc{cquad} algorithm. The function returns
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:The @sc{cquad} algorithm divides the integration region into
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:The following book is the definitive reference for @sc{quadpack}, and was
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:the numerical integration literature used in developing @sc{quadpack}.
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:@cite{@sc{quadpack} A subroutine package for automatic integration}
./SAVANNAH-crawl/gsl/doc_texinfo/integration.texi:The @sc{cquad} integration algorithm is described in the following paper:
./SAVANNAH-crawl/gsl/doc_texinfo/math.texi:The library ensures that the standard @sc{bsd} mathematical constants
./SAVANNAH-crawl/gsl/doc_texinfo/math.texi:(regardless of its @sc{ieee} sign bit).
./SAVANNAH-crawl/gsl/doc_texinfo/autoconf.texi:presence of a @sc{cblas} and math library as well, so these must also be
./SAVANNAH-crawl/gsl/doc_texinfo/autoconf.texi:@sc{major.minor} or @sc{major.minor.micro} version number of the release
./SAVANNAH-crawl/gsl/doc_texinfo/spblas.texi:The Sparse Basic Linear Algebra Subprograms (@sc{blas}) define a set of
./SAVANNAH-crawl/quagga/doc/install.texi:Force to enable @sc{gnu}/Linux netlink interface. Quagga configure
./SAVANNAH-crawl/quagga/doc/install.texi:There are several options available only to @sc{gnu}/Linux systems:
./SAVANNAH-crawl/quagga/doc/install.texi:@footnote{@sc{gnu}/Linux has very flexible kernel configuration features}. If
./SAVANNAH-crawl/quagga/doc/install.texi:you use @sc{gnu}/Linux, make sure that the current kernel configuration is
./SAVANNAH-crawl/quagga/doc/install.texi:IPv6 support has been added in @sc{gnu}/Linux kernel version 2.2. If you
./SAVANNAH-crawl/quagga/doc/install.texi:try to use the Quagga IPv6 feature on a @sc{gnu}/Linux kernel, please
./SAVANNAH-crawl/quagga/doc/install.texi:these libraries will not be needed when you uses @sc{gnu} C library 2.1
./SAVANNAH-crawl/quagga/doc/overview.texi: Quagga is distributed under the @sc{gnu} General Public License.
./SAVANNAH-crawl/quagga/doc/overview.texi:which comes with @sc{gnu}/Linux or FreeBSD has some problems with running
./SAVANNAH-crawl/quagga/doc/overview.texi:Currently Quagga supports @sc{gnu}/Linux and BSD. Porting Quagga
./SAVANNAH-crawl/quagga/doc/overview.texi:@sc{gnu}/Linux
./SAVANNAH-crawl/quagga/doc/overview.texi:of their original release (in case of @sc{gnu}/Linux, this is since the kernel's
./SAVANNAH-crawl/quagga/doc/overview.texi:@sc{gnu}'s GCC
./SAVANNAH-crawl/foliot/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/g-golf/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/libredwg/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gtypist/doc/gtypist.cs.texi:Simon Baldwin @email{simonb@@sco.com} přepsal verzi D. Jason Penneyho,
./SAVANNAH-crawl/gtypist/doc/gtypist.texi:@email{simonb@@sco.com, Simon Baldwin} rewrote the version of D. Jason
./SAVANNAH-crawl/gtypist/doc/gtypist.texi:In 2003, @email{rutsky@@school.ioffe.rssi.ru, Dmitry Rutsky} joined
./SAVANNAH-crawl/gtypist/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gtypist/doc/gtypist.es.texi:@email{simonb@@sco.com, Simon Baldwin} re-escribió la versión de
./SAVANNAH-crawl/gtypist/doc/gtypist.es.texi:En 2003, @email{rutsky@@school.ioffe.rssi.ru, Dmitry Rutsky} se unió
./SAVANNAH-crawl/smalltalk/snprintfv/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SAVANNAH-crawl/smalltalk/doc/gst-libs.texi:@sc{gnu} Smalltalk
./SAVANNAH-crawl/smalltalk/doc/gst-libs.texi:@sc{gnu}
./SAVANNAH-crawl/smalltalk/doc/gst-libs.texi:@title @sc{gnu} Smalltalk Library Reference
./SAVANNAH-crawl/smalltalk/doc/gst-base.texi:@sc{gnu} Smalltalk
./SAVANNAH-crawl/smalltalk/doc/gst-base.texi:@sc{gnu}
./SAVANNAH-crawl/smalltalk/doc/gst-base.texi:@title @sc{gnu} Smalltalk Library Reference
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@sc{gnu} Smalltalk
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@sc{gnu}
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@title @sc{gnu} Smalltalk User's Guide
./SAVANNAH-crawl/smalltalk/doc/gst.texi:languages}. Therefore, even though we have a @sc{gui} environment based
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@multitable {@option{--verbose -aq -c}} {Options seen by @sc{gnu} Smalltalk} {@code{Smalltalk arguments}}
./SAVANNAH-crawl/smalltalk/doc/gst.texi:operations to @code{stdout}. If you load the VisualGST @sc{gui}, instead,
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@gst{} inherits from @sc{iso} C the concept of a @dfn{locale}, that is, a
./SAVANNAH-crawl/smalltalk/doc/gst.texi:Format a monetary value together with its @sc{iso} currency symbol.
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@sc{mo} file format adopted by the @gnu{} @code{gettext} library.
./SAVANNAH-crawl/smalltalk/doc/gst.texi:engine which is now superseded by Swazoo. It is based on the @sc{gpl}'ed
./SAVANNAH-crawl/smalltalk/doc/gst.texi:authentication support, virtual hosting, and @sc{http} 1.1 compliance.
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@gst{} includes an almost complete abstraction of the @sc{tcp}, @sc{udp}
./SAVANNAH-crawl/smalltalk/doc/gst.texi:and @sc{ip} protocols. Although based on the standard @sc{bsd} sockets,
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@sc{ftp}, @sc{http}, @sc{nntp}, @sc{smtp}, @sc{pop3} and @sc{imap}.
./SAVANNAH-crawl/smalltalk/doc/gst.texi:The @sc{xml} parser library for Smalltalk, loaded as package @code{XML}
./SAVANNAH-crawl/smalltalk/doc/gst.texi:includes a validating @sc{xml} parser and Document Object Model.
./SAVANNAH-crawl/smalltalk/doc/gst.texi:and a @sc{xslr} interpreter based on it is bundled with @gst{} as
./SAVANNAH-crawl/smalltalk/doc/gst.texi:@item @sc{gdbm}
./SAVANNAH-crawl/smalltalk/doc/gst.texi:with the library at run-time using @sc{dld}, using either
./SAVANNAH-crawl/smalltalk/doc/gst.texi:run-time; but since some@footnote{The most notable are @sc{aix} and
./SAVANNAH-crawl/smalltalk/doc/tutorial.texi: @gst{} supports completion in the same way as Bash or @sc{gdb}.
./SAVANNAH-crawl/smalltalk/build-aux/texi2html:# - Don't use latex2html to produce smallcaps (@sc)
./SAVANNAH-crawl/idutils/doc/idutils.texi:@sc{gnu} @command{find}, using its @option{-print0} predicate. Do not
./SAVANNAH-crawl/idutils/doc/idutils.texi:virtual address space. A typical @sc{unix}-like operating system with
./SAVANNAH-crawl/idutils/doc/idutils.texi:took over an hour on a @sc{vax 11/750} to build a database for a
./SAVANNAH-crawl/idutils/doc/idutils.texi:@sc{4.1bsd} derived kernel. The first version of @file{lid} used the
./SAVANNAH-crawl/idutils/doc/idutils.texi:@sc{unix} system utility @code{look}, modified to handle very long
./SAVANNAH-crawl/mdk/doc/mdk_emacs.texi:@sc{mdk} adds support to Emacs for both writing and debugging MIX
./SAVANNAH-crawl/mdk/doc/mdk_emacs.texi:This chapter shows how to use the Elisp modules included in @sc{mdk},
./SAVANNAH-crawl/mdk/doc/mdk_emacs.texi:initiate an @sc{mdk}/@acronym{GUD} session inside Emacs with the command
./SAVANNAH-crawl/mdk/doc/mdk_gstart.texi:using the @sc{mdk} utilities. Familiarity with the MIX mythical computer
./SAVANNAH-crawl/mdk/doc/mdk_gstart.texi:when used with the @sc{mdk} utilities. As you can see in the above
./SAVANNAH-crawl/mdk/doc/mdk_gstart.texi:fixed pre-defined column number, the @sc{mdk} assembler loosens this
./SAVANNAH-crawl/mdk/doc/mdk_gstart.texi:and @code{mixguile}, are included in the @sc{mdk} tools. They are able to
./SAVANNAH-crawl/mdk/doc/mdk_gstart.texi:favorite hardware provider. @sc{mdk} provides three software simulators of
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:Many people have further contributed to @sc{mdk} by reporting problems,
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:provided MIXAL test programs pinpointing bugs in the first @sc{mdk}
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:has been following @sc{mdk}'s development for many years, indefatigably
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:is the author of the German translation of @sc{mdk}'s user interface.
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:kindly and thoroughly reviewed the @sc{mdk} documentation, providing
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:has tested @sc{mdk} in a lot of Unix platforms, suggesting portability
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:ported @sc{mdk} to different platforms, and created and/or maintain
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:tested @sc{mdk} on different platforms, and helped fixing the configuration
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:kept an eye on each @sc{mdk} release.
./SAVANNAH-crawl/mdk/doc/mdk_ack.texi:@item @sc{mdk} was inspired by Darius Bacon's
./SAVANNAH-crawl/mdk/doc/mdk_mixvm.texi:compiled @sc{mdk} with readline support, i.e., if GNU readline is
./SAVANNAH-crawl/mdk/doc/mdk_mixvm.texi:@sc{mdk} configuration directory (@file{~/.mdk}).
./SAVANNAH-crawl/mdk/doc/mdk_mixvm.texi:machine behaviour. This configuration is stored in the @sc{mdk}
./SAVANNAH-crawl/mdk/doc/mdk_mixvm.texi:If you have compiled @sc{mdk} with @code{libguile} support
./SAVANNAH-crawl/mdk/doc/mdk_mixasm.texi:form by @code{mixasm}, the MIXAL assembler included in @sc{mdk}. In this
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:@chapter Installing @sc{mdk}
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:GNU @sc{mdk} is distributed as a source tarball available for download in
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:The above sites contain the latest stable releases of @sc{mdk}. The
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:@uref{https://savannah.gnu.org/git/?group=mdk, @sc{mdk}'s Git page} for
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:In order to build and install @sc{mdk}, you will need the following
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:libguile is found, the @sc{mdk} utilities will be compiled with Guile
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:@sc{mdk} uses GNU Autoconf and Automake tools, and, therefore, should
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:The next command, @code{make}, will actually build the @sc{mdk} programs
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:@sc{mdk} includes extensive support for Emacs. Upon installation, all
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:@sc{mdk}'s @code{mixvm} and Emacs, via @acronym{GUD}. Place this file
./SAVANNAH-crawl/mdk/doc/mdk_install.texi:@sc{mdk} will probably work on any GNU/Linux or BSD platform. If you
./SAVANNAH-crawl/mdk/doc/mdk_bugs.texi:If you find a bug in @sc{mdk}, please send electronic mail to
./SAVANNAH-crawl/mdk/doc/mdk_bugs.texi:@email{bug-mdk@@gnu.org, the @sc{mdk} bug list}.
./SAVANNAH-crawl/mdk/doc/mdk.texi:@subtitle Edition @value{EDITION}, for GNU @sc{mdk} Version @value{VERSION}
./SAVANNAH-crawl/mdk/doc/mdk.texi:@value{MIKE} is the author of the German translation of @sc{mdk}'s
./SAVANNAH-crawl/mdk/doc/mdk.texi:* Getting started:: Basic usage of the @sc{mdk} tools.
./SAVANNAH-crawl/mdk/doc/mdk.texi:* Copying:: @sc{mdk} licensing terms.
./SAVANNAH-crawl/mdk/doc/mdk.texi:Installing @sc{mdk}
./SAVANNAH-crawl/mdk/doc/mdk_mixguile.texi:@sc{mdk} emulators (@code{mixguile}, @code{mixvm} and @code{gmixvm}). See
./SAVANNAH-crawl/mdk/doc/mdk_mixguile.texi:@sc{mdk} MIX virtual machines.
./SAVANNAH-crawl/mdk/doc/mdk_mixguile.texi:it looks for a file named @file{mixguile.scm} in the user's @sc{mdk}
./SAVANNAH-crawl/mdk/doc/mdk_mixguile.texi:language, Scheme, to extend the @sc{mdk} virtual machine emulators (see
./SAVANNAH-crawl/mdk/doc/mdk_copying.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mdk/doc/mdk_gmixvm.texi:shipped with @sc{mdk}. In addition to having all the command-oriented
./SAVANNAH-crawl/mdk/doc/mdk_gmixvm.texi:If you have built @sc{mdk} with GTK+ support (@pxref{Installing MDK}), a
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:@cindex @sc{ov}
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:@cindex @sc{cm}
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:@dfn{off}). In this manual, this toggle is denoted @sc{ov}.
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:@sc{cm}, and its possible values are abbreviated as @dfn{E}, @dfn{G} and
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:set the @sc{cm} indicator to the result of the comparison (i.e. to
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:we do in @sc{mdk} simulator). For the same reason, @sc{mdk} devices are
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:provided by @sc{mdk} are described later on (@pxref{Getting started}).
./SAVANNAH-crawl/mdk/doc/mdk_tut.texi:MIXAL assembler included in @sc{mdk}, @code{mixasm}, does not impose
./SAVANNAH-crawl/mdk/doc/mdk_intro.texi:The @sc{mdk} package aims at providing such virtual development
./SAVANNAH-crawl/mdk/doc/mdk_intro.texi:environment on a GNU box. Thus, @sc{mdk} offers you a set of utilities
./SAVANNAH-crawl/mdk/doc/mdk_intro.texi:programs. As of version @value{VERSION}, @sc{mdk} includes
./SAVANNAH-crawl/mdk/doc/mdk_intro.texi:description of the use of the @sc{mdk} utilities.
./SAVANNAH-crawl/tar/doc/tar.texi:* Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
./SAVANNAH-crawl/tar/doc/tar.texi:12:56:31 @sc{utc}, you will have to chose between @acronym{GNU} and
./SAVANNAH-crawl/web/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{sos} is a Scheme @dfn{object system} derived from Tiny @sc{clos}
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@footnote{Tiny @sc{clos} was written by Gregor Kiczales of Xerox
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{parc}; @sc{sos} is derived from version 1.2 of Tiny @sc{clos}.},
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:which in turn was loosely derived from @sc{clos}, the Common Lisp Object
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{clos}, but there are differences in naming and interface.
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:you already have a passing familiarity with @sc{clos} and with Scheme.
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@dfn{instance} objects. Instances are special because @sc{sos} has
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:pair whose @sc{car} is a symbol and whose @sc{cdr} is an alist. The
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{sos} provides a rich set of predefined classes that can be used to
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{sos} allows generic procedures to discriminate on record types.
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:In order to support this, @sc{sos} accepts record type descriptors in
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:descriptor has an associated @sc{sos} class; either the class or the
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:accepted; the @sc{cdr} may be @code{#f} indicating no upper bound.
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:an @dfn{effective method procedure}, or @sc{emp}, then tail-recursively
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:invoking the @sc{emp}. @code{compute-effective-method-procedure} is the
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:them into an @sc{emp}.
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:returns that @sc{emp}.
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:Note that computed methods and computed @sc{emp}s both satisfy the
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:A @dfn{computed @sc{emp}} takes the computed-method mechanism one step
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:further. A computed @sc{emp} is like a computed method, except that it
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:computed @sc{emp}s, and if exactly one of them returns an @sc{emp}, that
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:Create and return a computed @sc{emp}. @var{Procedure} will be called
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:arguments as its arguments. It must return either an @sc{emp} or
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{emp}. The @var{key} is used by @code{add-method} and
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@code{delete-method} to decide whether two computed @sc{emp}s are
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{emp} with the same specializers.
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:Returns @code{#t} if @var{object} is a computed @sc{emp}, otherwise
./SAVANNAH-crawl/mit-scheme/doc/sos/sos.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mit-scheme/doc/ffi/ffi.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mit-scheme/doc/user-manual/user.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/graphics.texi:bitmaps (@sc{dib}s).
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/numbers.texi:used to implement all inexact reals; on machines that support @sc{ieee}
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/numbers.texi:but does not require, that the @sc{ieee} 32-bit and 64-bit floating
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/numbers.texi:modes required by the @sc{ieee} floating point standard.
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/io.texi:unix this procedure can be used to open terminal device files, @sc{pty}
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/special-forms.texi:values are only useful with a @sc{boa} constructor with argument list or
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/special-forms.texi:constructor procedures are called ``@sc{boa} constructors'', for ``By
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/special-forms.texi:@sc{boa} constructors are described using Scheme lambda lists. Since there
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/os-interface.texi:@sc{pty} devices; if true, @sc{pty}s will be used, otherwise pipes will
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/os-interface.texi:inter-process communication. @sc{tcp} stream sockets are supported,
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/os-interface.texi:which communicate between computers over a @sc{tcp/ip} network.
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/os-interface.texi:@sc{tcp} sockets are supported on all operating systems.
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/os-interface.texi:@sc{tcp} sockets have two distinct interfaces: one interface to
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/os-interface.texi:Next we will treat setting up a @sc{tcp} server, which is slightly more
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/os-interface.texi:terminated by @sc{cr-lf}, which is the standard for most internet
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:stopping the computation and putting the user in an error @sc{repl}.
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:and stops the computation, entering an error @sc{repl}. Under normal
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:breakpoint @sc{repl} is initiated. Otherwise (or when that @sc{repl}
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:creates a new @sc{repl} prior to its normal operation when its argument
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:Arranges for @code{signal-condition} to create an interactive @sc{repl}
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:In order to create a @sc{repl} when @emph{any} condition type is
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:@code{signal-condition}. Normally creates a new @sc{repl} with
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:@sc{repl}. It is passed one argument, the condition being signalled.
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/error.texi:of computation. This is the restart provided by Scheme's @sc{repl}.
./SAVANNAH-crawl/mit-scheme/doc/ref-manual/gfdl.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mit-scheme/src/imail/mit-scheme-imail.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mit-scheme/src/blowfish/mit-scheme-blowfish.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex halt
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex reboot
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libpthread
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex pthread.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libports
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex ports.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libihash
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex ihash.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libshouldbeinlibc
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libhurdbugaddr
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libiohelp
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex iohelp.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libpager
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex pager.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex io.defs
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libtrivfs
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex trivfs.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libfshelp
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex fshelp.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex fs.defs
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex fsys.defs
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libstore
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex store.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libdiskfs
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex diskfs.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libstorefs
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex libftpconn
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex ftpconn.h
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex socket.defs
./SAVANNAH-crawl/hurd/doc/hurd.texi:@scindex auth.defs
./SAVANNAH-crawl/anubis/doc/anubis.texi:@subsection Support for @sc{rot-13}
./SAVANNAH-crawl/anubis/doc/anubis.texi:The @sc{rot-13} transformation is a simple form of encryption where the
./SAVANNAH-crawl/anubis/doc/anubis.texi:GNU Anubis supports @sc{rot}-13 via a loadable Guile function. To enable
./SAVANNAH-crawl/anubis/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/auctex/doc/auctex.texi:Insert @sc{small caps} @samp{\textsc@{@point{}@}} text.
./SAVANNAH-crawl/auctex/doc/auctex.texi:Insert @sc{swash} @samp{\textsw@{@point{}@}} text.
./SAVANNAH-crawl/auctex/doc/quickstart.texi:Insert @sc{small caps} @samp{\textsc@{@point{}@}} text.
./SAVANNAH-crawl/auctex/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/auctex/doc/history.texi:@samp{}, Uffe Kjaerulff
./SAVANNAH-crawl/auctex/doc/history.texi:@samp{}.@refill
./SAVANNAH-crawl/auctex/doc/macros.texi:@sc{\text\}
./SAVANNAH-crawl/auctex/doc/preview-readme.texi:@cindex @sc{git} access
./SAVANNAH-crawl/g-wrap/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gforth/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/netutils/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/texinfo/ChangeLog.65: it when in @sc and the original output would have been not have
./SAVANNAH-crawl/texinfo/ChangeLog.65: (_convert): uppercase @sc argument. Suggestion from Arnold Robbins,
./SAVANNAH-crawl/texinfo/doc/texinfo-tex-test.texi:@sansserif{`sans serif'} @sc{`small caps'} {@ensuremath@clubsuit}
./SAVANNAH-crawl/texinfo/doc/refcard/txirefcard.tex:\txicmd{@sc}{\ttbraced{text}}{Set \var{text} in a small caps font in printed output, and uppercase in Info. No other font command has any effect in Info.}
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:acronym. Use @code{@@sc} instead (@pxref{Smallcaps}).
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@subsection @code{@@sc}@{@var{text}@}: The Small Caps Font
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:Use the @samp{@@sc} command to set text in @sc{a small caps font}
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:Richard @@sc@{Stallman@} a commenc@'{e} le projet GNU.
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:Richard @sc{Stallman} a commenc@'{e} le projet GNU.
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:As shown here, we recommend reserving @code{@@sc} for special cases
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@code{@@sc} command in full-size capitals; only lowercase letters are
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@code{@@sc} is printed in all uppercase. In HTML, the argument is
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@sc{car} and the @sc{cdr}. Here is how you would write the first line
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@@samp @@sansserif @@sc @@slanted @@strong @@sub @@sup
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@noindent For @code{@@sc}, any letters are capitalized.
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@item @@sc@{@var{text}@}
./SAVANNAH-crawl/texinfo/doc/texinfo.texi:@code{@@sc}, @code{@@asis}) may contain raw formatter commands such as
./SAVANNAH-crawl/texinfo/doc/texi2oldapi.texi:is in @code{@@sc}. The function should also take care of protecting
./SAVANNAH-crawl/texinfo/doc/texi2oldapi.texi:@code{@@sc}. Special characters (@samp{&}, @samp{"}, @samp{<} and
./SAVANNAH-crawl/texinfo/texindex/ti.twjr:@uref{https://github.com/arnoldrobbins/texiwebjr, @sc{TexiWeb Jr.@:}
./SAVANNAH-crawl/texinfo/contrib/txipsfonts-bronger.tex:% Explicit font changes: @r, @sc, undocumented @ii.
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \expandafter \ifx \csname fam@scale/#1\endcsname\relax \else
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \expandafter\def\csname fam@scale/#1\endcsname{#2}%
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \expandafter \ifx \csname fam@scale/#1\endcsname\relax
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \edef\base@fntscale{\csname fam@scale/#1\endcsname}%
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \expandafter \ifx \csname fam@scale/#2\endcsname\relax
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex:\def\mf@scr@factor{700 }%
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex:\def\mf@scrscr@factor{500 }%
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \scale@f@size\mf@scr@factor
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \scale@f@size\mf@scrscr@factor
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \multiply\count@ by\csname fam@scale/\f@family\endcsname % This family's factor.
./SAVANNAH-crawl/texinfo/contrib/texifont/fsel.tex: \count@ \csname fam@scale/\f@family\endcsname % This family's factor.
./SAVANNAH-crawl/texinfo/po/rw.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/ro.po:#~ msgid "@sc argument all uppercase, thus no effect"
Binary file ./SAVANNAH-crawl/texinfo/po/ro.po matches
./SAVANNAH-crawl/texinfo/po/es.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/es.po:#~ "Todos los argumentos dados a la primitiva `@sc' están en mayúsculas. No "
./SAVANNAH-crawl/texinfo/po/vi.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/vi.po:#~ msgstr "đối số @sc hoàn toàn chữ hoa nên không có tác động"
./SAVANNAH-crawl/texinfo/po/it.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/it.po:#~ "Tutti gli argomenti per la @sc sono in maiuscolo, perciò non hanno alcun "
./SAVANNAH-crawl/texinfo/po/he.po:#~ msgid "@sc argument all uppercase, thus no effect"
Binary file ./SAVANNAH-crawl/texinfo/po/he.po matches
./SAVANNAH-crawl/texinfo/po/cs.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/cs.po:#~ msgstr "@sc argument je celý velkými písmeny, zbytečně"
./SAVANNAH-crawl/texinfo/po/nl.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/nl.po:#~ msgstr "argument van @sc is in hoofdletters, heeft dus geen effect"
./SAVANNAH-crawl/texinfo/po/sv.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/sv.po:#~ "@sc-argumentet är enbart med stora bokstäver, därför har det ingen effekt"
./SAVANNAH-crawl/texinfo/po/tr.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/tr.po:#~ msgstr "@sc argümanı tamamen büyükharf(le yazılmış), etkisiz"
./SAVANNAH-crawl/texinfo/po/sl.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/sl.po:#~ msgstr "argument @sc ima same velike črke in zato nima učinka"
./SAVANNAH-crawl/texinfo/po/zh_CN.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/zh_CN.po:#~ msgstr "@sc 的参数全部为大写，因此无效"
./SAVANNAH-crawl/texinfo/po/uk.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/uk.po:#~ msgstr "аргумент до @sc весь у великому регістрі, отож ніякого ефекту"
./SAVANNAH-crawl/texinfo/po/zh_TW.po:#~ msgid "@sc argument all uppercase, thus no effect"
Binary file ./SAVANNAH-crawl/texinfo/po/zh_TW.po matches
./SAVANNAH-crawl/texinfo/po/hu.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/hu.po:#~ msgstr "@sc argumentuma végig nagybetűs, így nincs hatása"
./SAVANNAH-crawl/texinfo/po/eo.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/eo.po:#~ msgstr "argumento de @sc tute majusklas, do neniel efikas"
./SAVANNAH-crawl/texinfo/po/id.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/id.po:#~ msgstr "@sc argumen semuanya huruf besar, jadi tidak ada efek"
./SAVANNAH-crawl/texinfo/po/nb.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/nb.po:#~ msgstr "@sc-argument med store bokstaver, dermed ingen effekt"
./SAVANNAH-crawl/texinfo/po/ru.po:#~ msgid "@sc argument all uppercase, thus no effect"
./SAVANNAH-crawl/texinfo/po/ru.po:#~ msgstr "весь аргумент @sc набран заглавными буквами, результата не будет"
./SAVANNAH-crawl/texinfo/ChangeLog.46: cm_var and cm_sc, since @var and @sc have different effects in
./SAVANNAH-crawl/texinfo/ChangeLog.46: From: Khimenko Victor
./SAVANNAH-crawl/texinfo/ChangeLog.46: suggestion from: Reiner Schlotte .
./SAVANNAH-crawl/texinfo/ChangeLog.46: .
./SAVANNAH-crawl/texinfo/tp/tests/coverage_macro.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/chapter2.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/subsection.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/anchor.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting_abt.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/chapter.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting_ovr.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/subsubsection-three_002d_002d_002dfour_002d_002d_002d_002d_0027_0027.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/index.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/s_002d_002dect_002cion.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/subsubsection-_0060_0060simple_002ddouble_002d_002d.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_chm/formatting_toc.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_fr_icons/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_fr_icons/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_fr_icons/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_fr_icons/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_fr_icons/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_fr_icons/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/chapter2.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/subsection.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/anchor.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/formatting_fot.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/formatting_abt.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/chapter.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/formatting_ovr.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/subsubsection-three_002d_002d_002dfour_002d_002d_002d_002d_0027_0027.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/index.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/index.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/s_002d_002dect_002cion.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/subsubsection-_0060_0060simple_002ddouble_002d_002d.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html_nodes/formatting_toc.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_xml/formatting.xml:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_mathjax/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_mathjax/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_mathjax/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_mathjax/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_mathjax/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_mathjax/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_docbook/formatting.xml:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_docbook/formatting.xml:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_docbook/formatting.xml:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_docbook/formatting.xml:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_docbook/formatting.xml:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_docbook/formatting.xml:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_regions/formatting_regions.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_regions/formatting_regions.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_regions/formatting_regions.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_regions/formatting_regions.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_regions/formatting_regions.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_regions/formatting_regions.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_plaintext/formatting.txt:'@r{--a}' -a '@samp{--a}' '--a' '@sc{--a}' -A '@strong{--a}' *-a*
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_plaintext/formatting.txt:'@r{--a}' -a '@samp{--a}' '--a' '@sc{--a}' -A '@strong{--a}' *-a*
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_plaintext/formatting.txt: @sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/chapter2.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/subsection.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/anchor.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/formatting_fot.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/formatting_abt.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/chapter.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/formatting_ovr.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/subsubsection-three_002d_002d_002dfour_002d_002d_002d_002d_0027_0027.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/index.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/index.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/s_002d_002dect_002cion.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/subsubsection-_0060_0060simple_002ddouble_002d_002d.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_nodes/formatting_toc.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html32/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html32/formatting.html:@sc{--a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html32/formatting.html:@sc{--a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html32/formatting.html:@sc{--a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html32/formatting.html:@sc{--a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_html32/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/chapter2.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/subsection.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/anchor.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/formatting_abt.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/chapter.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/formatting_ovr.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/subsubsection-three_002d_002d_002dfour_002d_002d_002d_002d_0027_0027.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/index.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/index.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/index.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/s_002d_002dect_002cion.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/subsubsection-_0060_0060simple_002ddouble_002d_002d.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_exotic/formatting_toc.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_weird_quotes/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_weird_quotes/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_weird_quotes/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_weird_quotes/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_weird_quotes/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/layout/res_parser/formatting_weird_quotes/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/chapter2.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/subsection.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/anchor.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/sing_fot.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/sing_toc.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/sing_ovr.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/chapter.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/index.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/index.htm:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/index.htm:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/index.htm:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/subsubsection-three_002d_002d_002dfour_002d_002d_002d_002d_0027_0027.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/index.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/sing_abt.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/s_002d_002dect_002cion.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular_tex4ht/subsubsection-_0060_0060simple_002ddouble_002d_002d.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/chapter2.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/subsection.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/anchor.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/sing_fot.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/sing_toc.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/sing_ovr.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/chapter.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/index.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/index.htm:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/index.htm:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/index.htm:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/subsubsection-three_002d_002d_002dfour_002d_002d_002d_002d_0027_0027.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/index.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/sing_abt.htm:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/s_002d_002dect_002cion.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/tex_html/res_parser/formatting_singular/subsubsection-_0060_0060simple_002ddouble_002d_002d.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/formatting/formatting.html:@sc{-a} -A
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/formatting/formatting.html:@sc{--a} –A
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser/formatting/formatting.html:@sc{--a} --A
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser_info/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser_info/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser_info/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser_info/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser_info/texi_formatting/formatting.texi:@code{@@sc@{--a@}} @sc{--a}
Binary file ./SAVANNAH-crawl/texinfo/tp/tests/coverage/res_parser_info/formatting/formatting.info matches
./SAVANNAH-crawl/texinfo/tp/TODO:Test @sc{@aa{}} and @sc{@'e} in HTML with 8bit and utf8, with and without
./SAVANNAH-crawl/texinfo/tp/t/10menu.t:* @sc{value}:@sc{node}. @sc{descrip tion}
./SAVANNAH-crawl/texinfo/tp/t/10menu.t:@sc{menu comment}
./SAVANNAH-crawl/texinfo/tp/t/10menu.t:* @sc{menu-example value}:(dir)@sc{menu-example node}. @sc{menu-example descrip tion}
./SAVANNAH-crawl/texinfo/tp/t/10menu.t:@sc{menu-example comment}
./SAVANNAH-crawl/texinfo/tp/t/10menu.t:@node @sc{node}
./SAVANNAH-crawl/texinfo/tp/t/10menu.t:* @sc{example value}:(dir)@sc{example node}. @sc{example descrip tion}
./SAVANNAH-crawl/texinfo/tp/t/10menu.t:@sc{example comment}
./SAVANNAH-crawl/texinfo/tp/t/html_tests.t:@settitle @@title @sc{html} @code{test}
./SAVANNAH-crawl/texinfo/tp/t/html_tests.t:@top Top of @@title @sc{html} @code{test}
./SAVANNAH-crawl/texinfo/tp/t/html_tests.t:@sc{@AA{} @~{@dotless{i}} @dotless{i}}.
./SAVANNAH-crawl/texinfo/tp/t/02coverage.t:--- -- \'\' ``. @sc{small caps}.
./SAVANNAH-crawl/texinfo/tp/t/results/float/complex_float.pl:@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.
./SAVANNAH-crawl/texinfo/tp/t/results/float/complex_float.pl:@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.
./SAVANNAH-crawl/texinfo/tp/t/results/float/complex_float.pl:@shortcaption{@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.}
./SAVANNAH-crawl/texinfo/tp/t/results/float/complex_float.pl:@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_utf8.pl:* @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}::
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_utf8.pl:@node @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_utf8.pl:@chapter @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_utf8.pl:@ref{@cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}}
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_latin1.pl:* @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}::
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_latin1.pl:@node @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_latin1.pl:@chapter @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs_latin1.pl:@ref{@cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}}
Binary file ./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/at_commands_in_refs.pl matches
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/some_at_commands_in_ref_nodes.pl:* A @sc{sc @~n @aa{} @TeX{}} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}::
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/some_at_commands_in_ref_nodes.pl:@node A @sc{sc @~n @aa{} @TeX{}} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/some_at_commands_in_ref_nodes.pl:@chapter A @sc{sc} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}
./SAVANNAH-crawl/texinfo/tp/t/results/converters_tests/some_at_commands_in_ref_nodes.pl:see @ref{a @strong{strong} ref with @sc{sc}@comma{} a i trema @"i@comma{} a dotless i trema @"{@dotless{i}} @`{@=E} and exclamdown @exclamdown{},,,manual}.
./SAVANNAH-crawl/texinfo/tp/t/results/coverage_braces/nested_in_sc.pl:$result_texis{'nested_in_sc'} = '@sc{@sc{aaa @~n @aa{} @TeX{} @~{@aa{}} @footnote{In footnote}, @abbr{ABr, expl},
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/sc_with_utf8_enable_encoding.pl:@sc{in sc}.
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/punctuation_and_upper_case_commands_utf8.pl:@sc{aaa}. @sc{@~e}. @sc{@aa{}}.
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/punctuation_and_upper_case_commands_utf8.pl:@sc{AAA}. @sc{@~E}. @sc{@AA{}}.
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/punctuation_and_upper_case_commands_utf8.pl:@sc{double AAA}. @sc{double @~E}. @sc{double @AA{}}. End.
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/punctuation_and_upper_case_commands.pl:@sc{aaa}. @sc{@~e}. @sc{@aa{}}.
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/punctuation_and_upper_case_commands.pl:@sc{AAA}. @sc{@~E}. @sc{@AA{}}.
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/punctuation_and_upper_case_commands.pl:@sc{double AAA}. @sc{double @~E}. @sc{double @AA{}}. End.
./SAVANNAH-crawl/texinfo/tp/t/results/plaintext_tests/punctuation_in_sc.pl:$result_texis{'punctuation_in_sc'} = 'one @sc{two.} three @sc{FOUR.} five';
./SAVANNAH-crawl/texinfo/tp/t/results/menu/sc_in_menu.pl:* @sc{value}:@sc{node}. @sc{descrip tion}
./SAVANNAH-crawl/texinfo/tp/t/results/menu/sc_in_menu.pl:@sc{menu comment}
./SAVANNAH-crawl/texinfo/tp/t/results/menu/sc_in_menu.pl:* @sc{menu-example value}:(dir)@sc{menu-example node}. @sc{menu-example descrip tion}
./SAVANNAH-crawl/texinfo/tp/t/results/menu/sc_in_menu.pl:@sc{menu-example comment}
./SAVANNAH-crawl/texinfo/tp/t/results/menu/sc_in_menu.pl:@node @sc{node}
./SAVANNAH-crawl/texinfo/tp/t/results/menu/sc_in_menu.pl:* @sc{example value}:(dir)@sc{example node}. @sc{example descrip tion}
./SAVANNAH-crawl/texinfo/tp/t/results/menu/sc_in_menu.pl:@sc{example comment}
./SAVANNAH-crawl/texinfo/tp/t/results/sectioning/at_commands_in_node.pl:$result_texis{'at_commands_in_node'} = '@node A @sc{sc} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}';
./SAVANNAH-crawl/texinfo/tp/t/results/coverage/commands.pl:--- -- \'\' ``. @sc{small caps}.
./SAVANNAH-crawl/texinfo/tp/t/results/html_tests/titles.pl:@settitle @@title @sc{html} @code{test}
./SAVANNAH-crawl/texinfo/tp/t/results/html_tests/titles.pl:@top Top of @@title @sc{html} @code{test}
./SAVANNAH-crawl/texinfo/tp/t/nodenormalization.t:Para. @LaTeX{}, @sc{@AA{} bbb}. @image{unknown,,,}. @ref{index}
./SAVANNAH-crawl/texinfo/tp/t/nodenormalization.t:my $texi_line = 'A @sc{sc} accents @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @={@,{@~{n}}} @v{@\'{r}} @={@~{@dotless{i}}} @"y @dotless{i} @dotless{j} @,{C} @ogonek{E} @udotaccent{a} @tieaccent{a} @dotaccent{a} characters @l{} @exclamdown{} @aa{} @oe{} @comma{} @error{} @today{} @dots{} @enddots{} no brace commands @@ @: @. @ @* @} signs -- --- `` \'\' !_"#$%&\'()*+-. /;<=>?[\\]^_`|~';
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:* @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}::
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:@node @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:@chapter @cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:@ref{@cite{cite @asis{asis}} @w{in @@w @b{b}} @r{in r} @sc{sc} @strong{str} @t{t} @var{var} @dfn{dfn} @i{i}}
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:* A @sc{sc @~n @aa{} @TeX{}} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}::
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:@node A @sc{sc @~n @aa{} @TeX{}} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:@chapter A @sc{sc} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}
./SAVANNAH-crawl/texinfo/tp/t/converters_tests.t:see @ref{a @strong{strong} ref with @sc{sc}@comma{} a i trema @"i@comma{} a dotless i trema @"{@dotless{i}} @`{@=E} and exclamdown @exclamdown{},,,manual}.
./SAVANNAH-crawl/texinfo/tp/t/03coverage_braces.t:'@sc{@sc{aaa @~n @aa{} @TeX{} @~{@aa{}} @footnote{In footnote}, @abbr{ABr, expl},
./SAVANNAH-crawl/texinfo/tp/t/27float.t:@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.
./SAVANNAH-crawl/texinfo/tp/t/27float.t:@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.
./SAVANNAH-crawl/texinfo/tp/t/27float.t:@shortcaption{@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.}
./SAVANNAH-crawl/texinfo/tp/t/27float.t:@TeX{} and @emph{@b{t@\'e@^{@dotless{i}}}@url{an_url}} @sc{and} @verb{!it is @verb!} @ a wo@-rd @!@@ @AE{}.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:['punctuation_in_sc', 'one @sc{two.} three @sc{FOUR.} five'],
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@sc{in sc}.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@sc{aaa}. @sc{@~e}. @sc{@aa{}}.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@sc{AAA}. @sc{@~E}. @sc{@AA{}}.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@sc{double AAA}. @sc{double @~E}. @sc{double @AA{}}. End.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@sc{aaa}. @sc{@~e}. @sc{@aa{}}.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@sc{AAA}. @sc{@~E}. @sc{@AA{}}.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@sc{double AAA}. @sc{double @~E}. @sc{double @AA{}}. End.
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:'@code{@samp{@code{@sc{@b{@var{@code{@samp{@code{@sc{@b{@var{
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@code{@samp{@code{@sc{@b{@var{@code{@samp{@code{@sc{@b{@var{
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@code{@samp{@code{@sc{@b{@var{@code{@samp{@code{@sc{@b{@var{
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@code{@samp{@code{@sc{@b{@var{@code{@samp{@code{@sc{@b{@var{
./SAVANNAH-crawl/texinfo/tp/t/plaintext_tests.t:@code{@samp{@code{@sc{@b{@var{@code{@samp{@code{@sc{@b{@var{
./SAVANNAH-crawl/texinfo/tp/t/30sectioning.t:'@node A @sc{sc} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@\'C} @exclamdown{}'
./SAVANNAH-crawl/texinfo/tp/t/input_files/at_commands_in_refs.texi:* A @sc{sc} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@'C} @exclamdown{}::
./SAVANNAH-crawl/texinfo/tp/t/input_files/at_commands_in_refs.texi:@node A @sc{sc} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@'C} @exclamdown{}
./SAVANNAH-crawl/texinfo/tp/t/input_files/at_commands_in_refs.texi:@chapter A @sc{sc} node @"i @"{@dotless{i}} @`{@=E} @l{} @,{@'C} @exclamdown{}
./SAVANNAH-crawl/texinfo/tp/t/input_files/at_commands_in_refs.texi:see @ref{a @strong{strong} ref with @sc{sc}@comma{} a i trema @"i@comma{} a dotless i trema @"{@dotless{i}} @`{@=E} and exclamdown @exclamdown{},,,manual}.
./SAVANNAH-crawl/texinfo/tp/maintain/lib/Unicode-EastAsianWidth/inc/Module/Install/Metadata.pm:my @scalar_keys = qw{
./SAVANNAH-crawl/texinfo/tp/maintain/lib/Unicode-EastAsianWidth/inc/Module/Install/Metadata.pm:sub Meta_ScalarKeys { @scalar_keys }
./SAVANNAH-crawl/texinfo/tp/maintain/lib/Unicode-EastAsianWidth/inc/Module/Install/Metadata.pm:foreach my $key (@scalar_keys) {
./SAVANNAH-crawl/texinfo/tp/Texinfo/Convert/Plaintext.pm: # is the case whether we are in @sc or not.
./SAVANNAH-crawl/dvipng/macros.texi:@sc{\text\}
./SAVANNAH-crawl/parted/doc/parted-pt_BR.texi:@sc{tm}.
./SAVANNAH-crawl/ratpoison/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/www-ja/www/licenses/old-licenses/fdl-1.1.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SAVANNAH-crawl/www-ja/www/licenses/old-licenses/fdl-1.2.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/www-ja/www/patent-examp/patent-examples.texi:Marc van Woerkom @email{marc.vanwoerkom@@science-factory.com}
./SAVANNAH-crawl/www-ja/www/philosophy/fsfs2/foreword.texi:@sc{Lawrence Lessig}
./SAVANNAH-crawl/www-ja/www/philosophy/fsfs2/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/www-ja/www/philosophy/fsfs2/texinfo.tex.used:% Explicit font changes: @r, @sc, undocumented @ii.
./SAVANNAH-crawl/www-ja/www/philosophy/fsfs/texinfo_times.tex:% Explicit font changes: @r, @sc, undocumented @ii.
./SAVANNAH-crawl/www-ja/www/philosophy/fsfs/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SAVANNAH-crawl/gnupod/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/rpge/doc/fdl.texi~:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/muesli/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/3dldf/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/3dldf/doc/old_doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/emms/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/guile-lib/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/guile-lib/src/texinfo/indexing.scm:The returned index is a list of pairs, the @sc{car} of which is the
./SAVANNAH-crawl/guile-lib/src/texinfo/indexing.scm:entry (a string) and the @sc{cdr} of which is a node name (a string)."
./SAVANNAH-crawl/grip/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/riece/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SAVANNAH-crawl/mpria/doc/mpria.texi:either the one digit version number @sc{MAJOR},
./SAVANNAH-crawl/mpria/doc/mpria.texi:the two digit dotted version number @sc{MAJOR.Minor}
./SAVANNAH-crawl/mpria/doc/mpria.texi:or the three digit dotted version number @sc{MAJOR.Minor.micro}
./SAVANNAH-crawl/bash/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/bash/doc/bashref.texi:for the @sc{gnu} operating system.
./SAVANNAH-crawl/bash/doc/bashref.texi:It is intended to be a conformant implementation of the @sc{ieee}
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{posix} Shell and Tools portion of the @sc{ieee} @sc{posix}
./SAVANNAH-crawl/bash/doc/bashref.texi:specification (@sc{ieee} Standard 1003.1).
./SAVANNAH-crawl/bash/doc/bashref.texi:While the @sc{gnu} operating system provides other shells, including
./SAVANNAH-crawl/bash/doc/bashref.texi:Like other @sc{gnu} software, Bash is quite portable. It currently runs
./SAVANNAH-crawl/bash/doc/bashref.texi:independently-supported ports exist for @sc{ms-dos}, @sc{os/2},
./SAVANNAH-crawl/bash/doc/bashref.texi:interface to the rich set of @sc{gnu} utilities. The programming
./SAVANNAH-crawl/bash/doc/bashref.texi:A shell allows execution of @sc{gnu} commands, both synchronously and
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{posix} 1003.1 standard.
./SAVANNAH-crawl/bash/doc/bashref.texi:group @sc{id}.
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{posix} standard.
./SAVANNAH-crawl/bash/doc/bashref.texi:The rules for evaluation and quoting are taken from the @sc{posix}
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{posix} mode (@pxref{Bash POSIX Mode}),
./SAVANNAH-crawl/bash/doc/bashref.texi:by the @sc{posix} 1003.1 @code{waitpid} function, or 128+@var{n} if
./SAVANNAH-crawl/bash/doc/bashref.texi:by @sc{posix}.
./SAVANNAH-crawl/bash/doc/bashref.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}),
./SAVANNAH-crawl/bash/doc/bashref.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}), @code{time}
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{and} and @sc{or} lists are sequences of one or more pipelines
./SAVANNAH-crawl/bash/doc/bashref.texi:respectively. @sc{and} and @sc{or} lists are executed with left
./SAVANNAH-crawl/bash/doc/bashref.texi:An @sc{and} list has the form
./SAVANNAH-crawl/bash/doc/bashref.texi:An @sc{or} list has the form
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{and} and @sc{or} lists is the exit status of the last command
./SAVANNAH-crawl/bash/doc/bashref.texi:a @sc{posix} extended regular expression and matched accordingly
./SAVANNAH-crawl/bash/doc/bashref.texi:(using the @sc{posix} @code{regcomp} and @code{regexec} interfaces
./SAVANNAH-crawl/bash/doc/bashref.texi:When the shell is in @sc{posix} mode (@pxref{Bash POSIX Mode}),
./SAVANNAH-crawl/bash/doc/bashref.texi:When in @sc{posix} mode (@pxref{Bash POSIX Mode}), these builtins may appear
./SAVANNAH-crawl/bash/doc/bashref.texi:($$) Expands to the process @sc{id} of the shell. In a @code{()} subshell, it
./SAVANNAH-crawl/bash/doc/bashref.texi:expands to the process @sc{id} of the invoking shell, not the subshell.
./SAVANNAH-crawl/bash/doc/bashref.texi:($!) Expands to the process @sc{id} of the job most recently placed into the
./SAVANNAH-crawl/bash/doc/bashref.texi:above, when in @sc{posix} mode.
./SAVANNAH-crawl/bash/doc/bashref.texi:pipes (@sc{fifo}s) or the @file{/dev/fd} method of naming open files.
./SAVANNAH-crawl/bash/doc/bashref.texi:The @sc{nul} character may not occur in a pattern.
./SAVANNAH-crawl/bash/doc/bashref.texi:following classes defined in the @sc{posix} standard:
./SAVANNAH-crawl/bash/doc/bashref.texi:various process @sc{id}s, including those of background jobs
./SAVANNAH-crawl/bash/doc/bashref.texi:the @option{-e} option from the parent shell. When not in @sc{posix} mode,
./SAVANNAH-crawl/bash/doc/bashref.texi:Many of the builtins have been extended by @sc{posix} or Bash.
./SAVANNAH-crawl/bash/doc/bashref.texi:These commands are implemented as specified by the @sc{posix} standard.
./SAVANNAH-crawl/bash/doc/bashref.texi:When Bash is not in @sc{posix} mode, the current directory is searched
./SAVANNAH-crawl/bash/doc/bashref.texi:Some of these commands are specified in the @sc{posix} standard.
./SAVANNAH-crawl/bash/doc/bashref.texi:The @option{-s} option restricts @code{enable} to the @sc{posix} special
./SAVANNAH-crawl/bash/doc/bashref.texi:The maximum number of bytes in @sc{posix} message queues.
./SAVANNAH-crawl/bash/doc/bashref.texi:and, when in @sc{posix} Mode (@pxref{Bash POSIX Mode}),
./SAVANNAH-crawl/bash/doc/bashref.texi:In @sc{posix} mode, only shell variables are listed.
./SAVANNAH-crawl/bash/doc/bashref.texi:from the @sc{posix} standard to match the standard
./SAVANNAH-crawl/bash/doc/bashref.texi:If set, shell error messages are written in the standard @sc{gnu} error
./SAVANNAH-crawl/bash/doc/bashref.texi:This option is enabled when @sc{posix} mode is enabled.
./SAVANNAH-crawl/bash/doc/bashref.texi:For historical reasons, the @sc{posix} standard has classified
./SAVANNAH-crawl/bash/doc/bashref.texi:When Bash is executing in @sc{posix} mode, the special builtins
./SAVANNAH-crawl/bash/doc/bashref.texi:When Bash is not executing in @sc{posix} mode, these builtins behave no
./SAVANNAH-crawl/bash/doc/bashref.texi:The Bash @sc{posix} mode is described in @ref{Bash POSIX Mode}.
./SAVANNAH-crawl/bash/doc/bashref.texi:These are the @sc{posix} special builtins:
./SAVANNAH-crawl/bash/doc/bashref.texi:Bash will not allow this value to be decreased below a @sc{posix}-mandated
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{posix} Mode (@pxref{Bash POSIX Mode}).
./SAVANNAH-crawl/bash/doc/bashref.texi:is executing, in the standard @sc{gnu} @var{cpu-company-system} format.
./SAVANNAH-crawl/bash/doc/bashref.texi:enters @sc{posix} mode (@pxref{Bash POSIX Mode}) before reading the
./SAVANNAH-crawl/bash/doc/bashref.texi:If it is set while the shell is running, Bash enables @sc{posix} mode,
./SAVANNAH-crawl/bash/doc/bashref.texi:When the shell enters @sc{posix} mode, it sets this variable if it was
./SAVANNAH-crawl/bash/doc/bashref.texi:The process @sc{id} of the shell's parent process. This variable
./SAVANNAH-crawl/bash/doc/bashref.texi:in the @sc{gnu} @code{gettext} PO (portable object) file format.
./SAVANNAH-crawl/bash/doc/bashref.texi:Do not use the @sc{gnu} Readline library (@pxref{Command Line Editing})
./SAVANNAH-crawl/bash/doc/bashref.texi:from the @sc{posix} standard to match the standard. This
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{posix} mode.
./SAVANNAH-crawl/bash/doc/bashref.texi:possible, while conforming to the @sc{posix} standard as well.
./SAVANNAH-crawl/bash/doc/bashref.texi:When invoked as @code{sh}, Bash enters @sc{posix} mode after
./SAVANNAH-crawl/bash/doc/bashref.texi:@subsubheading Invoked in @sc{posix} mode
./SAVANNAH-crawl/bash/doc/bashref.texi:When Bash is started in @sc{posix} mode, as with the
./SAVANNAH-crawl/bash/doc/bashref.texi:@option{--posix} command line option, it follows the @sc{posix} standard
./SAVANNAH-crawl/bash/doc/bashref.texi:@subsubheading Invoked with unequal effective and real @sc{uid/gid}s
./SAVANNAH-crawl/bash/doc/bashref.texi:When running in @sc{posix} mode, a special builtin returning an error
./SAVANNAH-crawl/bash/doc/bashref.texi:@samp{=} should be used with the @code{test} command for @sc{posix} conformance.
./SAVANNAH-crawl/bash/doc/bashref.texi:closely to the @sc{posix} standard by changing the behavior to
./SAVANNAH-crawl/bash/doc/bashref.texi:match that specified by @sc{posix} in areas where the Bash default differs.
./SAVANNAH-crawl/bash/doc/bashref.texi:When invoked as @code{sh}, Bash enters @sc{posix} mode after reading the
./SAVANNAH-crawl/bash/doc/bashref.texi:The following list is what's changed when `@sc{posix} mode' is in effect:
./SAVANNAH-crawl/bash/doc/bashref.texi:The @sc{posix} @env{PS1} and @env{PS2} expansions of @samp{!} to
./SAVANNAH-crawl/bash/doc/bashref.texi:The @sc{posix} startup files are executed (@env{$ENV}) rather than
./SAVANNAH-crawl/bash/doc/bashref.texi:Function names may not be the same as one of the @sc{posix} special
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{posix} special builtins are found before shell functions
./SAVANNAH-crawl/bash/doc/bashref.texi:If a @sc{posix} special builtin returns an error status, a
./SAVANNAH-crawl/bash/doc/bashref.texi:the @sc{posix} standard, and include things like passing incorrect options,
./SAVANNAH-crawl/bash/doc/bashref.texi:Assignment statements preceding @sc{posix} special builtins
./SAVANNAH-crawl/bash/doc/bashref.texi:when not in @sc{posix} mode, assignment builtins lose their assignment
./SAVANNAH-crawl/bash/doc/bashref.texi:output in the format required by @sc{posix}.
./SAVANNAH-crawl/bash/doc/bashref.texi:Enabling @sc{posix} mode has the effect of setting the
./SAVANNAH-crawl/bash/doc/bashref.texi:Enabling @sc{posix} mode has the effect of setting the
./SAVANNAH-crawl/bash/doc/bashref.texi:There is other @sc{posix} behavior that Bash does not implement by
./SAVANNAH-crawl/bash/doc/bashref.texi:default even when in @sc{posix} mode.
./SAVANNAH-crawl/bash/doc/bashref.texi:Bash can be configured to be @sc{posix}-conformant by default, by specifying
./SAVANNAH-crawl/bash/doc/bashref.texi:recognized as a reserved word (this is @sc{posix} interpretation 267)
./SAVANNAH-crawl/bash/doc/bashref.texi:(this is @sc{posix} interpretation 221)
./SAVANNAH-crawl/bash/doc/bashref.texi:(this is part of @sc{posix} interpretation 221);
./SAVANNAH-crawl/bash/doc/bashref.texi:indicating that this job is job number 1 and that the process @sc{id}
./SAVANNAH-crawl/bash/doc/bashref.texi:process group @sc{id}. Members of this process group (processes whose
./SAVANNAH-crawl/bash/doc/bashref.texi:process group @sc{id} is equal to the current terminal process group
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{id}) receive keyboard-generated signals such as @code{SIGINT}.
./SAVANNAH-crawl/bash/doc/bashref.texi:processes are those whose process group @sc{id} differs from the
./SAVANNAH-crawl/bash/doc/bashref.texi:List process @sc{id}s in addition to the normal information.
./SAVANNAH-crawl/bash/doc/bashref.texi:List only the process @sc{id} of the job's process group leader.
./SAVANNAH-crawl/bash/doc/bashref.texi:corresponding process group @sc{id}, and executes @var{command},
./SAVANNAH-crawl/bash/doc/bashref.texi:named by job specification @var{jobspec} or process @sc{id} @var{pid}.
./SAVANNAH-crawl/bash/doc/bashref.texi:Wait until the child process specified by each process @sc{id} @var{pid}
./SAVANNAH-crawl/bash/doc/bashref.texi:supplied process @sc{id}s.
./SAVANNAH-crawl/bash/doc/bashref.texi:analogous to the @samp{%?} job @sc{id} (@pxref{Job Control Basics}).
./SAVANNAH-crawl/bash/doc/bashref.texi:analogous to the @samp{%} job @sc{id}.
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{gnu} operating systems, nearly every version of Unix, and several
./SAVANNAH-crawl/bash/doc/bashref.texi:@sc{ms-dos}, @sc{os/2}, and Windows platforms.
./SAVANNAH-crawl/bash/doc/bashref.texi:@code{malloc} that appears in @sc{gnu} libc, but an older version
./SAVANNAH-crawl/bash/doc/bashref.texi:originally derived from the 4.2 @sc{bsd} @code{malloc}. This @code{malloc}
./SAVANNAH-crawl/bash/doc/bashref.texi:Include support for matching @sc{posix} regular expressions using the
./SAVANNAH-crawl/bash/doc/bashref.texi:Make Bash @sc{posix}-conformant by default (@pxref{Bash POSIX Mode}).
./SAVANNAH-crawl/bash/doc/bashref.texi:Bash uses the @sc{posix} standard as the specification of
./SAVANNAH-crawl/bash/doc/bashref.texi:Bash is @sc{posix}-conformant, even where the @sc{posix} specification
./SAVANNAH-crawl/bash/doc/bashref.texi:Bash includes the @sc{posix} pattern removal @samp{%}, @samp{#}, @samp{%%}
./SAVANNAH-crawl/bash/doc/bashref.texi:The @sc{posix} @code{$()} form of command substitution
./SAVANNAH-crawl/bash/doc/bashref.texi:Bash implements the full set of @sc{posix} filename expansion operators,
./SAVANNAH-crawl/bash/doc/bashref.texi:is slightly different, as it implements the @sc{posix} algorithm,
./SAVANNAH-crawl/bash/doc/bashref.texi:and effective @sc{uid} and @sc{gid} if they are less than some
./SAVANNAH-crawl/bash/doc/bashref.texi:a script only if one of the @sc{posix} special builtins fails, and
./SAVANNAH-crawl/bash/doc/bashref.texi:only for certain failures, as enumerated in the @sc{posix} standard.
./SAVANNAH-crawl/bash/lib/readline/doc/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library
./SAVANNAH-crawl/bash/lib/readline/doc/hsuser.texi:For information on using the @sc{gnu} History Library in other programs,
./SAVANNAH-crawl/bash/lib/readline/doc/hsuser.texi:see the @sc{gnu} Readline Library Manual.
./SAVANNAH-crawl/bash/lib/readline/doc/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library interactively,
./SAVANNAH-crawl/bash/lib/readline/doc/hsuser.texi:information on using the @sc{gnu} History Library in your own programs,
./SAVANNAH-crawl/bash/lib/readline/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:This chapter describes the basic features of the @sc{gnu}
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:eighth bit set to an @sc{ascii} key sequence by stripping the eighth
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:the key sequence in double quotes. Some @sc{gnu} Emacs style key
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:The following @sc{gnu} Emacs style escape sequences are available when
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:In addition to the @sc{gnu} Emacs style escape sequences, a second
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:interprets it as the end of input and returns @sc{eof}.
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:same character as the tty @sc{eof} character, as @kbd{C-d}
./SAVANNAH-crawl/bash/lib/readline/doc/rluser.texi:the @sc{posix} standard.
./SAVANNAH-crawl/bash/lib/readline/doc/rltech.texi:This chapter describes the interface between the @sc{gnu} Readline Library and
./SAVANNAH-crawl/bash/lib/readline/doc/rltech.texi:features found in @sc{gnu} Readline
./SAVANNAH-crawl/bash/lib/readline/doc/rltech.texi:Always set to 1, denoting that this is @sc{gnu} readline rather than some
./SAVANNAH-crawl/bash/lib/readline/doc/hstech.texi:with the @sc{gnu} History Library.
./SAVANNAH-crawl/bash/lib/readline/doc/hstech.texi:For information on the interactive use of @sc{gnu} History, @pxref{Using
./SAVANNAH-crawl/bash/lib/readline/doc/hstech.texi:Many programs read input from the user a line at a time. The @sc{gnu}
./SAVANNAH-crawl/bash/lib/readline/doc/hstech.texi:exported by the @sc{gnu} History library.
./SAVANNAH-crawl/bash/lib/readline/doc/hstech.texi:the @sc{gnu} History Library.
./SAVANNAH-crawl/bash/lib/readline/doc/hstech.texi:The following program demonstrates simple use of the @sc{gnu} History Library.
./SAVANNAH-crawl/femlisp/doc/femlisp.texinfo:@sc{Femlisp}
./SAVANNAH-crawl/gama/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SAVANNAH-crawl/radius/doc/texinfo/radius.texi:@cindex @sc{nas}
./SAVANNAH-crawl/radius/doc/texinfo/radius.texi:@item Session @sc{id}
./SAVANNAH-crawl/radius/doc/texinfo/radlast.texi:@item Session @sc{id}
./SAVANNAH-crawl/radius/doc/texinfo/radlast.texi:@item Caller @sc{id}
./SAVANNAH-crawl/radius/doc/texinfo/radlast.texi:If multiple arguments are given, the logical @sc{or} operation between them
./SAVANNAH-crawl/radius/doc/texinfo/radlast.texi:always combined with the rest of command line by logical @sc{and}.
./SAVANNAH-crawl/radius/doc/texinfo/radwho.texi:Unique session @sc{id} assigned by the terminal server.
./SAVANNAH-crawl/radius/doc/texinfo/radwho.texi:Caller station @sc{id} ad reported by the @NAS{}.
./SAVANNAH-crawl/radius/doc/texinfo/radwho.texi:Display the calling station @sc{id} in the second column. Equivalent to
./SAVANNAH-crawl/radius/doc/texinfo/radwho.texi:Display session @sc{id} instead of @sc{gecos} in the second column.
./SAVANNAH-crawl/radius/doc/texinfo/radwho.texi:The @sc{gecos} field from the local @file{/etc/passwd} corresponding
./SAVANNAH-crawl/radius/doc/texinfo/radwho.texi:are: login name, @sc{gecos} name, connection protocol, port number, time when
./SAVANNAH-crawl/radius/doc/texinfo/radtest.texi:@sc{ip}v4 addresses. These can be input either as decimal numbers or
./SAVANNAH-crawl/radius/doc/texinfo/client.texi:Set the session @sc{id} (@attr{Acct-Session-Id} attribute).
./SAVANNAH-crawl/radius/doc/texinfo/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:physical connection on the @NAS{}, not in the sense of a @sc{tcp} or
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:@sc{udp} port number.
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:attribute value. For example, the @sc{max a}scend terminal server constructs
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:A rewrite function for @sc{max a}scend servers is provided in the
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:value is @sc{xor}ed with the first 16 octet segment of the password and
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:is @sc{xor}ed with the second 16 octet segment of the password and
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:If necessary, this operation is repeated, with each @sc{xor} result
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:to @sc{xor} the next segment of the password, up to no more than 128
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:This attribute is a unique accounting @sc{id} to make it easy to match
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:The MD5-encrypted user's password is queried from the @sc{sql} database
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:his calling station @sc{id} followed by a newline will be sent to the
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:of the user's entry. The values of these attributes @sc{or}ed together
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:form a mask, which is applied via an @sc{xor} operation to the current log
./SAVANNAH-crawl/radius/doc/texinfo/attributes.texi:Now, user @samp{johns}, having a valid account in the @sc{sql} database,
./SAVANNAH-crawl/radius/doc/texinfo/config.texi:@sc{radius}
./SAVANNAH-crawl/radius/doc/texinfo/config.texi:@sc{nas}
./SAVANNAH-crawl/radius/doc/texinfo/config.texi:@sc{a/v} pair
./SAVANNAH-crawl/radius/doc/texinfo/config.texi:@sc{lhs}
./SAVANNAH-crawl/radius/doc/texinfo/config.texi:@sc{rhs}
./SAVANNAH-crawl/radius/doc/texinfo/config.texi:@sc{ip} address
./SAVANNAH-crawl/radius/doc/texinfo/config.texi:@sc{unix}
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:Cisco @sc{as5300} terminal server used as a voice-over IP router packs
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:it obtains the form prescribed by @sc{rfc}s and its further processing
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:For example, in the case of the @sc{as5300} router, a corresponding Rewrite
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:@subheading 1. Port rewriting for @sc{max a}scend terminal servers
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:Some @sc{max a}scend terminal servers pack additional information
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:@subheading 2. Session @sc{id} parsing for Cisco AS 5300 series
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:Cisco @sc{voip ios} encodes a lot of other information into its
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:@samp{/} character is the actual session @sc{id}.
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:(vendor @sc{pec} 9), which is a string in the form @samp{ISDN 9:D:999}
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:@subheading 3. User-name rewriting for @sc{nt} machines
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:Users coming from Windows @sc{nt} machines often authenticate themselves as
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:Port @sc{id} of the session.
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:Session @sc{id}.
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:@c{tty} number (port @sc{id}); and the seventh field, the session @sc{id}.
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:user name and port and session @sc{id}s:
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:can be coerced to an integer if it contains a valid @sc{ascii} representation
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:to a string, the result of such coercion being the @sc{ascii} string
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:an @sc{ascii} character itself or of its value, enclosed in a pair of
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:@tab If the string value of the variable is a valid @sc{ascii} representation
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:@tab The @sc{ascii} representation (in decimal) of the integer number.
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:Returns the source @sc{udp} port.
./SAVANNAH-crawl/radius/doc/texinfo/extensions.texi:The session @sc{id}
./SAVANNAH-crawl/radius/doc/texinfo/radzap.texi:joined by the logical @sc{and} operation.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Contains the configuration for the @sc{sql} system. This includes the
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:type of @sc{sql} interface used, the IP and port number of the server
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:and the definition of the @sc{sql} requests used by @command{radiusd}.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Add the process @sc{id} of the process generating the logging information.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Sets the number of which @sc{udp} port to listen on for the
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:as well, unless you supply an alternative @sc{mlc} method (currently
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:@sc{sql}, @xref{Multiple Login Checking}, for the detailed discussion
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:will use @sc{sql} database.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:method specified by @sc{rfc 2865}. However some @NAS{}es, most notably
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:@sc{max a}scend series, implement a broken method of encoding long
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:This type suits for @sc{unix} boxes running finger service able to return information
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:The @file{raddb/sqlserver} file configures the connection to @sc{sql} server.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:connection between @sc{sql} client and the server, @dfn{Authentication
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:@sc{sql} client and the server.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the @sc{sql} interface to use. Currently supported values
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the hostname or @IP{} of the @sc{sql} server.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Sets the @sc{sql} communication port number. It can be omitted if your
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Sets the @sc{sql} user login name.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Sets the @sc{sql} user password.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Set idle timeout in seconds for an open @sc{sql} connection.
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:These parameters configure the @sc{sql} authentication. The general
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:When set to @code{yes}, enables authentication via @sc{sql}. All @code{auth_}
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the @sc{sql} query to be used to obtain user's password from the
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:information from the @sc{sql} database. All the queries refer to
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Suppose your attribute information is stored in a @sc{sql} table of
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:these conditions, he is allowed to use @sc{ppp} service, and is
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:To perform the @sc{sql} accounting @command{radiusd} needs to know the
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:When set to @code{yes} enables @sc{sql} accounting. All @code{acct_}
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:types (@pxref{Accounting Requests}) has a @sc{sql} query associated with
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the @sc{sql} query to be used when @dfn{Session Start Packet}
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the @sc{sql} query to be used when @dfn{Session Stop Packet}
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the @sc{sql} query to be executed upon arrival of a
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the @sc{sql} query to be used upon arrival of an
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:Specifies the @sc{sql} query to be used when a @NAS{} sends
./SAVANNAH-crawl/radius/doc/texinfo/configure.texi:@item @sc{sql} query templates in @file{sqlserver}
./SAVANNAH-crawl/radius/doc/texinfo/operation.texi:@cindex @sc{nas}
./SAVANNAH-crawl/radius/doc/texinfo/operation.texi:original Access-Request with a new request @sc{id} and request
./SAVANNAH-crawl/radius/doc/texinfo/radping.texi:@sc{id} to indicate the user.
./SAVANNAH-crawl/radius/doc/texinfo/radscm.texi:@item @var{id-str} @tab Server @sc{id}
./SAVANNAH-crawl/radius/doc/texinfo/radscm.texi:server @sc{id} and IP.
./SAVANNAH-crawl/radius/doc/texinfo/radscm.texi:Returns the @sc{id} of the currently selected server.
./SAVANNAH-crawl/radius/doc/texinfo/radscm.texi:@item @var{id-str} @tab Server @sc{id}
./SAVANNAH-crawl/radius/doc/texinfo/radscm.texi:@item @var{id-str} @tab Server @sc{id}
./SAVANNAH-crawl/radius/doc/texinfo/radscm.texi:For each server from @code{rad-server-list}, print its @sc{id} and hostname
./SAVANNAH-crawl/radius/doc/texinfo/invoke.texi:Listen the @sc{udp} port PORTNO. The accounting port is computed as @var{PORTNO} + 1.
./SAVANNAH-crawl/radius/doc/es/radwho.texi:El valor del campo @sc{gecos} del archivo local @file{/etc/passwd},
Binary file ./SAVANNAH-crawl/radius/doc/es/radwho.texi matches
./SAVANNAH-crawl/radius/doc/es/attributes.texi:@sc{xor} y se pone en los segundos 16 octetos del atributo @attr{Password}.
./SAVANNAH-crawl/radius/doc/es/attributes.texi:del @sc{xor} y el secreto compartido para formar la suma MD5 con que
Binary file ./SAVANNAH-crawl/radius/doc/es/attributes.texi matches
./SAVANNAH-crawl/rush/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/inetutils/doc/inetutils.texi:@settitle @sc{gnu} Inetutils
./SAVANNAH-crawl/inetutils/doc/inetutils.texi:This manual documents version @value{VERSION} of the @sc{gnu} networking
./SAVANNAH-crawl/inetutils/doc/inetutils.texi:@title @sc{gnu} @code{inetutils}
./SAVANNAH-crawl/inetutils/doc/inetutils.texi:entire @sc{gnu} community will benefit.
./SAVANNAH-crawl/inetutils/doc/inetutils.texi:described here. (In fact, every @sc{gnu} program accepts, or should
./SAVANNAH-crawl/sed/doc/sed.texi:Note: the @sc{posix} standard does not specify what should happen
./SAVANNAH-crawl/sed/doc/sed.texi:a @sc{nul} character. This is a @value{SSED} extension.
./SAVANNAH-crawl/sed/doc/sed.texi:some implementations of @command{sed} (which are not @sc{posix}
./SAVANNAH-crawl/sed/doc/sed.texi:executed contains a @sc{nul} character.
./SAVANNAH-crawl/sed/doc/sed.texi:in the input stream. @sc{posix} mandates that such sequences
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a @sc{bel} character, that is an ``alert'' (@sc{ascii} 7).
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a form feed (@sc{ascii} 12).
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a newline (@sc{ascii} 10).
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a carriage return (@sc{ascii} 13).
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a horizontal tab (@sc{ascii} 9).
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a so called ``vertical tab'' (@sc{ascii} 11).
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches @kbd{@sc{Control}-@var{x}}, where @var{x} is
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a character whose decimal @sc{ascii} value is @var{xxx}.
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a character whose octal @sc{ascii} value is @var{xxx}.
./SAVANNAH-crawl/sed/doc/sed.texi:Produces or matches a character whose hexadecimal @sc{ascii} value is @var{xx}.
./SAVANNAH-crawl/sed/doc/sed.texi:(@samp{0x5e} is the hexadecimal @sc{ascii} value of the character @samp{^}):
./SAVANNAH-crawl/sed/doc/sed.texi:@sc{ascii} values of @samp{[},@samp{]}, respectively):
./SAVANNAH-crawl/sed/doc/sed.texi:Ubben wrote an implementation of the @command{dc} @sc{rpn} calculator!
./SAVANNAH-crawl/sed/doc/sed.texi:The @sc{posix} standard specifies that conforming @command{sed}
./SAVANNAH-crawl/sed/doc/sed.texi:@command{sed} uses the @sc{posix} basic regular expression syntax. According to
./SAVANNAH-crawl/sed/doc/sed.texi:As in all GNU programs that use @sc{posix} basic regular
./SAVANNAH-crawl/sed/doc/sed.texi:sequences. @sc{posix} mandates that such sequences
./SAVANNAH-crawl/tinycc/texi2pod.pl: s/\@sc\{([^\}]*)\}/\U$1/g;
./SAVANNAH-crawl/bbdb/doc/doclicense.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/pretest/doc/pretest.texi:convert the image from @sc{RAW} format to @sc{qcow2} format.
./SAVANNAH-crawl/pretest/doc/pretest.texi:run script (@file{pretest-run.sh}) use @sc{IDE} for disk emulation,
./SAVANNAH-crawl/pretest/doc/pretest.texi:and @sc{rtl8139} for network emulation.
./SAVANNAH-crawl/vrtater/doc/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/groff/doc/groff.texi:Postprocessors for character devices, @sc{PostScript}, @TeX{}'s
./SAVANNAH-crawl/groff/doc/groff.texi:@code{groff} has postprocessors for @sc{PostScript} devices, character
./SAVANNAH-crawl/groff/doc/groff.texi:For @sc{PostScript} printers and previewers.
./SAVANNAH-crawl/groff/doc/groff.texi:distributed with a @sc{PostScript} font called @file{freeeuro.pfa},
./SAVANNAH-crawl/groff/doc/groff.texi:If you process this with the @sc{PostScript} device (@code{-Tps}),
./SAVANNAH-crawl/groff/doc/groff.texi:@sc{PostScript}, etc.)@: which interprets this intermediate output
./SAVANNAH-crawl/groff/doc/groff.texi:rather than fonts. For example, the default setting for @sc{PostScript}
./SAVANNAH-crawl/groff/doc/groff.texi:In the following example, we want to access the @sc{PostScript} font
./SAVANNAH-crawl/groff/doc/groff.texi:The default font position at start-up is@tie{}1; for the @sc{PostScript}
./SAVANNAH-crawl/groff/doc/groff.texi:ordered list of @dfn{special fonts}. By default, the @sc{PostScript}
./SAVANNAH-crawl/groff/doc/groff.texi:@code{u00CA_0301} is not a valid glyph name since U+00CA (@sc{latin
./SAVANNAH-crawl/groff/doc/groff.texi:(@sc{latin capital letter e}) and U+0302 (@sc{combining circumflex
./SAVANNAH-crawl/groff/doc/groff.texi:@sc{latin capital letter e with circumflex and acute}.
./SAVANNAH-crawl/groff/doc/groff.texi:names that are composites itself. For example, @code{u0100} (@sc{latin
./SAVANNAH-crawl/groff/doc/groff.texi:Most @sc{PostScript} fonts support the fi and fl ligatures. The C/A/T
./SAVANNAH-crawl/groff/doc/groff.texi:to its type size! For example, the standard @sc{PostScript} font
./SAVANNAH-crawl/groff/doc/groff.texi:@sc{PostScript} into the final document.
./SAVANNAH-crawl/groff/doc/groff.texi:Retrieve the bounding box of the @sc{PostScript} image found in
./SAVANNAH-crawl/groff/doc/groff.texi:@command{troff} into a form suitable for Adobe @sc{PostScript}
./SAVANNAH-crawl/groff/doc/groff.texi:@subsection Embedding @sc{PostScript}
./SAVANNAH-crawl/groff/doc/groff.texi:@sc{PostScript} drawing from file @var{file} bound by the box from
./SAVANNAH-crawl/groff/doc/groff.texi:@var{llx} @var{lly} to @var{urx} @var{ury} (in @sc{PostScript}
./SAVANNAH-crawl/groff/doc/groff.texi:The @sc{PostScript} device is used to create all the image files (for
./SAVANNAH-crawl/groff/doc/groff.texi:@sc{PostScript} file.
./SAVANNAH-crawl/groff/doc/groff.texi:@sc{PostScript} device is called @code{post} and has a resolution of
./SAVANNAH-crawl/groff/doc/groff.texi:PNG images from @sc{PostScript} input. Under GNU/Linux this is
./SAVANNAH-crawl/direvent/doc/direvent.texi:compatibility with the @sc{c} preprocessor.
./SAVANNAH-crawl/direvent/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/guile-rpc/modules/silex/silex.texi:standards do not impose a particular character set, such as @sc{ascii}.
./SAVANNAH-crawl/guile-rpc/modules/silex/silex.texi:@appendix Interfacing with an @sc{lalr}(1) parser
./SAVANNAH-crawl/guile-rpc/modules/silex/silex.texi:@cindex @sc{lalr}(1) parser generator
./SAVANNAH-crawl/guile-rpc/modules/silex/silex.texi: A nice @sc{lalr}(1) parser generator for Scheme has been written
./SAVANNAH-crawl/guile-rpc/modules/silex/silex.texi: The @sc{lalr}(1) parsers expect that the tokens are pairs with a
./SAVANNAH-crawl/guile-rpc/modules/silex/silex.texi:number in the @sc{car}, the token number, and any value in the @sc{cdr},
./SAVANNAH-crawl/guile-rpc/modules/silex/silex.texi:Furthermore, the file created by the @sc{lalr}(1) parser generator
./SAVANNAH-crawl/guile-rpc/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/skribilo/src/guile/silex/silex.texi:standards do not impose a particular character set, such as @sc{ascii}.
./SAVANNAH-crawl/skribilo/src/guile/silex/silex.texi:@appendix Interfacing with an @sc{lalr}(1) parser
./SAVANNAH-crawl/skribilo/src/guile/silex/silex.texi:@cindex @sc{lalr}(1) parser generator
./SAVANNAH-crawl/skribilo/src/guile/silex/silex.texi: A nice @sc{lalr}(1) parser generator for Scheme has been written
./SAVANNAH-crawl/skribilo/src/guile/silex/silex.texi: The @sc{lalr}(1) parsers expect that the tokens are pairs with a
./SAVANNAH-crawl/skribilo/src/guile/silex/silex.texi:number in the @sc{car}, the token number, and any value in the @sc{cdr},
./SAVANNAH-crawl/skribilo/src/guile/silex/silex.texi:Furthermore, the file created by the @sc{lalr}(1) parser generator
./SAVANNAH-crawl/libchop/doc/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/pem/gfdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:@sc{jwhois} is an Internet Whois client that contains an extensible
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:Upon execution, @sc{jwhois} searches through its configuration
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:reply from that whois server, @sc{jwhois} can assume the query was
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:@sc{jwhois} uses the following command-line options:
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:@sc{jwhois} is configurable via its configuration file, normally
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:If no configuration file can be found, @sc{jwhois} will default all queries
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:The global options of @sc{jwhois} configure some basic facilities
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:@sc{jwhois} would look for an address @url{se.whois-servers.net}
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:These options control the HTTP support on @sc{jwhois}.
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:program such as @sc{lynx} or @sc{curl}.
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:options to the standard output. @sc{jwhois} catches
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:the browser. If set to @sc{true}, @sc{lynx}-style processing
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:If set to @sc{false}, @sc{w3m}-style processing is enabled,
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:When making a query, @sc{jwhois} looks at the @option{whois-servers}
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:rwhois protocol, this option makes @sc{jwhois} send all
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:are therefore not directly incorporated into the @sc{jwhois} client.
./SAVANNAH-crawl/jwhois/doc/jwhois.texi:It is possible to use these options together with @sc{jwhois} by changing
./SAVANNAH-crawl/readline/doc/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library
./SAVANNAH-crawl/readline/doc/hsuser.texi:For information on using the @sc{gnu} History Library in other programs,
./SAVANNAH-crawl/readline/doc/hsuser.texi:see the @sc{gnu} Readline Library Manual.
./SAVANNAH-crawl/readline/doc/hsuser.texi:This chapter describes how to use the @sc{gnu} History Library interactively,
./SAVANNAH-crawl/readline/doc/hsuser.texi:information on using the @sc{gnu} History Library in your own programs,
./SAVANNAH-crawl/readline/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/readline/doc/rluser.texi:This chapter describes the basic features of the @sc{gnu}
./SAVANNAH-crawl/readline/doc/rluser.texi:eighth bit set to an @sc{ascii} key sequence by stripping the eighth
./SAVANNAH-crawl/readline/doc/rluser.texi:the key sequence in double quotes. Some @sc{gnu} Emacs style key
./SAVANNAH-crawl/readline/doc/rluser.texi:The following @sc{gnu} Emacs style escape sequences are available when
./SAVANNAH-crawl/readline/doc/rluser.texi:In addition to the @sc{gnu} Emacs style escape sequences, a second
./SAVANNAH-crawl/readline/doc/rluser.texi:interprets it as the end of input and returns @sc{eof}.
./SAVANNAH-crawl/readline/doc/rluser.texi:same character as the tty @sc{eof} character, as @kbd{C-d}
./SAVANNAH-crawl/readline/doc/rluser.texi:the @sc{posix} standard.
./SAVANNAH-crawl/readline/doc/rltech.texi:This chapter describes the interface between the @sc{gnu} Readline Library and
./SAVANNAH-crawl/readline/doc/rltech.texi:features found in @sc{gnu} Readline
./SAVANNAH-crawl/readline/doc/rltech.texi:Always set to 1, denoting that this is @sc{gnu} readline rather than some
./SAVANNAH-crawl/readline/doc/hstech.texi:with the @sc{gnu} History Library.
./SAVANNAH-crawl/readline/doc/hstech.texi:For information on the interactive use of @sc{gnu} History, @pxref{Using
./SAVANNAH-crawl/readline/doc/hstech.texi:Many programs read input from the user a line at a time. The @sc{gnu}
./SAVANNAH-crawl/readline/doc/hstech.texi:exported by the @sc{gnu} History library.
./SAVANNAH-crawl/readline/doc/hstech.texi:the @sc{gnu} History Library.
./SAVANNAH-crawl/readline/doc/hstech.texi:The following program demonstrates simple use of the @sc{gnu} History Library.
./SAVANNAH-crawl/gnumach/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gnumach/doc/mach.texi:@sc{carnegie mellon allows free use of this software in its ``as is''
./SAVANNAH-crawl/w3/texi/w3.txi:All of the widely used (and even some not very widely used) @sc{url}
./SAVANNAH-crawl/w3/texi/w3.txi:* Supported URLs:: What @sc{url} schemes are supported.
./SAVANNAH-crawl/w3/texi/w3.txi:* MIME Support:: Support for @sc{mime}
./SAVANNAH-crawl/w3/texi/w3.txi:* Installing SSL:: Turning on @sc{ssl} support.
./SAVANNAH-crawl/w3/texi/w3.txi:@item fetch a @sc{url}
./SAVANNAH-crawl/w3/texi/w3.txi:type the @sc{url}, and then press the @kbd{RETURN} key,
./SAVANNAH-crawl/w3/texi/w3.txi:and also dvi files. @sc{html} and postscript can be generated by @samp{make
./SAVANNAH-crawl/w3/texi/w3.txi:Emacs's bookmarks) are a list of @sc{url}s. Emacs/W3 supports mosaic's
./SAVANNAH-crawl/w3/texi/w3.txi:hotlist format which associates an alias with each @sc{url} ---
./SAVANNAH-crawl/w3/texi/w3.txi:@c --- and also the @sc{html} style hotlists used by
./SAVANNAH-crawl/w3/texi/w3.txi:This shows the @sc{url} of the current document in the minibuffer
./SAVANNAH-crawl/w3/texi/w3.txi:This shows the @sc{url} of the hypertext link under point in the
./SAVANNAH-crawl/w3/texi/w3.txi:(@code{w3-document-information}). This includes the @sc{url}, the last
./SAVANNAH-crawl/w3/texi/w3.txi:modified date, @sc{mime} headers, the @sc{http} response code, and any
./SAVANNAH-crawl/w3/texi/w3.txi:Shows information about the @sc{url} at point (@code{w3-popup-info}).
./SAVANNAH-crawl/w3/texi/w3.txi:This shows the @sc{html} source of the current document in a separate
./SAVANNAH-crawl/w3/texi/w3.txi:document's @sc{url}.
./SAVANNAH-crawl/w3/texi/w3.txi:Shows the @sc{html} source of the hypertext link under point in a
./SAVANNAH-crawl/w3/texi/w3.txi:is based on the document's @sc{url}.
./SAVANNAH-crawl/w3/texi/w3.txi:This stores the current document's @sc{url} in the kill ring, and also in the
./SAVANNAH-crawl/w3/texi/w3.txi:Stores the @sc{url} of the document under point in the kill ring, and also in
./SAVANNAH-crawl/w3/texi/w3.txi:Download the @sc{url} at point (@code{w3-download-url-at-point}).
./SAVANNAH-crawl/w3/texi/w3.txi:Download the current @sc{url} (@code{w3-download-this-url}).
./SAVANNAH-crawl/w3/texi/w3.txi:Prompts for a @sc{url} in the minibuffer, and attempts to fetch it
./SAVANNAH-crawl/w3/texi/w3.txi:print: formatted text, @sc{html} source, PostScript (with ps-print), or by using
./SAVANNAH-crawl/w3/texi/w3.txi:Prints out the @sc{url} under point in a variety of formats
./SAVANNAH-crawl/w3/texi/w3.txi:return to the last @sc{www} page visited --- it is the same as using
./SAVANNAH-crawl/w3/texi/w3.txi:Choose from several different formats to mail: formatted text, @sc{html}
./SAVANNAH-crawl/w3/texi/w3.txi:source, PostScript, or LaTeX source. When the @sc{html} source is
./SAVANNAH-crawl/w3/texi/w3.txi:different formats to mail: formatted text, @sc{html} source, PostScript,
./SAVANNAH-crawl/w3/texi/w3.txi:or LaTeX source. When the @sc{html} source is mailed, then an
./SAVANNAH-crawl/w3/texi/w3.txi:Insert a fully formatted @sc{html} link into another buffer
./SAVANNAH-crawl/w3/texi/w3.txi:(@code{w3-insert-formatted-url}). This gets the name and @sc{url} of
./SAVANNAH-crawl/w3/texi/w3.txi:Inserts the @sc{url} of the current document into another buffer
./SAVANNAH-crawl/w3/texi/w3.txi:With prefix arg, uses the @sc{url} of the link under point.
./SAVANNAH-crawl/w3/texi/w3.txi:Goto a user specified @sc{url} or file
./SAVANNAH-crawl/w3/texi/w3.txi:Send an @sc{http} @sc{head} request for the current doc or link (ignored)
./SAVANNAH-crawl/w3/texi/w3.txi:Goto a user specified @sc{url} or file
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{http} allows servers to ask browsers what browser they are, and what
./SAVANNAH-crawl/w3/texi/w3.txi:functions to masquerade as lynx, netscape, @sc{ie} or arena. For each
./SAVANNAH-crawl/w3/texi/w3.txi:Emacs/W3 supports two types of hotlist, mosaic hotlists and @sc{html} as
./SAVANNAH-crawl/w3/texi/w3.txi:Unfortunately, not all hotlist operations are supported for @sc{html}
./SAVANNAH-crawl/w3/texi/w3.txi:a file that contains @sc{url}s and aliases. Hotlists allow quick access to any
./SAVANNAH-crawl/w3/texi/w3.txi:Converts the hotlist into @sc{html} and displays it.
./SAVANNAH-crawl/w3/texi/w3.txi:Almost all web browsers keep track of the @sc{url}s followed from a page, so
./SAVANNAH-crawl/w3/texi/w3.txi:of @sc{url}s that can be traversed easily.
./SAVANNAH-crawl/w3/texi/w3.txi:of all the @sc{url}s visited in an Emacs session. If @code{t} then
./SAVANNAH-crawl/w3/texi/w3.txi:of all the @sc{url}s visited in the session.
./SAVANNAH-crawl/w3/texi/w3.txi:generates an @sc{html} document showing every @sc{url} visited since
./SAVANNAH-crawl/w3/texi/w3.txi:Emacs/W3 buffers remember what @sc{url}, buffer, and buffer position of the
./SAVANNAH-crawl/w3/texi/w3.txi:Most web browsers also support the idea of a ``history'' of @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:normal @sc{url}s. Emacs/W3 will read and write history files generated
./SAVANNAH-crawl/w3/texi/w3.txi:a list of all the @sc{url}s visited in a session. The file is
./SAVANNAH-crawl/w3/texi/w3.txi:for MS operating systems, @file{~/mosaic.global-history} for @sc{vms} and
./SAVANNAH-crawl/w3/texi/w3.txi:If any @sc{url} in the list is found in the file, it is not saved, but new
./SAVANNAH-crawl/w3/texi/w3.txi:partial @sc{url}. This is very useful, especially for very long @sc{url}s that
./SAVANNAH-crawl/w3/texi/w3.txi:Display the @sc{url} of the target.
./SAVANNAH-crawl/w3/texi/w3.txi:Many @sc{html} pages use horizontal lines (rules) to seperate sections
./SAVANNAH-crawl/w3/texi/w3.txi:@code{w3-image-mappings} controls the mapping of @sc{mime} types to
./SAVANNAH-crawl/w3/texi/w3.txi:a @sc{mime} type string and an image-type symbol.
./SAVANNAH-crawl/w3/texi/w3.txi:document specify a @sc{css} stylesheet.
./SAVANNAH-crawl/w3/texi/w3.txi:If this is non-@code{nil} then document retrievals over @sc{http} will
./SAVANNAH-crawl/w3/texi/w3.txi:supports the @sc{W3C} recommendation for Cascading Style Sheets, Level 1
./SAVANNAH-crawl/w3/texi/w3.txi:(commonly known as @sc{CSS1}) with a few experimental items from other
./SAVANNAH-crawl/w3/texi/w3.txi:Support for @sc{dsssl} is progressing, but spare time is at an all-time
./SAVANNAH-crawl/w3/texi/w3.txi:The following sections closely parallel the @sc{css1} specification so
./SAVANNAH-crawl/w3/texi/w3.txi:through the @sc{css1} specification. Please note that a lot of the text
./SAVANNAH-crawl/w3/texi/w3.txi:An element which has a line break before and after (e.g.@: 'H1' in @sc{html}).
./SAVANNAH-crawl/w3/texi/w3.txi:A subelement in @sc{sgml} terminology.
./SAVANNAH-crawl/w3/texi/w3.txi:@item @sc{css}
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{html} document.
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{html} element.
./SAVANNAH-crawl/w3/texi/w3.txi:A generic identifier in @sc{sgml} terminology.
./SAVANNAH-crawl/w3/texi/w3.txi:@item @sc{html} extension
./SAVANNAH-crawl/w3/texi/w3.txi:effects. The @sc{font}, @sc{center} and @sc{blink} elements are examples
./SAVANNAH-crawl/w3/texi/w3.txi:of HTML extensions, as is the @sc{bgcolor} attribute. One of the goals
./SAVANNAH-crawl/w3/texi/w3.txi:of @sc{css} is to provide an alternative to @sc{html} extensions.
./SAVANNAH-crawl/w3/texi/w3.txi:(e.g. '@sc{strong}' in @sc{html})
./SAVANNAH-crawl/w3/texi/w3.txi:The containing element in @sc{sgml} terminology.
./SAVANNAH-crawl/w3/texi/w3.txi:Pseudo-elements are used in @sc{css} selectors to address typographical
./SAVANNAH-crawl/w3/texi/w3.txi:Pseudo-classes are used in @sc{css} selectors to allow information
./SAVANNAH-crawl/w3/texi/w3.txi:external to the @sc{html} source (e.g. the fact that an anchor has been
./SAVANNAH-crawl/w3/texi/w3.txi:A stylistic parameter that can be influenced through @sc{css}.
./SAVANNAH-crawl/w3/texi/w3.txi:An element that the @sc{css} formatter only knows the intrinsic
./SAVANNAH-crawl/w3/texi/w3.txi:dimensions of. In @sc{html}, @sc{img}, @sc{input}, @sc{textarea},
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{select} and @sc{object} elements can be examples of replaced
./SAVANNAH-crawl/w3/texi/w3.txi:elements. E.g., the content of the @sc{img} element is often replaced by
./SAVANNAH-crawl/w3/texi/w3.txi:the image that the @sc{src} attribute points to. @sc{css1} does not
./SAVANNAH-crawl/w3/texi/w3.txi:(e.g. @sc{'H1'}).
./SAVANNAH-crawl/w3/texi/w3.txi:contextual selector (e.g. @sc{'h1 b'}) which consists of several simple
./SAVANNAH-crawl/w3/texi/w3.txi:@item @sc{sgml}
./SAVANNAH-crawl/w3/texi/w3.txi:Standard Generalized Markup Language, of which @sc{html} is an
./SAVANNAH-crawl/w3/texi/w3.txi:@item @sc{ua}
./SAVANNAH-crawl/w3/texi/w3.txi:In @sc{css1}, style is normally attached to an element based on its
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{css1} to allow external information to influence the formatting
./SAVANNAH-crawl/w3/texi/w3.txi:Pseudo-classes and pseudo-elements can be used in @sc{css} selectors,
./SAVANNAH-crawl/w3/texi/w3.txi:but do not exist in the @sc{html} source. Rather, they are "inserted" by
./SAVANNAH-crawl/w3/texi/w3.txi:the @sc{ua} under certain conditions to be used for addressing in style
./SAVANNAH-crawl/w3/texi/w3.txi:older ones. In @sc{css1}, this is handled through pseudo-classes on the
./SAVANNAH-crawl/w3/texi/w3.txi:inserted manually. A @sc{ua} is not required to reformat a currently
./SAVANNAH-crawl/w3/texi/w3.txi:In @sc{css1}, anchor pseudo-classes have no effect on elements other
./SAVANNAH-crawl/w3/texi/w3.txi:In @sc{css}, more than one style sheet can influence the presentation
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{ua} is free to choose the mechanism for referencing personal style
./SAVANNAH-crawl/w3/texi/w3.txi:and author rules override the @sc{ua}'s default values.
./SAVANNAH-crawl/w3/texi/w3.txi:In @sc{css1}, all '@@import' statements must occur at the start of a
./SAVANNAH-crawl/w3/texi/w3.txi:NOTE: The use of !important in @sc{css} stylesheets is unsupported at
./SAVANNAH-crawl/w3/texi/w3.txi:The @sc{ua} may choose to honor other stylistic @sc{html} attributes,
./SAVANNAH-crawl/w3/texi/w3.txi:corresponding @sc{css} rules with specificity equal to 1. The rules are
./SAVANNAH-crawl/w3/texi/w3.txi:extension to be able to fully specify the behaviour of @sc{br} and
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{hr} elements within a stylesheet.
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{html} documents, frequently on a bitmapped display. This is not the
./SAVANNAH-crawl/w3/texi/w3.txi:@dfn{Uniform Resource Locators} (@sc{url}s) are a specific form of
./SAVANNAH-crawl/w3/texi/w3.txi:@dfn{Uniform Resource Identifiers} (@sc{uri}) described in @sc{rfc}2396
./SAVANNAH-crawl/w3/texi/w3.txi:which updates @sc{rfc}1738 and @sc{rfc}1808.
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{rfc2016} defines uniform resource agents.
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{uri} have the form @var{scheme}:@var{scheme-specific-part}, where @var{scheme}
./SAVANNAH-crawl/w3/texi/w3.txi:appears in the menu below for @sc{url}s supported by Emacs/W3.
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{ftp, nfs, http, https}, @code{rlogin}, @code{telnet}, tn3270,
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{irc} and gopher @sc{url}s all have the form
./SAVANNAH-crawl/w3/texi/w3.txi:is listening on that port (eg. a gopher @sc{url} specifying the
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{smtp} port can cause mail to be sent), but @xref{Other Variables,
./SAVANNAH-crawl/w3/texi/w3.txi:* http/https:: @sc{http/1.0} support.
./SAVANNAH-crawl/w3/texi/w3.txi:@section File @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex File @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{url} points to a directory, then it will try to retrieve a file
./SAVANNAH-crawl/w3/texi/w3.txi:mode. If the @sc{url} refers to a file on a remote host, then Emacs/W3
./SAVANNAH-crawl/w3/texi/w3.txi:@section @sc{ftp} @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{ftp}
./SAVANNAH-crawl/w3/texi/w3.txi:For details of usage see @ref{file}. In Emacs/W3 file and @sc{ftp} @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:than by @sc{ftp}. Emacs/W3 relies on @samp{ange-ftp}
./SAVANNAH-crawl/w3/texi/w3.txi:@section @sc{nfs} @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{nfs}
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{nfs} @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:Since @sc{nfs} is fairly transparent to the user (at least when it's
./SAVANNAH-crawl/w3/texi/w3.txi:working), there isn't very much to say here. An nfs @sc{url} is similar
./SAVANNAH-crawl/w3/texi/w3.txi:to a file @sc{url} except that it points to a file on a remote host that
./SAVANNAH-crawl/w3/texi/w3.txi:depending on local configuration. The @sc{nfs} @sc{url} is defined in
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{rfc2224}.
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex info @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:Info @sc{url}s are not an officially recognised @sc{url} (gdj1: is this
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{http}
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{https}
./SAVANNAH-crawl/w3/texi/w3.txi:from the World Wide Web. Emacs/W3 supports @sc{http} version 1.0 as
./SAVANNAH-crawl/w3/texi/w3.txi:defined in @sc{rfc}1945 --- now superseded by version 1.1 defined in
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{rfc}2068.
./SAVANNAH-crawl/w3/texi/w3.txi:whether @sc{http} is used to discover file attributes, or whether
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{https} is a secure version of @sc{http} defined in @sc{rfc}2069
./SAVANNAH-crawl/w3/texi/w3.txi:(gdj1: ?). Emacs/W3 requires @sc{ssl} to handle this, @xref{Installing SSL}.
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex mailto @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:A mailto @sc{url} will send an email message to the address in the
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{url}, for example @samp{mailto:foo@@bar.com} would compose a
./SAVANNAH-crawl/w3/texi/w3.txi:header field containing the @sc{url} of the document that contained the
./SAVANNAH-crawl/w3/texi/w3.txi:mailto @sc{url} is added, as is an X-Mailer header field containing the
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{rfc}2368 extends the definition of mailto @sc{url}s in @sc{rfc1738}.
./SAVANNAH-crawl/w3/texi/w3.txi:The form of a mailto @sc{url} is
./SAVANNAH-crawl/w3/texi/w3.txi:Email messages are defined in @sc{rfc}822.
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex mailserver @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:A mailserver @sc{url} allows you to send an email to a person, but this
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{url} optionally specifies a subject and a body. The basic format is
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex news @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:If the @sc{url} doesn't specify a host, then the host in
./SAVANNAH-crawl/w3/texi/w3.txi:@code{url-news-server} will be used, and unless the @sc{url} has a port
./SAVANNAH-crawl/w3/texi/w3.txi:The username and password specified in the @sc{url} will be used if
./SAVANNAH-crawl/w3/texi/w3.txi:present. The @sc{url} may contain a message-id, in which case that
./SAVANNAH-crawl/w3/texi/w3.txi:mode, otherwise they are turned into @sc{html} and rendered by Emacs/W3.
./SAVANNAH-crawl/w3/texi/w3.txi:An @sc{nntp url} is the same as a news @sc{url}, except that the
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{url} may specify an article by its number.
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex rlogin @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex telnet @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex tn3270 @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:To handle rlogin, telnet and tn3270 @sc{url}s, Emacs/W3 runs an
./SAVANNAH-crawl/w3/texi/w3.txi:Well-known ports are used if the @sc{url} does not specify a port.
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{irc}
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{irc url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@dfn{Internet Relay Chat} (@sc{irc}) is handled by handing off the @sc{irc}
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex data @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:Data @sc{url}s contain @sc{mime} data in the @sc{url} itself, by default
./SAVANNAH-crawl/w3/texi/w3.txi:the data is 8bit encoded @samp{text/plain}, but the @sc{url} can specify either
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{url}'s data as @sc{mime} and display it appropriately. @xref{MIME Support}.
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex gopher @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{mime} types. If @code{url-use-hypertext-gopher} is non-@code{nil},
./SAVANNAH-crawl/w3/texi/w3.txi:then gopher pages will be turned into @sc{html} for Emacs/W3 to parse
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex finger @sc{url}s
./SAVANNAH-crawl/w3/texi/w3.txi:Finger @sc{url}s will finger a given user at a given host, or @samp{localhost}
./SAVANNAH-crawl/w3/texi/w3.txi:if no host is specified, processing the results to create an @sc{html}
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{mime} is an emerging standard for multimedia mail. It offers a very
./SAVANNAH-crawl/w3/texi/w3.txi:@samp{text/html} specifies an @sc{html} document, whereas
./SAVANNAH-crawl/w3/texi/w3.txi:This typing allows much more flexibility in naming files. @sc{http}/1.0
./SAVANNAH-crawl/w3/texi/w3.txi:and not have the client second-guess it based on file extensions. @sc{html}
./SAVANNAH-crawl/w3/texi/w3.txi:only be needed when accessing files via @sc{ftp}, local file access, or old
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{http}/0.9 servers.
./SAVANNAH-crawl/w3/texi/w3.txi:Both Mosaic and the NCSA @sc{http} daemon rely on a separate file for mapping
./SAVANNAH-crawl/w3/texi/w3.txi:Each line contains information for one @sc{http} type. These types resemble
./SAVANNAH-crawl/w3/texi/w3.txi:Not all files look as they should when parsed as an @sc{html} document
./SAVANNAH-crawl/w3/texi/w3.txi:an assoc list of information about the viewer. Please see the @sc{url}
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{http} transfers over an SSL encrypted channel, if the appropriate
./SAVANNAH-crawl/w3/texi/w3.txi:been. @sc{http} is quite happy to tell everyone it meets who you are
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{http} is a stateless protocol which means that the server sees every
./SAVANNAH-crawl/w3/texi/w3.txi:servers which do understand it.} are used to add state to @sc{http}
./SAVANNAH-crawl/w3/texi/w3.txi:sessions. Cookies are defined in @sc{rfc2109}.
./SAVANNAH-crawl/w3/texi/w3.txi:that match @sc{url}s from which cookies should be accepted and rejected
./SAVANNAH-crawl/w3/texi/w3.txi:respectively. If a @sc{url} matches patterns in both of these, then
./SAVANNAH-crawl/w3/texi/w3.txi:will still reject cookies from @sc{url}s matched in
./SAVANNAH-crawl/w3/texi/w3.txi:* Printing:: Emacs/W3 can print @sc{html} by various methods.
./SAVANNAH-crawl/w3/texi/w3.txi: @sc{html}/@sc{html}+ constructs.
./SAVANNAH-crawl/w3/texi/w3.txi:a function that takes a @sc{url} as an argument and returns the absolute
./SAVANNAH-crawl/w3/texi/w3.txi:pathname of the cache-file corresponding to that @sc{url}. You may
./SAVANNAH-crawl/w3/texi/w3.txi:filename more obviously connected to the @sc{url}, but it is more likely
./SAVANNAH-crawl/w3/texi/w3.txi:If you want to print an @sc{html} document, then Emacs/W3 needs to
./SAVANNAH-crawl/w3/texi/w3.txi:@item @sc{html} source
./SAVANNAH-crawl/w3/texi/w3.txi:This will simply print the raw @sc{html} source code using
./SAVANNAH-crawl/w3/texi/w3.txi:Emacs/W3 can generate a LaTeX equivalent of the @sc{html} document.
./SAVANNAH-crawl/w3/texi/w3.txi:The document style to use when printing or mailing converted @sc{html} files
./SAVANNAH-crawl/w3/texi/w3.txi:If non-@code{nil}, prints the @sc{url}s of hypertext links as endnotes at the
./SAVANNAH-crawl/w3/texi/w3.txi:end of the document. If set to @code{footnote}, prints the @sc{url}'s as
./SAVANNAH-crawl/w3/texi/w3.txi:More and more people are including @sc{url}s in their signatures, and within
./SAVANNAH-crawl/w3/texi/w3.txi:(5.x), @sc{url}s are automatically highlighted, and can be followed with the
./SAVANNAH-crawl/w3/texi/w3.txi:mouse or the return key. How the @sc{url}s are viewed is determined by the
./SAVANNAH-crawl/w3/texi/w3.txi:To access @sc{url}s from within RMAIL, the following hook should do the
./SAVANNAH-crawl/w3/texi/w3.txi:people writing valid @sc{html}, set the variable @code{w3-debug-html} to
./SAVANNAH-crawl/w3/texi/w3.txi:font-lock highlighting in the @sc{html} error buffer, use
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{html} errors for a page, it runs @code{w3-display-errors-hook}.
./SAVANNAH-crawl/w3/texi/w3.txi:If a Emacs/W3 thinks it has encountered invalid @sc{html}, then a debugging
./SAVANNAH-crawl/w3/texi/w3.txi:These hooks are run the first time a @sc{url} is fetched. All the
./SAVANNAH-crawl/w3/texi/w3.txi:the mail, @sc{nntp} and chargen ports so a malicious @sc{html} author
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{http}/1.0 requests.
./SAVANNAH-crawl/w3/texi/w3.txi:run to retrieve @sc{url}s. It is @file{www} by default.
./SAVANNAH-crawl/w3/texi/w3.txi:Not everyone uses proper @sc{html} comments. To allow for the presence
./SAVANNAH-crawl/w3/texi/w3.txi:This controls whether to parse @sc{mime} headers in a message. If it is
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{http/1.0} requests. If it is @code{nil} then the field isn't added
./SAVANNAH-crawl/w3/texi/w3.txi:is sent in the @sc{from} field in an @sc{http/1.0} request, but
./SAVANNAH-crawl/w3/texi/w3.txi:will display the @sc{url} under the mouse in the echo-area.
./SAVANNAH-crawl/w3/texi/w3.txi:By default, Emacs can support standard @sc{tcp}/@sc{ip} network
./SAVANNAH-crawl/w3/texi/w3.txi:connections on almost all the platforms it runs on (Unix, @sc{vms},
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{mis} department.)
./SAVANNAH-crawl/w3/texi/w3.txi:@cindex @sc{term}
./SAVANNAH-crawl/w3/texi/w3.txi:@item Using @sc{term} (or @sc{term}-like) Networking Software
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{term} @footnote{@sc{term} is a user-level protocol for emulating
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{ip} over a serial line. More information is available at
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{note}: XEmacs and Emacs 19.22 or later have patches to enable native
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{term} networking. To enable it, @code{#define TERM} in the
./SAVANNAH-crawl/w3/texi/w3.txi:comes with the latest versions of @sc{term}.
./SAVANNAH-crawl/w3/texi/w3.txi:If you run into any problems with the native @sc{term} networking
./SAVANNAH-crawl/w3/texi/w3.txi:@item @sc{socks}
./SAVANNAH-crawl/w3/texi/w3.txi:Use if the firewall has a @sc{socks} gateway running on it. @sc{socks}
./SAVANNAH-crawl/w3/texi/w3.txi:v5 protocol is defined in @sc{rfc1928}.
./SAVANNAH-crawl/w3/texi/w3.txi:it will be used as the password for authenticating you to the @sc{socks}
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{socks} server. By default this is your login name
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{socks} server; it is 5 by default.
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{ip} addresses which specify a range of @sc{ip} addresses, an @sc{ip}
./SAVANNAH-crawl/w3/texi/w3.txi:address and a netmask, a domain name or a unique hostname or @sc{ip}
./SAVANNAH-crawl/w3/texi/w3.txi:protocol requests to. Each protocol (@sc{http}, @sc{wais}, gopher,
./SAVANNAH-crawl/w3/texi/w3.txi:@sc{ftp}, etc.) can have a different gateway server. The environment
./SAVANNAH-crawl/w3/texi/w3.txi:supported network protocols (gopher, file, @sc{http}, @sc{ftp}, etc.)
./SAVANNAH-crawl/w3/texi/w3.txi:on the protocol type (@sc{http}, gopher, etc) in all lowercase. The
./SAVANNAH-crawl/w3/texi/w3.txi:@code{cdr} of each entry should be the @sc{address} of the proxy server
./SAVANNAH-crawl/w3/texi/w3.txi:@code{ssl-certificate-directory} is the directory in which @sc{ca}
./SAVANNAH-crawl/w3/texi/w3.txi:@c @sc{html} font families. The format is @code{(@var{html_family}
./SAVANNAH-crawl/rtliber/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/fc2d/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SAVANNAH-crawl/a2ps/doc/regex.texi:regular expressions. One group---the @sc{gnu} group---is more powerful
./SAVANNAH-crawl/a2ps/doc/regex.texi:but not completely compatible with the other two, namely the @sc{posix}
./SAVANNAH-crawl/a2ps/doc/regex.texi:and Berkeley @sc{unix} groups; its interface was designed specifically
./SAVANNAH-crawl/a2ps/doc/regex.texi:for @sc{gnu}. The other groups have the same interfaces as do the
./SAVANNAH-crawl/a2ps/doc/regex.texi:regular expression functions in @sc{posix} and Berkeley
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{unix}.
./SAVANNAH-crawl/a2ps/doc/regex.texi:programs---@sc{gnu} Emacs,
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{posix} Awk,
./SAVANNAH-crawl/a2ps/doc/regex.texi:Egrep---in addition to syntaxes for @sc{posix} basic and extended
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{posix} generalizes the notion of a character to that of a
./SAVANNAH-crawl/a2ps/doc/regex.texi:Since @sc{posix}'s ``collating element'' preserves the essential idea of
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{posix}; @sc{gnu} also uses these. Most operators have more than one
./SAVANNAH-crawl/a2ps/doc/regex.texi:representations, while @sc{posix} dictates others.
./SAVANNAH-crawl/a2ps/doc/regex.texi:system-dependent; for @sc{gnu}, a space or tab
./SAVANNAH-crawl/a2ps/doc/regex.texi:control characters (in the @sc{ascii} encoding, code 0177 and codes
./SAVANNAH-crawl/a2ps/doc/regex.texi:printable characters (in the @sc{ascii} encoding, space
./SAVANNAH-crawl/a2ps/doc/regex.texi:another @samp{-}. For example, in the @sc{ascii} encoding, @samp{)},
./SAVANNAH-crawl/a2ps/doc/regex.texi:English, in @sc{ascii}).
./SAVANNAH-crawl/a2ps/doc/regex.texi:Following are operators that @sc{gnu} defines (and @sc{posix} doesn't).
./SAVANNAH-crawl/a2ps/doc/regex.texi:character set. In the @sc{ascii} encoding, therefore, a syntax table
./SAVANNAH-crawl/a2ps/doc/regex.texi:Following are operators that @sc{gnu} defines (and @sc{posix} doesn't)
./SAVANNAH-crawl/a2ps/doc/regex.texi:character set. In the @sc{ascii} encoding, therefore, a syntax table
./SAVANNAH-crawl/a2ps/doc/regex.texi:C programs. Regex has three interfaces: one designed for @sc{gnu}, one
./SAVANNAH-crawl/a2ps/doc/regex.texi:compatible with @sc{posix} and one compatible with Berkeley @sc{unix}.
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{posix} or Berkeley @sc{unix}, you can use these functions. They
./SAVANNAH-crawl/a2ps/doc/regex.texi:In @sc{gnu}, you can both match and search for a given regular
./SAVANNAH-crawl/a2ps/doc/regex.texi:compiled; with @sc{gnu}, you indicate what syntax you want by setting
./SAVANNAH-crawl/a2ps/doc/regex.texi:Matching the @sc{gnu} way means trying to match as much of a string as
./SAVANNAH-crawl/a2ps/doc/regex.texi:your character set. Under the @sc{ascii} encoding, therefore, a fastmap
./SAVANNAH-crawl/a2ps/doc/regex.texi:table, then the @sc{gnu} Regex functions to which you've passed that
./SAVANNAH-crawl/a2ps/doc/regex.texi:character set. Under the @sc{ascii} encoding, therefore, a translate
./SAVANNAH-crawl/a2ps/doc/regex.texi:ones. Under the @sc{ascii} encoding, here's how you could initialize
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{gnu} matching or searching function (@pxref{GNU Matching} and
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{posix}, on the other hand, requires a different interface: the
./SAVANNAH-crawl/a2ps/doc/regex.texi:@sc{posix} function described in @ref{Freeing POSIX Pattern Buffers},
./SAVANNAH-crawl/a2ps/doc/regex.texi:since the type @code{regex_t}---the type for @sc{posix} pattern
./SAVANNAH-crawl/a2ps/doc/regex.texi:If you're writing code that has to be @sc{posix} compatible, you'll need
./SAVANNAH-crawl/a2ps/doc/regex.texi:to use these functions. Their interfaces are as specified by @sc{posix},
./SAVANNAH-crawl/a2ps/doc/regex.texi:To compile or match a given regular expression the @sc{posix} way, you
./SAVANNAH-crawl/a2ps/doc/regex.texi:must supply a pattern buffer exactly the way you do for @sc{gnu}
./SAVANNAH-crawl/a2ps/doc/regex.texi:(@pxref{GNU Pattern Buffers}). @sc{posix} pattern buffers have type
./SAVANNAH-crawl/a2ps/doc/regex.texi:@code{regex_t}, which is equivalent to the @sc{gnu} pattern buffer
./SAVANNAH-crawl/a2ps/doc/regex.texi:With @sc{posix}, you can only search for a given regular expression; you
./SAVANNAH-crawl/a2ps/doc/regex.texi:as you do for @sc{gnu} (@pxref{GNU Regular Expression Compiling}). See
./SAVANNAH-crawl/a2ps/doc/regex.texi:says to use @sc{posix} Extended Regular Expression syntax; if this isn't
./SAVANNAH-crawl/a2ps/doc/regex.texi:set, then says to use @sc{posix} Basic Regular Expression syntax.
./SAVANNAH-crawl/a2ps/doc/regex.texi:also sets the same fields the same way as does the @sc{gnu} compiling
./SAVANNAH-crawl/a2ps/doc/regex.texi:Matching the @sc{posix} way means trying to match a null-terminated
./SAVANNAH-crawl/a2ps/doc/regex.texi:In @sc{posix}, variables of type @code{regmatch_t} hold analogous
./SAVANNAH-crawl/a2ps/doc/regex.texi:information, but are not identical to, @sc{gnu}'s registers (@pxref{Using
./SAVANNAH-crawl/a2ps/doc/regex.texi:Registers}). To get information about registers in @sc{posix}, pass to
./SAVANNAH-crawl/a2ps/doc/regex.texi:If you're writing code that has to be Berkeley @sc{unix} compatible,
./SAVANNAH-crawl/a2ps/doc/regex.texi:in Berkeley @sc{unix}.
./SAVANNAH-crawl/a2ps/doc/regex.texi:With Berkeley @sc{unix}, you can only search for a given regular
./SAVANNAH-crawl/a2ps/doc/regex.texi:Searching the Berkeley @sc{unix} way means searching in a string
./SAVANNAH-crawl/a2ps/doc/regex.texi:automatically uses a @sc{gnu} fastmap (@pxref{Searching with Fastmaps}).
./SAVANNAH-crawl/m4/doc/m4.texi:encoding, such as @sc{ISO-8859-1}, you will not notice a difference).
./SAVANNAH-crawl/m4/doc/m4.texi:use non-@sc{ascii} characters in quoted strings (@pxref{Changequote}),
./SAVANNAH-crawl/m4/doc/m4.texi:exception of the @sc{nul} character (the zero byte @samp{'\0'}).
./SAVANNAH-crawl/m4/doc/m4.texi:In the @sc{ascii} encoding, the first example deletes all uppercase
./SAVANNAH-crawl/m4/doc/m4.texi:portable to @sc{ebcdic} or other encodings. The fourth example shows a
./SAVANNAH-crawl/m4/doc/m4.texi:or @samp{\0} for @sc{nul}, so that the frozen file can be pure
./SAVANNAH-crawl/m4/doc/m4.texi:@sc{ascii} (although when hand-editing a frozen file, it is still
./SAVANNAH-crawl/nyacc/doc/nyacc-c99-ug.texi:Manual. It is included with the @sc{nyacc} source as COPYING.DOC.
./SAVANNAH-crawl/nyacc/doc/nyacc-c99-hg.texi:Manual. It is included with the @sc{nyacc} source as COPYING.DOC.
./SAVANNAH-crawl/nyacc/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/nyacc/doc/nyacc-ug.texi:@sc{NYACC}
./SAVANNAH-crawl/nyacc/doc/nyacc-ug.texi:@c @alias NYACC = @sc{NYACC}
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:@xref{References}. In the application of @sc{nyacc} one writes out a
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:represented by a set of items. In @sc{nyacc} we use a pair (a cons
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:In @sc{nyacc} we denote a la-item with a cons cell where the car is
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:It is an important function used by @sc{nyacc} in generating a parser.
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:In @sc{nyacc} the canonical grammer will always include the following
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:parsers having one additional state with respect to @sc{nyacc} parsers.)
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:The generation of the automaton (aka the @dfn{machine}) in @sc{nyacc}
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:@chapter The @sc{NYACC} Module ::
./SAVANNAH-crawl/nyacc/doc/nyacc-hg.texi:Manual. It is included with the @sc{nyacc} source as COPYING.DOC.
./SAVANNAH-crawl/nyacc/doc/nyacc-fh-ug.texi:which are included in the @uref{https://www.nongnu.org/nyacc,@sc{NYACC}}
./SAVANNAH-crawl/nyacc/doc/nyacc-fh-ug.texi:@sc{NYACC} distribution, the relevant modules can be found under the
./SAVANNAH-crawl/nyacc/doc/nyacc-fh-ug.texi:guile)} are required. No other code from the @sc{NYACC} distribution
./SAVANNAH-crawl/guile-cv/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/autogen/autoopts/tpl/mdoc2texi.pl:Mdoc::def_macro( '.Ux', sub { '@sc{unix}', @_ } );
./SAVANNAH-crawl/autogen/autoopts/tpl/mdoc2texi.pl:Mdoc::def_macro( '.Fx', sub { '@sc{freebsd}', @_ } );
./SAVANNAH-crawl/arc/doc/fdl.texinfo:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/sqltutor/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gawk/doc/gawktexi.in:@samp{.} does not match the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawktexi.in:Otherwise, @sc{nul} is just another character. Other versions of @command{awk}
./SAVANNAH-crawl/gawk/doc/gawktexi.in:may not be able to match the @sc{nul} character.
./SAVANNAH-crawl/gawk/doc/gawktexi.in:You might think that for text files, the @sc{nul} character, which
./SAVANNAH-crawl/gawk/doc/gawktexi.in:@command{gawk} in fact accepts this, and uses the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawktexi.in:GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
./SAVANNAH-crawl/gawk/doc/gawktexi.in:@sc{nul} character as the string terminator. In effect, this means that
./SAVANNAH-crawl/gawk/doc/gawktexi.in:It happens that recent versions of @command{mawk} can use the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawktexi.in:@command{mawk} does not allow embedded @sc{nul} characters in strings.
./SAVANNAH-crawl/gawk/doc/gawktexi.in:eight-bit ASCII characters, including ASCII @sc{nul} (character code zero).
./SAVANNAH-crawl/gawk/doc/gawktexi.in:String values maintain both pointer and length, because embedded @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawktexi.in:@sc{nul}-terminated. Thus it is safe to pass such string values to
./SAVANNAH-crawl/gawk/doc/gawktexi.in:allows embedded @sc{nul} characters in string data, before using the data
./SAVANNAH-crawl/gawk/doc/gawktexi.in:require more work. Because @command{gawk} allows embedded @sc{nul} bytes
./SAVANNAH-crawl/gawk/doc/gawktexi.in:Message-Id: <9510311732.AA28472@scalpel.netlabs.com>
./SAVANNAH-crawl/gawk/doc/gawktexi.in:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gawk/doc/gawkinet.texi:@headitem @sc{protocol} @tab @sc{local port} @tab @sc{host name}
./SAVANNAH-crawl/gawk/doc/gawkinet.texi:@tab @sc{remote port} @tab @sc{Resulting connection-level behavior}
./SAVANNAH-crawl/gawk/doc/gawkinet.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gawk/doc/gawk.texi:@samp{.} does not match the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawk.texi:Otherwise, @sc{nul} is just another character. Other versions of @command{awk}
./SAVANNAH-crawl/gawk/doc/gawk.texi:may not be able to match the @sc{nul} character.
./SAVANNAH-crawl/gawk/doc/gawk.texi:You might think that for text files, the @sc{nul} character, which
./SAVANNAH-crawl/gawk/doc/gawk.texi:@command{gawk} in fact accepts this, and uses the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawk.texi:GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
./SAVANNAH-crawl/gawk/doc/gawk.texi:@sc{nul} character as the string terminator. In effect, this means that
./SAVANNAH-crawl/gawk/doc/gawk.texi:It happens that recent versions of @command{mawk} can use the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawk.texi:@command{mawk} does not allow embedded @sc{nul} characters in strings.
./SAVANNAH-crawl/gawk/doc/gawk.texi:You might think that for text files, the @sc{nul} character, which
./SAVANNAH-crawl/gawk/doc/gawk.texi:@command{gawk} in fact accepts this, and uses the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawk.texi:GNU/Linux systems, where the @sc{nul} character is in fact the record separator.
./SAVANNAH-crawl/gawk/doc/gawk.texi:@sc{nul} character as the string terminator. In effect, this means that
./SAVANNAH-crawl/gawk/doc/gawk.texi:It happens that recent versions of @command{mawk} can use the @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawk.texi:@command{mawk} does not allow embedded @sc{nul} characters in strings.
./SAVANNAH-crawl/gawk/doc/gawk.texi:eight-bit ASCII characters, including ASCII @sc{nul} (character code zero).
./SAVANNAH-crawl/gawk/doc/gawk.texi:String values maintain both pointer and length, because embedded @sc{nul}
./SAVANNAH-crawl/gawk/doc/gawk.texi:@sc{nul}-terminated. Thus it is safe to pass such string values to
./SAVANNAH-crawl/gawk/doc/gawk.texi:allows embedded @sc{nul} characters in string data, before using the data
./SAVANNAH-crawl/gawk/doc/gawk.texi:require more work. Because @command{gawk} allows embedded @sc{nul} bytes
./SAVANNAH-crawl/gawk/doc/gawk.texi:Message-Id: <9510311732.AA28472@scalpel.netlabs.com>
./SAVANNAH-crawl/gawk/doc/gawk.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gawk/doc/ChangeLog.1: * gawktexi.in: Restore use of @sc. Karl fixed makeinfo. :-)
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:@samp{.} non individua il carattere @sc{nul},
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:In altri contesti, @sc{nul} @`e solo un carattere qualsiasi. Altre versioni
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:@sc{nul}.
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:Si potrebbe pensare che per i file di testo il carattere @sc{NUL}, che
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:@command{gawk} di fatto lo accetta, e usa il carattere @sc{NUL}
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:GNU/Linux, dove il carattere @sc{NUL} @`e di fatto un separatore di record..
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:in stile C. Le stringhe in stile C usano il carattere @sc{NUL} come
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:@sc{NUL} come separatore di record. Comunque questo @`e un caso particolare:
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:@command{mawk} non consente di includere caratteri @sc{NUL} nelle stringhe.
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:@sc{nul} (carattere con codice zero).
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:poich@'e nella stringa possono essere presenti dei caratteri @sc{nul}
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:sempre un carattere @sc{nul} alla fine (come delimitatore). Quindi @`e
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:essere presenti caratteri @sc{nul}, si dovrebbe controllare che la
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:@command{gawk} consente che le stringhe contengano dei byte @sc{nul}
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:Message-Id: <9510311732.AA28472@scalpel.netlabs.com>
./SAVANNAH-crawl/gawk/doc/it/gawktexi.in:Esempi di formati adatti per copie trasparenti sono l'@sc{ASCII} puro senza
Binary file ./SAVANNAH-crawl/teximpatient/.git/objects/pack/pack-a0ff0d349709622dadf237bd5016056743b9615a.pack matches
./SAVANNAH-crawl/teximpatient/teximpatient/eplain.tex:\def\bblsc{\ifx\@scfont\@undefined
./SAVANNAH-crawl/teximpatient/teximpatient/eplain.tex: \font\@scfont = cmcsc10
./SAVANNAH-crawl/teximpatient/teximpatient/eplain.tex: \@scfont
Binary file ./SAVANNAH-crawl/teximpatient/teximpatient/artwork/ch05-para.png matches
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:some implementations of @command{sed} (which are not @sc{posix}
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Note: the @sc{posix} standard does not specify what should happen
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:a @sc{nul} character. This is a @value{SSED} extension.
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:executed contains a @sc{nul} character.
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a @sc{bel} character, that is an ``alert'' (@sc{ascii} 7).
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a form feed (@sc{ascii} 12).
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a newline (@sc{ascii} 10).
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a carriage return (@sc{ascii} 13).
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a horizontal tab (@sc{ascii} 9).
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a so called ``vertical tab'' (@sc{ascii} 11).
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches @kbd{@sc{Control}-@var{x}}, where @var{x} is
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a character whose decimal @sc{ascii} value is @var{xxx}.
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a character whose octal @sc{ascii} value is @var{xxx}.
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:with the @code{o} is active in the normal or extended @sc{posix} regular
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Produces or matches a character whose hexadecimal @sc{ascii} value is @var{xx}.
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Ubben wrote an implementation of the @command{dc} @sc{rpn} calculator!
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:The @sc{posix} standard specifies that conforming @command{sed}
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Also, @value{SSED} recognizes the @sc{posix} syntax
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:@command{sed} uses the @sc{posix} basic regular expression syntax. According to
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:As in all GNU programs that use @sc{posix} basic regular expressions, @command{sed}
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:with the free @sc{pcre} regular expression matcher; it was written by Philip Hazel.}
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:@sc{ascii} values for characters can be specified in octal
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:for @var{xxx}. For example @code{\07} is a @sc{bel} character
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:rather than a @sc{nul} and a literal @code{7} (this sequence is
./SAVANNAH-crawl/sed-history/doc/sed-in.texi: \377 @i{is a byte consisting entirely of 1 bits (@sc{ascii} 255)}
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:outside character classes. Instead, in @sc{posix} mode these sequences
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:@code{\<} and @code{\>} achieve this purpose in @sc{posix} mode
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:@code{\`} and @code{\'} that are active in @sc{posix} mode.
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Ranges operate in @sc{ascii} collating sequence. They can also be
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Unlike in @sc{posix} mode, the character types @code{\d},
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:Perl 5.6 supports the @sc{posix} notation for character classes, which
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:By default, the quantifiers are @dfn{greedy} like in @sc{posix}
./SAVANNAH-crawl/sed-history/doc/sed-in.texi:in @sc{posix} mode. If the pattern continues with a digit
./SAVANNAH-crawl/sed-history/doc/sed.texi:some implementations of @command{sed} (which are not @sc{posix}
./SAVANNAH-crawl/sed-history/doc/sed.texi:Note: the @sc{posix} standard does not specify what should happen
./SAVANNAH-crawl/sed-history/doc/sed.texi:a @sc{nul} character. This is a @value{SSED} extension.
./SAVANNAH-crawl/sed-history/doc/sed.texi:executed contains a @sc{nul} character.
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a @sc{bel} character, that is an ``alert'' (@sc{ascii} 7).
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a form feed (@sc{ascii} 12).
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a newline (@sc{ascii} 10).
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a carriage return (@sc{ascii} 13).
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a horizontal tab (@sc{ascii} 9).
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a so called ``vertical tab'' (@sc{ascii} 11).
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches @kbd{@sc{Control}-@var{x}}, where @var{x} is
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a character whose decimal @sc{ascii} value is @var{xxx}.
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a character whose octal @sc{ascii} value is @var{xxx}.
./SAVANNAH-crawl/sed-history/doc/sed.texi:with the @code{o} is active in the normal or extended @sc{posix} regular
./SAVANNAH-crawl/sed-history/doc/sed.texi:Produces or matches a character whose hexadecimal @sc{ascii} value is @var{xx}.
./SAVANNAH-crawl/sed-history/doc/sed.texi:Ubben wrote an implementation of the @command{dc} @sc{rpn} calculator!
./SAVANNAH-crawl/sed-history/doc/sed.texi:The @sc{posix} standard specifies that conforming @command{sed}
./SAVANNAH-crawl/sed-history/doc/sed.texi:Also, @value{SSED} recognizes the @sc{posix} syntax
./SAVANNAH-crawl/sed-history/doc/sed.texi:@command{sed} uses the @sc{posix} basic regular expression syntax. According to
./SAVANNAH-crawl/sed-history/doc/sed.texi:As in all GNU programs that use @sc{posix} basic regular expressions, @command{sed}
./SAVANNAH-crawl/sed-history/doc/sed.texi:with the free @sc{pcre} regular expression matcher; it was written by Philip Hazel.}
./SAVANNAH-crawl/sed-history/doc/sed.texi:@sc{ascii} values for characters can be specified in octal
./SAVANNAH-crawl/sed-history/doc/sed.texi:for @var{xxx}. For example @code{\07} is a @sc{bel} character
./SAVANNAH-crawl/sed-history/doc/sed.texi:rather than a @sc{nul} and a literal @code{7} (this sequence is
./SAVANNAH-crawl/sed-history/doc/sed.texi: \377 @i{is a byte consisting entirely of 1 bits (@sc{ascii} 255)}
./SAVANNAH-crawl/sed-history/doc/sed.texi:outside character classes. Instead, in @sc{posix} mode these sequences
./SAVANNAH-crawl/sed-history/doc/sed.texi:@code{\<} and @code{\>} achieve this purpose in @sc{posix} mode
./SAVANNAH-crawl/sed-history/doc/sed.texi:@code{\`} and @code{\'} that are active in @sc{posix} mode.
./SAVANNAH-crawl/sed-history/doc/sed.texi:Ranges operate in @sc{ascii} collating sequence. They can also be
./SAVANNAH-crawl/sed-history/doc/sed.texi:Unlike in @sc{posix} mode, the character types @code{\d},
./SAVANNAH-crawl/sed-history/doc/sed.texi:Perl 5.6 supports the @sc{posix} notation for character classes, which
./SAVANNAH-crawl/sed-history/doc/sed.texi:By default, the quantifiers are @dfn{greedy} like in @sc{posix}
./SAVANNAH-crawl/sed-history/doc/sed.texi:in @sc{posix} mode. If the pattern continues with a digit
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@samp{%c} debe ser un n@'umero de c@'odigo @sc{ascii}; eso ser@'a
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:impreso como el caracter con este c@'odigo @sc{ascii}. (Otras varias
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:El @sc{car} de una lista es, bastante simple, el primer
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@'{@dotless{i}}tem en la lista. De este modo, el @sc{car} de la lista
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:El @sc{cdr} de una lista es el resto de la lista, que es, la funci@'on
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@'{@dotless{i}}tem. De este modo, mientras el @sc{car} de la lista
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:el @sc{cdr} de la lista es una lista por s@'{@dotless{i}} misma,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:En este ejemplo, el primer elemento de @sc{car} de la lista es la
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{cdr}. Que lo que hace es tomar la @sc{cdr} de una lista repetidamente.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Si se toma el @sc{cdr} de la lista @code{(pino roble abeto arce)},
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:arce)}. (De acuerdo, se repite @sc{cdr} en la lista original solo se
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:dar@'a @sc{cdr} desde la funci@'on que no cambia la lista. Se necesita
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:evaluar el @sc{cdr} del @sc{cdr} y as@'{@dotless{i}}.) Si se conti@'ua
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Para revisar, aqu@'{@dotless{i}} hay una serie de @sc{cdr}s repetidos,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Tambi@'en se pueden hacer varios @sc{cdr}s sin imprimir los valores
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:La funci@'on @code{nthcdr} toma el @sc{cdr} de una lista
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:repetidamente. La funci@'on @code{nth} toma el @sc{car} del resultado
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:decir, el primer elemento de una lista, su @sc{car} es el elemento
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{setcar} y @code{setcdr} asignan el @sc{car} o la @sc{cdr} de una
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@sc{cdr} de la primera lista sea asignada;
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:a @code{(caballo gato perro)}. El @sc{cdr} de la lista es cambiada desde
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:primer elemento (el @sc{car} del anillo de la muerte. Por otro lado,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:al @sc{car} del anillo de la muerte @emph{kill ring}. Si eso se
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{setcdr}}). Eso asigna el @sc{cdr} de una lista, solo como
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{setcar} asigna el @sc{car} de una lista. En este caso, sin
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:embargo, @code{setcdr} no estar@'a configurando el @sc{cdr} del kill
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:asignar el @sc{cdr} del siguiente al @'ultimo elemento del kill ring
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:--- esto significa que desde el @sc{cdr} del siguiente al @'ultimo
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:La funci@'on @code{nthcdr} funciona repetidamente tomando el @sc{cdr}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:de una lista --- eso toma el @sc{cdr} del @sc{cdr} del @sc{cdr}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@sc{cdr} del siguiente al @'ultimo elemento a @code{nil}, y por eso se
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{(arce encina pino abedul)} entonces asigna el @sc{cdr} de su
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:segundo @sc{cdr} y entonces encuentra el valor de @code{arboles}.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:desde que es que el @sc{cdr} es asignado.)
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@sc{cdr} un n@'umero de veces que es uno menos que el tama@~no
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{setcdr} asigna el @sc{cdr} de este elemento (que ser@'a el resto
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Devuelve el resultado de tomar @sc{cdr} `n' veces en una lista.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Si un s@'{@dotless{i}}mbolo se asigna al @sc{cdr} de una lista, la
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@sc{car} y @sc{cdr} son `no destructivos'.) De este modo, se eval@'ua
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:De este modo, en Lisp, tiene el @sc{cdr} de una lista, se obtiene la
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:direcci@'on del siguiente cons en las serie; para tener el @sc{car} de
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{mas-flores}. Asigna el @sc{car} de @code{flores} a un
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:que el primer elemento (el @sc{car}) ser@'a insertado.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{while} que asigna el valor de la lista para ser el @sc{cdr} de
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{animals} se puede asignar a ser el @sc{cdr} de la lista original
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{dolist} funciona como un bucle @code{while} con `@sc{cdr}s que
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:vez que la lista hace bucles --- toma la @sc{cdr} de la lista --- y
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:asocia el @sc{car} de cada versi@'on ordenada de la lista al primero
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:se repite --- eso es `recorrer los @sc{cdr}s de la lista' en
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:s@'{@dotless{i}} --- y eso autom@'aticamente asocia el @sc{car} de
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:En el ejemplo, el @sc{car} de cada versi@'on ordenada de la lista se
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:La expresi@'on @code{dolist} asocia el @sc{car} de cada versi@'on
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:primer elemento de la lista, el @sc{car} de la lista. Entonces la
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:subsiguientes elementos de la lista, el @sc{cdr} de la lista.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:con la @sc{cdr} del @sc{cdr} de la lista original.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:eval@'ua el primer elemento (el @sc{car} o true-or-false-test) de la
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Si no, se va al principio de la lista (el @sc{car} de la lista) actuando
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:(el @sc{cdr}) de la lista,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@item act@'ua al principio de la lista (el @sc{car} de la lista),
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@item y crea una llamada recursiva en el resto (el @sc{cdr} de la lista).
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Lo dem@'as, act@'ua al principio de la lista (el @sc{car} de la
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:la funci@'on en el resto (el @sc{cdr}) de la lista.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:Lo dem@'as, si el principio de la lista (el @sc{car} de la lista) pasa
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@item una llamada recursiva por la funci@'on en el resto (el @sc{cdr}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:De otro modo, si el principio de la lista (el @sc{car} de la lista)
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@item y, recursivamente llama la funci@'on al resto (el @sc{cdr}) de
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:lista para el valor del @sc{cdr} de la lista cada vez que el cuerpo es
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:`next-step-expression' resetea el @code{list-of-files} al @sc{cdr} en
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:`@sc{cdr}s' bajo la lista de tama@~nos, parece que cada elemento,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:@code{(setq numbers-list (cdr numbers-list))}, el @sc{car} de cada
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:como los eventos del rat@'on y caracteres no @sc{ascii} son escritos
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:tres hexadecimales, y @sc{ascii} `control-c' (la tercera letra del
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:asignado para ser igual a alg@'un @sc{cdr} del anillo de la muerte
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:funciona repetidamente tomando el @sc{cdr} de una lista --- eso toma
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:el @sc{cdr}, del @sc{cdr}, del @sc{cdr}, @dots{}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:funci@'on @code{mod} para determinar que @sc{cdr} para seleccionar.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro-es.texi:un @sc{cons} en vez de un n@'umero o nada, se pone el punto al principio
./SAVANNAH-crawl/elisp-es/doclicense.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:number. The argument used by @samp{%c} must be an @sc{ascii} code
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:number; it will be printed as the character with that @sc{ascii} code.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:The @sc{car} of a list is, quite simply, the first item in the list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:Thus the @sc{car} of the list @code{(rose violet daisy buttercup)} is
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:The @sc{cdr} of a list is the rest of the list, that is, the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:first item. Thus, while the @sc{car} of the list @code{'(rose violet
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:list. However, the @sc{cdr} of the list is a list itself, @code{(fir
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:In this example, the first element or @sc{car} of the list is the list of
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:What it does is take the @sc{cdr} of a list repeatedly.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:If you take the @sc{cdr} of the list @code{(pine fir
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@code{(oak maple)}. (Of course, repeated @sc{cdr}ing on the original
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:list will just give you the original @sc{cdr} since the function does
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:not change the list. You need to evaluate the @sc{cdr} of the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{cdr} and so on.) If you continue this, eventually you will be
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:For review, here is a series of repeated @sc{cdr}s, the text following
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:You can also do several @sc{cdr}s without printing the values in
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:The @code{nthcdr} function takes the @sc{cdr} of a list repeatedly.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:The @code{nth} function takes the @sc{car} of the result returned by
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:say, the first element of a list, its @sc{car} is the zeroth element.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:functions set the @sc{car} or the @sc{cdr} of a list to a new value.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{cdr} of the first list will be set;
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@code{(horse cat dog)}. The @sc{cdr} of the list is changed from
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:with the text already in the first element (the @sc{car}) of the kill
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:the @sc{car} of the kill ring. Whether it prepends or appends the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:It sets the @sc{cdr} of a list, just as @code{setcar} sets the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{car} of a list. In this case, however, @code{setcdr} will not be
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:setting the @sc{cdr} of the whole kill ring; the @code{nthcdr}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:function is used to cause it to set the @sc{cdr} of the next to last
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:element of the kill ring---this means that since the @sc{cdr} of the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:The @code{nthcdr} function works by repeatedly taking the @sc{cdr} of a
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:list---it takes the @sc{cdr} of the @sc{cdr} of the @sc{cdr}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:elements long, we could set the @sc{cdr} of the next to last element
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:birch)}, then set the @sc{cdr} of its second @sc{cdr} to @code{nil}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:that is what the @sc{cdr} is set to.)
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{cdr} a number of times that is one less than the maximum permitted
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:size of the kill ring and @code{setcdr} sets the @sc{cdr} of that
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:Return the result of taking @sc{cdr} `n' times on a list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:If a symbol is set to the @sc{cdr} of a list, the list itself is not
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:the jargon, @sc{car} and @sc{cdr} are `non-destructive'.) Thus,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:Thus, in Lisp, to get the @sc{cdr} of a list, you just get the address
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:of the next cons cell in the series; to get the @sc{car} of a list,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@code{more-flowers}. Set the @sc{car} of @code{flowers} to a fish.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:of the kill ring of which the first element (the @sc{car}) will be
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:expression set the value of the list to be the @sc{cdr} of the list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:can be set to be the @sc{cdr} of the original list with the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@code{dolist} works like a @code{while} loop that `@sc{cdr}s down a
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:loops---takes the @sc{cdr} of the list---and binds the @sc{car} of
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:`@sc{cdr}s down the list' on its own---and it automatically binds
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:the @sc{car} of each shorter version of the list to the first of its
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:In the example, the @sc{car} of each shorter version of the list is
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:The @code{dolist} expression binds the @sc{car} of each shorter
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:first element of the list, the @sc{car} of the list. Then the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{cdr} of the list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:list). Then the function `calls itself' with the @sc{cdr} of the list
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:it is invoked with, which (the second time around) is the @sc{cdr} of
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:the @sc{cdr} of the original list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:evaluates the first element (the @sc{car} or true-or-false-test) of
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list)
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi: @sc{cdr}) of the list,
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi: act on the beginning of the list (the @sc{car} of the list),
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi: and make a recursive call on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:Else, act on the beginning of the list (the @sc{car} of the list),
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:Else, if the beginning of the list (the @sc{car} of the list) passes
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi: a recursive call by the function on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:Otherwise, if the beginning of the list (the @sc{car} of the list) fails
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi: and, recursively call the function on the rest (the @sc{cdr}) of the list.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:technique is to set the value of the list to the value of the @sc{cdr}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{cdr} of itself, so eventually the list will be empty; and the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:should not be too hard to write a function that `@sc{cdr}s' down the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:(cdr numbers-list))} expression, the @sc{car} of each instance of the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:non-@sc{ascii} characters are written within square brackets, without
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:hexadecimal three, and @sc{ascii} `control-c' (the third letter of the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:set to be equal to some @sc{cdr} of the kill ring, using the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:works by repeatedly taking the @sc{cdr} of a list---it takes the
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{cdr} of the @sc{cdr} of the @sc{cdr} @dots{}
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:the @code{mod} function to determine which @sc{cdr} to select.
./SAVANNAH-crawl/elisp-es/emacs-lisp-intro.texi:@sc{cons} rather than a number or nothing, it puts point at beginning
./SAVANNAH-crawl/rawtools/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gluster/doc/user-guide/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/libcdio/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/make/doc/make.texi:Program to make @TeX{} @sc{dvi} files from @TeX{} source;
./SAVANNAH-crawl/make/doc/make.texi:Program to make @TeX{} @sc{dvi} files from Texinfo source;
./SAVANNAH-crawl/guile/module/texinfo/indexing.scm:The returned index is a list of pairs, the @sc{car} of which is the
./SAVANNAH-crawl/guile/module/texinfo/indexing.scm:entry (a string) and the @sc{cdr} of which is a node name (a string)."
./SAVANNAH-crawl/guile/doc/ref/api-regex.texi:Or matching a @sc{yyyymmdd} format date such as @samp{20020828} and
./SAVANNAH-crawl/guile/doc/ref/api-data.texi:Return the bitwise @sc{and} of the integer arguments.
./SAVANNAH-crawl/guile/doc/ref/api-data.texi:Return the bitwise @sc{or} of the integer arguments.
./SAVANNAH-crawl/guile/doc/ref/api-data.texi:Return the bitwise @sc{xor} of the integer arguments. A bit is
./SAVANNAH-crawl/guile/doc/ref/api-data.texi:common @sc{unix} command of the same name.
./SAVANNAH-crawl/guile/doc/ref/srfi-modules.texi:Return two values, the @sc{car} and the @sc{cdr} of @var{pair}.
./SAVANNAH-crawl/guile/doc/ref/srfi-modules.texi:Return the first pair of @var{lst} whose @sc{car} satisfies the
./SAVANNAH-crawl/guile/doc/ref/srfi-modules.texi:Return the first sublist of @var{lst} whose @sc{car} is equal to
./SAVANNAH-crawl/guile/doc/ref/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/guile/doc/ref/texinfo.texi:The returned index is a list of pairs, the @sc{car} of which is the
./SAVANNAH-crawl/guile/doc/ref/texinfo.texi:entry (a string) and the @sc{cdr} of which is a node name (a string).
./SAVANNAH-crawl/guile/doc/ref/data-rep.texi:the @sc{car} and @sc{cdr}. Is there any way to represent pairs using
./SAVANNAH-crawl/guile/doc/ref/api-binding.texi:@sc{Algol 60}. Readers familiar to languages like C or Java should
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author R@sc{ICHARD} K@sc{ELSEY}, W@sc{ILLIAM} C@sc{LINGER, AND} J@sc{ONATHAN} R@sc{EES} (@i{Editors})
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author H. A@sc{BELSON}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author R. K. D@sc{YBVIG}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author C. T. H@sc{AYNES}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author G. J. R@sc{OZAS}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author N. I. A@sc{DAMS IV}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author D. P. F@sc{RIEDMAN}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author E. K@sc{OHLBECKER}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author G. L. S@sc{TEELE} J@sc{R}.
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author D. H. B@sc{ARTLEY}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author R. H@sc{ALSTEAD}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author D. O@sc{XLEY}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author G. J. S@sc{USSMAN}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author G. B@sc{ROOKS}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author C. H@sc{ANSON}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author K. M. P@sc{ITMAN}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@author M. W@sc{AND}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:R@sc{ichard} K@sc{elsey}, W@sc{illiam} C@sc{linger, and} J@sc{onathan} R@sc{ees} (@i{Editors})
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@item H. A@sc{belson} @tab R. K. D@sc{ybvig} @tab C. T. H@sc{aynes} @tab G. J. R@sc{ozas}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@item N. I. A@sc{dams IV} @tab D. P. F@sc{riedman} @tab E. K@sc{ohlbecker} @tab G. L. S@sc{teele} J@sc{r}.
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@item D. H. B@sc{artley} @tab R. H@sc{alstead} @tab D. O@sc{xley} @tab G. J. S@sc{ussman}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:@item G. B@sc{rooks} @tab C. H@sc{anson} @tab K. M. P@sc{itman} @tab M. W@sc{and}
./SAVANNAH-crawl/guile/doc/r5rs/r5rs.texi:and notation used here are described in @sc{[Stoy77]}.
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:@set TITLE Using @sc{gnu} @i{lightning}
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:@sc{gnu}
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:generator is @sc{dcg}, by Dawson R.@: Engler and T.@: A.@: Proebsting.
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:Further work by Dawson R. Engler resulted in the @sc{vcode} system;
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:unlike @sc{dcg}, @sc{vcode} used no intermediate representation and
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:program @sc{ccg} under the GNU General Public License, thereby allowing
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:@lightning{} to use the run-time assemblers he had wrote for @sc{ccg}.
./SAVANNAH-crawl/guile/libguile/lightening/lightning.texi:@sc{ccg} provides a way of dynamically assemble programs written in the
./SAVANNAH-crawl/autobuild/doc/htmlfontify.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./SAVANNAH-crawl/mailutils/doc/texinfo/libmu_sieve.texi:@code{mu_sieve_machine_add_destructor()} are executed in @sc{lifo}
./SAVANNAH-crawl/mailutils/doc/texinfo/libmu_auth.texi:information about a user from several places, like @sc{sql} database,
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:This section describes the textual date representations that @sc{gnu}
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:* Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:1972-09-24 # @sc{iso} 8601.
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:@cindex @sc{iso} 8601 date format
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:@cindex date format, @sc{iso} 8601
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:For numeric months, the @sc{iso} 8601 format
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:20:02-0500 # In @sc{est} (U.S. Eastern Standard Time).
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:Coordinated Universal Time (@sc{utc}), overriding any previous
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:ahead of @sc{utc} (e.g., India).
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:@acronym{POSIX} systems, the epoch is 1970-01-01 00:00:00 @sc{utc}, so
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:00:00:01 @sc{utc}, and so forth. @acronym{GNU} and most other
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:represents 1969-12-31 23:59:59 @sc{utc}.
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:2038-01-19 03:14:07 @sc{utc}. More modern systems use 64-bit counts
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:23:59:59 @sc{utc}, @samp{@@915148800} represents 1999-01-01 00:00:00
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:@sc{utc}, and there is no way to represent the intervening leap second
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:1998-12-31 23:59:60 @sc{utc}.
./SAVANNAH-crawl/mailutils/doc/texinfo/getdate.texi:revisions for the @sc{gnu} system were made by David MacKenzie, Jim Meyering,
./SAVANNAH-crawl/mailutils/doc/texinfo/mailutils.texi:* Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
./SAVANNAH-crawl/mailutils/doc/texinfo/sieve.texi:It treats uppercase and lowercase characters in the @sc{ascii} subset of
./SAVANNAH-crawl/mailutils/doc/texinfo/sieve.texi:@sc{utf-8} as the same. This is the default comparator.
./SAVANNAH-crawl/mailutils/doc/texinfo/sieve.texi:Treats the two arguments as @sc{ascii} representation of decimal
./SAVANNAH-crawl/mailutils/doc/texinfo/sieve.texi:The @code{envelope} test is true if the specified part of the @sc{smtp}
./SAVANNAH-crawl/mailutils/doc/texinfo/sieve.texi:@emph{Notice}, that due to the limitations imposed by @sc{smtp} envelope
./SAVANNAH-crawl/mailutils/doc/texinfo/sieve.texi:@sc{unix}. The address on the SMTP envelope is replaced with the one on
./SAVANNAH-crawl/mailutils/doc/texinfo/programs/mailutils.texi:single @sc{tab} character. Empty lines are ignored. For example:
./SAVANNAH-crawl/mailutils/doc/texinfo/programs/mailutils.texi:beginning with a sharp sign or containing @sc{tab}. The version 1.0
./SAVANNAH-crawl/mailutils/doc/texinfo/programs/imap4d.texi:GNU @command{imap4d} is a daemon implementing @sc{imap4} rev1 protocol
./SAVANNAH-crawl/mailutils/doc/texinfo/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/bison/doc/bison.texi:``Reverse Polish @sc{calc}ulator''). Bison produces a parser
./SAVANNAH-crawl/ccd2cue/doc/philosophy/gnu-free-documentation-license.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/qpimd/doc/install.texi:Force to enable @sc{gnu}/Linux netlink interface. Quagga configure
./SAVANNAH-crawl/qpimd/doc/install.texi:There are several options available only to @sc{gnu}/Linux systems:
./SAVANNAH-crawl/qpimd/doc/install.texi:@footnote{@sc{gnu}/Linux has very flexible kernel configuration features}. If
./SAVANNAH-crawl/qpimd/doc/install.texi:you use @sc{gnu}/Linux, make sure that the current kernel configuration is
./SAVANNAH-crawl/qpimd/doc/install.texi:IPv6 support has been added in @sc{gnu}/Linux kernel version 2.2. If you
./SAVANNAH-crawl/qpimd/doc/install.texi:try to use the Quagga IPv6 feature on a @sc{gnu}/Linux kernel, please
./SAVANNAH-crawl/qpimd/doc/install.texi:these libraries will not be needed when you uses @sc{gnu} C library 2.1
./SAVANNAH-crawl/qpimd/doc/overview.texi: Quagga is distributed under the @sc{gnu} General Public License.
./SAVANNAH-crawl/qpimd/doc/overview.texi:which comes with @sc{gnu}/Linux or FreeBSD has some problems with running
./SAVANNAH-crawl/qpimd/doc/overview.texi:Currently Quagga supports @sc{gnu}/Linux, BSD and Solaris. Porting Quagga
./SAVANNAH-crawl/qpimd/doc/overview.texi:@sc{gnu}/Linux 2.4.x and higher
./SAVANNAH-crawl/gnugo/doc/copying.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-de.texinfo:Für @sc{posix}-kompatible Betriebssysteme gibt es auch einen
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-de.texinfo:Dieses Kapitel beschreibt die Installation für @sc{posix}-kompatible
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-de.texinfo:Das Programm @command{avatarsay} kann auf @sc{posix}-kompatiblen Systemen
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-de.texinfo:vielen anderen @sc{posix}-kompatiblen Systemen ebenfalls ohne weiteres laufen.
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-en.texinfo:For @sc{posix}-compatible operating systems there is a manpage viewer, and
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-en.texinfo:This chapter describes the installation for @sc{posix} compatible operating
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-en.texinfo:frontend for textconsole programs on @sc{posix}-compatible systems (not for
./SAVANNAH-crawl/akfavatar/olddoc/akfavatar-en.texinfo:on other @sc{posix}-compatible systems also.
./SAVANNAH-crawl/pspp/doc/pspp.texi:@sc{pspp}
./SAVANNAH-crawl/pspp/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/haploid/doc/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/aris/doc/aris.texi:A connective is a logical symbol that connects one or more sentences. The connectives used in system @sc{psi} are conjuction (@samp{^}), disjunction (@samp{v}), negation, (@samp{~}), conditional (@samp{@arrow{}}), and biconditional (@samp{<->}). In addition, system @sc{psi} recognizes the one-place connectives of the tautology (@samp{T}) and the contradiction (@samp{!}).
./SAVANNAH-crawl/aris/doc/aris.texi:A quantifier is a type of logical symbol that claims something about the amount, or quantity, of an object that holds a specific property. The quantifiers used in system @sc{psi} are the universal (@samp{V}), and the existential (@samp{3}).
./SAVANNAH-crawl/autoconf/doc/make-stds.texi:@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf,
./SAVANNAH-crawl/autoconf/doc/make-stds.texi:shell and the @sc{posix} shell), not @code{csh}. Don't use any
./SAVANNAH-crawl/autoconf/doc/make-stds.texi:special features of @code{ksh} or @code{bash}, or @sc{posix} features
./SAVANNAH-crawl/autoconf/doc/make-stds.texi:@sc{posix}-specified) options and features of these programs. For
./SAVANNAH-crawl/autoconf/ChangeLog.2: * doc/autoconf.texi: Use @sc where upper case names were used.
./SAVANNAH-crawl/autoconf/ChangeLog.3: * doc/autoconf.texi: Remove all usage of @sc in the manual.
./SAVANNAH-crawl/wget/doc/texi2pod.pl: s/\@sc\{([^\}]*)\}/\U$1/g;
./SAVANNAH-crawl/wget/doc/wget.texi:the Web. It supports @sc{http}, @sc{https}, and @sc{ftp} protocols, as
./SAVANNAH-crawl/wget/doc/wget.texi:well as retrieval through @sc{http} proxies.
./SAVANNAH-crawl/wget/doc/wget.texi:Wget can follow links in @sc{html}, @sc{xhtml}, and @sc{css} pages, to
./SAVANNAH-crawl/wget/doc/wget.texi:available when retrieving via @sc{ftp}. Wget can read the time-stamp
./SAVANNAH-crawl/wget/doc/wget.texi:information given by both @sc{http} and @sc{ftp} servers, and store it
./SAVANNAH-crawl/wget/doc/wget.texi:makes Wget suitable for mirroring of @sc{ftp} sites, as well as home
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp} downloading by default, active @sc{ftp} being an option.
./SAVANNAH-crawl/wget/doc/wget.texi:Wget will simply download all the @sc{url}s specified on the command
./SAVANNAH-crawl/wget/doc/wget.texi:available via the Internet. Wget recognizes the @sc{url} syntax as per
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{rfc1738}. This is the most widely used form (square brackets denote
./SAVANNAH-crawl/wget/doc/wget.texi:You can also encode your username and password within a @sc{url}:
./SAVANNAH-crawl/wget/doc/wget.texi:leave out either the @sc{http} username or password, no authentication
./SAVANNAH-crawl/wget/doc/wget.texi:will be sent. If you leave out the @sc{ftp} username, @samp{anonymous}
./SAVANNAH-crawl/wget/doc/wget.texi:will be used. If you leave out the @sc{ftp} password, your email
./SAVANNAH-crawl/wget/doc/wget.texi:@strong{Important Note}: if you specify a password-containing @sc{url}
./SAVANNAH-crawl/wget/doc/wget.texi:and feed the @sc{url}s to Wget's standard input, each on a separate
./SAVANNAH-crawl/wget/doc/wget.texi:You can encode unsafe characters in a @sc{url} as @samp{%xy}, @code{xy}
./SAVANNAH-crawl/wget/doc/wget.texi:being the hexadecimal representation of the character's @sc{ascii}
./SAVANNAH-crawl/wget/doc/wget.texi:@samp{%40}). Refer to @sc{rfc1738} for a comprehensive list of unsafe
./SAVANNAH-crawl/wget/doc/wget.texi:Wget also supports the @code{type} feature for @sc{ftp} @sc{url}s. By
./SAVANNAH-crawl/wget/doc/wget.texi:default, @sc{ftp} documents are retrieved in the binary mode (type
./SAVANNAH-crawl/wget/doc/wget.texi:Two alternative variants of @sc{url} specification are also supported,
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp}-only syntax (supported by @code{NcFTP}):
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{http}-only syntax (introduced by @code{Netscape}):
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{url} @samp{-x}, reporting failure to @file{log}:
./SAVANNAH-crawl/wget/doc/wget.texi:Read @sc{url}s from a local or external @var{file}. If @samp{-} is
./SAVANNAH-crawl/wget/doc/wget.texi:specified as @var{file}, @sc{url}s are read from the standard input.
./SAVANNAH-crawl/wget/doc/wget.texi:If this function is used, no @sc{url}s need be present on the command
./SAVANNAH-crawl/wget/doc/wget.texi:line. If there are @sc{url}s both on the command line and in an input
./SAVANNAH-crawl/wget/doc/wget.texi:When input is read from a file, force it to be treated as an @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{html} files on your local disk, by adding @code{} to @sc{html}, or using the @samp{--base} command-line
./SAVANNAH-crawl/wget/doc/wget.texi:a server describing it as @sc{html}). This is equivalent to the
./SAVANNAH-crawl/wget/doc/wget.texi:presence of a @code{BASE} tag in the @sc{html} input file, with
./SAVANNAH-crawl/wget/doc/wget.texi:@samp{-c} is if you have a lame @sc{http} proxy that inserts a
./SAVANNAH-crawl/wget/doc/wget.texi:Note that @samp{-c} only works with @sc{ftp} servers and with @sc{http}
./SAVANNAH-crawl/wget/doc/wget.texi:The ``bar'' indicator is used by default. It draws an @sc{ascii} progress
./SAVANNAH-crawl/wget/doc/wget.texi:Print the headers sent by @sc{http} servers and responses sent by
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp} servers.
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{url}s are specified on the command-line. The quota is checked only
./SAVANNAH-crawl/wget/doc/wget.texi:those in the @sc{ascii} range of values.
./SAVANNAH-crawl/wget/doc/wget.texi:are outside the range of @sc{ascii} characters (that is, greater than
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp} and @sc{http} file retrieval. These parameters can be overridden
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp} connections and the @samp{--http-user} and @samp{--http-password}
./SAVANNAH-crawl/wget/doc/wget.texi:options for @sc{http} connections.
./SAVANNAH-crawl/wget/doc/wget.texi:how Wget converts URLs specified as arguments from locale to @sc{utf-8} for
./SAVANNAH-crawl/wget/doc/wget.texi:environment variable to get the locale. If it fails, @sc{ascii} is used.
./SAVANNAH-crawl/wget/doc/wget.texi:to @sc{utf-8} during a recursive fetch. This options is only useful for
./SAVANNAH-crawl/wget/doc/wget.texi:IRI support, for the interpretation of non-@sc{ascii} characters.
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{http} server. According to the type of the challenge, Wget will
./SAVANNAH-crawl/wget/doc/wget.texi:Another way to specify username and password is in the @sc{url} itself
./SAVANNAH-crawl/wget/doc/wget.texi:process typically works by the web server issuing an @sc{http} cookie
./SAVANNAH-crawl/wget/doc/wget.texi:Unfortunately, some @sc{http} servers (@sc{cgi} programs, to be more
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{http} request. The supplied header is sent as-is, which means it
./SAVANNAH-crawl/wget/doc/wget.texi:Save the headers sent by the @sc{http} server to the file, preceding the
./SAVANNAH-crawl/wget/doc/wget.texi:Identify as @var{agent-string} to the @sc{http} server.
./SAVANNAH-crawl/wget/doc/wget.texi:The @sc{http} protocol allows the clients to identify themselves using a
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{www} software, usually for statistical purposes or for tracing of
./SAVANNAH-crawl/wget/doc/wget.texi:not to send the @code{User-Agent} header in @sc{http} requests.
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp} server. Without this, or the corresponding startup option,
./SAVANNAH-crawl/wget/doc/wget.texi:Another way to specify username and password is in the @sc{url} itself
./SAVANNAH-crawl/wget/doc/wget.texi:Don't remove the temporary @file{.listing} files generated by @sc{ftp}
./SAVANNAH-crawl/wget/doc/wget.texi:received from @sc{ftp} servers. Not removing them can be useful for
./SAVANNAH-crawl/wget/doc/wget.texi:Turn off @sc{ftp} globbing. Globbing refers to the use of shell-like
./SAVANNAH-crawl/wget/doc/wget.texi:By default, globbing will be turned on if the @sc{url} contains a
./SAVANNAH-crawl/wget/doc/wget.texi:You may have to quote the @sc{url} to protect it from being expanded by
./SAVANNAH-crawl/wget/doc/wget.texi:system-specific. This is why it currently works only with Unix @sc{ftp}
./SAVANNAH-crawl/wget/doc/wget.texi:By default, when retrieving @sc{ftp} directories recursively and a symbolic link
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{.listing} file.
./SAVANNAH-crawl/wget/doc/wget.texi:@samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:and @samp{-l}. To download the essential items to view a single @sc{html} page, see @samp{page requisites}.
./SAVANNAH-crawl/wget/doc/wget.texi:such as embedded images, links to style sheets, hyperlinks to non-@sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:and time-stamping, sets infinite recursion depth and keeps @sc{ftp}
./SAVANNAH-crawl/wget/doc/wget.texi:properly display a given @sc{html} page. This includes such things as
./SAVANNAH-crawl/wget/doc/wget.texi:Ordinarily, when downloading a single @sc{html} page, any requisite documents
./SAVANNAH-crawl/wget/doc/wget.texi:@samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:@samp{-i} @sc{url} input file) and its (or their) requisites, simply leave off
./SAVANNAH-crawl/wget/doc/wget.texi:@cindex @sc{html} comments
./SAVANNAH-crawl/wget/doc/wget.texi:@cindex comments, @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:Turn on strict parsing of @sc{html} comments. The default is to terminate
./SAVANNAH-crawl/wget/doc/wget.texi:According to specifications, @sc{html} comments are expressed as @sc{sgml}
./SAVANNAH-crawl/wget/doc/wget.texi:may contain comments between a pair of @samp{--} delimiters. @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:comments are ``empty declarations'', @sc{sgml} declarations without any
./SAVANNAH-crawl/wget/doc/wget.texi:On the other hand, most @sc{html} writers don't perceive comments as anything
./SAVANNAH-crawl/wget/doc/wget.texi:Follow @sc{ftp} links from @sc{html} documents. Without this option,
./SAVANNAH-crawl/wget/doc/wget.texi:Wget will ignore all the @sc{ftp} links.
./SAVANNAH-crawl/wget/doc/wget.texi:Wget has an internal table of @sc{html} tag / attribute pairs that it
./SAVANNAH-crawl/wget/doc/wget.texi:certain @sc{html} tags when recursively looking for documents to download,
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{http} or @sc{ftp} server), following links and directory structure.
./SAVANNAH-crawl/wget/doc/wget.texi:With @sc{http} @sc{url}s, Wget retrieves and parses the @sc{html} or
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{css} from the given @sc{url}, retrieving the files the document
./SAVANNAH-crawl/wget/doc/wget.texi:refers to, through markup like @code{href} or @code{src}, or @sc{css}
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{uri} values specified using the @samp{url()} functional notation.
./SAVANNAH-crawl/wget/doc/wget.texi:Recursive retrieval of @sc{http} and @sc{html}/@sc{css} content is
./SAVANNAH-crawl/wget/doc/wget.texi:When retrieving an @sc{ftp} @sc{url} recursively, Wget will retrieve all
./SAVANNAH-crawl/wget/doc/wget.texi:locally. @sc{ftp} retrieval is also limited by the @code{depth}
./SAVANNAH-crawl/wget/doc/wget.texi:parameter. Unlike @sc{http} recursion, @sc{ftp} recursion is performed
./SAVANNAH-crawl/wget/doc/wget.texi:important of which is mirroring. It is also useful for @sc{www}
./SAVANNAH-crawl/wget/doc/wget.texi:three servers. Maybe the server has two equivalent names, and the @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:interested in downloading @sc{gif}s, you will not be overjoyed to get
./SAVANNAH-crawl/wget/doc/wget.texi:files ending with @samp{gif} or @samp{jpg}, i.e. @sc{gif}s and
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{jpeg}s. On the other hand, @samp{wget -A "zelazny*196[0-9]*"} will
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{mpeg}s and @sc{.au} files, you can use @samp{wget -R mpg,mpeg,au}.
./SAVANNAH-crawl/wget/doc/wget.texi:Note that these two options do not affect the downloading of @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:The rules for @sc{ftp} are somewhat specific, as it is necessary for
./SAVANNAH-crawl/wget/doc/wget.texi:them to be. @sc{ftp} links in @sc{html} documents are often included
./SAVANNAH-crawl/wget/doc/wget.texi:To have @sc{ftp} links followed from @sc{html} documents, you need to
./SAVANNAH-crawl/wget/doc/wget.texi:specify the @samp{--follow-ftp} option. Having done that, @sc{ftp}
./SAVANNAH-crawl/wget/doc/wget.texi:as @sc{ftp} links rarely point to the same host where the @sc{http}
./SAVANNAH-crawl/wget/doc/wget.texi:Also note that followed links to @sc{ftp} directories will not be
./SAVANNAH-crawl/wget/doc/wget.texi:without @samp{-N} (at least for @sc{http}).
./SAVANNAH-crawl/wget/doc/wget.texi:The same goes for @sc{ftp}. For example:
./SAVANNAH-crawl/wget/doc/wget.texi:gives a timestamp. For @sc{http}, this depends on getting a
./SAVANNAH-crawl/wget/doc/wget.texi:@code{Last-Modified} header. For @sc{ftp}, this depends on getting a
./SAVANNAH-crawl/wget/doc/wget.texi:Time-stamping in @sc{http} is implemented by checking of the
./SAVANNAH-crawl/wget/doc/wget.texi:@file{foo.html} through @sc{http}, Wget will check whether
./SAVANNAH-crawl/wget/doc/wget.texi:Arguably, @sc{http} time-stamping should be implemented using the
./SAVANNAH-crawl/wget/doc/wget.texi:In theory, @sc{ftp} time-stamping works much the same as @sc{http}, only
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp} has no headers---time-stamps must be ferreted out of directory
./SAVANNAH-crawl/wget/doc/wget.texi:If an @sc{ftp} download is recursive or uses globbing, Wget will use the
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp} @code{LIST} command to get a file listing for the directory
./SAVANNAH-crawl/wget/doc/wget.texi:The rest is exactly the same as for @sc{http}. Note that when
./SAVANNAH-crawl/wget/doc/wget.texi:retrieving individual files from an @sc{ftp} server without using
./SAVANNAH-crawl/wget/doc/wget.texi:non-Unix @sc{ftp} servers use the Unixoid listing format because most
./SAVANNAH-crawl/wget/doc/wget.texi:(all?) of the clients understand it. Bear in mind that @sc{rfc959}
./SAVANNAH-crawl/wget/doc/wget.texi:that is supported by some @sc{ftp} servers (including the popular
./SAVANNAH-crawl/wget/doc/wget.texi:Consider relative @sc{url}s in input files (specified via the
./SAVANNAH-crawl/wget/doc/wget.texi:Follow @sc{ftp} links from @sc{html} documents---the same as
./SAVANNAH-crawl/wget/doc/wget.texi:Only follow certain @sc{html} tags when doing a recursive retrieval,
./SAVANNAH-crawl/wget/doc/wget.texi:If set to on, force the input filename to be regarded as an @sc{html}
./SAVANNAH-crawl/wget/doc/wget.texi:Set your @sc{ftp} password to @var{string}. Without this setting, the
./SAVANNAH-crawl/wget/doc/wget.texi:anonymous @sc{ftp} access.
./SAVANNAH-crawl/wget/doc/wget.texi:Use @var{string} as @sc{ftp} proxy, instead of the one specified in
./SAVANNAH-crawl/wget/doc/wget.texi:Set @sc{ftp} user to @var{string}.
./SAVANNAH-crawl/wget/doc/wget.texi:Set @sc{http} password, equivalent to
./SAVANNAH-crawl/wget/doc/wget.texi:Use @var{string} as @sc{http} proxy, instead of the one specified in
./SAVANNAH-crawl/wget/doc/wget.texi:Set @sc{http} user to @var{string}, equivalent to
./SAVANNAH-crawl/wget/doc/wget.texi:Use @var{string} as @sc{https} proxy, instead of the one specified in
./SAVANNAH-crawl/wget/doc/wget.texi:Ignore certain @sc{html} tags when doing a recursive retrieval, like
./SAVANNAH-crawl/wget/doc/wget.texi:Read the @sc{url}s from @var{string}, like @samp{-i @var{file}}.
./SAVANNAH-crawl/wget/doc/wget.texi:Download all ancillary documents necessary for a single @sc{html} page to
./SAVANNAH-crawl/wget/doc/wget.texi:Change setting of passive @sc{ftp}, equivalent to the
./SAVANNAH-crawl/wget/doc/wget.texi:Specify password @var{string} for both @sc{ftp} and @sc{http} file retrieval.
./SAVANNAH-crawl/wget/doc/wget.texi:@samp{http_password} command for @sc{ftp} and @sc{http} respectively.
./SAVANNAH-crawl/wget/doc/wget.texi:the @sc{http} spec who got the spelling of ``referrer'' wrong.)
./SAVANNAH-crawl/wget/doc/wget.texi:If set to on, remove @sc{ftp} listings downloaded by Wget. Setting it
./SAVANNAH-crawl/wget/doc/wget.texi:Choose whether or not to print the @sc{http} and @sc{ftp} server
./SAVANNAH-crawl/wget/doc/wget.texi:Set number of retries per @sc{url}---the same as @samp{-t @var{n}}.
./SAVANNAH-crawl/wget/doc/wget.texi:Specify username @var{string} for both @sc{ftp} and @sc{http} file retrieval.
./SAVANNAH-crawl/wget/doc/wget.texi:@samp{http_user} command for @sc{ftp} and @sc{http} respectively.
./SAVANNAH-crawl/wget/doc/wget.texi:Say you want to download a @sc{url}. Just type:
./SAVANNAH-crawl/wget/doc/wget.texi:The usage of @sc{ftp} is as simple. Wget will take care of login and
./SAVANNAH-crawl/wget/doc/wget.texi:parse it and convert it to @sc{html}. Try:
./SAVANNAH-crawl/wget/doc/wget.texi:If you specify @samp{-} as file name, the @sc{url}s will be read from
./SAVANNAH-crawl/wget/doc/wget.texi:Retrieve only one @sc{html} page, but make sure that all the elements needed
./SAVANNAH-crawl/wget/doc/wget.texi:The @sc{html} page will be saved to @file{www.example.com/dir/page.html}, and
./SAVANNAH-crawl/wget/doc/wget.texi:You want to download all the @sc{gif}s from a directory on an @sc{http}
./SAVANNAH-crawl/wget/doc/wget.texi:didn't work because @sc{http} retrieval does not support globbing. In
./SAVANNAH-crawl/wget/doc/wget.texi:download only the @sc{gif} files. @samp{-A "*.gif"} would have worked
./SAVANNAH-crawl/wget/doc/wget.texi:If you want to encode your own username and password to @sc{http} or
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{ftp}, use the appropriate @sc{url} syntax (@pxref{URL Format}).
./SAVANNAH-crawl/wget/doc/wget.texi:If you wish Wget to keep a mirror of a page (or @sc{ftp}
./SAVANNAH-crawl/wget/doc/wget.texi:back up the original @sc{html} files before the conversion. Wget invocation
./SAVANNAH-crawl/wget/doc/wget.texi:when @sc{html} files are saved under extensions other than @samp{.html},
./SAVANNAH-crawl/wget/doc/wget.texi:@dfn{Proxies} are special-purpose @sc{http} servers designed to transfer
./SAVANNAH-crawl/wget/doc/wget.texi:achieved by channeling all @sc{http} and @sc{ftp} requests through the
./SAVANNAH-crawl/wget/doc/wget.texi:Wget supports proxies for both @sc{http} and @sc{ftp} retrievals. The
./SAVANNAH-crawl/wget/doc/wget.texi:contain the @sc{url}s of the proxies for @sc{http} and @sc{https}
./SAVANNAH-crawl/wget/doc/wget.texi:This variable should contain the @sc{url} of the proxy for @sc{ftp}
./SAVANNAH-crawl/wget/doc/wget.texi:@env{ftp_proxy} are set to the same @sc{url}.
./SAVANNAH-crawl/wget/doc/wget.texi:be sent by Wget. As with @sc{http} authorization, several
./SAVANNAH-crawl/wget/doc/wget.texi:@sc{url} or through the command-line options. Assuming that the
./SAVANNAH-crawl/wget/doc/wget.texi:proxy @sc{url} location containing authorization data might look like
./SAVANNAH-crawl/wget/doc/wget.texi:section handled by a CGI Perl script that converts Info files to @sc{html} on
./SAVANNAH-crawl/wget/doc/wget.texi:an @sc{rfc}, is available at
./SAVANNAH-crawl/wget/doc/wget.texi:way around it is to use @code{wget -i -} and feed the @sc{url}s to
./SAVANNAH-crawl/wget/doc/wget.texi:The @sc{ftp} passwords are also in no way encrypted. There is no good
./SAVANNAH-crawl/wget/doc/wget.texi:resources such as the mailing list, web space, @sc{ftp} space, and
./SAVANNAH-crawl/wget/doc/wget.texi:Junio Hamano---donated support for Opie and @sc{http} @code{Digest}
./SAVANNAH-crawl/lightning/doc/body.texi:generator is @sc{dcg}, by Dawson R.@: Engler and T.@: A.@: Proebsting.
./SAVANNAH-crawl/lightning/doc/body.texi:Further work by Dawson R. Engler resulted in the @sc{vcode} system;
./SAVANNAH-crawl/lightning/doc/body.texi:unlike @sc{dcg}, @sc{vcode} used no intermediate representation and
./SAVANNAH-crawl/lightning/doc/body.texi:program @sc{ccg} under the GNU General Public License, thereby allowing
./SAVANNAH-crawl/lightning/doc/body.texi:@lightning{} to use the run-time assemblers he had wrote for @sc{ccg}.
./SAVANNAH-crawl/lightning/doc/body.texi:@sc{ccg} provides a way of dynamically assemble programs written in the
./SAVANNAH-crawl/lightning/doc/lightning.texi:@set TITLE Using @sc{gnu} @i{lightning}
./SAVANNAH-crawl/lightning/doc/lightning.texi:@sc{gnu}
./SAVANNAH-crawl/guile-sdl/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/cflow/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/identica-mode/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/classpath/doc/texi2pod.pl: s/\@sc\{([^\}]*)\}/\U$1/g;
./SAVANNAH-crawl/mediatex/doc/useCase.texi:@sc{Mediatex} should help building a whole @sc{oais} system.
./SAVANNAH-crawl/mediatex/doc/useCase.texi:Archive are now injected. You can browses the icons catalog at this @sc{url}: @*
./SAVANNAH-crawl/mediatex/doc/useCase.texi:A minimal @sc{cakePhp} application is provided with the sources
./SAVANNAH-crawl/mediatex/doc/useCase.texi:showing how to use the @sc{Mediatex} system as a storage layer.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Support} entity lists all the local supports.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Collection} entity lists all the collections the local server belongs to.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Server} entity lists all the servers.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Image} entity lists on @sc{iso} images hold by a server.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Archive} entity lists all archives known at running time.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Containter} entity gives rule to extract archives from each others.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Document} entity groups archives in order to describe them in a catalog.
./SAVANNAH-crawl/mediatex/doc/data.texi:@item The @sc{Record} entity lists archives we works with.
./SAVANNAH-crawl/mediatex/doc/client.texi:@activity{Client} is the front-end for the @sc{Mediatex} system.
./SAVANNAH-crawl/mediatex/doc/exim.texi:@sc{Mediatex} uses @sc{Exim4}
./SAVANNAH-crawl/mediatex/doc/main.texi:@mediatexO{} focus on providing an @sc{api} to ask for, and retrieve
./SAVANNAH-crawl/mediatex/doc/main.texi:The following specifications use the @sc{Merise} conception method.
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{Archive} entity lists all archive's data files.
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{Document} entity groups archives (data, parts, versions time-stamps @dots{}) related to an archived document.
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{Category} entity groups documents by themes (onthology).
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{Human} entity lists humans (using an @acronym{AVL} tree) related to a document.
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{Role} entity lists all titles a human contributing to a document may have (ex: producer, actor, @dots{} for a movie).
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{*_Carac} entities are unidirectional in order to consume less memory.
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{asso_role} relationship matches a human, a role and a document.
./SAVANNAH-crawl/mediatex/doc/catalog.txt.texi:The @sc{contains} relationships matches ether humans or documents to categories, or records to documents.
./SAVANNAH-crawl/mediatex/doc/mount-umount.texi:These 2 scripts mount or un-mount an @sc{iso} disk or file.
./SAVANNAH-crawl/mediatex/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:The @sc{Container} entity lists (using an @acronym{AVL} tree) all the container files from where archives are extracted. A Container is identified by its type (@sc{iso},@sc{tar}...) and the first archive needed for extraction (ex: @file{archive-part1.rar}), also called its first parent. Containers may provide a relative directory path to use when extracting the archive. This allow for instance to extract @sc{tar} container, that handle files on the root, into a directory.
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:@note{} 2 dedicated @sc{Container} instances are used internally by @mediatex{} to manage the incoming (recently uploaded) archives, and where to extract supports into the cache.
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:The @sc{Location} entity lists external ressources (directories).
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:The @sc{Archive} entity lists the archive's data files
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:The @sc{fromAsso} relationship enumerate (using an @acronym{AVL} tree) the content of a container. For instance, all files provided by a tarball archive: @code{tar -tf archive.tar}.
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:@note{} for the incoming @sc{Container} instance, the @sc{fromAsso} relationship gives the date the archive was uploaded.
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:The @sc{parents} relationship gives all the parts a container is using to perform extraction. (@file{archive-part1.rar}, @dots{}, @file{archive-part@var{N}.rar}).
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:The @sc{toContainer} relationship gives the container object an Archive may provides.
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:@note{} we can only have on containers for an archive: in the case of a compressed tarball for instance, we have to choose between the two possibilities (@sc{tar}+@sc{gz} or @sc{tgz}).
./SAVANNAH-crawl/mediatex/doc/extract.txt.texi:The @sc{fromLocation} relationship gives files accessible by the collection user from the location directory. These ``located files'' are not true archives ; they still may be uploaded as ``archives'' later.
./SAVANNAH-crawl/mediatex/doc/syslog.texi:@process{syslog} (actually @sc{rsyslog}: see @code{man rsyslogd (8)} and @sc{logrorate}: see @code{man logrotate (8)})
./SAVANNAH-crawl/mediatex/doc/misc.texi:@item Build the @sc{html} catalogues.
./SAVANNAH-crawl/mediatex/doc/consistency.texi:@sc{Mediatex} should ease managing server changes.
./SAVANNAH-crawl/mediatex/doc/servers.txt.texi:The @sc{Server} entity lists all the servers participating to a collection.
./SAVANNAH-crawl/mediatex/doc/servers.txt.texi:The @sc{Image} entity lists all the images files known by the collection.
./SAVANNAH-crawl/mediatex/doc/servers.txt.texi:The @sc{Network} entity lists public and private networks we logically defined.
./SAVANNAH-crawl/mediatex/doc/servers.txt.texi:The @sc{Archive} entity reminds all archives the programm is currently using per collection.
./SAVANNAH-crawl/mediatex/doc/servers.txt.texi:The @sc{networks} relationship lists all the networks a server belongs to.
./SAVANNAH-crawl/mediatex/doc/servers.txt.texi:The @sc{gateways} relationship lists all the networks for which a server
./SAVANNAH-crawl/mediatex/doc/server.texi:exchange files with other @sc{Mediatex}'s @activity{Server}s.
./SAVANNAH-crawl/mediatex/doc/apache.texi:@actorUser{} use @sc{Apache} to browse the @acronym{HTML} catalogue and access archives. (For tips, you should maybe read this section first : @pxref{HTTP}).
./SAVANNAH-crawl/mediatex/doc/apache.texi:@sc{Apache} is configured to query the @activityServer{} via the @procScriptsCgi{} @acronym{CGI} script.
./SAVANNAH-crawl/mediatex/doc/apache.texi:The followings @sc{Apache}'s modules are enabled by @sc{Mediatex}:
./SAVANNAH-crawl/mediatex/doc/apache.texi:The @sc{Apache}'s configuration files given bellow are generated by
./SAVANNAH-crawl/mediatex/doc/apache.texi:In current release we use if statement to manage 2.2 and 2.4 @sc{Apache}'s configuration files :
./SAVANNAH-crawl/mediatex/doc/macros.texi:@sc{\label\}
./SAVANNAH-crawl/mediatex/doc/macros.texi:@sc{\label\}
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{Configuration} entity is the single main contexte.
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{Collection} entity lists all the collections shared.
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{Network} entity lists logical networks the local host belongs to.
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{Support} entity lists all the local supports.
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{Server} entity lists all servers sharing a given collection.
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{manage} relationship lists all the collections our local server share.
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{networks} relationship lists all the networks the local host belongs to.
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{gateways} relationship lists all the networks for which our local
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{localhost} relationship gives our local server related to the
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:The @sc{localImages} relationship lists all the supports shared within a
./SAVANNAH-crawl/mediatex/doc/mdtx.conf.texi:@note{} @dataServers{} summerize the @sc{imageFiles}, @sc{networks} and @sc{gateways} relationships from all the hosts sharing a collection.
./SAVANNAH-crawl/mediatex/doc/git.texi:@sc{Git}
./SAVANNAH-crawl/mediatex/doc/mdtx-COLL.md5.texi:@item The @sc{Record} entity lists all informations we need to load/save and exchange about archives.
./SAVANNAH-crawl/mediatex/doc/mdtx-COLL.md5.texi:The @sc{Archive} entity reminds all archives the programm is currently using per collection.
./SAVANNAH-crawl/mediatex/doc/mdtx-COLL.md5.texi:The @sc{Server} entity, from
./SAVANNAH-crawl/mediatex/doc/mdtx-COLL.md5.texi:The @sc{localSupply} relationhip gives the archive's file when available (@code{LOCAL_DEMAND}) on the local cache.
./SAVANNAH-crawl/mediatex/doc/mdtx-COLL.md5.texi:The @sc{finalSupplies} relationhip lists supports presentely available on local host (@code{FINAL_SUPPLY}).
./SAVANNAH-crawl/mediatex/doc/mdtx-COLL.md5.texi:The @sc{remoteSupplies} relationhip lists all archives available remotely (@code{REMOTE_SUPPLY}) from the other @activityServerO{}.
./SAVANNAH-crawl/mediatex/doc/mdtx-COLL.md5.texi:The @sc{demands} relationhip lists all demand (@code{FINAL_DEMAND}, @code{LOCAL_DEMAND} and @code{REMOTE_DEMAND}) for an archive
./SAVANNAH-crawl/mediatex/doc/init-remove-purge.texi:These 3 scripts manage @sc{Mediatex}'s installation (install, remove and purge).
./SAVANNAH-crawl/mediatex/doc/invoking.texi:The goal of this section is to help to install @sc{mediatex} software
./SAVANNAH-crawl/mediatex/doc/invoking.texi:As @sc{Publisher}, please check the ``message of the day''
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@sc{motd} will not complain any more about this support
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@note{} As it works the same way, we are using here @sc{iso} files
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@actorUser{} to the collection's @sc{apache} users.
./SAVANNAH-crawl/mediatex/doc/invoking.texi:Give him permissions on some of the @sc{html} sections by editing
./SAVANNAH-crawl/mediatex/doc/invoking.texi:Browses the remotely available collection's catalog via this @sc{url}: @*
./SAVANNAH-crawl/mediatex/doc/invoking.texi:As a @sc{User}, browse the collection via this @sc{url}:
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@url{https://@/@sc{hostname1}/@/~mdtx-hello} and ask for a content
./SAVANNAH-crawl/mediatex/doc/invoking.texi:As @sc{Publisher}, please check the ``message of the day''
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@sc{Publisher} has to add your key to the collection.
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@var{hostname1}$ mediatex add key @sc{keyFile} to coll hello
./SAVANNAH-crawl/mediatex/doc/invoking.texi:As a @sc{User}, browse the collection on the first server via this @sc{url}:
./SAVANNAH-crawl/mediatex/doc/invoking.texi:When first server reload (scheduled by @sc{cron}),
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@sc{Publisher} on @var{hostname2} is now asked to provide the supports it shares
./SAVANNAH-crawl/mediatex/doc/invoking.texi:Once second server notify, first server will copy back the provided file it will needs, to serve the @sc{User} query.
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@section Scenario 6: add a @sc{nat} server
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@note{} By @sc{nat} we mean this third server should be located
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@var{hostname1}# ping @sc{hostname3} (ko: Destination Host Unreachable)
./SAVANNAH-crawl/mediatex/doc/invoking.texi:server (via @sc{cron}) which will relay them to the third one.
./SAVANNAH-crawl/mediatex/doc/invoking.texi:@sc{Publisher} on @var{hostname3} is now asked
./SAVANNAH-crawl/mediatex/doc/invoking.texi:file and delivers a mail to advice the @sc{User} it becomes available.
./SAVANNAH-crawl/mediatex/doc/supports.txt.texi:@item The @sc{Support} entity list all the local supports.
./SAVANNAH-crawl/mediatex/doc/supports.txt.texi:@item The @sc{Collection} entity, from
./SAVANNAH-crawl/mediatex/doc/supports.txt.texi:The @sc{collections} relationship list all the collection a specific support is shared with. This relation is not recorded into this file but into
./SAVANNAH-crawl/mediatex/doc/overview.texi:to provides an @sc{api} to manage supports (to drive jukeboxes).
./SAVANNAH-crawl/mediatex/doc/overview.texi:Trace-ability is done by @sc{Syslog} for programs
./SAVANNAH-crawl/mediatex/doc/overview.texi:and by @sc{git} for changes in the meta-data.
./SAVANNAH-crawl/mediatex/doc/overview.texi:Access is granted by @sc{Apache}, but when archives need to be retrieved, the
./SAVANNAH-crawl/mediatex/doc/overview.texi:probably use the @sc{Sendmail} interface.
./SAVANNAH-crawl/mediatex/doc/overview.texi:Servers tasks are driven by @sc{Cron}.
./SAVANNAH-crawl/mediatex/doc/overview.texi:via the host's @sc{Motd} (by default).
./SAVANNAH-crawl/mediatex/doc/overview.texi:using @sc{git}.
./SAVANNAH-crawl/mediatex/doc/mediatex.texi:focusing on the archival storage entity define by the @sc{Oais} draft,
./SAVANNAH-crawl/mediatex/doc/mediatex.texi:and on the @sc{NF Z 42-013} requirements.
./SAVANNAH-crawl/mediatex/examples/jukebox/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mediatex/examples/jukebox/doc/macros.texi:@sc{\label\}
./SAVANNAH-crawl/mediatex/examples/jukebox/doc/macros.texi:@sc{\label\}
./SAVANNAH-crawl/mediatex/examples/sso/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/mediatex/examples/sso/doc/macros.texi:@sc{\label\}
./SAVANNAH-crawl/mediatex/examples/sso/doc/macros.texi:@sc{\label\}
./SAVANNAH-crawl/ccrtp/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/dico/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/dico/doc/dico.texi:compatibility with the @sc{c} preprocessor.
./SAVANNAH-crawl/dico/doc/dico.texi:# defdb(@sc{name}[, @sc{descr}])
./SAVANNAH-crawl/dico/doc/dico.texi:# @r{Produce a standard definition for a database @sc{name}}.
./SAVANNAH-crawl/dico/doc/dico.texi:# @r{If @sc{descr} is given, use it as a description}.
./SAVANNAH-crawl/dico/doc/dico.texi:It takes two arguments. The first one, @sc{name}, defines the dictionary
./SAVANNAH-crawl/gnulib/doc/make-stds.texi:@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf,
./SAVANNAH-crawl/gnulib/doc/make-stds.texi:shell and the @sc{posix} shell), not @code{csh}. Don't use any
./SAVANNAH-crawl/gnulib/doc/make-stds.texi:special features of @code{ksh} or @code{bash}, or @sc{posix} features
./SAVANNAH-crawl/gnulib/doc/make-stds.texi:@sc{posix}-specified) options and features of these programs. For
./SAVANNAH-crawl/libtool/doc/notes.texi:@c FreeBSD @command{make} does not conform to @sc{posix} in its handling
./SAVANNAH-crawl/libtool/ChangeLog.old: * doc/libtool.texi: Remove all usage of @sc.
./SAVANNAH-crawl/rottlog/doc/doclicense.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Christian Schindelhauer}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Adam Barnett} and @sc{Nigel P. Smart}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Jens Groth}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Jens Groth}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Sebastiaan de Hoogh}, @sc{Berry Schoenmakers}, @sc{Boris Skoric}, and @sc{Jose Villegas}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Heiko Stamer}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Heiko Stamer}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Amos Fiat} and @sc{Adi Shamir}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Mihir Bellare} and @sc{Phillip Rogaway}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Mihir Bellare} and @sc{Phillip Rogaway}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Dan Boneh}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Rosario Gennaro}, @sc{Daniele Micciancio}, and @sc{Tal Rabin}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Stanislaw Jarecki} and @sc{Anna Lysyanskaya}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Christian Cachin}, @sc{Klaus Kursawe}, @sc{Frank Petzold}, and @sc{Victor Shoup}.
./SAVANNAH-crawl/libtmcg/doc/libTMCG.texi: @sc{Christian Cachin}, @sc{Rachid Guerraoui}, and @sc{Luis Rodrigues}.
./SAVANNAH-crawl/pdf/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:@sc{LETTER DZ WITH CARON} comes in three forms:
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:@sc{LATIN CAPITAL LETTER DZ WITH CARON} (DZ),
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:@sc{LATIN CAPITAL LETTER D WITH SMALL LETTER Z WITH CARON} (Dz),
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:@sc{LATIN SMALL LETTER DZ WITH CARON} (dz).
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:is not true for German, where the @sc{LATIN SMALL LETTER SHARP S}, when
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:This is not true for the Greek sigma: @sc{GREEK CAPITAL LETTER SIGMA} is
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:the uppercase of both @sc{GREEK SMALL LETTER SIGMA} and
./SAVANNAH-crawl/libunistring/doc/libunistring.texi:@sc{GREEK SMALL LETTER FINAL SIGMA}.
./SAVANNAH-crawl/libunistring/doc/unicase.texi:@sc{LETTER DZ WITH CARON}, the German @sc{LATIN SMALL LETTER SHARP S}, the
./SAVANNAH-crawl/libunistring/doc/unicase.texi:a character, U+00C4 @sc{LATIN CAPITAL LETTER A WITH DIAERESIS} and
./SAVANNAH-crawl/libunistring/doc/unicase.texi:U+0041 @sc{LATIN CAPITAL LETTER A} U+0308 @sc{COMBINING DIAERESIS} the same.
./SAVANNAH-crawl/libunistring/doc/unigbrk.texi:character U+00E8 @sc{LATIN SMALL LETTER E WITH ACUTE}. It is,
./SAVANNAH-crawl/libunistring/doc/unigbrk.texi:however, equally valid to use the pair of characters U+0065 @sc{LATIN
./SAVANNAH-crawl/libunistring/doc/unigbrk.texi:SMALL LETTER E} followed by U+0301 @sc{COMBINING ACUTE ACCENT}. Since
./SAVANNAH-crawl/thales/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/gnu-social-mode/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./SAVANNAH-crawl/guile-baux/doc/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./make/make.texi:Program to make @TeX{} @sc{dvi} files from @TeX{} source;
./make/make.texi:Program to make @TeX{} @sc{dvi} files from Texinfo source;
./make/make-stds.texi:@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf,
./make/make-stds.texi:shell and the @sc{posix} shell), not @code{csh}. Don't use any
./make/make-stds.texi:special features of @code{ksh} or @code{bash}, or @sc{posix} features
./make/make-stds.texi:@sc{posix}-specified) options and features of these programs. For
./guile/api-regex.texi:Or matching a @sc{yyyymmdd} format date such as @samp{20020828} and
./guile/api-data.texi:Return the bitwise @sc{and} of the integer arguments.
./guile/api-data.texi:Return the bitwise @sc{or} of the integer arguments.
./guile/api-data.texi:Return the bitwise @sc{xor} of the integer arguments. A bit is
./guile/api-data.texi:common @sc{unix} command of the same name.
./guile/srfi-modules.texi:Return two values, the @sc{car} and the @sc{cdr} of @var{pair}.
./guile/srfi-modules.texi:Return the first pair of @var{lst} whose @sc{car} satisfies the
./guile/srfi-modules.texi:Return the first sublist of @var{lst} whose @sc{car} is equal to
./guile/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./guile/texinfo.texi:The returned index is a list of pairs, the @sc{car} of which is the
./guile/texinfo.texi:entry (a string) and the @sc{cdr} of which is a node name (a string).
./guile/data-rep.texi:the @sc{car} and @sc{cdr}. Is there any way to represent pairs using
./guile/api-binding.texi:@sc{Algol 60}. Readers familiar to languages like C or Java should
./gst-base/gst-libs.texi:@sc{gnu} Smalltalk
./gst-base/gst-libs.texi:@sc{gnu}
./gst-base/gst-libs.texi:@title @sc{gnu} Smalltalk Library Reference
./gst-base/gst-base.texi:@sc{gnu} Smalltalk
./gst-base/gst-base.texi:@sc{gnu}
./gst-base/gst-base.texi:@title @sc{gnu} Smalltalk Library Reference
./gst-base/gst.texi:@sc{gnu} Smalltalk
./gst-base/gst.texi:@sc{gnu}
./gst-base/gst.texi:@title @sc{gnu} Smalltalk User's Guide
./gst-base/gst.texi:languages}. Therefore, even though we have a @sc{gui} environment based
./gst-base/gst.texi:@multitable {@option{--verbose -aq -c}} {Options seen by @sc{gnu} Smalltalk} {@code{Smalltalk arguments}}
./gst-base/gst.texi:operations to @code{stdout}. If you load the VisualGST @sc{gui}, instead,
./gst-base/gst.texi:@gst{} inherits from @sc{iso} C the concept of a @dfn{locale}, that is, a
./gst-base/gst.texi:Format a monetary value together with its @sc{iso} currency symbol.
./gst-base/gst.texi:@sc{mo} file format adopted by the @gnu{} @code{gettext} library.
./gst-base/gst.texi:engine which is now superseded by Swazoo. It is based on the @sc{gpl}'ed
./gst-base/gst.texi:authentication support, virtual hosting, and @sc{http} 1.1 compliance.
./gst-base/gst.texi:@gst{} includes an almost complete abstraction of the @sc{tcp}, @sc{udp}
./gst-base/gst.texi:and @sc{ip} protocols. Although based on the standard @sc{bsd} sockets,
./gst-base/gst.texi:@sc{ftp}, @sc{http}, @sc{nntp}, @sc{smtp}, @sc{pop3} and @sc{imap}.
./gst-base/gst.texi:The @sc{xml} parser library for Smalltalk, loaded as package @code{XML}
./gst-base/gst.texi:includes a validating @sc{xml} parser and Document Object Model.
./gst-base/gst.texi:and a @sc{xslr} interpreter based on it is bundled with @gst{} as
./gst-base/gst.texi:@item @sc{gdbm}
./gst-base/gst.texi:with the library at run-time using @sc{dld}, using either
./gst-base/gst.texi:run-time; but since some@footnote{The most notable are @sc{aix} and
./gst-base/tutorial.texi: @gst{} supports completion in the same way as Bash or @sc{gdb}.
./autobuild/htmlfontify.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
./mailutils/libmu_sieve.texi:@code{mu_sieve_machine_add_destructor()} are executed in @sc{lifo}
./mailutils/libmu_auth.texi:information about a user from several places, like @sc{sql} database,
./mailutils/getdate.texi:This section describes the textual date representations that @sc{gnu}
./mailutils/getdate.texi:* Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
./mailutils/getdate.texi:1972-09-24 # @sc{iso} 8601.
./mailutils/getdate.texi:@cindex @sc{iso} 8601 date format
./mailutils/getdate.texi:@cindex date format, @sc{iso} 8601
./mailutils/getdate.texi:For numeric months, the @sc{iso} 8601 format
./mailutils/getdate.texi:20:02-0500 # In @sc{est} (U.S. Eastern Standard Time).
./mailutils/getdate.texi:Coordinated Universal Time (@sc{utc}), overriding any previous
./mailutils/getdate.texi:ahead of @sc{utc} (e.g., India).
./mailutils/getdate.texi:@acronym{POSIX} systems, the epoch is 1970-01-01 00:00:00 @sc{utc}, so
./mailutils/getdate.texi:00:00:01 @sc{utc}, and so forth. @acronym{GNU} and most other
./mailutils/getdate.texi:represents 1969-12-31 23:59:59 @sc{utc}.
./mailutils/getdate.texi:2038-01-19 03:14:07 @sc{utc}. More modern systems use 64-bit counts
./mailutils/getdate.texi:23:59:59 @sc{utc}, @samp{@@915148800} represents 1999-01-01 00:00:00
./mailutils/getdate.texi:@sc{utc}, and there is no way to represent the intervening leap second
./mailutils/getdate.texi:1998-12-31 23:59:60 @sc{utc}.
./mailutils/getdate.texi:revisions for the @sc{gnu} system were made by David MacKenzie, Jim Meyering,
./mailutils/mailutils.texi:* Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
./mailutils/sieve.texi:It treats uppercase and lowercase characters in the @sc{ascii} subset of
./mailutils/sieve.texi:@sc{utf-8} as the same. This is the default comparator.
./mailutils/sieve.texi:Treats the two arguments as @sc{ascii} representation of decimal
./mailutils/sieve.texi:The @code{envelope} test is true if the specified part of the @sc{smtp}
./mailutils/sieve.texi:@emph{Notice}, that due to the limitations imposed by @sc{smtp} envelope
./mailutils/sieve.texi:@sc{unix}. The address on the SMTP envelope is replaced with the one on
./mailutils/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./bison/bison.texi:``Reverse Polish @sc{calc}ulator''). Bison produces a parser
./ccd2cue/philosophy/gnu-free-documentation-license.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./gst/gst-libs.texi:@sc{gnu} Smalltalk
./gst/gst-libs.texi:@sc{gnu}
./gst/gst-libs.texi:@title @sc{gnu} Smalltalk Library Reference
./gst/gst-base.texi:@sc{gnu} Smalltalk
./gst/gst-base.texi:@sc{gnu}
./gst/gst-base.texi:@title @sc{gnu} Smalltalk Library Reference
./gst/gst.texi:@sc{gnu} Smalltalk
./gst/gst.texi:@sc{gnu}
./gst/gst.texi:@title @sc{gnu} Smalltalk User's Guide
./gst/gst.texi:languages}. Therefore, even though we have a @sc{gui} environment based
./gst/gst.texi:@multitable {@option{--verbose -aq -c}} {Options seen by @sc{gnu} Smalltalk} {@code{Smalltalk arguments}}
./gst/gst.texi:operations to @code{stdout}. If you load the VisualGST @sc{gui}, instead,
./gst/gst.texi:@gst{} inherits from @sc{iso} C the concept of a @dfn{locale}, that is, a
./gst/gst.texi:Format a monetary value together with its @sc{iso} currency symbol.
./gst/gst.texi:@sc{mo} file format adopted by the @gnu{} @code{gettext} library.
./gst/gst.texi:engine which is now superseded by Swazoo. It is based on the @sc{gpl}'ed
./gst/gst.texi:authentication support, virtual hosting, and @sc{http} 1.1 compliance.
./gst/gst.texi:@gst{} includes an almost complete abstraction of the @sc{tcp}, @sc{udp}
./gst/gst.texi:and @sc{ip} protocols. Although based on the standard @sc{bsd} sockets,
./gst/gst.texi:@sc{ftp}, @sc{http}, @sc{nntp}, @sc{smtp}, @sc{pop3} and @sc{imap}.
./gst/gst.texi:The @sc{xml} parser library for Smalltalk, loaded as package @code{XML}
./gst/gst.texi:includes a validating @sc{xml} parser and Document Object Model.
./gst/gst.texi:and a @sc{xslr} interpreter based on it is bundled with @gst{} as
./gst/gst.texi:@item @sc{gdbm}
./gst/gst.texi:with the library at run-time using @sc{dld}, using either
./gst/gst.texi:run-time; but since some@footnote{The most notable are @sc{aix} and
./gst/tutorial.texi: @gst{} supports completion in the same way as Bash or @sc{gdb}.
./gnugo/copying.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./pspp/pspp.texi:@sc{pspp}
./pspp/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./haploid/fdl-1.3.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./aris/aris.texi:A connective is a logical symbol that connects one or more sentences. The connectives used in system @sc{psi} are conjuction (@samp{^}), disjunction (@samp{v}), negation, (@samp{~}), conditional (@samp{@arrow{}}), and biconditional (@samp{<->}). In addition, system @sc{psi} recognizes the one-place connectives of the tautology (@samp{T}) and the contradiction (@samp{!}).
./aris/aris.texi:A quantifier is a type of logical symbol that claims something about the amount, or quantity, of an object that holds a specific property. The quantifiers used in system @sc{psi} are the universal (@samp{V}), and the existential (@samp{3}).
./autoconf/make-stds.texi:@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf,
./autoconf/make-stds.texi:shell and the @sc{posix} shell), not @code{csh}. Don't use any
./autoconf/make-stds.texi:special features of @code{ksh} or @code{bash}, or @sc{posix} features
./autoconf/make-stds.texi:@sc{posix}-specified) options and features of these programs. For
./grub-dev/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./grub-dev/grub.texi:@item Detect all installed @sc{ram}
./grub-dev/grub.texi:GRUB can generally find all the installed @sc{ram} on a PC-compatible
./grub-dev/grub.texi:@sc{pc} slice number in the BSD terminology). The partition numbers are
./grub-dev/grub.texi:This means the BSD @samp{a} partition on first @sc{pc} slice number
./grub-dev/grub.texi:as @sc{gnu}), invoke the program @command{grub-install} (@pxref{Invoking
./LibreDWG/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./wget/wget.texi:the Web. It supports @sc{http}, @sc{https}, and @sc{ftp} protocols, as
./wget/wget.texi:well as retrieval through @sc{http} proxies.
./wget/wget.texi:Wget can follow links in @sc{html}, @sc{xhtml}, and @sc{css} pages, to
./wget/wget.texi:available when retrieving via @sc{ftp}. Wget can read the time-stamp
./wget/wget.texi:information given by both @sc{http} and @sc{ftp} servers, and store it
./wget/wget.texi:makes Wget suitable for mirroring of @sc{ftp} sites, as well as home
./wget/wget.texi:@sc{ftp} downloading by default, active @sc{ftp} being an option.
./wget/wget.texi:Wget will simply download all the @sc{url}s specified on the command
./wget/wget.texi:available via the Internet. Wget recognizes the @sc{url} syntax as per
./wget/wget.texi:@sc{rfc1738}. This is the most widely used form (square brackets denote
./wget/wget.texi:You can also encode your username and password within a @sc{url}:
./wget/wget.texi:leave out either the @sc{http} username or password, no authentication
./wget/wget.texi:will be sent. If you leave out the @sc{ftp} username, @samp{anonymous}
./wget/wget.texi:will be used. If you leave out the @sc{ftp} password, your email
./wget/wget.texi:@strong{Important Note}: if you specify a password-containing @sc{url}
./wget/wget.texi:and feed the @sc{url}s to Wget's standard input, each on a separate
./wget/wget.texi:You can encode unsafe characters in a @sc{url} as @samp{%xy}, @code{xy}
./wget/wget.texi:being the hexadecimal representation of the character's @sc{ascii}
./wget/wget.texi:@samp{%40}). Refer to @sc{rfc1738} for a comprehensive list of unsafe
./wget/wget.texi:Wget also supports the @code{type} feature for @sc{ftp} @sc{url}s. By
./wget/wget.texi:default, @sc{ftp} documents are retrieved in the binary mode (type
./wget/wget.texi:Two alternative variants of @sc{url} specification are also supported,
./wget/wget.texi:@sc{ftp}-only syntax (supported by @code{NcFTP}):
./wget/wget.texi:@sc{http}-only syntax (introduced by @code{Netscape}):
./wget/wget.texi:@sc{url} @samp{-x}, reporting failure to @file{log}:
./wget/wget.texi:Read @sc{url}s from a local or external @var{file}. If @samp{-} is
./wget/wget.texi:specified as @var{file}, @sc{url}s are read from the standard input.
./wget/wget.texi:If this function is used, no @sc{url}s need be present on the command
./wget/wget.texi:line. If there are @sc{url}s both on the command line and in an input
./wget/wget.texi:When input is read from a file, force it to be treated as an @sc{html}
./wget/wget.texi:@sc{html} files on your local disk, by adding @code{} to @sc{html}, or using the @samp{--base} command-line
./wget/wget.texi:a server describing it as @sc{html}). This is equivalent to the
./wget/wget.texi:presence of a @code{BASE} tag in the @sc{html} input file, with
./wget/wget.texi:@samp{-c} is if you have a lame @sc{http} proxy that inserts a
./wget/wget.texi:Note that @samp{-c} only works with @sc{ftp} servers and with @sc{http}
./wget/wget.texi:The ``bar'' indicator is used by default. It draws an @sc{ascii} progress
./wget/wget.texi:Print the headers sent by @sc{http} servers and responses sent by
./wget/wget.texi:@sc{ftp} servers.
./wget/wget.texi:@sc{url}s are specified on the command-line. The quota is checked only
./wget/wget.texi:those in the @sc{ascii} range of values.
./wget/wget.texi:are outside the range of @sc{ascii} characters (that is, greater than
./wget/wget.texi:@sc{ftp} and @sc{http} file retrieval. These parameters can be overridden
./wget/wget.texi:@sc{ftp} connections and the @samp{--http-user} and @samp{--http-password}
./wget/wget.texi:options for @sc{http} connections.
./wget/wget.texi:how Wget converts URLs specified as arguments from locale to @sc{utf-8} for
./wget/wget.texi:environment variable to get the locale. If it fails, @sc{ascii} is used.
./wget/wget.texi:to @sc{utf-8} during a recursive fetch. This options is only useful for
./wget/wget.texi:IRI support, for the interpretation of non-@sc{ascii} characters.
./wget/wget.texi:@sc{http} server. According to the type of the challenge, Wget will
./wget/wget.texi:Another way to specify username and password is in the @sc{url} itself
./wget/wget.texi:process typically works by the web server issuing an @sc{http} cookie
./wget/wget.texi:Unfortunately, some @sc{http} servers (@sc{cgi} programs, to be more
./wget/wget.texi:@sc{http} request. The supplied header is sent as-is, which means it
./wget/wget.texi:Save the headers sent by the @sc{http} server to the file, preceding the
./wget/wget.texi:Identify as @var{agent-string} to the @sc{http} server.
./wget/wget.texi:The @sc{http} protocol allows the clients to identify themselves using a
./wget/wget.texi:@sc{www} software, usually for statistical purposes or for tracing of
./wget/wget.texi:not to send the @code{User-Agent} header in @sc{http} requests.
./wget/wget.texi:@sc{ftp} server. Without this, or the corresponding startup option,
./wget/wget.texi:Another way to specify username and password is in the @sc{url} itself
./wget/wget.texi:Don't remove the temporary @file{.listing} files generated by @sc{ftp}
./wget/wget.texi:received from @sc{ftp} servers. Not removing them can be useful for
./wget/wget.texi:Turn off @sc{ftp} globbing. Globbing refers to the use of shell-like
./wget/wget.texi:By default, globbing will be turned on if the @sc{url} contains a
./wget/wget.texi:You may have to quote the @sc{url} to protect it from being expanded by
./wget/wget.texi:system-specific. This is why it currently works only with Unix @sc{ftp}
./wget/wget.texi:By default, when retrieving @sc{ftp} directories recursively and a symbolic link
./wget/wget.texi:@sc{.listing} file.
./wget/wget.texi:@samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
./wget/wget.texi:and @samp{-l}. To download the essential items to view a single @sc{html} page, see @samp{page requisites}.
./wget/wget.texi:such as embedded images, links to style sheets, hyperlinks to non-@sc{html}
./wget/wget.texi:and time-stamping, sets infinite recursion depth and keeps @sc{ftp}
./wget/wget.texi:properly display a given @sc{html} page. This includes such things as
./wget/wget.texi:Ordinarily, when downloading a single @sc{html} page, any requisite documents
./wget/wget.texi:@samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
./wget/wget.texi:@samp{-i} @sc{url} input file) and its (or their) requisites, simply leave off
./wget/wget.texi:@cindex @sc{html} comments
./wget/wget.texi:@cindex comments, @sc{html}
./wget/wget.texi:Turn on strict parsing of @sc{html} comments. The default is to terminate
./wget/wget.texi:According to specifications, @sc{html} comments are expressed as @sc{sgml}
./wget/wget.texi:may contain comments between a pair of @samp{--} delimiters. @sc{html}
./wget/wget.texi:comments are ``empty declarations'', @sc{sgml} declarations without any
./wget/wget.texi:On the other hand, most @sc{html} writers don't perceive comments as anything
./wget/wget.texi:Follow @sc{ftp} links from @sc{html} documents. Without this option,
./wget/wget.texi:Wget will ignore all the @sc{ftp} links.
./wget/wget.texi:Wget has an internal table of @sc{html} tag / attribute pairs that it
./wget/wget.texi:certain @sc{html} tags when recursively looking for documents to download,
./wget/wget.texi:@sc{http} or @sc{ftp} server), following links and directory structure.
./wget/wget.texi:With @sc{http} @sc{url}s, Wget retrieves and parses the @sc{html} or
./wget/wget.texi:@sc{css} from the given @sc{url}, retrieving the files the document
./wget/wget.texi:refers to, through markup like @code{href} or @code{src}, or @sc{css}
./wget/wget.texi:@sc{uri} values specified using the @samp{url()} functional notation.
./wget/wget.texi:Recursive retrieval of @sc{http} and @sc{html}/@sc{css} content is
./wget/wget.texi:When retrieving an @sc{ftp} @sc{url} recursively, Wget will retrieve all
./wget/wget.texi:locally. @sc{ftp} retrieval is also limited by the @code{depth}
./wget/wget.texi:parameter. Unlike @sc{http} recursion, @sc{ftp} recursion is performed
./wget/wget.texi:important of which is mirroring. It is also useful for @sc{www}
./wget/wget.texi:three servers. Maybe the server has two equivalent names, and the @sc{html}
./wget/wget.texi:interested in downloading @sc{gif}s, you will not be overjoyed to get
./wget/wget.texi:files ending with @samp{gif} or @samp{jpg}, i.e. @sc{gif}s and
./wget/wget.texi:@sc{jpeg}s. On the other hand, @samp{wget -A "zelazny*196[0-9]*"} will
./wget/wget.texi:@sc{mpeg}s and @sc{.au} files, you can use @samp{wget -R mpg,mpeg,au}.
./wget/wget.texi:Note that these two options do not affect the downloading of @sc{html}
./wget/wget.texi:The rules for @sc{ftp} are somewhat specific, as it is necessary for
./wget/wget.texi:them to be. @sc{ftp} links in @sc{html} documents are often included
./wget/wget.texi:To have @sc{ftp} links followed from @sc{html} documents, you need to
./wget/wget.texi:specify the @samp{--follow-ftp} option. Having done that, @sc{ftp}
./wget/wget.texi:as @sc{ftp} links rarely point to the same host where the @sc{http}
./wget/wget.texi:Also note that followed links to @sc{ftp} directories will not be
./wget/wget.texi:without @samp{-N} (at least for @sc{http}).
./wget/wget.texi:The same goes for @sc{ftp}. For example:
./wget/wget.texi:gives a timestamp. For @sc{http}, this depends on getting a
./wget/wget.texi:@code{Last-Modified} header. For @sc{ftp}, this depends on getting a
./wget/wget.texi:Time-stamping in @sc{http} is implemented by checking of the
./wget/wget.texi:@file{foo.html} through @sc{http}, Wget will check whether
./wget/wget.texi:Arguably, @sc{http} time-stamping should be implemented using the
./wget/wget.texi:In theory, @sc{ftp} time-stamping works much the same as @sc{http}, only
./wget/wget.texi:@sc{ftp} has no headers---time-stamps must be ferreted out of directory
./wget/wget.texi:If an @sc{ftp} download is recursive or uses globbing, Wget will use the
./wget/wget.texi:@sc{ftp} @code{LIST} command to get a file listing for the directory
./wget/wget.texi:The rest is exactly the same as for @sc{http}. Note that when
./wget/wget.texi:retrieving individual files from an @sc{ftp} server without using
./wget/wget.texi:non-Unix @sc{ftp} servers use the Unixoid listing format because most
./wget/wget.texi:(all?) of the clients understand it. Bear in mind that @sc{rfc959}
./wget/wget.texi:that is supported by some @sc{ftp} servers (including the popular
./wget/wget.texi:Consider relative @sc{url}s in input files (specified via the
./wget/wget.texi:Follow @sc{ftp} links from @sc{html} documents---the same as
./wget/wget.texi:Only follow certain @sc{html} tags when doing a recursive retrieval,
./wget/wget.texi:If set to on, force the input filename to be regarded as an @sc{html}
./wget/wget.texi:Set your @sc{ftp} password to @var{string}. Without this setting, the
./wget/wget.texi:anonymous @sc{ftp} access.
./wget/wget.texi:Use @var{string} as @sc{ftp} proxy, instead of the one specified in
./wget/wget.texi:Set @sc{ftp} user to @var{string}.
./wget/wget.texi:Set @sc{http} password, equivalent to
./wget/wget.texi:Use @var{string} as @sc{http} proxy, instead of the one specified in
./wget/wget.texi:Set @sc{http} user to @var{string}, equivalent to
./wget/wget.texi:Use @var{string} as @sc{https} proxy, instead of the one specified in
./wget/wget.texi:Ignore certain @sc{html} tags when doing a recursive retrieval, like
./wget/wget.texi:Read the @sc{url}s from @var{string}, like @samp{-i @var{file}}.
./wget/wget.texi:Download all ancillary documents necessary for a single @sc{html} page to
./wget/wget.texi:Change setting of passive @sc{ftp}, equivalent to the
./wget/wget.texi:Specify password @var{string} for both @sc{ftp} and @sc{http} file retrieval.
./wget/wget.texi:@samp{http_password} command for @sc{ftp} and @sc{http} respectively.
./wget/wget.texi:the @sc{http} spec who got the spelling of ``referrer'' wrong.)
./wget/wget.texi:If set to on, remove @sc{ftp} listings downloaded by Wget. Setting it
./wget/wget.texi:Choose whether or not to print the @sc{http} and @sc{ftp} server
./wget/wget.texi:Set number of retries per @sc{url}---the same as @samp{-t @var{n}}.
./wget/wget.texi:Specify username @var{string} for both @sc{ftp} and @sc{http} file retrieval.
./wget/wget.texi:@samp{http_user} command for @sc{ftp} and @sc{http} respectively.
./wget/wget.texi:Say you want to download a @sc{url}. Just type:
./wget/wget.texi:The usage of @sc{ftp} is as simple. Wget will take care of login and
./wget/wget.texi:parse it and convert it to @sc{html}. Try:
./wget/wget.texi:If you specify @samp{-} as file name, the @sc{url}s will be read from
./wget/wget.texi:Retrieve only one @sc{html} page, but make sure that all the elements needed
./wget/wget.texi:The @sc{html} page will be saved to @file{www.example.com/dir/page.html}, and
./wget/wget.texi:You want to download all the @sc{gif}s from a directory on an @sc{http}
./wget/wget.texi:didn't work because @sc{http} retrieval does not support globbing. In
./wget/wget.texi:download only the @sc{gif} files. @samp{-A "*.gif"} would have worked
./wget/wget.texi:If you want to encode your own username and password to @sc{http} or
./wget/wget.texi:@sc{ftp}, use the appropriate @sc{url} syntax (@pxref{URL Format}).
./wget/wget.texi:If you wish Wget to keep a mirror of a page (or @sc{ftp}
./wget/wget.texi:back up the original @sc{html} files before the conversion. Wget invocation
./wget/wget.texi:when @sc{html} files are saved under extensions other than @samp{.html},
./wget/wget.texi:@dfn{Proxies} are special-purpose @sc{http} servers designed to transfer
./wget/wget.texi:achieved by channeling all @sc{http} and @sc{ftp} requests through the
./wget/wget.texi:Wget supports proxies for both @sc{http} and @sc{ftp} retrievals. The
./wget/wget.texi:contain the @sc{url}s of the proxies for @sc{http} and @sc{https}
./wget/wget.texi:This variable should contain the @sc{url} of the proxy for @sc{ftp}
./wget/wget.texi:@env{ftp_proxy} are set to the same @sc{url}.
./wget/wget.texi:be sent by Wget. As with @sc{http} authorization, several
./wget/wget.texi:@sc{url} or through the command-line options. Assuming that the
./wget/wget.texi:proxy @sc{url} location containing authorization data might look like
./wget/wget.texi:section handled by a CGI Perl script that converts Info files to @sc{html} on
./wget/wget.texi:an @sc{rfc}, is available at
./wget/wget.texi:way around it is to use @code{wget -i -} and feed the @sc{url}s to
./wget/wget.texi:The @sc{ftp} passwords are also in no way encrypted. There is no good
./wget/wget.texi:resources such as the mailing list, web space, @sc{ftp} space, and
./wget/wget.texi:Junio Hamano---donated support for Opie and @sc{http} @code{Digest}
./lightning/body.texi:generator is @sc{dcg}, by Dawson R.@: Engler and T.@: A.@: Proebsting.
./lightning/body.texi:Further work by Dawson R. Engler resulted in the @sc{vcode} system;
./lightning/body.texi:unlike @sc{dcg}, @sc{vcode} used no intermediate representation and
./lightning/body.texi:program @sc{ccg} under the GNU General Public License, thereby allowing
./lightning/body.texi:@lightning{} to use the run-time assemblers he had wrote for @sc{ccg}.
./lightning/body.texi:@sc{ccg} provides a way of dynamically assemble programs written in the
./lightning/lightning.texi:@set TITLE Using @sc{gnu} @i{lightning}
./lightning/lightning.texi:@sc{gnu}
./guile-sdl/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./guile-sdl/ref.texi:If @var{setting} is @code{#t}, enable @sc{mmx} instructions
./guile-sdl/ref.texi:loop it is shown via @code{update-rect}; or a pair whose @sc{car} is
./guile-sdl/ref.texi:a surface and whose @sc{cdr} is a thunk that should do the showing.
./cflow/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./identica-mode/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./acm/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./mediatex/useCase.texi:@sc{Mediatex} should help building a whole @sc{oais} system.
./mediatex/useCase.texi:Archive are now injected. You can browses the icons catalog at this @sc{url}: @*
./mediatex/useCase.texi:A minimal @sc{cakePhp} application is provided with the sources
./mediatex/useCase.texi:showing how to use the @sc{Mediatex} system as a storage layer.
./mediatex/data.texi:@item The @sc{Support} entity lists all the local supports.
./mediatex/data.texi:@item The @sc{Collection} entity lists all the collections the local server belongs to.
./mediatex/data.texi:@item The @sc{Server} entity lists all the servers.
./mediatex/data.texi:@item The @sc{Image} entity lists on @sc{iso} images hold by a server.
./mediatex/data.texi:@item The @sc{Archive} entity lists all archives known at running time.
./mediatex/data.texi:@item The @sc{Containter} entity gives rule to extract archives from each others.
./mediatex/data.texi:@item The @sc{Document} entity groups archives in order to describe them in a catalog.
./mediatex/data.texi:@item The @sc{Record} entity lists archives we works with.
./mediatex/client.texi:@activity{Client} is the front-end for the @sc{Mediatex} system.
./mediatex/exim.texi:@sc{Mediatex} uses @sc{Exim4}
./mediatex/main.texi:@mediatexO{} focus on providing an @sc{api} to ask for, and retrieve
./mediatex/main.texi:The following specifications use the @sc{Merise} conception method.
./mediatex/catalog.txt.texi:The @sc{Archive} entity lists all archive's data files.
./mediatex/catalog.txt.texi:The @sc{Document} entity groups archives (data, parts, versions time-stamps @dots{}) related to an archived document.
./mediatex/catalog.txt.texi:The @sc{Category} entity groups documents by themes (onthology).
./mediatex/catalog.txt.texi:The @sc{Human} entity lists humans (using an @acronym{AVL} tree) related to a document.
./mediatex/catalog.txt.texi:The @sc{Role} entity lists all titles a human contributing to a document may have (ex: producer, actor, @dots{} for a movie).
./mediatex/catalog.txt.texi:The @sc{*_Carac} entities are unidirectional in order to consume less memory.
./mediatex/catalog.txt.texi:The @sc{asso_role} relationship matches a human, a role and a document.
./mediatex/catalog.txt.texi:The @sc{contains} relationships matches ether humans or documents to categories, or records to documents.
./mediatex/mount-umount.texi:These 2 scripts mount or un-mount an @sc{iso} disk or file.
./mediatex/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./mediatex/extract.txt.texi:The @sc{Container} entity lists (using an @acronym{AVL} tree) all the container files from where archives are extracted. A Container is identified by its type (@sc{iso},@sc{tar}...) and the first archive needed for extraction (ex: @file{archive-part1.rar}), also called its first parent. Containers may provide a relative directory path to use when extracting the archive. This allow for instance to extract @sc{tar} container, that handle files on the root, into a directory.
./mediatex/extract.txt.texi:@note{} 2 dedicated @sc{Container} instances are used internally by @mediatex{} to manage the incoming (recently uploaded) archives, and where to extract supports into the cache.
./mediatex/extract.txt.texi:The @sc{Location} entity lists external ressources (directories).
./mediatex/extract.txt.texi:The @sc{Archive} entity lists the archive's data files
./mediatex/extract.txt.texi:The @sc{fromAsso} relationship enumerate (using an @acronym{AVL} tree) the content of a container. For instance, all files provided by a tarball archive: @code{tar -tf archive.tar}.
./mediatex/extract.txt.texi:@note{} for the incoming @sc{Container} instance, the @sc{fromAsso} relationship gives the date the archive was uploaded.
./mediatex/extract.txt.texi:The @sc{parents} relationship gives all the parts a container is using to perform extraction. (@file{archive-part1.rar}, @dots{}, @file{archive-part@var{N}.rar}).
./mediatex/extract.txt.texi:The @sc{toContainer} relationship gives the container object an Archive may provides.
./mediatex/extract.txt.texi:@note{} we can only have on containers for an archive: in the case of a compressed tarball for instance, we have to choose between the two possibilities (@sc{tar}+@sc{gz} or @sc{tgz}).
./mediatex/extract.txt.texi:The @sc{fromLocation} relationship gives files accessible by the collection user from the location directory. These ``located files'' are not true archives ; they still may be uploaded as ``archives'' later.
./mediatex/syslog.texi:@process{syslog} (actually @sc{rsyslog}: see @code{man rsyslogd (8)} and @sc{logrorate}: see @code{man logrotate (8)})
./mediatex/misc.texi:@item Build the @sc{html} catalogues.
./mediatex/consistency.texi:@sc{Mediatex} should ease managing server changes.
./mediatex/servers.txt.texi:The @sc{Server} entity lists all the servers participating to a collection.
./mediatex/servers.txt.texi:The @sc{Image} entity lists all the images files known by the collection.
./mediatex/servers.txt.texi:The @sc{Network} entity lists public and private networks we logically defined.
./mediatex/servers.txt.texi:The @sc{Archive} entity reminds all archives the programm is currently using per collection.
./mediatex/servers.txt.texi:The @sc{networks} relationship lists all the networks a server belongs to.
./mediatex/servers.txt.texi:The @sc{gateways} relationship lists all the networks for which a server
./mediatex/server.texi:exchange files with other @sc{Mediatex}'s @activity{Server}s.
./mediatex/apache.texi:@actorUser{} use @sc{Apache} to browse the @acronym{HTML} catalogue and access archives. (For tips, you should maybe read this section first : @pxref{HTTP}).
./mediatex/apache.texi:@sc{Apache} is configured to query the @activityServer{} via the @procScriptsCgi{} @acronym{CGI} script.
./mediatex/apache.texi:The followings @sc{Apache}'s modules are enabled by @sc{Mediatex}:
./mediatex/apache.texi:The @sc{Apache}'s configuration files given bellow are generated by
./mediatex/apache.texi:In current release we use if statement to manage 2.2 and 2.4 @sc{Apache}'s configuration files :
./mediatex/macros.texi:@sc{\label\}
./mediatex/macros.texi:@sc{\label\}
./mediatex/mdtx.conf.texi:The @sc{Configuration} entity is the single main contexte.
./mediatex/mdtx.conf.texi:The @sc{Collection} entity lists all the collections shared.
./mediatex/mdtx.conf.texi:The @sc{Network} entity lists logical networks the local host belongs to.
./mediatex/mdtx.conf.texi:The @sc{Support} entity lists all the local supports.
./mediatex/mdtx.conf.texi:The @sc{Server} entity lists all servers sharing a given collection.
./mediatex/mdtx.conf.texi:The @sc{manage} relationship lists all the collections our local server share.
./mediatex/mdtx.conf.texi:The @sc{networks} relationship lists all the networks the local host belongs to.
./mediatex/mdtx.conf.texi:The @sc{gateways} relationship lists all the networks for which our local
./mediatex/mdtx.conf.texi:The @sc{localhost} relationship gives our local server related to the
./mediatex/mdtx.conf.texi:The @sc{localImages} relationship lists all the supports shared within a
./mediatex/mdtx.conf.texi:@note{} @dataServers{} summerize the @sc{imageFiles}, @sc{networks} and @sc{gateways} relationships from all the hosts sharing a collection.
./mediatex/git.texi:@sc{Git}
./mediatex/mdtx-COLL.md5.texi:@item The @sc{Record} entity lists all informations we need to load/save and exchange about archives.
./mediatex/mdtx-COLL.md5.texi:The @sc{Archive} entity reminds all archives the programm is currently using per collection.
./mediatex/mdtx-COLL.md5.texi:The @sc{Server} entity, from
./mediatex/mdtx-COLL.md5.texi:The @sc{localSupply} relationhip gives the archive's file when available (@code{LOCAL_DEMAND}) on the local cache.
./mediatex/mdtx-COLL.md5.texi:The @sc{finalSupplies} relationhip lists supports presentely available on local host (@code{FINAL_SUPPLY}).
./mediatex/mdtx-COLL.md5.texi:The @sc{remoteSupplies} relationhip lists all archives available remotely (@code{REMOTE_SUPPLY}) from the other @activityServerO{}.
./mediatex/mdtx-COLL.md5.texi:The @sc{demands} relationhip lists all demand (@code{FINAL_DEMAND}, @code{LOCAL_DEMAND} and @code{REMOTE_DEMAND}) for an archive
./mediatex/init-remove-purge.texi:These 3 scripts manage @sc{Mediatex}'s installation (install, remove and purge).
./mediatex/invoking.texi:The goal of this section is to help to install @sc{mediatex} software
./mediatex/invoking.texi:As @sc{Publisher}, please check the ``message of the day''
./mediatex/invoking.texi:@sc{motd} will not complain any more about this support
./mediatex/invoking.texi:@note{} As it works the same way, we are using here @sc{iso} files
./mediatex/invoking.texi:@actorUser{} to the collection's @sc{apache} users.
./mediatex/invoking.texi:Give him permissions on some of the @sc{html} sections by editing
./mediatex/invoking.texi:Browses the remotely available collection's catalog via this @sc{url}: @*
./mediatex/invoking.texi:As a @sc{User}, browse the collection via this @sc{url}:
./mediatex/invoking.texi:@url{https://@/@sc{hostname1}/@/~mdtx-hello} and ask for a content
./mediatex/invoking.texi:As @sc{Publisher}, please check the ``message of the day''
./mediatex/invoking.texi:@sc{Publisher} has to add your key to the collection.
./mediatex/invoking.texi:@var{hostname1}$ mediatex add key @sc{keyFile} to coll hello
./mediatex/invoking.texi:As a @sc{User}, browse the collection on the first server via this @sc{url}:
./mediatex/invoking.texi:When first server reload (scheduled by @sc{cron}),
./mediatex/invoking.texi:@sc{Publisher} on @var{hostname2} is now asked to provide the supports it shares
./mediatex/invoking.texi:Once second server notify, first server will copy back the provided file it will needs, to serve the @sc{User} query.
./mediatex/invoking.texi:@section Scenario 6: add a @sc{nat} server
./mediatex/invoking.texi:@note{} By @sc{nat} we mean this third server should be located
./mediatex/invoking.texi:@var{hostname1}# ping @sc{hostname3} (ko: Destination Host Unreachable)
./mediatex/invoking.texi:server (via @sc{cron}) which will relay them to the third one.
./mediatex/invoking.texi:@sc{Publisher} on @var{hostname3} is now asked
./mediatex/invoking.texi:file and delivers a mail to advice the @sc{User} it becomes available.
./mediatex/supports.txt.texi:@item The @sc{Support} entity list all the local supports.
./mediatex/supports.txt.texi:@item The @sc{Collection} entity, from
./mediatex/supports.txt.texi:The @sc{collections} relationship list all the collection a specific support is shared with. This relation is not recorded into this file but into
./mediatex/overview.texi:to provides an @sc{api} to manage supports (to drive jukeboxes).
./mediatex/overview.texi:Trace-ability is done by @sc{Syslog} for programs
./mediatex/overview.texi:and by @sc{git} for changes in the meta-data.
./mediatex/overview.texi:Access is granted by @sc{Apache}, but when archives need to be retrieved, the
./mediatex/overview.texi:probably use the @sc{Sendmail} interface.
./mediatex/overview.texi:Servers tasks are driven by @sc{Cron}.
./mediatex/overview.texi:via the host's @sc{Motd} (by default).
./mediatex/overview.texi:using @sc{git}.
./mediatex/mediatex.texi:focusing on the archival storage entity define by the @sc{Oais} draft,
./mediatex/mediatex.texi:and on the @sc{NF Z 42-013} requirements.
./ccrtp/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./dico/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./dico/dico.texi:compatibility with the @sc{c} preprocessor.
./dico/dico.texi:# defdb(@sc{name}[, @sc{descr}])
./dico/dico.texi:# @r{Produce a standard definition for a database @sc{name}}.
./dico/dico.texi:# @r{If @sc{descr} is given, use it as a description}.
./dico/dico.texi:It takes two arguments. The first one, @sc{name}, defines the dictionary
./gnulib/make-stds.texi:@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf,
./gnulib/make-stds.texi:shell and the @sc{posix} shell), not @code{csh}. Don't use any
./gnulib/make-stds.texi:special features of @code{ksh} or @code{bash}, or @sc{posix} features
./gnulib/make-stds.texi:@sc{posix}-specified) options and features of these programs. For
./libtool/notes.texi:@c FreeBSD @command{make} does not conform to @sc{posix} in its handling
./dc/dc.texi:This file documents @sc{dc}, an arbitrary precision calculator.
./dc/dc.texi:@sc{dc} is a reverse-polish desk calculator
./dc/dc.texi:Normally @sc{dc} reads from the standard input;
./dc/dc.texi:and @sc{dc} reads and executes the contents of the files
./dc/dc.texi:To enter a number in @sc{dc}, type the digits,
./dc/dc.texi:@sc{dc} may be invoked with the following command-line options:
./dc/dc.texi:Evaluate @var{expr} as @sc{dc} commands.
./dc/dc.texi:Read and evaluate @sc{dc} commands from @var{file}.
./dc/dc.texi:@sc{dc} provides at least 256 memory registers,
./dc/dc.texi:@sc{dc} has three parameters that control its operation:
./dc/dc.texi:@sc{dc} can operate on strings as well as on numbers.
./dc/dc.texi:(which means that the contents of the string are processed as @sc{dc} commands).
./dc/dc.texi:and @sc{dc} always knows whether any given object is a string or a number.
./dc/dc.texi:the @samp{q} command will cause @sc{dc} to exit.
./rottlog/doclicense.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./libunistring/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./libunistring/libunistring.texi:@sc{LETTER DZ WITH CARON} comes in three forms:
./libunistring/libunistring.texi:@sc{LATIN CAPITAL LETTER DZ WITH CARON} (DZ),
./libunistring/libunistring.texi:@sc{LATIN CAPITAL LETTER D WITH SMALL LETTER Z WITH CARON} (Dz),
./libunistring/libunistring.texi:@sc{LATIN SMALL LETTER DZ WITH CARON} (dz).
./libunistring/libunistring.texi:is not true for German, where the @sc{LATIN SMALL LETTER SHARP S}, when
./libunistring/libunistring.texi:This is not true for the Greek sigma: @sc{GREEK CAPITAL LETTER SIGMA} is
./libunistring/libunistring.texi:the uppercase of both @sc{GREEK SMALL LETTER SIGMA} and
./libunistring/libunistring.texi:@sc{GREEK SMALL LETTER FINAL SIGMA}.
./libunistring/unicase.texi:@sc{LETTER DZ WITH CARON}, the German @sc{LATIN SMALL LETTER SHARP S}, the
./libunistring/unicase.texi:a character, U+00C4 @sc{LATIN CAPITAL LETTER A WITH DIAERESIS} and
./libunistring/unicase.texi:U+0041 @sc{LATIN CAPITAL LETTER A} U+0308 @sc{COMBINING DIAERESIS} the same.
./thales/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./guile-baux/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input
./reftex/reftex.texi:@email{dominik@@science.uva.nl}, with contributions by @i{Stephen
./bpel2owfn/fdl.texi:@sc{ascii} without markup, Texinfo input format, La@TeX{} input