mirror of
https://github.com/Ponce/slackbuilds
synced 2024-11-22 19:44:21 +01:00
Various: more whitespace cleanups
Reformatted all of my READMEs that weren't wrapped at column 72. Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
This commit is contained in:
slakmagik
Robby Workman
parent
1d0419e752
commit
6015cd2f1e
11 changed files with 88 additions and 87 deletions
|
|
@ -1,13 +1,12 @@
|
|||
shntool is a command-line utility to view and/or modify WAVE data
|
||||
and properties. It runs in several different operating modes, and
|
||||
supports various lossless audio formats.
|
||||
shntool is a command-line utility to view and/or modify WAVE data and
|
||||
properties. It runs in several different operating modes, and supports
|
||||
various lossless audio formats.
|
||||
|
||||
shntool is comprised of three parts - its core, mode modules, and
|
||||
format modules. This helps to make the code easier to maintain, as
|
||||
well as aid other programmers in developing new functionality. The
|
||||
distribution archive contains a file named 'modules.howto' that
|
||||
describes how to create a new mode or format module, for those so
|
||||
inclined.
|
||||
shntool is comprised of three parts - its core, mode modules, and format
|
||||
modules. This helps to make the code easier to maintain, as well as aid
|
||||
other programmers in developing new functionality. The distribution
|
||||
archive contains a file named 'modules.howto' that describes how to
|
||||
create a new mode or format module, for those so inclined.
|
||||
|
||||
If you wish to have shntool support shorten, you should install
|
||||
shorten (also available from SlackBuilds.org) first.
|
||||
If you wish to have shntool support shorten, you should install shorten
|
||||
(also available from SlackBuilds.org) first.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,8 @@
|
|||
shorten reduces the size of waveform files (such as audio) using
|
||||
Huffman coding of prediction residuals and optional additional
|
||||
quantisation. In lossless mode the amount of compression obtained
|
||||
depends on the nature of the waveform. Those composing of low
|
||||
frequencies and low amplitudes give the best compression, which may
|
||||
be 2:1 or better. Lossy compression operates by specifying a minimum
|
||||
acceptable segmental signal to noise ratio or a maximum bit rate. Lossy
|
||||
compression operates by zeroing the lower order bits of the waveform,
|
||||
so retaining waveform shape.
|
||||
shorten reduces the size of waveform files (such as audio) using Huffman
|
||||
coding of prediction residuals and optional additional quantisation. In
|
||||
lossless mode the amount of compression obtained depends on the nature
|
||||
of the waveform. Those composing of low frequencies and low amplitudes
|
||||
give the best compression, which may be 2:1 or better. Lossy compression
|
||||
operates by specifying a minimum acceptable segmental signal to noise
|
||||
ratio or a maximum bit rate. Lossy compression operates by zeroing the
|
||||
lower order bits of the waveform, so retaining waveform shape.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,20 @@
|
|||
Root-tail displays a given file anywhere on your X11 root window, i.e. it is
|
||||
kind of tail -f for multiple files using your desktop background as output
|
||||
window.
|
||||
Root-tail displays a given file anywhere on your X11 root window, i.e.
|
||||
it is kind of tail -f for multiple files using your desktop background
|
||||
as output window.
|
||||
|
||||
It has configurable colors, fonts, wrapping, justifying, continuation
|
||||
indicators, geometry, and more and can interleave multiple files also making
|
||||
it a sort of multi-tail.
|
||||
indicators, geometry, and more and can interleave multiple files also
|
||||
making it a sort of multi-tail.
|
||||
|
||||
For example:
|
||||
root-tail -g 800x250+100+50 -font 10x20 /var/log/messages,green \
|
||||
-font 12x24 /var/log/secure,red,'ALERT'
|
||||
|
||||
By default root-tail doesn't seem to work on XFCE. You need to explicitly
|
||||
specify the ID of the display to use it (by using the "-id" flag of
|
||||
root-tail). Use the xprop command to find the active root display, and run
|
||||
this through the cut command to strip out the ID number for insertion into the
|
||||
root-tail `-id` field.
|
||||
By default root-tail doesn't seem to work on XFCE. You need to
|
||||
explicitly specify the ID of the display to use it (by using the "-id"
|
||||
flag of root-tail). Use the xprop command to find the active root
|
||||
display, and run this through the cut command to strip out the ID number
|
||||
for insertion into the root-tail `-id` field.
|
||||
|
||||
It looks a little something like this:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
Xdialog is designed to be a drop in replacement for the "dialog" or "cdialog"
|
||||
programs. It converts any terminal based program into a program with an
|
||||
X-windows interface. The dialogs are easier to see and use while adding even
|
||||
more functionalities (e.g. with the treeview, the file selector, the edit box,
|
||||
the range box, the help button/box). Because Xdialog uses GTK+, it will also
|
||||
match your desktop theme.
|
||||
Xdialog is designed to be a drop in replacement for the "dialog" or
|
||||
"cdialog" programs. It converts any terminal based program into a
|
||||
program with an X-windows interface. The dialogs are easier to see and
|
||||
use while adding even more functionalities (e.g. with the treeview, the
|
||||
file selector, the edit box, the range box, the help button/box).
|
||||
Because Xdialog uses GTK+, it will also match your desktop theme.
|
||||
|
||||
If you wish to have NLS support, pass 'NLS=enable' to the SlackBuild. Xdialog
|
||||
is a GTK"1" program but may optionally be compiled against GTK2. The developer
|
||||
recommends against this but you may enable it (as I do) with 'GTK2=enable'.
|
||||
If you wish to have NLS support, pass 'NLS=enable' to the SlackBuild.
|
||||
Xdialog is a GTK"1" program but may optionally be compiled against GTK2.
|
||||
The developer recommends against this but you may enable it (as I do)
|
||||
with 'GTK2=enable'.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Gtkdialog is a small utility for fast and easy GUI building. It can be
|
||||
used to create dialog boxes for almost any interpreted and compiled
|
||||
programs which is a very attractive feature since the developer
|
||||
does not have to learn various GUI languages for the miscellaneous
|
||||
programming languages.
|
||||
programs which is a very attractive feature since the developer does not
|
||||
have to learn various GUI languages for the miscellaneous programming
|
||||
languages.
|
||||
|
|
|
|||
|
|
@ -1,18 +1,19 @@
|
|||
mtPaint is a painting program which Mark Tyler developed from scratch so he
|
||||
could easily create pixel art and manipulate digital photos.
|
||||
mtPaint is a painting program which Mark Tyler developed from scratch so
|
||||
he could easily create pixel art and manipulate digital photos.
|
||||
|
||||
It uses the GTK+ toolkit (version 1 or 2) and runs on PC's via the GNU/Linux or
|
||||
Windows operating systems. Due to its efficient design it can run on older PC
|
||||
hardware (e.g. a 200MHz CPU and 16MB of free RAM).
|
||||
It uses the GTK+ toolkit (version 1 or 2) and runs on PC's via the
|
||||
GNU/Linux or Windows operating systems. Due to its efficient design it
|
||||
can run on older PC hardware (e.g. a 200MHz CPU and 16MB of free RAM).
|
||||
|
||||
mtPaint is free software, which means you are able to freely use, modify and
|
||||
distribute it according to the GNU General Public License.
|
||||
mtPaint is free software, which means you are able to freely use, modify
|
||||
and distribute it according to the GNU General Public License.
|
||||
|
||||
Currently mtPaint is maintained by Dmitry Groshev.
|
||||
|
||||
If you want internationalization, pass INTL=yes to the SlackBuild.
|
||||
If you want this built as a gtk1 app, pass GTK1=yes; else it will be gtk2.
|
||||
If you want gtk{1,2} widgets then pass TKWIDGETS=yes; else it will use its own
|
||||
file and color selector widgets.
|
||||
If you want the handbook installed (about a three meg html book) then pass
|
||||
HANDBOOK=yes.
|
||||
If you want this built as a gtk1 app, pass GTK1=yes; else it will be
|
||||
gtk2.
|
||||
If you want gtk{1,2} widgets then pass TKWIDGETS=yes; else it will use
|
||||
its own file and color selector widgets.
|
||||
If you want the handbook installed (about a three meg html book) then
|
||||
pass HANDBOOK=yes.
|
||||
|
|
|
|||
|
|
@ -1,18 +1,19 @@
|
|||
dwdiff is a front-end for the diff program that operates at the word level
|
||||
instead of the line level. It is different from wdiff in that it allows the
|
||||
user to specify what should be considered whitespace, and in that it takes an
|
||||
optional list of characters that should be considered delimiters. Delimiters
|
||||
are single characters that are treated as if they are words, even when there is
|
||||
no whitespace separating them from preceding words or delimiters. dwdiff is
|
||||
mostly commandline compatible with wdiff. Only the --autopager, --terminal and
|
||||
--avoid-wraps options are not supported.
|
||||
dwdiff is a front-end for the diff program that operates at the word
|
||||
level instead of the line level. It is different from wdiff in that it
|
||||
allows the user to specify what should be considered whitespace, and in
|
||||
that it takes an optional list of characters that should be considered
|
||||
delimiters. Delimiters are single characters that are treated as if they
|
||||
are words, even when there is no whitespace separating them from
|
||||
preceding words or delimiters. dwdiff is mostly commandline compatible
|
||||
with wdiff. Only the --autopager, --terminal and --avoid-wraps options
|
||||
are not supported.
|
||||
|
||||
The default output from dwdiff is the new text, with the deleted and inserted
|
||||
parts annotated with markers. Command line options are available to change both
|
||||
what is printed, and the markers.
|
||||
The default output from dwdiff is the new text, with the deleted and
|
||||
inserted parts annotated with markers. Command line options are
|
||||
available to change both what is printed, and the markers.
|
||||
|
||||
If you wish to have de localization or nl localization and manpages, pass
|
||||
'NLS="de nl"' or either one to the SlackBuild.
|
||||
If you wish to have de localization or nl localization and manpages,
|
||||
pass 'NLS="de nl"' or either one to the SlackBuild.
|
||||
|
||||
If you wish to enable the handling of Unicode text, install the icu4c library
|
||||
and pass "UNICODE=yes" to the SlackBuild.
|
||||
If you wish to enable the handling of Unicode text, install the icu4c
|
||||
library and pass "UNICODE=yes" to the SlackBuild.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
gcolor2 is a simple color selector that was originally based on gcolor, ported
|
||||
to use GTK+2, and now has a completely new UI.
|
||||
gcolor2 is a simple color selector that was originally based on gcolor,
|
||||
ported to use GTK+2, and now has a completely new UI.
|
||||
|
||||
It is also completely desktop-independent, requiring only GTK2.
|
||||
|
||||
It includes the usual color wheel method, input box method, color-picker
|
||||
method, and can store colors, coming with the contents of rgb.txt already
|
||||
stored.
|
||||
method, and can store colors, coming with the contents of rgb.txt
|
||||
already stored.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
rlwrap is a 'readline wrapper' that uses the GNU readline library
|
||||
to allow the editing of keyboard input for any other command. Input
|
||||
history is remembered across invocations, separately for each command;
|
||||
history completion and search work as in bash and completion word
|
||||
lists can be specified on the command line.
|
||||
rlwrap is a 'readline wrapper' that uses the GNU readline library to
|
||||
allow the editing of keyboard input for any other command. Input history
|
||||
is remembered across invocations, separately for each command; history
|
||||
completion and search work as in bash and completion word lists can be
|
||||
specified on the command line.
|
||||
|
||||
If you wish to have history and completion files kept somewhere other
|
||||
than $HOME, you will need to set RLWRAP_HOME to the desired path and
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Good-old rdate date- and time-setting software implementing RFC
|
||||
868 (inetd time) and RFC 2030 (SNTP/NTP) protocols. An independent
|
||||
package of the OpenBSD's rdate program.
|
||||
Good-old rdate date- and time-setting software implementing RFC 868
|
||||
(inetd time) and RFC 2030 (SNTP/NTP) protocols. An independent package
|
||||
of the OpenBSD's rdate program.
|
||||
|
||||
An alternative to netdate and ntpd/ntpdate.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
dtach is a tiny program that emulates the detach feature of screen,
|
||||
allowing you to run a program in an environment that is protected
|
||||
from the controlling terminal and attach to it later. dtach does not
|
||||
keep track of the contents of the screen, and thus works best with
|
||||
programs that know how to redraw themselves. It is designed to be
|
||||
transparent and un-intrusive; it avoids interpreting the input and
|
||||
output between attached terminals and the program under its control.
|
||||
allowing you to run a program in an environment that is protected from
|
||||
the controlling terminal and attach to it later. dtach does not keep
|
||||
track of the contents of the screen, and thus works best with programs
|
||||
that know how to redraw themselves. It is designed to be transparent and
|
||||
un-intrusive; it avoids interpreting the input and output between
|
||||
attached terminals and the program under its control.
|
||||
|
||||
dtach does not, however, have the other features of screen, such as its
|
||||
support of multiple terminals or its terminal emulation support. This
|
||||
|
|
|
|||
Loading…
Reference in a new issue