On Fri, Jun 26, 2015 at 02:00:33AM +0100, Guillaume M-M wrote:
> Le 25/06/2015 23:45, Richard Heck a écrit :
> >On 06/25/2015 02:58 PM, Enrico Forestieri wrote:
> >>On Thu, Jun 25, 2015 at 02:16:19PM -0400, Richard Heck wrote:
> >>>This more or less completes this work?
> >>I think so. The most imp
Le 25/06/2015 23:45, Richard Heck a écrit :
On 06/25/2015 02:58 PM, Enrico Forestieri wrote:
On Thu, Jun 25, 2015 at 02:16:19PM -0400, Richard Heck wrote:
This more or less completes this work?
I think so. The most important glitches were identified and solved.
(For which thanks very much, t
On 06/25/2015 02:58 PM, Enrico Forestieri wrote:
On Thu, Jun 25, 2015 at 02:16:19PM -0400, Richard Heck wrote:
This more or less completes this work?
I think so. The most important glitches were identified and solved.
(For which thanks very much, to you
and Guillaume.)
The credit goes mainly
On Thu, Jun 25, 2015 at 02:16:19PM -0400, Richard Heck wrote:
> On 06/25/2015 02:13 PM, Enrico Forestieri wrote:
> >On Thu, Jun 25, 2015 at 01:44:15PM +0200, Enrico Forestieri wrote:
> >>On Thu, Jun 25, 2015 at 10:16:21AM +0200, Enrico Forestieri wrote:
> >>>The third patch is the simpler one propo
On 06/25/2015 02:13 PM, Enrico Forestieri wrote:
On Thu, Jun 25, 2015 at 01:44:15PM +0200, Enrico Forestieri wrote:
On Thu, Jun 25, 2015 at 10:16:21AM +0200, Enrico Forestieri wrote:
The third patch is the simpler one proposed by Guillaume. I have already
applied the better patch to master but
On Thu, Jun 25, 2015 at 01:44:15PM +0200, Enrico Forestieri wrote:
> On Thu, Jun 25, 2015 at 10:16:21AM +0200, Enrico Forestieri wrote:
> >
> > The third patch is the simpler one proposed by Guillaume. I have already
> > applied the better patch to master but there is a glitch with it.
> > Namely,
On Thu, Jun 25, 2015 at 10:16:21AM +0200, Enrico Forestieri wrote:
>
> The third patch is the simpler one proposed by Guillaume. I have already
> applied the better patch to master but there is a glitch with it.
> Namely, if a preview snippet produces a blank image, its metrics are
> not invalidat
On Wed, Jun 24, 2015 at 09:36:50PM -0400, Richard Heck wrote:
> On 06/24/2015 08:49 PM, Guillaume M-M wrote:
> >Le 25/06/2015 00:44, Enrico Forestieri a écrit :
> >>On Mon, Jun 22, 2015 at 11:32:17PM +0100, Guillaume M-M wrote:
> >>>
> >>>3) Previews have the incorrect size with layouts that offer
On 06/24/2015 08:49 PM, Guillaume M-M wrote:
Le 25/06/2015 00:44, Enrico Forestieri a écrit :
On Mon, Jun 22, 2015 at 11:32:17PM +0100, Guillaume M-M wrote:
3) Previews have the incorrect size with layouts that offer font
sizes other
than 1[0-2]pt (lyx-preview-fontsize.lyx). The legacy metho
Le 25/06/2015 00:44, Enrico Forestieri a écrit :
On Mon, Jun 22, 2015 at 11:32:17PM +0100, Guillaume M-M wrote:
3) Previews have the incorrect size with layouts that offer font sizes other
than 1[0-2]pt (lyx-preview-fontsize.lyx). The legacy method offers a
function that retrieves the actual fo
On Mon, Jun 22, 2015 at 11:32:17PM +0100, Guillaume M-M wrote:
>
> 3) Previews have the incorrect size with layouts that offer font sizes other
> than 1[0-2]pt (lyx-preview-fontsize.lyx). The legacy method offers a
> function that retrieves the actual font size and calculates the actual dpi.
> Att
On Tue, Jun 23, 2015 at 11:14:29AM -0400, Richard Heck wrote:
> On 06/22/2015 06:59 PM, Enrico Forestieri wrote:
> >On Sat, Jun 20, 2015 at 02:11:53AM +0200, Enrico Forestieri wrote:
> >>On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
> >>
> >>>Also, lyx-preview-macros-2-lassert.lyx
On Tue, Jun 23, 2015 at 10:20:21PM +0200, Georg Baum wrote:
> Enrico Forestieri wrote:
>
> > I don't know, maybe this is a case of a race condition. Most probably,
> > with preview on, updateMacros() is not called (or is called later) and
> > the MacroData:sym_ pointer is not updated at the time M
On Tue, Jun 23, 2015 at 10:20:21PM +0200, Georg Baum wrote:
> Enrico Forestieri wrote:
>
> > I don't know, maybe this is a case of a race condition. Most probably,
> > with preview on, updateMacros() is not called (or is called later) and
> > the MacroData:sym_ pointer is not updated at the time M
Enrico Forestieri wrote:
> I don't know, maybe this is a case of a race condition. Most probably,
> with preview on, updateMacros() is not called (or is called later) and
> the MacroData:sym_ pointer is not updated at the time MacroData::xlmname()
> is called so that it contains bogus values. This
On Tue, Jun 23, 2015 at 02:23:18PM +0100, Guillaume M-M wrote:
> Le 23/06/2015 10:46, Enrico Forestieri a écrit :
> >
> >Indeed, this has to do with the general problem of copying macros and
> >how the various structures are carried on when copying.
>
> OK for the fact that this is not a regressio
On Tue, Jun 23, 2015 at 02:23:18PM +0100, Guillaume M-M wrote:
> Le 23/06/2015 10:46, Enrico Forestieri a écrit :
> >
> >Indeed, this has to do with the general problem of copying macros and
> >how the various structures are carried on when copying.
>
> OK for the fact that this is not a regressio
On 06/22/2015 06:59 PM, Enrico Forestieri wrote:
On Sat, Jun 20, 2015 at 02:11:53AM +0200, Enrico Forestieri wrote:
On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
Also, lyx-preview-macros-2-lassert.lyx no longer lasserts but on opening the
preview is not generated because \Colo
Le 23/06/2015 10:46, Enrico Forestieri a écrit :
On Tue, Jun 23, 2015 at 11:18:56AM +0200, Enrico Forestieri wrote:
On Tue, Jun 23, 2015 at 02:44:00AM +0100, Guillaume M-M wrote:
Still there at cd046f0e (master). But here's the trace I get when it crashes
right at the first Ctrl+C:
I doubt t
On Tue, Jun 23, 2015 at 11:18:56AM +0200, Enrico Forestieri wrote:
> On Tue, Jun 23, 2015 at 02:44:00AM +0100, Guillaume M-M wrote:
> >
> > Still there at cd046f0e (master). But here's the trace I get when it crashes
> > right at the first Ctrl+C:
>
> I doubt this has anything to do with the rece
On Tue, Jun 23, 2015 at 02:44:00AM +0100, Guillaume M-M wrote:
> Le 23/06/2015 02:36, Guillaume M-M a écrit :
> >Le 23/06/2015 02:34, Guillaume M-M a écrit :
> >>Another segfault in the stable branch involving previews (and master as
> >>well). When Instant preview is on and one copies a formula, i
Le 23/06/2015 02:36, Guillaume M-M a écrit :
Le 23/06/2015 02:34, Guillaume M-M a écrit :
Another segfault in the stable branch involving previews (and master as
well). When Instant preview is on and one copies a formula, it randomly
crashes. In the attached, select the math inset and hold Ctrl+
Le 23/06/2015 02:34, Guillaume M-M a écrit :
Another segfault in the stable branch involving previews (and master as
well). When Instant preview is on and one copies a formula, it randomly
crashes. In the attached, select the math inset and hold Ctrl+C until it
segfaults. Sometimes it happens on
Another segfault in the stable branch involving previews (and master as
well). When Instant preview is on and one copies a formula, it randomly
crashes. In the attached, select the math inset and hold Ctrl+C until it
segfaults. Sometimes it happens on the first press. This is pretty
annoying be
On Mon, Jun 22, 2015 at 11:32:17PM +0100, Guillaume M-M wrote:
>
> 1) SIGSEGV with previews (no math macros involved). I believe this is the
> one I mentioned in a previous message. See the attached
> lyx-preview-sigsegv.lyx for instructions.
Thanks for catching this. I fixed this issue at cd046f
On Sat, Jun 20, 2015 at 02:11:53AM +0200, Enrico Forestieri wrote:
> On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
>
> > Also, lyx-preview-macros-2-lassert.lyx no longer lasserts but on opening the
> > preview is not generated because \Coloneqq is not defined. This looks like
> >
Three bugs in the current stable (93c0512b). The third one has an easy
fix (and also a very trivial partial fix if you want to move forward
with the release). The first two could be postponed after the release,
or maybe they are trivial as well to Enrico. Found the first two while
testing my so
Guillaume M-M wrote:
> Thank you very much, this is really quick now. Thanks also for the timer
> for generating previews. Also I only had 1 segmentation error, which I
> could not reproduce unfortunately. It happened after changing from
> "Instant preview: On" to "No maths" and zooming. But proba
On Sat, Jun 20, 2015 at 09:13:40PM -0400, Richard Heck wrote:
> On 06/20/2015 08:45 PM, Scott Kostyshak wrote:
> >On Sun, Jun 21, 2015 at 01:38:55AM +0100, Guillaume M-M wrote:
> >
> >>Thank you for the convenience.
> >>
> >>I have no other issue to report for stable, Enrico wins :)
> >LyX users a
On 06/20/2015 08:45 PM, Scott Kostyshak wrote:
On Sun, Jun 21, 2015 at 01:38:55AM +0100, Guillaume M-M wrote:
Thank you for the convenience.
I have no other issue to report for stable, Enrico wins :)
LyX users across the globe win now :)
Thanks to both of you!
For stable, this is again you
On Sun, Jun 21, 2015 at 01:38:55AM +0100, Guillaume M-M wrote:
> Thank you for the convenience.
>
> I have no other issue to report for stable, Enrico wins :)
LyX users across the globe win now :)
Thanks to both of you!
Scott
Le 20/06/2015 15:58, Enrico Forestieri a écrit :
On Sat, Jun 20, 2015 at 08:14:03AM +0100, Guillaume M-M wrote:
Le 20/06/2015 01:11, Enrico Forestieri a écrit :
On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
Lastly I see that you prevent loading the microtype package by redefi
On Sat, Jun 20, 2015 at 04:58:35PM +0200, Enrico Forestieri wrote:
> On Sat, Jun 20, 2015 at 08:14:03AM +0100, Guillaume M-M wrote:
> > Le 20/06/2015 01:11, Enrico Forestieri a écrit :
> > >On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
> > >
> > >>Lastly I see that you prevent load
On Sat, Jun 20, 2015 at 08:14:03AM +0100, Guillaume M-M wrote:
> Le 20/06/2015 01:11, Enrico Forestieri a écrit :
> >On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
> >
> >>Lastly I see that you prevent loading the microtype package by redefining
> >>\usepackage as you described earl
Le 20/06/2015 01:11, Enrico Forestieri a écrit :
On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
Le 07/06/2015 12:49, Enrico Forestieri a écrit :
On Sat, Jun 06, 2015 at 08:07:12PM +0100, Guillaume M-M wrote:
lyx-preview-macros2-failure.lyx shows two cases where a macro is for
On Fri, Jun 19, 2015 at 04:50:43PM +0100, Guillaume M-M wrote:
> Le 07/06/2015 12:49, Enrico Forestieri a écrit :
> >On Sat, Jun 06, 2015 at 08:07:12PM +0100, Guillaume M-M wrote:
> >>
> >>lyx-preview-macros2-failure.lyx shows two cases where a macro is forgotten
> >>from the list. The third inset
Le 07/06/2015 12:49, Enrico Forestieri a écrit :
On Sat, Jun 06, 2015 at 08:07:12PM +0100, Guillaume M-M wrote:
lyx-preview-macros2-failure.lyx shows two cases where a macro is forgotten
from the list. The third inset works and is meant as a control. All 3 work
without the patch.
Here I was f
2015-06-14 16:04 GMT+02:00 Enrico Forestieri :
> I agree that this would have been better but, unfortunately, it doesn't
> fit the instant preview infrastructure. You wold have to output different
> definitions depending on whether you compile the whole set of snippets
> or only some of them. This
On Sun, Jun 14, 2015 at 01:34:40PM +0200, Jürgen Spitzmüller wrote:
> 2015-06-14 13:31 GMT+02:00 Enrico Forestieri :
>
> > Jürgen, this is going to become complicated and fragile. What about
> > following the same strategy used in stable?
> > This implies reverting bc47054b.
> >
>
> Since I do n
2015-06-14 13:31 GMT+02:00 Enrico Forestieri :
> Jürgen, this is going to become complicated and fragile. What about
> following the same strategy used in stable?
> This implies reverting bc47054b.
>
Since I do not have time to investigate further, please do whatever you see
fit.
I would have pr
On Thu, Jun 04, 2015 at 07:25:25PM +0200, Enrico Forestieri wrote:
> On Thu, Jun 04, 2015 at 06:56:46PM +0200, Jürgen Spitzmüller wrote:
> > 2015-06-04 18:39 GMT+02:00 Enrico Forestieri :
> >
> > > Yes, I can reproduce in master. It does not occur in stable, where a
> > > different strategy is us
On 06/07/2015 07:49 AM, Enrico Forestieri wrote:
The attached patch solves all of the above problems (and also the
segfault you report separately) for me. I am also attaching the patch
for #9354 accordingly updated. Please test both and report the issues
you find. If your paper pass the tests,
On Fri, Jun 05, 2015 at 05:11:45PM -0400, Scott Kostyshak wrote:
> On Fri, Jun 5, 2015 at 3:40 AM, Jean-Marc Lasgouttes
> wrote:
> > Le 05/06/2015 09:14, Enrico Forestieri a écrit :
> >>
> >> A possible way out would be outputting all the macros once at the
> >> beginning of the file, such that t
On Sat, Jun 06, 2015 at 08:18:12PM +0200, Kornel Benko wrote:
>
> But I wonder why there are preview entries in the lyxpreview*.tex
> ...
> \begin{document}
> \begin{preview}
> ${\displaystyle {#1}}$
> \end{preview}
>
> \begin{preview}
> $#1$
> \end{preview}
>
> \begin{preview}
> ${\scriptstyle
On Sat, Jun 06, 2015 at 08:20:43PM +0100, Guillaume M-M wrote:
>
> Obvious one to test for
Thanks for spotting this. It is due to the recursion in the macro
definitions. The patch I sent takes this into account and lyx does
not segfaults anymore, but latex will be caught in an endless loop
and th
On Sat, Jun 06, 2015 at 08:07:12PM +0100, Guillaume M-M wrote:
>
> lyx-preview-macros2-failure.lyx shows two cases where a macro is forgotten
> from the list. The third inset works and is meant as a control. All 3 work
> without the patch.
Here I was forgetting to also scan nested insets.
> lyx-
Le 06/06/2015 18:12, Enrico Forestieri a écrit :
On Sat, Jun 06, 2015 at 03:23:48PM +0200, Kornel Benko wrote:
Am Samstag, 6. Juni 2015 um 13:13:22, schrieb Enrico Forestieri
+void InsetMathHull::usedMacros(MathData const & md, MacroNameSet & macros)
const
+{
+ for (size_t i = 0; i < m
Le 06/06/2015 18:12, Enrico Forestieri a écrit :
On Sat, Jun 06, 2015 at 03:23:48PM +0200, Kornel Benko wrote:
Am Samstag, 6. Juni 2015 um 13:13:22, schrieb Enrico Forestieri
+void InsetMathHull::usedMacros(MathData const & md, MacroNameSet & macros)
const
+{
+ for (size_t i = 0; i < m
Am Samstag, 6. Juni 2015 um 19:12:45, schrieb Enrico Forestieri
> On Sat, Jun 06, 2015 at 03:23:48PM +0200, Kornel Benko wrote:
>
> > Am Samstag, 6. Juni 2015 um 13:13:22, schrieb Enrico Forestieri
> >
> > > +void InsetMathHull::usedMacros(MathData const & md, MacroNameSet &
> > > macros) cons
On Sat, Jun 06, 2015 at 03:23:48PM +0200, Kornel Benko wrote:
> Am Samstag, 6. Juni 2015 um 13:13:22, schrieb Enrico Forestieri
>
> > +void InsetMathHull::usedMacros(MathData const & md, MacroNameSet & macros)
> > const
> > +{
> > + for (size_t i = 0; i < md.size(); ++i) {
> > +
Am Samstag, 6. Juni 2015 um 13:13:22, schrieb Enrico Forestieri
> +void InsetMathHull::usedMacros(MathData const & md, MacroNameSet & macros)
> const
> +{
> + for (size_t i = 0; i < md.size(); ++i) {
> + MathMacro * mi = const_cast *>(md[i].nucleus()->asMacro());
> +
On Fri, Jun 05, 2015 at 09:40:39AM +0200, Jean-Marc Lasgouttes wrote:
> Le 05/06/2015 09:14, Enrico Forestieri a écrit :
> >A possible way out would be outputting all the macros once at the
> >beginning of the file, such that they are seen by all snippets, and then
> >the specific one appearing in
On Fri, Jun 05, 2015 at 11:03:48PM +0100, Guillaume M-M wrote:
> Le 05/06/2015 08:14, Enrico Forestieri a écrit :
> >On Thu, Jun 04, 2015 at 07:32:03PM -0400, Richard Heck wrote:
> >>On 06/04/2015 07:13 PM, Guillaume M-M wrote:
> >>>
> >>>Bad news, it seems to forget that macros can use macros. Wi
Le 05/06/2015 08:14, Enrico Forestieri a écrit :
On Thu, Jun 04, 2015 at 07:32:03PM -0400, Richard Heck wrote:
On 06/04/2015 07:13 PM, Guillaume M-M wrote:
Bad news, it seems to forget that macros can use macros. With the attached
file the preview is as follows:
\begin{preview}
\global\long\d
On Fri, Jun 5, 2015 at 3:40 AM, Jean-Marc Lasgouttes wrote:
> Le 05/06/2015 09:14, Enrico Forestieri a écrit :
>>
>> A possible way out would be outputting all the macros once at the
>> beginning of the file, such that they are seen by all snippets, and then
>> the specific one appearing in a math
Le 05/06/2015 09:14, Enrico Forestieri a écrit :
A possible way out would be outputting all the macros once at the
beginning of the file, such that they are seen by all snippets, and then
the specific one appearing in a math inset (as done in the patch I was
proposing). I'll have a look whether t
On Thu, Jun 04, 2015 at 07:32:03PM -0400, Richard Heck wrote:
> On 06/04/2015 07:13 PM, Guillaume M-M wrote:
> >
> >Bad news, it seems to forget that macros can use macros. With the attached
> >file the preview is as follows:
> >
> >\begin{preview}
> >\global\long\def\b{\a}
> >
> >$\b$
> >\end{prev
On 06/04/2015 07:13 PM, Guillaume M-M wrote:
Bad news, it seems to forget that macros can use macros. With the
attached file the preview is as follows:
\begin{preview}
\global\long\def\b{\a}
$\b$
\end{preview}
I suspect this is why all macros are included.
Richard
Le 04/06/2015 22:29, Enrico Forestieri a écrit :
On Thu, Jun 04, 2015 at 06:33:28PM +0100, Guillaume M-M wrote:
1) the explosion in size mentioned above. This affects both stable and
master. (This is also responsible for a regression wrt 2.1.3 because of
zooming triggers preview as already disc
On 06/04/2015 05:29 PM, Enrico Forestieri wrote:
Richard, I think that this is pretty safe for stable. It simply omits
the macro definition if it is not used in the math inset. At worst, it
is added unnecessarily if for example \beta appears in the inset and
the macro name is \b, \be, or \bet.
On Thu, Jun 04, 2015 at 06:33:28PM +0100, Guillaume M-M wrote:
>
> 1) the explosion in size mentioned above. This affects both stable and
> master. (This is also responsible for a regression wrt 2.1.3 because of
> zooming triggers preview as already discussed.)
Using vim I duplicated your documen
Le 04/06/2015 20:17, Scott Kostyshak a écrit :
On Thu, Jun 4, 2015 at 3:05 PM, Enrico Forestieri wrote:
On Thu, Jun 04, 2015 at 02:44:56PM -0400, Scott Kostyshak wrote:
On Thu, Jun 4, 2015 at 2:34 PM, Scott Kostyshak wrote:
On Thu, Jun 4, 2015 at 2:31 PM, Enrico Forestieri wrote:
On Thu, J
On 06/04/2015 03:35 PM, Jean-Marc Lasgouttes wrote:
Le 04/06/2015 20:44, Scott Kostyshak a écrit :
Can someone please confirm that I should indeed revert?
I took a look at lyx-preview-explosion.lyx and I can indeed reproduce
the assertion. My guess though is that the referenced commits expose a
Le 04/06/2015 20:44, Scott Kostyshak a écrit :
Can someone please confirm that I should indeed revert?
I took a look at lyx-preview-explosion.lyx and I can indeed reproduce
the assertion. My guess though is that the referenced commits expose a
different bug that has to do with previews and macros
On Thu, Jun 4, 2015 at 3:05 PM, Enrico Forestieri wrote:
> On Thu, Jun 04, 2015 at 02:44:56PM -0400, Scott Kostyshak wrote:
>> On Thu, Jun 4, 2015 at 2:34 PM, Scott Kostyshak wrote:
>> > On Thu, Jun 4, 2015 at 2:31 PM, Enrico Forestieri wrote:
>> >> On Thu, Jun 04, 2015 at 06:33:28PM +0100, Guil
On Thu, Jun 04, 2015 at 02:44:56PM -0400, Scott Kostyshak wrote:
> On Thu, Jun 4, 2015 at 2:34 PM, Scott Kostyshak wrote:
> > On Thu, Jun 4, 2015 at 2:31 PM, Enrico Forestieri wrote:
> >> On Thu, Jun 04, 2015 at 06:33:28PM +0100, Guillaume M-M wrote:
> >>>
> >>> 2) an assertion violation that hap
On Thu, Jun 4, 2015 at 2:34 PM, Scott Kostyshak wrote:
> On Thu, Jun 4, 2015 at 2:31 PM, Enrico Forestieri wrote:
>> On Thu, Jun 04, 2015 at 06:33:28PM +0100, Guillaume M-M wrote:
>>>
>>> 2) an assertion violation that happen on copy-paste with preview (does not
>>> happen without preview). This
On Thu, Jun 4, 2015 at 2:31 PM, Enrico Forestieri wrote:
> On Thu, Jun 04, 2015 at 06:33:28PM +0100, Guillaume M-M wrote:
>>
>> 2) an assertion violation that happen on copy-paste with preview (does not
>> happen without preview). This is a regression in master, does not happen in
>> the stable br
On Thu, Jun 04, 2015 at 06:33:28PM +0100, Guillaume M-M wrote:
>
> 2) an assertion violation that happen on copy-paste with preview (does not
> happen without preview). This is a regression in master, does not happen in
> the stable branch.
I can reproduce the assertion. Bisect points at 73460423
Le 04/06/2015 17:39, Enrico Forestieri a écrit :
On Thu, Jun 04, 2015 at 01:42:51AM +0100, Guillaume M-M wrote:
Le 02/06/2015 23:50, Enrico Forestieri a écrit :
Try using gdb for getting a backtrace after setting a breakpoint at
lassert.cpp:53. If this is due to some recent change, you could t
Le 01/06/2015 23:04, Enrico Forestieri a écrit :
You may be right that microtype may have been the reason why I had the
impression that latex is slower than pdflatex, but this does not account for
the 55s (on a good computer) during which LyX is frozen while generating the
16MB tex file. I will r
On Thu, Jun 04, 2015 at 06:56:46PM +0200, Jürgen Spitzmüller wrote:
> 2015-06-04 18:39 GMT+02:00 Enrico Forestieri :
>
> > Yes, I can reproduce in master. It does not occur in stable, where a
> > different strategy is used, only involving the instant preview scripts.
> > If I am not mistaken, it g
2015-06-04 18:39 GMT+02:00 Enrico Forestieri :
> Yes, I can reproduce in master. It does not occur in stable, where a
> different strategy is used, only involving the instant preview scripts.
> If I am not mistaken, it goes like this. When you enter and then leave
> a math inset, the generated pre
On Thu, Jun 04, 2015 at 01:42:51AM +0100, Guillaume M-M wrote:
> Le 02/06/2015 23:50, Enrico Forestieri a écrit :
> >
> >Try using gdb for getting a backtrace after setting a breakpoint at
> >lassert.cpp:53. If this is due to some recent change, you could try
> >bisetting for finding the relevant c
Le 02/06/2015 23:50, Enrico Forestieri a écrit :
In fact I am currently having an assertion violation when activating full
instant preview (attached), which prevents me from completing the test. Can
anyone tell me how I get more meaningful symbols? I can try to send a
reproducer but I am a bit
On Wed, Jun 03, 2015 at 12:03:55AM +0100, Guillaume M-M wrote:
>
> I did the test, I wrote the following in the preamble:
>
> \PassOptionsToPackage{draft}{microtype}
> \usepackage[protrusion=true,expansion=true,tracking=true,kerning=true,spacing=true]{microtype}
>
> and managed to compile in pos
Le 02/06/2015 23:56, Enrico Forestieri a écrit :
On Tue, Jun 02, 2015 at 11:47:45PM +0100, Guillaume M-M wrote:
Le 02/06/2015 23:38, Enrico Forestieri a écrit :
On Tue, Jun 02, 2015 at 12:04:20AM +0200, Enrico Forestieri wrote:
On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
On Tue, Jun 02, 2015 at 11:47:45PM +0100, Guillaume M-M wrote:
> Le 02/06/2015 23:38, Enrico Forestieri a écrit :
> >On Tue, Jun 02, 2015 at 12:04:20AM +0200, Enrico Forestieri wrote:
> >>On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
> >>
> >>>By the way, a safer way to force not
On Tue, Jun 02, 2015 at 02:19:56AM +0100, Guillaume M-M wrote:
> Le 01/06/2015 23:04, Enrico Forestieri a écrit :
> >>You may be right that microtype may have been the reason why I had the
> >>impression that latex is slower than pdflatex, but this does not account for
> >>the 55s (on a good comput
Le 02/06/2015 23:38, Enrico Forestieri a écrit :
On Tue, Jun 02, 2015 at 12:04:20AM +0200, Enrico Forestieri wrote:
On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
By the way, a safer way to force not loading a package is to prepend
\usepackage with "\@namedef{v...@microtype.sty
On Tue, Jun 02, 2015 at 12:04:20AM +0200, Enrico Forestieri wrote:
> On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
>
> > By the way, a safer way to force not loading a package is to prepend
> > \usepackage with "\@namedef{v...@microtype.sty}{/12/31}". If you just
> > strip the
On Mon, Jun 01, 2015 at 08:50:49PM +0200, Jürgen Spitzmüller wrote:
> 2015-06-01 19:34 GMT+02:00 Enrico Forestieri :
>
> > On Mon, Jun 01, 2015 at 03:50:49PM +0200, Enrico Forestieri wrote:
> > > On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M-M wrote:
> > > >
> > > > 1) b3d2ffc0 introduces
2015-06-02 3:19 GMT+02:00 Guillaume M-M :
> I think this was already addressed by Jürgen at 83a9ed4e.
>
>>
>>
> For me the bug is still here at cb201027. Try again my file
> lyx-bug-renewcommandx.lyx attached to my first message.
>
Cannot reproduce.
Jürgen
Le 01/06/2015 23:04, Enrico Forestieri a écrit :
You may be right that microtype may have been the reason why I had the
impression that latex is slower than pdflatex, but this does not account for
the 55s (on a good computer) during which LyX is frozen while generating the
16MB tex file. I will r
On Mon, Jun 01, 2015 at 10:14:23PM +0100, Guillaume M-M wrote:
> Le 01/06/2015 21:16, Guillaume M-M a écrit :
> >
> >Anyway, here's a suggestion for getting those horrible bitmap fonts out
> >of the way of new users, in a perfectly non-intrusive and
> >backwards-compatible manner: just set Latin Mo
On Mon, Jun 01, 2015 at 11:01:48PM +0100, Guillaume M-M wrote:
> Le 01/06/2015 22:12, Enrico Forestieri a écrit :
> >On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
> >
> >>I don't understand the
> >>backwards-compatibility argument here, I think that it is safer to use the
> >>same
On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
>
> IF the inconsistency regarding the meaning of "Default output format:
> Default" is intended for performance reason and that I did not make you
> change your mind, then I vote for:
> > omitting the microtype
> > package for the sak
Le 01/06/2015 22:12, Enrico Forestieri a écrit :
On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
I don't understand the
backwards-compatibility argument here, I think that it is safer to use the
same default format as Ctrl+R in all cases.
I think that the backward-compatibility
On Mon, Jun 01, 2015 at 09:16:00PM +0100, Guillaume M-M wrote:
>
> Is there any lyx file demonstrating the poor font quality? I have been
> unable to reproduce the font issue in master (after removing the line that
> forces latin modern in instant previews), even with the default setting of
> LyX
Le 01/06/2015 21:16, Guillaume M-M a écrit :
Le 01/06/2015 19:50, Jürgen Spitzmüller a écrit :
2015-06-01 19:34 GMT+02:00 Enrico Forestieri mailto:for...@lyx.org>>:
On Mon, Jun 01, 2015 at 03:50:49PM +0200, Enrico Forestieri wrote:
> On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M
On Mon, Jun 01, 2015 at 08:07:11PM +0100, Guillaume M-M wrote:
> I don't understand the
> backwards-compatibility argument here, I think that it is safer to use the
> same default format as Ctrl+R in all cases.
I think that the backward-compatibility argument is a serious one.
If an old document
Le 01/06/2015 19:50, Jürgen Spitzmüller a écrit :
2015-06-01 19:34 GMT+02:00 Enrico Forestieri mailto:for...@lyx.org>>:
On Mon, Jun 01, 2015 at 03:50:49PM +0200, Enrico Forestieri wrote:
> On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M-M wrote:
> >
> > 1) b3d2ffc0 introduc
Le 01/06/2015 18:16, Enrico Forestieri a écrit :
On Mon, Jun 01, 2015 at 03:50:49PM +0200, Enrico Forestieri wrote:
On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M-M wrote:
2) In master, preview incorrectly calls latex instead of pdflatex if the
default output format is set to "default".
2015-06-01 19:34 GMT+02:00 Enrico Forestieri :
> On Mon, Jun 01, 2015 at 03:50:49PM +0200, Enrico Forestieri wrote:
> > On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M-M wrote:
> > >
> > > 1) b3d2ffc0 introduces a regression in stable and master wrt 2.1.3.
> See the
> > > attached lyx-bug-fo
On Mon, Jun 01, 2015 at 03:50:49PM +0200, Enrico Forestieri wrote:
> On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M-M wrote:
> >
> > 1) b3d2ffc0 introduces a regression in stable and master wrt 2.1.3. See the
> > attached lyx-bug-font2.lyx. This is because legacy_lyxpreview2ppm.py now
> > i
On Mon, Jun 01, 2015 at 03:50:49PM +0200, Enrico Forestieri wrote:
> On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M-M wrote:
> >
> > 2) In master, preview incorrectly calls latex instead of pdflatex if the
> > default output format is set to "default". More details in the attached
> > lyx-b
On Mon, Jun 01, 2015 at 07:26:55AM +0100, Guillaume M-M wrote:
>
> In fact it does not work entirely in master. There is a regression (after
> bc47054b I believe) because compilation can now fail due to \renewcommandx
> being used without the command being defined prior to that (try the attached
>
Le 01/06/2015 08:26, Guillaume M-M a écrit :
5) I find that the preferences dialog is counter-intuitive, with the
distinction between Save, Apply and Close. I don't see the point of
applying without saving (e.g. I think I have disabled instant preview,
but then I find that it is reactivated the n
Le 31/05/2015 16:12, Enrico Forestieri a écrit :
On Sun, May 31, 2015 at 01:24:05PM +0200, Kornel Benko wrote:
Am Sonntag, 31. Mai 2015 um 00:53:41, schrieb Enrico Forestieri
commit ad0d0f6d69a7acd6e99f7858f08b427a28d8f8cc
Author: Enrico Forestieri
Date: Sun May 31 00:52:49 2015 +0200
99 matches
Mail list logo
