diff options
author | 2020-02-24 21:16:31 +0000 | |
---|---|---|
committer | 2020-02-24 21:16:31 +0000 | |
commit | 83ad1abc9ffe08ed430d83909fe1297738f5c224 (patch) | |
tree | 186ffcaf1c2b771cf58d1837352354e08d5ed7b4 /regress/tbl/mod/misalign.out_ascii | |
parent | 34bee6097a58670fc58c4e6bcf0516bda8db47d7 (diff) | |
download | mandoc-83ad1abc9ffe08ed430d83909fe1297738f5c224.tar.gz mandoc-83ad1abc9ffe08ed430d83909fe1297738f5c224.tar.zst mandoc-83ad1abc9ffe08ed430d83909fe1297738f5c224.zip |
Marc Espie reported that "man p*ipc" displayed the perlipc(1) manual.
The reason was that as a last resort when failing to find a page
name in mandoc.db(5) or at a few well well-defined fully qualified
file names, man(1) uses glob(3) to look for candidate files in
relevant directories, because some operating systems have weird
file name extensions, for example pcap.3pcap and BF_set_key.3ssl
on Linux. But during that globbing, the metacharacters "*?[" need
to be escaped in the name, section, and path supplied by the user,
or you would get weird false positives and misleading warning
messages and would be unable to use the fallback for path or file
names that actually contain an opening bracket.
Feedback and OK espie@.
Diffstat (limited to 'regress/tbl/mod/misalign.out_ascii')
0 files changed, 0 insertions, 0 deletions