Shame on you, Jeff. You hijacked Anton's thread on upper case handling,
to ask this completely unrelated question. Now, when I find a few
moments to respond, I have to remember which thread you hijacked,
because ThunderBird has buried your original query in a collapsed
thread, where I can't readi
James K. Lowden wrote:
It does make you wish for which(1) or "command -v" for Windows, doesn't
it?
I have which(1), but it doesn't help here ...
I think your plan is reasonable.
The alternative would be to push on configure.guess and assume the
path separator for any form of Windows is
On Thu, 24 Nov 2011 19:14:00 -0800
Jeff Conrad wrote:
> And the idiosyncrasies continue ... The current test invocation finds
> sh on my system only because I have /bin as a symbolic link to c:/
> Program Files/MKS Toolkit/mksnt. Now the idea isn't that novel, so
> I'm sure some others have als
From time to time, I've built groff using Microsoft Visual C/C++ and
the MKS Toolkit. The MKS environment provides most of the necessary
Unix-like utilities without much diddling, but not without a few
quirks.
One quirk makes it impossible for configure to detect the path
separator. With the M
