mailing-list for TeXmacs Users

[Massimiliano Gubinelli <address@hidden>]

You can run without installation, just to check. I do not know how 
installation works on Linux.

From the source directory (where ./configure is) you can run

TEXMACS_PATH=$PWD/TeXmacs TeXmacs/bin/texmacs.bin

and should work.

Max


> On 21. Mar 2020, at 13:06, Giovanni Piredda <address@hidden> wrote:
> 
> I recompiled it with the branch guile3. The behaviour is the same: 
> (version) gives 1.8.8.
> 
> 
> Configure outputs
> 
> configure: Guile version 2.0
> configure: Guile data path: /usr/share/guile/2.0
> 
> (I checked running ./configure again after I have compiled and installed, 
> but it is irrelevant as far as I know).
> 
> 
> I am suspecting a different thing: that the command ./texmacs (run from the 
> installation directory) does not run the TeXmacs I have just installed but 
> the copy I have set as default by exporting $TEXMACS_PATH at login
> 
> To this point: what does the line in the shell script
> 
> if [ -z "$TEXMACS_PATH" ] ;
> 
> do? Does it check whether $TEXMACS_PATH exists? In this case that is the 
> reason why the "usual" TeXmacs get run, that is $TEXMACS_PATH is already 
> set in my shell.
> 
> I have tried running the shell script without the ifs, that is, reduced
> 
> if [ -z "$TEXMACS_PATH" ] ; then
>   TEXMACS_PATH=${datarootdir}/TeXmacs
>   export TEXMACS_PATH
>   if [ -z "$TEXMACS_BIN_PATH" ] ; then
>     TEXMACS_BIN_PATH=${exec_prefix}/libexec/TeXmacs
>     export TEXMACS_BIN_PATH
>   fi
> else
>   TEXMACS_BIN_PATH="$TEXMACS_PATH"
>   export TEXMACS_BIN_PATH
> fi
> 
> 
> to
> 
> 
> TEXMACS_PATH=${datarootdir}/TeXmacs
>   export TEXMACS_PATH
> 
> TEXMACS_BIN_PATH=${exec_prefix}/libexec/TeXmacs
>     export TEXMACS_BIN_PATH
> 
> and TeXmacs starts the compilation, then crashes: this makes me think I am 
> going in the right direction.
> 
> I am seeing that the environments variables exported in this way are valid 
> only in the terminal where I defined them, so this keeps the "usual" 
> TeXmacs running when calling it from other terminal windows, and this means 
> I can experiment easily. I would need a hint on how to go on.
> 
> 
> Giovanni
> 
> 
> On 21.03.20 12:31, Massimiliano Gubinelli wrote:
>> --enable-guile2 does not do much.
>> 
>> You would have to check the output from configure and see if TeXmacs pick 
>> up the right guile.
>> 
>> Use the branch guile3 or qt5+guile2 on my github account mgubi/texmacs
>> 
>> 
>> Best
>> Max
>> 
>> 
>> 
>>> On 21. Mar 2020, at 12:13, Giovanni Piredda <address@hidden> wrote:
>>> 
>>> which guile-config
>>> 
>>> returns
>>> 
>>> /usr/bin/guile-config
>>> 
>>> and
>>> 
>>> guile-config --version
>>> 
>>> returns
>>> 
>>> guile-config - Guile version 2.0.13
>>> 
>>> I suspect I cloned the wrong branch (although I do not understand why, if 
>>> this were the case, --enable-guile2 was accepted by the ./configure 
>>> command). I cloned it again and I am compiling it again.
>>> 
>>> Giovanni
>>> 
>>> On 21.03.20 12:03, Massimiliano Gubinelli wrote:
>>>> Usually it is enough to change your PATH variable in such a way that 
>>>> configure find the right 'guile-config'. Do
>>>> 
>>>> which guile-config
>>>> 
>>>> to check.
>>>> 
>>>> Max
>>>> 
>>>> 
>>>>> On 21. Mar 2020, at 11:47, Giovanni Piredda <address@hidden> wrote:
>>>>> 
>>>>> 
>>>>> On 21.03.20 11:41, Kovács Zoltán wrote:
>>>>>> Dear all,
>>>>>> after several emails with Max I finally managed to compile TeXmacs 
>>>>>> 1.99.12 on Ubuntu 18.04 with guile-2.2. I used his branches qt5 and 
>>>>>> guile2 (however, he already merged them into one branch). The 
>>>>>> compilation was smooth when adding the option --enable-guile2 when 
>>>>>> launching the configure script.
>>>>>> image.png
>>>>>> Ubuntu 18.04 has Qt version 5.9.5.
>>>>> I thought I had also compiled it - I used --enable-guile2 in the 
>>>>> ./configure command, but (version) is giving me 1.8.8. I know that I am 
>>>>> running the one I compiled as I am invoking it with the full path. Any 
>>>>> suggestions?
>>>>> 
>>>>> 
>>>>> Giovanni
>>>>>