Am Donnerstag, dem 25.07.2024 um 11:30 +0200 schrieb Jean-Marc
Lasgouttes:
> It would be unfair to say that it is my doing, though %-]
And I very consciously didn't ;-)
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Mittwoch, dem 24.07.2024 um 16:46 -0400 schrieb Scott Kostyshak:
> 1949 - export/doc/Math_xhtml (Failed)
Yes, LyX crashes on this. However, I don't think this is my doing.
Bisect points me to:
commit 999fb37ebb1aecfda9889fa6a2b2fbb15133f2aa
Author: Jean-Marc Lasgouttes
Date: Sat Jul 20
Am Mittwoch, dem 24.07.2024 um 16:46 -0400 schrieb Scott Kostyshak:
> Here is the list of failing tests. Indeed no xhtml tests are timing
> out anymore. Some docbook tests are timing out but I'm not sure this
> commit is the one that caused them to (I only bisected based on the
> ModernCV xhtml men
Am Mittwoch, dem 24.07.2024 um 14:40 -0400 schrieb Scott Kostyshak:
> Starting with this commit, some of our ctests time out. For example
> for
> the English Modern_CV:
>
> lyx -e xhtml Modern_CV.lyx
Should be fixed. XHTML uses convertLaTeXCommands() but it expects math
to be returned as is (wh
Am Mittwoch, dem 24.07.2024 um 10:20 -0400 schrieb Scott Kostyshak:
> I just pushed. There was one file that had a non-trivial diff. Does
> the following look expected, or at least harmless?
absolutely expected.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
l
Am Mittwoch, dem 24.07.2024 um 10:40 +0100 schrieb José Matos:
> What do you think? Any idea about this?
Since I do access it often, I am personally not too fond of having it
hidden deeper down the hierarchy.
I also think some external programs (bibliography managers) have the
path to the persona
Am Dienstag, dem 23.07.2024 um 15:16 -0400 schrieb Scott Kostyshak:
> Can we update the layouts now?
Go ahead. Nobody seems to have time to look at the problem.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http:
Am Montag, dem 22.07.2024 um 07:53 + schrieb Juergen Spitzmueller:
> commit 5bc4c11fd601773a7ffba850524afa03eafe13f9
> Author: Juergen Spitzmueller
> Date: Mon Jul 22 09:51:54 2024 +0200
>
> tex2lyx: Fix two bugs in nomencl import
>
> * The comment character % is made active to
Am Donnerstag, dem 06.06.2024 um 12:01 -0400 schrieb Richard Kimberly
Heck:
> It's possible that it is enough to change KeySequence::print, which
> seems to ignore ~S and the like, but I haven't experimented with it.
I provided a patch for anybody who wants to try out at
https://www.lyx.org/trac/
Sent privately.
Jürgen
Am Donnerstag, dem 18.07.2024 um 12:51 +0900 schrieb Yokota K.:
> To the manager of Trac:
>
> Hi, I tried to post to Trac and found I seem to have lost my Trac
> password.
> Could you kindly reset it? If my user ID is needed, I will send it
> personally.
>
> Koji
--
Jür
Am Mittwoch, dem 17.07.2024 um 17:46 +0200 schrieb Léo de Souza:
> I would like to report that LyX hangs when copying an inline formula
> containing a thin space in an mbox.
I think this is
https://www.lyx.org/trac/ticket/13069
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://
Am Montag, dem 15.07.2024 um 13:53 +0100 schrieb José Matos:
> On Sun, 2024-07-14 at 14:32 +0200, Jürgen Spitzmüller wrote:
> > I think the attached patch fixes it.
>
> I confirm that.
>
> It does not crash anymore. :-)
I committed it. Might be candidate for stable as well
Am Sonntag, dem 14.07.2024 um 09:37 -0500 schrieb T Rex:
> The issue for me is irregular behavior regarding the "clip to
> coordinates" option.
> What I expect from "clip to coordinates" when it is active is that
> the action is performed, if not, the image is restored to its
> original state. What
Am Samstag, dem 13.07.2024 um 09:58 -0500 schrieb T Rex:
> I don't know if I'm misinterpreting how the "Clip to coordinates"
> option works, but it seems that even if it's not selected, the
> clipping is still being done.
I don't see that. The coordinates are still being used, which is
intentional
Am Samstag, dem 13.07.2024 um 17:18 +0100 schrieb José Matos:
> On Fri, 2024-07-12 at 23:14 -0500, T Rex wrote:
> > The file and the backtrace:
> >
> >
> > /usr/include/c++/13.2.0/bits/stl_vector.h:1232: std::vector<_Tp,
> > _Alloc>::reference std::vector<_Tp, _Alloc>::back() [with _Tp =
> > lyx:
Am Sonntag, dem 14.07.2024 um 12:20 + schrieb Juergen Spitzmueller:
> commit 2bf3124f25bd7f71ad37adcf710b66dfb52192ff
> Author: Juergen Spitzmueller
> Date: Sun Jul 14 14:20:05 2024 +0200
>
> GuiTabular: add missing connections
Candidate for stable.
--
Jürgen
--
lyx-devel mailing li
Am Sonntag, dem 14.07.2024 um 11:03 +0200 schrieb Bernd Hafke:
> I want to report a bug on v2.4.1 (on Windows) in the table-settings
> window.
> When the frame spacing (e.g. below the lines) is set to custom via
> the dropdown, the custom setting can be done. After reopening ot the
> able-settings
Am Sonntag, dem 14.07.2024 um 11:08 +0200 schrieb Bernd Hafke:
> Dear LyX-Dev-Team,
>
> I would like to request the new feature to add the option (within the
> tool/setting/display section) to manually change to dark/light mode
> on Windows.
>
> Thanks for considerating this feature.
See https:/
Am Sonntag, dem 14.07.2024 um 09:04 +0200 schrieb Jürgen Spitzmüller:
> I'll have a look later today.
Should be fixed.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/list
Am Sonntag, dem 14.07.2024 um 00:11 -0400 schrieb Scott Kostyshak:
> Some of the Tufte ctests are timing out for me on current master.
> Here
> is one manual example:
>
> lyx -e pdflatex Tufte_Handout.lyx
>
> Can anyone reproduce on current master?
Yes, probably my fault. I'll have a look late
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
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
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
Am Donnerstag, dem 11.07.2024 um 12:58 -0400 schrieb Scott Kostyshak:
> templates/Articles/American_Psychological_Association_%28APA%29,_v._7
> .xhtml:211: parser error : xmlParseEntityRef: no name
> r">1961;
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing
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
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"
Am Dienstag, dem 09.07.2024 um 15:51 -0400 schrieb Scott Kostyshak:
> A lot of ctests are failing now. I think it is because if you
> continuously do lyx2lyx round trip (I tested with format 2.2.x and
> with
> Welcome.lyx), a few lines keep being added. e.g., after a few
> roundtrips
> we get the f
Dear Andreas
Am Donnerstag, dem 04.07.2024 um 17:18 +0200 schrieb Andreas Plihal:
> Ad settings window:
> * required lines: You used to be able to specify it. Now you can
> check the box, but you can no longer enter the number of lines.
Don't see this. I can enter the lines still (and also nothi
Am Donnerstag, dem 04.07.2024 um 00:01 +0200 schrieb Jean-Marc
Lasgouttes:
> I guess we should just limit the number of authors that we parse.
Done that as well in master now (7d2d26132b6bb28).
This helps a lot with the remaining performance problems of that
particular file.
Possible candidate f
Am Donnerstag, dem 04.07.2024 um 17:12 +0200 schrieb Jean-Marc
Lasgouttes:
> From what I understand, it exhausts the memory of the computer by
> allocating memory somewhere in the regex machinery (see the backtrace
> in the report). So the problem is not just about caching.
Regex indeed was the m
Am Donnerstag, dem 04.07.2024 um 17:12 +0200 schrieb Jean-Marc
Lasgouttes:
> > I suppose caching this vector and only recreating it when necessary
> > will make the case in the bug report usable again (the long list
> > causes
> > a noticeable delay, but it's bearable if done once IMHO), and it
> >
Am Mittwoch, dem 03.07.2024 um 19:02 -0400 schrieb Richard Kimberly
Heck:
> > Could you take a look at it now? I do not understand at all this
> > bibio.cpp stuff to fetch author names. I guess we should just limit
> > the number of authors that we parse.
>
> Will do. We had another bug like this
Am Dienstag, dem 02.07.2024 um 15:15 +0200 schrieb Jean-Marc
Lasgouttes:
> 2/ can we avoid, when we see that dvipng failed (because there is no
> dvi file?), to run these nonsensical epstopdf commands?
If dvipng fails this does not necessarily mean that we have no dvi
file, I think. Trying legacy
Am Dienstag, dem 02.07.2024 um 15:00 + schrieb Juergen
Spitzmueller:
> commit 4ed8bfb974e9bf5c626f00f4a57989c64320a568
> Author: Juergen Spitzmueller
> Date: Tue Jul 2 16:59:28 2024 +0200
>
> Do not check for diverging input encoding if the files use
> XeTeX/LuaTeX
>
> Fixes th
Am Dienstag, dem 02.07.2024 um 09:04 + schrieb Juergen
Spitzmueller:
> commit 574db220255dcd8c83f85e30527009a9af41e21d
> Author: Juergen Spitzmueller
> Date: Tue Jul 2 11:02:36 2024 +0200
>
> GuiDocument::onBufferViewChanged(): exit early if dialog is not
> open
>
> This should
Am Donnerstag, dem 27.06.2024 um 15:21 + schrieb Doc Who:
> there should be no double quotation marks in the second string there.
>
> Is this intentional? This has been working for many years. I cannot
> find anything about the wanted format in LyX documentation, though I
> believe I modeled i
Am Montag, dem 24.06.2024 um 17:17 +0200 schrieb Jürgen Spitzmüller:
> Am Montag, dem 24.06.2024 um 16:56 +0200 schrieb Jean-Marc
> Lasgouttes:
> > I see that Qt6.4 build fails when I enforce C++11. Is there an
> > announcement somewhere that this is the requirement?
>
Am Montag, dem 24.06.2024 um 16:56 +0200 schrieb Jean-Marc Lasgouttes:
> I see that Qt6.4 build fails when I enforce C++11. Is there an
> announcement somewhere that this is the requirement?
Sort of:
https://www.qt.io/blog/qt6-development-hosts-and-targets
--
Jürgen
--
lyx-devel mailing list
l
Am Samstag, dem 22.06.2024 um 14:07 +0200 schrieb Jürgen Spitzmüller:
> If I compile master with cmake
>
> HAVE_HUNSPELL_CXXABI = FALSE
>
> although it should be true (and also is with autotools).
With a fresh build the problem is gone.
Sorry for the noise.
--
Jürgen
--
ly
If I compile master with cmake
HAVE_HUNSPELL_CXXABI = FALSE
although it should be true (and also is with autotools).
In consequence I get deprecation warning for hunspell commands (which
are surpassed by the above boolean).
This is with external hunspell. With -DLYX_EXTERNAL_HUNSPELL:BOOL=OFF
e
Am Samstag, dem 22.06.2024 um 11:41 + schrieb Juergen Spitzmueller:
> commit 8659924abd7026aa97a36bd99efeb11705ff7190
> Author: Juergen Spitzmueller
> Date: Sat Jun 22 13:38:47 2024 +0200
>
> \cprotect amendment
>
> \cprotect'ed insets do not need forced local font switch; in f
Am Samstag, dem 15.06.2024 um 12:50 + schrieb Juergen Spitzmueller:
> commit 0fc8ee5ace22c11175cb93f5b6f7310cc4d646c1
> Author: Juergen Spitzmueller
> Date: Sat Jun 15 14:48:37 2024 +0200
>
> Prevent division by zero
>
> Fixes crash reported at
> https://marc.info/?l=lyx-us
Am Freitag, dem 14.06.2024 um 21:58 +0200 schrieb Pavel Sanda:
> This patch add possibility to dissolve the caption inset of the
> float.
>
> It's not particularly nice, because the menu entry is on the top
> above all
> editing options and would feel more natural next to "Split inset"
> entry -
>
Am Dienstag, dem 11.06.2024 um 21:37 +0300 schrieb Udicoudco:
> How can it break old documents?
All good. I missed the file format change part.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Sonntag, dem 09.06.2024 um 01:36 +0300 schrieb Udicoudco:
> Somewhat but not entirely related to that, if I execute textstyle-
> update shape up, LyX crash and I get a segmentation fault in 2.3.7,
> and "Exception: basic_string::_M_construct null not valid" on LyX
> 2.4 and master.
Fixed in
Am Samstag, dem 08.06.2024 um 12:17 -0400 schrieb Scott Kostyshak:
> Can anyone else confirm (or refute) on latest TeX Live?
Yes. It seems the package arydshln does not work anymore with the
tabular changes in LaTeX 6/24.
--
Jürgen
signature.asc
Description: This is a digitally signed message
Am Samstag, dem 08.06.2024 um 21:10 +0200 schrieb Jean-Marc Lasgouttes:
> > requiresFeature(name)?
>
> Yes, why not.
Went with that.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Samstag, dem 08.06.2024 um 16:29 +0200 schrieb Jean-Marc Lasgouttes:
> Maybe required(name)?
We already have the required() member which returns the whole set.
requiresFeature(name)?
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Samstag, dem 08.06.2024 um 15:37 +0200 schrieb Jean-Marc Lasgouttes:
> Is the Package part needed here? It is more a feature than a package
> that we require, isn't it?
I started with requires, but this has been flagged as a keyword by
QtCreator, so I extended it. Maybe hasRequirement()?
--
Am Samstag, dem 08.06.2024 um 11:16 +0200 schrieb Jean-Marc Lasgouttes:
> No this is a change that I did later. I did test that there is no
> crash in the 2.4.1-devel branch, which only has the hopefully safe
> part of biginset. I am relieved to see that so far the bugs that we
> had are not in the
Am Freitag, dem 07.06.2024 um 16:54 +0200 schrieb Jean-Marc Lasgouttes:
> This should be fixed in master now. This was actually more general
> than just an inset-split issue.
Thank you, I confirm this fixes the crash for me, too.
Does this need to get backported to biginset, too?
--
Jürgen
--
Am Freitag, dem 07.06.2024 um 15:29 +0200 schrieb Jürgen Spitzmüller:
> I suspect some update is missing now (after the biginset change) in
> the
> splitInset chain, but I do not see where (and which).
>
> JMarc, do you happen to have an idea?
As a pointer: The crash is caused a
Am Donnerstag, dem 06.06.2024 um 07:17 +0200 schrieb Jürgen
Spitzmüller:
> Am Dienstag, dem 04.06.2024 um 10:35 +0200 schrieb Pavel Sanda:
> > I see new crash:
> >
> > 1) New file && Insert -> Float -> Figure && type "a" inside the
> > in
Am Dienstag, dem 04.06.2024 um 12:16 +0100 schrieb John Robert Hudson:
> Sorry, having installed 2.4, I am still getting the error message in
> the LaTeX
> log:
>
> Package natbib Warning: There were undefined citations.
>
> Package bibtopic Warning: Please (re)run BibTeX on the file(s):
> (bibt
Am Dienstag, dem 04.06.2024 um 10:35 +0200 schrieb Pavel Sanda:
> I see new crash:
>
> 1) New file && Insert -> Float -> Figure && type "a" inside the
> innermost box
> 2) Dissolve outer inset via context menu on "Float: Figure" box
> 3) Postion the mouse cursor couple inches from left the side of
Am Donnerstag, dem 06.06.2024 um 00:19 +0300 schrieb Udicoudco:
> I attached a file that compiles with 2.3.x but not with 2.4.0.
> If I remove the quotes around the second argument of PackageOptions
> then LyX 2.3.7 complains that the layout is invalid, and with 2.4.0
> the file compiles.
That's d
Am Montag, dem 03.06.2024 um 16:00 +0100 schrieb José Matos:
> So I think that for the moment a pragmatic solution is to always
> update
> the layouts when updating the layout format. By reviewing the changes
> we can ensure that the update code does what it should.
I might have misunderstood the
Am Montag, dem 03.06.2024 um 02:53 + schrieb Scott Kostyshak:
> commit 7c041af6425001d7779f5e44d72918d8591ea37d
> Author: Scott Kostyshak
> Date: Sun Jun 2 22:52:37 2024 -0400
>
> Update layouts
Hm, I intentionally held that back unless we fix the problem discussed
at https://marc.info
Am Sonntag, dem 02.06.2024 um 17:05 +0200 schrieb Jürgen Spitzmüller:
> Am Sonntag, dem 02.06.2024 um 16:28 +0200 schrieb Pavel Sanda:
> > ./lyx -dbg any
> > ends up in infinite layout2layout conversion loop (strangely it
> > does
> > not when running without -dbg).
Am Sonntag, dem 02.06.2024 um 16:28 +0200 schrieb Pavel Sanda:
> ./lyx -dbg any
> ends up in infinite layout2layout conversion loop (strangely it does
> not when running without -dbg).
> Did we forget to update layout format number with some recent
> feature?
I stepped the format number at 2a7ec05
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
Am Samstag, dem 01.06.2024 um 07:10 + schrieb Juergen Spitzmueller:
> commit e1cb15ee5d9377cef6e3683a6d0bb68eb9b379c1
> Author: Juergen Spitzmueller
> Date: Sat Jun 1 09:06:44 2024 +0200
>
> Reset require_fresh_start_ after buffer has been viewed/exported
>
> The LFUN buffer-re
Am Donnerstag, dem 30.05.2024 um 21:59 -0400 schrieb Richard Kimberly
Heck:
> I'm happy to keep doing it. If anyone would like to take over,
> though, I'd be happy to pass the baton.
Excellent. You are doing an outstanding job.
And congrats to the release. I think it is a real milestone on many
r
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 (and the commit it
Am Montag, dem 20.05.2024 um 18:30 +0200 schrieb Kornel Benko:
> xdvipdfmx:fatal: Invalid font: -1 (27)
Probably some of your installed fonts are invalid. I had that, too,
with some of my fonts.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing
Am Montag, dem 20.05.2024 um 15:11 +0200 schrieb Kornel Benko:
> So the only remaining test is
> export/export/latex/languages/supported-languages_polyglossia-
> XeTeX_pdf4_systemF
Compiles for me. What errors do you get?
--
Jürgen
signature.asc
Description: This is a digitally signed message
Am Montag, dem 20.05.2024 um 15:11 +0200 schrieb Kornel Benko:
> Yes, this helps. At least the tests passed.
Committed.
Riki, this probably should go to 2.4.1.
> So the only remaining test is
> export/export/latex/languages/supported-languages_polyglossia-
> XeTeX_pdf4_systemF
I'll have a look.
Am Montag, dem 20.05.2024 um 11:40 +0200 schrieb Kornel Benko:
> Some russian documents fail
They work for me if I set appropriate fonts. What error do you get?
> Also failing American_Astronomical_Society
This is because \acknowledgements has been deprecated in favor of an
environment, and the
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-devel mailing list
lyx-dev
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
Am Montag, dem 20.05.2024 um 06:51 + schrieb Juergen Spitzmueller:
> commit 10b5f03d95dca8f3e8c225aa2deca4d473f8b169
> Author: Juergen Spitzmueller
> Date: Mon May 20 08:50:39 2024 +0200
>
> Initialize is_long_tabular before updateIndexes() (which employs
> it)
Should maybe go to 2.4.1
Am Sonntag, dem 19.05.2024 um 19:23 +0200 schrieb Jean-Marc Lasgouttes:
> You are right. What happens is that, since ad6aa8ba4b9,
> updateIndexes()
> relies on is_long_tabular, but this boolean is initialized *after*
> calling updateIndexes() in Tabular::init().
>
> I could just put the initiali
Am Sonntag, dem 19.05.2024 um 12:22 -0400 schrieb Scott Kostyshak:
> Starting with this commit, one of my knitr chunks in a beamer file
> now
> fails to compile. I committed a minimal example file to master
> located
> here:
>
> autotests/export/latex/lyxbugs/ed62816e-knitr-comment-beamer.lyx
S
Am Samstag, dem 18.05.2024 um 20:00 +0100 schrieb José Matos:
> But, for example, to correctly
> compile the User Guide what is the list of latex dependencies?
The User Guide loads these, but of course, other docs will require
other packages:
*File List*
scrbook.cls2023/07/07 v3.41 KOMA-Scr
Am Samstag, dem 18.05.2024 um 16:28 +0200 schrieb Kornel Benko:
> How should I know? I am reacting to the output of
> valgrind only.
I'd like to understand why the patch is needed. And why only for this
boolean. Otherwise it seems just a shot in the dark.
--
Jürgen
signature.asc
Description: T
Am Samstag, dem 18.05.2024 um 14:16 +0200 schrieb Kornel Benko:
> Am Sat, 18 May 2024 13:58:21 +0200
> schrieb Jean-Marc Lasgouttes :
>
> > Le 18/05/2024 à 13:52, Kornel Benko a écrit :
> > > Test passes after the attached patch.
> >
> > The patch looks good. Is this where other variables are
>
Am Freitag, dem 17.05.2024 um 18:08 +0200 schrieb Jean-Marc Lasgouttes:
> Should be OK now. Note that the cause was more profound than I
> anticipated, I hope I got it right. I added some assertions for good
> measure, so that we will soon see whether my assumptions about the
> code are correct :
Am Samstag, dem 18.05.2024 um 13:13 +0300 schrieb fcana...@gmail.com:
> Problem was mysterious because (1) it happened in LyX 2.4.0 but not
> in LyX 2.3.7, and (2) there was no indication that previews were not
> generated because these style files were missing. Perhaps something
> in lyxpreview2bi
Am Donnerstag, dem 16.05.2024 um 22:19 +0200 schrieb Kornel Benko:
> -- Error line = /usr2/src/lyx/lyx-
> git/src/insets/InsetTabular.cpp:1070:51: runtime
> error: load of value 110, which is not a valid value for type 'bool'
>
> Picky compiler ...
Aha. I don't get what it is complaining about, t
Am Donnerstag, dem 16.05.2024 um 10:54 +0200 schrieb Kornel Benko:
> With today's test, I get only
> export/doc/es/UserGuide_lyx16 (Failed)
> export/doc/es/UserGuide_lyx20 (Failed)
> export/doc/es/UserGuide_lyx21 (Failed)
> export/doc/es/UserGuide_lyx22 (Failed)
> expo
Am Donnerstag, dem 16.05.2024 um 10:00 +0200 schrieb Jean-Marc
Lasgouttes:
> If the situation is too annoying, I can revert it.
No pressure from my side. I can live with it. Just wanted to bring it
to your attention.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.o
Am Donnerstag, dem 16.05.2024 um 05:35 + schrieb Juergen
Spitzmueller:
> commit 2d95f8fc160d6ecc63acb81ffac16a99339083b2
> Author: Juergen Spitzmueller
> Date: Thu May 16 07:33:29 2024 +0200
>
> Amend 207eaeee9071cb
>
> The upstream encoding needs to be updated after this routi
Am Mittwoch, dem 15.05.2024 um 16:50 -0400 schrieb Scott Kostyshak:
> Bisect leads to:
>
> 207eaeee9071cb828a2ab7f4680f8ff92e379af8 is the first bad commit
> commit 207eaeee9071cb828a2ab7f4680f8ff92e379af8
> Author: Juergen Spitzmueller
> Date: Sun May 12 07:52:16 2024 +0200
>
> Introduce
Am Donnerstag, dem 16.05.2024 um 06:24 +0200 schrieb Jürgen
Spitzmüller:
> Well, the iconv conversion error stems from the fact that the
> encodings
> of master and child differ (latin9 vs. utf8). This looks very wring.
> Why is this?
>
> If I change the encoding of the master f
The screen moves a bit, but not to the point where the highlighted
match is.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Mittwoch, dem 15.05.2024 um 16:50 -0400 schrieb Scott Kostyshak:
> > These are iconv conversion errors. Strange.
>
> Bisect leads to:
Well, the iconv conversion error stems from the fact that the encodings
of master and child differ (latin9 vs. utf8). This looks very wring.
Why is this?
If I
Am Mittwoch, dem 15.05.2024 um 14:24 -0400 schrieb Scott Kostyshak:
> Yes the timeouts are gone now. The only remaining newly failing tests
> are the following:
>
> export/export/latex/languages/supported-languages_babel_auto-
> legacy_dvi (Failed)
> export/export/latex/languages/supported-lan
Am Mittwoch, dem 15.05.2024 um 11:05 -0400 schrieb Scott Kostyshak:
> And now tests are timing out. For example:
>
> cd lib/doc && lyx -e lyx23x Additional.lyx
>
> Can anyone reproduce the issue with that command?
Better now?
(I don't have time to check myself, but I'll do so in a few days i
Am Dienstag, dem 14.05.2024 um 11:38 + schrieb Juergen
Spitzmueller:
> commit a716fb96b534475759799b195a7edaeb049fbcf6
> Author: Juergen Spitzmueller
> Date: Tue May 14 13:37:29 2024 +0200
>
> NeedCProtect -1 also for InsetLayouts
Riki, this should go to 2.4.1.
--
Jürgen
--
lyx-deve
Am Sonntag, dem 12.05.2024 um 12:39 -0400 schrieb Richard Kimberly
Heck:
> Since 2.4.x has been branched, you can go ahead with that.
OK, so the new stage is open now.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Sonntag, dem 12.05.2024 um 19:04 +0200 schrieb Jürgen Spitzmüller:
> the documentation part manually later.
Done now. I have pasted the new English paragraph in a note to those
translated docs that already had the old version translated.
--
Jürgen
--
lyx-devel mailing list
lyx-de
Am Sonntag, dem 12.05.2024 um 12:39 -0400 schrieb Richard Kimberly
Heck:
> Since it's a regression, I think you should go ahead.
Thanks, I pulled the two code commits and do the documentation part
manually later.
> I assume it is otherwise safe?
Yes.
--
Jürgen
--
lyx-devel mailing list
lyx-d
Am Samstag, dem 25.03.2023 um 15:43 +0100 schrieb Jürgen Spitzmüller:
> > Should LyX escape '#' in the 'Frame' environment, or do we put the
> > responsibility on the user to know to use a Fragile Frame?
>
> The former, but this requires some effort (probab
Am Sonntag, dem 12.05.2024 um 05:53 + schrieb Juergen Spitzmueller:
> commit 207eaeee9071cb828a2ab7f4680f8ff92e379af8
> Author: Juergen Spitzmueller
> Date: Sun May 12 07:52:16 2024 +0200
>
> Introduce NeedCProtect -1 layout option
>
> It turns out beamer frame does not allow \
Am Freitag, dem 10.05.2024 um 21:34 +0300 schrieb Udicoudco:
> Dear all,
>
> I think I've encountered a regression in the 2.4 branch.
>
> The location of equation numbers/tags in RTL paragraphs seems wrong
> to me.
>
> When I tried to bisect yesterday I got way back to 2019 until I could
> not
Am Donnerstag, dem 09.05.2024 um 18:49 +0200 schrieb Jean-Pierre
Chrétien:
> The utf8 errors are gone, only the cprotect fatal error in the note
> if 6.6.1 remains, but it can't be easily solved AFAIU.
Correct.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mai
Am Donnerstag, dem 09.05.2024 um 15:32 +0200 schrieb Pavel Sanda:
> I'll just repeat from the second thread so the issue is more clear:
> Both 2.3 and 2.4 produce from UG
> \item
> [{\ensuremath{\lceil}\textsf{Outer}\ensuremath{\rfloor}\textsf{~and~}
> \ensuremath{\llceil}\textsf{inner}\ensuremath{
Am Donnerstag, dem 09.05.2024 um 12:18 +0200 schrieb Jean-Marc
Lasgouttes:
> Le 09/05/2024 à 12:10, Jürgen Spitzmüller a écrit :
> > Am Donnerstag, dem 09.05.2024 um 09:03 +0200 schrieb Enrico
> > Forestieri:
> > > Maybe Jürgen knows how feasible is backp
Am Donnerstag, dem 09.05.2024 um 09:03 +0200 schrieb Enrico Forestieri:
> Maybe Jürgen knows how feasible is backporting the cprotect work.
Definitely too much work.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Sonntag, dem 21.04.2024 um 23:22 +0300 schrieb fcana...@gmail.com:
> 1. Launch LyX 2.4.0 and start a new document using toolbar or menu.
> 2. Type some math and observe instant preview is working.
> 3. Insert either a Comment or Figure Float or Table Float (need not
> be filled in).
> 4. Type so
101 - 200 of 1005 matches
Mail list logo
