On Sun, Dec 21, 2003 at 11:50:29PM -0600, Bo Peng wrote:
> The following works for 1.4cvs: a black WrongFormula box will be shown
> in place of wrong formula. This is just to show the idea, no efficiency
> has been considered.
My small script only works for *new* wrong formula and will fail wh
> cat >> wrong formula.tex <> wrongformula.tex <
> I had a look at the source code and found that we only need to change
> lib/scripts/lypreview2bitmap.sh. If you allow, I will try to figure out a
> patch.
The following works for 1.4cvs: a black WrongFormula box will be shown
in place of wrong formula. This is just to show the idea, no efficien
>
> As the guy writing the code, I beg to differ.
>
> Turn on instant preview and assume that any inset not previewed is
> wrong?
>
I notice that instant preview is not *always* working. I have not tried to
repeat this bug (?) but I sometimes need to enter a formula and leave to
let it be display
Bo Peng wrote:
>
>> The effort for a black alpha is zero, the effort for a red one is
>> substantial, or in other words, _I_ won't do it. If there was a
>> clean patch by someone else, I might apply it, though...
>
>
> I have another idea. Under 'instant preview', when error happens and
> latex
> The effort for a black alpha is zero, the effort for a red one is
> substantial, or in other words, _I_ won't do it. If there was a clean
> patch by someone else, I might apply it, though...
I have another idea. Under 'instant preview', when error happens and
latex can not compile the snipet,
Andre Poenitz wrote:
>> How about a red \alpha instead of black one? Or, a red error box
>> like the ones after we compile the file?
>
> The effort for a black alpha is zero, the effort for a red one is
> substantial, or in other words, _I_ won't do it. If there was a
> clean patch by someone else
On Thu, Dec 11, 2003 at 12:11:08PM -0600, Bo Peng wrote:
> > > It is not a very bad idea. A big message box will be intrusive (and
> > > scary) but users will learn very quickly how to avoid it.
>
> > No they won't, they'll just come and complain at you, and at us. Users
> > do not read error box
> > It is not a very bad idea. A big message box will be intrusive (and
> > scary) but users will learn very quickly how to avoid it.
> No they won't, they'll just come and complain at you, and at us. Users
> do not read error boxes, and they certainly don't read intrusive and
> rude ones like th
On Thu, Dec 11, 2003 at 11:55:55AM -0600, Bo Peng wrote:
> > but also because I won't go through all 700 supported symbols and
> > figure out which ones are safe to use in text and which ones are not.
>
> As I said, the warning message does not have to be fired for ALL
> symbols. Just all Greek
On Thu, Dec 11, 2003 at 11:55:55AM -0600, Bo Peng wrote:
> > How should the warning message look like? I don't think a full blown
> > message box is in order,
>
> It is not a very bad idea. A big message box will be intrusive (and
> scary) but users will learn very quickly how to avoid it.
No
> In mathed's text mode you mean?
Yes.
> The \alpha in textmode is black, isn't it? The simplest way would to tell
> people 'real alphas are blue'.
Yes. I told them the trick.
> How should the warning message look like? I don't think a full blown
> message box is in order,
It is not a very ba
On Thu, Dec 11, 2003 at 11:20:15AM -0600, Bo Peng wrote:
> Hi,
>
> I upgraded lyx 1.2 to lyx 1.3.1 for our department yesterday and I already
> got angry emails claiming lyx 1.3 is worse than 1.2, because users get
> compile errors when they input symbols inside text mode (as they did in
> lyx1
Hi,
I upgraded lyx 1.2 to lyx 1.3.1 for our department yesterday and I already
got angry emails claiming lyx 1.3 is worse than 1.2, because users get
compile errors when they input symbols inside text mode (as they did in
lyx1.2).
I have discussed this problem before and totally agree with And
14 matches
Mail list logo
