[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #56221] groffer does not support colon-specific values in MANPATH
From: |
anonymous |
Subject: |
[bug #56221] groffer does not support colon-specific values in MANPATH |
Date: |
Fri, 26 Apr 2019 01:59:19 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0 |
URL:
<https://savannah.gnu.org/bugs/?56221>
Summary: groffer does not support colon-specific values in
MANPATH
Project: GNU troff
Submitted by: None
Submitted on: Fri 26 Apr 2019 05:59:17 AM UTC
Category: None
Severity: 3 - Normal
Item Group: Incorrect behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Details:
The MANPATH environment variable may be prefixed or suffixed by a bare colon
(:) character or contains a double colon (::). These colon characters have the
meaning to insert respectively before, after or between the man directory list
determined from the content of the man configuration files.
See the description of the MANPATH variable in the manpath man page
<http://man7.org/linux/man-pages/man1/manpath.1.html#ENVIRONMENT> for the
complete reference.
The *groffer* tool does not support these colon-specific values in MANPATH and
ends in error when facing them:
$ echo $MANPATH
/usr/share/man/mpich-x86_64:
$ man -w ls
/usr/share/man/man1/ls.1.gz
$ groffer ls
main_do_fileargs(): ls is neither a file nor a man page; at
/usr/share/groff/1.22.3/groffer/main_subs.pl line 1548.
groffer: empty input
$ groffer -v
groffer 2.2.5 is part of groff version 1.22.3.
GNU groff and groffer come with ABSOLUTELY NO WARRANTY.
You may redistribute copies of groff and its subprograms
under the terms of the GNU General Public License.
Looking in _/usr/share/groff/1.22.3/groffer/man.pl_, the _man_setup()_
function should be adapted maybe to only rely on the output of the *manpath*
command as this command could return the manpath system configuration needed
when MANPATH is prefixed/suffixed by a colon character or contains a double
colon.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56221>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #56221] groffer does not support colon-specific values in MANPATH,
anonymous <=