Re: 3.6.2 on Win7, signal pkg not in path

[Andy Buckle]

> On Mon, Aug 20, 2012 at 11:23 AM, Andy Buckle <address@hidden> wrote:
>> On 20 August 2012 10:16, Børge Strand-Bergesen <address@hidden> wrote:
>>> I have recently installed from octave-3.6.2-vs2010-setup.exe. Signal
>>> package was selected and is installed according to pkg list. Path
>>> contains "C:\Program Files
>>> (x86)\Octave-3.6.2\share\octave\3.6.2\m\signal" but not "...
>>> share\octave\packages\signal-1.1.3".
>>>
>>> The former contains 33 files while the latter contains 134 files,
>>> including cheb.m which I use in my code.
>>>
>>> Obviously, it's easy to copy the m files around. But before I do that
>>> I'd like to know if things are like this on purpose and if there's an
>>> official way to call cheb.m and the other 133 files in that directory.
>>>
>>> Thanks,
>>> Børge
>>
>> Spaces in the path is a problem for pkg command: "Program Files". I
>> think rebuild will not work.
>>
>> does
>>
>> pkg load signal
>>
>> work?
>>
>> /* andy buckle */
On 20 August 2012 13:04, Børge Strand-Bergesen <address@hidden> wrote:
> Thanks for your quick feedback!
>
> pkg load signal actually worked on the installation with spaces. To
> stay on the safe side I reinstalled to C:\Octave-3.6.2. The program
> acts as before. After startup, cheb() is undefined. After pkg load
> signal it is available.
>
> Is there a way to make it available at startup?
>
> Børge
>

When including previous text in emails, this list prefers chronological order.

Add "pkg load signal" to a startup script eg

%homepath%\.octaverc

-- 
/* andy buckle */