>>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> Really (redundantly) Emphatically Dead-set Against Lyx's Evil
Amir> Red Text!
Good. We were missing some catchy names...
Amir> My personal contribution to the war effort is, of course, making
Amir> reLyX write as little ERT as possible. To that end, I'd like to
Amir> implement the idea we've thrown around before, where \mbox{foo}
Amir> will be translated to \mbox{foo} in the lyx file, but "\mbox{"
Amir> and "}" will be ERT (sorry) while foo will be Excellent Regular
Amir> Text, or ERT for short...
It's about time ;)
Amir> What I need from people is a list of commands for which we're
Amir> allowed to do this. I already thought of \mbox, and it should
Amir> work for \fbox, too. \centering should work, too (and stop
Amir> complaining, Jean-Marc :) How about \protect?
\protect does not take any argument, so you do not have to care about
that. However, LyX does generate some \protects by itself, so you
should probably ignore them in some cases (if some -quickanddirty flag
is added one day to LyX, dropping protects could be set to on by this
flag).
Amir> But there must be pleny of others. Basically,
Amir> any command that has regular LaTeX in its argument should
Amir> work. Note that math mode commands won't help, since mathed
Amir> takes care of those, and any command already translated by reLyX
Amir> is obviously not necessary, here.
A good starting point is John latex macros list, I
guess. Unfortunately, I do not have it anymore.
Amir> I THINK that I can also set it up so that commands with more
Amir> than one argument will translate some arguments, but leave
Amir> others in TeX mode. For example, it seems to me that for
Amir> \parbox{1in}{foo}, the 1in should really be ERT (sorry), because
Amir> it's really performing a LaTeX function, not a LyX one.
Yes, this would be much needed.
If you send me a list of commands that are not currently handled, I
can try to do a bit of classification.
JMarc
