Problem:
I wish to hack and solve Bidirectionality related bugs in Lyx.
However, I don't want to read all and understand all the code in Lyx,
but only the code related to cursor movement, character insertion,
etc.
How can I find the relevant pieces of code quickly?
Suggested Solution:
Run Lyx
Hi Elazar,
Put some fprintfs into the code, start with main().
Save the output to a file.
This is a quick way to circumvent all the gdb hassle.
This requires some code understanding.
Example:
== ce.h
#include cstdio
static char *cefilename = ce.txt;
#define
Hi Elazar,
Using the cpp macro that I have mentioned in my previous post
eliminates the need to recompile all the LyX source files
with debug information. No more g++ -g !
Elazar Leibovich wrote:
Problem:
I wish to hack and solve Bidirectionality related bugs in Lyx.
However, I don't want to
* Elazar Leibovich [EMAIL PROTECTED] [070426 16:24]:
Problem:
I wish to hack and solve Bidirectionality related bugs in Lyx.
However, I don't want to read all and understand all the code in Lyx,
but only the code related to cursor movement, character insertion,
etc.
How can I find the
