suckless/sbase
1
0
Fork 0
mirror of git://git.suckless.org/sbase synced 2024-12-23 07:25:07 +00:00
Code Issues Projects Releases Wiki Activity
51e432cc44
sbase/strings.1

53 lines
860 B
Groff
Raw Normal View History

Use ISO-date-format in manpages The one specified by mdoc is hard to read for non-native speakers from countries which read the date day-first (like Germany, Greece, North-Korea, Swamp,...). This is also consistent with how we generally specify dates at suckless.org.
2015-10-08 15:15:08 +00:00
.Dd 2015-10-08
remove sbase-VERSION from man page, fix sponge.1 date
2015-01-31 13:20:02 +00:00
.Dt STRINGS 1
Add .Os sbase and sed replace to .Os sbase $(VERSION) in make install
2015-01-31 19:37:03 +00:00
.Os sbase
Respect exit status in strings(1) and update manpage
2014-11-23 12:44:07 +00:00
.Sh NAME
.Nm strings
Add UTF-8-support to strings(1), add t-flag and refactor code Previously, the string-length was limited to BUFSIZ, which is an obvious deficiency. Now the buffer only needs to be as long as the user specifies the minimal string length. I added UTF-8-support, because that's how POSIX wants it and there are cases where you need this. It doesn't add ELF-barf compared to the previous implementation. The t-flag is also pretty important for POSIX-compliance, so I added it. The only trouble previously was the a-flag, but given that POSIX leaves undefined what the a-flag actually does, we set it as default and don't care about parsing ELF-headers, which has already turned out to be a security issue in GNU coreutils[0]. [0]: http://lcamtuf.blogspot.ro/2014/10/psa-dont-run-strings-on-untrusted-files.html
2015-02-17 16:04:36 +00:00
.Nd print strings of printable characters in files
Respect exit status in strings(1) and update manpage
2014-11-23 12:44:07 +00:00
.Sh SYNOPSIS
add some mandoc pages and fix some warnings - add .Os, it is mandatory. - don't redeclare .Nm when it's not needed. - fix some warnings (checked with mandoc -Tlint). - remove some leftover old stuff.
2015-01-30 20:17:58 +00:00
.Nm
strings: Default to -a
2015-02-17 13:39:17 +00:00
.Op Fl a
Add UTF-8-support to strings(1), add t-flag and refactor code Previously, the string-length was limited to BUFSIZ, which is an obvious deficiency. Now the buffer only needs to be as long as the user specifies the minimal string length. I added UTF-8-support, because that's how POSIX wants it and there are cases where you need this. It doesn't add ELF-barf compared to the previous implementation. The t-flag is also pretty important for POSIX-compliance, so I added it. The only trouble previously was the a-flag, but given that POSIX leaves undefined what the a-flag actually does, we set it as default and don't care about parsing ELF-headers, which has already turned out to be a security issue in GNU coreutils[0]. [0]: http://lcamtuf.blogspot.ro/2014/10/psa-dont-run-strings-on-untrusted-files.html
2015-02-17 16:04:36 +00:00
.Op Fl n Ar num
.Op Fl t Ar format
Respect exit status in strings(1) and update manpage
2014-11-23 12:44:07 +00:00
.Op Ar file ...
.Sh DESCRIPTION
.Nm
Add UTF-8-support to strings(1), add t-flag and refactor code Previously, the string-length was limited to BUFSIZ, which is an obvious deficiency. Now the buffer only needs to be as long as the user specifies the minimal string length. I added UTF-8-support, because that's how POSIX wants it and there are cases where you need this. It doesn't add ELF-barf compared to the previous implementation. The t-flag is also pretty important for POSIX-compliance, so I added it. The only trouble previously was the a-flag, but given that POSIX leaves undefined what the a-flag actually does, we set it as default and don't care about parsing ELF-headers, which has already turned out to be a security issue in GNU coreutils[0]. [0]: http://lcamtuf.blogspot.ro/2014/10/psa-dont-run-strings-on-untrusted-files.html
2015-02-17 16:04:36 +00:00
writes sequences of at least 4 printable characters in each
.Ar file
to stdout.
If no
.Ar file
is given,
fix mandoc warnings - sort references in SEE ALSO section to section number, name. - cols.1: proper order of sections. - wrap lines to max 79 column length.
2015-01-31 13:43:27 +00:00
.Nm
reads from stdin.
strings: Default to -a
2015-02-17 13:39:17 +00:00
.Sh OPTIONS
.Bl -tag -width Ds
.It Fl a
Add UTF-8-support to strings(1), add t-flag and refactor code Previously, the string-length was limited to BUFSIZ, which is an obvious deficiency. Now the buffer only needs to be as long as the user specifies the minimal string length. I added UTF-8-support, because that's how POSIX wants it and there are cases where you need this. It doesn't add ELF-barf compared to the previous implementation. The t-flag is also pretty important for POSIX-compliance, so I added it. The only trouble previously was the a-flag, but given that POSIX leaves undefined what the a-flag actually does, we set it as default and don't care about parsing ELF-headers, which has already turned out to be a security issue in GNU coreutils[0]. [0]: http://lcamtuf.blogspot.ro/2014/10/psa-dont-run-strings-on-untrusted-files.html
2015-02-17 16:04:36 +00:00
Scan each
.Ar file
entirely. This is the default.
.It Fl n Ar num
Print sequences of at least
.Ar num
characters. The default is 4.
.It Fl t Ar format
Prepend each string with its byte offset, with
.Ar format
being one of
.Sy d , o , x
for decimal, octal or hexadecimal numbers.
strings: Default to -a
2015-02-17 13:39:17 +00:00
.El
Add note about standards for strings.1
2014-11-23 12:46:12 +00:00
.Sh STANDARDS
Add UTF-8-support to strings(1), add t-flag and refactor code Previously, the string-length was limited to BUFSIZ, which is an obvious deficiency. Now the buffer only needs to be as long as the user specifies the minimal string length. I added UTF-8-support, because that's how POSIX wants it and there are cases where you need this. It doesn't add ELF-barf compared to the previous implementation. The t-flag is also pretty important for POSIX-compliance, so I added it. The only trouble previously was the a-flag, but given that POSIX leaves undefined what the a-flag actually does, we set it as default and don't care about parsing ELF-headers, which has already turned out to be a security issue in GNU coreutils[0]. [0]: http://lcamtuf.blogspot.ro/2014/10/psa-dont-run-strings-on-untrusted-files.html
2015-02-17 16:04:36 +00:00
The
Add note about standards for strings.1
2014-11-23 12:46:12 +00:00
.Nm
Add UTF-8-support to strings(1), add t-flag and refactor code Previously, the string-length was limited to BUFSIZ, which is an obvious deficiency. Now the buffer only needs to be as long as the user specifies the minimal string length. I added UTF-8-support, because that's how POSIX wants it and there are cases where you need this. It doesn't add ELF-barf compared to the previous implementation. The t-flag is also pretty important for POSIX-compliance, so I added it. The only trouble previously was the a-flag, but given that POSIX leaves undefined what the a-flag actually does, we set it as default and don't care about parsing ELF-headers, which has already turned out to be a security issue in GNU coreutils[0]. [0]: http://lcamtuf.blogspot.ro/2014/10/psa-dont-run-strings-on-untrusted-files.html
2015-02-17 16:04:36 +00:00
utility is compliant with the
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 16:22:48 +00:00
.St -p1003.1-2013
Add UTF-8-support to strings(1), add t-flag and refactor code Previously, the string-length was limited to BUFSIZ, which is an obvious deficiency. Now the buffer only needs to be as long as the user specifies the minimal string length. I added UTF-8-support, because that's how POSIX wants it and there are cases where you need this. It doesn't add ELF-barf compared to the previous implementation. The t-flag is also pretty important for POSIX-compliance, so I added it. The only trouble previously was the a-flag, but given that POSIX leaves undefined what the a-flag actually does, we set it as default and don't care about parsing ELF-headers, which has already turned out to be a security issue in GNU coreutils[0]. [0]: http://lcamtuf.blogspot.ro/2014/10/psa-dont-run-strings-on-untrusted-files.html
2015-02-17 16:04:36 +00:00
specification.
.Pp
The
.Op Fl t
output format has been changed from "%F %s" to "%8lF: %s", with
.Sy F
being one of
.Sy d , o , x .
Reference in New Issue Copy Permalink