[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7
From: |
Ralph Corderoy |
Subject: |
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7 |
Date: |
Sun, 26 Nov 2017 13:03:46 +0000 |
Hi Steven,
> Well, if you don't use mhfixmsg, then probably. :-) I'll have a
> look, though I don't think it will be something obvious.
I think it was something obvious. Can you add `-P' to the pwd below in
your copy and see if it passes? I suspect your /big is a symlink. :-)
Searching for that `start_test' string will find just that test.
diff --git test/mhfixmsg/test-mhfixmsg test/mhfixmsg/test-mhfixmsg
index c2070c51..e37b56a3 100755
--- test/mhfixmsg/test-mhfixmsg
+++ test/mhfixmsg/test-mhfixmsg
@@ -1727,7 +1727,7 @@ check "`mhpath last`" "$actual" 'keep first'
start_test "pass through message with relative folder path with parse
error"
#### Factor out leading portion of current folder path and make it
relative.
-pwd=`pwd`
+pwd=`pwd -P`
set +e
run_prog mhfixmsg +./`mhpath | sed "s%^$pwd/%%"` last -out - >"$actual"
2>/dev/null
set -e
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7, Steven Winikoff, 2017/11/26