Re: local layout file + relative inputs?

[Ulrich Thomas Gabor]

Hi

> Am 28.02.2017 um 22:11 schrieb Enrico Forestieri :
> 
> On Tue, Feb 28, 2017 at 09:26:31AM -0500, Richard Heck wrote:
>> On 02/28/2017 04:36 AM, Ulrich Thomas Gabor wrote:
>>> Hi
>>> 
>>> Since nobody replied on the normal users lists, maybe someone here can tell
>>> me if it is possible to reference an include from a layout file relatively? 
>> 
>> Probably not. These "local layout" files were always a hack, and really
>> a bad idea. If you file a bug report, we can perhaps make import work.
> 
> The attached patch works for me. When the path for Input is explicitly
> relative (i.e., it starts with ./ or ../), the path is considered to
> be relative to the document directory, but only when the layout is loaded
> from a local file. So,
> 
> Input name.inc
> 
> always searches first in the user directory and then in the system one,
> even when used in a local layout file. But
> 
> Input ./name.inc
> 
> will try to load the file name.inc in the document directory. If the layout
> is a system one, the above two commands are equivalent and name.inc is
> always searched as usual.

Thanks for patching this!
By "relative to the document directory" do you mean the directory the lyx file 
is in or the layout file is in? Because I think it should be relative from the 
layout file.
Layout and include files form kind of a bundle, which may regularly be crafted 
by the same person. The lyx file instead is likely created by another person 
and should not know if the layout is one file or broken down into includes.

Best
Ulrich


> 
> -- 
> Enrico
> 

Re: [LyX/master] Ignore missing glyphs in a test after TL update

[Scott Kostyshak]

On Wed, Mar 01, 2017 at 12:32:35AM +0100, Scott Kostyshak wrote:
> commit 34d2f3cf06db9e5988d26ef45ac6b02cb23379e3
> Author: Scott Kostyshak 
> Date:   Tue Feb 28 18:31:02 2017 -0500
> 
> Ignore missing glyphs in a test after TL update
> 
> After a TL 2016 update, a test started to fail due to missing
> glyphs. For more information, see the ML thread here:
> 
>   
> https://www.mail-archive.com/search?l=mid=20170225203955.nas2qopy4l4ukyqq%40steph

The test still fails for me. I tested manually and the missing glyphs
are the only errors I get. What else should I do?

Scott


signature.asc
Description: PGP signature

Re: iconv error with listing + Spanish

[Scott Kostyshak]

On Tue, Feb 28, 2017 at 06:24:51PM -0500, Scott Kostyshak wrote:
> On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:
> 
> > Note that this affects lib/examples/es/linguistics.lyx
> > 
> > Can anyone else reproduce? Is the problem obvious?
> > 
> > I can reproduce the issue on 2.2.0 and on master. I cannot reproduce on
> > 2.1.0. I can do a git bisect if someone thinks the time would be worth
> > it.
> 
> Perhaps this is http://www.lyx.org/trac/ticket/9871 ?
> I inverted the affected test.
> 
> But that issue is not labeled as a regression. Why does the MWE work
> with 2.1.0?

The commit that changed the behavior was 36b9645b.

Günter, can you confirm that the export just worked by chance (perhaps
even bad output?) before, so that 36b9645b did not really break the
export? I have a vague memory that this is the case, but I want to
double-check.

Scott


signature.asc
Description: PGP signature

Re: local layout file + relative inputs?

[Richard Heck]

On 02/28/2017 04:11 PM, Enrico Forestieri wrote:
> On Tue, Feb 28, 2017 at 09:26:31AM -0500, Richard Heck wrote:
>> On 02/28/2017 04:36 AM, Ulrich Thomas Gabor wrote:
>>> Hi
>>>
>>> Since nobody replied on the normal users lists, maybe someone here can tell
>>> me if it is possible to reference an include from a layout file relatively? 
>> Probably not. These "local layout" files were always a hack, and really
>> a bad idea. If you file a bug report, we can perhaps make import work.
> The attached patch works for me. When the path for Input is explicitly
> relative (i.e., it starts with ./ or ../), the path is considered to
> be relative to the document directory, but only when the layout is loaded
> from a local file. So,
>
> Input name.inc
>
> always searches first in the user directory and then in the system one,
> even when used in a local layout file. But
>
> Input ./name.inc
>
> will try to load the file name.inc in the document directory. If the layout
> is a system one, the above two commands are equivalent and name.inc is
> always searched as usual.

Very nice, thank you! If you want to commit to master, I will cherry
pick it for 2.2.3.

Richard

Re: TL update broke latex/languagenesting2_pdf5_systemF

[Scott Kostyshak]

On Sun, Feb 26, 2017 at 10:06:48PM +, Guenter Milde wrote:

> Of course it would be the simplest option for LyX, if this were fixed soon
> upstream. So reporting is in any case advisable.
> 
> However, if the LaTeX developers decline to see this as a bug or don't have
> the time to fix this before the next TeXLive release, LyX should add a
> workaround.

In the mean time, I added the test to the list of tests that ignore
missing glyph errors at 34d2f3cf.

Scott


signature.asc
Description: PGP signature

Re: iconv error with listing + Spanish

[Scott Kostyshak]

On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:

> Note that this affects lib/examples/es/linguistics.lyx
> 
> Can anyone else reproduce? Is the problem obvious?
> 
> I can reproduce the issue on 2.2.0 and on master. I cannot reproduce on
> 2.1.0. I can do a git bisect if someone thinks the time would be worth
> it.

Perhaps this is http://www.lyx.org/trac/ticket/9871 ?
I inverted the affected test.

But that issue is not labeled as a regression. Why does the MWE work
with 2.1.0?

Scott


signature.asc
Description: PGP signature

Re: local layout file + relative inputs?

[Enrico Forestieri]

On Tue, Feb 28, 2017 at 09:26:31AM -0500, Richard Heck wrote:
> On 02/28/2017 04:36 AM, Ulrich Thomas Gabor wrote:
> > Hi
> >
> > Since nobody replied on the normal users lists, maybe someone here can tell
> > me if it is possible to reference an include from a layout file relatively? 
> 
> Probably not. These "local layout" files were always a hack, and really
> a bad idea. If you file a bug report, we can perhaps make import work.

The attached patch works for me. When the path for Input is explicitly
relative (i.e., it starts with ./ or ../), the path is considered to
be relative to the document directory, but only when the layout is loaded
from a local file. So,

Input name.inc

always searches first in the user directory and then in the system one,
even when used in a local layout file. But

Input ./name.inc

will try to load the file name.inc in the document directory. If the layout
is a system one, the above two commands are equivalent and name.inc is
always searched as usual.

-- 
Enrico
diff --git a/src/LayoutFile.cpp b/src/LayoutFile.cpp
index 771a9c4..ccf2838 100644
--- a/src/LayoutFile.cpp
+++ b/src/LayoutFile.cpp
@@ -43,7 +43,8 @@ LayoutFile::LayoutFile(string const & fn, string const & cln,
   string const & desc, string const & prereq,
   string const & category, bool texclassavail) 
 {
-   name_ = fn;
+   name_ = onlyFileName(fn);
+   path_ = fn.rfind('/') == string::npos ? string() : onlyPath(fn);
latexname_ = cln;
description_ = desc;
prerequisites_ = prereq;
@@ -331,7 +332,8 @@ LayoutFileIndex  LayoutFileList::addLocalLayout(
return string();
 
LayoutFile * tmpl =
-   new LayoutFile(textclass, class_name, textclass, class_prereq, 
category, true);
+   new LayoutFile(addName(moved ? oldpath : path, textclass),
+   class_name, textclass, class_prereq, category, true);
//FIXME: The prerequisites are available from the layout file and
//   can be extracted from the above regex, but for now this
//   field is simply set to class_name + ".cls"
diff --git a/src/TextClass.cpp b/src/TextClass.cpp
index 34b55fa..b127f24 100644
--- a/src/TextClass.cpp
+++ b/src/TextClass.cpp
@@ -463,8 +463,13 @@ TextClass::ReturnValues TextClass::read(Lexer & lexrc, 
ReadType rt)
 
case TC_INPUT: // Include file
if (lexrc.next()) {
+   FileName tmp;
string const inc = lexrc.getString();
-   FileName tmp = libFileSearch("layouts", inc,
+   if (!path().empty() && (prefixIs(inc, "./") ||
+   prefixIs(inc, "../")))
+   tmp = fileSearch(path(), inc, "layout");
+   else
+   tmp = libFileSearch("layouts", inc,
"layout");
 
if (tmp.empty()) {
diff --git a/src/TextClass.h b/src/TextClass.h
index 56a61da..b84179f 100644
--- a/src/TextClass.h
+++ b/src/TextClass.h
@@ -194,6 +194,8 @@ public:
///
std::string const & name() const { return name_; }
///
+   std::string const & path() const { return path_; }
+   ///
std::string const & category() const { return category_; }
///
std::string const & description() const { return description_; }
@@ -242,6 +244,8 @@ protected:
mutable LayoutList layoutlist_;
/// Layout file name
std::string name_;
+   /// Layout file path (empty for system layout files)
+   std::string path_;
/// Class category
std::string category_;
/// document class name

Re: lyx errors with lualatex and non-tex fonts

[Scott Kostyshak]

> > export/export/latex/languagenesting2_pdf5_systemF (Failed)

This one is being discussed in a separate thread. I think the plan is to
invert and possibly (we have no volunteer) report a bug

> > UNRELIABLE.WRONG_OUTPUT_export/examples/es/linguistics_pdf4_texF (Failed)

I just started a new thread for this one. I think the inversion status
was changed at d319976, but I think there is a bug that causes the
failure that hopefully we can fix.

Scott


signature.asc
Description: PGP signature

iconv error with listing + Spanish

[Scott Kostyshak]

To reproduce, either use the attached MWE, or do the following:

1. create a new program listing.
2. enter "abc"
3. In Document > Settings > Language change to "Spanish".

Export to XeLaTeX (either the TeX or the PDF).

I get messages like the following in the terminal:

Error 84 returned from iconv when converting from UCS-4LE to ascii: Invalid or 
incomplete multibyte or wide character
Converted input: 0x005c 0x0062 0x0061 0x0074 0x0063 0x0068 0x006d 0x006f 0x0064 
0x0065 0x000a 0x005c 0x006d 0x0061 0x006b 0x0065 0x0061 0x0074 0x006c 0x0065 
0x0074 0x0074 0x0065 0x0072 0x000a 0x005c 0x0064 0x0065 0x0066 0x005c 0x0069 
0x006e 0x0070 0x0075 0x0074 0x0040 0x0070 0x0061 0x0074 0x0068 0x007b 0x007b 
0x002f 0x0068 0x006f 0x006d 0x0065 0x002f 0x0073 0x0063 0x006f 0x0074 0x0074 
0x002f 0x0044 0x0065 0x0073 0x006b 0x0074 0x006f 0x0070 0x002f 0x006d 0x0077 
0x0065 0x002f 0x007d 0x007d 0x000a 0x005c 0x006d 0x0061 0x006b 0x0065 0x0061 
0x0074 0x006f 0x0074 0x0068 0x0065 0x0072 0x000a 0x005c 0x0064 0x006f 0x0063 
0x0075 0x006d 0x0065 0x006e 0x0074 0x0063 0x006c 0x0061 0x0073 0x0073 0x005b 
0x0073 0x0070 0x0061 0x006e 0x0069 0x0073 0x0068 0x005d 0x007b 0x0061 0x0072 
0x0074 0x0069 0x0063 0x006c 0x0065 0x007d 0x000a 0x005c 0x0075 0x0073 0x0065 
0x0070 0x0061 0x0063 0x006b 0x0061 0x0067 0x0065 0x005b 0x0054 0x0031 0x005d 
0x007b 0x0066 0x006f 0x006e 0x0074 0x0065 0x006e 0x0063 0x007d 0x000a 0x005c 
0x0075 0x0073 0x0065 0x0070 0x0061 0x0063 0x006b 0x0061 0x0067 0x0065 0x007b 
0x0062 0x0061 0x0062 0x0065 0x006c 0x007d 0x000a 0x005c 0x0061 0x0064 0x0064 
0x0074 0x006f 0x005c 0x0073 0x0068 0x006f 0x0072 0x0074 0x0068 0x0061 0x006e 
0x0064 0x0073 0x0073 0x0070 0x0061 0x006e 0x0069 0x0073 0x0068 0x007b 0x005c 
0x0073 0x0070 0x0061 0x006e 0x0069 0x0073 0x0068 0x0064 0x0065 0x0061 0x0063 
0x0074 0x0069 0x0076 0x0061 0x0074 0x0065 0x007b 0x007e 0x003c 0x003e 0x007d 
0x007d 0x000a 0x000a 0x005c 0x0075 0x0073 0x0065 0x0070 0x0061 0x0063 0x006b 
0x0061 0x0067 0x0065 0x007b 0x006c 0x0069 0x0073 0x0074 0x0069 0x006e 0x0067 
0x0073 0x007d 0x000a 0x005c 0x0072 0x0065 0x006e 0x0065 0x0077 0x0063 0x006f 
0x006d 0x006d 0x0061 0x006e 0x0064 0x007b 0x005c 0x006c 0x0073 0x0074 0x006c 
0x0069 0x0073 0x0074 0x0069 0x006e 0x0067 0x006e 0x0061 0x006d 0x0065 0x007d 
0x007b 0x004c 0x0069 0x0073 0x0074 0x0061 0x0064 0x006f 0x0020 0x0064 0x0065 
0x0020 0x0063
Stopped at: 0x00f3
Unconverted input: 0x0064 0x0069 0x0067 0x006f 0x007d 0x000a 0x000a 0x005c 
0x0062 0x0065 0x0067 0x0069 0x006e 0x007b 0x0064 0x006f 0x0063 0x0075 0x006d 
0x0065 0x006e 0x0074 0x007d 0x000a

Note that this affects lib/examples/es/linguistics.lyx

Can anyone else reproduce? Is the problem obvious?

I can reproduce the issue on 2.2.0 and on master. I cannot reproduce on
2.1.0. I can do a git bisect if someone thinks the time would be worth
it.

Scott
#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options true
\maintain_unincluded_children false
\language spanish
\language_package default
\inputencoding auto
\fontencoding global
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 1
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language french
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Standard
\begin_inset listings
inline false
status open

\begin_layout Plain Layout

abc
\end_layout

\end_inset


\end_layout

\end_body
\end_document


signature.asc
Description: PGP signature

Re: lyx errors with lualatex and non-tex fonts

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 13:13:28, schrieb Scott Kostyshak 

> On Tue, Feb 28, 2017 at 11:06:06AM +0100, Kornel Benko wrote:
> 
> > Failed 20, out of 3973. Tested '-L export -E "xhtml|lyx16|lyx21|lyx22"'
> > 317 - export/export/latex/languagenesting2_pdf5_systemF (Failed)
> > 2450 - export/doc/he/Intro_dvi (Failed)
> > 2453 - export/doc/he/Intro_pdf (Failed)
> > 2454 - export/doc/he/Intro_pdf2 (Failed)
> > 2455 - export/doc/he/Intro_pdf3 (Failed)
> > 2466 - export/doc/he/Tutorial_dvi (Failed)
> > 2469 - export/doc/he/Tutorial_pdf (Failed)
> > 2470 - export/doc/he/Tutorial_pdf2 (Failed)
> > 2471 - export/doc/he/Tutorial_pdf3 (Failed)
> > 5049 - export/examples/he/example_lyxified_dvi (Failed)
> > 5052 - export/examples/he/example_lyxified_pdf (Failed)
> > 5053 - export/examples/he/example_lyxified_pdf2 (Failed)
> > 5054 - export/examples/he/example_lyxified_pdf3 (Failed)
> > 5065 - export/examples/he/example_raw_dvi (Failed)
> > 5068 - export/examples/he/example_raw_pdf (Failed)
> > 5069 - export/examples/he/example_raw_pdf2 (Failed)
> > 5070 - export/examples/he/example_raw_pdf3 (Failed)
> > 5084 - export/examples/he/splash_pdf (Failed)
> > 5085 - export/examples/he/splash_pdf2 (Failed)
> > 5086 - export/examples/he/splash_pdf3 (Failed)
> > 
> > Not one was unreliable. Here modernCV now compiles. Font awesome is from 
> > TL2016.
> > (It was my error using awesome installed from the ubuntu packages)
> 
> I get the following on a1faa41c:
> 
> 2 tests failed out of 6418:
> 
> export/export/latex/languagenesting2_pdf5_systemF (Failed)
> UNRELIABLE.WRONG_OUTPUT_export/examples/es/linguistics_pdf4_texF (Failed)

Confirmed with actual TL2016 and actual lyx.

> Scott

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Working on CI job that runs automated tests

[Scott Kostyshak]

On Tue, Feb 28, 2017 at 09:31:33AM +0100, Kornel Benko wrote:
> Am Montag, 27. Februar 2017 um 18:28:28, schrieb Pavel Sanda 
> > Christian Ridderström wrote:
> > > Hi,
> > > 
> > > This is a CI job I'm working on that's intended to run automated tests:
> > > 
> > >https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/
> > 
> > How often do you intend to run those?
> > While compile errs tend to get fixed quickly I see quite longer
> > fixing time for automated test (sometimes stuff needs to be discussed etc),
> > so we don't want to shout at mailling list every day about it.

Do you really think 1 email a day would be a bother? For me it would
not, but I understand that this is subjective.

> In contrary, it will show us pretty soon if a commit broke anything.

+1

I think the important thing is to note that the tests are only valid for
an up-to-date TL system. If the texlive packages are used from the
Ubuntu repos and no update is done, then I am sure there would be
failures. A tlmgr update needs to be run, e.g. every week. In fact,
every week or so I would recommend:

1. run the ctests
2. update with tlmgr
3. run the ctests again

That way we could see exactly which tests fail due to the tlmgr update.

Scott


signature.asc
Description: PGP signature

Re: lyx errors with lualatex and non-tex fonts

[Scott Kostyshak]

On Tue, Feb 28, 2017 at 11:06:06AM +0100, Kornel Benko wrote:

> Failed 20, out of 3973. Tested '-L export -E "xhtml|lyx16|lyx21|lyx22"'
>   317 - export/export/latex/languagenesting2_pdf5_systemF (Failed)
>   2450 - export/doc/he/Intro_dvi (Failed)
>   2453 - export/doc/he/Intro_pdf (Failed)
>   2454 - export/doc/he/Intro_pdf2 (Failed)
>   2455 - export/doc/he/Intro_pdf3 (Failed)
>   2466 - export/doc/he/Tutorial_dvi (Failed)
>   2469 - export/doc/he/Tutorial_pdf (Failed)
>   2470 - export/doc/he/Tutorial_pdf2 (Failed)
>   2471 - export/doc/he/Tutorial_pdf3 (Failed)
>   5049 - export/examples/he/example_lyxified_dvi (Failed)
>   5052 - export/examples/he/example_lyxified_pdf (Failed)
>   5053 - export/examples/he/example_lyxified_pdf2 (Failed)
>   5054 - export/examples/he/example_lyxified_pdf3 (Failed)
>   5065 - export/examples/he/example_raw_dvi (Failed)
>   5068 - export/examples/he/example_raw_pdf (Failed)
>   5069 - export/examples/he/example_raw_pdf2 (Failed)
>   5070 - export/examples/he/example_raw_pdf3 (Failed)
>   5084 - export/examples/he/splash_pdf (Failed)
>   5085 - export/examples/he/splash_pdf2 (Failed)
>   5086 - export/examples/he/splash_pdf3 (Failed)
> 
> Not one was unreliable. Here modernCV now compiles. Font awesome is from 
> TL2016.
> (It was my error using awesome installed from the ubuntu packages)

I get the following on a1faa41c:

2 tests failed out of 6418:

export/export/latex/languagenesting2_pdf5_systemF (Failed)
UNRELIABLE.WRONG_OUTPUT_export/examples/es/linguistics_pdf4_texF (Failed)

Scott


signature.asc
Description: PGP signature

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 5:06 PM, Enrico Forestieri  wrote:

> On Tue, Feb 28, 2017 at 03:29:37PM +0100, Liviu Andronic wrote:
> > This doesn't look right, as user:
> >
> > geek@liv-inspiron:~/Build/Devel/lyx$ which moc
> > /home/geek/anaconda3/bin/moc
> > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> > moc 5.6.0
> >
> > If I'm not wrong, 'anaconda3' has something to do with the Python
> install.
> > And I most definitely don't have Qt 5.6.0 installed via Synaptic.
> >
> > As root however I get something else:
> > root@liv-inspiron:/tmp# which moc
> > /usr/bin/moc
> > root@liv-inspiron:/tmp# moc -v
> > moc 5.2.1
> >
> > Is it possible that the recent Python packages I had installed have
> somehow
> > screwed my Qt setup?
>
> No, the problem you experiment is that you are using different PATH
> settings when you configure and later when you issue make. The
> configuration process looks for qtchooser and for a moc binary in the
> PATH, and only tries this moc binary if it is in the same directory as
> qtchooser. Otherwise either moc-qt4 or moc-qt5 are tried.
> Unfortunately, due to limitations of the AC_CHECK_PROGS macro, the
> the binaries are to be checked without their path, which is dropped.
> This means that, when you configure, the ~/anaconda3/bin is not in the
> PATH, so that the correct moc is spotted. But later, when you issue
> "make", the ~/anaconda3/bin is in the PATH and the wrong moc is used.
> You have to make sure that the PATH setting you use is the same for
> both configure and make.
>
>
Nicely spotted. I run ./configure from emelFM2, and make from bash (as it's
easier to kill the process if needed). Now the Anaconda install put this in
~/.bashrc:
geek@liv-inspiron:~/Build/Devel/lyx$ cat ~/.bashrc | grep -i anaconda

# added by Anaconda3 4.2.0 installer
export PATH="/home/geek/anaconda3/bin:$PATH"

Which explains the discrepancies. Sorry all for the noise. Now the
compilation advances much more nicely (though I still have `make distclean`
issues, and I'll start a new thread if this issue persists).

Thanks all,
Liviu



> --
> Enrico
>

Re: Working on CI job that runs automated tests

[Jean-Pierre Chrétien]

Le 27/02/2017 à 09:48, Jean-Pierre Chrétien a écrit :



I proposed recently to add something about this,  as I made a list of 
dependencies that are not in TL.


Here is the tds of the additional LaTeX stuff which is not un TL2016 and is 
needed to run ctest on unreliable templates and examples files.


http://dl.free.fr/rjsiLvxLE

The agutex.cls package is missing, I could not find it as it is obsoleted by 
agujournal.cls.


Attached is the listing of the files.

--
Jean-Pierre

Archive:  tds_neededForUnreliable.zip
  Length  DateTimeName
-  -- -   
0  2017-02-07 18:08   tex/latex/foiltex/
 3718  2017-02-07 18:03   tex/latex/foiltex/foil20.clo
 2385  2017-02-07 18:03   tex/latex/foiltex/foils.sty
 3208  2017-02-07 18:03   tex/latex/foiltex/foilshrt.clo
 3884  2017-02-07 18:03   tex/latex/foiltex/foil17.clo
11604  2017-02-07 18:03   tex/latex/foiltex/fltfonts.def
 3831  2017-02-07 18:03   tex/latex/foiltex/foil25.clo
 3888  2017-02-07 18:03   tex/latex/foiltex/foil30.clo
27886  2017-02-07 18:03   tex/latex/foiltex/foils.cls
0  2017-02-07 18:39   tex/latex/aa/
65331  2016-09-08 16:09   tex/latex/aa/aa.cls
0  2017-02-08 11:16   tex/latex/knitr/
  810  2013-11-03 21:59   tex/latex/knitr/knitr.sty
 2853  2013-11-03 21:59   tex/latex/knitr/Sweavel.sty
22449  2015-10-19 22:32   tex/latex/knitr/framed.sty
0  2017-02-08 17:46   tex/latex/springer/
0  2017-02-08 17:41   tex/latex/springer/templates/
 1735  2007-10-17 00:00   tex/latex/springer/templates/book.tex
  835  2007-06-29 00:00   tex/latex/springer/templates/acronym.tex
16074  2010-10-20 00:00   tex/latex/springer/templates/author.tex
  512  2007-06-29 00:00   tex/latex/springer/templates/acknow.tex
62739  2007-06-29 00:00   tex/latex/springer/templates/figure.eps
  535  2007-06-29 00:00   tex/latex/springer/templates/part.tex
  502  2007-06-29 00:00   tex/latex/springer/templates/dedic.tex
 8269  2007-06-29 00:00   tex/latex/springer/templates/referenc.tex
 3160  2007-06-29 00:00   tex/latex/springer/templates/appendix.tex
  321  2007-06-29 00:00   tex/latex/springer/templates/solutions.tex
 1307  2007-06-29 00:00   tex/latex/springer/templates/glossary.tex
14338  2007-10-17 00:00   tex/latex/springer/templates/chapter.tex
 1116  2007-06-29 00:00   tex/latex/springer/templates/preface.tex
  834  2007-06-29 00:00   tex/latex/springer/templates/foreword.tex
0  2011-02-22 14:31   tex/latex/springer/deutsch/
 1331  2007-06-29 00:00   tex/latex/springer/deutsch/liesmich.txt
  190  2007-06-29 00:00   tex/latex/springer/deutsch/svindd.ist
31706  2007-06-29 00:00   tex/latex/springer/quickstart.pdf
   118729  2008-06-24 00:00   tex/latex/springer/instruct.pdf
   123690  2008-06-24 00:00   tex/latex/springer/authinst.pdf
50988  2008-10-01 00:00   tex/latex/springer/usrguid3.dvi
   120184  2010-10-20 00:00   tex/latex/springer/authsamp.pdf
   190374  2008-10-01 00:00   tex/latex/springer/usrguid3.pdf
0  2011-03-14 14:48   tex/latex/springer/editor/
0  2011-03-14 14:48   tex/latex/springer/editor/templates/
  835  2007-06-29 00:00   tex/latex/springer/editor/templates/acronym.tex
16108  2010-10-20 00:00   tex/latex/springer/editor/templates/author.tex
  678  2007-06-29 00:00   tex/latex/springer/editor/templates/cblist.tex
  512  2007-06-29 00:00   tex/latex/springer/editor/templates/acknow.tex
62739  2007-06-29 00:00   tex/latex/springer/editor/templates/figure.eps
 1895  2007-06-29 00:00   tex/latex/springer/editor/templates/editor.tex
  535  2007-06-29 00:00   tex/latex/springer/editor/templates/part.tex
  493  2007-06-29 00:00   tex/latex/springer/editor/templates/dedic.tex
 8251  2007-06-29 00:00   tex/latex/springer/editor/templates/referenc.tex
 3181  2007-09-26 00:00   tex/latex/springer/editor/templates/appendix.tex
 1307  2007-06-29 00:00   tex/latex/springer/editor/templates/glossary.tex
 1082  2007-06-29 00:00   tex/latex/springer/editor/templates/preface.tex
  787  2007-06-29 00:00   tex/latex/springer/editor/templates/foreword.tex
   107317  2007-06-29 00:00   tex/latex/springer/editor/edinst.pdf
   126330  2010-10-20 00:00   tex/latex/springer/editor/edsamp.pdf
49110  2010-11-25 10:43   tex/latex/springer/svjour3.cls
 5509  2010-09-16 12:45   tex/latex/springer/template.tex
   173631  2017-02-08 17:17   tex/latex/springer/svjour3.zip
   623954  2011-09-15 11:49   tex/latex/springer/example.pdf
   190989  2007-06-29 00:00   tex/latex/springer/refguide.pdf
 1127  2010-11-25 10:31   tex/latex/springer/history.txt
28600  2004-11-08 11:50   tex/latex/springer/spphys.bst
0  2017-02-08 17:41   tex/latex/springer/styles/
33250  2007-06-29 00:00   tex/latex/springer/styles/spbasic.bst
  180  2007-06-29 00:00   tex/latex/springer/styles/svind.ist
68383  

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 4:11 PM, Kornel Benko  wrote:

> Am Dienstag, 28. Februar 2017 um 15:29:37, schrieb Liviu Andronic <
> landr...@lyx.org>
> > On Tue, Feb 28, 2017 at 3:20 PM, Kornel Benko  wrote:
> >
>
> ...
>
> > >
> > > Maybe the PATH env is not OK, or you have an alias for moc?
> > > # which moc
> > > /usr/bin/moc
> > > # moc -v
> > > Qt Meta Object Compiler version 63 (Qt 4.8.6)
> > >
> > >
> > This doesn't look right, as user:
> >
> > geek@liv-inspiron:~/Build/Devel/lyx$ which moc
> > /home/geek/anaconda3/bin/moc
> > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> > moc 5.6.0
> >
> > If I'm not wrong, 'anaconda3' has something to do with the Python
> install.
> > And I most definitely don't have Qt 5.6.0 installed via Synaptic.
> >
> > As root however I get something else:
> > root@liv-inspiron:/tmp# which moc
> > /usr/bin/moc
> > root@liv-inspiron:/tmp# moc -v
> > moc 5.2.1
> >
> > Is it possible that the recent Python packages I had installed have
> somehow
> > screwed my Qt setup?
>
> Remove /home/geek/anaconda3/bin from your PATH while configuring and
> compiling for QT4.
> Apparently root has PATH set without anaconda3.
>
>
Yes, I've just noticed this as well.

geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i anacon
PATH=/home/geek/anaconda3/bin:/home/geek/Build/Testing/
coverity/cov-analysis-linux64-7.6.0/bin:/usr/local/sbin:/
usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
It seems this was set when I installed Anaconda (for whatever reason). I'll
remove this and try again.

Liviu



> > Thanks,
> > Liviu
> >
> >
> >
> Kornel

Re: master GIT broken?

[Enrico Forestieri]

On Tue, Feb 28, 2017 at 03:29:37PM +0100, Liviu Andronic wrote:
> This doesn't look right, as user:
> 
> geek@liv-inspiron:~/Build/Devel/lyx$ which moc
> /home/geek/anaconda3/bin/moc
> geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> moc 5.6.0
> 
> If I'm not wrong, 'anaconda3' has something to do with the Python install.
> And I most definitely don't have Qt 5.6.0 installed via Synaptic.
> 
> As root however I get something else:
> root@liv-inspiron:/tmp# which moc
> /usr/bin/moc
> root@liv-inspiron:/tmp# moc -v
> moc 5.2.1
> 
> Is it possible that the recent Python packages I had installed have somehow
> screwed my Qt setup?

No, the problem you experiment is that you are using different PATH
settings when you configure and later when you issue make. The
configuration process looks for qtchooser and for a moc binary in the
PATH, and only tries this moc binary if it is in the same directory as
qtchooser. Otherwise either moc-qt4 or moc-qt5 are tried.
Unfortunately, due to limitations of the AC_CHECK_PROGS macro, the
the binaries are to be checked without their path, which is dropped.
This means that, when you configure, the ~/anaconda3/bin is not in the
PATH, so that the correct moc is spotted. But later, when you issue
"make", the ~/anaconda3/bin is in the PATH and the wrong moc is used.
You have to make sure that the PATH setting you use is the same for
both configure and make.

-- 
Enrico

Re: master GIT broken?

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 15:29:37, schrieb Liviu Andronic 

> On Tue, Feb 28, 2017 at 3:20 PM, Kornel Benko  wrote:
> 

...

> >
> > Maybe the PATH env is not OK, or you have an alias for moc?
> > # which moc
> > /usr/bin/moc
> > # moc -v
> > Qt Meta Object Compiler version 63 (Qt 4.8.6)
> >
> >
> This doesn't look right, as user:
> 
> geek@liv-inspiron:~/Build/Devel/lyx$ which moc
> /home/geek/anaconda3/bin/moc
> geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> moc 5.6.0
> 
> If I'm not wrong, 'anaconda3' has something to do with the Python install.
> And I most definitely don't have Qt 5.6.0 installed via Synaptic.
> 
> As root however I get something else:
> root@liv-inspiron:/tmp# which moc
> /usr/bin/moc
> root@liv-inspiron:/tmp# moc -v
> moc 5.2.1
> 
> Is it possible that the recent Python packages I had installed have somehow
> screwed my Qt setup?

Remove /home/geek/anaconda3/bin from your PATH while configuring and compiling 
for QT4.
Apparently root has PATH set without anaconda3.

> Thanks,
> Liviu
> 
> 
> 
Kornel

signature.asc
Description: This is a digitally signed message part.

Re: master GIT broken?

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 15:37:16, schrieb Liviu Andronic 

> On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benko  wrote:
> 
> > Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic <
> > landr...@lyx.org>
> > > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes <
> > lasgout...@lyx.org>
> > > wrote:
> > >
> > > > Le 28/02/2017 à 14:45, Liviu Andronic a écrit :
> > > >
> > > >> Not sure how to proceed next.
> > > >>
> > > >
> > > > A few questions:
> > > >
> > > > - do you have only one moc binary?
> > > >
> > >
> > > geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc*
> > > lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser
> > > lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 ->
> > > ../lib/x86_64-linux-gnu/qt4/bin/moc
> > >
> > >
> > > > - do you have qt4 and qt5 in parallel ?
> > > >
> > >
> > > Yes. Qt 4.8.6 and 5.2.1.
> > >
> > >
> > >
> > > > - what are the options that moc accepts?
> > > >
> > > >
> > > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> > > moc 5.6.0
> >
> >  That's it.
> >
> > I have also both installed, but can switch in between with
> > setting the environment QT_SELECT
> > # setenv QT_SELECT qt5
> > # moc -v
> > moc 5.2.1
> >
> >
> Hmm, I don't have `setenv` here. Which package did you install to get it?
> 

That is tcsh syntax. For 'sh' it simply is 'export QT_SELECT=qt5'

> Liviu

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: local layout file + relative inputs?

[Ulrich Thomas Gabor]

Hi

> Am 28.02.2017 um 15:26 schrieb Richard Heck :
> 
> On 02/28/2017 04:36 AM, Ulrich Thomas Gabor wrote:
>> Hi
>> 
>> Since nobody replied on the normal users lists, maybe someone here can tell 
>> me if it is possible to reference an include from a layout file relatively? 
> 
> Probably not. These "local layout" files were always a hack, and really
> a bad idea. If you file a bug report, we can perhaps make import work.

Why do you think they are a bad idea? I do not see how to distribute versioned 
layout files another way?

I tried dropping them into ~/Library/Application Support/LyX-2.2/layouts (on a 
mac), but they are not found, even after a reconfigure. This is also only a 
possibility, if subdirectories are transparent there, because versioning the 
whole layouts directory in one VCS repository is not an option, if one wants to 
drop two VCS repositories there.

If there is a better way to do it, I'd be happy to hear about it.

Best
Ulrich


> 
> Richard
> 
> 
>> See the mail I sent to the users list:
>> 
>>> Am 26.02.2017 um 15:59 schrieb Ulrich Thomas Gabor 
>>> :
>>> 
>>> Hi
>>> 
>>> I have a local layout file, which I reference as "Local Layout" with a 
>>> relative path (../templates/my.layout). Now I want to clean up the layout 
>>> and move some parts into a separate include file for reuse. My wish is to 
>>> create an include file next to the layout file (../templates/my.inc) and 
>>> reference it from the layout-file, but this does not work, i.e. the include 
>>> file is not found. Neither "input my.inc" nor "input ../templates/my.inc" 
>>> works, presumably because LyX copies the layout file to a temp directory 
>>> and the inc file is ignored.
>>> 
>>> How can I get this constellation to work?
>>> 
>>> Thanks in advance for hints into the right direction!
>>> 
>>> Best
>>> Ulrich
>> I do not want to drop the includes in the system directories, because the 
>> lyx files and the layout/include files are versioned and should stay closely 
>> together.
>> 
>> Can someone give me a hint, if this is possible at all?
>> 
>> Best
>> Ulrich
>> 
> 

--
Ulrich Thomas Gabor, M.Sc.
Technische Universität Dortmund
Informatik, Lehrstuhl 12
Otto-Hahn-Str. 16, E09
44227 Dortmund, Germany

Phone:  +49 231 / 755-6263
Fax:+49 231 / 755-6116
http://ess.cs.tu-dortmund.de/~ug

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 3:48 PM, Liviu Andronic  wrote:

>
>
> On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benko  wrote:
>
>> Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic <
>> landr...@lyx.org>
>> > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes <
>> lasgout...@lyx.org>
>>
>
> > >
>> > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
>> > moc 5.6.0
>>
>>  That's it.
>>
>> I have also both installed, but can switch in between with
>> setting the environment QT_SELECT
>> # setenv QT_SELECT qt5
>> # moc -v
>> moc 5.2.1
>>
>>
> For some reason this doesn't seem to have an effect here:
>
> geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4
> geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_sel
> QT_SELECT=qt4
> geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> moc 5.6.0
>
>
So this won't work for user, it will work for root:

root@liv-inspiron:/tmp# export QT_SELECT=qt4
root@liv-inspiron:/tmp# env | grep -i qt_sel
QT_SELECT=qt4
root@liv-inspiron:/tmp# moc -v
Qt Meta Object Compiler version 63 (Qt 4.8.6)
root@liv-inspiron:/tmp# export QT_SELECT=qt5
root@liv-inspiron:/tmp# moc -v
moc 5.2.1

I'm stumped.

Liviu



> Liviu
>
>
>> Kornel
>
>
>

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benko  wrote:

> Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic <
> landr...@lyx.org>
> > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes <
> lasgout...@lyx.org>
>

> >
> > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> > moc 5.6.0
>
>  That's it.
>
> I have also both installed, but can switch in between with
> setting the environment QT_SELECT
> # setenv QT_SELECT qt5
> # moc -v
> moc 5.2.1
>
>
For some reason this doesn't seem to have an effect here:

geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4
geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_sel
QT_SELECT=qt4
geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
moc 5.6.0

Liviu


> Kornel

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 3:29 PM, Kornel Benko  wrote:

> Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic <
> landr...@lyx.org>
> > On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes <
> lasgout...@lyx.org>
> > wrote:
> >
> > > Le 28/02/2017 à 14:45, Liviu Andronic a écrit :
> > >
> > >> Not sure how to proceed next.
> > >>
> > >
> > > A few questions:
> > >
> > > - do you have only one moc binary?
> > >
> >
> > geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc*
> > lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser
> > lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 ->
> > ../lib/x86_64-linux-gnu/qt4/bin/moc
> >
> >
> > > - do you have qt4 and qt5 in parallel ?
> > >
> >
> > Yes. Qt 4.8.6 and 5.2.1.
> >
> >
> >
> > > - what are the options that moc accepts?
> > >
> > >
> > geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> > moc 5.6.0
>
>  That's it.
>
> I have also both installed, but can switch in between with
> setting the environment QT_SELECT
> # setenv QT_SELECT qt5
> # moc -v
> moc 5.2.1
>
>
Hmm, I don't have `setenv` here. Which package did you install to get it?


Liviu



> Kornel

Re: master GIT broken?

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 15:08:33, schrieb Liviu Andronic 

> On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes 
> wrote:
> 
> > Le 28/02/2017 à 14:45, Liviu Andronic a écrit :
> >
> >> Not sure how to proceed next.
> >>
> >
> > A few questions:
> >
> > - do you have only one moc binary?
> >
> 
> geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc*
> lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser
> lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 ->
> ../lib/x86_64-linux-gnu/qt4/bin/moc
> 
> 
> > - do you have qt4 and qt5 in parallel ?
> >
> 
> Yes. Qt 4.8.6 and 5.2.1.
> 
> 
> 
> > - what are the options that moc accepts?
> >
> >
> geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
> moc 5.6.0

 That's it.

I have also both installed, but can switch in between with
setting the environment QT_SELECT
# setenv QT_SELECT qt5
# moc -v
moc 5.2.1

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 3:20 PM, Kornel Benko  wrote:

> Am Dienstag, 28. Februar 2017 um 14:45:06, schrieb Liviu Andronic <
> landr...@lyx.org>
> > On Tue, Feb 28, 2017 at 1:39 PM, Kornel Benko  wrote:
> >
> > > Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic <
> > > landr...@lyx.org>
>
> ...
>
> > Still no luck.
> >
> > geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4
> > geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_se
> > QT_SELECT=qt4
> > geek@liv-inspiron:~/Build/Devel/lyx$ make
> > [...]
> > Making all in src
> > make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
> > rm -f hash-temp \
> > @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1
> > --pretty=format:%H 2>/dev/null || echo none` ; \
> > sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp
> ; \
> > cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \
> > rm -f hash-temp
> > GEN moc_Compare.cpp
> > Unknown options: q, t, =, q, t, 4.
> > make[2]: *** [moc_Compare.cpp] Error 1
> > make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
> > make: *** [all] Error 2
>
> I am out of suggestions.
> I retried on clean build tree without any error.
> # cd 
> # /configure --bindir=/usr/local/bin
> --datarootdir=/usr/local/share/lyx2.3 --with-version-suffix=2.3
> # make
>
> Maybe the PATH env is not OK, or you have an alias for moc?
> # which moc
> /usr/bin/moc
> # moc -v
> Qt Meta Object Compiler version 63 (Qt 4.8.6)
>
>
This doesn't look right, as user:

geek@liv-inspiron:~/Build/Devel/lyx$ which moc
/home/geek/anaconda3/bin/moc
geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
moc 5.6.0

If I'm not wrong, 'anaconda3' has something to do with the Python install.
And I most definitely don't have Qt 5.6.0 installed via Synaptic.

As root however I get something else:
root@liv-inspiron:/tmp# which moc
/usr/bin/moc
root@liv-inspiron:/tmp# moc -v
moc 5.2.1

Is it possible that the recent Python packages I had installed have somehow
screwed my Qt setup?

Thanks,
Liviu



> Kornel

Re: local layout file + relative inputs?

[Richard Heck]

On 02/28/2017 04:36 AM, Ulrich Thomas Gabor wrote:
> Hi
>
> Since nobody replied on the normal users lists, maybe someone here can tell 
> me if it is possible to reference an include from a layout file relatively? 

Probably not. These "local layout" files were always a hack, and really
a bad idea. If you file a bug report, we can perhaps make import work.

Richard


> See the mail I sent to the users list:
>
>> Am 26.02.2017 um 15:59 schrieb Ulrich Thomas Gabor 
>> :
>>
>> Hi
>>
>> I have a local layout file, which I reference as "Local Layout" with a 
>> relative path (../templates/my.layout). Now I want to clean up the layout 
>> and move some parts into a separate include file for reuse. My wish is to 
>> create an include file next to the layout file (../templates/my.inc) and 
>> reference it from the layout-file, but this does not work, i.e. the include 
>> file is not found. Neither "input my.inc" nor "input ../templates/my.inc" 
>> works, presumably because LyX copies the layout file to a temp directory and 
>> the inc file is ignored.
>>
>> How can I get this constellation to work?
>>
>> Thanks in advance for hints into the right direction!
>>
>> Best
>> Ulrich
> I do not want to drop the includes in the system directories, because the lyx 
> files and the layout/include files are versioned and should stay closely 
> together.
>
> Can someone give me a hint, if this is possible at all?
>
> Best
> Ulrich
>

Re: master GIT broken?

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 14:45:06, schrieb Liviu Andronic 

> On Tue, Feb 28, 2017 at 1:39 PM, Kornel Benko  wrote:
> 
> > Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic <
> > landr...@lyx.org>

...

> Still no luck.
> 
> geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4
> geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_se
> QT_SELECT=qt4
> geek@liv-inspiron:~/Build/Devel/lyx$ make
> [...]
> Making all in src
> make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
> rm -f hash-temp \
> @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1
> --pretty=format:%H 2>/dev/null || echo none` ; \
> sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \
> cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \
> rm -f hash-temp
> GEN moc_Compare.cpp
> Unknown options: q, t, =, q, t, 4.
> make[2]: *** [moc_Compare.cpp] Error 1
> make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
> make: *** [all] Error 2

I am out of suggestions.
I retried on clean build tree without any error.
# cd 
# /configure --bindir=/usr/local/bin 
--datarootdir=/usr/local/share/lyx2.3 --with-version-suffix=2.3
# make

Maybe the PATH env is not OK, or you have an alias for moc?
# which moc
/usr/bin/moc
# moc -v
Qt Meta Object Compiler version 63 (Qt 4.8.6)

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 12:16 PM, Liviu Andronic  wrote:

> I have troubles compiling current GIT. Today I've updated from e7654d9 ->
> a1faa41, and all of a sudden master no longer compiles. Before the
> compilation failures I did a `make distclean` which worked fine.  I'm using
> libqt4-dev 4.8.5 on Ubuntu 14.04.
>

Also, I've done a git bisect, and I couldn't find any commit that I could
compile, i.e. I can't even compile e7654d9. Which points to something being
wrong on my system.

Liviu

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 2:58 PM, Jean-Marc Lasgouttes 
wrote:

> Le 28/02/2017 à 14:45, Liviu Andronic a écrit :
>
>> Not sure how to proceed next.
>>
>
> A few questions:
>
> - do you have only one moc binary?
>

geek@liv-inspiron:~/Build/Devel/lyx$ ls -l /usr/bin/moc*
lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser
lrwxrwxrwx 1 root root 35 May 27 2015 /usr/bin/moc-qt4 ->
../lib/x86_64-linux-gnu/qt4/bin/moc


> - do you have qt4 and qt5 in parallel ?
>

Yes. Qt 4.8.6 and 5.2.1.



> - what are the options that moc accepts?
>
>
geek@liv-inspiron:~/Build/Devel/lyx$ moc -v
moc 5.6.0
geek@liv-inspiron:~/Build/Devel/lyx$ moc --help
Usage: moc [options] [header-file] [@option-file]
Qt Meta Object Compiler version 67 (Qt 5.6.0)

Options:
-h, --help Displays this help.
-v, --version Displays version information.
-o  Write output to file rather than stdout.
-I  Add dir to the include path for header files.
-F  Add Mac framework to the include path for header
files.
-E Preprocess only; do not generate meta object code.
-D  Define macro, with optional definition.
-U  Undefine macro.
-M 

Re: master GIT broken?

[Jean-Marc Lasgouttes]

Le 28/02/2017 à 14:45, Liviu Andronic a écrit :

Not sure how to proceed next.


A few questions:

- do you have only one moc binary?
- do you have qt4 and qt5 in parallel ?
- what are the options that moc accepts?

JMarc

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 1:39 PM, Kornel Benko  wrote:

> Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic <
> landr...@lyx.org>
> > On Tue, Feb 28, 2017 at 1:07 PM, Kornel Benko  wrote:
> >
> > > Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic <
> > > landr...@lyx.org>
> > > > On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes <
> > > lasgout...@lyx.org>
> > > > wrote:
> > > >
> > > > > Le 28/02/2017 à 12:16, Liviu Andronic a écrit :
> > > > >
> > > > >> Dear all,
> > > > >> I have troubles compiling current GIT. Today I've updated from
> e7654d9
> > > > >> -> a1faa41, and all of a sudden master no longer compiles. Before
> the
> > > > >> compilation failures I did a `make distclean` which worked fine.
> I'm
> > > > >> using libqt4-dev 4.8.5 on Ubuntu 14.04.
>
> ...
>
> > And I'm still getting the same compilation failure:
> > Making all in src
> > make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
> > rm -f hash-temp \
> > @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1
> > --pretty=format:%H 2>/dev/null || echo none` ; \
> > sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp
> ; \
> > cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \
> > rm -f hash-temp
> > GEN moc_Compare.cpp
> > Unknown options: q, t, =, q, t, 4.
> > make[2]: *** [moc_Compare.cpp] Error 1
> > make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
> > make: *** [all] Error 2
> >
>
> I am using also 'export QT_SELECT=qt4" before compiling.
>
>

Still no luck.

geek@liv-inspiron:~/Build/Devel/lyx$ export QT_SELECT=qt4
geek@liv-inspiron:~/Build/Devel/lyx$ env | grep -i qt_se
QT_SELECT=qt4
geek@liv-inspiron:~/Build/Devel/lyx$ make
[...]
Making all in src
make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
rm -f hash-temp \
@echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1
--pretty=format:%H 2>/dev/null || echo none` ; \
sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \
cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \
rm -f hash-temp
GEN moc_Compare.cpp
Unknown options: q, t, =, q, t, 4.
make[2]: *** [moc_Compare.cpp] Error 1
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
make: *** [all] Error 2






> > And if I'm using JMarc's suggestion, I'm still getting the same error as
> > before:
>

I also tried supplying `moc-qt4` and the compilation gets farther, but
still fails:

geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc-qt4
[...]
Making all in frontends
make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/frontends'
Making all in qt4
make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/frontends/qt4'
GEN ui_AboutUi.h
Unknown option 'qt'.
make[5]: *** [ui_AboutUi.h] Error 1
make[5]: Leaving directory `/home/geek/Build/Devel/lyx/src/frontends/qt4'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/geek/Build/Devel/lyx/src/frontends'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/geek/Build/Devel/lyx/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
make: *** [all] Error 2


Not sure how to proceed next.

Liviu



>
> ...
>
> > > Yes, but I think that it is only because of previous compilation with
> qt5.
> > >
> > >
> > I can't be sure, but I don't think I ever compiled with Qt5 in this tree.
> > What's more, before updating GIT I did a full `make distclean` which
> > completed successfully, so the tree should be clean as far as past
> > compilations are concerned.
> >
> > Liviu
> >
>
> Kornel

Re: X-Apps

[Helge Hafting]

Den 10. jan. 2017 23:50, skrev Paul A. Rubin:
I saw the MIME configuration issue mentioned in the threads, but I 
thought that was the result of not using a desktop manager (see, for 
instance, this question 
), 
which would presumably leave the XDG_CURRENT_DESKTOP variable either 
unset or set to null. Perhaps I misunderstood the circumstances in 
which the funnel-everything-to-Firefox problem occurred.
FWIW, I tried xdg-open on arch linux. I don't run a desktop manager, 
only a window manager. There is no variable called XDG_CURRENT_DESKTOP. 
But xdg-open still open sensible viewers for pdf and png. In this case, 
"feh" for the png and "evince" for the pdf. A .lyx file was opened in 
vim though.


Helge Hafting

Re: master GIT broken?

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 13:31:42, schrieb Liviu Andronic 

> On Tue, Feb 28, 2017 at 1:07 PM, Kornel Benko  wrote:
> 
> > Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic <
> > landr...@lyx.org>
> > > On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes <
> > lasgout...@lyx.org>
> > > wrote:
> > >
> > > > Le 28/02/2017 à 12:16, Liviu Andronic a écrit :
> > > >
> > > >> Dear all,
> > > >> I have troubles compiling current GIT. Today I've updated from e7654d9
> > > >> -> a1faa41, and all of a sudden master no longer compiles. Before the
> > > >> compilation failures I did a `make distclean` which worked fine.  I'm
> > > >> using libqt4-dev 4.8.5 on Ubuntu 14.04.

...

> And I'm still getting the same compilation failure:
> Making all in src
> make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
> rm -f hash-temp \
> @echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1
> --pretty=format:%H 2>/dev/null || echo none` ; \
> sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \
> cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \
> rm -f hash-temp
> GEN moc_Compare.cpp
> Unknown options: q, t, =, q, t, 4.
> make[2]: *** [moc_Compare.cpp] Error 1
> make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
> make: *** [all] Error 2
> 

I am using also 'export QT_SELECT=qt4" before compiling.

> And if I'm using JMarc's suggestion, I'm still getting the same error as
> before:

...

> > Yes, but I think that it is only because of previous compilation with qt5.
> >
> >
> I can't be sure, but I don't think I ever compiled with Qt5 in this tree.
> What's more, before updating GIT I did a full `make distclean` which
> completed successfully, so the tree should be clean as far as past
> compilations are concerned.
> 
> Liviu
> 

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 1:07 PM, Kornel Benko  wrote:

> Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic <
> landr...@lyx.org>
> > On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes <
> lasgout...@lyx.org>
> > wrote:
> >
> > > Le 28/02/2017 à 12:16, Liviu Andronic a écrit :
> > >
> > >> Dear all,
> > >> I have troubles compiling current GIT. Today I've updated from e7654d9
> > >> -> a1faa41, and all of a sudden master no longer compiles. Before the
> > >> compilation failures I did a `make distclean` which worked fine.  I'm
> > >> using libqt4-dev 4.8.5 on Ubuntu 14.04.
> > >>
> > >
> > > Dear Liviu,
> > >
> > > What can you tell us about your 'moc' binary? What version of Qt is it
> > > from?
> > > It seems that it does not understand the '-qt=qt4' argument.
> > >
> > >
> > I'm using libqt4-dev 4.8.5 on Ubuntu 14.04. Previously compilations
> worked
> > fine, and I hadn't changed Qt version since.
> >
>
> So do I.
>
> >
> > > Do you have qtchooser installed? What does 'qtchooser -l' return?
> > >
> > >
> > geek@liv-inspiron:~/Build/Devel/lyx$ qtchooser -l
> > 4
> > 5
> > default
> > qt4-i386-linux-gnu
> > qt4-x86_64-linux-gnu
> > qt4
> > qt5-x86_64-linux-gnu
> > qt5
> >
> >
> > > Note that on my ancient ubuntu 12.04, I have
> > > QT_MOC=moc-qt4
> > >
> > > As a workaround for now, you can probably configure with QT_MOC=moc,
> or at
> > > least pass this to make.
> > >
> > >
> > Still getting an error, but a later one:
> > geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc
> > [...]
> > GEN moc_Compare.cpp
> > GEN moc_PreviewLoader.cpp
> > make all-recursive
> > make[3]: Entering directory `/home/geek/Build/Devel/lyx/src'
> > Making all in support
> > make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
> > moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h
> > moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h
> > make all-am
> > make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
> > CXX FileMonitor.o
> > CXX ConsoleApplication.o
> > In file included from ConsoleApplication.cpp:51:0:
> > moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was
> > generated using the moc from 5.6.0. It"
> > #error "This file was generated using the moc from 5.6.0. It"
> >
>
> Which apparently means that 'make distclean' is not working.
> Remove all moc_*.cpp ui_*.h
>
>
I removed two moc_*.cpp files (and there were no ui_*.h). Then:
make clean
./autogen.sh
./configure

And I'm still getting the same compilation failure:
Making all in src
make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
rm -f hash-temp \
@echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1
--pretty=format:%H 2>/dev/null || echo none` ; \
sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \
cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \
rm -f hash-temp
GEN moc_Compare.cpp
Unknown options: q, t, =, q, t, 4.
make[2]: *** [moc_Compare.cpp] Error 1
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
make: *** [all] Error 2


And if I'm using JMarc's suggestion, I'm still getting the same error as
before:
geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc
[...]
GEN moc_Compare.cpp
GEN moc_PreviewLoader.cpp
make all-recursive
make[3]: Entering directory `/home/geek/Build/Devel/lyx/src'
Making all in support
make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h
moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h
make all-am
make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
CXX FileMonitor.o
CXX ConsoleApplication.o
In file included from ConsoleApplication.cpp:51:0:
moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was
generated using the moc from 5.6.0. It"
#error "This file was generated using the moc from 5.6.0. It"
^
moc_ConsoleApplicationPrivate.cpp:16:2: error: #error "cannot be used with
the include files from this version of Qt."
#error "cannot be used with the include files from this version of Qt."
^
moc_ConsoleApplicationPrivate.cpp:17:2: error: #error "(The moc has changed
too much.)"
#error "(The moc has changed too much.)"
^
moc_ConsoleApplicationPrivate.cpp:22:5: error: ‘QByteArrayData’ does not
name a type
QByteArrayData data[3];
^
moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not
declared in this scope
- idx * sizeof(QByteArrayData)) \
^
moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(0, 0, 39), // "lyx::support::ConsoleApplicat..."
^
moc_ConsoleApplicationPrivate.cpp:29:5: error:
‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared
in this scope
)
^
moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(0, 0, 39), // 

Re: User template directory

[Helge Hafting]

Den 21. jan. 2017 09:35, skrev Jürgen Spitzmüller:


It has been brought up repeatedly, and I've looked into it several
times. The problem is that, astonishingly, there is no straightforward
way to add custom items to Qt's "places" widget (the "directory panel
on the left").


Well, is it possible to add/change a pushbutton on the top instead?
There is already "Documents" which uselessly takes me to the home 
folder, and "Templates" that gives me the folder with LyX templates.


The "Templates" button is useful, it gives me all the templates 
distributed with LyX.
Could the "Document" button be changed so it brings up 
"~/.lyx/templates/" instead of just "~/"? And perhaps with a caption 
like "Private templates" instead of "Documents"?


The un-changeable directory panel on the left already has the home 
folder ready, so no need to have a button for that.


Newbies don't notice, but as soon as you use LyX so much that you create 
your own template documents, this becomes a problem. The proper place 
for a private template is ~/.lyx/templates (at least on linux), but it 
is only accessible by typing the path.


Last time I recruited a LyX user, I provided templates for commonly used 
document types here. It was kind of painful explaining that the 
templates we just put in their correct place was so hard to reach 
afterwards.



"Save As" is even worse. Clicking "Templates" make one think that this 
is how you save a template for future use. But it brings up 
/usr/share/lyx/templates/ where users don't have write access. (And they 
should not have either.) It'd be much better if "Save As..."->Templates 
gave us ~/.lyx/templates/  There is no need to bring up the LyX template 
folder in the save dialog.


Helge Hafting

Re: master GIT broken?

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 12:50:05, schrieb Liviu Andronic 

> On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes 
> wrote:
> 
> > Le 28/02/2017 à 12:16, Liviu Andronic a écrit :
> >
> >> Dear all,
> >> I have troubles compiling current GIT. Today I've updated from e7654d9
> >> -> a1faa41, and all of a sudden master no longer compiles. Before the
> >> compilation failures I did a `make distclean` which worked fine.  I'm
> >> using libqt4-dev 4.8.5 on Ubuntu 14.04.
> >>
> >
> > Dear Liviu,
> >
> > What can you tell us about your 'moc' binary? What version of Qt is it
> > from?
> > It seems that it does not understand the '-qt=qt4' argument.
> >
> >
> I'm using libqt4-dev 4.8.5 on Ubuntu 14.04. Previously compilations worked
> fine, and I hadn't changed Qt version since.
> 

So do I.

> 
> > Do you have qtchooser installed? What does 'qtchooser -l' return?
> >
> >
> geek@liv-inspiron:~/Build/Devel/lyx$ qtchooser -l
> 4
> 5
> default
> qt4-i386-linux-gnu
> qt4-x86_64-linux-gnu
> qt4
> qt5-x86_64-linux-gnu
> qt5
> 
> 
> > Note that on my ancient ubuntu 12.04, I have
> > QT_MOC=moc-qt4
> >
> > As a workaround for now, you can probably configure with QT_MOC=moc, or at
> > least pass this to make.
> >
> >
> Still getting an error, but a later one:
> geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc
> [...]
> GEN moc_Compare.cpp
> GEN moc_PreviewLoader.cpp
> make all-recursive
> make[3]: Entering directory `/home/geek/Build/Devel/lyx/src'
> Making all in support
> make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
> moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h
> moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h
> make all-am
> make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
> CXX FileMonitor.o
> CXX ConsoleApplication.o
> In file included from ConsoleApplication.cpp:51:0:
> moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was
> generated using the moc from 5.6.0. It"
> #error "This file was generated using the moc from 5.6.0. It"
>

Which apparently means that 'make distclean' is not working.
Remove all moc_*.cpp ui_*.h

...

> 
> Is it possible I have some mix-up between Qt4 and Qt5?

Yes, but I think that it is only because of previous compilation with qt5.

> Liviu
> 
> 
> 
> > JMarc
> >

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: master GIT broken?

[Liviu Andronic]

On Tue, Feb 28, 2017 at 12:30 PM, Jean-Marc Lasgouttes 
wrote:

> Le 28/02/2017 à 12:16, Liviu Andronic a écrit :
>
>> Dear all,
>> I have troubles compiling current GIT. Today I've updated from e7654d9
>> -> a1faa41, and all of a sudden master no longer compiles. Before the
>> compilation failures I did a `make distclean` which worked fine.  I'm
>> using libqt4-dev 4.8.5 on Ubuntu 14.04.
>>
>
> Dear Liviu,
>
> What can you tell us about your 'moc' binary? What version of Qt is it
> from?
> It seems that it does not understand the '-qt=qt4' argument.
>
>
I'm using libqt4-dev 4.8.5 on Ubuntu 14.04. Previously compilations worked
fine, and I hadn't changed Qt version since.



> Do you have qtchooser installed? What does 'qtchooser -l' return?
>
>
geek@liv-inspiron:~/Build/Devel/lyx$ qtchooser -l
4
5
default
qt4-i386-linux-gnu
qt4-x86_64-linux-gnu
qt4
qt5-x86_64-linux-gnu
qt5


> Note that on my ancient ubuntu 12.04, I have
> QT_MOC=moc-qt4
>
> As a workaround for now, you can probably configure with QT_MOC=moc, or at
> least pass this to make.
>
>
Still getting an error, but a later one:
geek@liv-inspiron:~/Build/Devel/lyx$ make QT_MOC=moc
[...]
GEN moc_Compare.cpp
GEN moc_PreviewLoader.cpp
make all-recursive
make[3]: Entering directory `/home/geek/Build/Devel/lyx/src'
Making all in support
make[4]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
moc -o moc_ConsoleApplicationPrivate.cpp ConsoleApplicationPrivate.h
moc -o moc_SystemcallPrivate.cpp SystemcallPrivate.h
make all-am
make[5]: Entering directory `/home/geek/Build/Devel/lyx/src/support'
CXX FileMonitor.o
CXX ConsoleApplication.o
In file included from ConsoleApplication.cpp:51:0:
moc_ConsoleApplicationPrivate.cpp:15:2: error: #error "This file was
generated using the moc from 5.6.0. It"
#error "This file was generated using the moc from 5.6.0. It"
^
moc_ConsoleApplicationPrivate.cpp:16:2: error: #error "cannot be used with
the include files from this version of Qt."
#error "cannot be used with the include files from this version of Qt."
^
moc_ConsoleApplicationPrivate.cpp:17:2: error: #error "(The moc has changed
too much.)"
#error "(The moc has changed too much.)"
^
moc_ConsoleApplicationPrivate.cpp:22:5: error: ‘QByteArrayData’ does not
name a type
QByteArrayData data[3];
^
moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not
declared in this scope
- idx * sizeof(QByteArrayData)) \
^
moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(0, 0, 39), // "lyx::support::ConsoleApplicat..."
^
moc_ConsoleApplicationPrivate.cpp:29:5: error:
‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared
in this scope
)
^
moc_ConsoleApplicationPrivate.cpp:32:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(0, 0, 39), // "lyx::support::ConsoleApplicat..."
^
moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not
declared in this scope
- idx * sizeof(QByteArrayData)) \
^
moc_ConsoleApplicationPrivate.cpp:33:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(1, 40, 6), // "doExec"
^
moc_ConsoleApplicationPrivate.cpp:29:5: error:
‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared
in this scope
)
^
moc_ConsoleApplicationPrivate.cpp:33:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(1, 40, 6), // "doExec"
^
moc_ConsoleApplicationPrivate.cpp:28:24: error: ‘QByteArrayData’ was not
declared in this scope
- idx * sizeof(QByteArrayData)) \
^
moc_ConsoleApplicationPrivate.cpp:34:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(2, 47, 0) // ""
^
moc_ConsoleApplicationPrivate.cpp:29:5: error:
‘Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET’ was not declared
in this scope
)
^
moc_ConsoleApplicationPrivate.cpp:34:1: note: in expansion of macro
‘QT_MOC_LITERAL’
QT_MOC_LITERAL(2, 47, 0) // ""
^
In file included from ConsoleApplication.cpp:51:0:
moc_ConsoleApplicationPrivate.cpp:78:103: error: ‘const struct
qt_meta_stringdata_lyx__support__ConsoleApplicationPrivate_t’ has no member
named ‘data’
{ ::staticMetaObject,
qt_meta_stringdata_lyx__support__ConsoleApplicationPrivate.data,
^
moc_ConsoleApplicationPrivate.cpp:79:82: error: ‘Q_NULLPTR’ was not
declared in this scope
qt_meta_data_lyx__support__ConsoleApplicationPrivate, qt_static_metacall,
Q_NULLPTR, Q_NULLPTR}
^
moc_ConsoleApplicationPrivate.cpp:79:93: error: ‘Q_NULLPTR’ was not
declared in this scope
qt_meta_data_lyx__support__ConsoleApplicationPrivate, qt_static_metacall,
Q_NULLPTR, Q_NULLPTR}
^
moc_ConsoleApplicationPrivate.cpp: In member function ‘virtual const
QMetaObject* lyx::support::ConsoleApplicationPrivate::metaObject() const’:
moc_ConsoleApplicationPrivate.cpp:85:57: error: ‘class QObjectData’ has no
member named ‘dynamicMetaObject’
return QObject::d_ptr->metaObject ? QObject::d_ptr->dynamicMetaObject() :

^
moc_ConsoleApplicationPrivate.cpp: In member function ‘virtual void*

Re: master GIT broken?

[Jean-Marc Lasgouttes]

Le 28/02/2017 à 12:16, Liviu Andronic a écrit :

Dear all,
I have troubles compiling current GIT. Today I've updated from e7654d9
-> a1faa41, and all of a sudden master no longer compiles. Before the
compilation failures I did a `make distclean` which worked fine.  I'm
using libqt4-dev 4.8.5 on Ubuntu 14.04.


Dear Liviu,

What can you tell us about your 'moc' binary? What version of Qt is it from?
It seems that it does not understand the '-qt=qt4' argument.

Do you have qtchooser installed? What does 'qtchooser -l' return?

Note that on my ancient ubuntu 12.04, I have
QT_MOC=moc-qt4

As a workaround for now, you can probably configure with QT_MOC=moc, or 
at least pass this to make.


JMarc

master GIT broken?

[Liviu Andronic]

Dear all,
I have troubles compiling current GIT. Today I've updated from e7654d9 ->
a1faa41, and all of a sudden master no longer compiles. Before the
compilation failures I did a `make distclean` which worked fine.  I'm using
libqt4-dev 4.8.5 on Ubuntu 14.04.

Here's what I see:
>"/home/geek/Build/Devel/lyx/autogen.sh" (29715)
Using automake (GNU automake) 1.14.1
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
Building configure...
Building po/POTFILES.in...

run "./configure && make"

>"/home/geek/Build/Devel/lyx/autogen.sh" (29715) returned '0'

>/home/geek/Build/Devel/lyx/configure (30084)
configuring LyX version 2.3.0dev
[...]

Configuration
Host type: x86_64-unknown-linux-gnu
Special build flags: build=development warnings assertions stdlib-debug
use-aspell use-enchant use-hunspell
C++ Compiler: g++ (4.8)
C++ Compiler flags: -Wall -Wextra -g -O -std=c++11
C++ Compiler user flags:
Linker flags:
Linker user flags:
Qt Frontend:
Qt version: 4.8.6
Packaging: posix
LyX binary dir: /usr/local/bin
LyX files dir: /usr/local/share/lyx

Configuration of LyX was successful.
Type 'make' to compile the program,
and then 'make install' to install it.
>/home/geek/Build/Devel/lyx/configure (30084) returned '0'

geek@liv-inspiron:~/Build/Devel/lyx$ make
make all-recursive
make[1]: Entering directory `/home/geek/Build/Devel/lyx'
Making all in autotests
make[2]: Entering directory `/home/geek/Build/Devel/lyx/autotests'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/autotests'
Making all in config
make[2]: Entering directory `/home/geek/Build/Devel/lyx/config'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/config'
Making all in development
make[2]: Entering directory `/home/geek/Build/Devel/lyx/development'
make[3]: Entering directory `/home/geek/Build/Devel/lyx/development'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/geek/Build/Devel/lyx/development'
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/development'
Making all in po
make[2]: Entering directory `/home/geek/Build/Devel/lyx/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/po'
Making all in 3rdparty
make[2]: Entering directory `/home/geek/Build/Devel/lyx/3rdparty'
Making all in boost
make[3]: Entering directory `/home/geek/Build/Devel/lyx/3rdparty/boost'
CXX libs/regex/src/c_regex_traits.o
CXX libs/regex/src/cpp_regex_traits.o
CXX libs/regex/src/cregex.o
CXX libs/regex/src/fileiter.o
CXX libs/regex/src/instances.o
CXX libs/regex/src/posix_api.o
CXX libs/regex/src/regex.o
CXX libs/regex/src/regex_debug.o
CXX libs/regex/src/regex_raw_buffer.o
CXX libs/regex/src/regex_traits_defaults.o
CXX libs/regex/src/w32_regex_traits.o
CXX libs/regex/src/wc_regex_traits.o
CXX libs/regex/src/wide_posix_api.o
CXX libs/regex/src/winstances.o
CXX libs/regex/src/static_mutex.o
AR liblyxboost.a
make[3]: Leaving directory `/home/geek/Build/Devel/lyx/3rdparty/boost'
make[3]: Entering directory `/home/geek/Build/Devel/lyx/3rdparty'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/geek/Build/Devel/lyx/3rdparty'
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/3rdparty'
Making all in src
make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
rm -f hash-temp \
@echo " GEN lyx_commit_hash.h";hash=`cd ".." && git log -1
--pretty=format:%H 2>/dev/null || echo none` ; \
sed s/@LYX_GIT_COMMIT_HASH@/$hash/ "."/lyx_commit_hash.h.in >hash-temp ; \
cmp -s lyx_commit_hash.h hash-temp || cp hash-temp lyx_commit_hash.h ; \
rm -f hash-temp
GEN moc_Compare.cpp
Unknown options: q, t, =, q, t, 4.
make[2]: *** [moc_Compare.cpp] Error 1
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/geek/Build/Devel/lyx'
make: *** [all] Error 2


In src/Makefile I have:
QT_MOC = moc -qt=qt4

And config.log is attached.

In addition, now `make distclean` fails as well:
>make distclean (9653)
[...]
Making distclean in .
make[2]: Entering directory `/home/geek/Build/Devel/lyx/src'
Makefile:2443:
support/tests/.deps/check_ExternalTransforms-dummy_functions.Po: No such
file or directory
Makefile:2444: support/tests/.deps/check_Length-dummy_functions.Po: No such
file or directory
Makefile:2445:
support/tests/.deps/check_ListingsCaption-dummy_functions.Po: No such file
or directory
Makefile:2446: support/tests/.deps/check_layout-dummy_functions.Po: No such
file or directory
make[2]: *** No rule to make target
`support/tests/.deps/check_layout-dummy_functions.Po'. Stop.
make[2]: Leaving directory `/home/geek/Build/Devel/lyx/src'
make[1]: *** [distclean-recursive] Error 1
make[1]: Leaving directory `/home/geek/Build/Devel/lyx/src'
make: *** [distclean-recursive] Error 1
>make distclean (9653) returned '2'

So right now I'm unable to completely clean-up the tree.

Re: [LyX/master] Generalise the deletion protection mechanism from math to text (#9540)

[Guillaume Munch]

Le 28/02/2017 à 11:22, Jean-Marc Lasgouttes a écrit :


I agree. My point is that the behavior should be predictable and as far
as possible uniform between text and math.

Note that I am actually not sure that special casing empty insets is a
good idea. I makes things less predictable, and I do not know when it is
useful.



Makes sense. What do people prefer?

Re: [LyX/master] Generalise the deletion protection mechanism from math to text (#9540)

[Jean-Marc Lasgouttes]

Le 27/02/2017 à 20:16, Guillaume Munch a écrit :

Le 27/02/2017 à 11:23, Jean-Marc Lasgouttes a écrit :


Small questions though:
- I create an empty \mathord inset in a formula, backspace does use
deletion confirmation. Is this normal?


This is the legacy behaviour, but can be changed.


- if there are several cells (empty fraction) that are empty, why should
there be a confirmation?


Some as above; in addition, for math hulls I decided that the counts of
lines and columns was non-empty data.

All this can now be redefined very easily via confirmDeletion.


I agree. My point is that the behavior should be predictable and as far 
as possible uniform between text and math.


Note that I am actually not sure that special casing empty insets is a 
good idea. I makes things less predictable, and I do not know when it is 
useful.


JMarc

Re: lyx errors with lualatex and non-tex fonts

[Kornel Benko]

Am Dienstag, 28. Februar 2017 um 08:11:58, schrieb Guenter Milde 

> On 2017-02-15, Kornel Benko wrote:
> 
> > [-- Type: text/plain, Encoding: quoted-printable --]
> 
> > Am Mittwoch, 15. Februar 2017 um 08:37:46, schrieb Jürgen Spitzmüller 
> > 
> >> Am Dienstag, den 14.02.2017, 20:51 +0100 schrieb Kornel Benko:
> >> > Apart from this there are still 72 messages with
> >> > ! LaTeX Error: Command \textquotedbl unavailable in encoding
> >> > TU.
> >> > in
> >> > export/examples/modernCV_dvi3_texF
> >> > export/examples/es/modernCV_pdf4_texF
> >> > export/examples/es/modernCV_pdf5_texF
> 
> >> Should be fixed now.
> 
> > It is.
> 
> >> Jürgen
> 
> > Still failing for instance export/examples/modernCV_pdf4_texF
> > Missing character: There is no  in font FontAwesome/OT!
> 
> > Now only 5 failed tests remain.
> 
> They pass here with the newest texlive in Debian/testing providing
> 
>  \ProvidesClass{moderncv}[2015/07/28 v2.0.0 modern curriculum vitae and 
> letter document class]
> 
> It seems a new version added another new "awesome" character and your
> awsome font is not as up to date as the document class.
> (We had this already one time with the last update and the "mobile" icon.)
> 
> I recommend adding modernCV to the unreliable:varying-versions tests -- it
> seems to have a quite strict version dependency on the awesome fonts.
> 
> How many *reliable* failing test remain?
> 
> Günter

Failed 20, out of 3973. Tested '-L export -E "xhtml|lyx16|lyx21|lyx22"'
317 - export/export/latex/languagenesting2_pdf5_systemF (Failed)
2450 - export/doc/he/Intro_dvi (Failed)
2453 - export/doc/he/Intro_pdf (Failed)
2454 - export/doc/he/Intro_pdf2 (Failed)
2455 - export/doc/he/Intro_pdf3 (Failed)
2466 - export/doc/he/Tutorial_dvi (Failed)
2469 - export/doc/he/Tutorial_pdf (Failed)
2470 - export/doc/he/Tutorial_pdf2 (Failed)
2471 - export/doc/he/Tutorial_pdf3 (Failed)
5049 - export/examples/he/example_lyxified_dvi (Failed)
5052 - export/examples/he/example_lyxified_pdf (Failed)
5053 - export/examples/he/example_lyxified_pdf2 (Failed)
5054 - export/examples/he/example_lyxified_pdf3 (Failed)
5065 - export/examples/he/example_raw_dvi (Failed)
5068 - export/examples/he/example_raw_pdf (Failed)
5069 - export/examples/he/example_raw_pdf2 (Failed)
5070 - export/examples/he/example_raw_pdf3 (Failed)
5084 - export/examples/he/splash_pdf (Failed)
5085 - export/examples/he/splash_pdf2 (Failed)
5086 - export/examples/he/splash_pdf3 (Failed)

Not one was unreliable. Here modernCV now compiles. Font awesome is from TL2016.
(It was my error using awesome installed from the ubuntu packages)

Kornel

signature.asc
Description: This is a digitally signed message part.

local layout file + relative inputs?

[Ulrich Thomas Gabor]

Hi

Since nobody replied on the normal users lists, maybe someone here can tell me 
if it is possible to reference an include from a layout file relatively? See 
the mail I sent to the users list:

> Am 26.02.2017 um 15:59 schrieb Ulrich Thomas Gabor 
> :
> 
> Hi
> 
> I have a local layout file, which I reference as "Local Layout" with a 
> relative path (../templates/my.layout). Now I want to clean up the layout and 
> move some parts into a separate include file for reuse. My wish is to create 
> an include file next to the layout file (../templates/my.inc) and reference 
> it from the layout-file, but this does not work, i.e. the include file is not 
> found. Neither "input my.inc" nor "input ../templates/my.inc" works, 
> presumably because LyX copies the layout file to a temp directory and the inc 
> file is ignored.
> 
> How can I get this constellation to work?
> 
> Thanks in advance for hints into the right direction!
> 
> Best
> Ulrich

I do not want to drop the includes in the system directories, because the lyx 
files and the layout/include files are versioned and should stay closely 
together.

Can someone give me a hint, if this is possible at all?

Best
Ulrich

Re: Working on CI job that runs automated tests

[Kornel Benko]

Am Montag, 27. Februar 2017 um 18:28:28, schrieb Pavel Sanda 
> Christian Ridderström wrote:
> > Hi,
> > 
> > This is a CI job I'm working on that's intended to run automated tests:
> > 
> >https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/
> 
> How often do you intend to run those?
> While compile errs tend to get fixed quickly I see quite longer
> fixing time for automated test (sometimes stuff needs to be discussed etc),
> so we don't want to shout at mailling list every day about it.
> 
> Pavel

In contrary, it will show us pretty soon if a commit broke anything.

-1

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: EmDash Problems (patch)

[Enrico Forestieri]

On Mon, Feb 27, 2017 at 10:39:25PM +, Guenter Milde wrote:
> On 2017-02-27, Enrico Forestieri wrote:
> > On Mon, Feb 27, 2017 at 09:18:50PM +, Guenter Milde wrote:
> >> On 2017-02-27, Enrico Forestieri wrote:
> 
> >> >> >> Then, a decision has to still be taken as regards the original 
> >> >> >> problem
> >> >> >> in this thread. I think that the patch Günther proposed on Jan. 25 is
> >> >> >> the less controversial one.
> 
> >> >> > I think you mean
> >> >> > https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg198620.html
> 
> >> >> However, this patch is obsolete. As Guillaume pointed out, there are use
> >> >> cases for the dashes with and without line break opportunity. (See also
> >> >> the attachments to https://www.lyx.org/trac/ticket/10543)
> 
> >> > A patch that does not exist cannot obsolete anything ;)
> 
> >> But it can be obsolete. Obsoleted by new findings during testing and
> >> discussion of the problem.
> 
> > This is a sophism.
> 
> Can you explain this, please?

https://www.merriam-webster.com/dictionary/sophism

> >> > At this point we have two simple alternatives. Either the above one or
> >> > https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg198615.html
> 
> >> Both have serious drawbacks. See #10543.
> 
> > TL;DR
> 
> Sorry, but forcing a simple but insufficient patch to a complex problem
> because the description is too long is not the right thing.

You make it complex. We output latex and thus should follow latex rules.
Since ever LyX was outputting -- and --- and nobody was complaining
(I am not speaking about text or html output, which are different).
Now LyX outputs \textendash and \textemdash and this is causing problems.
What is the conclusion?

-- 
Enrico

Re: lyx errors with lualatex and non-tex fonts

[Guenter Milde]

On 2017-02-15, Kornel Benko wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> Am Mittwoch, 15. Februar 2017 um 08:37:46, schrieb Jürgen Spitzmüller 
> 
>> Am Dienstag, den 14.02.2017, 20:51 +0100 schrieb Kornel Benko:
>> > Apart from this there are still 72 messages with
>> > ! LaTeX Error: Command \textquotedbl unavailable in encoding
>> > TU.
>> > in
>> > export/examples/modernCV_dvi3_texF
>> > export/examples/es/modernCV_pdf4_texF
>> > export/examples/es/modernCV_pdf5_texF

>> Should be fixed now.

> It is.

>> Jürgen

> Still failing for instance export/examples/modernCV_pdf4_texF
>   Missing character: There is no  in font FontAwesome/OT!

> Now only 5 failed tests remain.

They pass here with the newest texlive in Debian/testing providing

 \ProvidesClass{moderncv}[2015/07/28 v2.0.0 modern curriculum vitae and letter 
document class]

It seems a new version added another new "awesome" character and your
awsome font is not as up to date as the document class.
(We had this already one time with the last update and the "mobile" icon.)

I recommend adding modernCV to the unreliable:varying-versions tests -- it
seems to have a quite strict version dependency on the awesome fonts.

How many *reliable* failing test remain?

Günter