On Fri, May 20, 2016 at 07:36:20AM +0200, Kornel Benko wrote:
> Am Freitag, 20. Mai 2016 um 01:20:58, schrieb Scott Kostyshak
>
> > On Thu, May 19, 2016 at 09:02:10PM +0200, Stephan Witt wrote:
> > > Am 18.05.2016 um 01:58 schrieb Guillaume Munch :
> > > >
> > > > Le 17/05/2016 19:31, Scott Kost
On Thu, May 19, 2016 at 04:15:06PM +0100, Guillaume Munch wrote:
> Le 18/05/2016 03:27, Scott Kostyshak a écrit :
> > On Wed, May 18, 2016 at 12:58:51AM +0100, Guillaume Munch wrote:
> > > Le 17/05/2016 19:31, Scott Kostyshak a écrit :
> > > >
> > > > I tried your patch. I have the same problems a
Am Freitag, 20. Mai 2016 um 01:20:58, schrieb Scott Kostyshak
> On Thu, May 19, 2016 at 09:02:10PM +0200, Stephan Witt wrote:
> > Am 18.05.2016 um 01:58 schrieb Guillaume Munch :
> > >
> > > Le 17/05/2016 19:31, Scott Kostyshak a écrit :
> > >>
> > >> I tried your patch. I have the same problems
On Thu, May 19, 2016 at 09:02:10PM +0200, Stephan Witt wrote:
> Am 18.05.2016 um 01:58 schrieb Guillaume Munch :
> >
> > Le 17/05/2016 19:31, Scott Kostyshak a écrit :
> >>
> >> I tried your patch. I have the same problems as with Stephan's patch
> >> (also reported by Kornel). For example, none
Am 18.05.2016 um 01:58 schrieb Guillaume Munch :
>
> Le 17/05/2016 19:31, Scott Kostyshak a écrit :
>>
>> I tried your patch. I have the same problems as with Stephan's patch
>> (also reported by Kornel). For example, none of alt+f, alt+f, alt+d,
>> alt+s work for me.
>>
>
> How about removing
Le 18/05/2016 03:27, Scott Kostyshak a écrit :
On Wed, May 18, 2016 at 12:58:51AM +0100, Guillaume Munch wrote:
Le 17/05/2016 19:31, Scott Kostyshak a écrit :
I tried your patch. I have the same problems as with Stephan's patch
(also reported by Kornel). For example, none of alt+f, alt+f, alt+
Am 18.05.2016 um 04:27 schrieb Scott Kostyshak:
Tested all key combinations I can think of and the patch seems to work
perfectly for me. Stephan, Uwe, can you please test on Mac and Win?
I tested this now as well and it works perfectly. So +1 from me to go to
master.
regards Uwe
On 17.05.16 08:37, Scott Kostyshak wrote:
> On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
>>
>> 2. There is a crash that seems mostly reproducible on OS X. Although it is
>> only
>> on OS X and only in a particular case, I consider this bug important because
>> it
>> is a crash
Am 17.05.2016 um 20:31 schrieb Scott Kostyshak :
>
>> On Tue, May 17, 2016 at 02:17:25PM -0400, Scott Kostyshak wrote:
>>> On Tue, May 17, 2016 at 07:08:17PM +0100, Guillaume Munch wrote:
>>> Le 17/05/2016 07:34, Scott Kostyshak a écrit :
On Sat, May 14, 2016 at 01:18:47AM -0400, Scott Kostys
On Wed, May 18, 2016 at 12:58:51AM +0100, Guillaume Munch wrote:
> Le 17/05/2016 19:31, Scott Kostyshak a écrit :
> >
> > I tried your patch. I have the same problems as with Stephan's patch
> > (also reported by Kornel). For example, none of alt+f, alt+f, alt+d,
> > alt+s work for me.
> >
>
> H
Le 17/05/2016 19:31, Scott Kostyshak a écrit :
I tried your patch. I have the same problems as with Stephan's patch
(also reported by Kornel). For example, none of alt+f, alt+f, alt+d,
alt+s work for me.
How about removing what makes no sense?
>From 334bb3ef61273cc2c3f348dbf27169623633231d M
On Tue, May 17, 2016 at 02:17:25PM -0400, Scott Kostyshak wrote:
> On Tue, May 17, 2016 at 07:08:17PM +0100, Guillaume Munch wrote:
> > Le 17/05/2016 07:34, Scott Kostyshak a écrit :
> > > On Sat, May 14, 2016 at 01:18:47AM -0400, Scott Kostyshak wrote:
> > > > On Tue, May 10, 2016 at 03:04:13AM -0
On Tue, May 17, 2016 at 07:08:17PM +0100, Guillaume Munch wrote:
> Le 17/05/2016 07:34, Scott Kostyshak a écrit :
> > On Sat, May 14, 2016 at 01:18:47AM -0400, Scott Kostyshak wrote:
> > > On Tue, May 10, 2016 at 03:04:13AM -0400, Scott Kostyshak wrote:
> > > > On Wed, May 04, 2016 at 04:39:54PM -0
Le 17/05/2016 07:34, Scott Kostyshak a écrit :
On Sat, May 14, 2016 at 01:18:47AM -0400, Scott Kostyshak wrote:
On Tue, May 10, 2016 at 03:04:13AM -0400, Scott Kostyshak wrote:
On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
Dear all,
As new issues have popping up (and will w
On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
> Dear all,
>
> As new issues have popping up (and will without doubt continue to keep popping
> up), I want to give an update of how close I think we are to the next step in
> the release process. The two main issues in my mind are:
On Sat, May 14, 2016 at 01:18:47AM -0400, Scott Kostyshak wrote:
> On Tue, May 10, 2016 at 03:04:13AM -0400, Scott Kostyshak wrote:
> > On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
> > > Dear all,
> > >
> > > As new issues have popping up (and will without doubt continue to kee
On Sat, May 14, 2016 at 03:38:30PM +0200, Jean-Marc Lasgouttes wrote:
> Le 10/05/16 à 09:04, Scott Kostyshak a écrit :
> > On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
> > > Dear all,
> > >
> > > As new issues have popping up (and will without doubt continue to keep
> > > popp
Le 10/05/16 à 09:04, Scott Kostyshak a écrit :
On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
Dear all,
As new issues have popping up (and will without doubt continue to keep popping
up), I want to give an update of how close I think we are to the next step in
the release proc
On Tue, May 10, 2016 at 03:04:13AM -0400, Scott Kostyshak wrote:
> On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
> > Dear all,
> >
> > As new issues have popping up (and will without doubt continue to keep
> > popping
> > up), I want to give an update of how close I think we ar
On Wed, May 04, 2016 at 04:39:54PM -0400, Scott Kostyshak wrote:
> Dear all,
>
> As new issues have popping up (and will without doubt continue to keep popping
> up), I want to give an update of how close I think we are to the next step in
> the release process. The two main issues in my mind are:
On Tue, May 10, 2016 at 07:09:04AM +0200, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > On Sat, May 07, 2016 at 11:16:50AM +0200, Georg Baum wrote:
> >>
> >> Done. Now I would recommend to merge all .po file contributions that are
> >> not based on the latest remerge by
> >>
> >> python devel
Scott Kostyshak wrote:
> On Sat, May 07, 2016 at 11:16:50AM +0200, Georg Baum wrote:
>>
>> Done. Now I would recommend to merge all .po file contributions that are
>> not based on the latest remerge by
>>
>> python development/tools/mergepo.py -o -l xx -t po /tmp/
>>
>> wher xx is the language
On Mon, May 09, 2016 at 07:58:53PM -0400, Ian Wilder wrote:
> +1 for not branching. If it's just print statements, the use functions to be
> compatible with Python 3.
> A lot of Python 3 functionality has been backported to 2.x
Thanks for the interest, Josh and Ian. Note that we have a ticket wher
On Sun, May 08, 2016 at 10:33:23PM +0100, Guillaume Munch wrote:
> Le 06/05/2016 21:09, Scott Kostyshak a écrit :
> > On Wed, May 04, 2016 at 11:19:56PM +0100, Guillaume Munch wrote:
> > > Le 04/05/2016 21:39, Scott Kostyshak a écrit :
> > > > What am I missing?
> > > >
> > >
> > > #10068: Files
On Sat, May 07, 2016 at 11:16:50AM +0200, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > On Thu, May 05, 2016 at 02:32:46PM +0200, Georg Baum wrote:
> >>
> >> I would like to merge all changes to mergepo.py from 2.3-staging to
> >> master (see attached). The users won't see this script at all,
+1 for not branching. If it's just print statements, the use functions
to be compatible with Python 3.
A lot of Python 3 functionality has been backported to 2.x
On 2016-05-09 00:35:57 +, Josh Hieronymus said:
Looking over the code, it looks like much of the problem is that Python
2 has pr
Looking over the code, it looks like much of the problem is that Python 2
has print as a statement, while Python 3 has print as a function. Since
we're supporting only Python 2.7 from the 2.x series, we could add an
import statement to use print as a function in order to avoid checking the
version
On 2016-05-04 20:39:54 +, Scott Kostyshak said:
3. A Python3 compatibility issue at [5]. I don't know whether the best
short-run approach is to ensure that we use Python2 to call the script or to
fix the script to be compatible with Python3. I CC'ed José to see if he has
some wisdom to shar
Le 06/05/2016 21:09, Scott Kostyshak a écrit :
On Wed, May 04, 2016 at 11:19:56PM +0100, Guillaume Munch wrote:
Le 04/05/2016 21:39, Scott Kostyshak a écrit :
What am I missing?
#10068: Files distributed with lyx should not contain parbreak and
latexpar http://mid.gmane.org/nfu741$c3j$1...@g
On Sat, May 7, 2016 at 3:32 AM, Stephan Witt wrote:
>
> Sorry, I should have mentioned the name. They are named org.lyx.LyX*
>
> But I’m not sure if these are the only locations where Qt stores internal
> state.
>
> Stephan
Moving org.lyx* out of that directory does not cure the crashing proble
Scott Kostyshak wrote:
> On Thu, May 05, 2016 at 02:32:46PM +0200, Georg Baum wrote:
>>
>> I would like to merge all changes to mergepo.py from 2.3-staging to
>> master (see attached). The users won't see this script at all, but it
>> will make updating translations easier, especially since most
Am 06.05.2016 um 23:52 schrieb Joel Kulesza :
>
> On Fri, May 6, 2016 at 5:22 PM, Stephan Witt wrote:
> You may consider to remove or rename the QSettings storage. It should be in
> $HOME/Library/Preferences.
>
> This doesn't appear to be the case.
>
> 10011 jkulesza@tempest[~/Library/Preferen
On Fri, May 6, 2016 at 5:22 PM, Stephan Witt wrote:
> You may consider to remove or rename the QSettings storage. It should be
> in $HOME/Library/Preferences.
This doesn't appear to be the case.
10011 jkulesza@tempest[~/Library/Preferences]> la QS*
ls: QS*: No such file or directory
10012 jkul
> Am 06.05.2016 um 22:18 schrieb Joel Kulesza :
>
> On Fri, May 6, 2016 at 4:09 PM, Scott Kostyshak wrote:
> On Wed, May 04, 2016 at 11:19:56PM +0100, Guillaume Munch wrote:
> > Le 04/05/2016 21:39, Scott Kostyshak a écrit :
> > >
> > > 4. Insert Cross-Reference Causes Crash. See #9992. Unfortun
On Fri, May 6, 2016 at 4:09 PM, Scott Kostyshak wrote:
> On Wed, May 04, 2016 at 11:19:56PM +0100, Guillaume Munch wrote:
> > Le 04/05/2016 21:39, Scott Kostyshak a écrit :
> > >
> > > 4. Insert Cross-Reference Causes Crash. See #9992. Unfortunately, no
> > > one can reproduce except the OP, Joel
On Wed, May 04, 2016 at 11:19:56PM +0100, Guillaume Munch wrote:
> Le 04/05/2016 21:39, Scott Kostyshak a écrit :
> >
> > 4. Insert Cross-Reference Causes Crash. See #9992. Unfortunately, no
> > one can reproduce except the OP, Joel. Joel has been extremely
> > helpful in debugging and is able to
On Thu, May 05, 2016 at 02:24:56PM +0200, Georg Baum wrote:
> Guillaume Munch wrote:
>
> > Le 04/05/2016 21:39, Scott Kostyshak a écrit :
> >>
> >> 9. Disabled OK button in Doc Settings if negative value (allowed in
> >> 2.1.x). See #10095 and [3]. I posted a patch. It is just a matter of
> >> see
On Thu, May 05, 2016 at 02:32:46PM +0200, Georg Baum wrote:
> Scott,
>
> thanks for the summary. I could not follow most of these issues, so I do not
> comment.
>
> Scott Kostyshak wrote:
>
> >
> > What am I missing?
>
> I would like to merge all changes to mergepo.py from 2.3-staging to mast
Scott,
thanks for the summary. I could not follow most of these issues, so I do not
comment.
Scott Kostyshak wrote:
>
> What am I missing?
I would like to merge all changes to mergepo.py from 2.3-staging to master
(see attached). The users won't see this script at all, but it will make
upda
Guillaume Munch wrote:
> Le 04/05/2016 21:39, Scott Kostyshak a écrit :
>>
>> 9. Disabled OK button in Doc Settings if negative value (allowed in
>> 2.1.x). See #10095 and [3]. I posted a patch. It is just a matter of
>> seeing if there is enough support for it.
>>
>
> I thought there was already
Josh Hieronymus wrote:
> With respect to issue #3, what versions of Python are we looking to support?
INSTALL:
The two following programs should be available at configuration time:
o Python 2.7 must be installed. Python is used for many simple tasks
that are executed by external scripts, su
Le 04/05/2016 21:39, Scott Kostyshak a écrit :
4. Insert Cross-Reference Causes Crash. See #9992. Unfortunately, no
one can reproduce except the OP, Joel. Joel has been extremely
helpful in debugging and is able to compile LyX but only with Qt
5.5.1. Unless we make further progress in debugging,
With respect to issue #3, what versions of Python are we looking to support?
On May 4, 2016 3:40 PM, "Scott Kostyshak" wrote:
> Dear all,
>
> As new issues have popping up (and will without doubt continue to keep
> popping
> up), I want to give an update of how close I think we are to the next st
Dear all,
As new issues have popping up (and will without doubt continue to keep popping
up), I want to give an update of how close I think we are to the next step in
the release process. The two main issues in my mind are:
1. Cannot create shortcuts. This problem is present with Qt 5.6 and on al
44 matches
Mail list logo
