d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Mechanically kill hard sentence breaks.

Browse Source
This commit is contained in:
ru 2004-07-02 21:53:39 +00:00
parent 42b6f36397
commit 2334c79a75
3 changed files with 85 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

102
gnu/lib/libdialog/dialog.3
View File

@ -143,17 +143,20 @@
The dialog library attempts to provide a fairly simplistic set of
fixed-presentation menus, input boxes, gauges, file requestors and
other general purpose GUI (a bit of a stretch, since it uses
ncurses) objects. Since the library also had its roots in a
ncurses) objects.
Since the library also had its roots in a
shell-script writer's utility (see the
.Xr dialog 1
command), the
early API was somewhat primitively based on strings being passed in or
out and parsed. This API was later extended to take either the
out and parsed.
This API was later extended to take either the
original arguments or arrays of
.Va dialogMenuItem
structures,
giving the user much more control over the internal behavior of each
control. The
control.
The
.Va dialogMenuItem
structure internals are public:
.Bd -literal -offset indent
@ -183,12 +186,14 @@ display and action hooks (the
.Dv data
variable being available for
the convenience of those hooks) when more tightly coupled feedback between
a menu object and user code is required. The
a menu object and user code is required.
The
.Va selected
hook also
allows you to verify whether or not a given item is selected (the cursor is
over it) for implementing pretty much any possible context-sensitive
behavior. A number of clever tricks for simulating various kinds of item
behavior.
A number of clever tricks for simulating various kinds of item
types can also be done by adjusting the values of
.Va lbra
(default: '['),
@ -227,7 +232,8 @@ The following flags are in the upper 16 bits of return status:
.Pp
Two special globals also exist for putting a dialog at any arbitrary
X,Y location (the early designers rather short-sightedly made no provisions
for this). If set to zero, the default centering behavior will be in
for this).
If set to zero, the default centering behavior will be in
effect.
.Pp
Below is a short description of the various functions:
@ -287,7 +293,8 @@ The
.Fn dialog_create_rc
function dumps dialog library settings into
.Pa filename
for later retrieval as defaults. Returns 0 on success, -1 on failure.
for later retrieval as defaults.
Returns 0 on success, -1 on failure.
.Pp
The
.Fn dialog_yesno
@ -308,7 +315,8 @@ The default selection is
.Em Yes .
If the
.Em Yes
button is chosen, return FALSE. If
button is chosen, return FALSE.
If
.Em \&No ,
return TRUE.
.Pp
@ -338,7 +346,8 @@ otherwise it is simply passed to
If
.Va pause
is TRUE, a final confirmation requestor will be put up when execution
terminates. Returns 0 on success, -1 on failure.
terminates.
Returns 0 on success, -1 on failure.
.Pp
The
.Fn dialog_textbox
@ -362,7 +371,8 @@ The
and
.Va it
arguments are of particular importance since they,
together, determine which of the 2 available APIs to use. To use the
together, determine which of the 2 available APIs to use.
To use the
older and traditional interface,
.Va cnt
should be a positive
@ -374,7 +384,8 @@ the strings are
expected to be in prompt and title order for each item and the
.Va result
parameter is expected to point to an array where the
prompt string of the item selected will be copied. To use the newer
prompt string of the item selected will be copied.
To use the newer
interface,
.Va cnt
should be a
@ -385,11 +396,13 @@ structures pointed to by
.Va it
(which should be of type
.Vt dialogMenuItem "*" ) ,
one structure per item. In the new interface, the
one structure per item.
In the new interface, the
.Va result
variable is used as a simple boolean (not a pointer) and should be NULL if
.Va it
only points to menu items and the default OK and Cancel buttons are desired. If
only points to menu items and the default OK and Cancel buttons are desired.
If
.Va result
is non-NULL, then
.Va it
@ -427,7 +440,8 @@ The
and
.Va it
arguments are of particular importance since they,
together, determine which of the 2 available APIs to use. To use the
together, determine which of the 2 available APIs to use.
To use the
older and traditional interface,
.Va cnt
should be a positive
@ -441,7 +455,8 @@ each item and the
.Va result
parameter is expected to point to an
array where the prompt string of the item(s) selected will be
copied. To use the newer interface,
copied.
To use the newer interface,
.Va cnt
should be a
.Em negative
@ -451,14 +466,16 @@ structures pointed to by
.Va it
(which should be of type
.Ft "dialogMenuItem *" ) ,
one structure per item. In the new interface,
one structure per item.
In the new interface,
the
.Va result
variable is used as a simple boolean (not a pointer)
and should be NULL if
.Va it
only points to menu items and the default OK and Cancel
buttons are desired. If
buttons are desired.
If
.Va result
is non-NULL, then
.Va it
@ -477,7 +494,8 @@ actions are used to override the default behavior, and
to the same for the OK button.
.Pp
In the standard API model, the menu supports the selection of multiple items,
each of which is marked with an `X' character to denote selection. When
each of which is marked with an `X' character to denote selection.
When
the OK button is selected, the prompt values for all items selected are
concatenated into the
.Va result
@ -488,7 +506,8 @@ In the new API model, it is not actually necessary to preserve
each item is displayed or marked as "selected" is fully configurable.
You could have a single checklist menu that actually contained a group
of items with "radio" behavior, "checklist" behavior and standard menu
item behavior. The only reason to call
item behavior.
The only reason to call
.Fn dialog_checklist
over
.Fn dialog_radiolist
@ -511,7 +530,8 @@ The
and
.Va it
arguments are of particular importance since they,
together, determine which of the 2 available APIs to use. To use the
together, determine which of the 2 available APIs to use.
To use the
older and traditional interface,
.Va cnt
should be a positive
@ -525,7 +545,8 @@ each item and the
.Va result
parameter is expected to point to an
array where the prompt string of the item(s) selected will be
copied. To use the newer interface,
copied.
To use the newer interface,
.Va cnt
should be a
.Dv negative
@ -535,14 +556,16 @@ structures pointed to by
.Va it
(which should be of type
.Ft "dialogMenuItem *" ,
one structure per item. In the new interface,
one structure per item.
In the new interface,
the
.Va result
variable is used as a simple boolean (not a pointer)
and should be NULL if
.Va it
only points to menu items and the default OK and Cancel
buttons are desired. If
buttons are desired.
If
.Va result
is non-NULL, then
.Va it
@ -561,7 +584,8 @@ does the same for the traditional OK button.
.Pp
In the standard API model, the menu supports the selection of only one
of multiple items, the currently active item marked with an `*'
character to denote selection. When the OK button is selected, the
character to denote selection.
When the OK button is selected, the
prompt value for this item is copied into the
.Va result
string.
@ -571,7 +595,8 @@ In the new API model, it is not actually necessary to preserve
each item is displayed or marked as "selected" is fully configurable.
You could have a single radio menu that actually contained a group
of items with "checklist" behavior, "radio" behavior and standard menu
item behavior. The only reason to call
item behavior.
The only reason to call
.Fn dialog_radiolist
over
.Fn dialog_checklistlist
@ -635,7 +660,8 @@ Returns 0 on success, -1 on failure.
.Pp
The
.Fn dialog_gauge
function displays a horizontal bar-graph style gauge. A value of
function displays a horizontal bar-graph style gauge.
A value of
.Em 100
for
.Em perc
@ -701,7 +727,8 @@ and
are positive numbers, they set the absolute
size of the whole
.Fn dialog_ftree
box. If
box.
If
.Va height
and
.Va width
@ -721,7 +748,8 @@ is shown inside the
.Fn dialog_ftree
box above the tree subwindow and can contain
.Ql \e\&n
to split lines. One can navigate in
to split lines.
One can navigate in
the tree by pressing UP/DOWN or
.Sm off
.So \&+ Sc \&/ So \&- Sc ,
@ -737,23 +765,29 @@ HOME/END or
.Sm on
A leaf of the
tree is selected by pressing TAB or LEFT/RIGHT the OK
button and pressing ENTER. filename may contain data like
button and pressing ENTER.
filename may contain data like
.Xr find 1
output, as well as like the output of
.Xr find 1
with
.Fl d
option. Some of the transient paths to the leaves of the tree may
be absent. Such data is corrected when fed from filename.
option.
Some of the transient paths to the leaves of the tree may
be absent.
Such data is corrected when fed from filename.
.Pp
The function returns 0 and a pointer to the selected leaf (to the path to
the leaf from the root of the tree) into result, if the OK button was
selected. The memory allocated for the building of the tree is freed on
selected.
The memory allocated for the building of the tree is freed on
exiting
.Fn dialog_ftree .
The memory for the result line should be freed
later manually, if necessary. If the Cancel button was selected, the
function returns 1. In case of exiting
later manually, if necessary.
If the Cancel button was selected, the
function returns 1.
In case of exiting
.Fn dialog_ftree
on ESC, the function returns -1.
.Pp

24
gnu/usr.bin/man/man/man.man
View File

@ -32,19 +32,23 @@
.Ar name ...
.Sh DESCRIPTION
.Nm Man
formats and displays the on-line manual pages. This version knows
formats and displays the on-line manual pages.
This version knows
about the
.Ev MANPATH
and
.Ev PAGER
environment variables, so you can have
your own set(s) of personal man pages and choose whatever program you
like to display the formatted pages. If section is specified,
like to display the formatted pages.
If section is specified,
.Nm
only looks in that section of the manual. You may also specify the
only looks in that section of the manual.
You may also specify the
order to search the sections for entries and which preprocessors to
run on the source files via command line options or environment
variables. If enabled by the system administrator, formatted man
variables.
If enabled by the system administrator, formatted man
pages will also be compressed with the `%compress%' command to save
space.
.Pp
@ -59,7 +63,8 @@ uses
(which is built into the
.Nm
binary)
to determine the path to search. This option overrides the
to determine the path to search.
This option overrides the
.Ev MANPATH
environment variable.
.It Fl P Ar pager
@ -80,7 +85,8 @@ environment variable.
By default,
.Nm
will exit after displaying the first manual page it
finds. Using this option forces
finds.
Using this option forces
.Nm
to display all the manual pages
that match
@ -208,7 +214,8 @@ is set, its value is used as the path to search for manual pages.
If
.Ev MANROFFSEQ
is set, its value is used to determine the set of preprocessors run
before running nroff or troff. By default, pages are passed through
before running nroff or troff.
By default, pages are passed through
the table preprocessor before nroff.
.It Ev MANSECT
If
@ -218,7 +225,8 @@ is set, its value is used to determine which manual sections to search.
If
.Ev PAGER
is set, its value is used as the name of the program to use to display
the man page. By default,
the man page.
By default,
.Nm %pager%
is used.
.El

2
gnu/usr.bin/tar/tar.1
View File

@ -440,7 +440,7 @@ archive).
To archive all files from the directory
.Pa srcdir ,
which were modified
after Feb. 9th 1997, 13:00 h, use
after Feb.\& 9th 1997, 13:00 h, use
.Dl "tar -c -f backup.tar --newer-mtime 'Feb 9 13:15 1997' srcdir/"
.Pp
Other possible time specifications are