... I get here.
* CompileC src/mathed/MathData.cpp normal i386 c++ com.apple.compilers.gcc.4_2
src/mathed/MathData.cpp: In member function 'void
lyx::MathData::detachMacroParameters(lyx::DocIterator*, size_t)':
src/mathed/MathData.cpp:508: warning: negative integer implicitly converted to
unsig
Am 21.12.2010 um 00:48 schrieb Pavel Sanda:
> hi,
>
> time to think about beta3.
> there is already a couple of things which need to be released
> and tested so we should start freezing at certain time.
>
> are there some particular issues you want to push in trunk
> before next beta?
As you k
Joost Verburg wrote:
> I still believe the best way forward is to start with the CMake build tools
> and the new libraries I've recently ported to Visual C++
i also think this is the best approach in long term.
> The question is whether this is feasible for 2.0. Perhaps I could start
> with bu
Op 21-12-2010 2:27, Joost Verburg schreef:
On 12/20/2010 7:40 PM, Pavel Sanda wrote:
although all the advantages above look like very good step forward
i'm afraid
there is nobody around who is going to write new NSIS code (i suppose
Uwe is
not going to leave his code for some unfinished stuff
On 12/20/2010 7:40 PM, Pavel Sanda wrote:
although all the advantages above look like very good step forward i'm afraid
there is nobody around who is going to write new NSIS code (i suppose Uwe is
not going to leave his code for some unfinished stuff he is not familiar with.)
That's why I think
Joost Verburg wrote:
> Unfortunately my current job keeps me extremely busy so I'm not sure when
> I'll have time to work on this. I will try to start working on some
although all the advantages above look like very good step forward i'm afraid
there is nobody around who is going to write new NS
On 12/20/2010 6:48 PM, Pavel Sanda wrote:
- windows installers. Joost, are there some advances in the
announced 'joint' installer, so we no more proceed with
the doublet official/alternative? or do we continue with
the current 1.6 model? any way we should start to offer
*some* officia
hi,
time to think about beta3.
there is already a couple of things which need to be released
and tested so we should start freezing at certain time.
are there some particular issues you want to push in trunk
before next beta?
we reduced from 3 pages of bugs with 2.0 milestone to nearly
one pag
On 12/20/2010 05:38 PM, Vincent van Ravesteijn wrote:
Author: rgheck
Date: Mon Dec 20 23:33:12 2010
New Revision: 36976
URL: http://www.lyx.org/trac/changeset/36976
Log:
Greyed out notes do produce output, which means that their counters need
to be treated as part of the document. For example, t
On 12/20/2010 05:29 PM, Vincent van Ravesteijn wrote:
Author: rgheck
Date: Mon Dec 20 22:55:09 2010
New Revision: 36974
URL: http://www.lyx.org/trac/changeset/36974
Log:
Finish disentangling tocString(). We introduce a new method, forToc(),
that also makes sure it doesn't do more work than it
> Author: rgheck
> Date: Mon Dec 20 23:33:12 2010
> New Revision: 36976
> URL: http://www.lyx.org/trac/changeset/36976
>
> Log:
> Greyed out notes do produce output, which means that their counters need
> to be treated as part of the document. For example, the footnote numbers
> in LyX are wrong pr
Author: rgheck
Date: Mon Dec 20 22:55:09 2010
New Revision: 36974
URL: http://www.lyx.org/trac/changeset/36974
Log:
Finish disentangling tocString(). We introduce a new method, forToc(),
that also makes sure it doesn't do more work than it needs to do, by
limiting the size to 40 characters. Pre
Georg Baum wrote:
> > Georg, it would be nice while doing this work to update a list of things
> > tex2lyx does not handle. Since I trust you are extra careful when doing
> > this update work, I assume the extra work would be minimal.
>
> Yes, that would be nice. I am only a bit unsure about the l
Georg Baum wrote:
> I would even suggest a new rule that tex2lyx update is mandatory if somebody
> increases the file format (once tex2lyx produces the current format). This
> does not mean that new features need to be supported, but if there are
> syntax changes, tex2lyx should be adapted to th
On 2010-12-17, Helge Hafting wrote:
> On 17. des. 2010 09:37, Guenter Milde wrote:
>> On 2010-12-16, Helge Hafting wrote:
...
>>> In addition to the module itself, the patch touches these 3 files:
>>> src/LaTeXFeatures.cpp (support for multicol.sty)
>> Isn't there a requires keyword in the lay
Jean-Marc Lasgouttes wrote:
> Le 19 déc. 2010 à 21:23, b...@lyx.org a écrit :
>>
>> 316: Nothing to do (tex2lyx does not know subfigures)
>
> Georg, it would be nice while doing this work to update a list of things
> tex2lyx does not handle. Since I trust you are extra careful when doing
> t
Richard Heck wrote:
> On 12/19/2010 08:21 PM, Uwe Stöhr wrote:
>> Hi Georg,
>>
>> good that someone works to update tex2lyx a bit. But I don't
>> understand your plan and your commit logs. E.g. in r36947 you write:
>>
>> > Increase tex2lyx output format to 310.
>> > 299-302: Nothing to do (empty l
Le 20 déc. 2010 à 15:04, Pavel Sanda a écrit :
> completely different. you need to configure with enable-profiling and then
> use sysprof.
No, --enable-profiling is for gprof actually. For sysprof, just compile with
--enable-build-type=rel --enable-debug
JMarc
Pavel Sanda wrote:
> Stephan Witt wrote:
> > >>> Question: what's the best way to solve that?
> > >>> Should the cursor shift operation redraw the current row
> > >>> unconditionally?
> > >>
> > >> if we have to pay next redraw on cursor movement for the sake of this bug
> > >> i vote for wontfix
Stephan Witt wrote:
> >>> Question: what's the best way to solve that?
> >>> Should the cursor shift operation redraw the current row unconditionally?
> >>
> >> if we have to pay next redraw on cursor movement for the sake of this bug
> >> i vote for wontfix. its damn hard to remedy lyx from slown
Liviu Andronic wrote:
> On Mon, Dec 20, 2010 at 2:34 PM, Pavel Sanda wrote:
> > Liviu Andronic wrote:
> >> I don't think 1.6.7 provides this functionality, unless the user is
> >> using some fancy config.
> >
> > but if he uses, then backward search using lyx pipes can be related,
> > the pipe han
Am 20.12.2010 um 14:19 schrieb Vincent van Ravesteijn:
> On Mon, Dec 20, 2010 at 2:06 PM, Pavel Sanda wrote:
>> Stephan Witt wrote:
>>> Question: what's the best way to solve that?
>>> Should the cursor shift operation redraw the current row unconditionally?
>>
>> if we have to pay next redraw o
On Mon, Dec 20, 2010 at 2:34 PM, Pavel Sanda wrote:
> Liviu Andronic wrote:
>> I don't think 1.6.7 provides this functionality, unless the user is
>> using some fancy config.
>
> but if he uses, then backward search using lyx pipes can be related,
> the pipe handling code is dark enough ;)
>
> any
Liviu Andronic wrote:
> I don't think 1.6.7 provides this functionality, unless the user is
> using some fancy config.
but if he uses, then backward search using lyx pipes can be related,
the pipe handling code is dark enough ;)
anyway, the comment:
"It persists in lyx 2.0.0. My solutions is to
Vincent van Ravesteijn wrote:
> Why don't you want a redraw when we want to paint the misspelled
> underline if necessary. This is a useful redraw.. right ?
>
> I don't see a problem when moving the cursor is as expensive as
> entering a character :S.
there is quite clear speed difference between
On Mon, Dec 20, 2010 at 2:06 PM, Pavel Sanda wrote:
> Stephan Witt wrote:
>> Question: what's the best way to solve that?
>> Should the cursor shift operation redraw the current row unconditionally?
>
> if we have to pay next redraw on cursor movement for the sake of this bug
> i vote for wontfix.
Stephan Witt wrote:
> Question: what's the best way to solve that?
> Should the cursor shift operation redraw the current row unconditionally?
if we have to pay next redraw on cursor movement for the sake of this bug
i vote for wontfix. its damn hard to remedy lyx from slowness bugs and this
just
Abdelrazak Younes wrote:
> I don't think this could happen but yes, better safe than sorry :-)
dunno how much is this related to the last changes but is see new assert
in bugzilla with lyx::RandomAccessList::operator[] keyword...
#7188
pavel
On Mon, Dec 20, 2010 at 9:54 AM, Jean-Marc Lasgouttes
wrote:
> Could there be some connection between evince and LyX (related to
> forward/backward search)?
>
I've been reading the descriptions in the bug report, and I'm
wondering if some of them are not related to the table painting issues
that
https://bugs.launchpad.net/bugs/353449
On Mon, Dec 20, 2010 at 9:54 AM, Jean-Marc Lasgouttes
wrote:
>> evince is not qt based, so i cant imagine what can cause such interference.
>> do yo se some clipboard manager btw?
>
> I don't, but I am not the author of the comment. I can ask, though.
>
> C
Am 20.12.2010 02:35, schrieb Richard Heck:
That said, if we know that tex2lyx is not detecting features representable in
files of format NNN,
then that is a bug, and it would be appropriate to enter it into trac.
This would pollute Trac because there are now already many of them. But I will n
Le 19 déc. 2010 à 23:32, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
>> Running on a machine with Ubuntu 10.10 64bit and Lyx 1.6.7 as well as
>> 1.6.8.
>> Not sure if it's the same bug, but in my case, I isolated the problem to a
>> simple procedure:
>> Close everything (best to reboot) and
Le 19 déc. 2010 à 21:23, b...@lyx.org a écrit :
>
> 316: Nothing to do (tex2lyx does not know subfigures)
Georg, it would be nice while doing this work to update a list of things tex2lyx
does not handle. Since I trust you are extra careful when doing this update
work,
I assume the extra wor
33 matches
Mail list logo
