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 

Re: Module for ellipsis

[racoon]

On 21.06.2017 23:42, Jürgen Spitzmüller wrote:
2017-06-21 14:46 GMT+02:00 racoon >:


Great. Yes, there are a number of things in which respect my module
is limited. I guess the csquotes command could be helpful. But there
is no LyX module for that yet, right?


Not, not officially. I have my own one (attached). This is also 
available on the Wiki (http://wiki.lyx.org/Layouts/Modules)


Thanks. Very nice. If I see it correctly there is not yet support for 
leaving the left out text from a quote in a note. I'll try to add it 
when I find time.


Also, I am wondering about your "Source" inset/argument. In the example 
file you provide, it strikes me as odd that it automatically adds 
brackets around the "citation". Because that is already taken care of by 
the citation itself. Maybe that inset should be used only when not using 
the "Insert citation" function? You might want to fix your example file 
in that way. Or have a missed something?


Daniel

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.

Re: Server rebooted

[Christian Ridderström]

Richard wrote:

> These look correct to me, but I usually use iptables via shorewall.
>
> That said, those are massive subnets to block. I guess if we're blocking
> legitimate users, we'll hear about it.
>

If the blocks seem to work I was thinking of announcing to users list the
blocked ranges, together with an explanation.

Separately, I was thinking of unblocking some of the ranges to see if the
server still works after a few days. We still don't know why we run low on
memory, ie if its related to Trac, a wiki or git or something else. So if
the server starts losing memory, I can see the IP of the culprit and then
perhaps figure out which of our services that has the memory leak.

Cheers,
Christian


>
> Richard
>
>

Re: #10119: Shortcut Control-M

[Stephan Witt]

Am 10.06.2017 um 19:26 schrieb Scott Kostyshak :
> 
> On Sat, Jun 10, 2017 at 03:36:28PM +0200, Stephan Witt wrote:
>> Am 09.06.2017 um 23:09 schrieb Scott Kostyshak :
>>> 
>>> On Fri, Jun 09, 2017 at 10:17:25PM +0200, Stephan Witt wrote:
>>> 
 Sorry, I don’t have the time right now, but I should have answered.
>>> 
>>> No problem at all, thanks for the response. Now that I've bugged you
>>> about it I can take it off my todo list :)
>> 
>> I gave it a try and it’s as bad as I was fearing…
>> 
>> The mixture of different changes of build environments is causing trouble.
>> I’m unable to compile most of the versions between 2.1.5 and 2.2.3 on my 
>> Macbook with 10.12 SDK.
>> 
>> I get errors and have to skip bisect.
>> 
>> Either this:
>> 
>> In file included from /Users/stephan/git/lyx/src/support/debug.cpp:21:
>> /Users/stephan/git/lyx/src/support/../support/regex.h:16:12: fatal error: 
>> 'regex' file not found
>> #  include 
>> 
>> or this:
>> make[4]: *** No rule to make target `ConsoleApplicationPrivate.h', needed by 
>> `moc_ConsoleApplicationPrivate.cpp'.  Stop.
>> 
>> After doing this 8 times I’m giving up.
> 
> Ouch, that is frustrating. Sorry for asking you to do that. I appreciate
> your trying, Stephan. Let's forget about this issue then and assume it
> was a change in Qt until we receive evidence otherwise.

No problem. After some thinking I did remember I’m using different compilers
for building the 2.2 branch and master… avoiding clang for the builds let me
pass this and I could do the bisect and I’ve learned it works well with Qt4
for 2.2.3dev and not with Qt5 and LyX 2.2.1 - it must be a Qt4 vs. Qt5 issue.

But that info doesn’t help. LyX 2.1.5 was build and packaged with Qt4.

So I’ve tried to run LyX 2.1.5 with Qt5. But this doesn’t work either.
I can build it but the executable crashes because of unresolved runtime
dependencies. Dead end again.

Stephan

Re: [LyX/2.2.x] Fix bugs #9598 and #10650

[Enrico Forestieri]

On Tue, Jun 20, 2017 at 02:45:19AM +0200, Guillaume MM wrote:

> Le 08/06/2017 à 02:07, Enrico Forestieri a écrit :
> > On Thu, Jun 08, 2017 at 12:50:19AM +0200, Guillaume MM wrote:
> > 
> > > Le 05/06/2017 à 23:15, Enrico Forestieri a écrit :
> > > > commit 59c22bd7b604a3ba9e0e78f7c51cb601f08d0192
> > > > Author: Enrico Forestieri
> > > > Date:   Mon Jun 5 23:14:48 2017 +0200
> > > > 
> > > >   Fix bugs #9598 and #10650
> > > > ---
> > > 
> > > > +// gcc < 4.8.0 and msvc < 2015 do not support C++11 thread_local
> > > > +#if defined(__GNUC__) && ((__GNUC__ == 4 && __GNUC_MINOR__ < 8) || 
> > > > __cplusplus < 201103L)
> > > > +#define THREAD_LOCAL_STATIC static __thread
> > > > +#elif defined(_MSC_VER) && ((_MSC_VER < 1900) || __cplusplus < 201103L)
> > > > +#define THREAD_LOCAL_STATIC static __declspec(thread)
> > > > +#else
> > > > +#define THREAD_LOCAL_STATIC thread_local static
> > > > +#endif
> > > > +
> > > 
> > > 
> > > According to Stephan in this discussion:
> > > 
> > > https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg196176.html
> > > 
> > > it is unfortunately not possible to use thread_local on Mac before some
> > > time, it seems. I would actually be happy to hear the contrary.
> > 
> > Note that I also added the check for __cplusplus < 201103L, which should
> > assure full compliance with C++11.
> 
> Only in a perfect world. Note also that for clang you are always taking
> the first branch so the value of __cplusplus is irrelevant. If
> intentional, I suggest that you make it clear in the comment.

This is not important. Either branches would do. If you think that
clang deserves an exception, you can add it.

> > If thread_local is not supported, the
> > compiler should not set __cplusplus to such value or higher and thus
> > should use the fallback definition.
> 
> Sorry, this does not make sense to me. First, all of your definitions
> use some form of thread-local storage. The problem referred to above is
> that there is no implementation of it at all, even called __thread or
> something else. You do not acknowledge that there is an issue, so it
> is not clear to me that you have read the discussion mentioned above
> carefully. To the best of our knowledge, in the best case your current
> patch requires a discussion about dropping the support of Xcode < 8.
 
No, I don't see anything about the non existence of __thread. Instead,
I see that for gcc < 4.8 this existence is guaranteed. No report has
been received so far about compiling problems. If they should come in,
they will be properly addressed.
 
> > > (Also, it had been decided that LyX requires msvc ≥ 2015 so the second
> > > branch would not be necessary.)
> > 
> > I don't think that LyX really cannot be compiled with older versions.
> > Are there reports in this regard?
> > 
> 
> There was a discussion at
> 
> and parent messages, and maybe someplace else as well. Since my patch on
> Unicode string literals alluded to in that message is not going to be
> committed before 2.4 at least, it could make sense to support MSVC 2013
> in 2.3 if it currently works. What worries me most is lack of support
> for 
> ("magic statics") for which your criteria “does it compile?” is not
> going to be enough.

So, I don't see any problem with the second branch.

-- 
Enrico

Re: Module for ellipsis

[Jürgen Spitzmüller]

2017-06-21 14:46 GMT+02:00 racoon :

> Great. Yes, there are a number of things in which respect my module is
> limited. I guess the csquotes command could be helpful. But there is no LyX
> module for that yet, right?
>

Not, not officially. I have my own one (attached). This is also available
on the Wiki (http://wiki.lyx.org/Layouts/Modules)

Jürgen


>
> Daniel
>
>
>


csquotes.module
Description: Binary data

Re: dash patch for stable

[Enrico Forestieri]

On Tue, Jun 20, 2017 at 02:59:00AM +0200, Guillaume MM wrote:
> 
> Enrico, I also have to criticise this sort of comment of yours. I am
> sorry to say that to me it looks disconnected with the understanding of
> the problem at the time and gratuitous.

Guillame, I have also to criticize this hypocritical comment of yours.
You are simply trying to giving back the same criticism you received
in the past. Sorry, but this shows your real attitude.

-- 
Enrico

Re: [LyX/master] Use otexstringstream for the captions of InsetCaptionables

[Enrico Forestieri]

On Tue, Jun 20, 2017 at 02:58:17AM +0200, Guillaume MM wrote:

> Le 11/06/2017 à 01:08, Enrico Forestieri a écrit :
> > On Mon, Oct 17, 2016 at 00:16:21AM +0200, Guillaume Munch wrote:
> > 
> > > commit 676a0639c505d52336e3228c44c2515ccbbaf34a
> > > Author: Guillaume Munch 
> > > Date:   Sat Sep 24 00:49:00 2016 +0200
> > > 
> > >  Use otexstringstream for the captions of InsetCaptionables
> > >  * Enable TexRow for InsetListings caption.
> > >  * Move getCaption* from InsetText to InsetCaptionable.
> > >  * Clean-up caption generation for InsetFloat.
> > [...]
> > > @@ -420,7 +417,11 @@ docstring InsetListings::getCaption(OutputParams 
> > > const & runparams) const
> > >   // NOTE that } is not allowed in blah2.
> > >   regex const reg("(.*)label\\{(.*?)\\}(.*)");
> > >   string const new_cap("$1$3},label={$2");
> > > - return from_utf8(regex_replace(to_utf8(cap), reg, new_cap));
> > > + // TexString validity: the substitution preserves the number of 
> > > newlines.
> > > + // Moreover we assume that $2 does not contain newlines, so that the 
> > > texrow
> > > + // information remains accurate.
> > > + cap.str = from_utf8(regex_replace(to_utf8(cap.str), reg, new_cap));
> > > + return cap;
> > >   }
> > 
> > This commit broke the caption handling in InsetListings. For example,
> > the document attached at #9382:
> > https://www.lyx.org/trac/raw-attachment/ticket/9382/problem.20_nopreamble.lyx
> > now fails to compile. It can be compiled again with the attached patch,
> > which is not the right one, of course.
> > 
> 
> 
> Dear Enrico,
> 
> 
> I had a look at this issue 8 days ago since you pointed at my commit. I
> realised then that my commit did nothing to worsen or improve this
> issue (the commit is meant to leave the output unchanged, and the bug
> appears in LyX 2.2.2 where this line of commits has never been). Sorry
> for the wait: I did not have much time on my hands and it was not a
> regression for me so I decided to postpone my reply until I had more time.
> 
> I now see that you are proposing a patch at
> . I have several questions about
> your patch.
> 
> Given that you had located a regression (you even point to a specific
> part of the code), have you tried to see what was causing the regression
> in the commit while coming up with a patch? I think that trying to do so
> would show you that the commit you are pointing to actually leaves the
> output unchanged.
> 
> In your bug report you notice that the bug is present in stable and you
> say to Scott that the patch is valid for stable. It does not apply. Why
> did you let Scott think that you have tested your patch on stable? I
> think that if you had, then you could have noticed that the commit was
> never backported.
> 
> As you know, you are writing to a developers list where people are
> willing to put in their valuable time to help you, and expect accurate
> technical informations. It happens to make a mistake, but it does not
> make sense to me that with enough care you did not find an occasion to
> correct yourself.
> 
> I want to be able to trust technical claims that are made on the list in
> the future, and so do other developers probably. I try to always
> double-check technical claims I make and sometimes it helps me catch
> errors at the last moment. I would like to be sure that we agree on
> everybody putting in the same care in their contributions.

I can't stand hypocrisy. You could have said "are you sure?"
Instead, you put it on an act. I thought you were willing
to change your attitude. But I was wrong, apparently.
I'll simply leave you alone.

-- 
Enrico

Re: Module for ellipsis

[racoon]

On 21.06.2017 21:56, Jürgen Spitzmüller wrote:
2017-06-21 10:47 GMT+02:00 racoon >:


I guess it would be nice to have a setting for what should be used
as replacement. For example, some author's prefer […] to …. This
would then also provide an easy way to switch between different
replacements. Maybe some publishers prefer the one or the other.


There are packages that deal with this (e.g., csquotes).


Great. Yes, there are a number of things in which respect my module is 
limited. I guess the csquotes command could be helpful. But there is no 
LyX module for that yet, right?


Daniel

Re: Module for ellipsis

[racoon]

On 21.06.2017 21:39, Pavel Sanda wrote:

racoon wrote:

necessary. But an ellipsis is not really a note and messes up the list of
notes.


Would your problem be solved by using branch named ellipsis?


I don't know what you mean.

Daniel

Re: Can shell-escape take advantage of needauth framework?

[Jürgen Spitzmüller]

2017-06-21 10:16 GMT+02:00 Jean-Marc Lasgouttes :

> We could try something in the status bar.
>

I also thought about this, and I would prefer it much over a toolbar button.

Jürgen


>
> JMarc
>

Re: Module for ellipsis

[Jürgen Spitzmüller]

2017-06-21 10:47 GMT+02:00 racoon :

> I guess it would be nice to have a setting for what should be used as
> replacement. For example, some author's prefer […] to …. This would then
> also provide an easy way to switch between different replacements. Maybe
> some publishers prefer the one or the other.
>

There are packages that deal with this (e.g., csquotes).

Jürgen

Re: Module for ellipsis

[Pavel Sanda]

racoon wrote:
> necessary. But an ellipsis is not really a note and messes up the list of 
> notes.

Would your problem be solved by using branch named ellipsis?
Pavel

Re: Module for ellipsis

[racoon]

On 21.06.2017 18:49, Jean-Marc Lasgouttes wrote:

Le 21/06/2017 à 10:47, racoon a écrit :

Hi!

When directly quoting left out parts have to be marked with an 
ellipsis. In LyX, I often put the left out parts in a note to look 
them up when necessary. But an ellipsis is not really a note and 
messes up the list of notes.


The attached module takes care of this and places the ellipsis symbol. 
I guess it would be nice to have a setting for what should be used as 
replacement. For example, some author's prefer […] to …. This would 
then also provide an easy way to switch between different 
replacements. Maybe some publishers prefer the one or the other.


What do you think about the solution? Would it be worth putting the 
module into the LyX modules or on the website?


Hi,

Just a technical remark on the module : the definition of remellipsis 
should be put in the style itself, so that the preamble snippet is used 
when the style itself is used.


Good point. New version attached.


Also, does it work with multiple paragraphs? Should it?


The module keeps the formatting as it is, including multiple paragraphs. 
I think that makes sense given one wants to know exactly what was replaced.


Or do you mean whether it inserts a break when text over multiple 
paragraphs is replaced. No, one will have to take care of this oneself.


Daniel
#\DeclareLyXModule{Ellipsis}
#DescriptionBegin
#Replace text with an ellipsis
#DescriptionEnd

Format 60

InsetLayout Flex:Ellipses
LabelString "…"
LatexType   command
LatexName   remellipsis
LyXType custom
Decoration  classic
BgColor   notebg
Font
  Color collapsable
EndFont
LabelFont
Color   note
  SizeSmall
EndFont
MultiPar  true
Preamble
  \newcommand\remellipsis[1]{%
\ldots{}%
  }
EndPreamble
End

Re: Module for ellipsis

[Jean-Marc Lasgouttes]

Le 21/06/2017 à 10:47, racoon a écrit :

Hi!

When directly quoting left out parts have to be marked with an ellipsis. 
In LyX, I often put the left out parts in a note to look them up when 
necessary. But an ellipsis is not really a note and messes up the list 
of notes.


The attached module takes care of this and places the ellipsis symbol. I 
guess it would be nice to have a setting for what should be used as 
replacement. For example, some author's prefer […] to …. This would then 
also provide an easy way to switch between different replacements. Maybe 
some publishers prefer the one or the other.


What do you think about the solution? Would it be worth putting the 
module into the LyX modules or on the website?


Hi,

Just a technical remark on the module : the definition of remellipsis 
should be put in the style itself, so that the preamble snippet is used 
when the style itself is used.


Also, does it work with multiple paragraphs? Should it?

JMarc

Module for ellipsis

[racoon]

Hi!

When directly quoting left out parts have to be marked with an ellipsis. 
In LyX, I often put the left out parts in a note to look them up when 
necessary. But an ellipsis is not really a note and messes up the list 
of notes.


The attached module takes care of this and places the ellipsis symbol. I 
guess it would be nice to have a setting for what should be used as 
replacement. For example, some author's prefer […] to …. This would then 
also provide an easy way to switch between different replacements. Maybe 
some publishers prefer the one or the other.


What do you think about the solution? Would it be worth putting the 
module into the LyX modules or on the website?


Daniel
#\DeclareLyXModule{Ellipsis}
#DescriptionBegin
#Replace text with an ellipsis
#DescriptionEnd

Format 60

AddToPreamble
\newcommand\remellipsis[1]{%
\ldots{}%
}
EndPreamble

InsetLayout Flex:Ellipses
LabelString "…"
LatexType   command
LatexName   remellipsis
LyXType custom
Decoration  classic
BgColor   notebg
Font
  Color collapsable
EndFont
LabelFont
Color   note
  SizeSmall
EndFont
MultiPar  true
End

Re: Can shell-escape take advantage of needauth framework?

[Jean-Marc Lasgouttes]

Le 21/06/2017 à 07:15, Guillaume MM a écrit :
I disagree. I think that this toolbar button even more promotes the 
option to enable a potentially risky feature.


I am not sure what you mean, but to be clear, adding visual feedback
and the ability to revoke permissions solves some of needauth's
shortcomings, and I do not really care about the particular form it
would take.


We could try something in the status bar.

JMarc