FRIGN
eee98ed3a4
Fix coding style
...
It was about damn time. Consistency is very important in such a
big codebase.
2014-11-13 18:08:43 +00:00
sin
0c5b7b9155
Stop using EXIT_{SUCCESS,FAILURE}
2014-10-02 23:46:59 +01:00
Hiltjo Posthuma
fab4b384e7
use agetline instead of agets
...
also use agetline where fgets with a static buffer was used previously.
Signed-off-by: Hiltjo Posthuma <hiltjo@codemadness.org>
2014-06-01 18:03:10 +01:00
Hiltjo Posthuma
953ebf3573
code style
...
Signed-off-by: Hiltjo Posthuma <hiltjo@codemadness.org>
2014-06-01 18:02:30 +01:00
sin
cb005c150d
Fix naming covention for uniq(1)
2014-01-20 10:49:28 +00:00
sin
b5a511dacf
Exit with EXIT_SUCCESS/EXIT_FAILURE instead of 0 and 1
...
Fixed for consistency purposes.
2013-10-07 16:44:22 +01:00
sin
83c2c3d1f5
Add 'not implemented' errors for unimplemented flags
...
These used to live in TODO but we got rid off them. Make sure
we keep track of what we want to support by printing a message
when those flags are unimplemented.
2013-10-05 13:51:45 +01:00
stateless
7216a53a7e
Remove unnecessary exit(1) in usage()
...
Signed-off-by: Christoph Lohmann <20h@r-36.net>
2013-06-19 19:58:19 +02:00
Christoph Lohmann
4d38f60685
Eliminating the getopt disgrace.
2013-06-14 20:20:47 +02:00
Christoph Lohmann
52d39e35c2
The style inquisition on basename.
2013-03-05 21:35:55 +01:00
Robert Ransom
a16f603b20
uniq: Lobotomize for POSIX-subset compatibility
...
POSIX uniq(1) is required to write to its second argument,
if one is given.
The multiple-input feature I accidentally added might be useful,
but users and scripts who rely on it would be put at risk for data loss
if they ever run into a POSIX uniq(1).
2012-05-21 23:33:36 +00:00
Robert Ransom
85efaad43b
uniq: Initial commit
2012-05-21 23:24:28 +00:00
