Guillaume Munch wrote:
> What do you think?
I do not really have opinion about such change. P
On 19.10.2016 07:08, racoon wrote:
On 19.10.2016 07:03, racoon wrote:
On 18.10.2016 21:44, Guillaume Munch wrote:
Le 15/10/2016 à 11:39, racoon a écrit :
Typing within the master's work area is slow on my computer (while
it is
fine in 2.2.2 and 2.1.5). Maybe this just has to do with some debug
On 19.10.2016 07:03, racoon wrote:
On 18.10.2016 21:44, Guillaume Munch wrote:
Le 15/10/2016 à 11:39, racoon a écrit :
Typing within the master's work area is slow on my computer (while it is
fine in 2.2.2 and 2.1.5). Maybe this just has to do with some debugging
running in the background or so
On 18.10.2016 21:44, Guillaume Munch wrote:
Le 15/10/2016 à 11:39, racoon a écrit :
Typing within the master's work area is slow on my computer (while it is
fine in 2.2.2 and 2.1.5). Maybe this just has to do with some debugging
running in the background or so?
A minimal working example to rep
On 18.10.2016 18:43, Kornel Benko wrote:
Am Dienstag, 18. Oktober 2016 um 18:30:22, schrieb racoon
On 18.10.2016 10:13, Kornel Benko wrote:
Am Dienstag, 18. Oktober 2016 um 09:58:14, schrieb Jean-Marc Lasgouttes
Le 18/10/2016 à 09:55, racoon a écrit :
On 18.10.2016 09:46, Jean-Marc Lasgo
On Thu, Sep 08, 2016 at 03:59:50PM +0200, Jean-Marc Lasgouttes wrote:
> commit 82808fea04315fd323ec074e8ad7865d190987d4
> Author: Jean-Marc Lasgouttes
> Date: Tue Sep 6 11:17:10 2016 +0200
>
> Set window title according to platform UI
>
> The window title is built from the current
On Wed, Oct 19, 2016 at 01:20:04AM +0200, Kornel Benko wrote:
> I have no crash either.
Thank you for trying. I cannot reproduce this with the above recipe
either now. I found a SIGSEGV that I don't know if it is related. I will
report that (in a different thread).
Scott
signature.asc
Descript
On Tue, Oct 18, 2016 at 11:40:19PM +0200, Guillaume Munch wrote:
> Le 18/10/2016 à 22:05, Enrico Forestieri a écrit :
> >On Tue, Oct 18, 2016 at 09:47:28PM +0200, Guillaume Munch wrote:
> >>
> >>Yes, this can be limited to the non-nice export. How strongly do you
> >>feel about it? Given the other
Am Dienstag, 18. Oktober 2016 um 19:11:42, schrieb Scott Kostyshak
> On Tue, Oct 18, 2016 at 06:12:52PM -0400, Richard Heck wrote:
> > On 10/18/2016 05:20 PM, Scott Kostyshak wrote:
> > > On Sun, Sep 18, 2016 at 10:18:22PM -0400, Scott Kostyshak wrote:
> > >
> > >> Richard, I just wanted to make
On Tue, Oct 18, 2016 at 06:12:52PM -0400, Richard Heck wrote:
> On 10/18/2016 05:20 PM, Scott Kostyshak wrote:
> > On Sun, Sep 18, 2016 at 10:18:22PM -0400, Scott Kostyshak wrote:
> >
> >> Richard, I just wanted to make sure you saw this email. Don't worry of
> >> course if you don't have enough ti
On 10/18/2016 05:20 PM, Scott Kostyshak wrote:
> On Sun, Sep 18, 2016 at 10:18:22PM -0400, Scott Kostyshak wrote:
>
>> Richard, I just wanted to make sure you saw this email. Don't worry of
>> course if you don't have enough time to take a look. To reproduce, you
>> do not need to have the XeTeX bi
Le 18/10/2016 à 22:05, Enrico Forestieri a écrit :
On Tue, Oct 18, 2016 at 09:47:28PM +0200, Guillaume Munch wrote:
Yes, this can be limited to the non-nice export. How strongly do you
feel about it? Given the other replies I am tempted to push my patch as is.
I have no strong opinion on this
On Sun, Sep 18, 2016 at 10:18:22PM -0400, Scott Kostyshak wrote:
> Richard, I just wanted to make sure you saw this email. Don't worry of
> course if you don't have enough time to take a look. To reproduce, you
> do not need to have the XeTeX binaries. You can do the following:
>
> 1. open lib/ex
On 18.10.2016 21:35, racoon wrote:
I think the attached fix leads to more intuitive results for added table
borders.
This solves one strange case:
1. create a new table (with the default borders, in particular the last
row has the borders |c|)
column not row I meant.
2. add a column after th
Le 18/10/16 à 22:10, Richard Heck a écrit :
I also found that calls to TabWorkArea::updateTabTexts are
expensive and repeatedb. This amounts to 31% of the total amount of CPU,
shared between QTabWidget::setTabText and QTabWidget::setTabIcon.
TabWorkArea::updateTabTexts is connected to the signal
On 10/18/2016 03:44 PM, Guillaume Munch wrote:
> Le 15/10/2016 à 11:39, racoon a écrit :
>> Typing within the master's work area is slow on my computer (while it is
>> fine in 2.2.2 and 2.1.5). Maybe this just has to do with some debugging
>> running in the background or so?
>>
>
>
> Profiling show
On 18.10.2016 21:35, racoon wrote:
I think the attached fix leads to more intuitive results for added table
borders.
This solves one strange case:
1. create a new table (with the default borders, in particular the last
row has the borders |c|)
2. add a column after the last most right) column
A
On Tue, Oct 18, 2016 at 09:47:28PM +0200, Guillaume Munch wrote:
>
> Yes, this can be limited to the non-nice export. How strongly do you
> feel about it? Given the other replies I am tempted to push my patch as is.
I have no strong opinion on this. However, sometimes I use sed or
awk for changin
Le 18/10/2016 à 09:20, Enrico Forestieri a écrit :
Maybe this can be limited to the non "nice" export? This is the format
that is exported only for previewing and not for generating latex code
meant for later editing. Specifically, this is the .tex file you get
in the temp dir, where you could a
Le 15/10/2016 à 11:39, racoon a écrit :
Typing within the master's work area is slow on my computer (while it is
fine in 2.2.2 and 2.1.5). Maybe this just has to do with some debugging
running in the background or so?
Profiling shows that calls to BufferParams::isExportableFormat
are numerous
I think the attached fix leads to more intuitive results for added table
borders.
This solves one strange case:
1. create a new table (with the default borders, in particular the last
row has the borders |c|)
2. add a column after the last most right) column
Actual result:
- The last two rows
On 2016-10-18, Kornel Benko wrote:
> Am Dienstag, 18. Oktober 2016 um 18:11:01, schrieb jeanpierre.chret...@free.fr
...
>> I did also run ctest both with master and branch with command
>> $ctest -R pdf2
>> and I find about 150 fails over about 350 tests in both cases. Is that
>> normal ?
> It
On 2016-10-18, jeanpierre.chret...@free.fr wrote:
>> Am Donnerstag, 13. Oktober 2016 um 09:39:29, schrieb Jean-Pierre
>> Chrétien
>> >
>> > Maybe I should rebuild the cbuildmaster dir from scratch?
>> >
>> I think, cleaning Testing/.lyx should be OK.
> OK, I did it, and the failing tests (d
Le 18/10/2016 à 09:44, Jean-Marc Lasgouttes a écrit :
I agree though that it is always annoying to have to guess what kind of
string is needed. I do not think that we implement a clear policy on
that. It would be nice to have one, so that we agree on what should be
what.
From what I got from
Le 18/10/2016 à 09:41, Jean-Marc Lasgouttes a écrit :
Le 18/10/2016 à 01:08, Guillaume Munch a écrit :
Le 17/10/2016 à 00:35, Guillaume Munch a écrit :
commit 01d6333db21d3ed2c16f7c958fa204ff1c52044a
Author: Guillaume Munch
Date: Wed Sep 7 01:36:55 2016 +0100
Implement reverse-search in
Am Dienstag, 18. Oktober 2016 um 18:42:02, schrieb Tommaso Cucinotta
> On 18/10/2016 17:14, Kornel Benko wrote:
> > Maybe mixed compilation units (compiled with different settings)?
> > I see 2 possibilities
> > 1.) try on _really_ clean build tree.
>
> had clean, distclean, autogen.sh sever
Am Dienstag, 18. Oktober 2016 um 18:30:22, schrieb racoon
> On 18.10.2016 10:13, Kornel Benko wrote:
> > Am Dienstag, 18. Oktober 2016 um 09:58:14, schrieb Jean-Marc Lasgouttes
> >
> >> Le 18/10/2016 à 09:55, racoon a écrit :
> >>>
> >>>
> >>> On 18.10.2016 09:46, Jean-Marc Lasgouttes wrote:
> >
On 18/10/2016 17:14, Kornel Benko wrote:
Maybe mixed compilation units (compiled with different settings)?
I see 2 possibilities
1.) try on _really_ clean build tree.
had clean, distclean, autogen.sh several times :-(...
However, seems the crash on start went away after
--disable-st
On 18.10.2016 10:13, Kornel Benko wrote:
Am Dienstag, 18. Oktober 2016 um 09:58:14, schrieb Jean-Marc Lasgouttes
Le 18/10/2016 à 09:55, racoon a écrit :
On 18.10.2016 09:46, Jean-Marc Lasgouttes wrote:
Le 15/10/2016 à 19:53, racoon a écrit :
Yes, I think so.
Does compiling in normal mod
Am Dienstag, 18. Oktober 2016 um 18:11:01, schrieb jeanpierre.chret...@free.fr
>
> > Am Donnerstag, 13. Oktober 2016 um 09:39:29, schrieb Jean-Pierre
> > Chrétien
>
> > >
> > > Maybe I should rebuild the cbuildmaster dir from scratch?
> > >
> >
> > I think, cleaning Testing/.lyx should be OK.
> Am Donnerstag, 13. Oktober 2016 um 09:39:29, schrieb Jean-Pierre
> Chrétien
> >
> > Maybe I should rebuild the cbuildmaster dir from scratch?
> >
>
> I think, cleaning Testing/.lyx should be OK.
OK, I did it, and the failing tests (due to the userdir problem) now pass.
But I still have fa
On 18.10.2016 09:37, Jean-Marc Lasgouttes wrote:
I had a go earlier to replace TEXT_TO_INSET_OFFSET with a function that
computes the length according to current zoom and screen resolution. I
abandonned the patch (attached) for now because it created problems for
vertical spacing.
Yes, maybe th
Am Dienstag, 18. Oktober 2016 um 16:58:02, schrieb Tommaso Cucinotta
> On 17/10/2016 23:24, Kornel Benko wrote:
> > Please try with std:regex enabled.
>
> just realized I was missing libboost_regex-dev, that's why configure was not
> using nor linking to that lib. After adding that, and compili
On 17/10/2016 23:24, Kornel Benko wrote:
Please try with std:regex enabled.
just realized I was missing libboost_regex-dev, that's why configure was not
using nor linking to that lib. After adding that, and compiling with
--without-included-boost --disable-std-regex
I have now a spectacular
On 18.10.2016 09:37, Jean-Marc Lasgouttes wrote:
Le 17/10/2016 à 01:28, racoon a écrit :
Though I have a non-high resolution display. Maybe it does not look as
good on a high-res display. If so, maybe there should be an adjustment
for high-res displays?
I had a go earlier to replace TEXT_TO_IN
On 2016-10-18, Jean-Marc Lasgouttes wrote:
> Le 18/10/2016 à 01:10, Guillaume Munch a écrit :
>> captions in listings appear as:
>> \begin{lstlisting}%
>> [caption={Caption}]
>> \end{lstlisting}
> In this case and in the sub-caption case, I do not think that LaTeX
> needs the "%".
Whitesp
Am Dienstag, 18. Oktober 2016 um 09:58:14, schrieb Jean-Marc Lasgouttes
> Le 18/10/2016 à 09:55, racoon a écrit :
> >
> >
> > On 18.10.2016 09:46, Jean-Marc Lasgouttes wrote:
> >> Le 15/10/2016 à 19:53, racoon a écrit :
> >>> Yes, I think so.
> >>
> >> Does compiling in normal mode help to recove
Le 18/10/2016 à 09:55, racoon a écrit :
On 18.10.2016 09:46, Jean-Marc Lasgouttes wrote:
Le 15/10/2016 à 19:53, racoon a écrit :
Yes, I think so.
Does compiling in normal mode help to recover the original speed?
Could you remind me how to compile in non-debug mode? Is that a setting
in CM
Le 14/10/2016 à 11:46, mn a écrit :
These are really low hanging fruit:
Image files are suboptimally compressed.
Vector: processed 1435 files saving 2.2 MB ( 56% )
in about 20 seconds
Results from a fresh download of 2.2.2 mac.
If someone could just once recompress those files in the devel-t
On 18.10.2016 09:46, Jean-Marc Lasgouttes wrote:
Le 15/10/2016 à 19:53, racoon a écrit :
Yes, I think so.
Does compiling in normal mode help to recover the original speed?
Could you remind me how to compile in non-debug mode? Is that a setting
in CMAKE that I have to uncheck or so?
Dani
Le 15/10/2016 à 19:53, racoon a écrit :
Yes, I think so.
Does compiling in normal mode help to recover the original speed?
JMarc
On 15.10.2016 18:39, Jean-Marc Lasgouttes wrote:
Did you compile in debug mode ?
Le 18/10/2016 à 01:08, Guillaume Munch a écrit :
Le 17/10/2016 à 00:35, Guillaume Munch a écrit :
commit 1f945177b9628b213c60872df88f2d155c3d6c54
Author: Guillaume Munch
Date: Sun Sep 25 12:37:40 2016 +0200
Docstringify getLongString in general and preamble snippets in
particular
Pr
Le 18/10/2016 à 01:08, Guillaume Munch a écrit :
Le 17/10/2016 à 00:35, Guillaume Munch a écrit :
commit 01d6333db21d3ed2c16f7c958fa204ff1c52044a
Author: Guillaume Munch
Date: Wed Sep 7 01:36:55 2016 +0100
Implement reverse-search in the source panel
Double-clicking on a line in the
Le 18/10/2016 à 01:10, Guillaume Munch a écrit :
Yes, both metrics and painting were taken into account when writing the
patch, and what you see is the result.
It did not look obvious from the patch, but I do trust you on this!
JMarc
Le 17/10/2016 à 01:28, racoon a écrit :
I just tried to do some fine tuning on the inset offsets (minimalistic
and classic so far).
Hi racoon,
I am glad you are looking at this. I agree that small offsets are better.
Though I have a non-high resolution display. Maybe it does not look as
good
Le 18/10/2016 à 01:10, Guillaume Munch a écrit :
captions in listings appear as:
\begin{lstlisting}%
[caption={Caption}]
\end{lstlisting}
In this case and in the sub-caption case, I do not think that LaTeX
needs the "%".
JMarc
On Tue, Oct 18, 2016 at 01:10:36AM +0200, Guillaume Munch wrote:
> Le 17/10/2016 à 04:12, Pavel Sanda a écrit :
> > Guillaume Munch wrote:
> > > Dear list,
> > >
> > > The attached patches add safe line breaks ("%\n") to the output, to
> > > crucially increase the precision of forward/reverse-sea
47 matches
Mail list logo
