Richard Heck wrote:
> This tag cannot be used in a module. I've committed the correct fix.
Oops, thanks for doing that.
Georg
Am 25.01.2016 um 00:28 schrieb Guillaume Munch:
> Georg's commit indeed fixed the alignment, but not the width of the
column, which sometimes makes it hard to see that the first line is
left-aligned and the last one right-aligned. So you are saying that the
fix of multline was not sufficient to
Am 24.01.2016 um 23:29 schrieb Guillaume Munch:
Here are the patches as a single diff. Can you please confirm that this
triggers your issue?
I cannot apply your patch. I get the 2 attached errors and the
TortoiseGit crashes.
I seems that your patches make problems for TortoiseGit (I use
Am 24.01.2016 um 22:02 schrieb Georg Baum:
It is not new. It has been there since at least 15 years, but the UI was in
the printing tab before http://www.lyx.org/trac/changeset/3c2b3e69/lyxgit.
Many thanks! I am good at searching but not in finding ;-)
I updated the docs accordingly.
On Fri, Jan 22, 2016 at 06:36:12PM -0500, Guillaume Munch wrote:
> Le 19/01/2016 19:00, Enrico Forestieri a écrit :
> >On Tue, Jan 19, 2016 at 05:27:47PM -0500, Guillaume Munch wrote:
> >>Le 19/01/2016 16:44, Enrico Forestieri a écrit :
> >>>On Mon, Jan 18, 2016 at 10:37:23PM -0500, Guillaume
The date inset does currently not produce any output. This is a regression
of http://www.lyx.org/trac/changeset/f09a9fe2/lyxgit. Before that change it
did work only by accident: compare_timestamps() is called with two temp
files which both have not been written to yet, so the time stamp
Am 24.01.2016 um 14:50 schrieb Georg Baum :
>
> Stephan Witt wrote:
>
>> Am 24.01.2016 um 13:00 schrieb Stephan Witt :
>> I’ve tried to follow the tokenizing and parsing program flow.
>>
>> While processing the „latin1“ option of „inputenc“ the
Stephan Witt wrote:
> For latin1 documents (e.g. algo2e.tex) it works better. The test now
> passed.
>
> For CJK.lex it’s obviously a problem:
> $ /Users/stephan/git/lyx-build/cmake/2.2.0dev/bin/Debug/tex2lyx -f
> -roundtrip /Users/stephan/git/lyx/src/tex2lyx/test/CJK.tex
>
Stephan Witt wrote:
> You are asking for running tex2lyx in the debugger? Yes, I’m able to do
> so. What should I try exactly?
>
> I started tex2lyx in debugger with these options:
> -f
> -roundtrip
> /Users/stephan/git/lyx/src/tex2lyx/test/algo2e.tex
> /Users/stephan/git/lyx-build/algo2e.lyx
>
Guenter Milde wrote:
> On 2016-01-21, Scott Kostyshak wrote:
>> On Wed, Jan 20, 2016 at 10:18:14PM +0100, Georg Baum wrote:
>>> Scott Kostyshak wrote:
>>> > On Mon, Jan 18, 2016 at 03:59:16PM +, Guenter Milde wrote:
>
>
> ...
>
>>> >> Alternatively, we could have an "untested" branch for
Am 24.01.2016 um 13:00 schrieb Stephan Witt :
>
> Am 24.01.2016 um 12:12 schrieb Georg Baum :
>>
>> Stephan Witt wrote:
>>
>>> You are asking for running tex2lyx in the debugger? Yes, I’m able to do
>>> so. What should I try exactly?
>>>
>>> I
Scott Kostyshak wrote:
> From what I understand, the renaming was done to avoid confusion from
> overloading (see the documentation for the signal in Qt 4.8 or Qt 5). I
> think this is related to this Qt bug [6]. In essence, this seems just to
> be a renaming from error() to errorOccurred().
>
>
Stephan Witt wrote:
> Am 24.01.2016 um 13:00 schrieb Stephan Witt :
> I’ve tried to follow the tokenizing and parsing program flow.
>
> While processing the „latin1“ option of „inputenc“ the encoding of
> the idocstream is changed. (Line 395 of support/docstream.cpp is called)
>
Stephan Witt wrote:
> Yes, we shouldn’t change that on the fly. If we change it we have to
> provide a migration path to copy the current contents to the new location.
> Not very difficult but a change in configure.py would be required.
>
> Since we don’t want to use different settings for Lyx,
Am 24.01.2016 um 12:12 schrieb Georg Baum :
>
> Stephan Witt wrote:
>
>> You are asking for running tex2lyx in the debugger? Yes, I’m able to do
>> so. What should I try exactly?
>>
>> I started tex2lyx in debugger with these options:
>> -f
>> -roundtrip
>>
Uwe Stöhr wrote:
> After the recent boost update in 2.1.x branch I get now many of these
> warnings:
>
> GraphicsCache.cpp
> CL : warning : Boost.Signals is no longer being maintained and is now
> deprecated. Please switch to Boost.Signals2. To disable this warning
> message, define
Am 24.01.2016 um 15:07 schrieb Georg Baum :
>
> Stephan Witt wrote:
>
>> Yes, we shouldn’t change that on the fly. If we change it we have to
>> provide a migration path to copy the current contents to the new location.
>> Not very difficult but a change in
Stephan Witt wrote:
> ATM, the directory LyX is using is "$HOME/Library/Application
> Support/PACKAGE“
>
> PACKAGE is LyX-2.2 on Mac when version suffix „-2.2“ is used.
Looks like QtApplication does something different here than
QtCoreApplication.
>> Stephan, does it work? Note that this is
Am 24.01.2016 um 12:02 schrieb Georg Baum :
>
> Stephan Witt wrote:
>
>> ATM, the directory LyX is using is "$HOME/Library/Application
>> Support/PACKAGE“
>>
>> PACKAGE is LyX-2.2 on Mac when version suffix „-2.2“ is used.
>
> Looks like QtApplication does
Am 25.01.2016 um 01:37 schrieb Uwe Stöhr :
>
> Am 24.01.2016 um 23:29 schrieb Guillaume Munch:
>
>> Here are the patches as a single diff. Can you please confirm that this
>> triggers your issue?
>
> I cannot apply your patch. I get the 2 attached errors and the TortoiseGit
>
Am 24.01.2016 um 03:32 schrieb Scott Kostyshak:
Can anyone reproduce? It would be nice to know if we need to update our
layout.
I will have a look. As the maintainer of this file my plan was to check
the examples with the latest class versions in the beta cycle nevertheless.
thanks and
Scott Kostyshak wrote:
> Do I understand correctly that this issue is no longer a beta blocker or
> is there still something that needs to be done here before beta?
The original reason why I viewed it as beta blocker (general user or sytem
directory problems) turned out to be wrong.
I would
Am 24.01.2016 um 18:17 schrieb Georg Baum :
>
> Scott Kostyshak wrote:
>
>> Do I understand correctly that this issue is no longer a beta blocker or
>> is there still something that needs to be done here before beta?
>
> The original reason why I viewed it as
On 01/24/2016 07:04 AM, Georg Baum wrote:
> Uwe Stöhr wrote:
>
>> After the recent boost update in 2.1.x branch I get now many of these
>> warnings:
>>
>> GraphicsCache.cpp
>> CL : warning : Boost.Signals is no longer being maintained and is now
>> deprecated. Please switch to Boost.Signals2. To
Am 19.01.2016 um 02:34 schrieb Uwe Stöhr:
Ping!
While updating the UserGuide I noticed a new preferences setting under
Outputs->General
"DVI-PS Options"
What feature of LyX is using this and where can I find a list of
possible options?
This new feature should be added to
On 01/24/2016 08:55 AM, Georg Baum wrote:
> The date inset does currently not produce any output. This is a regression
> of http://www.lyx.org/trac/changeset/f09a9fe2/lyxgit. Before that change it
> did work only by accident: compare_timestamps() is called with two temp
> files which both have
Am 22.01.2016 um 02:07 schrieb Uwe Stöhr:
I tried this but cannot see a problem in LyX 2.1.4 compared to LyX 2.2
with your patches applied.
I still had your patch applied and this caused a crash:
http://www.lyx.org/trac/ticket/9944
Can you please have a look and provide a new patch? (if
On Sun, Jan 24, 2016 at 03:36:09PM +0100, Georg Baum wrote:
> OK, but I don't think it is too important to know whether the old compiler
> did handle that. There is a FIXME near the imbue call anyway, since we do
> not know whether it is standard conforming what we do there.
>
> I'll have a
Am 22.01.2016 um 20:30 schrieb Guillaume Munch:
Can you please tell me what issue you are referring to precisely in
#1497 then?
Open the testfile I attached to
http://www.lyx.org/trac/ticket/1497
Compare the appearance in lyx with that in the PDF output:
- for multline (first formula in the
Am 24.01.2016 um 19:08 schrieb Georg Baum :
>
> Stephan Witt wrote:
>
>> Am 24.01.2016 um 18:17 schrieb Georg Baum
>> :
>>>
>>> Stephan, does the algo2e.tex test succeed if you apply the attached patch
>>> on a clean tree?
>>
>>
Stephan Witt wrote:
> Am 24.01.2016 um 18:17 schrieb Georg Baum
> :
>>
>> Stephan, does the algo2e.tex test succeed if you apply the attached patch
>> on a clean tree?
>
> No, it doesn’t work. With the patch I get:
It turned out that we used two different names
On 2016-01-24, Richard Heck wrote:
> On 01/23/2016 05:47 PM, Kornel Benko wrote:
>> Am Samstag, 23. Januar 2016 um 21:22:02, schrieb Kornel Benko
>>
>>> Latest version does not compile.
>>> All latex variants (pdflatex, lualatex, xelatex) fail.
>> Apparently lyx does not handle
On Sun, Jan 24, 2016 at 12:59:34PM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > From what I understand, the renaming was done to avoid confusion from
> > overloading (see the documentation for the signal in Qt 4.8 or Qt 5). I
> > think this is related to this Qt bug [6]. In essence,
On Sun, Jan 24, 2016 at 06:17:18PM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > Do I understand correctly that this issue is no longer a beta blocker or
> > is there still something that needs to be done here before beta?
>
> The original reason why I viewed it as beta blocker
On Sun, Jan 24, 2016 at 06:09:02PM +0100, Uwe Stöhr wrote:
> Am 24.01.2016 um 03:32 schrieb Scott Kostyshak:
>
> >Can anyone reproduce? It would be nice to know if we need to update our
> >layout.
>
> I will have a look. As the maintainer of this file my plan was to check the
> examples with the
Am Sonntag, 24. Januar 2016 um 22:19:25, schrieb Georg Baum
> Kornel Benko wrote:
>
> > BTW, the file was intently not mentioned in suspiciousTests. I hoped for
> > an easy fix soon, but obviously it is not so easy.
>
> See http://www.lyx.org/trac/ticket/4595
Le 24/01/2016 11:15, Uwe Stöhr a écrit :
Am 22.01.2016 um 02:07 schrieb Uwe Stöhr:
I tried this but cannot see a problem in LyX 2.1.4 compared to LyX 2.2
with your patches applied.
I still had your patch applied and this caused a crash:
http://www.lyx.org/trac/ticket/9944
Can you please
After I used my PDF viewer correctly I could finally reproduce the footnote
regression introduced by http://www.lyx.org/trac/changeset/0bf8b8a1/lyxgit.
Unfortunately there are no other options to fix this regression than
reverting 0bf8b8a1 or introducing preamble code before loading footmisc
Kornel Benko wrote:
> BTW, the file was intently not mentioned in suspiciousTests. I hoped for
> an easy fix soon, but obviously it is not so easy.
See http://www.lyx.org/trac/ticket/4595 for label insets, there are similar
bugs for other insets that expect LaTeX code. Unfortunately this
On Fri, Jan 22, 2016 at 06:36:03PM -0500, Guillaume Munch wrote:
> Le 21/01/2016 05:19, Enrico Forestieri a écrit :
> >
> >Please, find attached an updated patch that moves the check for
> >separators on mouse clicks to a centralized place (also accounting
> >for shift-clicks and other modifiers).
Am Sonntag, 24. Januar 2016 um 21:07:03, schrieb Günter Milde
> +# The "longest label" marker in a labeling must be valid LaTeX (just like
> ERT).
> +# What should we do:
> +# - document this,
> +# - escape special characters,
> +# - convert to LaTeXString,
> +# or just report
Uwe Stöhr wrote:
> While updating the UserGuide I noticed a new preferences setting under
> Outputs->General
>
> "DVI-PS Options"
>
> What feature of LyX is using this and where can I find a list of
> possible options?
These are options passed to dvips in some cases (see
On Sun, Jan 24, 2016 at 10:41:39PM +0100, Enrico Forestieri wrote:
> On Fri, Jan 22, 2016 at 06:36:03PM -0500, Guillaume Munch wrote:
> >
> > Maybe we can go with the improvements you already made for beta, and commit
> > this particular patch to master after release.
>
> Fair enough. Please find
Le 24/01/2016 12:04, Uwe Stöhr a écrit :
Am 22.01.2016 um 20:30 schrieb Guillaume Munch:
Can you please tell me what issue you are referring to precisely in
#1497 then?
Open the testfile I attached to
http://www.lyx.org/trac/ticket/1497
Compare the appearance in lyx with that in the PDF
44 matches
Mail list logo