Lines Matching refs:in
14 # This forces PL files to create target in same directory as PL file.
119 I<input> is the file to read for POD source (the POD can be embedded in
123 processed in the same B<pod2man> invocation (saving module load and compile
198 the manual section is 3, in which case the path is parsed to see if it is a
205 man page title to be in all-uppercase even if the command isn't.
221 I<quotes> may also be set to the special value C<none>, in which case no
244 By default, section 1 will be used unless the file ends in .pm in which case
270 To get index entries on stderr, turn on the F register, as in:
287 The name of the program being documented is conventionally written in bold
289 Arguments should be written in italics (IE<lt>E<gt>). Functions are
290 traditionally written in italics; if you write a function as function(),
292 be in CE<lt>E<gt>. References to other man pages should be in the form
297 References to other programs or functions are normally in the form of man
303 historically written in the rather startling ALL UPPER CASE format, although
305 are typically in mixed case.
319 section, so don't put anything in it except this line. A single dash, and
351 enclosed in BE<lt>E<gt>. Any values that the option takes should be
352 enclosed in IE<lt>E<gt>. For example, the section for the option
366 otherwise get lost in visual noise.)
380 STDOUT or STDERR and intended for the end user are documented in DIAGNOSTICS
382 programmers are documented in ERRORS. When documenting a function that sets
415 Used to determine the user's home directory. F<.foorc> in this
420 Since environment variables are normally in all uppercase, no additional
426 what it uses them for. File names should be enclosed in FE<lt>E<gt>. It's
450 use the standard C<name(section)> form, don't have to be enclosed in
451 LE<lt>E<gt> (although it's recommended), but other things in this section
488 consider maintaining it in a separate file, though.
493 standards and MT-LEVEL to note safeness for use in threaded programs or
503 DESCRIPTION, and OPTIONS generally always occur first and in that order if
509 As documented here and in L<Pod::Man>, you can safely leave Perl variables,
514 or URLs when wrapped in LE<lt>E<gt>, so don't do that.