On Tue, Jan 21, 2003 at 05:56:12PM +, John Levon wrote:
> > [Looks like I am the only one using inset locking?]
>
> What is this ?
If you press C-i inset a mathinset, it gets "locked" and Cursor Left/Right
jumps over it with a single keystroke.
To unlock, press C-i again. Up/Down isn't affec
On Tue, Jan 21, 2003 at 05:54:21PM +0100, Andre Poenitz wrote:
> [Looks like I am the only one using inset locking?]
What is this ?
john
--
"Anyone who quotes Rusty in their sig is an idiot."
- me
On Tue, Jan 21, 2003 at 05:47:38PM +0100, Lars Gullik Bjønnes wrote:
> Does it fix a real problem?
Yes. preview does not work without it if only a single formula is locked.
[Looks like I am the only one using inset locking?]
Andre'
--
Those who desire to give up Freedom in order to gain Securi
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Tue, Jan 21, 2003 at 02:44:52PM +, Angus Leeming wrote:
| > Happy if I apply it?
|
| Yes.
|
| > Guess that Lars should give his Ok too ;-)
|
| I suppose so.
Does it fix a real problem?
If so, commit it.
--
Lgb
On Tue, Jan 21, 2003 at 02:44:52PM +, Angus Leeming wrote:
> Happy if I apply it?
Yes.
> Guess that Lars should give his Ok too ;-)
I suppose so.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Andre Poenitz wrote:
> On Tue, Jan 21, 2003 at 02:12:42PM +, Angus Leeming wrote:
>> Is this your way of saying that the problem lies in mathed itself?
>> Ie, it would go away if we had control over the 'true' passed to
>> the WriteStream c-tor.
>
> We could certainly use that, but I don't kn
On Tue, Jan 21, 2003 at 02:12:42PM +, Angus Leeming wrote:
> Is this your way of saying that the problem lies in mathed itself?
> Ie, it would go away if we had control over the 'true' passed to the
> WriteStream c-tor.
We could certainly use that, but I don't know what the 'nice' flag is go
Andre Poenitz wrote:
> Judging from
> int InsetFormula::latex(Buffer const *, ostream & os, bool fragile,
> bool) const
> {
> WriteStream wi(os, fragile, true);
> par_->write(wi);
> return wi.line();
> }
> that's not the place.
Is this your way of saying that the problem lies in mathed itself?
On Tue, Jan 21, 2003 at 01:48:40PM +, Angus Leeming wrote:
> > There is another one: Currently, \lyxlock gets written to the .tex
> > snippets. This indicates that preview uses the "write to .lyx"
> > method instead of "write to .tex" (I think this is a boolean flag
> > somewhere, haven't looke
Andre Poenitz wrote:
> There is another one: Currently, \lyxlock gets written to the .tex
> snippets. This indicates that preview uses the "write to .lyx"
> method instead of "write to .tex" (I think this is a boolean flag
> somewhere, haven't looked at it, though)
Do you mean the 'nice' flag pass
On Tue, Jan 21, 2003 at 02:14:31PM +0100, Moritz Moeller-Herrmann wrote:
> The problems should simply be documented. AFAICS, if you do not use ERT,
> preview-latex will work fine.
Simply go into a 'a^b' inset and press C-I to lock it. No fancy preview
anymore...
Ok, this is the only bug I am aw
Andre Poenitz wrote:
> On Tue, Jan 21, 2003 at 11:58:34AM +0100, Michael Schmitt wrote:
>> After all, the problem will only occur for real power users. IMHO it
>> would be a complete waste of time to redesign the preview code which
>> works very well in general.
>
> But you accept that "very well
On Tue, Jan 21, 2003 at 11:58:34AM +0100, Michael Schmitt wrote:
> After all, the problem will only occur for real power users. IMHO it
> would be a complete waste of time to redesign the preview code which
> works very well in general.
But you accept that "very well in general" is not sufficien
Andre Poenitz wrote:
It's probably better to produce a single full dvi preview in the background
"all the time" and snip from there instead of the current "snippet based"
approach (which is simple and cute, but not robust at all).
Please do not put too much effort into something that can't be fi
On Tue, Jan 21, 2003 at 10:30:36AM +, Angus Leeming wrote:
> Ummm. We already loop over the document to output all math macros.
> Could we also output all ERT insets?
All up to the position of the snippet. And if the snippet is moved, we
can't use the cached image. And so on. This is a can of
Andre Poenitz wrote:
> On Tue, Jan 21, 2003 at 10:12:28AM +0100, Michael Schmitt wrote:
>> >No. There are still rough edges (display jumping) and there are
>> >conceptual problems (fancy preambles) that make this wonderful
>> >feature unusable under some circumstances. It certainly should not
>> >
Andre Poenitz wrote:
Yes, I guess so. Unfortunately, I don't have enough knowledge to provide
a patch for it
The ERT problem is unsolvable.
:-)
I didn't refer to the ERT problem but to the extension of the configure
script to list all third-party products (pspell, aiksaurus, checktex,
prev
On Tue, Jan 21, 2003 at 10:12:28AM +0100, Michael Schmitt wrote:
> >No. There are still rough edges (display jumping) and there are
> >conceptual problems (fancy preambles) that make this wonderful feature
> >unusable under some circumstances. It certainly should not default to on.
>
> I know the
Andre Poenitz wrote:
On Tue, Jan 21, 2003 at 09:48:30AM +0100, Michael Schmitt wrote:
I think we should provide a link to the preview-latex homepage in the
NEWS file.
Ok.
See attachment for patch.
I also wonder whether we should activate preview-latex by default
No. There are st
19 matches
Mail list logo
