Arvind Ajoy | 23 Jul 05:47 2014

Broken 'sources' link on Texmacs homepage

Dear Developers,

I wish to compile Texmacs on my Debian system. The links to sources (stable, and latest version) listed on seem to be broken. I thought I should bring this to your notice.

Thanks for an excellent piece of software!


Arvind Ajoy
Texmacs-dev mailing list
Texmacs-dev <at>
Sam Liddicott | 17 Jul 07:34 2014

stack overflow

This simplified macro:


gives these errors on the console when entered into the editor

.../TeXmacs/progs/kernel/library/list.scm:100:12: In expression (cdr (reverse l)):
.../TeXmacs/progs/kernel/library/list.scm:100:12: Stack overflow

the error vanishes when the first branch of the if block is removed.

I would guess it is over-optimistic reduction of the "if" statement when encountering recursion.

Texmacs-dev mailing list
Texmacs-dev <at>
Miguel de Benito Delgado | 13 Jul 13:14 2014

TeXmacs -> HTML

Hi everybody,

  I’m having some annoying problems with conversion to HTML. I’d like to use MathJAX and for that I
choose to export math with MathML. Problem is, XHTML is enforced and rendering by the browser is then
different (TeXmacs website).

Also, playing with the preferences I’ve noticed that it is possible to select contradictory options for
math formula export.

So, here’s my question / suggestion:

I’d like to create a new option “texmacs->html:math” with the possible values “html”,
“mathml”, “image”, “mathjax”.

The first three are those currently available. The idea is to disallow nonsensical settings.

The last one would include a <script> tag in the html output to use the MathJax Content Delivery Network (as
suggested here: ). It would also set MathML as the
output for mathematics, and it would *not* change the extension to .xhtml. The server would then serve the
content as text/html and rendering wouldn’t be affected.

Any ideas / objections?
Miguel de Benito.

Texmacs-dev mailing list
Texmacs-dev <at>
Sam Liddicott | 8 Jul 19:00 2014

building texmacs

texmacs currently failing, svn updated a few minutes ago:
building on linuxmint 17 (like Ubuntu 14.04)

./configure --with-x --disable-qt

In file included from Kernel/Abstractions/basic.hpp:14:0,
                 from Kernel/Types/string.hpp:15,
                 from Kernel/Abstractions/resource.hpp:13,
                 from Graphics/Bitmap_fonts/bitmap_font.hpp:14,
                 from Graphics/Renderer/renderer.hpp:14,
                 from ./Plugins/Pdf/pdf_hummus_renderer.hpp:15,
                 from ./Plugins/Pdf/pdf_hummus_renderer.cpp:12:
System/Misc/fast_alloc.hpp:380:7: error: from previous declaration
‘void operator delete(void*)’
 void  operator delete (register void* ptr);
In file included from /usr/include/c++/4.8/ext/new_allocator.h:33:0,
                 from /usr/include/c++/4.8/bits/allocator.h:46,
                 from /usr/include/c++/4.8/string:41,
                 from ./Plugins/Pdf/PDFWriter/OutputFile.h:24,
                 from ./Plugins/Pdf/PDFWriter/PDFWriter.h:29,
                 from ./Plugins/Pdf/pdf_hummus_renderer.cpp:32:
/usr/include/c++/4.8/new:98:41: error: declaration of ‘void operator
delete [](void*) throw ()’ has a different exception specifier
In file included from Kernel/Abstractions/basic.hpp:14:0,
                 from Kernel/Types/string.hpp:15,
                 from Kernel/Abstractions/resource.hpp:13,
                 from Graphics/Bitmap_fonts/bitmap_font.hpp:14,
                 from Graphics/Renderer/renderer.hpp:14,
                 from ./Plugins/Pdf/pdf_hummus_renderer.hpp:15,
                 from ./Plugins/Pdf/pdf_hummus_renderer.cpp:12:
System/Misc/fast_alloc.hpp:382:7: error: from previous declaration
‘void operator delete [](void*)’
 void  operator delete[] (register void* ptr);

Texmacs-dev mailing list
Texmacs-dev <at>
Sam Liddicott | 20 Jun 13:38 2014

paste verbatim interprets <tag> in red

With SVN updated just now, when I cut-n-paste some XML as text (to
show as text with all the angle-bracket glory) some of the items
appear in texmacs in red as single tokens.

e.g. if I copy this from a text editor:


and past-from-verbatim, this document fragment is produced:




which has the word <sample> in red.

I think that is not right

François Poulain | 6 Jun 17:17 2014

cleanup in color managment


I started 2 days ago a big cleanup into color managment. Code was
dramatically duplicated between Qt, x11, and converters.

Please, dont hesitates to complain about any strange behavior change,
since I cannot test all possible cases.

It remains some work on the converters side to take advantage of this,
but now it will be more easy to make the job.

As far as X11 backend is concerned, I don't know how to test it, but it
seems sure that the managment of 16 bit colors has been broken for a
long time. But I am not sure that anyone will use TeXmacs one day in
less than 2^24 colors.



François Poulain <fpoulain <at>>
Germán Arias | 2 Jun 07:27 2014

Re: Problem with Guile 2

On 2014-05-22 19:40:52 -0600 Germán Arias <germanandre <at>> wrote:
> I don't have problem to delete, move or change the attributes of these files. 
> So, I don't think so. Which is odd, is why "make" try to change files inside 
> .svn directories. I think this is really wrong.
> Germán.

OK, I downloaded the the tarball and this compiles without problem. So, I think there are some problems with
SVN trunk. Of course this don't works. But I will try to get it working. Although I have some questions, but
this is topic of other thread. 

胡小柯 | 6 May 11:56 2014

Re: [bug]input '-' in Inline code cause TeXmacs to exit immediately

sorry, I should say I set user interface language as Chinese.

2014年5月5日 下午6:26于 "胡小柯" <hot123tea123 <at>>写道:

sorry, I forgot it. I'm using TeXmacs on ArchLinux.
If I start TeXmacs from console, I get the error message "段错误(核心已转储)", it means "Segmentation fault (Core Dumped)".

2014-05-05 15:29 GMT+08:00 François Poulain <fpoulain <at>>:
> Le Sun, 4 May 2014 22:40:06 +0200,
> Miguel de Benito Delgado <m.debenito.delgado <at>> a écrit :
>> sorry, I can't reproduce the problem with the latest version from
>> SVN.
> Me too.
> François
> --
> François Poulain <fpoulain <at>>
> _______________________________________________
> Texmacs-dev mailing list
> Texmacs-dev <at>

sent from hottea's openSUSE

Texmacs-dev mailing list
Texmacs-dev <at>
胡小柯 | 2 May 15:34 2014

[bug]input '-' in Inline code cause TeXmacs to exit immediately

I can't find a bug report mail list, so I report it here.
When I insert inline Shell code by Insert->Program->Inline
code->Shell, I input '-', then TeXmacs exits immediately. I double
checked it, found that it would not happen when I set langue as
English, but it would happen when langue is Chinese and Taiwanese.
Andrey G. Grozin | 1 May 05:23 2014


Hello *,

What exactly --with-cairo adds to TeXmacs? I tried to compile 1.99.1 with 
--with-qt --with-cairo, but got

x86_64-pc-linux-gnu-g++ -ISystem -ISystem/Boot -ISystem/Classes 
-ISystem/Files -ISystem/Link -ISystem/Misc -ISystem/Language 
-IKernel/Abstractions -IKernel/Containers -IKernel/Types -IData/Convert 
-IData/Drd -IData/History -IData/Observers -IData/Document -IData/String 
-IData/Tmfs -IData/Tree -IScheme -IGraphics/Bitmap_fonts -IGraphics/Fonts 
-IGraphics/Gui -IGraphics/Mathematics -IGraphics/Renderer 
-IGraphics/Handwriting -IGraphics/Types -IGraphics/Pictures 
-IGraphics/Spacial -IPlugins -ITexmacs -ITexmacs/Data -IEdit -ITypeset 
-pipe -O2 -Wall -W -D_REENTRANT -pthread -DQT_NO_DEBUG -DQT_GUI_LIB 
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. 
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. 
-I. -DQTTEXMACS -Wall -Wno-return-type -O2 -march=native -pipe -fno-rtti 
-c ./Plugins/Qt/QTMWindow.cpp -o Objects/QTMWindow.o
In file included from ./Plugins/Qt/QTMWidget.cpp:25:0:
Plugins/Cairo/tm_cairo.hpp:21:19: fatal error: cairo.h: No such file or 
  #include <cairo.h>
compilation terminated.
makefile:315: recipe for target 'Objects/QTMWidget.o' failed
make[1]: *** [Objects/QTMWidget.o] Error 1

Is CXXCAIRO used in the relevant place in src/

By the way, what do --with-axel and --with-sqlite3 mean?

Miguel de Benito Delgado | 27 Apr 09:41 2014

Re: [TeXmacs] minibuffer support in Qt version

Hi Kostas,

  sorry for the late reply. I've shitloads of things to do and I've shunted all TeXmacs stuff to the "don't even think about it" folder.

Anyway, here are my 2c. I'm sending to the list as well, as this might be of interest to someone.

On 23 April 2014 14:35, Kostas Oikonomou <ko <at>> wrote:
Thanks.   I am now looking at QTMMenuHelper.cpp, where it says

QTMLineEdit::keyPressEvent (QKeyEvent* ev)

Is this the right place?  If so, please explain a little more how to proceed with your suggestion

Yes, that is the standard key event handler in a Qt Widget. The code there is intended to handle tab completion in an "intuitive" manner (and fails miserably at it). What you need to do is to add new cases (and if you have the time, please fix the mess already there). Basically you have to:

1. Call kbd-find-rev-binding to find which keys are currently bound to the actions you want to handle. E.g.

    string s = as_string (call ("kbd-find-rev-binding",  "(kbd-end-line)"));    // string representation of key to move to EOL

2. Decode these key definitions, which will be in a format like "C-x C-v", "M-right", etc. into something you can handle in your C++ code (e.g. Qt:Key_Right, etc.). You'll have to follow some of what is done at the beginning of QTMWidget::keyPressEvent(), but you might also have to handle the wildcards present in key definitions, e.g. things like "std c". There's some c++ code to this effect in tm_config.cpp, I think.

3. Add new cases to QTMLineEdit::keyPressEvent() where you handle the keys you must. The tricky part will be handling key sequences as well. I don't know precisely how this is done, but basically all keypresses are in the end sent to edit_interface_rep::key_press(), where it seems like try_shortcut() is the main player. You'll have to start by understanding how this works. :(

> I think it’d be best if the QTMLineWidget used the current shortcuts (that it can understand) to ensure consistency. This > can be done calling (for instance in the widget's constructor) the scheme function kbd-find-rev-binding.

Where is the widget's constructor?  Can you send an example line of code calling kbd-find-rev-binding()?

With widget constructor I mean C++ object constructor, so QTMLineEdit::QTMLineEdit. If it isn't already there, just add one.
Good luck!
Miguel de  Benito.


On 04/23/2014 01:27, Miguel de Benito Delgado wrote:

Ooops! That would be QTMLineEdit, of course! Sorry.


Am 23.04.2014 02:19 schrieb "Kostas Oikonomou" <ko <at>>:
Hi Miguel,

I'm finally getting around to this...   I just checked out the SVN version, and to start with I tried to find a mention
of QTMLineWidget:

[ko <at> wiley ~/build/texmacs-svn/src]$ find ./ -exec grep -l QTMLineWidget {} \;
[ko <at> wiley ~/build/texmacs-svn/src]$

But I didn't find anything.


On 01/12/2014 03:58, Miguel de Benito Delgado wrote:
Hi Kostas,

  sorry for the delay and glad to see you’re willing to help out. :)

The problem is that the QTMLineWidget, which implements the line inputs uses Qt standard shortcuts. Basically Joris says that in order to solve this it’s best to ignore TeXmacs' keyboard shortcut system and hardcode a few standard shortcuts for the line inputs in each “look and feel”.

I think this is not such a great idea so he suggests we provide some method for the user to change the shortcuts for those line inputs only. Probably through standard preferences in preferences.scm. 

I think it’d be best if the QTMLineWidget used the current shortcuts (that it can understand) to ensure consistency. This can be done calling (for instance in the widget's constructor) the scheme function kbd-find-rev-binding. To test it, in a scheme session type:

(kbd-find-rev-binding "(kbd-end-line)")

Notice that we use the string representation of the command, as given in the kbd-map. You can see all relevant shortcuts in progs/generic/generic-kbd.scm.

In Qt we need to reimplement the KeyEvent handler in QTMLineWidget and filter those key presses configured for left, right, end, start, etc.

If you finally find time to work on this don't hesitate to ask for help.

Miguel de  Benito.

On Mon, Jan 6, 2014 at 11:58 PM, Kostas Oikonomou <ko <at>> wrote:
Hi Miguel,

Glad to see you're the responsible party :-)

I read the link you sent, and I am willing to help.  (Though my abilities in C++ are limited.) 
As a first step, however, I am not sure exactly what is the solution you and Joris have agreed upon.
Could you please summarize?

I am not cc'ing the list, should I?


On 01/06/2014 13:04, Miguel de Benito Delgado wrote:
Hi Kostas,

  this would be:

and yes, it is assigned to yours truly... Patches are welcome! ;-D

Miguel de  Benito.

On Mon, Jan 6, 2014 at 4:46 PM, Kostas Oikonomou <ko <at>> wrote:

Given that the X version of TeXmacs seems to be on its way out, can someone comment on what it would take to make the minibuffer in the Qt version behave like the minibuffer of the X version?  In particular, to have C-g work, and to have the ability to move around in the minibuffer line, and to edit it?

In my view, minibuffer support is the only significant feature missing from the Qt version for it to be a compete replacement of the X version.


Texmacs-dev mailing list
Texmacs-dev <at>