This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Charles Wilson wrote:
But apparently I can't use octave.
Hm, actually we wouldn't want to lose such a knowledgeable user. We need users like you in order to improve octave.
Would this work for you? Prior to putting miktex at the front of your path, say in your .profile, it should be possible to save the unmodified path in an environmental variable, say PATH_FOR_OCTAVE.
Then write a short shell script named "octave" to start octave, and put it in /usr/local/bin; something like
======= #!/bin/sh
export PATH=$PATH_FOR_OCTAVE /usr/bin/octave =======
When typing "octave" from the command line, the shell script should be found in the path prior to the octave binary in /usr/bin. octave/octave-forge should then use the cygwin-native tetex binaries. I don't see any reason why this wouldn't work.
Hope you don't give up on octave.
jrp
Spinning complacently in the darkness, covered and blinded by a blanket of little lives, false security has lulled the madness of this world into a slumber. Wake up! An eye is upon you, staring straight down and keenly through, seeing all that you are and everything that you will never be. Yes, an eye is upon you, an eye ready to blink. So face forward, with arms wide open and mind reeling. Your future has arrived... Are you ready to go?
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |