My instructions for the C compiler and linker command line were wrong:
instead of -fsanitize=asan , use -fsanitize=address or
-fsanitize=thread or -fsanitize=undefined or -fsanitize=memory .
And, of course, include debugging symbols with "-g".
Regards,
Neven Sajko
--
lyx-devel mailin
eports will be output to stderr, but it is
possible to output them to a file by setting an environment variable
(search for log_path in
https://github.com/google/sanitizers/wiki/AddressSanitizerFlags if in
need of that option).
I hope that was helpful.
Regards,
Neven Sajko
--
lyx-devel mailing list
lyx
rk for both Python 2 and Python 3.
I'm curious, why is it necessary to support Python 2?
Regards,
Neven Sajko
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Actually, do something like this (no "using distributivity" like in my
first message, to get a minimal git diff)
def_re =
re.compile(r"(\newcommandx|\renewcommandx|\global\long\def)(\[a-zA-Z]+)(.+)")
Regards,
Neven Sajko
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
Two notes: it would be better to use raw strings (r"string") and to maybe do
r"\(a|b|c|d)" instead of r"(\a|\b|\c|\d)" (use distributivity, in other words).
So, I think you want this:
def_re =
re.compile(r"\(newcommandx|renewcommandx|global\long\def)(\[a-
> Please, note that this numbering scheme (i.e., adding a digit after a
> minus sign) is often used by packagers to distinguish several releases
> by the same upstream version. Thus, they would number this release
> 2.3.4-1-1, making unclear what the upstream version is.
I can confirm that
> Do we still need boost included in our tree instead of just using the system
> one?
> IIRC we needed this for particular version like decade ago and since then
> there
> was no problem (correct me if I am wrong). Handling it now seems like useless
> waste of time & we polute each of our
> Wayland, for example). But if the menus do not really work, I would
> check whether other qt5 applications work. This might not be our bug.
Just checked with two other QT5 applications: shotcut does not seem to
manifest this bug, but wireshark does. Don't know what to make of it.
As far as I
I will not have time to debug this for a few more weeks, probably, but
here is something I found on the Web, could maybe be relevant:
https://github.com/tallforasmurf/CHIP8IDE/issues/22
TLDR: Somebody had a similar problem and fixed it by adding two QT
calls after the QT Widget update() call.
> It is only the LyX work area that is not updated or the whole window
> (toolbar, menus...)?
I am not sure what do you mean by "work area", but for me (while I am
looking at the Xorg-powered display and using lyx), there are problems
on almost the whole window. The little animations that should
This is on an up-to-date Archlinux system which should mean all
software is at latest release version.
Software versions:
lyx 2.3.3, qt5 5.13.2, xorg 1.20.5
Reproducing: Create an empty HOME dir and .lyx in it, run
/usr/share/lyx/configure.py with python2, start Lyx with created HOME.
I tried
Note: Am am resending this message now, I already sent it yesterday,
but it did was not approved.
This is on an up-to-date Archlinux system which should mean all
software is at latest release version.
Software versions:
lyx 2.3.3, qt5 5.13.2, xorg 1.20.5
Reproducing: Create an empty HOME dir
12 matches
Mail list logo
