{ "content": [ { "type": "text", "text": "# refer (info)\n\n## NAME\n\nrefer - preprocess bibliographic references for groff\n\n## SYNOPSIS\n\nrefer [-benCPRS] [-a n] [-c fields] [-f n] [-i fields] [-k field]\n[-l m,n] [-p filename] [-s fields] [-t n] -B field.macro [file\n...]\nrefer --help\nrefer -v\nrefer --version\n\n## DESCRIPTION\n\nThis file documents the GNU version of refer, which is part of the\ngroff document formatting system. refer copies the contents of file-\nname... to the standard output, except that lines between .[ and .] are\ninterpreted as citations, and lines between .R1 and .R2 are interpreted\nas commands about how citations are to be processed.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (4 subsections)\n- **USAGE**\n- **FILES**\n- **ENVIRONMENT**\n- **SEE ALSO**\n- **BUGS**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "refer", "section": "", "mode": "info", "summary": "refer - preprocess bibliographic references for groff", "synopsis": "refer [-benCPRS] [-a n] [-c fields] [-f n] [-i fields] [-k field]\n[-l m,n] [-p filename] [-s fields] [-t n] -B field.macro [file\n...]\nrefer --help\nrefer -v\nrefer --version", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [ { "flag": "", "long": null, "arg": null, "description": "capitalize fields -fn label %n" }, { "flag": "", "long": null, "arg": null, "description": "search-ignore fields -k label L~%a" }, { "flag": "", "long": null, "arg": null, "description": "label field~%a -l label A.nD.y%a -lm label A.n+mD.y%a -l,n label A.nD.y-n%a -lm,n label A.n+mD.y-n%a" }, { "flag": "", "long": null, "arg": null, "description": "database filename -sspec sort spec -tn search-truncate n These options are equivalent to the following commands with the addi- tion that the filenames specified on the command line are processed as if they were arguments to the bibliography command instead of in the normal way: -B annotate X AP; no-label-in-reference -Bfield.macro annotate field macro; no-label-in-reference The following options have no equivalent commands: -v Print the version number. -R Don't recognize lines beginning with .R1/.R2." } ], "examples": [], "see_also": [ { "name": "indxbib", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/indxbib/1/json" }, { "name": "lookbib", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/lookbib/1/json" }, { "name": "lkbib", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/lkbib/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 9, "subsections": [] }, { "name": "DESCRIPTION", "lines": 42, "subsections": [] }, { "name": "OPTIONS", "lines": 19, "subsections": [ { "name": "-cfields", "lines": 4 }, { "name": "-ifields", "lines": 4 }, { "name": "-kfield", "lines": 10 }, { "name": "-pfilename", "lines": 22 } ] }, { "name": "USAGE", "lines": 501, "subsections": [] }, { "name": "FILES", "lines": 8, "subsections": [] }, { "name": "ENVIRONMENT", "lines": 2, "subsections": [] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "BUGS", "lines": 4, "subsections": [] } ], "sections": { "NAME": { "content": "refer - preprocess bibliographic references for groff\n", "subsections": [] }, "SYNOPSIS": { "content": "refer [-benCPRS] [-a n] [-c fields] [-f n] [-i fields] [-k field]\n[-l m,n] [-p filename] [-s fields] [-t n] -B field.macro [file\n...]\n\nrefer --help\n\nrefer -v\nrefer --version\n", "subsections": [] }, "DESCRIPTION": { "content": "This file documents the GNU version of refer, which is part of the\ngroff document formatting system. refer copies the contents of file-\nname... to the standard output, except that lines between .[ and .] are\ninterpreted as citations, and lines between .R1 and .R2 are interpreted\nas commands about how citations are to be processed.\n\nEach citation specifies a reference. The citation can specify a refer-\nence that is contained in a bibliographic database by giving a set of\nkeywords that only that reference contains. Alternatively it can spec-\nify a reference by supplying a database record in the citation. A com-\nbination of these alternatives is also possible.\n\nFor each citation, refer can produce a mark in the text. This mark\nconsists of some label which can be separated from the text and from\nother labels in various ways. For each reference it also outputs groff\ncommands that can be used by a macro package to produce a formatted\nreference for each citation. The output of refer must therefore be\nprocessed using a suitable macro package. The -ms and -me macros are\nboth suitable. The commands to format a citation's reference can be\noutput immediately after the citation, or the references may be accumu-\nlated, and the commands output at some later point. If the references\nare accumulated, then multiple citations of the same reference will\nproduce a single formatted reference.\n\nThe interpretation of lines between .R1 and .R2 as commands is a new\nfeature of GNU refer. Documents making use of this feature can still\nbe processed by Unix refer just by adding the lines\n\n.de R1\n.ig R2\n..\nto the beginning of the document. This will cause troff to ignore ev-\nerything between .R1 and .R2. The effect of some commands can also be\nachieved by options. These options are supported mainly for compati-\nbility with Unix refer. It is usually more convenient to use commands.\n\nrefer generates .lf lines so that filenames and line numbers in mes-\nsages produced by commands that read refer output will be correct; it\nalso interprets lines beginning with .lf so that filenames and line\nnumbers in the messages and .lf lines that it produces will be accurate\neven if the input has been preprocessed by a command such as soelim(1).\n", "subsections": [] }, "OPTIONS": { "content": "Whitespace is permitted between a command-line option and its argument.\n\nMost options are equivalent to commands (for a description of these\ncommands, see subsection \"Commands\" below).\n\n-b no-label-in-text; no-label-in-reference\n\n-e accumulate\n\n-n no-default-database\n\n-C compatible\n\n-P move-punctuation\n\n-S label \"(A.n|Q) ', ' (D.y|D)\"; bracket-label \" (\" ) \"; \"\n\n-an reverse An\n", "subsections": [ { "name": "-cfields", "content": "capitalize fields\n\n-fn label %n\n" }, { "name": "-ifields", "content": "search-ignore fields\n\n-k label L~%a\n" }, { "name": "-kfield", "content": "label field~%a\n\n-l label A.nD.y%a\n\n-lm label A.n+mD.y%a\n\n-l,n label A.nD.y-n%a\n\n-lm,n label A.n+mD.y-n%a\n" }, { "name": "-pfilename", "content": "database filename\n\n-sspec sort spec\n\n-tn search-truncate n\n\nThese options are equivalent to the following commands with the addi-\ntion that the filenames specified on the command line are processed as\nif they were arguments to the bibliography command instead of in the\nnormal way:\n\n-B annotate X AP; no-label-in-reference\n\n-Bfield.macro\nannotate field macro; no-label-in-reference\n\nThe following options have no equivalent commands:\n\n-v Print the version number.\n\n-R Don't recognize lines beginning with .R1/.R2.\n" } ] }, "USAGE": { "content": "Bibliographic databases\nThe bibliographic database is a text file consisting of records sepa-\nrated by one or more blank lines. Within each record fields start with\na % at the beginning of a line. Each field has a one character name\nthat immediately follows the %. It is best to use only upper and lower\ncase letters for the names of fields. The name of the field should be\nfollowed by exactly one space, and then by the contents of the field.\nEmpty fields are ignored. The conventional meaning of each field is as\nfollows:\n\n%A The name of an author. If the name contains a title such as Jr.\nat the end, it should be separated from the last name by a\ncomma. There can be multiple occurrences of the %A field. The\norder is significant. It is a good idea always to supply an %A\nfield or a %Q field.\n\n%B For an article that is part of a book, the title of the book.\n\n%C The place (city) of publication.\n\n%D The date of publication. The year should be specified in full.\nIf the month is specified, the name rather than the number of\nthe month should be used, but only the first three letters are\nrequired. It is a good idea always to supply a %D field; if the\ndate is unknown, a value such as in press or unknown can be\nused.\n\n%E For an article that is part of a book, the name of an editor of\nthe book. Where the work has editors and no authors, the names\nof the editors should be given as %A fields and , (ed) or\n, (eds) should be appended to the last author.\n\n%G US Government ordering number.\n\n%I The publisher (issuer).\n\n%J For an article in a journal, the name of the journal.\n\n%K Keywords to be used for searching.\n\n%L Label.\n\n%N Journal issue number.\n\n%O Other information. This is usually printed at the end of the\nreference.\n\n%P Page number. A range of pages can be specified as m-n.\n\n%Q The name of the author, if the author is not a person. This\nwill only be used if there are no %A fields. There can only be\none %Q field.\n\n%R Technical report number.\n\n%S Series name.\n\n%T Title. For an article in a book or journal, this should be the\ntitle of the article.\n\n%V Volume number of the journal or book.\n\n%X Annotation.\n\nFor all fields except %A and %E, if there is more than one occurrence\nof a particular field in a record, only the last such field will be\nused.\n\nIf accent strings are used, they should follow the character to be ac-\ncented. This means that the AM macro must be used with the -ms macros.\nAccent strings should not be quoted: use one \\ rather than two.\n\nCitations\nThe format of a citation is\n.[opening-text\nflags keywords\nfields\n.]closing-text\n\nThe opening-text, closing-text, and flags components are optional.\nOnly one of the keywords and fields components need be specified.\n\nThe keywords component says to search the bibliographic databases for a\nreference that contains all the words in keywords. It is an error if\nmore than one reference if found.\n\nThe fields components specifies additional fields to replace or supple-\nment those specified in the reference. When references are being accu-\nmulated and the keywords component is non-empty, then additional fields\nshould be specified only on the first occasion that a particular refer-\nence is cited, and will apply to all citations of that reference.\n\nThe opening-text and closing-text component specifies strings to be\nused to bracket the label instead of the strings specified in the\nbracket-label command. If either of these components is non-empty, the\nstrings specified in the bracket-label command will not be used; this\nbehaviour can be altered using the [ and ] flags. Note that leading\nand trailing spaces are significant for these components.\n\nThe flags component is a list of non-alphanumeric characters each of\nwhich modifies the treatment of this particular citation. Unix refer\nwill treat these flags as part of the keywords and so will ignore them\nsince they are non-alphanumeric. The following flags are currently\nrecognized:\n\n# This says to use the label specified by the short-label command,\ninstead of that specified by the label command. If no short la-\nbel has been specified, the normal label will be used. Typi-\ncally the short label is used with author-date labels and con-\nsists of only the date and possibly a disambiguating letter; the\n# is supposed to be suggestive of a numeric type of label.\n\n[ Precede opening-text with the first string specified in the\nbracket-label command.\n\n] Follow closing-text with the second string specified in the\nbracket-label command.\n\nOne advantages of using the [ and ] flags rather than including the\nbrackets in opening-text and closing-text is that you can change the\nstyle of bracket used in the document just by changing the bracket-la-\nbel command. Another advantage is that sorting and merging of cita-\ntions will not necessarily be inhibited if the flags are used.\n\nIf a label is to be inserted into the text, it will be attached to the\nline preceding the .[ line. If there is no such line, then an extra\nline will be inserted before the .[ line and a warning will be given.\n\nThere is no special notation for making a citation to multiple refer-\nences. Just use a sequence of citations, one for each reference.\nDon't put anything between the citations. The labels for all the cita-\ntions will be attached to the line preceding the first citation. The\nlabels may also be sorted or merged. See the description of the <> la-\nbel expression, and of the sort-adjacent-labels and abbreviate-label-\nranges command. A label will not be merged if its citation has a non-\nempty opening-text or closing-text. However, the labels for a citation\nusing the ] flag and without any closing-text immediately followed by a\ncitation using the [ flag and without any opening-text may be sorted\nand merged even though the first citation's opening-text or the second\ncitation's closing-text is non-empty. (If you wish to prevent this\njust make the first citation's closing-text \\&.)\n\nCommands\nCommands are contained between lines starting with .R1 and .R2. Recog-\nnition of these lines can be prevented by the -R option. When a .R1\nline is recognized any accumulated references are flushed out. Neither\n.R1 nor .R2 lines, nor anything between them is output.\n\nCommands are separated by newlines or ;s. # introduces a comment that\nextends to the end of the line (but does not conceal the newline).\nEach command is broken up into words. Words are separated by spaces or\ntabs. A word that begins with \" extends to the next \" that is not fol-\nlowed by another \". If there is no such \" the word extends to the end\nof the line. Pairs of \" in a word beginning with \" collapse to a sin-\ngle \". Neither # nor ; are recognized inside \"s. A line can be con-\ntinued by ending it with \\; this works everywhere except after a #.\n\nEach command name that is marked with * has an associated negative com-\nmand no-name that undoes the effect of name. For example, the no-sort\ncommand specifies that references should not be sorted. The negative\ncommands take no arguments.\n\nIn the following description each argument must be a single word; field\nis used for a single upper or lower case letter naming a field; fields\nis used for a sequence of such letters; m and n are used for a non-neg-\native numbers; string is used for an arbitrary string; filename is used\nfor the name of a file.\n\nabbreviate* fields string1 string2 string3 string4\nAbbreviate the first names of fields. An initial letter will be\nseparated from another initial letter by string1, from the last\nname by string2, and from anything else (such as a von or de) by\nstring3. These default to a period followed by a space. In a\nhyphenated first name, the initial of the first part of the name\nwill be separated from the hyphen by string4; this defaults to a\nperiod. No attempt is made to handle any ambiguities that might\nresult from abbreviation. Names are abbreviated before sorting\nand before label construction.\n\nabbreviate-label-ranges* string\nThree or more adjacent labels that refer to consecutive refer-\nences will be abbreviated to a label consisting of the first la-\nbel, followed by string followed by the last label. This is\nmainly useful with numeric labels. If string is omitted it de-\nfaults to -.\n\naccumulate*\nAccumulate references instead of writing out each reference as\nit is encountered. Accumulated references will be written out\nwhenever a reference of the form\n\n.[\n$LIST$\n.]\n\nis encountered, after all input files have been processed, and\nwhenever .R1 line is recognized.\n\nannotate* field string\nfield is an annotation; print it at the end of the reference as\na paragraph preceded by the line\n\n.string\n\nIf string is omitted it will default to AP; if field is also\nomitted it will default to X. Only one field can be an annota-\ntion.\n\narticles string...\nstring... are definite or indefinite articles, and should be ig-\nnored at the beginning of T fields when sorting. Initially,\nthe, a and an are recognized as articles.\n\nbibliography filename...\nWrite out all the references contained in the bibliographic\ndatabases filename... This command should come last in a\n.R1/.R2 block.\n\nbracket-label string1 string2 string3\nIn the text, bracket each label with string1 and string2. An\noccurrence of string2 immediately followed by string1 will be\nturned into string3. The default behaviour is\n\nbracket-label \\*([. \\*(.] \", \"\n\ncapitalize fields\nConvert fields to caps and small caps.\n\ncompatible*\nRecognize .R1 and .R2 even when followed by a character other\nthan space or newline.\n\ndatabase filename...\nSearch the bibliographic databases filename... For each file-\nname if an index filename.i created by indxbib(1) exists, then\nit will be searched instead; each index can cover multiple data-\nbases.\n\ndate-as-label* string\nstring is a label expression that specifies a string with which\nto replace the D field after constructing the label. See sub-\nsection \"Label expressions\" below for a description of label ex-\npressions. This command is useful if you do not want explicit\nlabels in the reference list, but instead want to handle any\nnecessary disambiguation by qualifying the date in some way.\nThe label used in the text would typically be some combination\nof the author and date. In most cases you should also use the\nno-label-in-reference command. For example,\n\ndate-as-label D.+yD.y%a*D.-y\n\nwould attach a disambiguating letter to the year part of the D\nfield in the reference.\n\ndefault-database*\nThe default database should be searched. This is the default\nbehaviour, so the negative version of this command is more use-\nful. refer determines whether the default database should be\nsearched on the first occasion that it needs to do a search.\nThus a no-default-database command must be given before then, in\norder to be effective.\n\ndiscard* fields\nWhen the reference is read, fields should be discarded; no\nstring definitions for fields will be output. Initially, fields\nare XYZ.\n\net-al* string m n\nControl use of et al in the evaluation of @ expressions in label\nexpressions. If the number of authors needed to make the author\nsequence unambiguous is u and the total number of authors is t\nthen the last t-u authors will be replaced by string provided\nthat t-u is not less than m and t is not less than n. The de-\nfault behaviour is\n\net-al \" et al\" 2 3\n\ninclude filename\nInclude filename and interpret the contents as commands.\n\njoin-authors string1 string2 string3\nThis says how authors should be joined together. When there are\nexactly two authors, they will be joined with string1. When\nthere are more than two authors, all but the last two will be\njoined with string2, and the last two authors will be joined\nwith string3. If string3 is omitted, it will default to\nstring1; if string2 is also omitted it will also default to\nstring1. For example,\n\njoin-authors \" and \" \", \" \", and \"\n\nwill restore the default method for joining authors.\n\nlabel-in-reference*\nWhen outputting the reference, define the string [F to be the\nreference's label. This is the default behaviour; so the nega-\ntive version of this command is more useful.\n\nlabel-in-text*\nFor each reference output a label in the text. The label will\nbe separated from the surrounding text as described in the\nbracket-label command. This is the default behaviour; so the\nnegative version of this command is more useful.\n\nlabel string\nstring is a label expression describing how to label each refer-\nence.\n\nseparate-label-second-parts string\nWhen merging two-part labels, separate the second part of the\nsecond label from the first label with string. See the descrip-\ntion of the <> label expression.\n\nmove-punctuation*\nIn the text, move any punctuation at the end of line past the\nlabel. It is usually a good idea to give this command unless\nyou are using superscripted numbers as labels.\n\nreverse* string\nReverse the fields whose names are in string. Each field name\ncan be followed by a number which says how many such fields\nshould be reversed. If no number is given for a field, all such\nfields will be reversed.\n\nsearch-ignore* fields\nWhile searching for keys in databases for which no index exists,\nignore the contents of fields. Initially, fields XYZ are ig-\nnored.\n\nsearch-truncate* n\nOnly require the first n characters of keys to be given. In ef-\nfect when searching for a given key words in the database are\ntruncated to the maximum of n and the length of the key. Ini-\ntially n is 6.\n\nshort-label* string\nstring is a label expression that specifies an alternative (usu-\nally shorter) style of label. This is used when the # flag is\ngiven in the citation. When using author-date style labels, the\nidentity of the author or authors is sometimes clear from the\ncontext, and so it may be desirable to omit the author or au-\nthors from the label. The short-label command will typically be\nused to specify a label containing just a date and possibly a\ndisambiguating letter.\n\nsort* string\nSort references according to string. References will automati-\ncally be accumulated. string should be a list of field names,\neach followed by a number, indicating how many fields with the\nname should be used for sorting. + can be used to indicate that\nall the fields with the name should be used. Also . can be used\nto indicate the references should be sorted using the (tenta-\ntive) label. (Subsection \"Label expressions\" below describes\nthe concept of a tentative label.)\n\nsort-adjacent-labels*\nSort labels that are adjacent in the text according to their po-\nsition in the reference list. This command should usually be\ngiven if the abbreviate-label-ranges command has been given, or\nif the label expression contains a <> expression. This will\nhave no effect unless references are being accumulated.\n\nLabel expressions\nLabel expressions can be evaluated both normally and tentatively. The\nresult of normal evaluation is used for output. The result of tenta-\ntive evaluation, called the tentative label, is used to gather the in-\nformation that normal evaluation needs to disambiguate the label. La-\nbel expressions specified by the date-as-label and short-label commands\nare not evaluated tentatively. Normal and tentative evaluation are the\nsame for all types of expression other than @, *, and % expressions.\nThe description below applies to normal evaluation, except where other-\nwise specified.\n\nfield\nfield n\nThe n-th part of field. If n is omitted, it defaults to 1.\n\n'string'\nThe characters in string literally.\n\n@ All the authors joined as specified by the join-authors command.\nThe whole of each author's name will be used. However, if the\nreferences are sorted by author (that is the sort specification\nstarts with A+), then authors last names will be used instead,\nprovided that this does not introduce ambiguity, and also an\ninitial subsequence of the authors may be used instead of all\nthe authors, again provided that this does not introduce ambigu-\nity. The use of only the last name for the i-th author of some\nreference is considered to be ambiguous if there is some other\nreference, such that the first i-1 authors of the references are\nthe same, the i-th authors are not the same, but the i-th au-\nthors last names are the same. A proper initial subsequence of\nthe sequence of authors for some reference is considered to be\nambiguous if there is a reference with some other sequence of\nauthors which also has that subsequence as a proper initial sub-\nsequence. When an initial subsequence of authors is used, the\nremaining authors are replaced by the string specified by the\net-al command; this command may also specify additional require-\nments that must be met before an initial subsequence can be\nused. @ tentatively evaluates to a canonical representation of\nthe authors, such that authors that compare equally for sorting\npurpose will have the same representation.\n\n%n\n%a\n%A\n%i\n%I The serial number of the reference formatted according to the\ncharacter following the %. The serial number of a reference\nis 1 plus the number of earlier references with same tentative\nlabel as this reference. These expressions tentatively evaluate\nto an empty string.\n\nexpr* If there is another reference with the same tentative label as\nthis reference, then expr, otherwise an empty string. It tenta-\ntively evaluates to an empty string.\n\nexpr+n\nexpr-n The first (+) or last (-) n upper or lower case letters or dig-\nits of expr. Troff special characters (such as \\('a) count as a\nsingle letter. Accent strings are retained but do not count to-\nwards the total.\n\nexpr.l expr converted to lowercase.\n\nexpr.u expr converted to uppercase.\n\nexpr.c expr converted to caps and small caps.\n\nexpr.r expr reversed so that the last name is first.\n\nexpr.a expr with first names abbreviated. Note that fields specified\nin the abbreviate command are abbreviated before any labels are\nevaluated. Thus .a is useful only when you want a field to be\nabbreviated in a label but not in a reference.\n\nexpr.y The year part of expr.\n\nexpr.+y\nThe part of expr before the year, or the whole of expr if it\ndoes not contain a year.\n\nexpr.-y\nThe part of expr after the year, or an empty string if expr does\nnot contain a year.\n\nexpr.n The last name part of expr.\n\nexpr1~expr2\nexpr1 except that if the last character of expr1 is - then it\nwill be replaced by expr2.\n\nexpr1 expr2\nThe concatenation of expr1 and expr2.\n\nexpr1|expr2\nIf expr1 is non-empty then expr1 otherwise expr2.\n\nexpr1&expr2\nIf expr1 is non-empty then expr2 otherwise an empty string.\n\nexpr1?expr2:expr3\nIf expr1 is non-empty then expr2 otherwise expr3.\n\n The label is in two parts, which are separated by expr. Two ad-\njacent two-part labels which have the same first part will be\nmerged by appending the second part of the second label onto the\nfirst label separated by the string specified in the separate-\nlabel-second-parts command (initially, a comma followed by a\nspace); the resulting label will also be a two-part label with\nthe same first part as before merging, and so additional labels\ncan be merged into it. Note that it is permissible for the\nfirst part to be empty; this maybe desirable for expressions\nused in the short-label command.\n\n(expr) The same as expr. Used for grouping.\n\nThe above expressions are listed in order of precedence (highest\nfirst); & and | have the same precedence.\n\nMacro interface\nEach reference starts with a call to the macro ]-. The string [F will\nbe defined to be the label for this reference, unless the no-label-in-\nreference command has been given. There then follows a series of\nstring definitions, one for each field: string [X corresponds to field\nX. The number register [P is set to 1 if the P field contains a range\nof pages. The [T, [A and [O number registers are set to 1 according as\nthe T, A and O fields end with one of the characters .?!. The [E num-\nber register will be set to 1 if the [E string contains more than one\nname. The reference is followed by a call to the ][ macro. The first\nargument to this macro gives a number representing the type of the ref-\nerence. If a reference contains a J field, it will be classified as\ntype 1, otherwise if it contains a B field, it will type 3, otherwise\nif it contains a G or R field it will be type 4, otherwise if it con-\ntains an I field it will be type 2, otherwise it will be type 0. The\nsecond argument is a symbolic name for the type: other, journal-arti-\ncle, book, article-in-book or tech-report. Groups of references that\nhave been accumulated or are produced by the bibliography command are\npreceded by a call to the ]< macro and followed by a call to the ]>\nmacro.\n", "subsections": [] }, "FILES": { "content": "/usr/dict/papers/Ind\nDefault database.\n\nfile.i Index files.\n\nrefer uses temporary files. See the groff(1) man page for details\nwhere such files are created.\n", "subsections": [] }, "ENVIRONMENT": { "content": "REFER If set, overrides the default database.\n", "subsections": [] }, "SEE ALSO": { "content": "indxbib(1), lookbib(1), lkbib(1)\n", "subsections": [] }, "BUGS": { "content": "In label expressions, <> expressions are ignored inside .char expres-\nsions.\n\ngroff 1.22.4 23 March 2022 REFER(1)", "subsections": [] } } } }