On Tue, 2025-05-20 at 19:05 +0200, Enrico Forestieri wrote:
> I don't know what to do. On the one hand the attached patch solves the
> issue for me with version 1.15, but I don't have any info on the return
> codes from dvipng and it very possible that that return code (136) is
> not specific to
On Mon, May 19, 2025 at 11:39:32PM +0200, Enrico Forestieri wrote:
On Mon, May 19, 2025 at 02:44:06PM +0200, Jean-Marc Lasgouttes wrote:
Dear all,
With UserGuide, I get a lot of output concerning previews:
Warning: dvipng failed to generate images from
lyxpreviewSZhsFp.dvi... fallback to
On Mon, May 19, 2025 at 02:44:06PM +0200, Jean-Marc Lasgouttes wrote:
Dear all,
With UserGuide, I get a lot of output concerning previews:
Warning: dvipng failed to generate images from lyxpreviewSZhsFp.dvi...
fallback to legacy method
Warning: epstopdf failed on page 1, file
Dear all,
With UserGuide, I get a lot of output concerning previews:
Warning: dvipng failed to generate images from lyxpreviewSZhsFp.dvi...
fallback to legacy method
Warning: epstopdf failed on page 1, file lyxpreviewSZhsFp.001
Warning: epstopdf failed on page 2, file lyxpreviewSZhsFp.002
Using external hunspell, I see these warnings
/usr2/src/lyx/lyx-git/src/HunspellChecker.cpp:372:9: warning: 'spell' is
deprecated
[-Wdeprecated-declarations]
/usr2/src/lyx/lyx-git/src/HunspellChecker.cpp:434:35:
warning: 'suggest' is deprecated [-Wdeprecated-declarations]
/
On Sun, May 04, 2025 at 12:20:57PM +0200, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 04.05.2025 um 12:13 +0200 schrieb Scott Kostyshak:
> > I now get (with -Werror):
> >
> > /home/scott/lyxbuilds/master-
> > master/repo/src/insets/InsetRef.cpp:1005:55: error: left operand of
> > comma operator ha
Am Sonntag, dem 04.05.2025 um 12:13 +0200 schrieb Scott Kostyshak:
> I now get (with -Werror):
>
> /home/scott/lyxbuilds/master-
> master/repo/src/insets/InsetRef.cpp:1005:55: error: left operand of
> comma operator has no effect [-Werror,-Wunused-value]
> 1005 | || (cmd == "forma
I now get (with -Werror):
/home/scott/lyxbuilds/master-master/repo/src/insets/InsetRef.cpp:1005:55:
error: left operand of comma operator has no effect [-Werror,-Wunused-value]
1005 | || (cmd == "formatted" &&
!(buffer().masterParams().xref_package, "prettyref"))
|
On Sat, Apr 05, 2025 at 01:51:57PM +0200, Jürgen Spitzmüller wrote:
> Am Samstag, dem 05.04.2025 um 11:49 +0200 schrieb Scott Kostyshak:
> > On one of my documents I get the following warning:
> >
> > Package biblatex Warning: 'babel/polyglossia' dete
Am Samstag, dem 05.04.2025 um 11:49 +0200 schrieb Scott Kostyshak:
> On one of my documents I get the following warning:
>
> Package biblatex Warning: 'babel/polyglossia' detected but
> 'csquotes' missing.
>
> Should we load csquotes whenever using bibl
On one of my documents I get the following warning:
Package biblatex Warning: 'babel/polyglossia' detected but 'csquotes' missing.
Should we load csquotes whenever using biblatex and either babel or
polyglossia?
I can make a minimal example in case it would be useful.
S
Am Montag, dem 03.03.2025 um 10:08 + schrieb José Matos:
> One solution is, just like Jürgen did, to escape the backslash
> itself:
> "r@{\\extracolsep{0pt}"
>
> The other option is to change the string to be raw, by prefixing an r
> before the
> string starts, where backslashes are normal cha
On Sat, 2025-03-01 at 21:49 +0100, Jean-Marc Lasgouttes wrote:
> /home/jean-marc/src/lyx/master/lib/lyx2lyx/lyx_2_5.py:2464:
> SyntaxWarning: invalid escape sequence '\e'
> cmd = " special=\"" + scmd + "r@{\extracolsep{0pt}" + decpoint + "}"
> + scmd2 + "l\">"
>
> I cannot reproduce it for so
Am Samstag, dem 01.03.2025 um 21:49 +0100 schrieb Jean-Marc Lasgouttes:
> While playing with master, I got the following warning:
>
> /home/jean-marc/src/lyx/master/lib/lyx2lyx/lyx_2_5.py:2464:
> SyntaxWarning: invalid escape sequence '\e'
> cmd = " special=\&q
Hello,
While playing with master, I got the following warning:
/home/jean-marc/src/lyx/master/lib/lyx2lyx/lyx_2_5.py:2464:
SyntaxWarning: invalid escape sequence '\e'
cmd = " special=\"" + scmd + "r@{\extracolsep{0pt}" + decpoint + "}"
+ sc
Am Montag, dem 21.10.2024 um 17:15 +0200 schrieb Jean-Marc Lasgouttes:
> So I can change the guard to check for Qt 6.5? It is better to have
> precise versions so that we know what #ifdefs can go when José forces
> us to require Qt 6.6 ;)
Yes, please go ahead.
--
Jürgen
--
lyx-devel mailing li
Le 20/10/2024 à 08:04, Jürgen Spitzmüller a écrit :
Am Samstag, dem 19.10.2024 um 19:24 +0200 schrieb Jean-Marc Lasgouttes:
It seems to me that this is usable from Qt 6.5:
https://www.qt.io/blog/unifying-qttimespec-within-qtimezone
Or is it something else?
Yes, looks like it. The deprecation
Am Samstag, dem 19.10.2024 um 19:24 +0200 schrieb Jean-Marc Lasgouttes:
> It seems to me that this is usable from Qt 6.5:
> https://www.qt.io/blog/unifying-qttimespec-within-qtimezone
>
> Or is it something else?
Yes, looks like it. The deprecation is only from 6.7 though.
--
Jürgen
--
lyx-dev
Le 19/10/2024 à 10:04, Juergen Spitzmueller a écrit :
commit 4d51a05ce401bd1ad7c2bae5b6aeb7a2b494f35a
Author: Juergen Spitzmueller
Date: Sat Oct 19 09:57:24 2024 +0200
Address Qt 6.7 deprecation warning
See https://doc.qt.io/qt-6.7/qdatetime-obsolete.html#setTimeSpec
It
On Sat, 2024-07-27 at 16:14 +0100, José Matos wrote:
> I am not sure if this is from LyX or from KDE.
Followup to this:
This issue is/seems to be from KDE from calling okular through xgd-
open.
Best regards,
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/m
While running 2.4.x, built over the latest commit, in Wayland I got
this warning:
kf.windowsystem: static int KX11Extras::currentDesktop() may only be
used on X11
I am not sure if this is from LyX or from KDE.
I leave this here just for reference. Everything seems to be working...
I have
On 7/24/24 1:56 PM, Pavel Sanda wrote:
On Wed, Jul 24, 2024 at 05:55:21PM +, Pavel Sanda wrote:
commit 307d59cdb9a51105404d8e82a48a6c619c9df0f7
Author: Pavel Sanda
Date: Wed Jul 24 19:55:05 2024 +0200
Squash gcc warning.
---
src/insets/InsetGraphicsParams.cpp | 2 +-
1 file
On Wed, Jul 24, 2024 at 05:55:21PM +, Pavel Sanda wrote:
> commit 307d59cdb9a51105404d8e82a48a6c619c9df0f7
> Author: Pavel Sanda
> Date: Wed Jul 24 19:55:05 2024 +0200
>
> Squash gcc warning.
> ---
> src/insets/InsetGraphicsParams.cpp | 2 +-
> 1 file ch
Le 12/07/2024 à 21:25, Richard Kimberly Heck a écrit :
On 7/12/24 11:13 AM, Jean-Marc Lasgouttes wrote:
Le 12/07/2024 à 17:02, Jürgen Spitzmüller a écrit :
Am Freitag, dem 12.07.2024 um 16:18 +0200 schrieb Jean-Marc Lasgouttes:
It is the fault of autoconf 2.72, actually. Try the patch below.
On 7/12/24 11:13 AM, Jean-Marc Lasgouttes wrote:
Le 12/07/2024 à 17:02, Jürgen Spitzmüller a écrit :
Am Freitag, dem 12.07.2024 um 16:18 +0200 schrieb Jean-Marc Lasgouttes:
It is the fault of autoconf 2.72, actually. Try the patch below.
Thanks, this works!
Very good. It is in master now.
Le 12/07/2024 à 17:02, Jürgen Spitzmüller a écrit :
Am Freitag, dem 12.07.2024 um 16:18 +0200 schrieb Jean-Marc Lasgouttes:
It is the fault of autoconf 2.72, actually. Try the patch below.
Thanks, this works!
Very good. It is in master now.
Riki, this is candidate for branch.
A workaround
Am Freitag, dem 12.07.2024 um 16:18 +0200 schrieb Jean-Marc Lasgouttes:
> It is the fault of autoconf 2.72, actually. Try the patch below.
Thanks, this works!
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Le 12/07/2024 à 15:56, Jean-Marc Lasgouttes a écrit :
Le 12/07/2024 à 15:47, Jürgen Spitzmüller a écrit :
Am Freitag, dem 12.07.2024 um 15:28 +0200 schrieb Jean-Marc Lasgouttes:
Do you see a mention of grep and egrep in the configure output?
yes:
checking for grep that handles long lines an
Le 12/07/2024 à 15:47, Jürgen Spitzmüller a écrit :
Am Freitag, dem 12.07.2024 um 15:28 +0200 schrieb Jean-Marc Lasgouttes:
Do you see a mention of grep and egrep in the configure output?
yes:
checking for grep that handles long lines and -e... /usr/bin/grep
I get nothing like the above, b
Am Freitag, dem 12.07.2024 um 15:28 +0200 schrieb Jean-Marc Lasgouttes:
> Do you see a mention of grep and egrep in the configure output?
yes:
> checking for grep that handles long lines and -e... /usr/bin/grep
I get nothing like the above, but
> checking for egrep... /usr/bin/grep -E
checking
Le 12/07/2024 à 14:16, Jürgen Spitzmüller a écrit :
Am Freitag, dem 12.07.2024 um 11:31 +0200 schrieb Pavel Sanda:
Can you share the exact autogen/configure sequence and params so I
can try to reproduce your workflow?
./autogen.sh
./configure --enable-build-type=rel
The issue shows up in the
Am Freitag, dem 12.07.2024 um 11:31 +0200 schrieb Pavel Sanda:
> Can you share the exact autogen/configure sequence and params so I
> can try to reproduce your workflow?
./autogen.sh
./configure --enable-build-type=rel
The issue shows up in the make install step.
--
Jürgen
--
lyx-devel mailing
On Fri, Jul 12, 2024 at 09:35:23AM +0200, Jürgen Spitzmüller wrote:
> Am Donnerstag, dem 11.07.2024 um 17:53 +0200 schrieb Pavel Sanda:
> > What does line EGREP in your config.log says?
> > Here I see EGREP='/usr/bin/grep -E'
>
> Don't have this. I have in config.log
>
> configure:9394: checking
Am Donnerstag, dem 11.07.2024 um 17:53 +0200 schrieb Pavel Sanda:
> What does line EGREP in your config.log says?
> Here I see EGREP='/usr/bin/grep -E'
Don't have this. I have in config.log
configure:9394: checking for egrep -e
configure:9524: result: /usr/bin/grep -E
and
ac_cv_path_EGREP_TRADI
On Thu, Jul 11, 2024 at 01:51:03PM +0200, Jürgen Spitzmüller wrote:
> If I understand the scrips correctly (which I very likely do not) the
> command that is missing here is egrep.
What does line EGREP in your config.log says?
Here I see EGREP='/usr/bin/grep -E'
Pavel
--
lyx-devel mailing list
l
When compiling stable (probably also master), I am getting this:
[...]
%28LyXified%29.lyx examples/Example_%28raw%29.lyx examples/Welcome.lyx
templates/EPS_%28cropped%29.lyx templates/PDF_%28cropped%29.lyx
templates/README.new_templates; do \
if -q "^origin " "/usr/local/share/lyx/$i"
ch hopefully would stop the build).
>
>
> According to the man page there is no space in between, it should be -
> Werror or even -We.
>
> But just like for C++ code I prefer for the warning to be a warning.
> :-)
Fair enough ;)
> > I haven't tested, but would the way
be -
Werror or even -We.
But just like for C++ code I prefer for the warning to be a warning.
:-)
> I haven't tested, but would the way to ask our build systems to use
> the flag be to use the PYTHON environment variable? (./configure --
> help tells me this is used)?
Please no, I
On Sat, Jun 08, 2024 at 08:17:09AM GMT, José Matos wrote:
> On Sat, 2024-06-08 at 00:15 -0400, Scott Kostyshak wrote:
> > In the attached patch, I just put a 'r' in front of the string inside
> > re.compile(). It seems to make Python happy. Is it OK to commit?
> >
> > Scott
>
> Yes, that is the r
On Sat, 2024-06-08 at 00:15 -0400, Scott Kostyshak wrote:
> In the attached patch, I just put a 'r' in front of the string inside
> re.compile(). It seems to make Python happy. Is it OK to commit?
>
> Scott
Yes, that is the right fix. :-)
Either that or doubling the backslash but IMHO your solut
I see several warnings on a newer system (with Python 3.12.3) along the
following lines:
[ 7%] /usr/bin/python3 /home/scott/lyxbuilds/master-master/repo/po/lyx_pot.py
-b /home/scott/lyxbuilds/master-master/repo -o
/home/scott/lyxbuilds/master-master/CMakeBuild/po/examples_templates_l10n.pot
-
On 5/20/24 08:02, Jürgen Spitzmüller wrote:
Am Montag, dem 20.05.2024 um 10:37 +0200 schrieb Jean-Marc Lasgouttes:
What about putting it in 2.4.1?
Yes, why not. Currently it is just another annoying warning, though.
OK for 2.4.1.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
Am Montag, dem 20.05.2024 um 14:09 +0200 schrieb Jean-Marc Lasgouttes:
> > Yes, why not. Currently it is just another annoying warning,
> > though.
>
> Yes, but eventually it will bite. And we know that 2.4 will stay for
> 2+ years.
Good point. Riki?
--
Jürgen
--
lyx-d
Le 20/05/2024 à 14:02, Jürgen Spitzmüller a écrit :
Am Montag, dem 20.05.2024 um 10:37 +0200 schrieb Jean-Marc Lasgouttes:
What about putting it in 2.4.1?
Yes, why not. Currently it is just another annoying warning, though.
Yes, but eventually it will bite. And we know that 2.4 will stay
Am Montag, dem 20.05.2024 um 10:37 +0200 schrieb Jean-Marc Lasgouttes:
> What about putting it in 2.4.1?
Yes, why not. Currently it is just another annoying warning, though.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
What about putting it in 2.4.1?
JMarc
Le 20 mai 2024 09:49:57 GMT+02:00, Juergen Spitzmueller a écrit
:
>commit 44633c7f729e79ea023f2a5ccbbdd0002411619f
>Author: Juergen Spitzmueller
>Date: Mon May 20 09:49:10 2024 +0200
>
>Address Qt 6.7 deprecation warning
>---
Le 10/11/2023 à 12:16, Pavel Sanda a écrit :
On Fri, Nov 10, 2023 at 10:55:56AM +0100, Jean-Marc Lasgouttes wrote:
PS: I have to admit that I have a kink with weird uses of preprocessor
macros: https://gitlab.inria.fr/lasgoutt/parameters
Funny, I found # and ## operators very handy for writing
On Fri, Nov 10, 2023 at 10:55:56AM +0100, Jean-Marc Lasgouttes wrote:
> PS: I have to admit that I have a kink with weird uses of preprocessor
> macros: https://gitlab.inria.fr/lasgoutt/parameters
Funny, I found # and ## operators very handy for writing commandline
parameter parsing via simple inc
Le 09/11/2023 à 21:54, José Matos a écrit :
On Thu, 2023-11-09 at 20:34 +0100, Pavel Sanda wrote:
Looks reasonable. Pavel
I agree.
After so many dark spells I fear for Jean-Marc's sanity. :-D
You mean that I should not rewrite parts of LyX in preprocessor macros
as I intended to?
JMarc
On Thu, 2023-11-09 at 20:34 +0100, Pavel Sanda wrote:
> Looks reasonable. Pavel
I agree.
After so many dark spells I fear for Jean-Marc's sanity. :-D
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Thu, Nov 09, 2023 at 06:21:03PM +0100, Jean-Marc Lasgouttes wrote:
> Thoughts?
Looks reasonable. Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Le 08/11/2023 à 22:50, Pavel Sanda a écrit :
We have to do something for this annoying warning. What about the following?
If it works why not. I stopped following that gcc bug, but last time I looked
they gcc devs seemed convinced that false-positive ratio is small enough that
they will not
e attached changes anything? P
> >>
> >>It does, now those attached are what remains.
> >
> >Nice, so now we know the culprit. The question is whether we want
> >to get rid of reference on the left side or fix the temps on the right.
>
> We have to do somethi
. The question is whether we want
to get rid of reference on the left side or fix the temps on the right.
We have to do something for this annoying warning. What about the following?
JMarc
From 71d372b787516a28e9ec726d4a390dcb83bff10c Mon Sep 17 00:00:00 2001
From: Jean-Marc Lasgouttes
Date
Le 05/05/2023 à 20:39, Jean-Marc Lasgouttes a écrit :
Le 21/11/2022 à 08:34, José Matos a écrit :
Hi,
I have been compiling and running 2.4 compiled with the latest
preview of gcc 13.
I got a new warning:
"note: the temporary was destroyed at the end of the full expression"
I
Le 09/05/2023 à 14:23, Kornel Benko a écrit :
Yes, looks good, OTOH not needed. But better be on the safe side.
I agree that there is no real problem here. It justs improves our
coverity score :)
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/ly
Am Tue, 9 May 2023 13:53:15 +0200
schrieb Jean-Marc Lasgouttes :
> Le 09/05/2023 à 12:44, Jean-Marc Lasgouttes a écrit :
> > commit e620920fe2488ba50ff0b992c2529fdb69f2691a
> > Author: Jean-Marc Lasgouttes
> > Date: Tue May 9 13:49:17 2023 +0200
> >
> >
Le 09/05/2023 à 12:44, Jean-Marc Lasgouttes a écrit :
commit e620920fe2488ba50ff0b992c2529fdb69f2691a
Author: Jean-Marc Lasgouttes
Date: Tue May 9 13:49:17 2023 +0200
Fix unitialized member warning by coverity
Kornel, is that OK?
JMarc
The members open_braces and
On Sun, May 07, 2023 at 12:02:42PM +0200, Jean-Marc Lasgouttes wrote:
> Le 07/05/2023 à 03:14, Scott Kostyshak a écrit :
> > > I still think that these warning are more annoying than useful.
> >
> > I don't understand the underlying issues well enough. But in thi
Le 07/05/2023 à 03:14, Scott Kostyshak a écrit :
I still think that these warning are more annoying than useful.
I don't understand the underlying issues well enough. But in this case, shall
we disable these instances with #pragma ?
The other solution may be to declare first the argume
On Fri, May 05, 2023 at 08:39:22PM +0200, Jean-Marc Lasgouttes wrote:
> Le 21/11/2022 à 08:34, José Matos a écrit :
> > Hi,
> >I have been compiling and running 2.4 compiled with the latest
> > preview of gcc 13.
> >
> > I got a new warning:
> > "
Le 21/11/2022 à 08:34, José Matos a écrit :
Hi,
I have been compiling and running 2.4 compiled with the latest
preview of gcc 13.
I got a new warning:
"note: the temporary was destroyed at the end of the full expression"
I managed to solve cleanly the ones related to Converte
Updating and recompiling I got this warning:
/home/jamatos/lyx/lyx.anon/src/support/mutex.cpp: In constructor
‘lyx::Mutex::Private::Private()’:
/home/jamatos/lyx/lyx.anon/src/support/mutex.cpp:25:21: warning:
‘QMutex::QMutex(RecursionMode)’ is deprecated: Use QRecursiveMutex instead of a
Am Fri, 17 Feb 2023 19:15:36 +0100
schrieb "Jürgen Spitzmüller" :
> Am Freitag, dem 17.02.2023 um 12:22 -0500 schrieb Scott Kostyshak:
> > Indeed. But for example we might want to know if an example or manual
> > fails because of this. I think Jürgen's point is that for a
> > *template*,
> > it ma
Am Freitag, dem 17.02.2023 um 12:22 -0500 schrieb Scott Kostyshak:
> Indeed. But for example we might want to know if an example or manual
> fails because of this. I think Jürgen's point is that for a
> *template*,
> it makes sense not to have it.
>
> > The disadvantage OTOH would be that we would
:15 -0500 schrieb Scott Kostyshak:
> > > > > >
> > > > > > > I get the following (the line number changes depending on the
> > > > > > > file):
> > > > > > >
> > > > > > > lyx2lyx warning: Can&#
rote:
> > > > On Fri, Feb 17, 2023 at 03:42:14PM +0100, Jürgen Spitzmüller wrote:
> > > > > Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> > > > > > I get the following (the line number changes depending on the file):
>
> > > > Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> > > > > I get the following (the line number changes depending on the file):
> > > > >
> > > > > lyx2lyx warning: Can't find bibfiles for bibtex inset at l
> > > > I get the following (the line number changes depending on the file):
> > > >
> > > > lyx2lyx warning: Can't find bibfiles for bibtex inset at line 83!
> > > >
> > > > Is this worth fixing?
> > >
> > >
ending on the file):
> > >
> > > lyx2lyx warning: Can't find bibfiles for bibtex inset at line 83!
> > >
> > > Is this worth fixing?
> >
> > The bibtex inset in these files does not contain any bib file, so the
> > warning is appropriate. I would not want
On Fri, Feb 17, 2023 at 03:42:14PM +0100, Jürgen Spitzmüller wrote:
> Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> > I get the following (the line number changes depending on the file):
> >
> > lyx2lyx warning: Can't find bibfiles for bibtex ins
Am Freitag, dem 17.02.2023 um 07:15 -0500 schrieb Scott Kostyshak:
> I get the following (the line number changes depending on the file):
>
> lyx2lyx warning: Can't find bibfiles for bibtex inset at line 83!
>
> Is this worth fixing?
The bibtex inset in these files does
I get the following (the line number changes depending on the file):
lyx2lyx warning: Can't find bibfiles for bibtex inset at line 83!
Is this worth fixing?
The following ctests are failing:
export/templates/ja/Articles/Japanese_Article_%28JS_Bundle_for_LuaTeX%29_lyx16
(Failed)
e
Am 16.12.2022 um 00:48 schrieb Richard Kimberly Heck :
>
> On 12/15/22 17:02, Stephan Witt wrote:
>> Hi all,
>>
>> I’m seeing this warning with more modern Apple compilers for lyx-2.3.x:
>>
>> lyx-2.3.x/src/graphics/PreviewLoader.cpp:730:28: warning: result
On 12/15/22 17:02, Stephan Witt wrote:
Hi all,
I’m seeing this warning with more modern Apple compilers for lyx-2.3.x:
lyx-2.3.x/src/graphics/PreviewLoader.cpp:730:28: warning: result of '2^20' is 22; did
you mean '1 << 20' (1048576)? [-Wxor-used-as-pow]
Hi all,
I’m seeing this warning with more modern Apple compilers for lyx-2.3.x:
lyx-2.3.x/src/graphics/PreviewLoader.cpp:730:28: warning: result of '2^20' is
22; did you mean '1 << 20' (1048576)? [-Wxor-used-as-pow]
static
On Thu, Dec 15, 2022 at 12:38:28AM +0100, Thibaut Cuvelier wrote:
> On Sat, 26 Nov 2022 at 20:33, Scott Kostyshak
> wrote:
>
> > On Wed, Nov 09, 2022 at 10:41:17AM +0100, Jean-Marc Lasgouttes wrote:
> > > Hi,
> > >
> > > I get this warning when compilin
On Sat, 26 Nov 2022 at 20:33, Scott Kostyshak
wrote:
> On Wed, Nov 09, 2022 at 10:41:17AM +0100, Jean-Marc Lasgouttes wrote:
> > Hi,
> >
> > I get this warning when compiling in C++11 mode :
> >
> > ../../master/src/insets/InsetIndex.cpp: In member function
On Thu, Dec 08, 2022 at 04:14:00PM +0100, Richard Kimberly Heck wrote:
> commit fa449e976906edb9510639f2ca7bf491a2e07b46
> Author: Richard Kimberly Heck
> Date: Thu Dec 8 11:09:48 2022 -0500
>
> Simplify conversion routine, and remove warning
> ---
> lib/lyx2
On Wed, Nov 09, 2022 at 10:41:17AM +0100, Jean-Marc Lasgouttes wrote:
> Hi,
>
> I get this warning when compiling in C++11 mode :
>
> ../../master/src/insets/InsetIndex.cpp: In member function ‘virtual void
> lyx::InsetIndex::docbook(lyx::XMLStream&, const lyx
the temps on the right.
So what is the issue that the warning detect? I still don't get it.
My interpretation is that gcc is nervous about the temporary created via
getFont which is then propagated to the bottom via chain of refs and it's
not possible for it to decide whether returne
>
> So what is the issue that the warning detect? I still don't get it.
My interpretation is that gcc is nervous about the temporary created via
getFont which is then propagated to the bottom via chain of refs and it's
not possible for it to decide whether returned value is independe
Le 22 novembre 2022 03:04:39 GMT+01:00, Pavel Sanda a écrit :
>Nice, so now we know the culprit. The question is whether we want
>to get rid of reference on the left side or fix the temps on the right.
So what is the issue that the warning detect? I still don't get it.
JMarc
--
On Tue, Nov 22, 2022 at 01:47:26AM +, José Matos wrote:
> On Mon, 2022-11-21 at 23:08 +0100, Pavel Sanda wrote:
> > Can you try whether the attached changes anything? P
>
> It does, now those attached are what remains.
Nice, so now we know the culprit. The question is whether we want
to get
lyx::Buffer*, const
lyx::support::FileName&, const lyx::support::FileName&, const
lyx::support::FileName&, const std::string&, const std::string&,
lyx::ErrorList&, int, bool)’:
/home/jamatos/lyx/lyx.anon/src/Converter.cpp:714:55: warning: possibly dangling
reference
On Mon, Nov 21, 2022 at 09:07:02PM +, José Matos wrote:
> I hope that this helps,
> --
> José Abílio
> /home/jamatos/lyx/lyx.anon/src/BufferView.cpp: In member function ???bool
> lyx::BufferView::needsFitCursor() const???:
> /home/jamatos/lyx/lyx.anon/src/BufferView.c
On Mon, Nov 21, 2022 at 02:07:57PM +0100, Pavel Sanda wrote:
> > And it seems to me that addresses are consistently returned, which point to
> > an array cell (which s not going away).
>
> Maybe, I haven't study the code carefully. Can look again in the evening.
It seems you are right, I did not
).
I hope that this helps,
--
José Abílio
/home/jamatos/lyx/lyx.anon/src/BufferView.cpp: In member function ‘bool
lyx::BufferView::needsFitCursor() const’:
/home/jamatos/lyx/lyx.anon/src/BufferView.cpp:485:47: warning: possibly
dangling reference to a temporary [-Wdangling-reference]
485 |
#x27;t we create and return temp at GuiApplication.cpp:3695 ?
> >If you look above at theFontLoader (GuiApplication.cpp 3689)
> >we do similar logic but we reserve font_loader_ for the construct.
>
> If it was in GuiApplication, the warning will be there, wouldn't it?
I don&#x
n.cpp 3689)
we do similar logic but we reserve font_loader_ for the construct.
If it was in GuiApplication, the warning will be there, wouldn't it? And
it seems to me that addresses are consistently returned, which point to
an array cell (which s not going away).
> Or we could stop
On Mon, Nov 21, 2022 at 10:09:15AM +0100, Jean-Marc Lasgouttes wrote:
> I cannot really understand what the destroyed temporary is.
Don't we create and return temp at GuiApplication.cpp:3695 ?
If you look above at theFontLoader (GuiApplication.cpp 3689)
we do similar logic but we reserve font_loa
Le 21/11/2022 à 08:34, José Matos a écrit :
Hi,
I have been compiling and running 2.4 compiled with the latest
preview of gcc 13.
I got a new warning:
"note: the temporary was destroyed at the end of the full expression"
Attached follows an example, there are more I can send i
Hi,
I have been compiling and running 2.4 compiled with the latest
preview of gcc 13.
I got a new warning:
"note: the temporary was destroyed at the end of the full expression"
Attached follows an example, there are more I can send if they are
relevant.
Best regards,
--
José Ab
Hi,
I get this warning when compiling in C++11 mode :
../../master/src/insets/InsetIndex.cpp: In member function ‘virtual void
lyx::InsetIndex::docbook(lyx::XMLStream&, const lyx::OutputParams&) const’:
../../master/src/insets/InsetIndex.cpp:376:6: warning: init-statement in
s
Am Tue, 27 Sep 2022 16:40:40 +0200
schrieb Jean-Marc Lasgouttes :
> Le 21/09/2022 à 20:10, Kornel Benko a écrit :
> >
> > /usr2/src/lyx/lyx-git/src/Paragraph.cpp:1931:1: warning: control reaches
> > end of
> > non-void function [-Wreturn-type]
> >
> >
Le 21/09/2022 à 20:10, Kornel Benko a écrit :
/usr2/src/lyx/lyx-git/src/Paragraph.cpp:1931:1: warning: control reaches end of
non-void
function [-Wreturn-type]
This is with gcc-12, compiled in debug mode.
What gcc 12 version? On ububtu jammy, we have 12.1, which has a weird
warning in the
Am Sat, 24 Sep 2022 21:07:09 -0400
schrieb Scott Kostyshak :
> It's in at 725168ba. Do you see any other warnings with gcc-12?
>
> Scott
No other warnings yet.
Thanks
Kornel
pgpdcp1b84z4P.pgp
Description: Digitale Signatur von OpenPGP
--
lyx-devel mailing list
lyx-devel@lists.lyx.or
On Sat, Sep 24, 2022 at 10:57:05PM +0200, Kornel Benko wrote:
> Am Sat, 24 Sep 2022 14:51:17 -0400
> schrieb Scott Kostyshak :
>
> > On Wed, Sep 21, 2022 at 08:10:54PM +0200, Kornel Benko wrote:
> > >
> > > /usr2/src/lyx/lyx-git/src/Paragraph.cpp:1931:1: warni
Am Sat, 24 Sep 2022 14:51:17 -0400
schrieb Scott Kostyshak :
> On Wed, Sep 21, 2022 at 08:10:54PM +0200, Kornel Benko wrote:
> >
> > /usr2/src/lyx/lyx-git/src/Paragraph.cpp:1931:1: warning: control reaches
> > end of
> > non-void function [-Wreturn-type]
> >
On Wed, Sep 21, 2022 at 08:10:54PM +0200, Kornel Benko wrote:
>
> /usr2/src/lyx/lyx-git/src/Paragraph.cpp:1931:1: warning: control reaches end
> of non-void
> function [-Wreturn-type]
>
> This is with gcc-12, compiled in debug mode.
It makes sense if the warning is only g
1 - 100 of 943 matches
Mail list logo
