Am Sonntag, dem 02.06.2024 um 14:44 +0200 schrieb Kornel Benko:
> If 2.4.x will become 2.4.1, what happens with 2.4.1~devel?
2.4.2, I suppose. But only in case we need an emergency release.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
Le 02/06/2024 à 15:18, Jean-Marc Lasgouttes a écrit :
Le 02/06/2024 à 14:44, Kornel Benko a écrit :
This is very confusing.
If 2.4.x will become 2.4.1, what happens with 2.4.1~devel?
It will go to 2.4.2.
The 2.4.1-devel branch is "next stable release which is not an emergency
release".
JM
Le 02/06/2024 à 14:44, Kornel Benko a écrit :
This is very confusing.
If 2.4.x will become 2.4.1, what happens with 2.4.1~devel?
It will go to 2.4.2.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Thu, 30 May 2024 12:17:15 -0400
schrieb Richard Kimberly Heck :
> On 5/30/24 02:46, Jürgen Spitzmüller wrote:
> > Am Mittwoch, dem 29.05.2024 um 14:50 + schrieb Richard Kimberly
> > Heck:
> >> commit e80fdf38e4dc095316547371d22284676e2e6c7d
> >> Author:
On 5/30/24 02:46, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 29.05.2024 um 14:50 + schrieb Richard Kimberly
Heck:
commit e80fdf38e4dc095316547371d22284676e2e6c7d
Author: Richard Kimberly Heck
Date: Wed May 29 10:49:58 2024 -0400
New status file, and status for last commit
What is
Am Mittwoch, dem 29.05.2024 um 14:50 + schrieb Richard Kimberly
Heck:
> commit e80fdf38e4dc095316547371d22284676e2e6c7d
> Author: Richard Kimberly Heck
> Date: Wed May 29 10:49:58 2024 -0400
>
> New status file, and status for last commit
What is the relation of this
On Tue, Feb 13, 2024 at 05:05:03PM +0100, Jean-Pierre Chrétien wrote:
> Then I run 'git commit' and 'git pv' to rebase before push, and here is your
> warning in English :
>
Do I get correctly that you run LyX session and git commands from the same
terminal?
It loo
not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: lib/doc/fr/Intro.lyx
When I run git add lib/doc/fr/Intro.lyx
Changes to be committed:
(use "g
On Mon, Feb 12, 2024 at 04:56:40PM +0100, Jean-Pierre Chrétien wrote:
> which means :
I prefer english messages in verbatin so I can google them :)
Anyway, what "git status" returns?
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Mon, Feb 12, 2024 at 05:01:32PM +0100, Jean-Pierre Chrétien wrote:
> >>>BTW, I will update the reference of the documentation in trac with
> >>>https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD
> >>
> >>Where exactly in the trac do you want to make that change?
> >
> >Here :
> >
> >
Here I change the subject for what concerns th change from trac to git.lyx.org.
Sorry if it is not the correct procedure.
Would it be better located in lyx-docs ? I understood that cross-posting is not
a good practice.
Le 12/02/2024 à 16:45, Jean-Pierre Chrétien a écrit :
BTW, I will update
Le 12/02/2024 à 13:31, Pavel Sanda a écrit :
Isn't it possible that you just had 2 lyx windows opened on the same file?
Or commited changes from different computer?
No, none of these possibilities. I run all lyx-related stuff from my Debian
bookworm box.
Here is the message in French :
$
Le 12/02/2024 à 13:37, Pavel Sanda a écrit :
On Mon, Feb 12, 2024 at 11:02:07AM +0100, Jean-Pierre Chrétien wrote:
Since the update of the git server (thanks a lot, Pavel!), I get a message
telling me that the file pending to be committed has been erased on my disk.
Happily this is not true, but
> >>>On Mon, Feb 12, 2024 at 11:02:07AM +0100, Jean-Pierre Chrétien wrote:
> Since the update of the git server (thanks a lot, Pavel!), I get a message
> telling me that the file pending to be committed has been erased on my
> disk.
> Happily this is not true, but a bit disturbing.
On Mon, Feb 12, 2024 at 11:12:28AM +0100, Jean-Pierre Chrétien wrote:
> Le 12/02/2024 ?? 11:02, Jean-Pierre Chrétien a écrit :
> >Dear developers
> >
> >Since the update of the git server (thanks a lot, Pavel!), I get a message
> >telling me that the file pending to be committed has been erased on
message
telling me that the file pending to be committed has been erased on my disk.
Happily this is not true, but a bit disturbing.
Disturbing indeed.
Can you send me the exact error message, possibly in english?
OK, I will retry a commit with my locale on C.
Alas, no message when I committed
has been erased on my disk.
Happily this is not true, but a bit disturbing.
Disturbing indeed.
Can you send me the exact error message, possibly in english?
OK, I will retry a commit with my locale on C.
Alas, no message when I committed a small change in French Intro.lyx, but there
were no
, but a bit disturbing.
Disturbing indeed.
Can you send me the exact error message, possibly in english?
OK, I will retry a commit with my locale on C.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Le 12/02/2024 à 11:02, Jean-Pierre Chrétien a écrit :
Dear developers
Since the update of the git server (thanks a lot, Pavel!), I get a message
telling me that the file pending to be committed has been erased on my disk.
Happily this is not true, but a bit disturbing.
As I had the file sill
On Mon, Feb 12, 2024 at 11:02:07AM +0100, Jean-Pierre Chrétien wrote:
> Since the update of the git server (thanks a lot, Pavel!), I get a message
> telling me that the file pending to be committed has been erased on my disk.
> Happily this is not true, but a bit disturbing.
Disturbing indeed.
Can
Dear developers
Since the update of the git server (thanks a lot, Pavel!), I get a message
telling me that the file pending to be committed has been erased on my disk.
Happily this is not true, but a bit disturbing.
Do you see this ?
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.ly
On Fri, Aug 25, 2023 at 11:47:13AM -0400, Richard Kimberly Heck wrote:
> On 8/25/23 10:31, Scott Kostyshak wrote:
> > On Fri, Aug 25, 2023 at 10:24:42AM -0400, Scott Kostyshak wrote:
> > > On Ubuntu 23.04 I now get an error without the following commi
On 8/25/23 10:31, Scott Kostyshak wrote:
On Fri, Aug 25, 2023 at 10:24:42AM -0400, Scott Kostyshak wrote:
On Ubuntu 23.04 I now get an error without the following commit in master:
9715d3504c6a74f9a498e2d9232956255110225d
Here's the error:
cd /home/scott/lyxbuilds/2.3.x/CMakeBuild/po &a
On Fri, Aug 25, 2023 at 10:24:42AM -0400, Scott Kostyshak wrote:
> On Ubuntu 23.04 I now get an error without the following commit in master:
> 9715d3504c6a74f9a498e2d9232956255110225d
>
> Here's the error:
>
> cd /home/scott/lyxbuilds/2.3.x/CMakeBuild/po &&
On Ubuntu 23.04 I now get an error without the following commit in master:
9715d3504c6a74f9a498e2d9232956255110225d
Here's the error:
cd /home/scott/lyxbuilds/2.3.x/CMakeBuild/po && /usr/bin/python3
/home/scott/lyxbuilds/2.3.x/repo/development/cmake/po/cat.py
/home/scott/ly
Le 13/06/2023 à 10:39, Scott Kostyshak a écrit :
I personally like to see a description in the first line of a Git commit
message. e.g., instead of "Fix #", I'd prefer to see "Fix crash when
exporting long docs". If the ticket number can be appended, and the line
is
I personally like to see a description in the first line of a Git commit
message. e.g., instead of "Fix #", I'd prefer to see "Fix crash when
exporting long docs". If the ticket number can be appended, and the line
is still under 52 characters, great. If not, I t
On Sun, Jan 29, 2023 at 09:49:09AM +0100, Jürgen Spitzmüller wrote:
> Am Samstag, dem 28.01.2023 um 14:28 -0500 schrieb Scott Kostyshak:
> > The following tests just started to fail:
> >
> > 3581 -
> > export/examples/Articles/Astronomy_%26_Astrophysics_lyx22 (Failed)
> > 3582 -
>
Am Samstag, dem 28.01.2023 um 14:28 -0500 schrieb Scott Kostyshak:
> The following tests just started to fail:
>
> 3581 -
> export/examples/Articles/Astronomy_%26_Astrophysics_lyx22 (Failed)
> 3582 -
> export/examples/Articles/Astronomy_%26_Astrophysics_lyx23 (Failed)
> 633
The following tests just started to fail:
3581 - export/examples/Articles/Astronomy_%26_Astrophysics_lyx22
(Failed)
3582 - export/examples/Articles/Astronomy_%26_Astrophysics_lyx23
(Failed)
6336 - export/templates/Articles/Astronomy_%26_Astrophysics_lyx22
(Failed)
On Mon, Dec 19, 2022 at 10:08:08AM +0100, Kornel Benko wrote:
> Am Mon, 19 Dec 2022 08:02:30 +0100
> schrieb "Jürgen Spitzmüller" :
>
> > Am Sonntag, dem 18.12.2022 um 16:03 -0500 schrieb Scott Kostyshak:
> > > The following ctest now fails:
> > >
> > > DEFAULTOUTPUT_export/export/latex/CJK/zh_
On Mon, Dec 19, 2022 at 08:02:30AM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 18.12.2022 um 16:03 -0500 schrieb Scott Kostyshak:
> > The following ctest now fails:
> >
> > DEFAULTOUTPUT_export/export/latex/CJK/zh_CN-en-de-el-ru_language-
> > default_pdf2
>
> Should be fixed.
Thanks for
On Mon, Dec 19, 2022 at 12:04:44PM +0100, Daniel wrote:
> I am surprised there is a beta1. There is none here:
>
> https://ftp.lip6.fr/pub/lyx/devel/lyx-2.4/
>
> Where can one download it?
Well, it never really took off, except of brief tarball availibility on
google drive which is no more there
On 2022-12-10 14:52, Scott Kostyshak wrote:
On Sat, Dec 10, 2022 at 11:48:24AM +, José Matos wrote:
On Fri, 2022-12-09 at 17:11 -0500, Richard Kimberly Heck wrote:
I think it's ok myself. But we could also go ahead and produce a new
alpha. I can do that if you wish, when I do the 2.3.7 tarb
Am Mon, 19 Dec 2022 08:02:30 +0100
schrieb "Jürgen Spitzmüller" :
> Am Sonntag, dem 18.12.2022 um 16:03 -0500 schrieb Scott Kostyshak:
> > The following ctest now fails:
> >
> > DEFAULTOUTPUT_export/export/latex/CJK/zh_CN-en-de-el-ru_language-
> > default_pdf2
>
> Should be fixed.
>
Test p
Am Sonntag, dem 18.12.2022 um 16:03 -0500 schrieb Scott Kostyshak:
> The following ctest now fails:
>
> DEFAULTOUTPUT_export/export/latex/CJK/zh_CN-en-de-el-ru_language-
> default_pdf2
Should be fixed.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-deve
The following ctest now fails:
DEFAULTOUTPUT_export/export/latex/CJK/zh_CN-en-de-el-ru_language-default_pdf2
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sun, Dec 11, 2022 at 06:00:29PM +, José Matos wrote:
> On Fri, 2022-12-09 at 12:28 -0500, Scott Kostyshak wrote:
> > This commit used the LyX binary to write the new .lyx files since
> > lyx2lyx does not apply semantic linefeeds.
>
> This is something that needs to be
On Fri, 2022-12-09 at 12:28 -0500, Scott Kostyshak wrote:
> This commit used the LyX binary to write the new .lyx files since
> lyx2lyx does not apply semantic linefeeds.
This is something that needs to be done. It is not high priority but it
should be done to keep to output of lyx2lyx as s
On Sat, Dec 10, 2022 at 12:08:55AM -0500, Scott Kostyshak wrote:
> On Fri, Dec 09, 2022 at 05:11:28PM -0500, Richard Kimberly Heck wrote:
> > On 12/9/22 14:40, Scott Kostyshak wrote:
> > > On Fri, Dec 09, 2022 at 07:19:37PM +0100, Pavel Sanda wrote:
> > > > On Fri, Dec 09, 2022 at 12:28:41PM -0500,
On Sat, Dec 10, 2022 at 11:48:24AM +, José Matos wrote:
> On Fri, 2022-12-09 at 17:11 -0500, Richard Kimberly Heck wrote:
> > I think it's ok myself. But we could also go ahead and produce a new
> > alpha. I can do that if you wish, when I do the 2.3.7 tarball this
> > weekend.
> >
> > Riki
>
On Fri, 2022-12-09 at 17:11 -0500, Richard Kimberly Heck wrote:
> I think it's ok myself. But we could also go ahead and produce a new
> alpha. I can do that if you wish, when I do the 2.3.7 tarball this
> weekend.
>
> Riki
If you do this (for 2.4) please call it beta-2 since we already have a
b
On Fri, Dec 09, 2022 at 05:11:28PM -0500, Richard Kimberly Heck wrote:
> On 12/9/22 14:40, Scott Kostyshak wrote:
> > On Fri, Dec 09, 2022 at 07:19:37PM +0100, Pavel Sanda wrote:
> > > On Fri, Dec 09, 2022 at 12:28:41PM -0500, Scott Kostyshak wrote:
> > > > OK to push?
> > > I'm not happy about upd
On 12/9/22 14:40, Scott Kostyshak wrote:
On Fri, Dec 09, 2022 at 07:19:37PM +0100, Pavel Sanda wrote:
On Fri, Dec 09, 2022 at 12:28:41PM -0500, Scott Kostyshak wrote:
OK to push?
I'm not happy about updating Additional.lyx as John doesn't have
up-to-date lyx binary and will stop him from updat
On Fri, Dec 09, 2022 at 07:19:37PM +0100, Pavel Sanda wrote:
> On Fri, Dec 09, 2022 at 12:28:41PM -0500, Scott Kostyshak wrote:
> > OK to push?
>
> I'm not happy about updating Additional.lyx as John doesn't have
> up-to-date lyx binary and will stop him from updates.
Makes sense. I'll exclude Ad
On Fri, Dec 09, 2022 at 12:28:41PM -0500, Scott Kostyshak wrote:
> OK to push?
I'm not happy about updating Additional.lyx as John doesn't have
up-to-date lyx binary and will stop him from updates.
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-
I wanted to check before pushing the commit, because even if I revert
that will be a non-trivial weight in the commit history.
Here is the commit message:
---
Update format of docs using LyX binary
Especially after the change to use semantic linefeeds
On Mon, Aug 01, 2022 at 06:18:53PM +0200, Jean-Pierre Chrétien wrote:
> >>$ git log
> >>commit 4c72d8aeac01c53e27732999108f249356e67c5c (HEAD -> master,
> >>origin/master,
> >>origin/HEAD)
...
> What bugs me is the (HEAD -> master, origin/mast
ess, but I see in the log that there is something fishy:
$ git log
commit 4c72d8aeac01c53e27732999108f249356e67c5c (HEAD -> master, origin/master,
origin/HEAD)
Author: jpc
Date: Sun Jul 31 18:28:23 2022 +0200
Info in French UserGuide
commit c04192526187c1b3bfe7d7dcabd9cd6c50
log that there is something fishy:
>
>
> $ git log
> commit 4c72d8aeac01c53e27732999108f249356e67c5c (HEAD -> master,
> origin/master,
> origin/HEAD)
> Author: jpc
> Date: Sun Jul 31 18:28:23 2022 +0200
>
> Info in French UserGuide
>
> co
Dear Developers,
While committing a very minor change in the French UserGuide, I had a warning
about the fact that I was in "Detached HEAD mode".
I committed nevertheless, but I see in the log that there is something fishy:
$ git log
commit 4c72d8aeac01c53e27732999108f249356e6
Le 12/03/2022 à 12:28, Kornel Benko a écrit :
Deserves an entry in ctests-costs-benefits.txt IMO.
Indeed it does. This bug would have been identified sooner or later, but
sooner is definitely better.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinf
sgouttes :
> > >
> > > > Le 10/03/2022 à 14:17, Scott Kostyshak a écrit :
> > > > > I just compiled current master and the following now fails:
> > > > >
> > > > > ctest -R "examples/Welcome_pdf2"
> > > >
gt; > > > I just compiled current master and the following now fails:
> > > >
> > > >ctest -R "examples/Welcome_pdf2"
> > > >
> > > > I'm guessing it's because of a recent commit in the last day.
> > >
>
>
> > >ctest -R "examples/Welcome_pdf2"
> > >
> > > I'm guessing it's because of a recent commit in the last day.
> >
> > I amended my commit from today, tell me whether it is fine now.
> >
> > JMarc
> >
>
> Much
Am Thu, 10 Mar 2022 18:23:38 +0100
schrieb Jean-Marc Lasgouttes :
> Le 10/03/2022 à 18:05, Kornel Benko a écrit :
> >> I knew it would not be correct on the first try, but it was not that far.
> >
> > Nonetheless great job. I have seen that the latex output was missing
> > '\usepakage{graphicx}
Le 10/03/2022 à 18:05, Kornel Benko a écrit :
I knew it would not be correct on the first try, but it was not that far.
Nonetheless great job. I have seen that the latex output was missing
'\usepakage{graphicx}' but was unable to see why.
validate() is something I know much better than the la
gt; I just compiled current master and the following now fails:
> >>>
> >>> ctest -R "examples/Welcome_pdf2"
> >>>
> >>> I'm guessing it's because of a recent commit in the last day.
> >>
> >> I amende
's because of a recent commit in the last day.
I amended my commit from today, tell me whether it is fine now.
JMarc
Much better. No errors for Welcome tests
$ ctest -R Welcome
100% tests passed, 0 tests failed out of 534
I knew it would not be correct on the first try, but
Am Thu, 10 Mar 2022 17:13:38 +0100
schrieb Jean-Marc Lasgouttes :
> Le 10/03/2022 à 14:17, Scott Kostyshak a écrit :
> > I just compiled current master and the following now fails:
> >
> >ctest -R "examples/Welcome_pdf2"
> >
> > I'm guessing
Le 10/03/2022 à 14:17, Scott Kostyshak a écrit :
I just compiled current master and the following now fails:
ctest -R "examples/Welcome_pdf2"
I'm guessing it's because of a recent commit in the last day.
I amended my commit from today, tell me whether it is fine no
Le 10/03/2022 à 14:17, Scott Kostyshak a écrit :
I just compiled current master and the following now fails:
ctest -R "examples/Welcome_pdf2"
I'm guessing it's because of a recent commit in the last day.
That would be my InsetInfo patch from today. I did try com
Am Thu, 10 Mar 2022 08:17:06 -0500
schrieb Scott Kostyshak :
> I just compiled current master and the following now fails:
>
> ctest -R "examples/Welcome_pdf2"
>
> I'm guessing it's because of a recent commit in the last day.
>
> Command-line export
I just compiled current master and the following now fails:
ctest -R "examples/Welcome_pdf2"
I'm guessing it's because of a recent commit in the last day.
Command-line export shows the following:
$ lyx master -e pdf2 Welcome.lyx
This is pdfTeX, Version 3.141592653-2.6-1.
gt; >
>>> > >> The attached example file used to compile to PDF a couple of days
>>> ago.
>>> > >>
>>> > >
>>> > > Bisect says:
>>> > > [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse
>>> > > supplem
>>
>> > >
>> > > Bisect says:
>> > > [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse
>> > > supplementary lines to encode alternative ways to encode symbols in
>> raw
>> > > LaTeX.
>> > >
>> >
c] unicodesymbols: parse
> > > supplementary lines to encode alternative ways to encode symbols in raw
> > > LaTeX.
> > >
> >
> > It's probably rather 3f9e21b82692, for that matter.
>
> CC'ing Thibaut.
>
Indeed, it's probably due to a recent commit of mine. I'll have a look,
tentatively tomorrow.
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Tue, Feb 22, 2022 at 11:43:23AM +0100, Jürgen Spitzmüller wrote:
> Am Di., 22. Feb. 2022 um 10:48 Uhr schrieb Jürgen Spitzmüller >:
>
> > Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak <
> > skost...@lyx.org>:
> >
> >> The attached example file used to compile to PDF a couple of da
Am Di., 22. Feb. 2022 um 10:48 Uhr schrieb Jürgen Spitzmüller :
> Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak <
> skost...@lyx.org>:
>
>> The attached example file used to compile to PDF a couple of days ago.
>>
>
> Bisect says:
> [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesy
Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak :
> The attached example file used to compile to PDF a couple of days ago.
>
Bisect says:
[0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse
supplementary lines to encode alternative ways to encode symbols in raw
LaTeX.
Jür
Am Di., 22. Feb. 2022 um 10:40 Uhr schrieb Kornel Benko :
> Am Mon, 21 Feb 2022 22:54:55 -0500
> schrieb Scott Kostyshak :
>
> > The attached example file used to compile to PDF a couple of days ago.
> >
> > Scott
>
> Using utf-8 encoding (by setting non-text-fonts) cures it.
> Works also if using
Am Mon, 21 Feb 2022 22:54:55 -0500
schrieb Scott Kostyshak :
> The attached example file used to compile to PDF a couple of days ago.
>
> Scott
Using utf-8 encoding (by setting non-text-fonts) cures it.
Works also if using
Document->Settings...->Language->Encoding->Unicode(utf8)
The attached example file used to compile to PDF a couple of days ago.
Scott
uncodable-dash-example.23.lyx
Description: application/lyx
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 8/17/20 1:35 AM, Jürgen Spitzmüller wrote:
> Am Sonntag, den 16.08.2020, 21:26 +0100 schrieb José Abílio Matos:
>> What is wrong with
>>
>> pos_type ipos = min(cur.pos(), cell(i).size());
>>
>> it expresses intent better than the other code, no? :-)
> This was my first choice, too. However,
Am 17.08.2020 um 13:30 schrieb Jürgen Spitzmüller :
>
> Am Montag, den 17.08.2020, 08:38 +0100 schrieb José Abílio Matos:
>> pos_type ipos = min(cur.pos(), pos_type(cell(i).size()));
>
> Changed on top of Stephan's fix (plus constify).
That’s better indeed. Fine.
Stephan
--
lyx-devel mailing l
Am Montag, den 17.08.2020, 08:38 +0100 schrieb José Abílio Matos:
> pos_type ipos = min(cur.pos(), pos_type(cell(i).size()));
Changed on top of Stephan's fix (plus constify).
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx
Am Montag, den 17.08.2020, 08:38 +0100 schrieb José Abílio Matos:
> OK then what about
>
> pos_type ipos = min(cur.pos(), pos_type(cell(i).size()));
Looks better.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http:
On Monday, 17 August 2020 06.35.27 WEST Jürgen Spitzmüller wrote:
> Am Sonntag, den 16.08.2020, 21:26 +0100 schrieb José Abílio Matos:
> > What is wrong with
> >
> > pos_type ipos = min(cur.pos(), cell(i).size());
> >
> > it expresses intent better than the other code, no? :-)
>
> This was my fi
Am Sonntag, den 16.08.2020, 21:29 +0200 schrieb Stephan Witt:
> This patch works with clang and avoids a type mismatch warning for
> signed vs unsigned typed values comparison.
This works for me, too. Please commit.
Jürgen
signature.asc
Description: This is a digitally signed messag
Am Sonntag, den 16.08.2020, 21:26 +0100 schrieb José Abílio Matos:
> What is wrong with
>
> pos_type ipos = min(cur.pos(), cell(i).size());
>
> it expresses intent better than the other code, no? :-)
This was my first choice, too. However, it triggers:
mathed/InsetMathGrid.cpp:1637:51: error:
On Sunday, 16 August 2020 20.29.50 WEST Stephan Witt wrote:
> This patch works with clang and avoids a type mismatch warning for signed vs
> unsigned typed values comparison.
>
> Stephan
What is wrong with
pos_type ipos = min(cur.pos(), cell(i).size());
it expresses intent better than the other
t;> error C3861: 'uint': identifier not found
>>
>> Here is my (simple) fix, in bold (formal patch attached):
>> pos_type ipos = pos_type(cur.pos()) > cell(i).size()
>> I preferred not to commit this directly, in case other compilers do not like
>> th
y (simple) fix, in bold (formal patch attached):
> pos_type ipos = pos_type(cur.pos()) > cell(i).size()
> I preferred not to commit this directly, in case other compilers do not like
> this version…
> <0001-Fix-compilation.patch>—
Why these cast at all?
cur.pos() is returning a
Hi,
I just tried to compile the latest version of the code with Visual C++.
However, it chokes on line 1637 of InsetMathGrid.cpp
<https://github.com/cburschka/lyx/commit/957b615b1fd02ca8b5d7a44c26789c1bb90afd72#diff-31a8ae53e6c07c737a4c53f70a401932>:
error C3861: 'uint': iden
On Wed, Feb 20, 2019 at 09:40:24AM +0100, Pavel Sanda wrote:
> On Tue, Feb 19, 2019 at 11:35:53PM -0500, Scott Kostyshak wrote:
> > I'm not sure when I would get to doing this, but for LyX's Git VC
> > backend, would it be OK if I added support for multi-line commit
>
On Tue, Feb 19, 2019 at 11:35:53PM -0500, Scott Kostyshak wrote:
> I'm not sure when I would get to doing this, but for LyX's Git VC
> backend, would it be OK if I added support for multi-line commit
> messages?
Sounds good.
> I could format it similar to how
I'm not sure when I would get to doing this, but for LyX's Git VC
backend, would it be OK if I added support for multi-line commit
messages?
I could format it similar to how Vim does it by default:
- Subject line should be 50 characters. The user could enter more
characters, but the
westo...@web.de
>
>
> So these commits by Alexander and Uwe were likely not sent to the list, but
> I guess you did notice the "spam" on lyx-devel..?
We did, but the purpose of this test was not clear...
The main problem is that report for each commit should be sent at most once...
Thanks,
Pavel
Hi,
Just FYI, the CI job that checks authors' email has triggered.
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/
Here's the difference:
Latest log:
cca365f26c 2018-02-15 11:28:34 -0800 name=Alexander Dunlap
email=alexander.dun...@gmail.com
c070c2f1f8 2018-0
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/50/Changes:
[spitz] tex2lyx: do not force default bibliography style if none is set
[spitz] Add literal param to InsetInclude
[spitz] Add LyX 2.3 format
[uwestoehr] ar.po: correct year
[sanda] * cs.po
[rgheck] Fix bug
On 02/25/2018 03:37 PM, Patrick De Visschere wrote:
> Commit ca4426e (bugfix #10888) broke (at least my) macos-build (qt5.10 and
> macos 10.12);
> A change from menu to menuptr in Menus.cpp escaped attention.
Thanks. QtCreator has this great ability to rename variables, but it
skips co
Commit ca4426e (bugfix #10888) broke (at least my) macos-build (qt5.10 and
macos 10.12);
A change from menu to menuptr in Menus.cpp escaped attention.
patch included.
pdv
menutomenuptr.diff
Description: Binary data
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/49/Changes:
[uwestoehr] Win installer: fix installation of Arabic dictionaries.nsh
[spitz] Adapt to new ChkTeX return values.
[spitz] Skip insets when checking for uncodable chars to paste.
[lasgouttes] Another go at
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/48/Changes:
[spitz] Fix child document regex in scanLogFile
[spitz] tex2lyx: normalize bib and bst paths
[milde] lyx2lyx fixes and cleanup.
[forenr] Avoid an infinite loop
[sanda] Cosmetics per JMarc's sugges
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/47/Changes:
[rgheck] Double escape binary regex in lyx2lyx and fix line-ending problem.
[rgheck] Double escape binary regexes in module and citeengine searches.
[rgheck] Make module and citeengine regexes a little more
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/46/Changes:
[spitz] Account for custom encoding in DocIteratior::getEncoding
[spitz] Properly communicate forced encodings
[lasgouttes] Fix embarrassing thinko (fixup 1a969fa4a61)
[sanda] * layouttranslations - update ar
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/45/Changes:
[spitz] remove unnecessary braces
[forenr] Update it.po
[rgheck] Introduce Inset::asInsetGraphics.
[spitz] Fix output of quote ligatures with TeX font LuaTeX
[milde] Fix preamble-code removal in lyx2lyx. Do
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/44/Changes:
[uwestoehr] UserGuide.lyx: distribute recent changes
[uwestoehr] de.po: update some translations
[spitz] Revert "de.po: update some translations"
[spitz] Complement the movement handling of en
https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/43/--
Started by timer
Building remotely on lyx-linux1 (linux) in workspace
<https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/ws/>
Wiping out workspace
On Wed, Jan 10, 2018 at 09:52:41AM +, Pavel Sanda wrote:
> Pavel Sanda wrote:
> > commit 8c24070c8529166f616747e966cdd9afd735ff9e
> > Author: Pavel Sanda
> > Date: Wed Jan 10 10:47:48 2018 +0100
> >
> > RCS: commit undo allowed only in unlocked state.
1 - 100 of 499 matches
Mail list logo
