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
When I load UserGuide with previews enabled, I see a lot of errors on
console:
Warning: dvipng failed to generate images from lyxpreviewjVAhXp.dvi...
fallback to legacy method
Warning: epstopdf failed on page 1, file lyxpreviewjVAhXp.001
Warning: epstopdf failed on page 2, file lyxpreviewjVAhX
; export/doc/ja/Shortcuts_pdf5_systemF
> > > export/doc/ja/Formula-numbering_pdf5_systemF
> > > export/examples/ja/Modules/Multilingual_Captions_pdf5_systemF
> > > export/doc/ja/Tutorial_pdf5_systemF
> >
> > Same here.
> >
> > > Perhaps
s/Multilingual_Captions_pdf5_systemF
> > export/doc/ja/Tutorial_pdf5_systemF
>
> Same here.
>
> > Perhaps my plan should be to wait a couple of weeks and see if the
> > failure persists before spending time checking them out.
>
> +1
>
> > Scott
> > See: https://tug.org/pipermail/tex-live/2024-May/050511.html
> >
> > Udi
>
> Thanks, Kornel and Udi. Indeed, after a new tlmgr update these tests
> pass. Now the following tests fail for me:
>
> export/examples/ja/Modules/Braille_pdf5_systemF
> e
t/examples/ja/Welcome_pdf5_systemF
export/doc/ja/Shortcuts_pdf5_systemF
export/doc/ja/Formula-numbering_pdf5_systemF
export/examples/ja/Modules/Multilingual_Captions_pdf5_systemF
export/doc/ja/Tutorial_pdf5_systemF
Perhaps my plan should be to wait a couple of weeks and see if the
failure persists before spending time checking them out.
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sat, May 4, 2024, 9:46 PM Kornel Benko wrote:
> Am Fri, 3 May 2024 10:31:42 -0400
> schrieb Scott Kostyshak :
>
> > This is likely not a LyX issue so feel free to ignore.
> >
> > After a tlmgr update, the following tests now fail:
> >
> > export/export/latex/languages/en-ja_platex_dvi3_syste
Am Fri, 3 May 2024 10:31:42 -0400
schrieb Scott Kostyshak :
> This is likely not a LyX issue so feel free to ignore.
>
> After a tlmgr update, the following tests now fail:
>
> export/export/latex/languages/en-ja_platex_dvi3_systemF (Failed)
> export/export/latex/languages/en-ja_platex_pdf4_
This is likely not a LyX issue so feel free to ignore.
After a tlmgr update, the following tests now fail:
export/export/latex/languages/en-ja_platex_dvi3_systemF (Failed)
export/export/latex/languages/en-ja_platex_pdf4_systemF (Failed)
export/export/latex/languages/en-ja_platex_pdf5_system
I get this at current git:
/home/jamatos/lyx/lyx/src/insets/InsetBibtex.cpp: In member function
‘virtual void lyx::InsetBibtex::docbook(lyx::XMLStream&, const
lyx::OutputParams&) const’:
/home/jamatos/lyx/lyx/src/insets/InsetBibtex.cpp:1223:70: error: ‘class
std::set >’ has no member named
‘contai
On 1/4/23 21:39, Scott Kostyshak wrote:
On Tue, Jan 03, 2023 at 10:30:27AM +0100, Jean-Marc Lasgouttes wrote:
With master, I cannot compile in c++11 mode:
../../master/src/mathed/InsetMathDecoration.cpp:191:22: error: ‘string_view’
has not been declared
191 | Attributes(bool o, string_view
On Tue, Jan 03, 2023 at 10:30:27AM +0100, Jean-Marc Lasgouttes wrote:
> With master, I cannot compile in c++11 mode:
>
> ../../master/src/mathed/InsetMathDecoration.cpp:191:22: error: ‘string_view’
> has not been declared
> 191 | Attributes(bool o, string_view entity)
> |
With master, I cannot compile in c++11 mode:
../../master/src/mathed/InsetMathDecoration.cpp:191:22: error:
‘string_view’ has not been declared
191 | Attributes(bool o, string_view entity)
| ^~~
Indeed, std::string_view is a c++17 thing.
JMarc
--
lyx-dev
Am Donnerstag, dem 03.02.2022 um 17:06 + schrieb José Abílio Matos:
> The changes were minimal and already referred here.
>
> It was enough to patch two files. The equivalent patch is already
> applied to the devel branch.
Just to confirm: OpenSuse Tumbleweed pushed gcc 12 on me today. I got
On Thu, Feb 03, 2022 at 05:04:29PM +, José Abílio Matos wrote:
> On Thursday, 27 January 2022 13.09.09 WET Scott Kostyshak wrote:
> > Except for that issue does it build with -Werror ?
> >
> > Scott
>
> For completeness sake, since this was answered before, it follows here an
> example of th
On Thursday, 27 January 2022 13.04.12 WET José Abílio Matos wrote:
> Hi,
>
> we are at the time of year again. :-)
>
>
> The gcc project will release version 12 and in Fedora we are rebuilding all
> packages with it.
The changes were minimal and already referred here.
It was enough to patch
On Thursday, 27 January 2022 13.09.09 WET Scott Kostyshak wrote:
> Except for that issue does it build with -Werror ?
>
> Scott
For completeness sake, since this was answered before, it follows here an
example of the output that you can expect when building lyx with gcc-12. In
this case I am st
On Thursday, 27 January 2022 13.52.56 WET Jean-Marc Lasgouttes wrote:
> José, what can you tell me about these messages?
> annobin: Timeout.cpp: Warning: -D_GLIBCXX_ASSERTIONS not defined
>
> We use _GLIBCXX_DEBUG currently. Should we switch to
> _GLIBCXX_ASSERTIONS? I have not found the gcc docs
On Thu, Jan 27, 2022 at 03:07:25PM +, José Abílio Matos wrote:
> On Thursday, 27 January 2022 13.09.09 WET Scott Kostyshak wrote:
> > Except for that issue does it build with -Werror ?
> >
> > Scott
>
> As Jean-Marc said the compilation has lots of warnings. Some of them are not
> our fault,
Am Thu, 27 Jan 2022 16:22:18 +
schrieb José Abílio Matos :
> On Thursday, 27 January 2022 15.48.33 WET Kornel Benko wrote:
> > This one may be needed for 2.4.0 version of lyxfind.cpp too.
>
> You are right but for some reason I got away without this fix, only the
> cstring of the other threa
On Thursday, 27 January 2022 15.48.33 WET Kornel Benko wrote:
> This one may be needed for 2.4.0 version of lyxfind.cpp too.
You are right but for some reason I got away without this fix, only the
cstring of the other thread. (BTW I am puzzled) The reason could be some
change in the code between
Am Thu, 27 Jan 2022 15:05:34 +
schrieb José Abílio Matos :
> lyxfind.cpp:55:1: note: 'std::ostream_iterator' is defined in header
> ''; did
> you forget to '#include '?
>
> 54 | #include "support/regex.h"
>
> +++ |+#include
>
> 55 |
This one may be needed for 2.4.0 version of lyx
On Thursday, 27 January 2022 13.09.09 WET Scott Kostyshak wrote:
> Except for that issue does it build with -Werror ?
>
> Scott
As Jean-Marc said the compilation has lots of warnings. Some of them are not
our fault, so I am not sure if it is possible to filter system warnings from -
Werror. :-)
On Thursday, 27 January 2022 13.52.56 WET Jean-Marc Lasgouttes wrote:
> This one is a warning, but you cut part of it out.
For complete sake the complete diagnose (warnings and errors) is here:
make[4]: Entering directory '/builddir/build/BUILD/lyx-2.3.6.1/src'
g++ -DHAVE_CONFIG_H -I. -I.. -I../
Le 27/01/2022 à 14:09, Scott Kostyshak a écrit :
On Thu, Jan 27, 2022 at 01:04:12PM +, José Abílio Matos wrote:
Hi,
we are at the time of year again. :-)
The gcc project will release version 12 and in Fedora we are rebuilding all
packages with it.
There is a failure to build 2.3.x (e.g
On Thu, Jan 27, 2022 at 01:04:12PM +, José Abílio Matos wrote:
> Hi,
> we are at the time of year again. :-)
>
> The gcc project will release version 12 and in Fedora we are rebuilding all
> packages with it.
>
> There is a failure to build 2.3.x (e.g
Hi,
we are at the time of year again. :-)
The gcc project will release version 12 and in Fedora we are rebuilding all
packages with it.
There is a failure to build 2.3.x (e.g. on x86-54):
https://kojipkgs.fedoraproject.org//work/tasks/4412/81984412/build.log
73 | class MatchString
Am 27.11.2021 um 18:36 schrieb Pavel Sanda :
>
> On Sat, Nov 27, 2021 at 09:47:36AM +0100, Stephan Witt wrote:
>> 2. Step - make dist
>>
>> $ (cd lyx-build/LyX-2.3.6dev.build;make dist)
>> /Applications/Xcode.app/Contents/Developer/usr/bin/make dist-bzip2
>> dist-gzip am__post_remove_distdir='@
On Sat, Nov 27, 2021 at 09:47:36AM +0100, Stephan Witt wrote:
> 2. Step - make dist
>
> $ (cd lyx-build/LyX-2.3.6dev.build;make dist)
> /Applications/Xcode.app/Contents/Developer/usr/bin/make dist-bzip2 dist-gzip
> am__post_remove_distdir='@:'
> /Applications/Xcode.app/Contents/Developer/usr/bin
Hi all,
I’ve tried to make a dist package to test it on one other machine.
1. Step - configure
2. Step - make dist
$ (cd lyx-build/LyX-2.3.6dev.build;make dist)
/Applications/Xcode.app/Contents/Developer/usr/bin/make dist-bzip2 dist-gzip
am__post_remove_distdir='@:'
/Applications/Xcode.app/Co
Am Di., 17. Nov. 2020 um 21:51 Uhr schrieb Kornel Benko :
> Am Tue, 17 Nov 2020 19:01:29 +0100
> schrieb Yu Jin :
>
> > Am Mo., 16. Nov. 2020 um 23:01 Uhr schrieb Kornel Benko >:
> >
> > > Am Mon, 16 Nov 2020 22:16:22 +0100
> > > schrieb Yu Jin :
> > > ...
> > > > >> In master it is called before
Am Tue, 17 Nov 2020 19:01:29 +0100
schrieb Yu Jin :
> Am Mo., 16. Nov. 2020 um 23:01 Uhr schrieb Kornel Benko :
>
> > Am Mon, 16 Nov 2020 22:16:22 +0100
> > schrieb Yu Jin :
> > ...
> > > >> In master it is called before the options,
> > > >> while in branch it is called after the options specs.
Am Mo., 16. Nov. 2020 um 23:01 Uhr schrieb Kornel Benko :
> Am Mon, 16 Nov 2020 22:16:22 +0100
> schrieb Yu Jin :
> ...
> > >> In master it is called before the options,
> > >> while in branch it is called after the options specs.
> > >>
> > >
> > > Yeah, thought so. I tried to move it behind the
Am Mon, 16 Nov 2020 22:16:22 +0100
schrieb Yu Jin :
...
> >> In master it is called before the options,
> >> while in branch it is called after the options specs.
> >>
> >
> > Yeah, thought so. I tried to move it behind the options which end at line
> > 250 something. But then I get this error in
Am Mo., 16. Nov. 2020 um 22:15 Uhr schrieb Yu Jin :
> Am Mo., 16. Nov. 2020 um 21:34 Uhr schrieb Kornel Benko :
>
>> Am Mon, 16 Nov 2020 19:45:15 +0100
>> schrieb Yu Jin :
>> > Ok then, I guess I can try to make a patch, I just don't understand one
>> > thing. In 2.3.x when I initially run configu
Am Mo., 16. Nov. 2020 um 21:34 Uhr schrieb Kornel Benko :
> Am Mon, 16 Nov 2020 19:45:15 +0100
> schrieb Yu Jin :
> > Ok then, I guess I can try to make a patch, I just don't understand one
> > thing. In 2.3.x when I initially run configure, it gives me an error that
> > the GNUWIN32_DIR is missin
Am Mon, 16 Nov 2020 19:45:15 +0100
schrieb Yu Jin :
> Am So., 15. Nov. 2020 um 22:47 Uhr schrieb Kornel Benko :
>
> > Am Sun, 15 Nov 2020 22:01:16 +0100
> > schrieb Yu Jin :
> >
> > > Am So., 15. Nov. 2020 um 21:28 Uhr schrieb Kornel Benko > >:
> > >
> > > > Am Sun, 15 Nov 2020 20:16:49 +0100
>
Am So., 15. Nov. 2020 um 22:47 Uhr schrieb Kornel Benko :
> Am Sun, 15 Nov 2020 22:01:16 +0100
> schrieb Yu Jin :
>
> > Am So., 15. Nov. 2020 um 21:28 Uhr schrieb Kornel Benko >:
> >
> > > Am Sun, 15 Nov 2020 20:16:49 +0100
> > > schrieb Yu Jin :
> > >
> > > > Am So., 15. Nov. 2020 um 20:15 Uhr s
Am Sun, 15 Nov 2020 22:01:16 +0100
schrieb Yu Jin :
> Am So., 15. Nov. 2020 um 21:28 Uhr schrieb Kornel Benko :
>
> > Am Sun, 15 Nov 2020 20:16:49 +0100
> > schrieb Yu Jin :
> >
> > > Am So., 15. Nov. 2020 um 20:15 Uhr schrieb Yu Jin :
> > > > I agree with CMAKE_PREFIX_PATH. I think that GNUWIN32
Am So., 15. Nov. 2020 um 21:28 Uhr schrieb Kornel Benko :
> Am Sun, 15 Nov 2020 20:16:49 +0100
> schrieb Yu Jin :
>
> > Am So., 15. Nov. 2020 um 20:15 Uhr schrieb Yu Jin :
> > > I agree with CMAKE_PREFIX_PATH. I think that GNUWIN32_DIR was a good
> way
> > > of handling that (I assume it was that
Am Sun, 15 Nov 2020 20:16:49 +0100
schrieb Yu Jin :
> Am So., 15. Nov. 2020 um 20:15 Uhr schrieb Yu Jin :
>
> > Am So., 15. Nov. 2020 um 18:20 Uhr schrieb Thibaut Cuvelier <
> > tcuvel...@lyx.org>:
> >
> >> On Sun, 15 Nov 2020 at 16:59, Kornel Benko wrote:
> >>
> >>> Am Sun, 15 Nov 2020 16:47:36
Am So., 15. Nov. 2020 um 20:15 Uhr schrieb Yu Jin :
> Am So., 15. Nov. 2020 um 18:20 Uhr schrieb Thibaut Cuvelier <
> tcuvel...@lyx.org>:
>
>> On Sun, 15 Nov 2020 at 16:59, Kornel Benko wrote:
>>
>>> Am Sun, 15 Nov 2020 16:47:36 +0100
>>> schrieb Yu Jin :
>>>
>>> > Am So., 15. Nov. 2020 um 16:34
Am So., 15. Nov. 2020 um 18:20 Uhr schrieb Thibaut Cuvelier <
tcuvel...@lyx.org>:
> On Sun, 15 Nov 2020 at 16:59, Kornel Benko wrote:
>
>> Am Sun, 15 Nov 2020 16:47:36 +0100
>> schrieb Yu Jin :
>>
>> > Am So., 15. Nov. 2020 um 16:34 Uhr schrieb Yu Jin :
>> >
>> > > Am So., 15. Nov. 2020 um 16:03
On Sun, 15 Nov 2020 at 16:59, Kornel Benko wrote:
> Am Sun, 15 Nov 2020 16:47:36 +0100
> schrieb Yu Jin :
>
> > Am So., 15. Nov. 2020 um 16:34 Uhr schrieb Yu Jin :
> >
> > > Am So., 15. Nov. 2020 um 16:03 Uhr schrieb Kornel Benko <
> kor...@lyx.org>:
> > >
> > >> Am Sun, 15 Nov 2020 15:08:43 +010
Am Sun, 15 Nov 2020 16:47:36 +0100
schrieb Yu Jin :
> Am So., 15. Nov. 2020 um 16:34 Uhr schrieb Yu Jin :
>
> > Am So., 15. Nov. 2020 um 16:03 Uhr schrieb Kornel Benko :
> >
> >> Am Sun, 15 Nov 2020 15:08:43 +0100
> >> schrieb Yu Jin :
> >>
> >> > > You have to investigate the cmake module FomdPe
Am Sun, 15 Nov 2020 16:34:59 +0100
schrieb Yu Jin :
> Am So., 15. Nov. 2020 um 16:03 Uhr schrieb Kornel Benko :
>
> > Am Sun, 15 Nov 2020 15:08:43 +0100
> > schrieb Yu Jin :
> >
> > > > You have to investigate the cmake module FomdPerl.cmake.
> > > > It may help, if you use HINTS, for instance fo
Am So., 15. Nov. 2020 um 16:34 Uhr schrieb Yu Jin :
> Am So., 15. Nov. 2020 um 16:03 Uhr schrieb Kornel Benko :
>
>> Am Sun, 15 Nov 2020 15:08:43 +0100
>> schrieb Yu Jin :
>>
>> > > You have to investigate the cmake module FomdPerl.cmake.
>> > > It may help, if you use HINTS, for instance for path
Am So., 15. Nov. 2020 um 16:03 Uhr schrieb Kornel Benko :
> Am Sun, 15 Nov 2020 15:08:43 +0100
> schrieb Yu Jin :
>
> > > You have to investigate the cmake module FomdPerl.cmake.
> > > It may help, if you use HINTS, for instance for path D:\
> > > find_package(Perl REQUIRED PATHS "D:\\
Am Sun, 15 Nov 2020 15:08:43 +0100
schrieb Yu Jin :
> > You have to investigate the cmake module FomdPerl.cmake.
> > It may help, if you use HINTS, for instance for path D:\
> > find_package(Perl REQUIRED PATHS "D:\\")
> >
> > At least, this one works on linux too.
> >
> Uhm, ist
Am So., 15. Nov. 2020 um 12:57 Uhr schrieb Kornel Benko :
> Am Sun, 15 Nov 2020 11:32:34 +0100
> schrieb Yu Jin :
>
> > I can not configure master with CMake currently, it says:
> >
> > CMake Error at C:/Program
> >
> Files/CMake/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146
> >
Am Sun, 15 Nov 2020 11:32:34 +0100
schrieb Yu Jin :
> I can not configure master with CMake currently, it says:
>
> CMake Error at C:/Program
> Files/CMake/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146
> (message):
> Could NOT find Perl (missing: PERL_EXECUTABLE)
> Call Stack
I can not configure master with CMake currently, it says:
CMake Error at C:/Program
Files/CMake/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146
(message):
Could NOT find Perl (missing: PERL_EXECUTABLE)
Call Stack (most recent call first):
C:/Program
Files/CMake/share/cmake-3.1
On 8/9/20 3:23 AM, Kornel Benko wrote:
> Am Sun, 9 Aug 2020 02:48:03 -0400
> schrieb Richard Kimberly Heck :
>
>> Sorry, I omitted the cmake step. Here's what I did this time:
>>
>> mkdir build/ # from the LyX directory
>> cd build/
>> cmake ..
>> make
>> sudo make install
>>
>> This used to work j
Am Sun, 9 Aug 2020 02:48:03 -0400
schrieb Richard Kimberly Heck :
> Sorry, I omitted the cmake step. Here's what I did this time:
>
> mkdir build/ # from the LyX directory
> cd build/
> cmake ..
> make
> sudo make install
>
> This used to work just fine but now doesn't. If instead I do:
>
> cma
On 8/8/20 7:18 PM, Kornel Benko wrote:
> Am Sat, 8 Aug 2020 18:59:43 -0400
> schrieb Richard Kimberly Heck :
>
>> On 8/8/20 3:10 PM, Scott Kostyshak wrote:
>>> On Sat, Aug 08, 2020 at 07:31:44AM +0200, Kornel Benko wrote:
Am Sat, 8 Aug 2020 00:33:47 -0400
schrieb Richard Kimberly Heck :
Am Sat, 8 Aug 2020 18:59:43 -0400
schrieb Richard Kimberly Heck :
> On 8/8/20 3:10 PM, Scott Kostyshak wrote:
> > On Sat, Aug 08, 2020 at 07:31:44AM +0200, Kornel Benko wrote:
> >> Am Sat, 8 Aug 2020 00:33:47 -0400
> >> schrieb Richard Kimberly Heck :
> >>
> >>> On Linux:
> >>>
> >>> ./autogen
On 8/8/20 3:10 PM, Scott Kostyshak wrote:
> On Sat, Aug 08, 2020 at 07:31:44AM +0200, Kornel Benko wrote:
>> Am Sat, 8 Aug 2020 00:33:47 -0400
>> schrieb Richard Kimberly Heck :
>>
>>> On Linux:
>>>
>>> ./autogen.sh
>>> mkdir build
>>> cd build
>>> make -j4
>>> sudo make install
>>>
>>> CMake Error
On Sat, Aug 08, 2020 at 07:31:44AM +0200, Kornel Benko wrote:
> Am Sat, 8 Aug 2020 00:33:47 -0400
> schrieb Richard Kimberly Heck :
>
> > On Linux:
> >
> > ./autogen.sh
> > mkdir build
> > cd build
> > make -j4
> > sudo make install
> >
> > CMake Error at po/cmake_install.cmake:45 (file):
> >
Am Sat, 8 Aug 2020 00:33:47 -0400
schrieb Richard Kimberly Heck :
> On Linux:
>
> ./autogen.sh
> mkdir build
> cd build
> make -j4
> sudo make install
>
> CMake Error at po/cmake_install.cmake:45 (file):
> file INSTALL cannot find "/cvs/lyx/lyx-pristine/build/po/ar.gmo": No such
> file or di
On Linux:
./autogen.sh
mkdir build
cd build
make -j4
sudo make install
CMake Error at po/cmake_install.cmake:45 (file):
file INSTALL cannot find "/cvs/lyx/lyx-pristine/build/po/ar.gmo": No such
file or directory.
The gmo files are not at /cvs/lyx/lyx-pristine/build/po/ but at
/cvs/lyx/lyx-pr
On Sunday, 27 January 2019 12.52.44 WET Jean-Marc Lasgouttes wrote:
> This is fixed in 2.3.3dev at 3a123b90.
>
> JMarc
Thank you Jean-Marc. :-)
--
José Abílio
Le 26/01/2019 à 23:54, José Abílio Matos a écrit :
FWIW:
While rebuilding lyx due the to update to boost 1.69 there was an error:
https://kojipkgs.fedoraproject.org//work/tasks/9306/32249306/build.log
This is fixed in 2.3.3dev at 3a123b90.
JMarc
FWIW:
While rebuilding lyx due the to update to boost 1.69 there was an error:
https://kojipkgs.fedoraproject.org//work/tasks/9306/32249306/build.log
The culprit seems to be:
make[5]: Leaving directory '/builddir/build/BUILD/lyx-2.3.2/src/support'
BUILDSTDERR: FileName.cpp:77:64: error: wrong num
e,
>
> - if I cannot open them in LyX
> - or if they become corrupted in a hidden way -- subtle changes that are
> easily overlooked but may be fatal (missing content due to missing
> characters or paragraphs, say).
>
> * Failure to export to an earlier LyX ver
> Warning: Malformed LyX document: Missing layout name on line 5101
>
> This will not solve the test failure, but give a better diagnosis and
> user-experience: LyX can open the file (it is broken but the parser replaces
> the missing layout name with "Standard".
> Th
sing content due to missing
characters or paragraphs, say).
* Failure to export to an earlier LyX version is less severe, especially
for really old versions. If everything else fails, I may try via LaTeX.
This is reflected in the unconditional commitment to ensure old files work
while back-convers
, however, is:
> Warning: Malformed LyX document: Can't find layout at line 5048
Yes, there is a *warning* which our ctests turn into a test failure.
However, it is only a sign of something going wrong, not the reason.
> But I only have your modernCV patch applied. I think you post
Am Donnerstag, 17. Januar 2019 09:15:03 CET schrieb Kornel Benko
:
> Am Mittwoch, 16. Januar 2019 14:20:37 CET schrieb Scott Kostyshak
> :
> > On Wed, Jan 16, 2019 at 08:10:39PM +0100, Kornel Benko wrote:
> > > Am Mittwoch, 16. Januar 2019 13:58:41 CET schrieb Scott Kostyshak
> > > :
> > > > On
Am Mittwoch, 16. Januar 2019 14:20:37 CET schrieb Scott Kostyshak
:
> On Wed, Jan 16, 2019 at 08:10:39PM +0100, Kornel Benko wrote:
> > Am Mittwoch, 16. Januar 2019 13:58:41 CET schrieb Scott Kostyshak
> > :
> > > On Wed, Jan 16, 2019 at 07:55:43PM +0100, Kornel Benko wrote:
> > >
> > > > I don'
On Wed, Jan 16, 2019 at 08:10:39PM +0100, Kornel Benko wrote:
> Am Mittwoch, 16. Januar 2019 13:58:41 CET schrieb Scott Kostyshak
> :
> > On Wed, Jan 16, 2019 at 07:55:43PM +0100, Kornel Benko wrote:
> >
> > > I don't remember why we do not test for lyx20x.
> >
> > It is because of the \origin t
Am Mittwoch, 16. Januar 2019 13:58:41 CET schrieb Scott Kostyshak
:
> On Wed, Jan 16, 2019 at 07:55:43PM +0100, Kornel Benko wrote:
>
> > I don't remember why we do not test for lyx20x.
>
> It is because of the \origin tag (which was introduced later). I think
> the test scripts rely on this tag
On Wed, Jan 16, 2019 at 07:55:43PM +0100, Kornel Benko wrote:
> I don't remember why we do not test for lyx20x.
It is because of the \origin tag (which was introduced later). I think
the test scripts rely on this tag existing for dealing with the
dependencies when copying to the temporary directo
Am Mittwoch, 16. Januar 2019 13:25:02 CET schrieb Scott Kostyshak
:
> On Wed, Jan 16, 2019 at 06:02:54PM +, Guenter Milde wrote:
> > Dear LyX developers,
> >
> > On 2019-01-15, Guenter Milde wrote:
> > > On 2019-01-15, Kornel Benko wrote:
> >
> > > It seems the problem with beamer export is
On Wed, Jan 16, 2019 at 06:02:54PM +, Guenter Milde wrote:
> Dear LyX developers,
>
> On 2019-01-15, Guenter Milde wrote:
> > On 2019-01-15, Kornel Benko wrote:
>
> > It seems the problem with beamer export is still there:
>
> > The following tests FAILED:
> > 3515 - export/examples/beam
Dear LyX developers,
On 2019-01-15, Guenter Milde wrote:
> On 2019-01-15, Kornel Benko wrote:
> It seems the problem with beamer export is still there:
> The following tests FAILED:
> 3515 - export/examples/beamer_lyx16 (Failed)
> Repeaded "hand-export" suggests there is a never-ending di
On Sat, Jan 12, 2019 at 11:23:31AM -0500, Richard Kimberly Heck wrote:
> Fine for stable, then.
Committed.
--
Enrico
On 1/12/19 6:33 AM, Enrico Forestieri wrote:
> On Wed, Jan 09, 2019 at 04:46:51PM +0100, Enrico Forestieri wrote:
>> On Tue, Jan 08, 2019 at 05:55:42PM -0500, Richard Kimberly Heck wrote:
>>> I'd guess maybe somehow we should store the full path to the 'right'
>>> Python interpreter, but I'm far fr
On Wed, Jan 09, 2019 at 04:46:51PM +0100, Enrico Forestieri wrote:
> On Tue, Jan 08, 2019 at 05:55:42PM -0500, Richard Kimberly Heck wrote:
> > I'd guess maybe somehow we should store the full path to the 'right'
> > Python interpreter, but I'm far from sure about that. Maybe Enrico can
> > help us
On Fri, Jan 11, 2019 at 02:30:06PM -0500, Richard Kimberly Heck wrote:
> On 1/11/19 12:26 PM, Enrico Forestieri wrote:
> > I added the missing call to replaceEnvironmentPath() at 472bdf59.
> > Let's see whether this solves this kind of issues.
> > Ok for stable?
>
> Yes, thank you.
Done.
--
Enr
properly. Please reconfigure again if needed."|
>>>> |
>>>> |
>>>> |The problem seems to be the same as described in
>>>> https://stackoverflow.com/questions/27196811/lyx-system-reconfiguration-failure.
>>>> The solution of Pete P (an
> |
> > > |
> > > |The problem seems to be the same as described in
> > > https://stackoverflow.com/questions/27196811/lyx-system-reconfiguration-failure.
> > > The solution of Pete P (answer from Nov 30, 2016) worked for me.|
> > > |
> > > |
> >
t an error "|The
> > system reconfiguration has failed. Default textclass is used but LyX
> > may not be able to work properly. Please reconfigure again if needed."|
> > |
> > |
> > |The problem seems to be the same as described in
> > https://stackoverflow.com/questi
e able to work properly. Please reconfigure again if needed."|
> |
> |
> |The problem seems to be the same as described in
> https://stackoverflow.com/questions/27196811/lyx-system-reconfiguration-failure.
> The solution of Pete P (answer from Nov 30, 2016) worked for me.|
> |
he problem seems to be the same as described in
https://stackoverflow.com/questions/27196811/lyx-system-reconfiguration-failure.
The solution of Pete P (answer from Nov 30, 2016) worked for me.
Nevertheless, I am reporting it because I did not see it appear on the bug
tracker.
Best,Sivan
Am 10.01.2018 um 09:57 schrieb Pavel Sanda:
Change your git config, so your commiter name is not uwesto...@web.de but
uwesto...@lyx.org .
Many thanks Pavel. I did this now. I see that my lyx.org address is
already subscribed to lyx-cvs. I see that all mails from lyx-cvs are
automatically pus
Uwe Stöhr wrote:
> What do others do? I mean I don't like to get a mail for every commit since
Change your git config, so your commiter name is not uwesto...@web.de but
uwesto...@lyx.org .
https://help.github.com/articles/setting-your-commit-email-address-in-git/
Pavel
On 2018-01-10, Uwe Stöhr wrote:
> My PC broke and I jot a new one. Therefore I had to setup everything new
> from scratch. I can commit but now I get for every commit this error
> message:
>
> Hi. This is the qmail-send program at thales.memphis.edu.
> I'm afraid I wasn't able t
My PC broke and I jot a new one. Therefore I had to setup everything new
from scratch. I can commit but now I get for every commit this error
message:
Hi. This is the qmail-send program at thales.memphis.edu.
I'm afraid I wasn't able to deliver your message to the following add
Am Freitag, den 13.10.2017, 11:45 -0400 schrieb Scott Kostyshak:
> On Fri, Oct 13, 2017 at 09:10:11AM +, Jürgen Spitzmüller wrote:
> > Am Freitag, den 13.10.2017, 10:57 +0200 schrieb Helge Hafting:
> > >
> > > Den 13. okt. 2017 10:10, skrev Jürgen Spitzmüller:
> > > > Helge, can you please sti
On Fri, Oct 13, 2017 at 09:10:11AM +, Jürgen Spitzmüller wrote:
> Am Freitag, den 13.10.2017, 10:57 +0200 schrieb Helge Hafting:
> >
> > Den 13. okt. 2017 10:10, skrev Jürgen Spitzmüller:
> > > Helge, can you please still verify whether this fixes your problem?
> >
> > Yes, the patch fixes my
Am Freitag, den 13.10.2017, 10:57 +0200 schrieb Helge Hafting:
>
> Den 13. okt. 2017 10:10, skrev Jürgen Spitzmüller:
> > Helge, can you please still verify whether this fixes your problem?
>
> Yes, the patch fixes my problem. LyX 2.3 now used my format 60
> layout
> file with no problems at all
Den 13. okt. 2017 10:10, skrev Jürgen Spitzmüller:
Helge, can you please still verify whether this fixes your problem?
Yes, the patch fixes my problem. LyX 2.3 now used my format 60 layout
file with no problems at all.
Helge Hafting
Am Donnerstag, den 12.10.2017, 13:47 +0200 schrieb Jürgen Spitzmüller:
> 2017-10-12 11:38 GMT+02:00 Helge Hafting:
> > If there is a problem in layout2layout, finding it may be useful
> > before release?
> >
>
> Yes. Can you try if the attached patch fixes the problem?
I have pushed the patch to
Am Donnerstag, 12. Oktober 2017 um 13:47:09, schrieb Jürgen Spitzmüller
> 2017-10-12 11:38 GMT+02:00 Helge Hafting:
>
> > If there is a problem in layout2layout, finding it may be useful before
> > release?
> >
>
> Yes. Can you try if the attached patch fixes the problem?
>
> Jürgen
>
>
> >
2017-10-12 11:38 GMT+02:00 Helge Hafting:
> If there is a problem in layout2layout, finding it may be useful before
> release?
>
Yes. Can you try if the attached patch fixes the problem?
Jürgen
>
>
> Helge Hafting
>
>
diff --git a/lib/scripts/layout2layout.py b/lib/scripts/layout2layout.py
ind
I compiled lyx 2.3 this week (from git). Today, I opened a file using
one of my own layouts, and got a failure to convet the layout file from
version 60 to version 64.
Assuming the format change is about new features (and not depreciation
of old stuff), I simply changed the version number
On Sun, Mar 12, 2017 at 11:21:33PM -0400, Scott Kostyshak wrote:
> On Wed, Aug 10, 2016 at 04:57:12PM -0400, Scott Kostyshak wrote:
> > On Thu, Jun 09, 2016 at 02:30:42AM +0200, Shankar Giri Venkita Giri wrote:
> > > Thanks Pavel.
> > >
> > > I'll try to produce a patch for #1. Then both #1 and #
Hi Devel-List,
I'm not sure if this is related to Biblatex/biber also going through an
update cycle the last week or so, but I suspect it's more likely related to
Lyx (as that was just released and the errors started afterwards).
I have a fairly large, complex file that is failing on xelatex pdf
Le 15/05/2017 à 10:31, Jean-Marc Lasgouttes a écrit :
commit 676ce147da9f5873b4177a0cc3dd706005dd0690
Author: Jean-Marc Lasgouttes
Date: Mon May 15 10:29:09 2017 +0200
Fix compilation failure
---
src/frontends/qt4/qt_helpers.h |2 ++
1 files changed, 2 insertions(+), 0 deletions
On Wed, Aug 10, 2016 at 04:57:12PM -0400, Scott Kostyshak wrote:
> On Thu, Jun 09, 2016 at 02:30:42AM +0200, Shankar Giri Venkita Giri wrote:
> > Thanks Pavel.
> >
> > I'll try to produce a patch for #1. Then both #1 and #2, after
> > review, can go into master/branch. I play around in FreeBSD
>
1 - 100 of 1082 matches
Mail list logo
