eventually the cygwin shell enviroment is not correctly passed to the
not-cygwin octave.
Yes, that's what it looks like to me. So what would cause the current working
directory not to be passed to Octave on one machine compared to another? To
reverse the question, suppose I wanted a command line invocation to ignore the
current working directory by default, how would I do it? Other than putting a
full path on the command line, I mean.
try
/cygdrive/c/Octave/Octave3.6.4_gcc4.6.2/bin/octave.exe -q $(cygpath -wa
test_me.m)
In this way you should pass the absolute location of the file
I do indeed. But howcome I need to do it now, and only on one machine and not
another?
dummy question : why you are not using the cygwin octave binary ?
Not a dummy question at all. I use Octave for multiple things. Sometimes I want
to use it standalone and sometimes I want to call it from the command line.
Until now, this has worked fine for me, across many laptops over the last
I-don't-know-how-many years, put probably something like 5 laptops over 10
years, administered by different organisations.
Given that it works on my machine, I believe it *can* work on his machine, if I
can find the difference between his and mine. The key question will be whether
or not the cygpath step makes his machine work or not; if so I will just get
over it and use that from now on (since it works on my machine too). I'm
reluctant to start installing a different version unless I really have to.