.obj/configmanager.o:configmanager.cpp:(.text+0x7477): more undefined references to `BuildManager::setLatexCommand(BuildManager::LatexCommand, QString const&)' follow
.obj/configmanager.o: In function `ConfigManager::readSettings()':
configmanager.cpp:(.text+0x96e2): undefined reference to `BuildManager::readSettings(QSettings const&)'
.obj/moc_buildmanager.o: In function `BuildManager::qt_metacall(QMetaObject::Call, int, void**)':
moc_buildmanager.cpp:(.text+0xbc): undefined reference to `BuildManager::conversionPreviewCompleted(int)'
moc_buildmanager.cpp:(.text+0xea): undefined reference to `BuildManager::latexPreviewCompleted(int)'
collect2: ld returned 1 exit status
make[1]: *** [texmakerx] Error 1
make[1]: Leaving directory `/home/enrico/Software/texmakerx'
make: *** [release-all] Error 2
Sorry for hijacking the thread and I apologize for not having read all of it, but maybe you could explain the reasons why this fork even exists and follows the development of the original Texmaker (would be nice to put it into the first post)? It seems very strange to me that you can't find a way to work on a GPL-ed program with together with the author...
In fact, I've sent an e-mail to Pascal with some suggestions for Texmaker few days ago and he didn't reply a single like (something like "Hey, I'm busy ATM, but I'll get back to you" would certainly cheer me up).
So I am wordering whether:
1) A source code repo for the official Texmaker exists (looks like if he doesn't use version control?!)
2) Somebody was able to get in touch with him, or the e-mail goes directly to /dev/null.
Zomg teh drama... Thanks for the explanation! Maybe I should write him in French then (luckily I do speak French) and if it doesn't work...
What are you up to? Are you going to continue updating TexMakerX to match 1.9.1?
Are you interested in discussing a few suggestions for the next release? Basically I have two of them, a quick and easy one and a big and hard one.
The first one is to allow users to specify the PATH to Hunspell dicos, not the dico itself so that the program would automatically scan this folder for dictionaries and allow user to pick a default & quickly pick a dictionary to use for the specific open file from the menu. This is VERY handy when you frequently edit files in many different languages (e.g. English, French, Russian, German etc.) - you don't have to go to the settings dialog and change the globally used dico every time.
The big and essential one is hard wraps. Many TeX users prefer them, because when you use some kind of VCS it helps to generate more sensible diffs. Otherwise TeXMaker is kind of useless for me ATM... I even have a rough idea on how I would implement this, but it still needs a lot of thinking.
