ENUM(1) | enum 1.1 | ENUM(1) |
enum - seq- and jot-like enumerator
enum [ OPTIONS ] LEFT .. COUNTx STEP .. RIGHT
enum [ OPTIONS ] LEFT STEP RIGHT
enum [ OPTIONS ] LEFT RIGHT
enum [ OPTIONS ] RIGHT
...
enum enumerates values (numbers) from LEFT to RIGHT adding/subtracting STEP each time. If STEP is not provided a value is implied. No more than COUNT values are printed. Before printing, values are passed through a formatter. Please see OPTIONS for details on controlling the formatter or EXAMPLES for use cases.
Further enum usage details are covered in USAGE IN DETAIL.
for i in $(enum -e 1 20); do
touch file_${i} done
number=$(enum --random 3 .. 10)
instead of native Bash like
f() { min=$1; max=$2; echo $((RANDOM * (max - min + 1) / 32767 + min)); } number=$(f 3 10)
enum -f '[%3i] "%c"' 0 127
-r, --random
-i, --seed=NUMBER
-b, --dumb=TEXT
-c, --characters
-e, --equal-width
-f, --format=FORMAT
FORMAT is subject to processing of C escape sequences (e.g. "\n" makes a newline). If FORMAT does not contain any placeholders, enum will print FORMAT repeatedly. In contrast, jot would have appended the number’s value instead. To make numbers appear at the end with enum, adjust FORMAT appropriately.
-l, --line
-n, --omit-newline
-p, --precision=COUNT
-s, --separator=TEXT
-t, --terminator=TEXT
-w, --word=FORMAT
-z, --zero, --null
-h, --help
-V, --version
The logic of enum's command line parameters is:
enum [ OPTIONS ] LEFT .. COUNTx STEP .. RIGHT
Four arguments are involved:
Not all four arguments are needed, though specifying all four is possible. For a list of all valid combinations see VALID COMBINATIONS below. Details on derivation of defaults are addressed in DERIVATION OF DEFAULTS.
With four arguments:
With three arguments:
With two arguments:
With one argument:
With less than three arguments, defaults apply. Details are described in DERIVATION OF DEFAULTS below.
Technically, more use cases are possible. For instance, COUNTx STEP .. RIGHT is unambiguous since the order of arguments is fixed. Yet, "enum 3x 4 .. 10" reads a lot like "3 values between 4 and 10" while it actually would mean "3 values up to 10 in steps of 4". In order to keep enum’s user interface as intuitive as possible, cases which could lead to misunderstandings are not implemented.
AUTO-SELECTION OF PRECISION
enum distinguishes between "2", "2.0", "2.00" and so on:
# enum 1 2 1 2 # enum 1 2.0 1.0 1.1 [..] 1.9 2.0
Also, if the derived step has more decimal places than the specified values for LEFT and RIGHT, the output precision will be raised to that of the step value:
# enum 1 .. 3x .. 2 1.0 1.5 2.0
A specified precision always takes precedence, though:
# enum -p 2 1 .. 3x .. 2 1.00 1.50 2.00
ARGUMENT DEFAULTS
In general, three arguments are needed; any three imply the fourth. This equation brings them together:
LEFT + (COUNT - 1) * STEP = RIGHT
If you specify less than three of them (see VALID COMBINATIONS), the unspecified ones are derived or set to their defaults:
Obviously, if COUNT is set to zero (0x), enum will output nothing, regardless of the other arguments.
DERIVATION OF LEFT
In general, LEFT defaults to 1:
# enum .. 3 1 2 3
If STEP and RIGHT is given, it is derived as
LEFT = RIGHT - STEP * floor(RIGHT / STEP)
# enum .. 4 .. 10 2 6 10
If, in addition to STEP and RIGHT, COUNT is given, it is derived as:
LEFT = RIGHT - (COUNT - 1) * STEP
# enum .. 2x 4 .. 10 6 10
When a custom step is requested, values are produced as follows:
value[0] = LEFT + 0 * STEP value[1] = LEFT + 1 * STEP .. value[i] = LEFT + i * STEP
Otherwise, to avoid imprecision adding up, values are produced as follows:
value[0] = LEFT + (RIGHT - LEFT) / (COUNT - 1) * 0 value[1] = LEFT + (RIGHT - LEFT) / (COUNT - 1) * 1 .. value[i] = LEFT + (RIGHT - LEFT) / (COUNT - 1) * i
Production stops when either COUNT values have been produced or RIGHT has been reached, whichever hits first. When all four values are given in perfect match they hit at the same time.
Basically, random mode differs in these regards:
This section covers these differences in detail.
In random mode only one value is produced, by default:
# enum 1 4 1 2 3 4 # enum -r 1 4 3
By specifying COUNT you can produce more values at a time:
# enum -r 1 .. 3x .. 4 2 1 3
When you need increasing numbers up to a certain maximum (say 10), each separated by a certain step (say 4) you can let enum calculate the needed starting value for you:
# enum .. 4 .. 10 2 6 10
In random mode LEFT is never calculated and defaults to 1 (one):
# enum -r .. 5x 4 .. 10 1 1 9 1 5
In general, enum supports running towards infinity:
# enum 1 .. 2.0 .. 1.0 3.0 5.0 [..]
However, in random mode enum would now produce random numbers from 1 to infinity (or a big number like FLT_MAX from <float.h>), which we have decided against.
enum is a fusion of GNU seq and jot, feature-wise. At the core both tools print sequences of numbers. GNU seq has a clean interface but very limited functionality. jot on the other hand offers more advanced features, like producing random numbers, at the cost of a rather unfriendly interface.
With enum we try to offer a tool with the power of jot and a usable, easily memorable interface. enum is licensed under a BSD license and written in C89 for maximum portability.
The following sections take a look at the differences in detail.
Using enum instead of jot offers two main advantages:
As of 2010-10-03, jot implementations still differ subtly between DragonFlyBSD, FreeBSD, MirOS BSD, NetBSD, OpenBSD, and OS X. For instance the command jot - 0 5 produces
0 1 2 3 4 5
0 1 2 [..] 97 98 99
0 0 0 0 0 0 0 0 0 0 1 1 [..] 4 4 5 5 5 5 5 5 5 5 5 5
Basically, the full feature set of jot plus a few enhancements is contained in enum. Names of parameters have been retained for increased compatibility, e.g. -p 2 works with enum as it does with jot:
# jot -p 2 3 1.00 2.00 3.00 # enum -p 2 3 1.00 2.00 3.00
Please see OPTIONS above for further details.
The extra features that enum offers over jot include:
MORE MEMORABLE COMMAND LINE USAGE
In order to produce 3 random numbers between 1 and 10 (inclusively), you would run
jot -r 3 1 10
with jot. We find these alternative calls to enum more intuitive:
enum -r 1 .. 3x .. 10 enum -r 1 3x 10
CUSTOM RESOLUTION OF RANDOM
With enum you can specify that the possible values to be randomly selected from have a particular spacing. These two cases illustrate the difference between a gap of 2 and 3:
# enum -r 4 .. 100x 2 .. 10 | sort -u -n 4 6 8 10 # enum -r 4 .. 100x 3 .. 10 | sort -u -n 4 7 10
SUPPORT FOR SEVERAL PLACEHOLDERS IN FORMAT STRINGS
jot on DragonFlyBSD, FreeBSD, MirOS BSD, OpenBSD, and OS X:
# jot -w %g%g 3 jot: too many conversions
jot on NetBSD:
# jot -w %g%g 3 jot: unknown or invalid format `%g%g'
enum on any platform:
# enum -f %g%g 3 11 22 33
SUPPORT FOR ESCAPE SEQUENCES
None of the jot implementations we tested (DragonFlyBSD, FreeBSD, MirOS BSD, NetBSD, OpenBSD, and OS X) supports escape sequences, say "\n", in FORMAT:
# jot -w '%g\x41' 1 1\x41
enum is able to unescape "\x41" properly:
# enum -w '%g\x41' 1 1A
On a side note, "\x25" produces a literal "%"; it does not make a placeholder:
# enum -w '%g \x25g' 1 1 %g
NULL BYTES AS SEPARATOR
When using format strings containing spaces, you may run into trouble in contexts like for loops or xargs: spaces are treated as separators which breaks up your strings in pieces:
# enum -f 'sheep number %d' 2 | xargs -n 1 echo sheep number 1 sheep number 2
To prevent this, you could pass --null to both enum and xargs:
# enum --null -f 'sheep number %d' 2 | xargs --null -n 1 echo sheep number 1 sheep number 2
HANDLING OF FORMATS WITHOUT PLACEHOLDERS
In contrast to jot, enum does not append the current value if the formatting string does not contain a placeholder. Behavior of jot:
# jot 3 -w test_ test_1 test_2 test_3
Behavior of enum:
# enum -w test_ 3 test_ test_ test_
In order to achieve jot’s output with enum, you should manually append a placeholder:
# enum -w test_%d 3 test_1 test_2 test_3
NON-NUMBER VALUES FOR LEFT AND RIGHT
enum does not support using ASCII characters instead of their numerical values (e.g. "A" for 65) for LEFT and RIGHT. With jot you can do:
# jot 3 A 65 66 67
Inconsistently,
# jot 3 0 0 1 2
jot does not interpret "0" as the ASCII character with code 48. We have no intention of duplicating this mix, at the moment.
Basically, enum's usage is backwards-compatible to that of GNU seq.
The extra features enum offers over GNU seq include:
RANDOM NUMBER MODE
enum supports output of constrained random numbers, e.g.
enum -r 4 .. 3x 2.0 .. 11
produces three (possibly duplicate) random numbers from the set {4.0, 6.0, 8.0, 10.0}.
SUPPORT FOR INVERSE ORDERING
In contrast to GNU seq, enum supports enumerating decreasing values:
# seq 3 1 # enum 3 1 3 2 1
SUPPORT FOR SEVERAL PLACEHOLDERS IN FORMAT STRINGS
# seq -f %g%g 3 seq: format `%g%g' has too many % directives # enum -f %g%g 3 11 22 33
SUPPORT FOR ESCAPE SEQUENCES
GNU seq does not support escape sequences, say "\n", in FORMAT:
# seq -f '%g\x41' 1 1\x41
In contrast, some of the other seq implementations around do. These three behaviours can be observed (as of 2010-10-25):
seq of Plan 9, 9base, and GNU seq:
# seq -f '%g\x41' 3 1\x41 2\x41 3\x41
seq on FreeBSD and NetBSD:
# seq -f '%g\x41' 1 1A 2A 3A
seq on DragonFlyBSD:
# seq -f '%g\x41' 1 1A3 2A3 3A3
enum unescape "\x41" to "A" as well:
# enum -f '%g\x41' 3 1A 2A 3A
On a side note, "\x25" produces a literal "%"; it does not make a placeholder:
# enum -f '%g \x25g' 1 1 %g
OMITTING FINAL NEWLINE
By specifying -n as a parameter, you can make enum omit the trailing newline.
GNU seq’s --equal-width shortcut -w conflicts with jot’s -w word. We chose to make -e the shortcut for --equal-width in enum, instead.
Also, while GNU seq is licensed under GPL v3 or later, enum is licensed under the New BSD license.
Elias Pipping, Andreas Gunschl, Justin B. Rye, David Prevot, Kamil Dudka, Michael Bienia
Jan Hauke Rahm <jhr@debian.org>
Sebastian Pipping <sping@gentoo.org>
Main web site: https://fedorahosted.org/enum/
Gitweb: http://git.fedorahosted.org/git/?p=enum.git
02/02/2012 | enum 1.1 |