Am 01.09.2022 um 22:00 schrieb Stephan Witt :
>
> Am 01.09.2022 um 19:40 schrieb Christopher Menzel :
>>
>> LyX folk:
>>
>> I’ve successfully compiled LyX from sources under Linux but my attempts to
>> do so under MacOS for my M1 Macs (since I don’t want to use Rosetta 2). I
>> installed QT5 u
Am 01.09.2022 um 19:40 schrieb Christopher Menzel :
>
> LyX folk:
>
> I’ve successfully compiled LyX from sources under Linux but my attempts to do
> so under MacOS for my M1 Macs (since I don’t want to use Rosetta 2). I
> installed QT5 using homebrew and I’m using what seem to me to be the rig
LyX folk:
I’ve successfully compiled LyX from sources under Linux but my attempts to do
so under MacOS for my M1 Macs (since I don’t want to use Rosetta 2). I
installed QT5 using homebrew and I’m using what seem to me to be the right
flags for the configure script, viz.,
% ./configure --enab
I really appreciate your help! LyX has become a very important tool for me. If
something goes wrong, it is a nightmare ;-)
Chris
> Am 09.12.2021 um 20:42 schrieb Jean-Marc Lasgouttes :
>
> Le 09/12/2021 à 19:53, Christoph Schmitz a écrit :
>> Jean-Marc,
>> Fantastic! Problem solved! :-)
>
> T
Le 09/12/2021 à 19:53, Christoph Schmitz a écrit :
Jean-Marc,
Fantastic! Problem solved! :-)
Thanks for confirming. The issue was in the borderless table at the top
of the document. There are still things that I do not understand in your
file, I will try to return to it.
JMarc
--
lyx-devel
Jean-Marc,
Fantastic! Problem solved! :-)
Chris
> Am 09.12.2021 um 19:47 schrieb Jean-Marc Lasgouttes :
>
> Le 09/12/2021 à 18:56, Christoph Schmitz a écrit :
>> Hi Jean-Marc,
>> No, it still does not work.
>> But I do not see any committed updates. The last commit is "ctests: log a
>> fixed
Le 09/12/2021 à 18:56, Christoph Schmitz a écrit :
Hi Jean-Marc,
No, it still does not work.
But I do not see any committed updates. The last commit is "ctests: log a fixed
issue (fr Linguistics.lyx)", 13 hours ago.
You are right, I forgot the most important part. That's what happens
when d
Hi Jean-Marc,
No, it still does not work.
But I do not see any committed updates. The last commit is "ctests: log a fixed
issue (fr Linguistics.lyx)", 13 hours ago.
Chris
> Am 09.12.2021 um 17:21 schrieb Jean-Marc Lasgouttes :
>
> Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
>> No, alw
Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
No, always¥s the same, whether no windows is open, whether it has the standard
size or any other size...
Hi Christoph,
Can you confirm that it works now?
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/l
Le 09/12/2021 à 12:23, Kornel Benko a écrit :
Am Wed, 8 Dec 2021 23:54:03 +0100
schrieb Jean-Marc Lasgouttes :
Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
No, always¥s the same, whether no windows is open, whether it has the standard
size
or any other size...
Believe it or not, this
Am Wed, 8 Dec 2021 23:54:03 +0100
schrieb Jean-Marc Lasgouttes :
> Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
> > No, always¥s the same, whether no windows is open, whether it has the
> > standard size
> > or any other size...
>
> Believe it or not, this is good news. Hopefully I will
I spotted the problem!
I first exported the document to LyX 2.3 format with the older LyX 2.4 version
that could still open the file, and opened it then with the problematic LyX 2.4
version. Then I saved the file again, created a diff and replaced each
difference in the faulty LyX document one
No, always¥s the same, whether no windows is open, whether it has the standard
size or any other size...
Chris
> Am 08.12.2021 um 22:32 schrieb Jean-Marc Lasgouttes :
>
> Le 08/12/2021 à 20:06, Christoph Schmitz a écrit :
>> I am attaching one of the documents that can no longer be opened. Do
Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
No, always¥s the same, whether no windows is open, whether it has the standard
size or any other size...
Believe it or not, this is good news. Hopefully I will be able to reproduce.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http
Le 08/12/2021 à 20:06, Christoph Schmitz a écrit :
I am attaching one of the documents that can no longer be opened. Do you have
any idea what could be the cause of the problem?
Unfortunately, I have an idea :( I pushed big changes in document
display. I will try to see if I can reproduce tom
I compile LyX for macOS myself. Since yesterday my compiled versions of LyX do
not open several files anymore (on both Intel and M1 Macs). I see the macOS
beachball forever, but LyX does not crash. Luckily I found a copy of a previous
LyX version, which still works(compiled on Dec 6).
This
; > > > Am Montag, 31. Dezember 2018 16:07:32 CET schrieb Scott Kostyshak <
> > > > skost...@lyx.org>:
> > > > > On both 2.3.x and master, with my updated system, our europassCV
> > > > > example
> > > > > file fails to compil
gt; > > skost...@lyx.org>:
> > > > On both 2.3.x and master, with my updated system, our europassCV
> > > > example
> > > > file fails to compile for me.
> > > >
> > > > The corresponding ctests fail:
> > > >
updated system, our europassCV
> > > example
> > > file fails to compile for me.
> > >
> > > The corresponding ctests fail:
> > >
> > > ctest -R "europassCV_pdf2"
> > >
> > > The first error is:
> >
me.
> >
> > The corresponding ctests fail:
> >
> > ctest -R "europassCV_pdf2"
> >
> > The first error is:
> >
> > ! Extra \or.
> >
> > Does compilation succeed for anyone with an updated TL 2018?
> >
> > Scot
Am Montag, 31. Dezember 2018 16:07:32 CET schrieb Scott Kostyshak
:
> On both 2.3.x and master, with my updated system, our europassCV example
> file fails to compile for me.
>
> The corresponding ctests fail:
>
> ctest -R "europassCV_pdf2"
>
> The
On both 2.3.x and master, with my updated system, our europassCV example
file fails to compile for me.
The corresponding ctests fail:
ctest -R "europassCV_pdf2"
The first error is:
! Extra \or.
Does compilation succeed for anyone with an updated TL 2018?
Scott
signature.asc
D
After looking into all the python scripts I have fixed most of the issues.
The only possible issues are files that are not in utf-8 encoding, I think that
in all those cases we are on the safe side but I could be wrong.
The patch as it is should be compatible with both python 2 and python 3, so
On Tuesday, 3 April 2018 12.55.20 WEST Helge Hafting wrote:
> Existing documents with xfig figures cannot be opened, because LyX then
> invokes /usr/share/lyx/scripts/fig_copy.py which python3 does not
> understand. In other words, backward compatibility seems broken.
>
> On arch linux, "python" i
On Tuesday, 3 April 2018 13.28.55 WEST José Abílio Matos
wrote:
> Could you test the attached patch?
There was a typo in the last patch...
--
José Abílio
diff --git a/lib/scripts/fig_copy.py b/lib/scripts/fig_copy.py
index d5e0421668..c6235195c2 100644
--- a/lib/scripts/fig_copy.py
+++ b/lib/sc
On Tuesday, 3 April 2018 12.55.20 WEST Helge Hafting wrote:
> Existing documents with xfig figures cannot be opened, because LyX then
> invokes /usr/share/lyx/scripts/fig_copy.py which python3 does not
> understand. In other words, backward compatibility seems broken.
>
> On arch linux, "python" i
Den 31. jan. 2018 21:25, skrev Scott Kostyshak:
On Wed, Jan 31, 2018 at 01:39:31PM +, Helge Hafting wrote:
File->Export->PDF is supposed to create a PDF in a temp directory, and then
copy it to the right place.
For me, this fails when the working directory is on a sshfs mount. (It works
f
Existing documents with xfig figures cannot be opened, because LyX then
invokes /usr/share/lyx/scripts/fig_copy.py which python3 does not
understand. In other words, backward compatibility seems broken.
On arch linux, "python" is now python3. Python version 2 is available,
but is called "pyth
This is now bug 11100, sorry for taking so long time to register it.
Helge Hafting
On Wed, Jan 31, 2018 at 08:25:17PM +, Scott Kostyshak wrote:
> On Wed, Jan 31, 2018 at 01:39:31PM +, Helge Hafting wrote:
> > File->Export->PDF is supposed to create a PDF in a temp directory, and then
> > copy it to the right place.
> >
> > For me, this fails when the working directory is
On Wed, Jan 31, 2018 at 01:39:31PM +, Helge Hafting wrote:
> File->Export->PDF is supposed to create a PDF in a temp directory, and then
> copy it to the right place.
>
> For me, this fails when the working directory is on a sshfs mount. (It works
> fine on a local filesystem)
>
> This has wo
uestion about overwriting it. So
LyX is able to see if it exists. But the copy fail in all cases - file
or no file to overwrite.
The sshfs mount command, if it matters:
sshfs -o workaround=rename,writeback_cache=no helgehaf@158.38.50.20:/www
~/www
"workaround=rename": Emulate ove
Am Freitag, 27. Oktober 2017 um 19:31:50, schrieb Guenter Milde
> On 2017-10-27, Kornel Benko wrote:
>
> > [-- Type: text/plain, Encoding: 7bit --]
>
> > Am Freitag, 27. Oktober 2017 um 13:52:36, schrieb Scott Kostyshak
> >
> >> On Fri, Oct 27, 2017 at 01:46:38PM +, Guenter Milde wrote:
>
On 2017-10-27, Kornel Benko wrote:
> [-- Type: text/plain, Encoding: 7bit --]
> Am Freitag, 27. Oktober 2017 um 13:52:36, schrieb Scott Kostyshak
>
>> On Fri, Oct 27, 2017 at 01:46:38PM +, Guenter Milde wrote:
>> > > So, remove the eu_UserGuide.lyx from export test or correct the paths
>>
Am Freitag, 27. Oktober 2017 um 13:52:36, schrieb Scott Kostyshak
> On Fri, Oct 27, 2017 at 01:46:38PM +, Guenter Milde wrote:
>
> > > So, remove the eu_UserGuide.lyx from export test or correct the paths and
> > > add again LaTeX.png?
> >
> > I propose to remove (ignore) the export test.
On Fri, Oct 27, 2017 at 01:46:38PM +, Guenter Milde wrote:
> > So, remove the eu_UserGuide.lyx from export test or correct the paths and
> > add again LaTeX.png?
>
> I propose to remove (ignore) the export test.
I'm fine with either way.
Scott
signature.asc
Description: PGP signature
On 2017-10-27, Kornel Benko wrote:
> Am Donnerstag, 26. Oktober 2017 um 17:04:41, schrieb Scott Kostyshak
>
>> On Thu, Oct 26, 2017 at 08:44:34PM +, Kornel Benko wrote:
>> > > > Thanks, Kornel. Why not put the string inside "diestack" instead of
>> > > > separate print?
>> > >
>> > > I did
Am Donnerstag, 26. Oktober 2017 um 17:04:41, schrieb Scott Kostyshak
> On Thu, Oct 26, 2017 at 08:44:34PM +, Kornel Benko wrote:
>
> > > > Thanks, Kornel. Why not put the string inside "diestack" instead of
> > > > separate print?
> > >
> > > I did it at first, but the string did not appear
On Thu, Oct 26, 2017 at 08:44:34PM +, Kornel Benko wrote:
> > > Thanks, Kornel. Why not put the string inside "diestack" instead of
> > > separate print?
> >
> > I did it at first, but the string did not appear in the output. Will
> > investigate why.
> >
> > > Scott
> >
>
> Hm, must have
> > Author: Kornel Benko
> > > Date: Thu Oct 26 21:48:33 2017 +0200
> > >
> > > Cmake export tests: Make test fail if there is some non-existant
> > > sub-file
> > > ---
> > > development/autotests/useSystemFonts.pl |7 +
On Thu, Oct 26, 2017 at 08:32:52PM +, Kornel Benko wrote:
> I did it at first, but the string did not appear in the output. Will
> investigate why.
I was just curious. If we do stay with print, let's at least print to
STDERR?
Scott
signature.asc
Description: PGP signature
Cmake export tests: Make test fail if there is some non-existant
> > sub-file
> > ---
> > development/autotests/useSystemFonts.pl |7 +++
> > 1 files changed, 7 insertions(+), 0 deletions(-)
> >
> > diff --git a/development/autotests/useSystemFont
On Thu, Oct 26, 2017 at 07:49:36PM +, Kornel Benko wrote:
> commit d63a866106a088fbf42504215a0a9193437e70de
> Author: Kornel Benko
> Date: Thu Oct 26 21:48:33 2017 +0200
>
> Cmake export tests: Make test fail if there is some non-existant sub-file
> ---
>
On 07/18/2016 05:22 AM, Jean-Marc Lasgouttes wrote:
> Le 18/07/2016 à 04:56, Richard Heck a écrit :
>> commit 4a75d358a1f0f6c4b63b64107c86d59cce4eecf9
>> Author: Richard Heck
>> Date: Sun Jul 17 22:50:17 2016 -0400
>>
>> The way this was previously, i
Le 18/07/2016 à 04:56, Richard Heck a écrit :
commit 4a75d358a1f0f6c4b63b64107c86d59cce4eecf9
Author: Richard Heck
Date: Sun Jul 17 22:50:17 2016 -0400
The way this was previously, it had to fail if the GUI language
was not English: We return the the abbreviated author "One an
Kornel Benko wrote:
> I'd like to remove the file development/cmake/configCompiler.h.msvc. It
> was meant as a cache-like set for compiler settings for msvc.
+1
> As a first step I want to disable the possibility to select this bypass
> (see attached) I expect this works for windows, but will wa
Am Dienstag, 14. Juni 2016 um 02:24:02, schrieb LyX Ticket Tracker
> #10214: Fail to Compile LyX with Visual C++ 2015
> -+--
> Reporter: zxvc | Owner: lasgouttes
> Type: defect | Status: closed
> Pr
On 2016-03-15, Kornel Benko wrote:
>> > Tested again:
>> > 0% tests passed, 11 tests failed out of 11
...
>> Kornel, could you please try to "recreate" one of the failing test cases "by
>> hand" and report the error log?
> OK, trying with EXAMPLES_export/examples/ru/splash_pdf5_systemF:
> ...
, but as the tests work (again) for both of you, you
> >> > could also just leave it.
>
> >> The tests do not work for me.
>
> Uff.
>
> >> I see that Kornel reports that
> >> .*/ru/Intro_pdf4_systemF
> >> now passes, but that test was neve
> I see that Kornel reports that
>> .*/ru/Intro_pdf4_systemF
>> now passes, but that test was never one of the 11 that failed for me.
>> The failing tests I reported still fail for me.
>> Do any of the tests I reported in the original email pass for you
>> Kornel?
l reports that
> .*/ru/Intro_pdf4_systemF
> now passes, but that test was never one of the 11 that failed for me.
> The failing tests I reported still fail for me.
>
> Do any of the tests I reported in the original email pass for you
> Kornel?
Tested again:
0% tests passed, 11 tests failed out of 11
> Scott
Kornel
signature.asc
Description: This is a digitally signed message part.
t as the tests work (again) for both of you, you
> could also just leave it.
The tests do not work for me.
I see that Kornel reports that
.*/ru/Intro_pdf4_systemF
now passes, but that test was never one of the 11 that failed for me.
The failing tests I reported still fail for me.
Do an
On 2016-03-13, Scott Kostyshak wrote:
> [-- Type: text/plain, Encoding: --]
> On Thu, Mar 10, 2016 at 05:24:55PM -0500, Scott Kostyshak wrote:
>> On Wed, Mar 09, 2016 at 07:40:34PM +, Guenter Milde wrote:
>> Thanks, Guenter. This really puts things into perspective for me.
>> I updated #803
On Thu, Mar 10, 2016 at 05:24:55PM -0500, Scott Kostyshak wrote:
> On Wed, Mar 09, 2016 at 07:40:34PM +, Guenter Milde wrote:
> Thanks, Guenter. This really puts things into perspective for me.
> I updated #8035 with your clear explanation.
Should we mark these tests as unreliable, with a com
;
> Not really. It it only fails with some fonts - actually only with some
> versions of fonts, to it is hard to reproduce. Your minimal example may work
> at some place and fail at another one. (Just like our tests did.)
>
> Also, it is not a new problem but a long standing issue.
I sent an email
> to the TeX Live list with a minimal example of a document that succeeded
> before the update and now fails?
Not really. It it only fails with some fonts - actually only with some
versions of fonts, to it is hard to reproduce. Your minimal example may work
at some place and
On Sat, Mar 05, 2016 at 09:36:43PM +, Guenter Milde wrote:
> After all, this is a know upstream bug, not a "real" LyX issue (although LyX
> may add a workaround as suggested in #8035).
Do you have a link to the upstream bug report?
So to make sure I understand, it would not be helpful if I
>> I've updated TL for the first time in a while and now the
> >> >>> >> >> following 11 tests fail for me:
>
> >> Did you manage to fix the problem or are the tests still failing?
>
> >> It works here:
>
> >>
On 2016-03-06, Kornel Benko wrote:
> Am Samstag, 5. März 2016 um 21:36:43, schrieb Guenter Milde
>
>> On 2016-02-27, Guenter Milde wrote:
Dear Kornel,
>> >>> >> >> I've updated TL for the first time in a while and now the
>> >>> >
:
>
> Dear Kornel,
>
> >>> >> >> I've updated TL for the first time in a while and now the
> >>> >> >> following 11 tests fail for me:
>
> Did you manage to fix the problem or are the tests still failing?
>
> It works h
n a while and now the
>>> >> >> following 11 tests fail for me:
Did you manage to fix the problem or are the tests still failing?
It works here:
/src/lyxtest > ctest -R .*/ru/Intro_pdf4_systemF
Test project /usr/local/src/lyxtest
Start 1655: MANUALS_export/doc/ru/I
On Sat, Feb 27, 2016 at 07:50:31PM +, Guenter Milde wrote:
> On 2016-02-27, Scott Kostyshak wrote:
> > On Sat, Feb 27, 2016 at 10:35:13AM +, Guenter Milde wrote:
> >> On 2016-02-26, Kornel Benko wrote:
>
> >> I insisted on a "hand export" as a means to get a helpfull error report.
> >> Jus
On 2016-02-27, Scott Kostyshak wrote:
> On Sat, Feb 27, 2016 at 10:35:13AM +, Guenter Milde wrote:
>> On 2016-02-26, Kornel Benko wrote:
>> I insisted on a "hand export" as a means to get a helpfull error report.
>> Just saying: "export fails" is no starting point for an investigation.
>> Unf
On Sat, Feb 27, 2016 at 10:35:13AM +, Guenter Milde wrote:
> On 2016-02-26, Kornel Benko wrote:
> I insisted on a "hand export" as a means to get a helpfull error report.
> Just saying: "export fails" is no starting point for an investigation.
>
> Unfortunately,
>
> * the tests cannot tell m
On 2016-02-26, Kornel Benko wrote:
> Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde
>
>> On 2016-02-26, Kornel Benko wrote:
>> >> >> I've updated TL for the first time in a while and now the following 11
>> >> >> tests fai
On Fri, Feb 26, 2016 at 10:50:02PM +0100, Kornel Benko wrote:
> Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde
>
> > This is why I argue in
> > http://www.lyx.org/trac/ticket/8035#comment:7
> > to ignore the polyglossia error: LyX's check for missing characters is more
> > accu
um 01:15:52, schrieb Scott Kostyshak
> >> >
> >> >> I've updated TL for the first time in a while and now the following 11
> >> >> tests fail for me:
>
> ...
>
> The common feature of these is (as regexp):
>
> .*/ru/.*systemF
>
first time in a while and now the following 11
>> >> tests fail for me:
...
The common feature of these is (as regexp):
.*/ru/.*systemF
.*/uk/.*systemF
>> Looks like a problem with either Cyrillic fonts or polyglossia.
>> Could you export at least one example &qu
for the first time in a while and now the following 11
> >> tests fail for me:
>
> >> ctest -R
> >> "MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|
> > confirmed
>
> >> MANUALS_export/doc/uk/Intro_dvi3_syste
On 2016-02-26, Kornel Benko wrote:
> [-- Type: text/plain, Encoding: 7bit --]
> Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak
>
>> I've updated TL for the first time in a while and now the following 11
>> tests fail for me:
>> cte
Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak
> I've updated TL for the first time in a while and now the following 11
> tests fail for me:
>
> ctest -R
> "MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|
confirmed
I've updated TL for the first time in a while and now the following 11
tests fail for me:
ctest -R
"MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|MANUALS_export/doc/uk/Intro_dvi3_systemF|MANUALS_export/doc/uk/Intro_pdf5_systemF|EXAMPLES_export/e
Am Donnerstag, 9. April 2015 um 13:28:02, schrieb Jean-Pierre Chrétien
> Kornel Benko lyx.org> writes:
>
> > Yes, the png are there, but there are also .svgz files. They are
> preferably used and converted to pdf.
>
> You mean, converted on the fly each time they are needed ? I correctly see
>
Kornel Benko lyx.org> writes:
> Yes, the png are there, but there are also .svgz files. They are
preferably used and converted to pdf.
You mean, converted on the fly each time they are needed ? I correctly see
the inskape commands appearb in the buffer line when I view PDF, but the
error happens
Scott Kostyshak wrote:
> examples/beamer-article.lyx
This one's another instance of the scrambled language environment nesting
(similar to #8896). I've committed something that works around this (since the
problem itself is rather tricky).
Regards,
Jürgen
On Sat, Dec 14, 2013 at 3:02 AM, Jürgen Spitzmüller wrote:
> Scott Kostyshak wrote:
>> I'm not so worried about many people using non-TeX fonts for LyX's
>> manuals and examples, but the failure of so many documents makes me
>> think that LyX could be doing something wrong.
>>
>> Any ideas?
>
> A
Scott Kostyshak wrote:
> I'm not so worried about many people using non-TeX fonts for LyX's
> manuals and examples, but the failure of so many documents makes me
> think that LyX could be doing something wrong.
>
> Any ideas?
A probable cause could be excessive preamble code that is only targeted
The following at the bottom of this email compile fine with XeTeX (not
changing anything leads to using TeX fonts). However, they all fail if
I go to Document > Settings > Fonts and click "use non-TeX fonts" and
then set the three fonts to FreeSans, they fail. Sometimes I get an
en
On Tue, Nov 12, 2013 at 9:14 PM, Tommaso Cucinotta wrote:
> commit 777156e0ff41aa1d14cb185928c8ef4c7b4dd251
> Author: Tommaso Cucinotta
> Date: Wed Nov 13 02:13:32 2013 +
>
> Added self-sanity-check for presence of pcregrep, otherwise many (almost
> all) tests wil
As described. Should be an easy fix?
rh
Helge Hafting wrote:
> Trying to compile LyX 2.1 in order to update translations.
>
> LyX itself compiles and links, but make breaks on tex2lyx. So I can
> probably work on translations anyway, but I tought you might like to know.
> This happens:
Do you compile on a clean tree? Sometimes I see t
Trying to compile LyX 2.1 in order to update translations.
LyX itself compiles and links, but make breaks on tex2lyx. So I can
probably work on translations anyway, but I tought you might like to
know. This happens:
$ ./configure --with-gnu-ld --with-version-suffix=-d
[...]
$ make -j 9
[...
Scott Kostyshak wrote:
> On Mon, Aug 5, 2013 at 3:10 PM, Pavel Sanda wrote:
> > Kornel Benko wrote:
> >> I do not agree. We should check attic too IMHO (or else do not provide it).
> >> Therefore I prefer you to commit :)
> >
> > We "provide it" :)
> > Have you ever looked at the junk in developme
Am Montag, 5. August 2013 um 19:42:25, schrieb Scott Kostyshak
> On Mon, Aug 5, 2013 at 3:10 PM, Pavel Sanda wrote:
> > Kornel Benko wrote:
> >> I do not agree. We should check attic too IMHO (or else do not provide it).
> >> Therefore I prefer you to commit :)
> >
> > We "provide it" :)
> > Hav
On Mon, Aug 5, 2013 at 3:10 PM, Pavel Sanda wrote:
> Kornel Benko wrote:
>> I do not agree. We should check attic too IMHO (or else do not provide it).
>> Therefore I prefer you to commit :)
>
> We "provide it" :)
> Have you ever looked at the junk in development/attic? It's almost definition
> th
On Mon, Aug 5, 2013 at 7:48 AM, Kornel Benko wrote:
> Am Montag, 5. August 2013 um 07:41:31, schrieb Scott Kostyshak
>
>
>> On Mon, Aug 5, 2013 at 7:34 AM, Kornel Benko wrote:
>
>> > Am Montag, 5. August 2013 um 07:07:58, schrieb Scott Kostyshak
>
>> >
>
>> >
>
>> >> On Mon, Aug 5, 2013 at 6:02
Kornel Benko wrote:
> I do not agree. We should check attic too IMHO (or else do not provide it).
> Therefore I prefer you to commit :)
We "provide it" :)
Have you ever looked at the junk in development/attic? It's almost definition
that we put files there if they are no more functional. The only
gt;
> >
> > > >> > Scott Kostyshak wrote:
> >
> > > >
> >
> > > >> >> > Sorry, I meant "This is also a test for lyx2lyx, isn't it?"
> >
> > > >
> >
> > > >> >>
> >
> > > >
> >
>
On Mon, Aug 5, 2013 at 8:53 AM, Vincent van Ravesteijn wrote:
> Op 3-8-2013 9:54, Scott Kostyshak schreef:
>
>> On Fri, Aug 2, 2013 at 2:36 PM, Kornel Benko wrote:
>>>
>>> Am Freitag, 2. August 2013 um 20:06:40, schrieb Vincent van Ravesteijn
>>>
>>>
> Why should we update? This is also the
ot;This is also a test for lyx2lyx, isn't it?"
>
>> >
>
>> >> >>
>
>> >
>
>> >> >> My opinion is that we should update those documents. I agree that it
>
>> >
>
>> >> >
>
>> >
>
>
Op 3-8-2013 9:54, Scott Kostyshak schreef:
On Fri, Aug 2, 2013 at 2:36 PM, Kornel Benko wrote:
Am Freitag, 2. August 2013 um 20:06:40, schrieb Vincent van Ravesteijn
Why should we update? This is also the test for lyx2lyx, isn't it?
No, this is not the way to test lyx2lyx.
Vincent
Sorry,
Am Montag, 5. August 2013 um 14:40:12, schrieb Vincent van Ravesteijn
> Op 5-8-2013 13:07, Scott Kostyshak schreef:
> > On Mon, Aug 5, 2013 at 6:02 AM, Vincent van Ravesteijn wrote:
> >> Op 4-8-2013 22:23, Scott Kostyshak schreef:
> >>
> >>> On Sat, Aug 3, 2013 at 3:54 AM, Scott Kostyshak wrote
uld update those documents. I agree
that it
> >
> >> >
> >
> >> > attic is just garbage and it is somewhat absurd that test
should fail
> >
> >> > because of some contents in there. Please create proper tests for
> >
Op 5-8-2013 13:07, Scott Kostyshak schreef:
On Mon, Aug 5, 2013 at 6:02 AM, Vincent van Ravesteijn wrote:
Op 4-8-2013 22:23, Scott Kostyshak schreef:
On Sat, Aug 3, 2013 at 3:54 AM, Scott Kostyshak wrote:
On Fri, Aug 2, 2013 at 5:58 AM, Vincent van Ravesteijn
wrote:
On Fri, Aug 2, 2013 at
t; >
> >> > Scott Kostyshak wrote:
> >
> >> >> > Sorry, I meant "This is also a test for lyx2lyx, isn't it?"
> >
> >> >>
> >
> >> >> My opinion is that we should update those documents. I agree that it
> >
>
a test for lyx2lyx, isn't it?"
>
>> >>
>
>> >> My opinion is that we should update those documents. I agree that it
>
>> >
>
>> > attic is just garbage and it is somewhat absurd that test should fail
>
>> > because of s
that we should update those documents. I agree that it
> >
> > attic is just garbage and it is somewhat absurd that test should fail
> > because of some contents in there. Please create proper tests for
> > things you want to test and do not impose some future maintenance
> >
On Mon, Aug 5, 2013 at 5:56 AM, Pavel Sanda wrote:
> Scott Kostyshak wrote:
>> > Sorry, I meant "This is also a test for lyx2lyx, isn't it?"
>>
>> My opinion is that we should update those documents. I agree that it
>
> attic is just garbage an
Am Montag, 5. August 2013 um 07:41:31, schrieb Scott Kostyshak
> On Mon, Aug 5, 2013 at 7:34 AM, Kornel Benko wrote:
> > Am Montag, 5. August 2013 um 07:07:58, schrieb Scott Kostyshak
> >
> >
> >> On Mon, Aug 5, 2013 at 6:02 AM, Vincent van Ravesteijn
> >> wrote:
> >
> > [snip]
> >
> >> > As f
On Mon, Aug 5, 2013 at 7:34 AM, Kornel Benko wrote:
> Am Montag, 5. August 2013 um 07:07:58, schrieb Scott Kostyshak
>
>
>> On Mon, Aug 5, 2013 at 6:02 AM, Vincent van Ravesteijn
>> wrote:
>
> [snip]
>
>> > As far as I see it, it cannot happen that there is no
>> > default_output_format.
>
>>
>
1 - 100 of 228 matches
Mail list logo
