Re: Minted example not displaying in pdf anymore

[Scott Kostyshak]

On Tue, Jun 27, 2017 at 01:35:19AM +0200, Kornel Benko wrote:
> Am Montag, 26. Juni 2017 um 23:46:32, schrieb Enrico Forestieri 
> 
> > On Mon, Jun 26, 2017 at 01:51:08AM +0200, Enrico Forestieri wrote:
> > > On Sun, Jun 25, 2017 at 04:24:18PM -0400, Scott Kostyshak wrote:
> > > > 
> > > > True, but I think that is partly because we used to support GCC 4.6 and
> > > > Qt 4.8. We have never supported minted, so that is why I think it is
> > > > "more OK" if we do not support older versions. In the end, I suppose it
> > > > depends on how long it would take us to add support for older versions,
> > > > and on if that support would be hackish or would be a good
> > > > implementation.
> > > > 
> > > > Enrico, any thoughts on the above?
> > > 
> > > Taking into account older versions of Pygments that are case
> > > sensitive would be straightforward. It would suffice to lower
> > > case the language only when it is going to be written in the
> > > LaTeX file. Indeed, our GUI is case sensitive and the language
> > > combo gets disabled if the case does not match (meaning that the
> > > language can only be changed through the advanced tab).
> > 
> > I did this at 28be7d55.
> 
> Nice.

+1 thanks, Enrico.

Scott

Re: Minted example not displaying in pdf anymore

[Kornel Benko]

Am Montag, 26. Juni 2017 um 23:46:32, schrieb Enrico Forestieri 
> On Mon, Jun 26, 2017 at 01:51:08AM +0200, Enrico Forestieri wrote:
> > On Sun, Jun 25, 2017 at 04:24:18PM -0400, Scott Kostyshak wrote:
> > > 
> > > True, but I think that is partly because we used to support GCC 4.6 and
> > > Qt 4.8. We have never supported minted, so that is why I think it is
> > > "more OK" if we do not support older versions. In the end, I suppose it
> > > depends on how long it would take us to add support for older versions,
> > > and on if that support would be hackish or would be a good
> > > implementation.
> > > 
> > > Enrico, any thoughts on the above?
> > 
> > Taking into account older versions of Pygments that are case
> > sensitive would be straightforward. It would suffice to lower
> > case the language only when it is going to be written in the
> > LaTeX file. Indeed, our GUI is case sensitive and the language
> > combo gets disabled if the case does not match (meaning that the
> > language can only be changed through the advanced tab).
> 
> I did this at 28be7d55.

Nice.

> > I don't think this has any adverse effect, except if you export to
> > LaTeX and then import back with tex2lyx. In this case the language
> > combo will be most certainly disabled. But it suffices going to the
> > advanced tab and properly adjust the case to have it functional again.
> 
> I also took this into account, so that the case used for language names
> is now irrelevant.
> 

Super!

Kornel

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

Re: Minted example not displaying in pdf anymore

[Enrico Forestieri]

On Mon, Jun 26, 2017 at 01:51:08AM +0200, Enrico Forestieri wrote:
> On Sun, Jun 25, 2017 at 04:24:18PM -0400, Scott Kostyshak wrote:
> > 
> > True, but I think that is partly because we used to support GCC 4.6 and
> > Qt 4.8. We have never supported minted, so that is why I think it is
> > "more OK" if we do not support older versions. In the end, I suppose it
> > depends on how long it would take us to add support for older versions,
> > and on if that support would be hackish or would be a good
> > implementation.
> > 
> > Enrico, any thoughts on the above?
> 
> Taking into account older versions of Pygments that are case
> sensitive would be straightforward. It would suffice to lower
> case the language only when it is going to be written in the
> LaTeX file. Indeed, our GUI is case sensitive and the language
> combo gets disabled if the case does not match (meaning that the
> language can only be changed through the advanced tab).

I did this at 28be7d55.

> I don't think this has any adverse effect, except if you export to
> LaTeX and then import back with tex2lyx. In this case the language
> combo will be most certainly disabled. But it suffices going to the
> advanced tab and properly adjust the case to have it functional again.

I also took this into account, so that the case used for language names
is now irrelevant.

-- 
Enrico

Re: Minted example not displaying in pdf anymore

[Enrico Forestieri]

On Sun, Jun 25, 2017 at 04:24:18PM -0400, Scott Kostyshak wrote:
> 
> True, but I think that is partly because we used to support GCC 4.6 and
> Qt 4.8. We have never supported minted, so that is why I think it is
> "more OK" if we do not support older versions. In the end, I suppose it
> depends on how long it would take us to add support for older versions,
> and on if that support would be hackish or would be a good
> implementation.
> 
> Enrico, any thoughts on the above?

Taking into account older versions of Pygments that are case
sensitive would be straightforward. It would suffice to lower
case the language only when it is going to be written in the
LaTeX file. Indeed, our GUI is case sensitive and the language
combo gets disabled if the case does not match (meaning that the
language can only be changed through the advanced tab).

I don't think this has any adverse effect, except if you export to
LaTeX and then import back with tex2lyx. In this case the language
combo will be most certainly disabled. But it suffices going to the
advanced tab and properly adjust the case to have it functional again.

-- 
Enrico

Re: Minted example not displaying in pdf anymore

[Scott Kostyshak]

On Thu, Jun 22, 2017 at 10:02:08PM +0200, Kornel Benko wrote:
> Am Donnerstag, 22. Juni 2017 um 13:22:20, schrieb Scott Kostyshak 
> 

> > > After some googling I came to this page:
> > >   http://pygments.org/docs/changelog/#version-2-2-0
> > > where I found this changelog line:
> > >   * Lexer aliases passed to get_lexer_by_name() are now case-insensitive.
> > > 
> > > This is for the version 2.0rc1, while I have only version 1.6. The 
> > > recommended upgrade with
> > >   # sudo pip install pygments --upgrade
> > >   Downloading/unpacking pygments from 
> > > https://pypi.python.org/packages/02/ee/b6e02dc6529e82b75bb06823ff7d005b141037cb1416b10c6f00fc419dca/Pygments-2.2.0-py2.py3-none-any.whl#md5=ce67fc58b51ffd29a2de8b97fcda274a
> > > Downloading Pygments-2.2.0-py2.py3-none-any.whl (841kB): 841kB 
> > > downloaded
> > >   Installing collected packages: pygments
> > > Found existing installation: Pygments 1.6
> > >   Not uninstalling Pygments at /usr/lib/python2.7/dist-packages, 
> > > owned by OS
> > >   Successfully installed pygments
> > >   Cleaning up...
> > > 
> > > cured the case for me. Of course, the same has to be done for python3
> > >   #   sudo pip3 install pygments --upgrade
> > 
> > Makes sense. My version was 2.1.
> > 
> > So the minimum version for pygmentize that we require is 2.0? It was
> > released in November 2014. To me, that is old enough that we should not
> > make a significant effort to support older versions since this will be a
> > new feature.
> 
> I am not so sure. For instance we still try to support e.g. gcc 4.6 or qt 4.8.

True, but I think that is partly because we used to support GCC 4.6 and
Qt 4.8. We have never supported minted, so that is why I think it is
"more OK" if we do not support older versions. In the end, I suppose it
depends on how long it would take us to add support for older versions,
and on if that support would be hackish or would be a good
implementation.

Enrico, any thoughts on the above?

> > Why did you have 1.6? Was it shipped with your distro?
> 
> Yes, it is part of the distro.
> I still have mint 17.3 based on ubuntu 14.04. I tried once to install
> mint 18 (based on ubuntu 16), but the following boot showed only a black 
> screen.
> Was unable to trace down what went wrong.
> Installation of ubuntu 16 was successful, but
> 1.) I was unable to use ssh with my old keys (e.g. could not connect to 
> lyx-git)
> 2.) my gpg-keys for mail invalid
> 3.) the use of mysql in digikam was dropped. And the conversion to sqlite 
> crashed regularly after 2 hours.
>   (In the mean time I wrote my own conversion script. It finishes in 2 
> minutes and does not crash)

I see, yes those are show-stoppers.

> 
> > And
> > why did it work before? Was it something in LyX that changed?
> 
> Apparently I did not check the pdf-output. (It compiles without errors, but 
> the pdf
> misses all inline listings)

Ah yes I often forget to check the output also.

Scott

Re: Minted example not displaying in pdf anymore

[Kornel Benko]

Am Donnerstag, 22. Juni 2017 um 13:22:20, schrieb Scott Kostyshak 

> On Thu, Jun 22, 2017 at 04:27:53PM +0200, Kornel Benko wrote:
> > Am Donnerstag, 22. Juni 2017 um 12:02:53, schrieb Kornel Benko 
> > 
> > > Am Mittwoch, 21. Juni 2017 um 23:48:18, schrieb Scott Kostyshak 
> > > 
> > > > On Thu, Jun 22, 2017 at 12:49:10AM +0200, Kornel Benko wrote:
> > > > > Hi,
> > > > > examples/minted-listings.lyx compiles, but there is no output of the 
> > > > > listings.
> > > > > Contrary to this, minted-filelisting.lyx displays fine.
> > > > > 
> > > > > I am sure it worked previously. First I thought, it may be because of 
> > > > > TL17 (I switched recently),
> > > > > but after configuring TL16 and compiling again, the effect did not 
> > > > > change.
> > > > > 
> > > > > Would be nice, if someone could confirm.
> > > > 
> > > > Attached are my PDF and log from pdflatex (with -shell-escape). Is the
> > > > PDF the expected output? If so should we compare logs?
> > > > I also have TL17 in a virtual box that I can test when I get access to
> > > > that computer. Let me know.
> > > > 
> > > > Scott
> > > 
> > > Thanks Scott. Unfortunatelly the program pygmentize is not working here.
> > > 
> > 
> > ...
> > After some googling I came to this page:
> > http://pygments.org/docs/changelog/#version-2-2-0
> > where I found this changelog line:
> > * Lexer aliases passed to get_lexer_by_name() are now case-insensitive.
> > 
> > This is for the version 2.0rc1, while I have only version 1.6. The 
> > recommended upgrade with
> > # sudo pip install pygments --upgrade
> > Downloading/unpacking pygments from 
> > https://pypi.python.org/packages/02/ee/b6e02dc6529e82b75bb06823ff7d005b141037cb1416b10c6f00fc419dca/Pygments-2.2.0-py2.py3-none-any.whl#md5=ce67fc58b51ffd29a2de8b97fcda274a
> >   Downloading Pygments-2.2.0-py2.py3-none-any.whl (841kB): 841kB 
> > downloaded
> > Installing collected packages: pygments
> >   Found existing installation: Pygments 1.6
> > Not uninstalling Pygments at /usr/lib/python2.7/dist-packages, 
> > owned by OS
> > Successfully installed pygments
> > Cleaning up...
> > 
> > cured the case for me. Of course, the same has to be done for python3
> > #   sudo pip3 install pygments --upgrade
> 
> Makes sense. My version was 2.1.
> 
> So the minimum version for pygmentize that we require is 2.0? It was
> released in November 2014. To me, that is old enough that we should not
> make a significant effort to support older versions since this will be a
> new feature.

I am not so sure. For instance we still try to support e.g. gcc 4.6 or qt 4.8.

> Why did you have 1.6? Was it shipped with your distro?

Yes, it is part of the distro.
I still have mint 17.3 based on ubuntu 14.04. I tried once to install
mint 18 (based on ubuntu 16), but the following boot showed only a black screen.
Was unable to trace down what went wrong.
Installation of ubuntu 16 was successful, but
1.) I was unable to use ssh with my old keys (e.g. could not connect to lyx-git)
2.) my gpg-keys for mail invalid
3.) the use of mysql in digikam was dropped. And the conversion to sqlite 
crashed regularly after 2 hours.
(In the mean time I wrote my own conversion script. It finishes in 2 
minutes and does not crash)

> And
> why did it work before? Was it something in LyX that changed?

Apparently I did not check the pdf-output. (It compiles without errors, but the 
pdf
misses all inline listings)

Kornel

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

Re: Minted example not displaying in pdf anymore

[Scott Kostyshak]

On Thu, Jun 22, 2017 at 04:27:53PM +0200, Kornel Benko wrote:
> Am Donnerstag, 22. Juni 2017 um 12:02:53, schrieb Kornel Benko 
> 
> > Am Mittwoch, 21. Juni 2017 um 23:48:18, schrieb Scott Kostyshak 
> > 
> > > On Thu, Jun 22, 2017 at 12:49:10AM +0200, Kornel Benko wrote:
> > > > Hi,
> > > > examples/minted-listings.lyx compiles, but there is no output of the 
> > > > listings.
> > > > Contrary to this, minted-filelisting.lyx displays fine.
> > > > 
> > > > I am sure it worked previously. First I thought, it may be because of 
> > > > TL17 (I switched recently),
> > > > but after configuring TL16 and compiling again, the effect did not 
> > > > change.
> > > > 
> > > > Would be nice, if someone could confirm.
> > > 
> > > Attached are my PDF and log from pdflatex (with -shell-escape). Is the
> > > PDF the expected output? If so should we compare logs?
> > > I also have TL17 in a virtual box that I can test when I get access to
> > > that computer. Let me know.
> > > 
> > > Scott
> > 
> > Thanks Scott. Unfortunatelly the program pygmentize is not working here.
> > 
> 
> ...
> After some googling I came to this page:
>   http://pygments.org/docs/changelog/#version-2-2-0
> where I found this changelog line:
>   * Lexer aliases passed to get_lexer_by_name() are now case-insensitive.
> 
> This is for the version 2.0rc1, while I have only version 1.6. The 
> recommended upgrade with
>   # sudo pip install pygments --upgrade
>   Downloading/unpacking pygments from 
> https://pypi.python.org/packages/02/ee/b6e02dc6529e82b75bb06823ff7d005b141037cb1416b10c6f00fc419dca/Pygments-2.2.0-py2.py3-none-any.whl#md5=ce67fc58b51ffd29a2de8b97fcda274a
> Downloading Pygments-2.2.0-py2.py3-none-any.whl (841kB): 841kB 
> downloaded
>   Installing collected packages: pygments
> Found existing installation: Pygments 1.6
>   Not uninstalling Pygments at /usr/lib/python2.7/dist-packages, 
> owned by OS
>   Successfully installed pygments
>   Cleaning up...
> 
> cured the case for me. Of course, the same has to be done for python3
>   #   sudo pip3 install pygments --upgrade

Makes sense. My version was 2.1.

So the minimum version for pygmentize that we require is 2.0? It was
released in November 2014. To me, that is old enough that we should not
make a significant effort to support older versions since this will be a
new feature. Why did you have 1.6? Was it shipped with your distro? And
why did it work before? Was it something in LyX that changed?

Scott

Re: Minted example not displaying in pdf anymore

[Kornel Benko]

Am Donnerstag, 22. Juni 2017 um 12:02:53, schrieb Kornel Benko 
> Am Mittwoch, 21. Juni 2017 um 23:48:18, schrieb Scott Kostyshak 
> 
> > On Thu, Jun 22, 2017 at 12:49:10AM +0200, Kornel Benko wrote:
> > > Hi,
> > > examples/minted-listings.lyx compiles, but there is no output of the 
> > > listings.
> > > Contrary to this, minted-filelisting.lyx displays fine.
> > > 
> > > I am sure it worked previously. First I thought, it may be because of 
> > > TL17 (I switched recently),
> > > but after configuring TL16 and compiling again, the effect did not change.
> > > 
> > > Would be nice, if someone could confirm.
> > 
> > Attached are my PDF and log from pdflatex (with -shell-escape). Is the
> > PDF the expected output? If so should we compare logs?
> > I also have TL17 in a virtual box that I can test when I get access to
> > that computer. Let me know.
> > 
> > Scott
> 
> Thanks Scott. Unfortunatelly the program pygmentize is not working here.
> 

...
After some googling I came to this page:
http://pygments.org/docs/changelog/#version-2-2-0
where I found this changelog line:
* Lexer aliases passed to get_lexer_by_name() are now case-insensitive.

This is for the version 2.0rc1, while I have only version 1.6. The recommended 
upgrade with
# sudo pip install pygments --upgrade
Downloading/unpacking pygments from 
https://pypi.python.org/packages/02/ee/b6e02dc6529e82b75bb06823ff7d005b141037cb1416b10c6f00fc419dca/Pygments-2.2.0-py2.py3-none-any.whl#md5=ce67fc58b51ffd29a2de8b97fcda274a
  Downloading Pygments-2.2.0-py2.py3-none-any.whl (841kB): 841kB 
downloaded
Installing collected packages: pygments
  Found existing installation: Pygments 1.6
Not uninstalling Pygments at /usr/lib/python2.7/dist-packages, 
owned by OS
Successfully installed pygments
Cleaning up...

cured the case for me. Of course, the same has to be done for python3
#   sudo pip3 install pygments --upgrade

Kornel

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

Re: Minted example not displaying in pdf anymore

[Kornel Benko]

Am Mittwoch, 21. Juni 2017 um 23:48:18, schrieb Scott Kostyshak 

> On Thu, Jun 22, 2017 at 12:49:10AM +0200, Kornel Benko wrote:
> > Hi,
> > examples/minted-listings.lyx compiles, but there is no output of the 
> > listings.
> > Contrary to this, minted-filelisting.lyx displays fine.
> > 
> > I am sure it worked previously. First I thought, it may be because of TL17 
> > (I switched recently),
> > but after configuring TL16 and compiling again, the effect did not change.
> > 
> > Would be nice, if someone could confirm.
> 
> Attached are my PDF and log from pdflatex (with -shell-escape). Is the
> PDF the expected output? If so should we compare logs?
> I also have TL17 in a virtual box that I can test when I get access to
> that computer. Let me know.
> 
> Scott

Thanks Scott. Unfortunatelly the program pygmentize is not working here.

Using 'pdflatex -shell-escape minted-listings.tex' the first time I get
Error: no lexer for alias 'C' found
system returned with code 256
Error: no lexer for alias 'Fortran' found
system returned with code 256
Error: no lexer for alias 'TeX' found
system returned with code 256

but 'pygmentize -L' shows them all.
But wait: There is no lexer for 'C', only for 'c'. If I change 

Looking into the file minted-listings.tex, I see that the specification for 
language is
\begin{minted}[numbers=left,showspaces=true,bgcolor=lgray]{C}
and
\begin{minted}[frame=lines,style=bw]{Fortran}
and
\mintinline[fontfamily=tt]{TeX}

If I change the values to 'c', 'fortran' and 'tex', I GET THE CORRECT output.

Selecting the language as 'language=c' in the extended options for the minted 
inset works too.

Or, how to convince pygmentize to be case insensitive?

Should we change src/insets/InsetListings.cpp(lines 271 and 297)
os << "{" << minted_language << "}";
?

Kornel

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

Re: Minted example not displaying in pdf anymore

[Scott Kostyshak]

On Thu, Jun 22, 2017 at 12:49:10AM +0200, Kornel Benko wrote:
> Hi,
> examples/minted-listings.lyx compiles, but there is no output of the listings.
> Contrary to this, minted-filelisting.lyx displays fine.
> 
> I am sure it worked previously. First I thought, it may be because of TL17 (I 
> switched recently),
> but after configuring TL16 and compiling again, the effect did not change.
> 
> Would be nice, if someone could confirm.

Attached are my PDF and log from pdflatex (with -shell-escape). Is the
PDF the expected output? If so should we compare logs?
I also have TL17 in a virtual box that I can test when I get access to
that computer. Let me know.

Scott
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016) (preloaded 
format=pdflatex 2017.4.28)  21 JUN 2017 23:45
entering extended mode
 \write18 enabled.
 %&-line parsing enabled.
**minted-listings.tex
(./minted-listings.tex
LaTeX2e <2017/01/01> patch level 3
Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.

(/usr/local/texlive/2016/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/local/texlive/2016/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2017/02/22 v2.0g Standard LaTeX package
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2017/02/22 v2.0g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 48.
)) (/usr/local/texlive/2016/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2015/03/17 v1.2c Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2015/03/17 v1.2c Input encoding file
)) (/usr/local/texlive/2016/texmf-dist/tex/latex/xcolor/xcolor.sty
Package: xcolor 2016/05/11 v2.12 LaTeX color extensions (UK)
(/usr/local/texlive/2016/texmf-dist/tex/latex/graphics-cfg/color.cfg
File: color.cfg 2016/01/02 v1.6 sample color configuration
)
Package xcolor Info: Driver file: pdftex.def on input line 225.
(/usr/local/texlive/2016/texmf-dist/tex/latex/graphics-def/pdftex.def
File: pdftex.def 2017/01/12 v0.06k Graphics/color for pdfTeX
(/usr/local/texlive/2016/texmf-dist/tex/generic/oberdiek/infwarerr.sty
Package: infwarerr 2016/05/16 v1.4 Providing info/warning/error messages (HO)
) (/usr/local/texlive/2016/texmf-dist/tex/generic/oberdiek/ltxcmds.sty
Package: ltxcmds 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
)
\Gread@gobject=\count87
)
Package xcolor Info: Model `cmy' substituted by `cmy0' on input line 1348.
Package xcolor Info: Model `hsb' substituted by `rgb' on input line 1352.
Package xcolor Info: Model `RGB' extended on input line 1364.
Package xcolor Info: Model `HTML' substituted by `rgb' on input line 1366.
Package xcolor Info: Model `Hsb' substituted by `hsb' on input line 1367.
Package xcolor Info: Model `tHsb' substituted by `hsb' on input line 1368.
Package xcolor Info: Model `HSB' substituted by `hsb' on input line 1369.
Package xcolor Info: Model `Gray' substituted by `gray' on input line 1370.
Package xcolor Info: Model `wave' substituted by `hsb' on input line 1371.
) (/usr/local/texlive/2016/texmf-dist/tex/generic/babel/babel.sty
Package: babel 2016/04/23 3.9r The Babel package
(/usr/local/texlive/2016/texmf-dist/tex/generic/babel-english/english.ldf
Language: english 2017/01/24 v3.3q English support from the babel system
(/usr/local/texlive/2016/texmf-dist/tex/generic/babel/babel.def
File: babel.def 2016/04/23 3.9r Babel common definitions
\babel@savecnt=\count88
\U@D=\dimen103
)
\l@canadian = a dialect from \language\l@american 
\l@australian = a dialect from \language\l@british 
\l@newzealand = a dialect from \language\l@british 
)) (/usr/local/texlive/2016/texmf-dist/tex/latex/minted/minted.sty
Package: minted 2016/10/31 v2.4.1 Yet another Pygments shim for LaTeX
(/usr/local/texlive/2016/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks16
) (/usr/local/texlive/2016/texmf-dist/tex/latex/oberdiek/kvoptions.sty
Package: kvoptions 2016/05/16 v3.12 Key value format for package options (HO)
(/usr/local/texlive/2016/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
Package: kvsetkeys 2016/05/16 v1.17 Key value parser (HO)
(/usr/local/texlive/2016/texmf-dist/tex/generic/oberdiek/etexcmds.sty
Package: etexcmds 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
(/usr/local/texlive/2016/texmf-dist/tex/generic/oberdiek/ifluatex.sty
Package: ifluatex 2016/05/16 v1.4 Provides the ifluatex switch (HO)
Package ifluatex Info: LuaTeX not 

Minted example not displaying in pdf anymore

[Kornel Benko]

Hi,
examples/minted-listings.lyx compiles, but there is no output of the listings.
Contrary to this, minted-filelisting.lyx displays fine.

I am sure it worked previously. First I thought, it may be because of TL17 (I 
switched recently),
but after configuring TL16 and compiling again, the effect did not change.

Would be nice, if someone could confirm.

Kornel


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