mtCellEdit 2.5



  • If you have Fontconfig on your system, it is used at compile time to set the default font.
  • The new default location for program preferences is ~/.config/mtcelledit/prefs.txt
  • The new location for temporary clipboard data is ~/.cache/libmtCedUI/clipboard.ledger.zip

These changes are fairly minor in code terms, but help the program better integrate with modern GNU/Linux systems.  See more here:


I don't blindly follow what standards people suggest (as their goals may be different to mine).  However, in this case I do think it would be an improvement as it leaves less clutter in the home directory and avoids the hassle of selecting a font.  Naturally the user can override the defaults by using a command line switch to set the prefs file, or by using the program preferences to set the font file and size.

Other changes include:

  • Maximum column width changed to 250 characters.
  • FreeBSD port added.
  • Desktop integration files added for mtEleana & mtRaft.
  • Directory structure changed (no internal version numbers, desktop and handbook files merged into mtcelledit).  Top level is now "mtcelledit-X.Y[.year.day.time]" with X.Y being the last stable version and optionally date and time for development versions.
  • Minor bugfixes.
  • Man pages added to the 6 apps.  README.txt files removed from subdirectories, and history now in NEWS.txt files.  Program documentation removed from --help switch.  This all avoids needless duplication.  Man pages are for quick reference such as command line usage.  The handbook is for deeper reading such as history, philosophy and practical examples.
  • mtEleana: cleanups and new search facility for the Qt versions.
  • cedutils can now receive data from stdin using "-i -", and print output to stdout using "-o -".  In other words the cedutils progs can now be used with pipes. Another joy of unix comes to the mtCellEdit suite. :)
  • mtCellEdit (Qt versions) now have a menu toggle to switch interaction with the system clipboard on and off.  This is useful for copying large amounts of data around a sheet or book internally as it is faster than involving the system clipboard or temp files.
  • Binary and hex numbers can now be larger than 2^32.  See the handbook section A.6.4 for details of these and other numerical limits.
  • It has been announced that the Google Code website will soon die so I have removed all references to the old website in the source tree and Sourceforge website.  If I missed any links, please let me know.  The new home page is mtcelledit.sf.net which holds a general description and useful links.  The website files are also in the source tarball.


djing said...

Hi Mark

I tried both the 2.5 and the mtcelledit-2.5.2015.0525.1747 (latest dev build)

the latest dev buld (mtcelledit-2.5.2015.0525.1747) across puppy linux versions (Puppy 3.01, 5.2.5 - codename *lucid* - puppy 5.3.1 -codename *slacko* - ) solves a little not too serious issue:

compiling the 2.5 build (latest stable branch of mtcelledit) previously I needed to comment some lines in



#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wcast-qual"

and 61

#pragma GCC diagnostic pop

to build limbtkit

while the latest dev build


solves this minot issue (it is not a serious thing anyway since commenting was enough to allow the compilation)

I also successfully built the qt4 version of mtcelledit

I failed to build limtqex lunking against 4.7.3 qt statically compiled

this time I used a shared build of qt 4.7.3 and I ended uip successfully

Only, I had a minor issue with mtcelledit-qu4

clicking on executable of mtcelledit-qt4, the program does not start

I only was able to start the program invoking from terminal wit the full path (all the rest seems to be okay)

How can I investigate on this minor issue?

thanks for any info

Mark Tyler said...

Hello djing.

Its good to hear that the Qt4 version is now compiling and working on your system. I did indeed correct the pragma problem that you noted. This pragma code is only for helping with debugging on more recent versions of GCC so not really relevant for most people.

The problem that you report regarding starting the Qt4 does seem odd. I assume that the GTK+2 version doesn't have this problem and works by clicking on it?

The only solution I can suggest is by having some kind of shortcut to start the program with the full path. For example I use the desktop file in the /mtcelledit/desktop/ directory which puts an entry into my XFCE/LXDE system menu for ease of access. This way also means I can open any spreadsheet file by clicking on a TSV file in a file manager such as Thunar or PCManFM.

I don't know how Puppy Linux works, but this desktop shortcut approach may help if you see how other programs solve this problem on your system (e.g. Gnumeric).

djing said...

Many thanks Mark

the gtk version is ok, it starts also clicking on executable

As said, this is not a serious issue, since I can invoke the qt4 version from terminal with the full path, but I'm puzzled by this behavior

can strace help to track the issue? otherwise what else can I use to track the issue and detect the reasons of this strange behavior?

Mark Tyler said...

Yes, this is very strange behaviour and very inconsistent. I suspect the problem may be the file manager, but without an error message from that program its impossible to know what the problem is.

How about starting the file manager from the command line, then clicking on the mtCellEdit file to see if an error message is printed in the terminal window?