Ticket #35549: patch-doc-pinfo.texi.diff

File patch-doc-pinfo.texi.diff, 5.1 KB (added by master@…, 12 years ago)
  • doc/pinfo.texi

    old new  
    6060@value{DATE}.
    6161
    6262@menu
    63 * Invoking::                    Comman line options.
     63* Invoking::                    Command line options.
    6464* Configuration::               Configurable behaviour of pinfo.
    6565* Internationalization Support::  Localization.
    6666* Author::                      Who wrote pinfo.
    6767* Bugs::                        Help debugging.
    6868* Copyright::                   Copying.
    69 * Index::                       Search.
     69* Index::                       Index.
    7070
    7171@detailmenu
    7272 --- The Detailed Node Listing ---
     
    8080
    8181* Color::                       Color settings.
    8282* Keys::                        Bindable keyboard.
    83 * Options::                     Confiruration options.
     83* Options::                     Configuration options.
    8484* Example config file::         Build in values.
    8585
    8686Keys
     
    100100@value{PROGRAM} [@var{options}] [@var{info_page}]
    101101
    102102@value{PROGRAM} is a program for viewing info files. You specify which
    103 page you want to read by passing it an @var{info_page} argument. This argumen
    104 t
     103page you want to read by passing it an @var{info_page} argument. This argument
    105104contains the name of an info page (i.e. @samp{bash}). The program
    106105will then (by default) search for it in the current diectory, @file{/usr/share/info},
    107106@file{/usr/info}, @file{/usr/local/share/info}, @file{/usr/local/info},
     
    113112to the function @code{openinfo()} in @file{filehandling_functions.c}.
    114113
    115114When the search for info pages fails, man is called with the @var{info_page}
    116 argument, and it's output is parsed by @value{PROGRAM}. This means that
     115argument, and its output is parsed by @value{PROGRAM}. This means that
    117116when you don't have the appropriate info page, but have a man page
    118117instead; the man page will be viewed.
    119118
     
    132131could be used as a manual pager). Warning: Everything what follows this
    133132option is passed to the @code{man} program. Don't be confused if
    134133@value{PROGRAM} options, which followed @samp{-m} don't work.
    135 When using this option, pinfo does not parse the info options as ussual!
     134When using this option, pinfo does not parse the info options as usual!
    136135It invokes the man part of program.
    137136
    138137You can also call the man function of @value{PROGRAM} in another way.
    139138When @value{PROGRAM} is called with an @code{argv[0]} (the program file
    140 name), which contains the word @code{man} in it's name, the man
     139name), which contains the word @code{man} in its name, the man
    141140functions are enabled automatically.
    142141
    143142Previously there was a symlink to @value{PROGRAM}, called @code{pman},
    144 but I had to remove it from the distribution, since it's name was in
     143but I had to remove it from the distribution, since its name was in
    145144conflict with some other utility. Anyway, you can feel free to create
    146145such a link if you wish.
    147146@item -r, --raw-filename
     
    161160@item -t, --force-manual-tag-table
    162161forces manual detection of tag table. This allows you to view info
    163162pages, which may be corrupted.  (as i.e.  version of jed's pages,
    164 shipped with RH5.0). The tag table corruption ussualy appears in that
     163shipped with RH5.0). The tag table corruption usualy appears in that
    165164the info links, which you follow, move you to quite unexpected nodes.
    166165@item --node=@var{nodename}, --node @var{nodename}
    167166Go to the node @var{nodename} of info file. Since 0.6.7 it is also
     
    239238@cindex How to use it
    240239
    241240Now let's move to the key definitions. Here we first put a key name
    242 (again all keys are present in the example); then we enter it's value --
     241(again all keys are present in the example); then we enter its value --
    243242either surrounded by apostrophes, or a keycode number (like in
    244 @var{KEY_REFRESH_1}), or its mnemonic code name if it's a special key
     243@var{KEY_REFRESH_1}), or its mnemonic code name if its a special key
    245244(like i.e.  in @var{KEY_FOLLOWLINK_1}).
    246245
    247246If you wish to specify key by code value, use the supplied program
     
    284283Alternate key for repeating the last search.
    285284
    286285@item KEY_GOTO_1
    287 Key for explicitly going to a node (by specifing it's name).
     286Key for explicitly going to a node (by specifing its name).
    288287
    289288@item KEY_GOTO_2
    290 Alternate key for explicitly going to a node (by specifing it's name).
     289Alternate key for explicitly going to a node (by specifing its name).
    291290
    292291@item KEY_PREVNODE_1
    293292Key for going to a node marked as 'Prev' in the header. In manpage viewer
     
    443442this means a printable character c. The syntax is just like in C/C++ ;).
    444443
    445444@item [number]
    446 you can also specify key as it's code number.  It is useful e.g. when
     445you can also specify key as its code number.  It is useful e.g. when
    447446specifing control keys, and some nonstandard keys.  A numerical value of
    448447zero turns given keybinding off.
    449448
     
    703702@email{pborys@@zeus.polsl.gliwice.pl}, or
    704703@email{pborys@@p-soft.silesia.linux.org.pl}.
    705704
    706 There was also a lot of other people, who contributed to this code. See
    707 the @file{AUTHORS} file.
     705A lot of other people also contributed
     706to this code.
     707See the @file{AUTHORS} file.
    708708
    709709Please send bug reports to the author: @value{AUTHOR} @value{CONTACT}.
    710710