Am 17.12.2017 um 05:12 schrieb Scott Kostyshak :
>
> On Sat, Dec 16, 2017 at 07:04:24PM +, Scott Kostyshak wrote:
>> On Wed, Dec 13, 2017 at 02:55:33AM +, Scott Kostyshak wrote:
>>> On Tue, Dec 12, 2017 at 08:05:56AM +, Stephan Witt wrote:
Am 12.12.2017 um 02:52 schrieb Scott Kost
On Sun, Dec 17, 2017 at 12:45:30AM +, Uwe Stöhr wrote:
> El 16.12.2017 a las 22:33, Scott Kostyshak escribió:
>
> > Uwe, should I make the Changelog file? What do you prefer?
>
> Better mail him directly. He usually responds quickly.
OK sent.
Thanks,
Scott
signature.asc
Description: PGP
On Sun, Dec 17, 2017 at 12:37:08AM +, Uwe Stöhr wrote:
> El 16.12.2017 a las 20:10, Scott Kostyshak escribió:
>
> > It's fine for 2.3.0.
>
> OK, I'll put it in.
>
> > Usually what I do when changing http to https is to
> > check that the https link is indeed secure.
>
> This is what I did.
On Sun, Dec 17, 2017 at 01:36:59AM +, Uwe Stöhr wrote:
> El 17.12.2017 a las 01:37, Uwe Stöhr escribió:
>
> > El 16.12.2017 a las 20:10, Scott Kostyshak escribió:
> >
> > > It's fine for 2.3.0.
> >
> > OK, I'll put it in.
>
> OK, I rethought this. I fear special cases in lyx2lyx or tex2lyx
On Sat, Dec 16, 2017 at 07:04:24PM +, Scott Kostyshak wrote:
> On Wed, Dec 13, 2017 at 02:55:33AM +, Scott Kostyshak wrote:
> > On Tue, Dec 12, 2017 at 08:05:56AM +, Stephan Witt wrote:
> > > Am 12.12.2017 um 02:52 schrieb Scott Kostyshak :
> > > >
> > > > On Tue, Dec 12, 2017 at 12:58
On 12/16/2017 10:03 PM, Uwe Stöhr wrote:
> El 17.12.2017 a las 02:54, Richard Heck escribió:
>
>> Yes, but these are usually the result of cases where someone is
>> comparing, say, as size_t variable (a typedef for unsigned int or
>> something) with an int in a for loop, or something of that sort,
El 17.12.2017 a las 02:54, Richard Heck escribió:
Yes, but these are usually the result of cases where someone is
comparing, say, as size_t variable (a typedef for unsigned int or
something) with an int in a for loop, or something of that sort, and the
int is never going to be negative. So it's
On 12/16/2017 08:32 PM, Uwe Stöhr wrote:
> El 17.12.2017 a las 02:02, Richard Heck escribió:
>
>>> I noted that when I extend from level /W4 to /Wall I get some
>>> additional signed/unsigned mismatch errors. Should I report them as
>>> well?
>>
>> Those are usually harmless. I wouldn't worry too m
El 17.12.2017 a las 01:37, Uwe Stöhr escribió:
El 16.12.2017 a las 20:10, Scott Kostyshak escribió:
It's fine for 2.3.0.
OK, I'll put it in.
OK, I rethought this. I fear special cases in lyx2lyx or tex2lyx where I
might have missed a thing. Then they might not work correctly just
because
El 17.12.2017 a las 02:02, Richard Heck escribió:
I noted that when I extend from level /W4 to /Wall I get some
additional signed/unsigned mismatch errors. Should I report them as well?
Those are usually harmless. I wouldn't worry too much about them.
OK. Just for curiosity, why ar they harm
On 12/16/2017 07:40 PM, Uwe Stöhr wrote:
> El 16.12.2017 a las 23:45, Richard Heck escribió:
>
>> I know it's late for a format change, but what about including this in
>> 2.3.0?
>
> I am opposed to this because this would change strings. I mean the
> user can simply add \usepackage{paratype} to th
On 12/16/2017 12:09 PM, Uwe Stöhr wrote:
> El 14.12.2017 a las 02:23, Uwe Stöhr escribió:
>
>> I just polluted the bug tracker with 86 new bug reports with
>> different compiler warnings
>
> Many thanks Jean-Marc and Richard for reviewing them.
> I feared that some developers are annoyed by thi
El 16.12.2017 a las 22:33, Scott Kostyshak escribió:
Uwe, should I make the Changelog file? What do you prefer?
Better mail him directly. He usually responds quickly.
thanks and regards
Uwe
El 16.12.2017 a las 22:30, Scott Kostyshak escribió:
However, it's important to note that LyX's Python is exposed to the
whole system, so the more Python packages that we support, the more code
it is possible for users to run even outside of LyX. This could be
viewed as a danger, as discussed he
El 16.12.2017 a las 23:45, Richard Heck escribió:
I know it's late for a format change, but what about including this in
2.3.0?
I am opposed to this because this would change strings. I mean the user
can simply add \usepackage{paratype} to the preamble to use it for all
fonts. I can also cre
El 16.12.2017 a las 20:10, Scott Kostyshak escribió:
It's fine for 2.3.0.
OK, I'll put it in.
Usually what I do when changing http to https is to
check that the https link is indeed secure.
This is what I did. if it is not secure I left it with http. While doing
this I detected a lot of b
On 12/16/2017 05:47 PM, Jean-Marc Lasgouttes wrote:
> Le 16 décembre 2017 15:25:44 GMT+01:00, Richard Heck
> a écrit :
>
> On 12/16/2017 04:52 AM, Jean-Marc Lasgouttes wrote:
>> Le 16 décembre 2017 06:59:12 GMT+01:00, Richard Heck
>> a écrit :
>>
>> commit 71005d6c1079637d7127
Le 16 décembre 2017 15:25:44 GMT+01:00, Richard Heck a écrit :
>On 12/16/2017 04:52 AM, Jean-Marc Lasgouttes wrote:
>> Le 16 décembre 2017 06:59:12 GMT+01:00, Richard Heck
>> a écrit :
>>
>> commit 71005d6c1079637d7127defc372a5aa4d62092b0
>> Author: Richard Heck
>> Date: Sat Dec 16
On 12/14/2017 06:15 PM, Uwe Stöhr wrote:
> Yuriy asked if LyX could support the paratype fonts
> https://ctan.org/pkg/paratype
> to offer an outline font alternative for the computer modern fonts for
> Cyrillic.
>
> This is in my opinion a good idea and so I created the applied patch.
> This is a f
On Wed, Dec 13, 2017 at 06:46:01AM +, Jürgen Spitzmüller wrote:
> Am Montag, den 11.12.2017, 21:07 -0500 schrieb Scott Kostyshak:
> > Will Koji know that the string should be translated? I assumed that
> > he
> > just searches for text that is marked as English. Should we just
> > notify
> > hi
On Thu, Dec 14, 2017 at 01:26:48AM +, Uwe Stöhr wrote:
> In https://wiki.lyx.org/LyX/NewInLyX23
> I read about support for the Python module Pygments.
>
> I don's know what to do for the installer. If the user hasn't installed
> Python, should I deliver LyX with python containing the Pygments
On Thu, Dec 14, 2017 at 02:22:13PM +, Uwe Stöhr wrote:
> I think we should use https wherever possible:
> https://www.lyx.org/trac/ticket/10945
> Attached is a patch that does this.
> OK to go in?
>
> What about LyX 2.3, should we do this there as well or can this be done for
> 2.3.1?
It's fi
On Sat, Dec 16, 2017 at 05:06:41PM +, Uwe Stöhr wrote:
> El 16.12.2017 a las 06:27, Pavel Sanda escribió:
>
> > I was about to ask the same, please don't break portability of files
> > until 2.3 is out if possible.
>
> OK.
>
> By the way, why don't we release RC1 right now? Did I miss someth
On Wed, Dec 13, 2017 at 02:55:33AM +, Scott Kostyshak wrote:
> On Tue, Dec 12, 2017 at 08:05:56AM +, Stephan Witt wrote:
> > Am 12.12.2017 um 02:52 schrieb Scott Kostyshak :
> > >
> > > On Tue, Dec 12, 2017 at 12:58:36AM +, Uwe Stöhr wrote:
> > >> El 10.12.2017 a las 21:28, Scott Kosty
El 14.12.2017 a las 02:23, Uwe Stöhr escribió:
I just polluted the bug tracker with 86 new bug reports with different
compiler warnings
Many thanks Jean-Marc and Richard for reviewing them.
I feared that some developers are annoyed by this.
I noted that when I extend from level /W4 to /Wa
El 16.12.2017 a las 06:27, Pavel Sanda escribió:
I was about to ask the same, please don't break portability of files
until 2.3 is out if possible.
OK.
By the way, why don't we release RC1 right now? Did I miss something?
thanks and regards
Uwe
On 12/16/2017 09:59 AM, Kornel Benko wrote:
> Open with lyx-master src/tex2lyx/test/test-insets.lyx.lyx:
> => many lines like this:
> + sys.argv[4])) != 0:
> IndexError: list index out of range
> Traceback (most recent call last):
> File "/usr/local/share/lyx2.4/scripts/co
Open with lyx-master src/tex2lyx/test/test-insets.lyx.lyx:
=> many lines like this:
+ sys.argv[4])) != 0:
IndexError: list index out of range
Traceback (most recent call last):
File "/usr/local/share/lyx2.4/scripts/convertDefault.py", line 67, in
if
On 12/16/2017 04:52 AM, Jean-Marc Lasgouttes wrote:
> Le 16 décembre 2017 06:59:12 GMT+01:00, Richard Heck
> a écrit :
>
> commit 71005d6c1079637d7127defc372a5aa4d62092b0
> Author: Richard Heck
> Date: Sat Dec 16 00:59:07 2017 -0500
>
> Fix #10894 compiler warnings.
> --
On 12/16/2017 02:37 AM, Kornel Benko wrote:
> Am Samstag, 16. Dezember 2017 um 07:03:34, schrieb Pavel Sanda
>> Richard Heck wrote:
>>> commit b684ec39eaaf7d5b0270bf8109b8e281fa8c5d9f
>>> Author: Richard Heck
>>> Date: Fri Dec 15 23:50:23 2017 -0500
>>>
>>> Fix #10863 compiler warnings.
>>>
Le 16 décembre 2017 06:59:12 GMT+01:00, Richard Heck a écrit :
>commit 71005d6c1079637d7127defc372a5aa4d62092b0
>Author: Richard Heck
>Date: Sat Dec 16 00:59:07 2017 -0500
>
>Fix #10894 compiler warnings.
>---
> src/insets/InsetCitation.cpp |4 ++--
> 1 files changed, 2 insertions(+), 2
31 matches
Mail list logo
