suckless/sbase
1
0
Fork 0
mirror of git://git.suckless.org/sbase synced 2024-12-22 23:13:44 +00:00
Code Issues Projects Releases Wiki Activity
d458fa2c7b
sbase/getconf.1

61 lines
849 B
Groff
Raw Normal View History

fix: update man pages to standard mdoc date format When viewing sbase's man pages the date displayed at the bottom is the current date rather than the date entered in the <program>.1 file. According to this: https://mandoc.bsd.lv/mdoc/details/date.html The traditional man date format used by sbase (.Dd year-month-day) is no longer recommended and no longer supported by GNU troff or Heirloom Docs and as a result the current date is displayed instead. Although this format is still accepted by mandoc for backward compatibility. For portability it states the standard mdoc date format should be used instead: .Dd month day, year I applied the following patch to sbase's last commit b30fb56 and it fixes the issue.
2024-09-07 22:57:31 +00:00
.Dd October 8, 2015
Add getconf(1) The logic is simple, it's just a pain in the ass to fill the data-structures. Some lines had to be commented out, as glibc/musl apparently have not fully implemented the mandatory variables for the 2013 corrigendum of POSIX 2008. Also added a manpage and the necessary entries in README. I also removed it from the TODO.
2015-09-30 22:59:40 +00:00
.Dt GETCONF 1
.Os sbase
.Sh NAME
.Nm getconf
.Nd get configuration values
.Sh SYNOPSIS
.Nm
.Op Fl v Ar spec
.Ar var
.Ar [path]
.Sh DESCRIPTION
.Nm
writes the value of the variable
.Ar var
to stdout.
.sp
If
.Ar path
is given,
.Ar var
is matched against configuration values from
.Xr pathconf 3 .
If
.Ar path
is not given,
.Ar var
is matched against configuration values from
.Xr sysconf 3 ,
.Xr confstr 3
and limits.h (Minimum and Maximum).
.sp
If
.Ar var
getconf: Report invalid variables as errors Printing `undefined` to stdout means that the variable is valid but not set. Instead, report an error in this case. linux 4.13 appends the result of `getconf LFS_CFLAGS` to HOSTCFLAGS, even if it prints `undefined`. This is arguably a bug in the Makefile, but even so, getconf shouldn't report that unsupported variables are valid.
2017-09-03 22:39:47 +00:00
is not defined,
Add getconf(1) The logic is simple, it's just a pain in the ass to fill the data-structures. Some lines had to be commented out, as glibc/musl apparently have not fully implemented the mandatory variables for the 2013 corrigendum of POSIX 2008. Also added a manpage and the necessary entries in README. I also removed it from the TODO.
2015-09-30 22:59:40 +00:00
.Nm
writes "undefined" to stdout.
.Sh OPTIONS
.Bl -tag -width Ds
.It Fl v Ar spec
Ignored.
.El
.Sh EXIT STATUS
.Bl -tag -width Ds
.It 0
.Ar var
was matched and its value written successfully.
.It 1
An error occured or
.Ar var
getconf: Report invalid variables as errors Printing `undefined` to stdout means that the variable is valid but not set. Instead, report an error in this case. linux 4.13 appends the result of `getconf LFS_CFLAGS` to HOSTCFLAGS, even if it prints `undefined`. This is arguably a bug in the Makefile, but even so, getconf shouldn't report that unsupported variables are valid.
2017-09-03 22:39:47 +00:00
was invalid.
getconf.1: fix: end list (El)
2015-10-09 23:18:24 +00:00
.El
Add getconf(1) The logic is simple, it's just a pain in the ass to fill the data-structures. Some lines had to be commented out, as glibc/musl apparently have not fully implemented the mandatory variables for the 2013 corrigendum of POSIX 2008. Also added a manpage and the necessary entries in README. I also removed it from the TODO.
2015-09-30 22:59:40 +00:00
.Sh STANDARDS
The
.Nm
utility is compliant with the
.St -p1003.1-2013
specification except from the
.Op Fl v
flag.
Reference in New Issue Copy Permalink