Le 19/11/2022 à 11:38, Jürgen Spitzmüller a écrit :
Am Freitag, dem 18.11.2022 um 17:33 +0100 schrieb Jean-Marc Lasgouttes:
What can you do to help?
* have look at the diff in src to spot what I broke
Looks good from what I can tell.
Thanks for checking.
* and look at KILLQT4 annotations t
Am Freitag, dem 18.11.2022 um 17:33 +0100 schrieb Jean-Marc Lasgouttes:
> What can you do to help?
> * have look at the diff in src to spot what I broke
Looks good from what I can tell.
> * and look at KILLQT4 annotations to see whethe rsome of them are in
> your ballpark
> * look for things to
Le 18/11/2022 à 18:03, Scott Kostyshak a écrit :
What can you do to help?
* have look at the diff in src to spot what I broke
* and look at KILLQT4 annotations to see whethe rsome of them are in your
ballpark
* look for things to do in TODO.killqt4
I think this was meant for Jürgen, but to be c
On Fri, Nov 18, 2022 at 05:33:43PM +0100, Jean-Marc Lasgouttes wrote:
> Le 17/11/2022 à 07:34, Jürgen Spitzmüller a écrit :
> > Am Mittwoch, dem 16.11.2022 um 11:11 -0500 schrieb Scott Kostyshak:
> > > Does anyone object then to supporting only Qt5 for
> > > 2.4.0 (and forward)?
> >
> > No. I thin
Le 17/11/2022 à 07:34, Jürgen Spitzmüller a écrit :
Am Mittwoch, dem 16.11.2022 um 11:11 -0500 schrieb Scott Kostyshak:
Does anyone object then to supporting only Qt5 for
2.4.0 (and forward)?
No. I think now is the time to do it.
I created a new branch killqt4 that removes #ifdefs in src and
Am Mittwoch, dem 16.11.2022 um 11:11 -0500 schrieb Scott Kostyshak:
> Does anyone object then to supporting only Qt5 for
> 2.4.0 (and forward)?
No. I think now is the time to do it.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-deve
On Wed, Nov 16, 2022 at 06:03:04PM +0100, Jean-Marc Lasgouttes wrote:
> Le 16/11/2022 à 17:57, Scott Kostyshak a écrit :
> > I don't know. What do others think? Do we go all-in and drop Qt4 and do
> > all the clean up now to simplify the code? That would indeed feel nice.
> >
> > Or do we leave it
Le 16/11/2022 à 17:57, Scott Kostyshak a écrit :
I don't know. What do others think? Do we go all-in and drop Qt4 and do
all the clean up now to simplify the code? That would indeed feel nice.
Or do we leave it as is, and just officially not support Qt4, so that if
some (from what I understand,
On Wed, Nov 16, 2022 at 05:51:30PM +0100, Jean-Marc Lasgouttes wrote:
> Le 16/11/2022 à 17:11, Scott Kostyshak a écrit :
> > On Wed, Nov 16, 2022 at 02:37:18PM +0100, Thibaut Cuvelier wrote:
> >
> > > Well, if barely anyone tests with Qt 4 (I'm only using Qt 5.15), it's
> > > already unsupported i
Le 16/11/2022 à 17:11, Scott Kostyshak a écrit :
On Wed, Nov 16, 2022 at 02:37:18PM +0100, Thibaut Cuvelier wrote:
Well, if barely anyone tests with Qt 4 (I'm only using Qt 5.15), it's
already unsupported in practice and making the necessary changes would be
(1) cumbersome and (2) a waste of re
On Wed, Nov 16, 2022 at 02:37:18PM +0100, Thibaut Cuvelier wrote:
> Well, if barely anyone tests with Qt 4 (I'm only using Qt 5.15), it's
> already unsupported in practice and making the necessary changes would be
> (1) cumbersome and (2) a waste of resources (little gain in supporting
> versions
On Mon, 14 Nov 2022 at 19:38, Scott Kostyshak wrote:
> On Tue, Oct 18, 2022 at 10:51:34AM -0400, Scott Kostyshak wrote:
> > On Tue, Oct 18, 2022 at 03:12:40PM +0200, Pavel Sanda wrote:
> > > On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote:
> > > > Still, I am wondering why we
On Tue, Oct 18, 2022 at 10:51:34AM -0400, Scott Kostyshak wrote:
> On Tue, Oct 18, 2022 at 03:12:40PM +0200, Pavel Sanda wrote:
> > On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote:
> > > Still, I am wondering why we insist on supporting Qt4 for 2.4.0
> > > (especially
> > > co
On Tue, Oct 18, 2022 at 06:27:00PM +0200, Jean-Marc Lasgouttes wrote:
> >That was decided when we planned to release 2.4 at the end of 2019.
> >It's clear we won't be able to push 2.4 even for next debian stable
> >and I think we can relax Qt4 support and move on.
>
> What do you mean by "relax" ?
Le 18/10/2022 à 15:12, Pavel Sanda a écrit :
On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote:
Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially
considering that we will have to continue this game for 2+ years after
that).
That was decided when we
On Tue, Oct 18, 2022 at 03:12:40PM +0200, Pavel Sanda wrote:
> On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote:
> > Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially
> > considering that we will have to continue this game for 2+ years after
> > that).
On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote:
> Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially
> considering that we will have to continue this game for 2+ years after
> that).
That was decided when we planned to release 2.4 at the end of 2019.
Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially considering that we will have to continue this game for 2+ years after that).
I join to your wondering. And here is the patch to at least clean
conditional code portions for Qt < 4.8.
Yuriy
From ba021353090922642e0e2
You can use
branchCO->itemData(branchCO->currentIndex()).toString()
This works in Qt 4 and upwards.
Thanks, Jürgen! This way even dedicated Qt4 users will be able to enjoy
this update :)
Committed.
Yuriy
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listin
Am Freitag, dem 07.10.2022 um 18:02 +0300 schrieb Yuriy Skalko:
> Now with "(master)" suffix in combobox labels we cannot use them
> directly as branch names. Is is OK to disable this for Qt4
> alltogether,
> as README says that LyX is only compilable on Qt4?
You can use
branchCO->itemData(bran
Le 07/10/2022 à 17:02, Yuriy Skalko a écrit :
Now with "(master)" suffix in combobox labels we cannot use them
directly as branch names. Is is OK to disable this for Qt4 alltogether,
as README says that LyX is only compilable on Qt4?
This seems like an acceptable solution, if the code is simpl
ames. Is is OK to disable this for Qt4 alltogether,
as README says that LyX is only compilable on Qt4?
Yuriy
From 716cc9991d1025614424b7ceaa6761ab0f817083 Mon Sep 17 00:00:00 2001
From: Yuriy Skalko
Date: Fri, 7 Oct 2022 17:41:46 +0300
Subject: [PATCH] Show branches from master document in branch inset dialog
---
src/fro
Le 06/10/2022 à 19:39, Yuriy Skalko a écrit :
Hello all,
Currently in LyX you can insert into child documents the insets for
branches defined in master document only. But it is impossible to change
the branch afterwards for such inset because master branches are not
shown in the "B
Am Freitag, dem 07.10.2022 um 09:43 +0200 schrieb Jürgen Spitzmüller:
> branchCO->addItem(
> toqstr(bformat( _("%1$s[[branch]]
> (%2$s)[[master]]"),
> toqstr(branch), qt_("master";
that should be _("master") of course.
--
Jürgen
signature.asc
Description: This is a digit
Am Donnerstag, dem 06.10.2022 um 20:39 +0300 schrieb Yuriy Skalko:
> Hello all,
>
> Currently in LyX you can insert into child documents the insets for
> branches defined in master document only. But it is impossible to
> change
> the branch afterwards for such inset because m
Hello all,
Currently in LyX you can insert into child documents the insets for
branches defined in master document only. But it is impossible to change
the branch afterwards for such inset because master branches are not
shown in the "Branch Settings" dialog.
The attached patch
Am Samstag, 13. April 2019, 15:54:03 CEST schrieb Guenter Milde:
> Thank you for testing and reporting
> (also for the helpfull logs in private mail).
>
> Günter
>
Confirmed that the /ja/ tests now pass :)
Kornel
signature.asc
Description: This is a digitally signed message part.
On 2019-04-13, Kornel Benko wrote:
> Am Freitag, 12. April 2019, 21:44:36 CEST schrieb Kornel Benko:
...
> That is 18 tests are failing, (not 164)
Mind, that this is after activation of a ~65 previously ignored tests for
Japanese with non-TeX fonts (.*_systemF)!
> ..., the remaining failures ar
Am Freitag, 12. April 2019, 21:44:36 CEST schrieb Kornel Benko:
> Am Freitag, 12. April 2019, 18:28:43 CEST schrieb Günter Milde:
> > commit 62f8b4fac126e1c0dc85107dac4852d725dc1cc9
> > Author: Günter Milde
> > Date: Fri Apr 12 18:34:06 2019 +0200
> >
> > Document languages with new polygl
Le 06/04/2017 à 06:41, Scott Kostyshak a écrit :
commit 22c4a24a360b4607551ff5275cf24ac5f5e5eb4a
Author: Scott Kostyshak
Date: Thu Apr 6 00:34:51 2017 -0400
Document new behavior of "delete" LFUNs
- Describe the change in RELEASE-NOTES.
- Update the example for inset-forall.
On Sun, Sep 25, 2016 at 01:33:38AM +0200, Enrico Forestieri wrote:
> On Thu, Sep 22, 2016 at 01:07:28PM +, Guenter Milde wrote:
>
> > Unit symbols wrong when using a fraction in \text:
> >
> > \begin_inset Formula $50\,\text{\frac{m}{s}}$
> > \end_inset
> >
> > exported as
> >
> > $50\,\
On Thu, Sep 22, 2016 at 01:07:28PM +, Guenter Milde wrote:
>
> It still fails for \textdegree:
>
> - \textdegree in math-mode input as-is
> - \textdegree in "mathematical text" wrapped in \ensuremath{}
This is because the MathMacro class was missing a currentMode method.
Fixed at 314e30d
On 2016-09-23, Jean-Marc Lasgouttes wrote:
> Le 22/09/2016 à 00:43, Guillaume Munch a écrit :
>> The attached patch does what you want.
>> The only problem is that now "View/Update Master Document" is always
>> shown.
> What about renaming master-buffer-view
Le 23/09/2016 à 11:31, Jean-Marc Lasgouttes a écrit :
Le 22/09/2016 à 00:43, Guillaume Munch a écrit :
The attached patch does what you want.
The only problem is that now "View/Update Master Document" is always
shown.
What about renaming master-buffer-view to buffer-view and buff
Le 22/09/2016 à 00:43, Guillaume Munch a écrit :
The attached patch does what you want.
The only problem is that now "View/Update Master Document" is always
shown.
What about renaming master-buffer-view to buffer-view and buffer-view to
child-buffer-view ("View only child
On 2016-09-21, Guillaume Munch wrote:
> Le 19/09/2016 à 11:58, Enrico Forestieri a écrit :
>> When inserting a command or symbol in mathed, it is now automatically
>> wrapped in a real inset (either \text or \ensuremath) assuring the correct
>> mode, instead of being wrapped only in the output. Th
make sense to have a first-class command that just
does the right thing IMO.
The attached patch does what you want.
The only problem is that now "View/Update Master Document" is always
shown.
I suppose the thing to do is something like this: If we are the master,
th
t;> However, it would make sense to have a first-class command that just
>> does the right thing IMO.
>>
>
>
> The attached patch does what you want.
>
> The only problem is that now "View/Update Master Document" is always
> shown.
I suppose the thing to do i
patch does what you want.
The only problem is that now "View/Update Master Document" is always
shown.
>From 683f25efbcb36cf0ff310395fe7cca1e7eaaf4a4 Mon Sep 17 00:00:00 2001
From: Guillaume Munch
Date: Thu, 22 Sep 2016 00:38:40 +0200
Subject: [PATCH] master-buffer-{view,update} now
Le 19/09/2016 à 11:58, Enrico Forestieri a écrit :
commit d0f608d28ebeabadc8308f408f2a67980da8e73c
Author: Enrico Forestieri
Date: Mon Sep 19 11:57:39 2016 +0200
Document the new behaviour in mathed
---
lib/RELEASE-NOTES | 12 +---
1 files changed, 9 insertions(+), 3 deletions(
On 29.08.2016 17:57, Guillaume Munch wrote:
The command:
command-alternative[s] master-buffer-view; buffer-view
does what you want.
Is there a reason why the work area is focus on the current cursor
position with this command? This is not the case with the other view
commands.
Daniel
Le 29/08/2016 à 16:05, Richard Heck a écrit :
Or just modify the bindings to use what's above.
+1
r own anyway. So I would like to remove the
View button from my interface. Unfortunately, the View master document
button is grayed out if there are no child documents in a "master". Is
that on purpose? Why not enable it anyway? So one normally presses one
and the same button and only for th
their own anyway. So I would like to remove the View button
>>> from my interface. Unfortunately, the View master document button is
>>> grayed out if there are no child documents in a "master". Is that on
>>> purpose? Why not enable it anyway? So one norma
ke to remove the View button
from my interface. Unfortunately, the View master document button is
grayed out if there are no child documents in a "master". Is that on
purpose? Why not enable it anyway? So one normally presses one and the
same button and only for the extraordinary circumstan
On 29.08.2016 17:57, Guillaume Munch wrote:
Le 29/08/2016 à 11:22, racoon a écrit :
Hi,
I almost never View child documents. Most of the time they don't compile
properly on their own anyway. So I would like to remove the View button
from my interface. Unfortunately, the View master doc
gt; properly on their own anyway. So I would like to remove the View button
>>> from my interface. Unfortunately, the View master document button is
>>> grayed out if there are no child documents in a "master". Is that on
>>> purpose? Why not enable it anyway? So
Le 29/08/2016 à 16:57, Guillaume Munch a écrit :
Le 29/08/2016 à 11:22, racoon a écrit :
Hi,
I almost never View child documents. Most of the time they don't compile
properly on their own anyway. So I would like to remove the View button
from my interface. Unfortunately, the View m
Le 29/08/2016 à 11:22, racoon a écrit :
Hi,
I almost never View child documents. Most of the time they don't compile
properly on their own anyway. So I would like to remove the View button
from my interface. Unfortunately, the View master document button is
grayed out if there are no
View button from my interface. Unfortunately, the View master document
button is grayed out if there are no child documents in a "master". Is
that on purpose? Why not enable it anyway? So one normally presses one
and the same button and only for the extraordinary circumstance of
viewing a
On 29.08.2016 14:28, Michael Berger wrote:
Are you sure to have understood the concept of master-child?
I thought so. But maybe I haven't. But what makes you think I haven't?
Daniel
ately, the View master document
button is grayed out if there are no child documents in a "master". Is
that on purpose? Why not enable it anyway? So one normally presses one
and the same button and only for the extraordinary circumstance of
viewing a child document has to press another button.
Daniel
Hi,
I almost never View child documents. Most of the time they don't compile
properly on their own anyway. So I would like to remove the View button
from my interface. Unfortunately, the View master document button is
grayed out if there are no child documents in a "master&qu
On Tuesday, July 12, 2016 10:57:05 AM WEST Richard Heck wrote:
> There was some discussion of this last cycle, too, and I think everyone
> generally thinks it is a good idea. Exactly how to do it is less clear.
> I had thought about having, for each format change, test files that
> could be used to
Richard Heck wrote:
> commit e57889ff2f38ed8e804a7e3c7e62114e31bf7715
> Author: Richard Heck
> Date: Tue Jul 12 00:20:27 2016 -0400
>
> Document new inverted branch insets in User Guide. Also add note to
> RELEASE_NOTES.
https://wiki.lyx.org/LyX/NewInLyX23 :)
On 07/12/2016 05:31 AM, José Abílio Matos wrote:
> On Tuesday, July 12, 2016 6:20:38 AM WEST Richard Heck wrote:
>> commit e57889ff2f38ed8e804a7e3c7e62114e31bf7715
>> Author: Richard Heck
>> Date: Tue Jul 12 00:20:27 2016 -0400
>>
>> Document new inverted branch insets in User Guide. Also ad
On Tuesday, July 12, 2016 6:20:38 AM WEST Richard Heck wrote:
> commit e57889ff2f38ed8e804a7e3c7e62114e31bf7715
> Author: Richard Heck
> Date: Tue Jul 12 00:20:27 2016 -0400
>
> Document new inverted branch insets in User Guide. Also add note to
> RELEASE_NOTES.
Since we are at the beg
On Sat, Nov 28, 2015 at 02:57:49PM +0100, Kornel Benko wrote:
> Am Samstag, 28. November 2015 um 14:44:13, schrieb Georg Baum
>
> > OK to go in?
>
> IMHO yes. It are new tests only. I will look for inversion of
> export/export/languagenesting1_lyx16
Yes I agree. I think that any code that onl
Am Samstag, 28. November 2015 um 14:44:13, schrieb Georg Baum
> Finally I have the first version. It works fine, except for the inversion of
> export/export/languagenesting1_lyx16, which is somehow not recognized.
> However, this is a lyx2lyx bug which I'll try to fix soon, so I don't care
It
Am Samstag, 28. November 2015 um 14:44:13, schrieb Georg Baum
> Georg Baum wrote:
>
> > Kornel Benko wrote:
> >
> >> It is now possible.
> >> All the tests there will be labeled by 'autotests' (additionally to label
> >> 'export').
> >
> > Thank you very much! Then I'll use that (may take some
Georg Baum wrote:
> Kornel Benko wrote:
>
>> It is now possible.
>> All the tests there will be labeled by 'autotests' (additionally to label
>> 'export').
>
> Thank you very much! Then I'll use that (may take some days though).
Finally I have the first version. It works fine, except for the in
Guenter Milde wrote:
> On 2015-11-22, Georg Baum wrote:
>
>> 1) lib/tests/ (or any new directory not at top level) just for new
>> dedicated export tests (will cause problems in cmake if other tests than
>> export tests are added)
>
> Don't like this, as binary LyX packages (*.deb, *.rpm) should
Kornel Benko wrote:
> Am Sonntag, 22. November 2015 um 19:22:42, schrieb Georg Baum
>
>
>> 2)
>> - autotests/export/ for export tests (does not work with the current
>> test
>> machinery)
>
> It is now possible.
> All the tests there will be labeled by 'autotests' (additionally to label
> '
On 2015-11-21, Kornel Benko wrote:
> Am Samstag, 21. November 2015 um 22:21:59, schrieb Guenter Milde
>
...
>> >> >> >> ATM, the line reads
>> >> >> >> 'foreach(libsubfolderx lib/doc lib/examples lib/templates)'
>> The idea was to put the test code not under lib (reserved for files that
>> sho
On 2015-11-22, Georg Baum wrote:
> Guenter Milde wrote:
>> On 2015-11-21, Kornel Benko wrote:
>>> Am Samstag, 21. November 2015 um 10:27:36, schrieb Georg Baum
>>>
I still think it is a good idea to follow the KDE standard here (see
above), and put all dedicated tests that can be run aut
Am Sonntag, 22. November 2015 um 19:22:42, schrieb Georg Baum
> Guenter Milde wrote:
>
> > On 2015-11-21, Kornel Benko wrote:
> >> Am Samstag, 21. November 2015 um 10:27:36, schrieb Georg Baum
> >>
> >>> I still think it is a good idea to follow the KDE standard here (see
> >>> above), and put
Guenter Milde wrote:
> On 2015-11-21, Kornel Benko wrote:
>> Am Samstag, 21. November 2015 um 10:27:36, schrieb Georg Baum
>>
>>> I still think it is a good idea to follow the KDE standard here (see
>>> above), and put all dedicated tests that can be run automatically
>>> unter top level autotest
Am Samstag, 21. November 2015 um 22:21:59, schrieb Guenter Milde
> On 2015-11-21, Kornel Benko wrote:
> > Am Samstag, 21. November 2015 um 10:27:36, schrieb Georg Baum
> >
> >> Kornel Benko wrote:
> >> > Am Freitag, 20. November 2015 um 21:23:07, schrieb Georg Baum
>
> >> >> >> > I created a n
On 2015-11-21, Kornel Benko wrote:
> Am Samstag, 21. November 2015 um 10:27:36, schrieb Georg Baum
>
>> Kornel Benko wrote:
>> > Am Freitag, 20. November 2015 um 21:23:07, schrieb Georg Baum
>> >> >> > I created a new file autotests/export/languagenesting1.lyx and tried
>> >> >> > to add autotes
Am Samstag, 21. November 2015 um 10:27:36, schrieb Georg Baum
> Kornel Benko wrote:
>
> > Am Freitag, 20. November 2015 um 21:23:07, schrieb Georg Baum
> >
> >> Kornel Benko wrote:
> >>
> >> > Am Mittwoch, 18. November 2015 um 22:35:09, schrieb Kornel Benko
> >> >
> >> >> Am Mittwoch, 18. Nov
Kornel Benko wrote:
> Am Freitag, 20. November 2015 um 21:23:07, schrieb Georg Baum
>
>> Kornel Benko wrote:
>>
>> > Am Mittwoch, 18. November 2015 um 22:35:09, schrieb Kornel Benko
>> >
>> >> Am Mittwoch, 18. November 2015 um 21:50:45, schrieb Georg Baum
>> >>
>> >>
>> >> > I created a new f
Am Donnerstag, 5. November 2015 um 21:37:11, schrieb Georg Baum
> Guenter Milde wrote:
>
> > Agreed. OTOH, I would prefer to have tests separated from src/, so maybe
> >
> > lib/
> > src/
> > tests/
> > unittests/
> > export-tests/
> > functional/
> > tests-scripts
> > input/
>
Am Freitag, 20. November 2015 um 21:23:07, schrieb Georg Baum
> Kornel Benko wrote:
>
> > Am Mittwoch, 18. November 2015 um 22:35:09, schrieb Kornel Benko
> >
> >> Am Mittwoch, 18. November 2015 um 21:50:45, schrieb Georg Baum
> >>
> >>
> >> > I created a new file autotests/export/languagenes
Kornel Benko wrote:
> Am Mittwoch, 18. November 2015 um 22:35:09, schrieb Kornel Benko
>
>> Am Mittwoch, 18. November 2015 um 21:50:45, schrieb Georg Baum
>>
>>
>> > I created a new file autotests/export/languagenesting1.lyx and tried to
>> > add autotests/export to the list, but it did not wor
Am Mittwoch, 18. November 2015 um 22:35:09, schrieb Kornel Benko
> Am Mittwoch, 18. November 2015 um 21:50:45, schrieb Georg Baum
>
> > Kornel Benko wrote:
> >
> > > Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum
> > >>
> > >> Therefore I would like to create some specific te
Am Mittwoch, 18. November 2015 um 21:50:45, schrieb Georg Baum
> Kornel Benko wrote:
>
> > Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum
> >>
> >> Therefore I would like to create some specific test cases for language
> >> nesting. Pure export tests would be fine for now, we c
Kornel Benko wrote:
> Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum
>>
>> Therefore I would like to create some specific test cases for language
>> nesting. Pure export tests would be fine for now, we could still add a
>> comparison of the exported .tex later. With these tests i
Guenter Milde wrote:
> Agreed. OTOH, I would prefer to have tests separated from src/, so maybe
>
> lib/
> src/
> tests/
> unittests/
> export-tests/
> functional/
> tests-scripts
> input/
> expected/ # expected output
> output/ # just a dir for the output, no content
On Thu, Nov 5, 2015 at 8:27 AM, Guenter Milde wrote:
> On 2015-11-04, Georg Baum wrote:
>> Guenter Milde wrote:
>
>>> On 2015-10-30, Georg Baum wrote:
Kornel Benko wrote:
>
These directories are clearly not suitable for pure test files, so I'll
need to add a new one. Would lib/tests
On 2015-11-04, Georg Baum wrote:
> Guenter Milde wrote:
>> On 2015-10-30, Georg Baum wrote:
>>> Kornel Benko wrote:
>>> These directories are clearly not suitable for pure test files, so I'll
>>> need to add a new one. Would lib/tests be OK?
>> If you use such a generic name, it should have sub-
Guenter Milde wrote:
> On 2015-10-30, Georg Baum wrote:
>> Kornel Benko wrote:
>
>> These directories are clearly not suitable for pure test files, so I'll
>> need to add a new one. Would lib/tests be OK?
>
> If you use such a generic name, it should have sub-directories for
>
> * unittests
un
Am Freitag, 30. Oktober 2015 um 22:54:43, schrieb Guenter Milde
> On 2015-10-30, Georg Baum wrote:
> > Kornel Benko wrote:
>
> >> This is easy, just add them in one of the scanned directories.
> >> To activate, rerun the configuration part (cmake .)
>
> >> After this they are accessible wit
Am Freitag, 30. Oktober 2015 um 23:30:46, schrieb Georg Baum
> Kornel Benko wrote:
>
> > Am Freitag, 30. Oktober 2015 um 22:33:14, schrieb Georg Baum
> >
> >> Scott Kostyshak wrote:
> >>
> >> > Would another approach be to add a label? You can see the current
> >> > labels we have with:
> >> >
On 2015-10-30, Georg Baum wrote:
> Kornel Benko wrote:
>> This is easy, just add them in one of the scanned directories.
>> To activate, rerun the configuration part (cmake .)
>> After this they are accessible with e.g.
>> ctest -R
>> The scanned directories (and subdirectories) are ATM
>>
Kornel Benko wrote:
> Am Freitag, 30. Oktober 2015 um 22:33:14, schrieb Georg Baum
>
>> Scott Kostyshak wrote:
>>
>> > Would another approach be to add a label? You can see the current
>> > labels we have with:
>> >
>> > ctest --print-labels
>>
>> Since we'll need a new directory anyway (I d
Am Freitag, 30. Oktober 2015 um 22:31:41, schrieb Georg Baum
> Kornel Benko wrote:
>
> > This is easy, just add them in one of the scanned directories.
> > To activate, rerun the configuration part (cmake .)
> >
> > After this they are accessible with e.g.
> > ctest -R
> >
> > The scanned
Am Freitag, 30. Oktober 2015 um 22:33:14, schrieb Georg Baum
> Scott Kostyshak wrote:
>
> > Would another approach be to add a label? You can see the current labels
> > we have with:
> >
> > ctest --print-labels
>
> Since we'll need a new directory anyway (I don't think that pure test files
Kornel Benko wrote:
> This is easy, just add them in one of the scanned directories.
> To activate, rerun the configuration part (cmake .)
>
> After this they are accessible with e.g.
> ctest -R
>
> The scanned directories (and subdirectories) are ATM
> lib/doc, lib/examples, lib/templates
Scott Kostyshak wrote:
> Would another approach be to add a label? You can see the current labels
> we have with:
>
> ctest --print-labels
Since we'll need a new directory anyway (I don't think that pure test files
which are not installed should show up in any of the listed directories, we
d
On Thu, Oct 29, 2015 at 11:42:58PM +0100, Kornel Benko wrote:
> Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum
>
> > Scott Kostyshak wrote:
> >
> > > Please let me know if there is anything else specifically that I should
> > > document regarding the export tests. I will try to
Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum
> Scott Kostyshak wrote:
>
> > Please let me know if there is anything else specifically that I should
> > document regarding the export tests. I will try to keep updating this
> > file.
>
> Very good! I have one question: While in
Scott Kostyshak wrote:
> Please let me know if there is anything else specifically that I should
> document regarding the export tests. I will try to keep updating this
> file.
Very good! I have one question: While investigating the language nesting
stuff further I found already a nesting bug wh
On Thu, Oct 29, 2015 at 07:30:04AM +0100, Scott Kostyshak wrote:
> commit 74059f6b5600c92166e66e9b6b78eda2b7b93331
> Author: Scott Kostyshak
> Date: Thu Oct 29 02:24:20 2015 -0400
>
> Document the export tests and other tests
>
> The export tests, check_load tests, and URL tests ar
I find the term "Master document" in the Settings tab of Advanced Find,
to be an unintuitive name. The tooltip does, however, clarify things.
To me, "Master document" implies that only the master document is
searched, not the children.
I have trouble thinking of a short n
Am Montag, 20. April 2015 um 18:31:10, schrieb Juergen Spitzmueller
> \author -712698321 "Jürgen Spitzmüller"
> \author -195340706 "Georg Baum"
> +\author 155139281 "Jrgen Spitzmller"
>
What happened with your name?
Kornel
signature.asc
Description: This is a digitally signed mes
Uwe Stöhr wrote:
> thanks for the description of the different paste modes. But as I need to
> update the other languages accordingly, please use change tracking.
No problem, I'll do that next time. Is that documented somewhere? I vaguely
remember that I used to use change tracking for manuals,
Am 05.02.2014 21:53, schrieb Georg Baum:
commit ac2c91be02c0cf4129cce8ba1ae0aca130b8bea8
Author: Georg Baum
Date: Wed Feb 5 21:50:33 2014 +0100
Hi Georg,
thanks for the description of the different paste modes. But as I need to update the other languages
accordingly, please use change tra
01/09/2013 20:17, Vincent van Ravesteijn:
Vincent, can I commit this somewhere?
JMarc
I put it in.
Thanks!
JMarc
Op 17-7-2013 11:25, Jean-Marc Lasgouttes schreef:
Le 16/07/2013 06:48, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
OK, let's keep it as it is right now. Shall I commit it somewhere
now or
wait?
I would put it into master. P
Vincent, can I commit this somewhere?
JMarc
I put it in.
Le 16/07/2013 06:48, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
OK, let's keep it as it is right now. Shall I commit it somewhere now or
wait?
I would put it into master. P
Vincent, can I commit this somewhere?
JMarc
1 - 100 of 165 matches
Mail list logo
