X-Spam-Check-By: sourceware.org Message-ID: <20051207145130.29088.qmail@web51506.mail.yahoo.com> Date: Wed, 7 Dec 2005 06:51:30 -0800 (PST) From: "James R. Phillips" Reply-To: antiskid56-cygwin AT yahoo DOT com Subject: Re: octave-forge dependency? To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 -- 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/