Am 17.03.2014 23:46, schrieb Uwe Stöhr:
@ everybody: Can you please review
http://wiki.lyx.org/LyX/NewInLyX21
if all new features are listed so that I know what to document.
These are not blocking issues, but thanks for reminding people.
I of course know that this is no blocker but why does
On Fri, Mar 21, 2014 at 1:28 AM, Uwe Stöhr wrote:
> Am 18.03.2014 08:53, schrieb Vincent van Ravesteijn:
>
>
>> LyX 2.1 is far past its due data, so, yes, I want to release as soon
>> as possible.
>
>
> OK. The installer is ready as I said. I can ship an older version of
> ImageMagick without the
Am 18.03.2014 08:53, schrieb Vincent van Ravesteijn:
LyX 2.1 is far past its due data, so, yes, I want to release as soon
as possible.
OK. The installer is ready as I said. I can ship an older version of ImageMagick without the bug and
hope I get a fixed verson before the final release.
Ho
Am 18.03.2014 09:02, schrieb Vincent van Ravesteijn:
See its changelog in master - I completely changed the handling of Perl, its
interaction with MikTeX and fixed some bugs. I can also not test all the
different languages (dictionaries and thesaurus) due to lack of time.
Btw. to where can I upl
On Tue, Mar 18, 2014 at 09:16:29PM +0100, Georg Baum wrote:
> Enrico Forestieri wrote:
>
> > On Thu, Mar 13, 2014 at 10:43:36PM +0100, Georg Baum wrote:
> >
> >> Vincent van Ravesteijn wrote:
> >>
> >> > I did some debugging. The problem lies in the use of
> >> > QProcess::startDetached. If you
Enrico Forestieri wrote:
> On Thu, Mar 13, 2014 at 10:43:36PM +0100, Georg Baum wrote:
>
>> Vincent van Ravesteijn wrote:
>>
>> > I did some debugging. The problem lies in the use of
>> > QProcess::startDetached. If you call this function with a the "cmd"
>> > prefix, you will inevitably get a c
On Tue, Mar 18, 2014 at 3:53 AM, Vincent van Ravesteijn wrote:
> On Mon, Mar 17, 2014 at 11:29 PM, Uwe Stöhr wrote:
>> Am 13.03.2014 09:08, schrieb Vincent van Ravesteijn:
>>
>>
> - the last few Imagemagick have a bug in the handling of PDF files and I
> don't want to release an older IM
On Mon, Mar 17, 2014 at 11:46 PM, Uwe Stöhr wrote:
> Am 13.03.2014 09:18, schrieb Vincent van Ravesteijn:
>
>
>> ... which means that in the ideal future, if you want a new feature
>> accepted into LyX, you should provide documentation about it and have
>> it well tested
>
>
> I am a bit annoy
On Mon, Mar 17, 2014 at 11:29 PM, Uwe Stöhr wrote:
> Am 13.03.2014 09:08, schrieb Vincent van Ravesteijn:
>
>
- the last few Imagemagick have a bug in the handling of PDF files and I
don't want to release an older IM version because of security bugs they
fixed (I already contacted t
Am 13.03.2014 09:18, schrieb Vincent van Ravesteijn:
... which means that in the ideal future, if you want a new feature
accepted into LyX, you should provide documentation about it and have
it well tested
I am a bit annoyed about this. I only want a working release. I develop LyX for 10 y
Am 13.03.2014 09:11, schrieb Vincent van Ravesteijn:
The bug is only in LyX 2.1git and yes, it is super annoying.
I created now a bug:
http://www.lyx.org/trac/ticket/9035
I agree it is super annoying, but at the same time I agree with Georg:
the issue didn't really make it to lyx-devel or trac
Am 13.03.2014 09:08, schrieb Vincent van Ravesteijn:
- the last few Imagemagick have a bug in the handling of PDF files and I
don't want to release an older IM version because of security bugs they
fixed (I already contacted the IM developers).
What is the bug ?
PDFs with a bounding or media
On Thu, Mar 13, 2014 at 10:43:36PM +0100, Georg Baum wrote:
> Vincent van Ravesteijn wrote:
>
> > I did some debugging. The problem lies in the use of
> > QProcess::startDetached. If you call this function with a the "cmd"
> > prefix, you will inevitably get a command window.
>
> So in some sens
On Thu, Mar 13, 2014 at 10:29:29PM +0100, Vincent van Ravesteijn wrote:
>
> I did some debugging. The problem lies in the use of
> QProcess::startDetached. If you call this function with a the "cmd"
> prefix, you will inevitably get a command window.
That's the only way to use batch files on Wind
On 13 Mar 2014 at 21:48:16 , Georg Baum (georg.b...@post.rwth-aachen.de) wrote:
Benjamin Piwowarski wrote:
> I have another question (this was what I was trying to fix also):
> - why the python2() code in os.cpp (line 41) does not prevent the wrong
> python to be selected.
I think this is
On 13 Mar 2014 at 21:48:16 , Georg Baum (georg.b...@post.rwth-aachen.de) wrote:
Benjamin Piwowarski wrote:
> I have another question (this was what I was trying to fix also):
> - why the python2() code in os.cpp (line 41) does not prevent the wrong
> python to be selected.
I think this is the
On 14/03/2014 10:20 a.m., Georg Baum wrote:
aparsloe wrote:
For instance, under the format LyX in the Viewer slots I have put Custom
and notepad++ (a Windows text editor). Clicking on the View other
formats > View LyX button displays the LyX file in its native format in
the text editor but wit
On Thu, Mar 13, 2014 at 5:29 PM, Vincent van Ravesteijn wrote:
> I did some debugging. The problem lies in the use of
> QProcess::startDetached. If you call this function with a the "cmd" prefix,
> you will inevitably get a command window.
>
> Omitting the "cmd" could be a solution. Does it have
Vincent van Ravesteijn wrote:
> I did some debugging. The problem lies in the use of
> QProcess::startDetached. If you call this function with a the "cmd"
> prefix, you will inevitably get a command window.
So in some sense it does what it is told to do;-)
> Omitting the "cmd" could be a solutio
Georg Baum schreef op 13-3-2014 22:20:
aparsloe wrote:
For instance, under the format LyX in the Viewer slots I have put Custom
and notepad++ (a Windows text editor). Clicking on the View other
formats > View LyX button displays the LyX file in its native format in
the text editor but with the
aparsloe wrote:
> For instance, under the format LyX in the Viewer slots I have put Custom
> and notepad++ (a Windows text editor). Clicking on the View other
> formats > View LyX button displays the LyX file in its native format in
> the text editor but with the command window also showing. Howev
Benjamin Piwowarski wrote:
> I have another question (this was what I was trying to fix also):
> - why the python2() code in os.cpp (line 41) does not prevent the wrong
> python to be selected.
I think this is the most important question. After all, we do not have
control over PATH, and in many
>
>
> > However, it still doesn't work for the OP of #8925. 5 days ago, he
> > couldn't find a "patched" dmg. I don't know what is patched, but are
> > you still sure the new package doesn't work on his machine ?
>
> The OP had python3 from macports installed.
>
> The path_prefix of LyX on Mac sets
Am 13.03.2014 um 10:41 schrieb Vincent van Ravesteijn :
>>> Is it correct that the MacOS problems are now all solved except for some
>>> cosmetic issues ?
>>
>> I don't know. Currently it's not clear. The package I've build is usable on
>> Benjamin's 10.9
>> and it's not usable on the machine
>> Is it correct that the MacOS problems are now all solved except for some
>> cosmetic issues ?
>
> I don't know. Currently it's not clear. The package I've build is usable on
> Benjamin's 10.9
> and it's not usable on the machine of the OP of ticket 8925. That's very
> strange.
[...]
> We ha
On Mon, Mar 10, 2014 at 11:10 PM, Uwe Stöhr wrote:
> Am 10.03.2014 21:47, schrieb Vincent van Ravesteijn:
>
>
>> I'm now confused on the status on Windows. For me it looks rather ok.
>
>
> I just finished the Win installer for LyX 2.1. But LyX itself cannot be
> released as it is because:
>
> - th
On Thu, Mar 13, 2014 at 1:01 AM, Uwe Stöhr wrote:
> Am 12.03.2014 22:01, schrieb Georg Baum:
>
>> Uwe Stöhr wrote:
>
>
>> I asked already for a list of features with missing documentation, but got
>> no reply, so here is the question again: Which features are not yet
>> documented?
>
>
> the red o
>
>> Besides this I have 2 further issues open:
>> - pdfcrop, that we use for cropped PDF output does not work on Windows
>> 64bit (I sent a fix to the maintainer)
>
Using pdfcrop is a new feature and this will not be blocking the release.
>
> This is not a LyX bug, so we should not wait for it.
On 03/12/2014 08:01 PM, Uwe Stöhr wrote:
Am 12.03.2014 22:01, schrieb Georg Baum:
Uwe Stöhr wrote:
I asked already for a list of features with missing documentation,
but got
no reply, so here is the question again: Which features are not yet
documented?
the red ones in
http://wiki.lyx.org/
Am 12.03.2014 22:01, schrieb Georg Baum:
Uwe Stöhr wrote:
I asked already for a list of features with missing documentation, but got
no reply, so here is the question again: Which features are not yet
documented?
the red ones in
http://wiki.lyx.org/LyX/NewInLyX21
- Windows-specific: when y
On 13/03/2014 10:01 a.m., Georg Baum wrote:
Uwe Stöhr wrote:
- Windows-specific: when you view a PDF a console window pops up and does
not disappear. This a super annoying regression to LyX 2.0
It can't be super annoying. This is known for several months, and there is
no bug entry targeted to 2.
Uwe Stöhr wrote:
> I just finished the Win installer for LyX 2.1. But LyX itself cannot be
> released as it is because:
>
> - the documentation is not yet fully updated and I recently found bugs for
> every new feature I described in the docs.
I you aim for a bug free release then it will never
Am 10.03.2014 um 21:47 schrieb Vincent van Ravesteijn :
> Georg Baum schreef op 3-3-2014 22:28:
>> Jürgen Spitzmüller wrote:
>>
>>> The status now is that we can release 2.1 as soon as the Mac Cocoa
>>> problems listed in #8959 are resolved:
>>>
>>> I think we should aim at a release in March. D
Am 10.03.2014 21:47, schrieb Vincent van Ravesteijn:
I'm now confused on the status on Windows. For me it looks rather ok.
I just finished the Win installer for LyX 2.1. But LyX itself cannot be
released as it is because:
- the documentation is not yet fully updated and I recently found bugs
Am 10.03.2014 20:52, schrieb Vincent van Ravesteijn:
I don't understand. We package Python with LyX and we install Python in a subdir of
the "C:\Program
Files (x86)\LyX". Then we add this directory to the path ourselves. How come
that we suddenly use
Python3.0 ?
Yes, it seems that the bug re
Vincent van Ravesteijn wrote:
> I agree with you. IMO, the critical bugs left in the bug tracker are
> difficult to fix, and have been around for a long time.
>
> Is it correct that the MacOS problems are now all solved except for some
> cosmetic issues ? Stefan, are you ok with release a version
Vincent van Ravesteijn wrote:
> I don't understand. We package Python with LyX and we install Python in
> a subdir of the "C:\Program Files (x86)\LyX". Then we add this directory
> to the path ourselves. How come that we suddenly use Python3.0 ?
Probably because the windows system path takes prec
On 03/10/2014 04:47 PM, Vincent van Ravesteijn wrote:
Georg Baum schreef op 3-3-2014 22:28:
Jürgen Spitzmüller wrote:
The status now is that we can release 2.1 as soon as the Mac Cocoa
problems listed in #8959 are resolved:
I think we should aim at a release in March. Do a RC in mid March, an
Georg Baum schreef op 3-3-2014 22:28:
Jürgen Spitzmüller wrote:
The status now is that we can release 2.1 as soon as the Mac Cocoa
problems listed in #8959 are resolved:
I think we should aim at a release in March. Do a RC in mid March, and
then release two weeks later, if no urgent problems a
Georg Baum schreef op 21-2-2014 21:55:
Hi,
fortunately there was a lot of activity in trac during the last days/weeks,
so although it might look on the list that the upcoming release is not being
worked on this is not true. However, I believe it would be good to get a
clear picture of what is mi
Uwe Stöhr schreef op 4-3-2014 0:20:
Am 03.03.2014 22:28, schrieb Georg Baum:
Thanks for the update, Jürgen, I agree. Uwe, are you finished with the
documentation until then?
No. There is still too much to do and the translators also need time.
I will see what I can do this week.
Is it really
Am 05.03.2014 um 00:25 schrieb Stephan Witt :
> Am 04.03.2014 um 23:45 schrieb Benjamin Piwowarski
> :
>
>> For some unknown reason, on OS X 10.9, I can reproduce the Omega bug with
>> Stephan's QT4/cocoa build but not with the QT5/cocoa one…
>
> So, they've changed the QTextEngine. No magic.
Am 04.03.2014 um 23:45 schrieb Benjamin Piwowarski
:
> For some unknown reason, on OS X 10.9, I can reproduce the Omega bug with
> Stephan's QT4/cocoa build but not with the QT5/cocoa one…
So, they've changed the QTextEngine. No magic. That's one of the pros to use
Qt-5.
Stephan
> On 03 Mar
For some unknown reason, on OS X 10.9, I can reproduce the Omega bug with
Stephan's QT4/cocoa build but not with the QT5/cocoa one...
benjamin
On 03 Mar 2014, at 21:48 , Georg Baum wrote:
> Jürgen Spitzmüller wrote:
>
>> Benjamin Piwowarski wrote:
>>> with the latest build that Stephan sent
OK, I updated the documentation - there are now two patches (one to update the
code for a better version - I hope it can make it for 2.1, one for the
documentation) attached to issue #8185.
http://lyx.lyx.org/trac/ticket/8185
Benjamin
On 03 Mar 2014, at 16:12 , Richard Heck wrote:
> On 03/03
Uwe Stöhr wrote:
> Am 03.03.2014 22:28, schrieb Georg Baum:
>
>> Thanks for the update, Jürgen, I agree. Uwe, are you finished with the
>> documentation until then?
>
> No. There is still too much to do and the translators also need time. I
> will see what I can do this week.
What is missing? I
04/03/2014 00:20, Uwe Stöhr:
No. There is still too much to do and the translators also need time. I
will see what I can do this week.
Is it really that pressing? I mean I will for sure find further issues
while updating the docs and I think we should take the time to fix as
many bugs as possible
Am 04.03.2014 00:46, schrieb Richard Heck:
As far as I know, nothing has been done about making the code safe for python
3.x. But it could be
done, and if it needs doing you should open a blocker bug, please.
done:
http://www.lyx.org/trac/ticket/9006
regards Uwe
On 03/03/2014 06:20 PM, Uwe Stöhr wrote:
Am 03.03.2014 22:28, schrieb Georg Baum:
Thanks for the update, Jürgen, I agree. Uwe, are you finished with the
documentation until then?
No. There is still too much to do and the translators also need time.
I will see what I can do this week.
Is it r
Am 03.03.2014 22:28, schrieb Georg Baum:
Thanks for the update, Jürgen, I agree. Uwe, are you finished with the
documentation until then?
No. There is still too much to do and the translators also need time. I will see what I can do this
week.
Is it really that pressing? I mean I will for sur
Jürgen Spitzmüller wrote:
> The status now is that we can release 2.1 as soon as the Mac Cocoa
> problems listed in #8959 are resolved:
>
> I think we should aim at a release in March. Do a RC in mid March, and
> then release two weeks later, if no urgent problems are reported.
Thanks for the up
Richard Heck wrote:
> On 03/03/2014 04:19 AM, Benjamin Piwowarski wrote:
>> Regarding OS X, there is a new functionality - applescript support -
>> which is not documented at all. As I submitted the patch, I could also
>> modify the documentation but where should I put this?
>
> I would add it to
Jürgen Spitzmüller wrote:
> Benjamin Piwowarski wrote:
>> with the latest build that Stephan sent me (qt4+cocoa), on OS X 10.9,
>>
>> - glyphs bugs are still there (7954 and 8945) - I have no idea of the
>> difficulty of solving those issues,
>
> I suggest you first check whether the problem is
On 03/03/2014 03:56 AM, Jürgen Spitzmüller wrote:
- I don't understand bug 8942 (what is the "menu bar options list"?)
I asked the reporter.
This was the bug that 2.0.7.1 fixed.
Richard
On 03/03/2014 04:19 AM, Benjamin Piwowarski wrote:
Regarding OS X, there is a new functionality - applescript support - which is
not documented at all. As I submitted the patch, I could also modify the
documentation but where should I put this?
I would add it to the Additional Features manual
Regarding OS X, there is a new functionality - applescript support - which is
not documented at all. As I submitted the patch, I could also modify the
documentation but where should I put this?
benjamin
On 03 Mar 2014, at 08:41 , Jürgen Spitzmüller wrote:
> Georg Baum wrote:
>> fortunately th
Benjamin Piwowarski wrote:
> with the latest build that Stephan sent me (qt4+cocoa), on OS X 10.9,
>
> - glyphs bugs are still there (7954 and 8945) - I have no idea of the
> difficulty of solving those issues,
I suggest you first check whether the problem is with the workaround in
GuiPainter.c
Hi,
with the latest build that Stephan sent me (qt4+cocoa), on OS X 10.9,
- glyphs bugs are still there (7954 and 8945) - I have no idea of the
difficulty of solving those issues,
- bug 8925 is fixed
- I cannot reproduce crashes 7959 and 8632
- I don't understand bug 8942 (what is the "menu bar
Georg Baum wrote:
> fortunately there was a lot of activity in trac during the last days/weeks,
> so although it might look on the list that the upcoming release is not being
> worked on this is not true. However, I believe it would be good to get a
> clear picture of what is missing here on the li
Am 21.02.2014 21:55, schrieb Georg Baum:
-- Documentation:
Uwe updated it a lot. Is this finished, or are any updates still missing?
There is still some work to do.
I guess I will need at least 2 more weeks and I guess I will uncover further
bugs.
regards Uwe
Am 26.02.2014 um 22:11 schrieb Georg Baum :
> Richard Heck wrote:
>
>> On 02/26/2014 08:54 AM, Jürgen Spitzmüller wrote:
>>> 2014-02-26 14:12 GMT+01:00 Stephan Witt:
>>>
>>>I don't have a Mac OS X 10.9 retail version.
>>>
>>>
>>> Given the importance of this task and the effort you invest
Richard Heck wrote:
> On 02/26/2014 08:54 AM, Jürgen Spitzmüller wrote:
>> 2014-02-26 14:12 GMT+01:00 Stephan Witt:
>>
>> I don't have a Mac OS X 10.9 retail version.
>>
>>
>> Given the importance of this task and the effort you invest for the
>> Mac users, I'd think the LyX project could just
On 02/26/2014 08:54 AM, Jürgen Spitzmüller wrote:
2014-02-26 14:12 GMT+01:00 Stephan Witt:
I don't have a Mac OS X 10.9 retail version.
Given the importance of this task and the effort you invest for the
Mac users, I'd think the LyX project could just buy you one. At least
I would +1 tha
On Wed, Feb 26, 2014 at 2:54 PM, Jürgen Spitzmüller wrote:
> 2014-02-26 14:12 GMT+01:00 Stephan Witt:
>
>> I don't have a Mac OS X 10.9 retail version.
>
Do we have any private or public data on how much donations we are
getting? I for one would be much more inclined to ramp up my donations
if I h
Am Mittwoch, 26. Februar 2014 um 14:54:35, schrieb Jürgen Spitzmüller
> 2014-02-26 14:12 GMT+01:00 Stephan Witt:
>
> > I don't have a Mac OS X 10.9 retail version.
> >
>
> Given the importance of this task and the effort you invest for the Mac
> users, I'd think the LyX project could just buy y
2014-02-26 14:12 GMT+01:00 Stephan Witt:
> I don't have a Mac OS X 10.9 retail version.
>
Given the importance of this task and the effort you invest for the Mac
users, I'd think the LyX project could just buy you one. At least I would
+1 that.
Jürgen
Stephan
Am 26.02.2014 um 13:55 schrieb Jürgen Spitzmüller :
> Am Dienstag 25 Februar 2014, 08:28:21 schrieb Stephan Witt:
>> I don't want to update my Mac OS to 10.9 because of privacy issues.
>> Apple dropped the sync support via USB and forces the users to sync their
>> devices via iCloud. I cannot acce
Am Dienstag 25 Februar 2014, 08:28:21 schrieb Stephan Witt:
> I don't want to update my Mac OS to 10.9 because of privacy issues.
> Apple dropped the sync support via USB and forces the users to sync their
> devices via iCloud. I cannot accept this and don't know how to proceed.
Would installing 1
Am 24.02.2014 um 22:24 schrieb Georg Baum :
> Stephan Witt wrote:
>
>> I've had to learn it's not a good idea to change the Qt-Version or Mac-API
>> for a branch version. Given the fact that when 2.1.0 is released it
>> becomes a branch version I'd prefer a 2.1.0 with Cocoa. On Mac OS 10.8.6 -
>>
On 02/24/2014 04:38 PM, Georg Baum wrote:
Anyway, the updated status is:
-- Bugs: The following bugs are scheduled to be fixed for 2.1.0:
8997 partly understood, needs some more work
8973 partly understood, needs some more work
8925 no fix yet (mac-specific)
8995 problem understood, but no pat
Pavel Sanda wrote:
> Georg Baum wrote:
>> collect information about the show stoppers. What needs to be done?
>
> When strings are more or less freezed, then what used to be #7386, i.e.
> update file, perhaps collect list of new strings compared to 2.0 (should
> be small) and send gentle request
Richard Heck wrote:
> I seem to remember a discussion a few months ago in which it was
> suggested that there are enough new features already at an advanced
> stage of development to start thinking about a 2.2 release. Anyone else
> have such a memory?
I don't remember exactly, but there was defi
Stephan Witt wrote:
> I've had to learn it's not a good idea to change the Qt-Version or Mac-API
> for a branch version. Given the fact that when 2.1.0 is released it
> becomes a branch version I'd prefer a 2.1.0 with Cocoa. On Mac OS 10.8.6 -
> already one major release behind the current one 10.
On 02/23/2014 09:30 AM, Stephan Witt wrote:
The decision what Qt-framework is best to use depends on the expected
life cycle of 2.1.0 LyX, IMHO. But, I'm not sure.
I seem to remember a discussion a few months ago in which it was
suggested that there are enough new features already at an advanc
Am 22.02.2014 um 16:14 schrieb Richard Heck :
> On 02/21/2014 03:55 PM, Georg Baum wrote:
>> Hi,
>>
>> fortunately there was a lot of activity in trac during the last days/weeks,
>> so although it might look on the list that the upcoming release is not being
>> worked on this is not true. Howeve
Georg Baum wrote:
> collect information about the show stoppers. What needs to be done?
When strings are more or less freezed, then what used to be #7386, i.e. update
file, perhaps collect list of new strings compared to 2.0 (should be small) and
send gentle request to translators to carefully rev
Am Freitag 21 Februar 2014, 21:55:22 schrieb Georg Baum:
> 8657 partly understood, needs some more work
We have a patch that works for the people hit by that bug on Linux. This is
rather straightforward and can be committed. However, the patch is not enough
on Windows. Obviously. It's just a mat
On 02/21/2014 03:55 PM, Georg Baum wrote:
Hi,
fortunately there was a lot of activity in trac during the last days/weeks,
so although it might look on the list that the upcoming release is not being
worked on this is not true. However, I believe it would be good to get a
clear picture of what is
On 02/22/2014 03:27 AM, Georg Baum wrote:
Scott Kostyshak wrote:
Do we have a way on trac to specify that a bug has more than one
milestone? For example, I'm wondering which of the bugs that currently
have milestone 2.0.8 also have an implicit target for 2.1.0.
Good question. I don't think tha
Scott Kostyshak wrote:
> Do we have a way on trac to specify that a bug has more than one
> milestone? For example, I'm wondering which of the bugs that currently
> have milestone 2.0.8 also have an implicit target for 2.1.0.
Good question. I don't think that this is possible. I also believe that
On Fri, Feb 21, 2014 at 3:55 PM, Georg Baum
wrote:
> Hi,
>
> fortunately there was a lot of activity in trac during the last days/weeks,
> so although it might look on the list that the upcoming release is not being
> worked on this is not true. However, I believe it would be good to get a
> clear
Hi,
fortunately there was a lot of activity in trac during the last days/weeks,
so although it might look on the list that the upcoming release is not being
worked on this is not true. However, I believe it would be good to get a
clear picture of what is missing here on the list, therefore I'd
82 matches
Mail list logo
