Re: Patch to remove Kluwer from Additional.lyx
Le 7 décembre 2022 07:20:29 Jürgen Spitzmüller a écrit : Am Dienstag, dem 06.12.2022 um 22:30 +0100 schrieb Pavel Sanda: We can safely remove the template. But what should we do with abandoned layouts? If I just remove it, old lyx documents might get into trouble. Should we keep all layouts in the tree forever? Please keep the layout. Removing it will break existing documents. And it really does not hurt anybody if we continue to ship it. Should not this apply to other removed layouts ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
Am Dienstag, dem 06.12.2022 um 22:30 +0100 schrieb Pavel Sanda: > We can safely remove the template. But what should we do with > abandoned layouts? If I just remove it, old lyx documents might > get into trouble. Should we keep all layouts in the tree forever? Please keep the layout. Removing it will break existing documents. And it really does not hurt anybody if we continue to ship it. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
On Tue, Dec 06, 2022 at 11:17:55PM +0100, Pavel Sanda wrote: > On Tue, Dec 06, 2022 at 10:31:51PM +0100, Jean-Marc Lasgouttes wrote: > > Shall we remove the layout file? It will make old files unreadable. It would > > be nice to have it in some attic, but I am not sure how to do it right. > > I was also thinking about some attic. It would be read if necessary, but > it would not show in .po files and we do not want to show Kluwer in > Document Settings->D. Class either. > > It seems some coding is necessary to get it right. > ATM we should perhaps just delete the template and somehow tag > layout for attic movement. Not sure if any better, but perhaps an alternative: could lyx2lyx just copy the module into the local layout? That is, the module could be hidden somewhere accessible to lyx2lyx and if it sees the .lyx file load the module it can just copy it into the local layout. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
On Tue, Dec 06, 2022 at 10:19:18PM +0100, Stephan Witt wrote: > Am 06.12.2022 um 22:12 schrieb Pavel Sanda : > > > > On Tue, Dec 06, 2022 at 12:25:53PM -0500, Scott Kostyshak wrote: > >> For a macOS user, can we tell whether they are on Ventura or not? > > > > I???ll try QSysInfo::productVersion() ??? > > This will show up like that: > > > > With Ventura it should be: 13.0 > >>> > >>> This would be the patch w/o I18N ??? > >> > >> Tested and works well here! I would say commit (unless someone else > >> disagrees). > >> > >> For me, the version showed up as "22.04". I actually expected my kernel > >> version to show up. > > > > I guess that's what QSysInfo::kernelType() is for. > > Anyway quickly checking members of QSysInfo you might actually > > want to use QSysInfo::prettyProductName(). > > Indeed. This prints "macOS Mojave (10.14)“ here. Ah yes, that is nice! Thanks, Stephan and Pavel. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Apply downstream macport patch?
On Wed, Dec 07, 2022 at 12:41:26AM +0100, Stephan Witt wrote: > Am 07.12.2022 um 00:38 schrieb Stephan Witt : > > > > Am 04.12.2022 um 16:28 schrieb Scott Kostyshak : > >> > >> On Thu, Dec 01, 2022 at 05:35:43PM +0100, Jean-Marc Lasgouttes wrote: > >>> Le 01/12/2022 à 16:25, Scott Kostyshak a écrit : > The following is a patch that (I think?) macports applies. I don't > understand it at all, but is it something we want? > > https://github.com/macports/macports-ports/blob/master/aqua/LyX/files/patch-lyx-linkbackserver-older-nsalert.diff > > Does 101200 correspond to a macOS version that we will support for 2.4.0? > > > > The patch ensures to compile and link LyX for macOS versions before 10.12 > > (Sierra as of 2016) (10.11 is El Capitan). > > > > The use of these systems is not recommended, AFAIK. > > > >>> This closes the following ticket > >>> https://trac.macports.org/ticket/61108 > >> > >> Stephan, any thoughts? > > > > Yes. > > > > 1. IMO, the link back server is a problem with Apple sandbox strategy in > > general. > > See e.g. https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg200962.html > > > > 2. I cannot see any movement with the project. > > https://www.linkbackproject.org/about/ > > > > 3. E.g. Qt 5.12 don’t support macos less than 10.12 too > > https://doc.qt.io/archives/qt-5.12/macos.html > > > > I think this patch isn’t critical - but it wouldn’t hurt either. > > BTW: If I try to build LyX 2.4 with minimum os version 10.11 I get this: > > /Users/lyx/git/lyx/src/insets/ExternalTransforms.cpp:334:20: error: > 'any_cast lyx::external::TransformOption, std::__1::default_delete lyx::external::TransformOption> > (std::__1::basic_string)> >' is > unavailable: introduced in macOS 10.14 > Factory factory = any_cast(any_factory); Thanks for taking a look, Stephan! I would say let's just skip it then. Scott > > Stephan signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [PATCH] Allow removing words from the personal dictionary, that weren't previously added
Am 21.11.2022 um 19:00 schrieb Jürgen Spitzmüller : > > Am Montag, dem 21.11.2022 um 18:53 +0100 schrieb Stephan Witt: >> Not easy, this would require to rewrite the spell check chunk split >> algorithm. >> >> ATM the complete paragraph is passed to the Apple spell checker at >> once. >> Obviously it won’t mark the unlearned word as misspelled in this >> case. >> So LyX has to iterate in a 2nd pass over the paragraph and find the >> unlearned words. >> I’d rather suggest the person who wants that to switch to the >> Hunspell engine. > > OK, fair enough. > >>> >> Yes, but I’d propose to add more values. >> At least UNLEARNED for exclude list and IGNORED for NO_SPELLCHECK >> font. > > OK. > >> 2. There is no context menu option to revert the >> LFUN_FONT_NO_SPELLCHECK. >> One may use the font options dialog - but opening it resets >> the >> NO_SPELLCHECK from word immediately. > > There is: "Ignore This Occurrence". It shows when opening the > context > menu upon a misspelled word. This triggers the LFUN. Yes, but the „Unignore“ option is not in drop-down menu. >>> >>> What do you mean by "drop-down" menu? It is in the context menu and >>> in >>> the spell checker dialog. >> >> >> Sorry - I meant the context menu. >> The font options dialog resets NO_SPELLCHECK on open. >>> >>> Not here. >> >> Here it is missing because of the spellcheck of the marked word >> returns OK. >> With the enum expansion mentioned above it would be possible to >> handle that. >> >> I don’t understand why we have different behavior here… see screen >> shots below. > > Strange. Something seems wrong in the Apple spellchecker chain. Is this > also without your patches? Yes. It is the same w/o the patches. Stephan -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Apply downstream macport patch?
Am 07.12.2022 um 00:38 schrieb Stephan Witt : > > Am 04.12.2022 um 16:28 schrieb Scott Kostyshak : >> >> On Thu, Dec 01, 2022 at 05:35:43PM +0100, Jean-Marc Lasgouttes wrote: >>> Le 01/12/2022 à 16:25, Scott Kostyshak a écrit : The following is a patch that (I think?) macports applies. I don't understand it at all, but is it something we want? https://github.com/macports/macports-ports/blob/master/aqua/LyX/files/patch-lyx-linkbackserver-older-nsalert.diff Does 101200 correspond to a macOS version that we will support for 2.4.0? > > The patch ensures to compile and link LyX for macOS versions before 10.12 > (Sierra as of 2016) (10.11 is El Capitan). > > The use of these systems is not recommended, AFAIK. > >>> This closes the following ticket >>> https://trac.macports.org/ticket/61108 >> >> Stephan, any thoughts? > > Yes. > > 1. IMO, the link back server is a problem with Apple sandbox strategy in > general. > See e.g. https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg200962.html > > 2. I cannot see any movement with the project. > https://www.linkbackproject.org/about/ > > 3. E.g. Qt 5.12 don’t support macos less than 10.12 too > https://doc.qt.io/archives/qt-5.12/macos.html > > I think this patch isn’t critical - but it wouldn’t hurt either. BTW: If I try to build LyX 2.4 with minimum os version 10.11 I get this: /Users/lyx/git/lyx/src/insets/ExternalTransforms.cpp:334:20: error: 'any_cast > (std::__1::basic_string)> >' is unavailable: introduced in macOS 10.14 Factory factory = any_cast(any_factory); Stephan -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Apply downstream macport patch?
Am 04.12.2022 um 16:28 schrieb Scott Kostyshak : > > On Thu, Dec 01, 2022 at 05:35:43PM +0100, Jean-Marc Lasgouttes wrote: >> Le 01/12/2022 à 16:25, Scott Kostyshak a écrit : >>> The following is a patch that (I think?) macports applies. I don't >>> understand it at all, but is it something we want? >>> >>> https://github.com/macports/macports-ports/blob/master/aqua/LyX/files/patch-lyx-linkbackserver-older-nsalert.diff >>> >>> Does 101200 correspond to a macOS version that we will support for 2.4.0? The patch ensures to compile and link LyX for macOS versions before 10.12 (Sierra as of 2016) (10.11 is El Capitan). The use of these systems is not recommended, AFAIK. >> This closes the following ticket >> https://trac.macports.org/ticket/61108 > > Stephan, any thoughts? Yes. 1. IMO, the link back server is a problem with Apple sandbox strategy in general. See e.g. https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg200962.html 2. I cannot see any movement with the project. https://www.linkbackproject.org/about/ 3. E.g. Qt 5.12 don’t support macos less than 10.12 too https://doc.qt.io/archives/qt-5.12/macos.html I think this patch isn’t critical - but it wouldn’t hurt either. Stephan -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
On Tue, Dec 06, 2022 at 10:31:51PM +0100, Jean-Marc Lasgouttes wrote: > Shall we remove the layout file? It will make old files unreadable. It would > be nice to have it in some attic, but I am not sure how to do it right. I was also thinking about some attic. It would be read if necessary, but it would not show in .po files and we do not want to show Kluwer in Document Settings->D. Class either. It seems some coding is necessary to get it right. ATM we should perhaps just delete the template and somehow tag layout for attic movement. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
Le 06/12/2022 à 22:15, Pavel Sanda a écrit : On Tue, Dec 06, 2022 at 05:00:21PM +, John Robert Hudson wrote: We do have ./lib/templates/Articles/Kluwer.lyx ./lib/layouts/kluwer.layout as well. Is Kluwer dead altogether? Pavel Yes, Kluwer was taken over in 2009; there are manuals from 1997 still on the Internet and a Kluwer BibTeX file still exists in the Harvard collection but the kluwer.cls is not available anywhere. Ok, thanks for your careful exploration. I'll apply your patch and will remove both kluwer files from 2.4 tree. Shall we remove the layout file? It will make old files unreadable. It would be nice to have it in some attic, but I am not sure how to do it right. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
On Tue, Dec 06, 2022 at 10:15:56PM +0100, Pavel Sanda wrote: > On Tue, Dec 06, 2022 at 05:00:21PM +, John Robert Hudson wrote: > > > We do have > > > ./lib/templates/Articles/Kluwer.lyx > > > ./lib/layouts/kluwer.layout > > > as well. Is Kluwer dead altogether? > > > > > Ok, thanks for your careful exploration. I'll apply your patch and will remove > both kluwer files from 2.4 tree. On a second though, this might not me that straightforward. We can safely remove the template. But what should we do with abandoned layouts? If I just remove it, old lyx documents might get into trouble. Should we keep all layouts in the tree forever? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
Am 06.12.2022 um 22:12 schrieb Pavel Sanda : > > On Tue, Dec 06, 2022 at 12:25:53PM -0500, Scott Kostyshak wrote: >> For a macOS user, can we tell whether they are on Ventura or not? > > I???ll try QSysInfo::productVersion() ??? This will show up like that: With Ventura it should be: 13.0 >>> >>> This would be the patch w/o I18N ??? >> >> Tested and works well here! I would say commit (unless someone else >> disagrees). >> >> For me, the version showed up as "22.04". I actually expected my kernel >> version to show up. > > I guess that's what QSysInfo::kernelType() is for. > Anyway quickly checking members of QSysInfo you might actually > want to use QSysInfo::prettyProductName(). Indeed. This prints "macOS Mojave (10.14)“ here. Stephan -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
On Tue, Dec 06, 2022 at 05:00:21PM +, John Robert Hudson wrote: > > We do have > > ./lib/templates/Articles/Kluwer.lyx > > ./lib/layouts/kluwer.layout > > as well. Is Kluwer dead altogether? > > > > Pavel > Yes, Kluwer was taken over in 2009; there are manuals from 1997 still on the > Internet and a Kluwer BibTeX file still exists in the Harvard collection but > the kluwer.cls is not available anywhere. Ok, thanks for your careful exploration. I'll apply your patch and will remove both kluwer files from 2.4 tree. > I have also prepared some material for these middle chapters to cover topics > not currently covered in Additional.lyx. I hope that a step by step approach > will enable people to keep up with the changes. Sounds good. Also if you add more details to commit messages (like "Kluwer was taken over in 2009") you might get less questions on the mailing list :) Thanks much for your efforts! Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
On Tue, Dec 06, 2022 at 12:25:53PM -0500, Scott Kostyshak wrote: > > >>> For a macOS user, can we tell whether they are on Ventura or not? > > >> > > >> I???ll try QSysInfo::productVersion() ??? > > > > > > This will show up like that: > > > > > > > > > > > > With Ventura it should be: 13.0 > > > > This would be the patch w/o I18N ??? > > Tested and works well here! I would say commit (unless someone else > disagrees). > > For me, the version showed up as "22.04". I actually expected my kernel > version to show up. I guess that's what QSysInfo::kernelType() is for. Anyway quickly checking members of QSysInfo you might actually want to use QSysInfo::prettyProductName(). Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: GuiRef.cpp Error Message
On Tue, Dec 06, 2022 at 05:11:52PM +0100, Christoph Schmitz wrote: > Hello Mac Pros, > > Since a few days I cannot compile LyX 2.4.0dev anymore. I get the following > error message: > > GuiRef.cpp:461:20: error: alias template 'QPair' requires template arguments; > argument deduction only allowed for class templates > refsNames.append(QPair(lab, toqstr((*iter).second))); > ^ > /opt/homebrew/lib/QtCore.framework/Headers/qpair.h:16:1: note: template is > declared here > using QPair = std::pair; > > System: > Apple MacBook Air M1, macOS Ventura 13.1 > Qt Version (run-time): 6.4.0 on platform cocoa > Qt Version (compile-time): 6.4.0 > Python detected: python3 -tt > > Any thoughts? Does it work after JMarc's recent commit (f3f478c2)? Thanks a lot for testing master, Chris! Best, Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Build problems (was: #6463: font encoding changes ...)
On Tue, Dec 06, 2022 at 07:02:17PM +0100, Guenter Milde wrote: > Am 6.12.22 schrieb LyX Ticket Tracker: > > > Replying to [comment:23 milde]: > ... > > > compiling from "master" fails with a "enchant++ not found" error > > > Are you building with autotools or CMake? What is your Enchant library > > version? Both made changes to accommodate Enchant 2. For example, > > [71977769/lyxgit] and [f1694db4/lyxgit], so I wonder if we messed > > something up. > > configuring with > > cmake -DLYX_ENABLE_EXPORT_TESTS=ON -DLYX_RELEASE=ON \ > -DLYX_INSTALL_PREFIX="git-" -DLYX_ENCHANT=ON ../lyx > > and then > > make > > The enchant library is > >libenchant-2-dev/stable,now 2.2.15-1 amd64 Thanks, Günter. Let's figure this out. What are the outputs to "dpkg -L libenchant-2-dev" and "apt-cache policy libenchant-2-dev" for you? Here are my outputs: $ dpkg -L libenchant-2-dev /. /usr /usr/include /usr/include/enchant-2 /usr/include/enchant-2/enchant++.h /usr/include/enchant-2/enchant-provider.h /usr/include/enchant-2/enchant.h /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/pkgconfig /usr/lib/x86_64-linux-gnu/pkgconfig/enchant-2.pc /usr/share /usr/share/doc /usr/share/doc/libenchant-2-dev /usr/share/doc/libenchant-2-dev/HACKING /usr/share/doc/libenchant-2-dev/NEWS.gz /usr/share/doc/libenchant-2-dev/copyright /usr/lib/x86_64-linux-gnu/libenchant-2.so /usr/share/doc/libenchant-2-dev/README /usr/share/doc/libenchant-2-dev/changelog.Debian.gz $ apt-cache policy libenchant-2-dev libenchant-2-dev: Installed: 2.3.2-1ubuntu2 Candidate: 2.3.2-1ubuntu2 Version table: Also, what enchant variables are in the CMake cache file? For me: $ grep -i "enchant" CMakeCache.txt ENCHANT_INCLUDE_DIR:PATH=/usr/include/enchant-2 ENCHANT_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libenchant-2.so //Require Enchant LYX_ENCHANT:BOOL=ON //ADVANCED property for variable: ENCHANT_INCLUDE_DIR ENCHANT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ENCHANT_LIBRARY ENCHANT_LIBRARY-ADVANCED:INTERNAL=1 //Details about finding ENCHANT FIND_PACKAGE_MESSAGE_DETAILS_ENCHANT:INTERNAL=[/usr/lib/x86_64-linux-gnu/libenchant-2.so][/usr/include/enchant-2][v()] //Test HAVE_ENCHANT2 HAVE_ENCHANT2:INTERNAL=1 $ Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Build problems (was: #6463: font encoding changes ...)
Am 6.12.22 schrieb LyX Ticket Tracker: > Replying to [comment:23 milde]: ... > > compiling from "master" fails with a "enchant++ not found" error > Are you building with autotools or CMake? What is your Enchant library > version? Both made changes to accommodate Enchant 2. For example, > [71977769/lyxgit] and [f1694db4/lyxgit], so I wonder if we messed > something up. configuring with cmake -DLYX_ENABLE_EXPORT_TESTS=ON -DLYX_RELEASE=ON \ -DLYX_INSTALL_PREFIX="git-" -DLYX_ENCHANT=ON ../lyx and then make The enchant library is libenchant-2-dev/stable,now 2.2.15-1 amd64 Günter -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
On Tue, Dec 06, 2022 at 06:11:40PM +0100, Stephan Witt wrote: > Am 06.12.2022 um 18:08 schrieb Stephan Witt : > > > > Am 06.12.2022 um 17:15 schrieb Stephan Witt : > >> > >> Am 06.12.2022 um 16:34 schrieb Scott Kostyshak : > >>> > >>> On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote: > Le 04/12/2022 à 21:41, Scott Kostyshak a écrit : > > When collecting information, it might be nice to have OS information. > > That way, the user only has to go to Help > About and click on "Copy > > Version Info" and all important information is copied; rather than > > having to ask them to separately state it. > > > > Is it OK if I add OS information? I'm not sure when I will get around to > > actually doing it but since it came up now I thought I would ask. > > Note that in the About LyX dialog, we have platform which gives the GUI > information. What else would you like? > >>> > >>> For a macOS user, can we tell whether they are on Ventura or not? > >> > >> I’ll try QSysInfo::productVersion() … > > > > This will show up like that: > > > > > > > > With Ventura it should be: 13.0 > > This would be the patch w/o I18N … Tested and works well here! I would say commit (unless someone else disagrees). For me, the version showed up as "22.04". I actually expected my kernel version to show up. This is a bit strange, since it doesn't say "Ubuntu" anywhere, but I think in many cases the distribution could be inferred from the number anyway. And in any case, I think this will be most useful for macOS and Windows. Thanks! Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
Am 06.12.2022 um 18:08 schrieb Stephan Witt : > > Am 06.12.2022 um 17:15 schrieb Stephan Witt : >> >> Am 06.12.2022 um 16:34 schrieb Scott Kostyshak : >>> >>> On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote: Le 04/12/2022 à 21:41, Scott Kostyshak a écrit : > When collecting information, it might be nice to have OS information. > That way, the user only has to go to Help > About and click on "Copy > Version Info" and all important information is copied; rather than > having to ask them to separately state it. > > Is it OK if I add OS information? I'm not sure when I will get around to > actually doing it but since it came up now I thought I would ask. Note that in the About LyX dialog, we have platform which gives the GUI information. What else would you like? >>> >>> For a macOS user, can we tell whether they are on Ventura or not? >> >> I’ll try QSysInfo::productVersion() … > > This will show up like that: > > > > With Ventura it should be: 13.0 This would be the patch w/o I18N … Stephan GuiAbout.patch Description: Binary data -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
Am 06.12.2022 um 17:15 schrieb Stephan Witt : > > Am 06.12.2022 um 16:34 schrieb Scott Kostyshak : >> >> On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote: >>> Le 04/12/2022 à 21:41, Scott Kostyshak a écrit : When collecting information, it might be nice to have OS information. That way, the user only has to go to Help > About and click on "Copy Version Info" and all important information is copied; rather than having to ask them to separately state it. Is it OK if I add OS information? I'm not sure when I will get around to actually doing it but since it came up now I thought I would ask. >>> >>> Note that in the About LyX dialog, we have platform which gives the GUI >>> information. What else would you like? >> >> For a macOS user, can we tell whether they are on Ventura or not? > > I’ll try QSysInfo::productVersion() … This will show up like that: With Ventura it should be: 13.0 Stephan-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
On Tuesday, 6 December 2022 10:58:32 GMT Pavel Sanda wrote: > On Tue, Dec 06, 2022 at 09:04:01AM +, John Robert Hudson wrote: > > >From fae09d387a7420cf659eef169b7ff47bc9256feb Mon Sep 17 00:00:00 2001 > > > > From: John R Hudson > > Date: Tue, 6 Dec 2022 09:00:08 + > > Subject: [PATCH] Kluwer no longer available; remove Kluwer section > > We do have > ./lib/templates/Articles/Kluwer.lyx > ./lib/layouts/kluwer.layout > as well. Is Kluwer dead altogether? > > Pavel Yes, Kluwer was taken over in 2009; there are manuals from 1997 still on the Internet and a Kluwer BibTeX file still exists in the Harvard collection but the kluwer.cls is not available anywhere. The final section which will need attention is Springer; all the svj* classes were replaced in 2013 with a completely new sr-vorl.cls. The documentation is in German; so it would be helpful if a German speaker were to revise the whole of the Springer section (though I have some German and could have a try if no- one else is in a position to do it). Having got rid of all the sections which have definitely been superseded - others may need updating like the Springer section - my plan is to structure the middle chapters of Additional.lyx to match entries in Document Settings like Document Class, Modules and Bibliography and move all the sections currently in other chapters into these new chapters so that a user gets a clear indication of material which relates to particular Document Settings entries. I have also prepared some material for these middle chapters to cover topics not currently covered in Additional.lyx. I hope that a step by step approach will enable people to keep up with the changes. John -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
Am 06.12.2022 um 16:34 schrieb Scott Kostyshak : > > On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote: >> Le 04/12/2022 à 21:41, Scott Kostyshak a écrit : >>> When collecting information, it might be nice to have OS information. >>> That way, the user only has to go to Help > About and click on "Copy >>> Version Info" and all important information is copied; rather than >>> having to ask them to separately state it. >>> >>> Is it OK if I add OS information? I'm not sure when I will get around to >>> actually doing it but since it came up now I thought I would ask. >> >> Note that in the About LyX dialog, we have platform which gives the GUI >> information. What else would you like? > > For a macOS user, can we tell whether they are on Ventura or not? I’ll try QSysInfo::productVersion() … Stephan -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
GuiRef.cpp Error Message
Hello Mac Pros, Since a few days I cannot compile LyX 2.4.0dev anymore. I get the following error message: GuiRef.cpp:461:20: error: alias template 'QPair' requires template arguments; argument deduction only allowed for class templates refsNames.append(QPair(lab, toqstr((*iter).second))); ^ /opt/homebrew/lib/QtCore.framework/Headers/qpair.h:16:1: note: template is declared here using QPair = std::pair; System: Apple MacBook Air M1, macOS Ventura 13.1 Qt Version (run-time): 6.4.0 on platform cocoa Qt Version (compile-time): 6.4.0 Python detected: python3 -tt Any thoughts? Best, Chris -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Put OS information in Help > About > Version ?
On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote: > Le 04/12/2022 à 21:41, Scott Kostyshak a écrit : > > When collecting information, it might be nice to have OS information. > > That way, the user only has to go to Help > About and click on "Copy > > Version Info" and all important information is copied; rather than > > having to ask them to separately state it. > > > > Is it OK if I add OS information? I'm not sure when I will get around to > > actually doing it but since it came up now I thought I would ask. > > Note that in the About LyX dialog, we have platform which gives the GUI > information. What else would you like? For a macOS user, can we tell whether they are on Ventura or not? Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: The lyx2lyx tests are suggesting regressions
On Tue, Dec 06, 2022 at 12:46:03AM -0500, Scott Kostyshak wrote: > On Mon, Dec 05, 2022 at 11:44:38PM -0500, Richard Kimberly Heck wrote: > > On 12/5/22 19:57, Scott Kostyshak wrote: > > > On Mon, Dec 05, 2022 at 06:35:21PM -0500, Richard Kimberly Heck wrote: > > > > On 12/5/22 15:01, Scott Kostyshak wrote: > > > > > Dear all, > > > > > > > > > > The lyx2lyx tests have been failing since yesterday, and now some > > > > > appear to be entering an infinite loop. > > > > > > > > > > I don't have time to look into this. Can someone take a look? > > > > I do not know how to do this, but the problem may be because I > > > > committed the > > > > reversion and conversion routines for format 612 separately, not > > > > realizing > > > > the conversion routine was needed. I've tested the two routines and just > > > > looked at them again, and they seem to work > > > The following will do it (adapt the 8 threads to whatever is good for > > > your computer): > > > > > >cmake -DLYX_ENABLE_EXPORT_TESTS=on . && make -j8 && ctest -R "lyx23" > > > --timeout 90 -j2 > > > > > > If it doesn't work for you, let me know and I'll have time on Friday to > > > take a look. > > > > OK, so I see the failing tests. Is there output I can see to find out what's > > going wrong? > > You can look at Testing/TemporaryLastTest.log, but usually I just > reproduce the test manually. > > Another thing is that you might not have all dependencies (e.g., CTAN > packages, fonts, etc.) for the tests to pass, so you don't know what's > broken and what's not unless you keep a "baseline" reference. > > We have documentation in Development.lyx, but I don't know if it's > helpful to you. > > Scott A lot of "check_load" tests are failing now. These tests correspond to just opening a document and checking whether there is terminal output. They can be run with the following command: ctest -R "check_load" Usually I just open them manually and check. For example, the following test is failing: check_load/doc/Additional If I just open Additional.lyx manually, I see many of these messages: lyx2lyx warning: lyx2lyx warning: Malformed LyX document: noprefix line not found where it should be. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patch to remove Kluwer from Additional.lyx
On Tue, Dec 06, 2022 at 09:04:01AM +, John Robert Hudson wrote: > >From fae09d387a7420cf659eef169b7ff47bc9256feb Mon Sep 17 00:00:00 2001 > From: John R Hudson > Date: Tue, 6 Dec 2022 09:00:08 + > Subject: [PATCH] Kluwer no longer available; remove Kluwer section We do have ./lib/templates/Articles/Kluwer.lyx ./lib/layouts/kluwer.layout as well. Is Kluwer dead altogether? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Patch to remove Kluwer from Additional.lyx
>From fae09d387a7420cf659eef169b7ff47bc9256feb Mon Sep 17 00:00:00 2001
From: John R Hudson
Date: Tue, 6 Dec 2022 09:00:08 +
Subject: [PATCH] Kluwer no longer available; remove Kluwer section
---
lib/doc/Additional.lyx | 48 ++
1 file changed, 48 insertions(+)
diff --git a/lib/doc/Additional.lyx b/lib/doc/Additional.lyx
index 1e80cdfcaa..bcc05d1a9f 100644
--- a/lib/doc/Additional.lyx
+++ b/lib/doc/Additional.lyx
@@ -13805,20 +13805,28 @@ For more informations like hints for special table and formula formatting,
\end_layout
\begin_layout Section
+
+\change_deleted 564990737 1670317155
Kluwer
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
by
\noun on
Panayotis Papasotiriou
\end_layout
\begin_layout Subsection
+
+\change_deleted 564990737 1670317155
Overview
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
The Kluwer package is a set of macros produced by Kluwer Academic Publishers
that facilitates electronic manuscript submission to the journals they
publish.
@@ -13859,6 +13867,8 @@ http://www.wkap.nl/kaphtml.htm/STYLEFILES
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
\SpecialChar LyX
supports many features of the package but not everything.
However, the \SpecialChar TeX
@@ -13891,10 +13901,14 @@ Astrophysics and Space Science
\end_layout
\begin_layout Subsection
+
+\change_deleted 564990737 1670317155
Writing a paper
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
The easiest way to write a paper is to start with the Kluwer template file.
Click on
\family sans
@@ -13921,10 +13935,14 @@ kluwer.lyx
\end_layout
\begin_layout Subsection
+
+\change_deleted 564990737 1670317155
Preparing a paper for submission
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
As in the AAS\SpecialChar TeX
package, before you submit your paper to a journal you must
@@ -13939,6 +13957,8 @@ postprocess
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
Export your paper as a \SpecialChar LaTeX
file.
To do this, click on
@@ -13953,6 +13973,8 @@ Export\SpecialChar menuseparator
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
Edit the resulting
\family typewriter
.tex
@@ -13962,6 +13984,8 @@ Edit the resulting
\begin_deeper
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
remove the comment lines before the
\family typewriter
@@ -13972,6 +13996,8 @@ documentclass
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
remove everything between (and including) the
\family typewriter
@@ -13989,6 +14015,8 @@ makeatother
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
Save the resulting
\family typewriter
.tex
@@ -13998,6 +14026,8 @@ Save the resulting
\end_deeper
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
Run the
\family typewriter
.tex
@@ -14007,6 +14037,8 @@ Run the
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
View the resulting
\family typewriter
.dvi
@@ -14027,6 +14059,8 @@ xdvi
\end_layout
\begin_layout Subsection
+
+\change_deleted 564990737 1670317155
\begin_inset Quotes eld
\end_inset
@@ -14045,6 +14079,8 @@ name "subsec:kluwer_peculiarities"
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
The Kluwer package has the following
\begin_inset Quotes eld
\end_inset
@@ -14057,6 +14093,8 @@ peculiarities
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
It is possible to write multiple articles in the same \SpecialChar LaTeX
file
\begin_inset Foot
@@ -14111,6 +14149,8 @@ end{article}
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
Information given at the beginning of the article (i.
\begin_inset space \thinspace{}
\end_inset
@@ -14151,6 +14191,8 @@ end{opening}
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
According to the user manual, the label of each bibliography item must be
written as
\family typewriter
@@ -14176,6 +14218,8 @@ year
\end_layout
\begin_layout Standard
+
+\change_deleted 564990737 1670317155
The
\family typewriter
kluwer.lyx
@@ -14195,11 +14239,15 @@ peculiarities
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
don't delete the \SpecialChar TeX
code included in the template, and
\end_layout
\begin_layout Enumerate
+
+\change_deleted 564990737 1670317155
copy the example bibliography item included in the template and modify it
as necessary to enter new bibliography items.
\end_layout
--
2.35.3
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
