#
330449 |
|
05-Mar-2018 |
eadler |
MFC r326276:
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
|
#
326687 |
|
08-Dec-2017 |
bapt |
MFC r326527:
Only skip looking for manpages if both man directory and cat directory are not existing.
This allows man(1) to read catpages when no man directories are available at all
PR: 223559 Reported by: wosch
|
#
326685 |
|
08-Dec-2017 |
bapt |
MFC r326526:
In case man(1) found a catpage to display skip looking ".so" which is manpage only.
In case we are trying to read a catpage, the manpage variable is not defined. It results in the "cattool" having no arguments.
In case the catpage is compressed, the cattool used is "zcat" which dies if the standard input is a terminal, meaning the function calling it is exiting as if there were no ".so" In case the catpage is uncompressed, the cattool used is "zcat -f" which waits reading standard input, making the man(1) command hang.
PR: 223560 Reported by: wosch
|
#
324233 |
|
03-Oct-2017 |
bapt |
MFC r324100:
man(1): silent the output of mandoc when testing
This reduce the spam a user may face when mandoc tries to figure out if it can renders a manpage or fallback on groff(1)
Reported by: bdrewery
|
#
315993 |
|
26-Mar-2017 |
bapt |
MFC r315053-r315054, r315056
r315053: Add share/man if it exists to the MANPATH
localbase is not consistent with base for manpages: /usr/local/man vs /usr/share/man adding share/man allows to fix that inconsistency and would permit to remove tons of patches/modifications in the ports tree
r315054: Extend functionality MANPATH in man(1) to followup with apropos(1) from mandoc.
If MANPATH begins with a colon, it is appended to the default list; if it ends with a colon, it is prepended to the default list; or if it contains two adjacent colons, the standard search path is inserted between the colons. If none of these conditions are met, it overrides the standard search path.
Import the MANPATH description from mandoc into the man(1) man page
Reported by: kargl MFC after: 1 week
r315056: Remove the warning when MANPATH is set in the environment
The MANPATH environment variable behaviour is documented properly in the manpage and it now has extended to new feature that allows to make MANPATH env variable extending the default search path rather than overwriting it making the warning painful
Reported by: kargl MFC after: 1 week
|
#
302408 |
|
07-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
287987 |
|
19-Sep-2015 |
bapt |
Restore man -t for manpages rendered by mandoc
Reported by: swills
|
#
285836 |
|
24-Jul-2015 |
bapt |
inode should be different to actually mean mandocdb is in used
Sponsored by: gandi.net
|
#
285835 |
|
24-Jul-2015 |
bapt |
Fix man -k with mandocdb
If apropos(1) and whatis(1) are not hardlinks to man(1) that means the system is using mandocdb, then man -k should spawn apropos(1) and/or whatis(1) directly
Reported by: kevlo Tested by: kevlo Sponsored by: gandi.net
|
#
282980 |
|
15-May-2015 |
bapt |
Allow MANWIDTH to work with mandoc(1)
Reported by: bdrewery
|
#
279527 |
|
02-Mar-2015 |
bapt |
Update mandoc to cvs snaphot from 20150302
Use the new unsupp warning level to detect the unsupported manpages in man(1)
|
#
276643 |
|
03-Jan-2015 |
bapt |
Only manpages with fatal errors should be rendered by groff(1)
|
#
276220 |
|
25-Dec-2014 |
bapt |
mandoc -Tlocale is now the default, no need to enforce it anymore
|
#
275432 |
|
02-Dec-2014 |
bapt |
Update to mandoc cvs version as of 20141201 - Compatiblity with existing manpages has been improved - Now support ".so" directive with compressed manpages (which fixes a regression we have since we have new man(1))
|
#
274905 |
|
22-Nov-2014 |
bapt |
Fix comments
|
#
274903 |
|
22-Nov-2014 |
bapt |
Fix typo
|
#
274901 |
|
22-Nov-2014 |
bapt |
Change man(1) to use mandoc to render manpages
man(1) now first test the manpage to run with mandoc to make sure it can be rendered. In case groff cannot be found (because base has been built WITHOUT_GROFF) it recommands to install groff from the packages
|
#
245514 |
|
16-Jan-2013 |
brooks |
Remove default support for 1aout section manpages. There haven't been any since at least July 2002.
|
#
228992 |
|
30-Dec-2011 |
uqs |
Spelling fixes for usr.bin/
|
#
222653 |
|
03-Jun-2011 |
ru |
When MANCOLOR environment variable is set, enable ANSI color escapes in grotty(1). This makes it possible to view colorized manpages in color.
When MANPAGER environment variable is set, use it instead of PAGER.
Why another environment variable, one might ask? With color output enabled, both a terminal and a pager should support the ANSI color escapes. On a supporting terminal, less(1) with option -R would be such a pager, while "more -s" (the current default pager for man(1)) will show garbage. It means a different default pager is needed when color output is enabled, but many people have PAGER set customary, and it's unlikely to support ANSI color escapes, so introducing yet another variable (MANPAGER) seemed like a good option to me:
- if MANPAGER is set, use that unconditionally;
- if you disable color support (it is by default), and don't set MANPAGER, you get an old behavior: -P pager, $PAGER, "more -s", in that order;
- if you enable color support (by setting MANCOLOR), and don't set MANPAGER, we ignore PAGER which is unlikely to support ANSI color escapes, and you get: -P pager, "less -Rs", in that order;
- you might have good reasons for different man(1) and general purpose pagers;
- later versions of GNU man(1) support MANPAGER.
|
#
222650 |
|
03-Jun-2011 |
ru |
Don't use col(1) since grotty(1) never outputs reverse line feeds, and because col(1) mangles ANSI color escapes if enabled. Spaces to tabs compression is now done by passing -h to grotty(1).
Discussed with: uqs
|
#
222638 |
|
03-Jun-2011 |
ru |
Trim more when parsing MANCONFIG directive.
|
#
222635 |
|
03-Jun-2011 |
ru |
Added support for the MANWIDTH environment variable:
If set to a numeric value, used as the width manpages should be displayed. Otherwise, if set to a special value ``tty'', and output is to a terminal, the pages may be displayed over the whole width of the screen.
|
#
222601 |
|
02-Jun-2011 |
uqs |
Fix man -t by not passing grotty flags to groff when grotty is not involved.
This fixes a regression introduced with r221303.
Noticed by: jilles
|
#
221303 |
|
01-May-2011 |
uqs |
Let users' PATH decide which groff suite to pick up.
Let groff pass the -c flag to grotty, which will turn off ANSI sequences. While these are not a problem for our more/less, they get mangled by col(1) and this will result in garbage output.
This makes man(1) work together with textproc/groff, in case the user decided to delete the old groff from base (-DWITHOUT_GROFF).
|
#
220261 |
|
02-Apr-2011 |
gordon |
Overhaul locale handling.
Use locale(1) to determine the locale instead of trying to hand roll it. Correctly construct groff call based on charset and locale independently, not the mix between the two.
Submitted by: uqs@
|
#
217831 |
|
25-Jan-2011 |
uqs |
Use test(1) operators and test for the catpage not being older than the manpage.
Identical mtimes (as generated by buildworld for these files) precluded catpages from working.
Approved by: gordon
|
#
216426 |
|
14-Dec-2010 |
gordon |
Move sysctl invocation to using a variable that's fully pathed. This prevents errors for users that don't have /sbin in their PATH.
Submitted by: Max Boyarov Approved by: mentor (wes@ implicit)
|
#
216140 |
|
03-Dec-2010 |
gordon |
Add ability to decompress different format manual pages. Add support for .so directive in manual pages.
Approved by: mentor (wes@)
|
#
213507 |
|
07-Oct-2010 |
gordon |
Add the ability to display specific manual pages if passed on the commandline. This mirrors the old (undocumented) GNU man functionality. Also document this feature in the implementation notes section of the manpage.
Submitted by: arundel Approved by: wes (mentor implicit)
|
#
213470 |
|
06-Oct-2010 |
gordon |
If LANG/LC_CTYPE/LC_ALL is set and the localized man page contains a page also in the base set, the man utility when invoked with -a would display pages for each locale in the same tree:
$ LANG=en_GB.ISO8859-15 man -wa man /usr/share/man/en.ISO8859-15/man1/man.1.gz /usr/share/man/man1/man.1.gz /usr/share/man/en.ISO8859-15/man7/man.7.gz /usr/share/man/man7/man.7.gz
Use continue to break out of the loop for the current locale. This results in behavior more closely matching the old GNU man implementation:
$ LANG=en_GB.ISO8859-15 man -wa man /usr/share/man/en.ISO8859-15/man1/man.1.gz /usr/share/man/en.ISO8859-15/man7/man.7.gz
This will still search for a copy of the file in other manual path locations. If there was a /usr/local/man/man1/man.1.gz file, it would still be displayed. This is also consistent with the GNU man implementation.
Submitted by: arundel Approved by: wes (mentor implicit)
|
#
213349 |
|
02-Oct-2010 |
gordon |
Fix up whatis/apropos issue displaying all output on a single due to forgotten quotes.
Submitted by: Brandon Gooch Approved by: wes (mentor, implicit)
|
#
213317 |
|
01-Oct-2010 |
gordon |
Implementaiton of man, manpath, whatis, and apropos written entirely in sh.
Features of this new version in favor of the old one: BSD licensed -- old one is GPL. Imports configuration from /etc/man.conf and LOCALBASE/etc/man.d/*.conf allowing ports to extend the base functionality. The pluggable configuration can supplement the manual search path (retiring use.perl), add locales, and override language specific toolsets (attempt to merge the japanese/man port into the base system as much as possible).
Much effort has been made to make this version mirror the functionality of the existing implementation. For 99% of users, it should be a drop in replacement.
PR: gnu/143271, gnu/4419 Reviewed by: dougb (previous versions) Approved by: wes (mentor)
|