mailing-list for TeXmacs Users

[Massimiliano Gubinelli <address@hidden>]

I think 

-ne

is a problem with the printing of the version of octave.
m


> On 28. Jun 2019, at 08:26, Giovanni Piredda <address@hidden> wrote:
> 
> I could try it with 1.99.7 and it does not work with that too, but to 
> figure it out completely should check with the version for which the plugin 
> has been written (and maybe with the original Octave version as well!).
> 
> Said this, if adding the path through the tm-start is a sensible thing to 
> do, then the command that does it is
> 
> addpath([d '/plugins/octave/octave/tm'])
> 
> just before
> 
> tmrepl
> 
> (the variable d has been defined reading the TeXmacs path from the 
> environment at the beginning of the script).
> 
> 
> 
> 
> 
> On 28.06.19 08:09, Massimiliano Gubinelli wrote:
>> I would say you just have to fix tm-start.m so that Octave looks for files 
>> inside the child directory, but I’m not familiar with that software so I 
>> do not know how to do it. Maybe I will look to it later.
>> 
>> Max
>> 
>> 
>>> On 28. Jun 2019, at 08:07, Massimiliano Gubinelli <address@hidden> wrote:
>>> 
>>> Hi Giovanni,
>>> did it worked before? Is a problem you see in the last versions?
>>> 
>>> Max
>>> 
>>> 
>>> 
>>>> On 28. Jun 2019, at 08:04, Giovanni Piredda <address@hidden> wrote:
>>>> 
>>>> Dear all,
>>>> 
>>>> 
>>>> the Octave plugin on Linux Xubuntu 18.04.2 gets stuck at "Busy ...". The 
>>>> Octave version is 4.2.2 (the one in the repositories).
>>>> 
>>>> 
>>>> There is an error message:
>>>> 
>>>> error: 'tmrepl' undefined near line 3 column 5
>>>> error: called from
>>>>    tm-start.m at line 3 column 5
>>>> 
>>>> 
>>>> (For info, before the welcome screen there is the following output
>>>> 
>>>> -ne
>>>> 
>>>> which I think comes from the shell start script and has probably nothing 
>>>> to do with the problem)
>>>> 
>>>> 
>>>> So it seems that Octave when called does not see the path that it needs 
>>>> to see. I have tried copying the whole content of the directory 
>>>> plugins/octave/octave/tm/ one level up (to plugins/octave/octave/) and 
>>>> it works (tried both on 1.99.9 and 1.99.10).
>>>> 
>>>> Maybe it is easy to fix this in a proper way, but I do not know how to 
>>>> do it. Should one perhaps add the path to Octave? Should the plugin do 
>>>> that automatically? Does someone know?
>>>> 
>>>> 
>>>> Giovanni
>>>>