Tighten MANPATH test

This is to fix tests on Travis, since that stores the commit message in an environment variable.

`env | grep MANPATH` of course picks it up and generates unwanted output.

Yes.
This commit is contained in:
Fabian Homborg 2017-04-18 22:42:38 +02:00
parent ffbda7fe64
commit c0d80ab996

View file

@ -272,6 +272,6 @@ env DISPLAY="localhost:0.0" ../test/root/bin/fish -c 'echo Elements in DISPLAY:
# Exported arrays should use record separator, with a few exceptions. So we can use an arbitrary variable for this.
env FOO=one\x1etwo\x1ethree\x1efour ../test/root/bin/fish -c 'echo Elements in FOO: (count $FOO)'
# some must use colon separators!
set -lx MANPATH man1 man2 man3 ; env | grep MANPATH
set -lx MANPATH man1 man2 man3 ; env | grep '^MANPATH='
true