mailing-list for TeXmacs Users

[Frank <address@hidden>]

Sorry, you are correct that development packages do conflict. However, it seems to me that you can remove the installed one (development packages contain header files, static libraries, etc).

Seemingly Debian Policy suggests using conflicts mechanism to avoid simultaneous existence of different development versions: https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#development-files

Best wishes,

On 15/07/2019 20:06, Fan Zhang wrote:

Unfortunately, it does on Ubuntu as they both provide libguile-dev.

pkg: regarding guile-1.8-dev_1.8.8+1-10_amd64.deb containing guile-1.8-dev:
guile-1.8-dev conflicts with libguile-dev
guile-2.0-dev provides libguile-dev and is present and installed.

Fan

On July 15, 2019 at 12:48 PM, Frank <address@hidden> wrote:

No, guile-1.8 does *not* conflict with guile-2.0 in Debian (likewise, there is no conflict between different versions of gcc or clang).

Best wishes,

On 15/07/2019 18:36, Fan Zhang wrote:

Thanks for the suggestions. I also tried the AppImage and that works fine too. Compiling a deb is fine but from a maintenance point of view, I don’t want to install guile-1.8 because it conflicts with guile-2.0. Indeed in this case AppImage is superior.

If I may suggest, I feel the official website should advice that the generic binary uses “ historical” X11 and should only be used as a last resort. The AppImage distribution is worth a mention, if not a recommendation.

Interestingly, if you search “appimage texmacs”, Sage Wiki comes up as the first:  https://wiki.sagemath.org/days92/install

On Jul 15, 2019, at 10:42 AM, address@hidden wrote:

thanks you for these details installation :

I am on ubuntu and I don't know where your deb is installed ? I use --prefix=/user

I had to sudo to build ?

But every thing is going well, I like this kind of compilation with deb.

Le 15/07/2019 à 14:54, Darcy Shen a écrit :

http://forum.texmacs.cn/t/step-by-step-guide-to-make-a-deb-package-for-gnu-texmacs/39

Just follow my step by step guide to make a deb by yourself.

If you have any difficulties, just post your error messages here.

---- On Mon, 15 Jul 2019 03:57:06 +0800 Fan Zhang <address@hidden> wrote ----

I'm using the generic binary downloaded from http://texmacs.org/tmweb/download/linux.en.html on Ubuntu 19.04. Just tested it on my home desktop and the same problem happened there too. It is also *very* slow to start up (2-3 minutes). 

I think it's the X11 version. It's not linked to Qt as it seems.

> ldd $TEXMACS_PATH/bin/texmacs.bin linux-vdso.so.1 (0x00007ffe31de6000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f2dd8e24000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f2dd8cea000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f2dd8b9c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f2dd8b96000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f2dd8b8b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f2dd8b6a000)
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f2dd8b2e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f2dd8b14000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2dd8929000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2dd905c000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f2dd8900000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f2dd86fc000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f2dd84f4000)
libbsd.so.0 => /usr/lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f2dd84da000)

Any suggestions?

Fan

On July 14, 2019 at 2:58 PM, "address@hidden" <address@hidden> wrote:

I am on ubuntu 19.10 and I don't see this kind of behavior ? qt version

qt5.12.4 from today

Le 14/07/2019 à 20:07, Massimiliano Gubinelli a écrit :

Sounds mostly like a bug.

Which Linux? Somebody else note the same problem?

Is the QT version or the X11 version of TeXmacs?

Best

mg On 12. Jul 2019, at 13:13, Fan Zhang <address@hidden> wrote:
Hey, I’m on linux and I notice that TeXmacs (1.99.10) always creates a fontconfig folder in its working dir every time I start it. I usually start TeXmacs from different working dirs. Is this behavior intended?
Mike

-- 
Best wishes!
Yours,

-- 
Best wishes!
Yours,