syntax error in po files due to Windows line endings

[Scott Kostyshak]

On master when I do (CMake)

make layouttranslations1

I get

OSError: Syntax error in po file /home/scott/lyxbuilds/master/repo/po/ar.po 
(line 35)

and indeed there are Windows line endings.

Scott

beta will be delayed for translations

[Scott Kostyshak]

Dear all,

I am late sending out an email to translators and we need to leave them
at least 2 weeks to do their work, which means that beta1 will not be
released on 9 June. I hope to have a revised date for beta1 by this
weekend.

Sorry for my sloppy organization,

Scott

Update translations webpage with new Chinese (simplified) translator

[Scott Kostyshak]

Using the script

getTranslators.pl

and specifically the test

ctest -R "check_translators"

we can see the following mismatch:

The translator of Chinese (simplified) is listed as Yihui Xie on

https://www.lyx.org/I18n-trunk

but as Zheru Qiu in the po file. Should we change to Zheru on the
webpage?

Scott

Copying translations from 2.2.x to master?

[Scott Kostyshak]

Uwe,

Do you have time to copy the translations from 2.2.x to master? From
what I understand, you've done this in the past.

If Uwe doesn't have time, hopefully someone else can help or can tell me
what I should do.

Scott

Re: Bad Citation Bug in 2.3dev

[Richard Heck]

On 05/28/2017 12:38 PM, Jürgen Spitzmüller wrote:
> Am Sonntag, den 28.05.2017, 12:32 -0400 schrieb Richard Heck:
>> Some do, not all. 
> But if a given style requests a pagination prefix, the bst (or biblatex
> cbx) can and should be configured to output that. This is a
> prerequisite for portability between different styles (and languages).

BibTeX bst files do not control the output of citations, only of
bibliography references. Right?

>> Another question: Should the "literal" flag default to true or false?
>> Having it default to true would be consistent with pre-2.3 behavior.
>> People who wanted it otherwise could set it once and then it would
>> (should) be remembered.
> The argument for setting it to false was that novices tend to run into
> more severe problems if they enter text that is interpreted as a
> command and might not know what happens (as opposed to LaTeX
> literates).
>
> For people who are used to the current situation, there will certainly
> a learning process. But on the other hand, the situation was not very
> clear at all, since some dialogs were outputting verbatim texts, some
> not, some partially. 

Having the checkbox is fine with me. I just don't want to have to keep
checking it.

I've committed something along these lines.

Richard

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

[Enrico Forestieri]

On Mon, May 29, 2017 at 05:53:08PM -0400, Scott Kostyshak wrote:

> It is a not-so-rare situation that the user needs to add -shell-escape as an
> option to the LaTeX converter that is being used, in order to compile a
> document.
> 
> We can't ship documents that compile out-of-the-box without the user
> doing the dance of figuring out how to add the option. The average user
> does not feel comfortable modifying converter options, and further they
> need to (or at least should) remember to remove the option after they
> are done compiling a document.
> 
> It would be nice to make the process of temporarily using -shell-escape
> more user-friendly.
> 
> One solution is to add a set of converters, one for each LaTeX flavor,
> and then to specify the "needauth" flag for those converters. It would
> be unfortunate to have
> 
> LaTeX (pdflatex) (shell-escape) -> PDF (pdflatex-se)
> 
> as a completely different converter from
> 
> LaTeX (pdflatex-shell-escape) -> PDF (pdflatex)
> 
> An alternative is to recognize that really this should be a document
> setting. We could have a document option "shell-escape" (or a more
> user-friendly name) in Document > Settings > Formats, which does the
> following if checked: If an export is chosen that uses a LaTeX
> converter, -shell-escape is added to the options.
> Of course, for this approach we need to be careful. A malicious user
> could just set the document setting and then do bad stuff. So LyX
> would need to confirm once that the user trusts the document (using
> the needauth framework?).
> 
> Any thoughts?

We could ship some already defined formats and converters with the needauth
option. Then, the format with the -shell-escape can be assigned as default
for a document. When the user tries to preview it, it should be automatically
warned, I think.

For example, this is what I currently use (minus the needauth):

\format "pdf2se" "pdf" "PDF (pdflatex se)" "" "qpdfview" "" "document,vector" ""
\format "pdf4se" "pdf" "PDF (XeTeX se)" "" "qpdfview" "" "document,vector" ""
\converter "pdflatex" "pdf2se" "pdflatex --shell-escape $$i" "latex=pdflatex"
\converter "xetex" "pdf4se" "xelatex --shell-escape $$i" "latex=xelatex"

There are many examples that require the -shell-escape option. Some that come
to mind are tikz and the gnuplottex package. See the attached.

-- 
Enrico
#LyX 2.2 created this file. For more info see http://www.lyx.org/
\lyxformat 508
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\begin_preamble
\usepackage[miktex,siunitx]{gnuplottex}
\usepackage{siunitx}

% Using pdflatex, the produced eps file is automatically converted
% to pdf using epstopdf by default. Unfortunately, the cairolatex
% terminal of gnuplot inserts a couple comment lines just before
% the line "%!PS-Adobe-3.0 EPSF-3.0" that characterizes an eps file.
% This confuses the epstopdf program that comes with MikTeX, which
% issues a "Invalid binary DOS header" error and produces an empty
% pdf file. The solution is using ps2pdf.
\usepackage{epstopdf}
\epstopdfDeclareGraphicsRule{.eps}{pdf}{.pdf}{%
ps2pdf -dEPSCrop #1 \OutputFile
}
\end_preamble
\use_default_options true
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\graphics default
\default_output_format pdf2
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize 12
\spacing single
\use_hyperref false
\papersize default
\use_geometry true
\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
\leftmargin 2cm
\topmargin 2cm
\rightmargin 2cm
\bottommargin 2cm
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\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 Note Note
status open

\begin_layout Plain Layout
Remember to add the -shell-escape option to the LaTeX(pdflatex)->PDF(pdflatex)
 converter.
\end_layout

\begin_layout Plain Layout
Note that the preview is only shown after the document is typeset, because
 the preview machinery simply ignores any extra option (thus including the
 

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Richard Heck]

On 05/29/2017 05:46 PM, Scott Kostyshak wrote:
> On Mon, May 29, 2017 at 11:15:01PM +0200, Enrico Forestieri wrote:
>
>> However, given the semantics of \vspace, that change should not have an
>> effect. Indeed, when used within a paragraph, the vertical space is added
>> after the line in which the \vspace appears. So, for example, if you have
>> the following snippet:
>>
>> Here is a vspace\vspace{1cm} after this line. How can be seen it only
>> appears after the first line of this paragraph.
>>
>> Supposing that the first line ends at the word "appears", the output would be
>>
>> Here is a vspace after this line. How can be seen it only appears
>>  ↕ 1cm
>> after the first line of this paragraph.
>>
>> Thus, given that after that \vspace the line ends, one can think that 
>> a following blank line is irrelevant, but apparently it is not so.
>> Moreover, the subsequent \vspace is not followed by a blank line
>> (and this is not due to the above hunk).
> I had always wondered how \vspace in paragraphs worked. Now I understand
> and I also understand how LyX cannot display them exactly like the PDF
> output because LyX does not know where the line break will be.
>
>> Anyway, neither the change is desired, nor I can explain how that hunk
>> slipped in, so I am going to revert it.
> Thanks for the quick fix.
>
> By the way, if anyone is curious how I noticed that difference in
> spacing, it is thanks to the open-source "diffpdf" tool.
>
> I compared the PDF that stable LyX produced for me of my paper with the
> PDF that master LyX produces, with the following command:
>
> diffpdf mwe_before.pdf mwe_after.pdf
>
> Setting compare to "Appearance" leads to the attached screenshot:
>
> I find diffpdf to be a valuable tool when testing.

I can see why!!

Richard

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Richard Heck]

On 05/29/2017 05:29 PM, Enrico Forestieri wrote:
> On Mon, May 29, 2017 at 11:15:01PM +0200, Enrico Forestieri wrote:
>> Anyway, neither the change is desired, nor I can explain how that hunk
>> slipped in, so I am going to revert it.
> Reverted at 90c423a6.
>
> Richard, I fear this slipped in also in stable, so you may want to
> revert it there, too.

I've done so.

Richard

Re: Font of Labels in Section Headings

[Richard Heck]

On 05/29/2017 04:28 PM, Scott Kostyshak wrote:
> On Mon, May 29, 2017 at 02:03:10PM -0400, Richard Heck wrote:
>> In 2.3.x, the font of a label in a section heading matches that of the
>> section heading (e.g., large and bold), which leads it to consume more
>> space than it did in 2.2.x, when it was just normal size. I would
>> suggest that this be switched back.
> Attached is a patch but I'm not sure it's right.

I saw this possibility, but the comment on inheritFont in Inset.h makes
it sound as if this will also affect the LaTeX output. In any event,
what's causing the change has to be elsewhere.

Richard

Re: [LyX/master] Add an external template for minted

[Scott Kostyshak]

On Sun, May 28, 2017 at 11:44:22PM +0200, Enrico Forestieri wrote:
> commit 85dd9a2f9c81ad8641c31aa1403cab2678590a0e
> Author: Enrico Forestieri 
> Date:   Sun May 28 23:43:19 2017 +0200
> 
> Add an external template for minted
> 
> See #9095

Tested and works well. The note has clear instructions. I made a couple
of minor changes at 7f0a1df4.

Thanks for this example file,

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Add an external template for minted

[Scott Kostyshak]

On Mon, May 29, 2017 at 01:38:16PM +0200, Kornel Benko wrote:

> Ehm, my mistake. I inserted "-shel-escape" instead of "-shell-escape" in the 
> converter.

I suppose for these tests to pass, we need to use a special preference
file that changes the converters. I forget, do we currently allow for a
test to use a different preference file?

Scott


signature.asc
Description: PGP signature

Can shell-escape take advantage of needauth framework?

[Scott Kostyshak]

It is a not-so-rare situation that the user needs to add -shell-escape as an
option to the LaTeX converter that is being used, in order to compile a
document.

We can't ship documents that compile out-of-the-box without the user
doing the dance of figuring out how to add the option. The average user
does not feel comfortable modifying converter options, and further they
need to (or at least should) remember to remove the option after they
are done compiling a document.

It would be nice to make the process of temporarily using -shell-escape
more user-friendly.

One solution is to add a set of converters, one for each LaTeX flavor,
and then to specify the "needauth" flag for those converters. It would
be unfortunate to have

LaTeX (pdflatex) (shell-escape) -> PDF (pdflatex-se)

as a completely different converter from

LaTeX (pdflatex-shell-escape) -> PDF (pdflatex)

An alternative is to recognize that really this should be a document
setting. We could have a document option "shell-escape" (or a more
user-friendly name) in Document > Settings > Formats, which does the
following if checked: If an export is chosen that uses a LaTeX
converter, -shell-escape is added to the options.
Of course, for this approach we need to be careful. A malicious user
could just set the document setting and then do bad stuff. So LyX
would need to confirm once that the user trusts the document (using
the needauth framework?).

Any thoughts?

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Scott Kostyshak]

On Mon, May 29, 2017 at 11:15:01PM +0200, Enrico Forestieri wrote:

> However, given the semantics of \vspace, that change should not have an
> effect. Indeed, when used within a paragraph, the vertical space is added
> after the line in which the \vspace appears. So, for example, if you have
> the following snippet:
> 
> Here is a vspace\vspace{1cm} after this line. How can be seen it only
> appears after the first line of this paragraph.
> 
> Supposing that the first line ends at the word "appears", the output would be
> 
> Here is a vspace after this line. How can be seen it only appears
>  ↕ 1cm
> after the first line of this paragraph.
> 
> Thus, given that after that \vspace the line ends, one can think that 
> a following blank line is irrelevant, but apparently it is not so.
> Moreover, the subsequent \vspace is not followed by a blank line
> (and this is not due to the above hunk).

I had always wondered how \vspace in paragraphs worked. Now I understand
and I also understand how LyX cannot display them exactly like the PDF
output because LyX does not know where the line break will be.

> Anyway, neither the change is desired, nor I can explain how that hunk
> slipped in, so I am going to revert it.

Thanks for the quick fix.

By the way, if anyone is curious how I noticed that difference in
spacing, it is thanks to the open-source "diffpdf" tool.

I compared the PDF that stable LyX produced for me of my paper with the
PDF that master LyX produces, with the following command:

diffpdf mwe_before.pdf mwe_after.pdf

Setting compare to "Appearance" leads to the attached screenshot:

I find diffpdf to be a valuable tool when testing.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Enrico Forestieri]

On Mon, May 29, 2017 at 11:15:01PM +0200, Enrico Forestieri wrote:
> 
> Anyway, neither the change is desired, nor I can explain how that hunk
> slipped in, so I am going to revert it.

Reverted at 90c423a6.

Richard, I fear this slipped in also in stable, so you may want to
revert it there, too.

-- 
Enrico

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Enrico Forestieri]

On Mon, May 29, 2017 at 12:23:29PM -0400, Scott Kostyshak wrote:
> 
> I think (if I did git bisect correctly) this commit caused a change in
> LaTeX and PDF output that I would like to make sure is expected.
> 
> See the attached mwe.lyx file (in 2.2.x format). mwe_before.tex and
> mwe_before.pdf are the outputs before this commit, and mwe_after.tex and
> mwe_after.pdf are the outputs after this commit.
> 
> Note the differences in vertical spacing around "point2".
> 
> The only difference in the .tex files is that after this commit there is
> no empty line after the \vspace command.
> 
> Is this change desired?

At first, it seemed strange to me that a commit dealing with language
nesting could have such an effect on pretty unrelated code. But, going
through the commit, I discovered the following hunk:

> @@ -1000,7 +1103,7 @@ void TeXOnePar(Buffer const & buf,
> // prevent unwanted whitespace
> os << '%';
> if (!os.afterParbreak() && !last_was_separator)
> -   os << '\n';
> +   os << breakln;
> }
> 
> // if this is a CJK-paragraph and the next isn't, close CJK
> 

which is responsible for the change. I really don't remember why I made
that change, which seems completely unrelated.

However, given the semantics of \vspace, that change should not have an
effect. Indeed, when used within a paragraph, the vertical space is added
after the line in which the \vspace appears. So, for example, if you have
the following snippet:

Here is a vspace\vspace{1cm} after this line. How can be seen it only
appears after the first line of this paragraph.

Supposing that the first line ends at the word "appears", the output would be

Here is a vspace after this line. How can be seen it only appears
 ↕ 1cm
after the first line of this paragraph.

Thus, given that after that \vspace the line ends, one can think that 
a following blank line is irrelevant, but apparently it is not so.
Moreover, the subsequent \vspace is not followed by a blank line
(and this is not due to the above hunk).

Anyway, neither the change is desired, nor I can explain how that hunk
slipped in, so I am going to revert it.

-- 
Enrico

Re: Font of Labels in Section Headings

[Scott Kostyshak]

On Mon, May 29, 2017 at 02:03:10PM -0400, Richard Heck wrote:
> In 2.3.x, the font of a label in a section heading matches that of the
> section heading (e.g., large and bold), which leads it to consume more
> space than it did in 2.2.x, when it was just normal size. I would
> suggest that this be switched back.

Attached is a patch but I'm not sure it's right.

Scott
diff --git a/src/insets/InsetLabel.h b/src/insets/InsetLabel.h
index 65a6d3a..fb055aa 100644
--- a/src/insets/InsetLabel.h
+++ b/src/insets/InsetLabel.h
@@ -44,6 +44,8 @@ public:
///
bool isLabeled() const { return true; }
///
+   bool inheritFont() const { return false; }
+   ///
bool hasSettings() const { return true; }
///
InsetCode lyxCode() const { return LABEL_CODE; }

Font of Labels in Section Headings

[Richard Heck]

In 2.3.x, the font of a label in a section heading matches that of the
section heading (e.g., large and bold), which leads it to consume more
space than it did in 2.2.x, when it was just normal size. I would
suggest that this be switched back.

Richard

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Scott Kostyshak]

On Sat, Sep 24, 2016 at 03:25:42AM +0200, Enrico Forestieri wrote:
> commit 3bc08a76c42cd350a3141f00f37082bc9fab8967
> Author: Enrico Forestieri 
> Date:   Sat Sep 24 03:15:02 2016 +0200
> 
> Sort the language nesting mess with polyglossia
> 
> When using polyglossia, lyx was making a real mess when changing
> language inside nested insets. The \begin{language} and
> \end{language} commands were not well paired such that they could
> easily occur just before and after the start or end of an
> environment. Of course this was causing latex errors such that
> "\begin{otherlanguage} ended by \end{environment}".
> There may still be some cases I did not take into account.

I think (if I did git bisect correctly) this commit caused a change in
LaTeX and PDF output that I would like to make sure is expected.

See the attached mwe.lyx file (in 2.2.x format). mwe_before.tex and
mwe_before.pdf are the outputs before this commit, and mwe_after.tex and
mwe_after.pdf are the outputs after this commit.

Note the differences in vertical spacing around "point2".

The only difference in the .tex files is that after this commit there is
no empty line after the \vspace command.

Is this change desired?

Scott
#LyX 2.2 created this file. For more info see http://www.lyx.org/
\lyxformat 508
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass beamer
\use_default_options true
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry true
\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 english
\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 Frame
\begin_inset Argument 4
status open

\begin_layout Plain Layout
One more extension
\end_layout

\end_inset


\begin_inset Separator latexpar
\end_inset


\end_layout

\begin_deeper
\begin_layout Standard
A common theme in this presentation has been about how OLS is not good at...
 I propose...:
\begin_inset VSpace 0.5cm
\end_inset


\end_layout

\begin_layout Quote
point 1
\end_layout

\begin_layout Standard
\begin_inset VSpace 0.5cm
\end_inset

point2:
\end_layout

\begin_layout Enumerate
point2.1
\end_layout

\begin_layout Enumerate
point2.2
\end_layout

\end_deeper
\end_body
\end_document


mwe_after.pdf
Description: Adobe PDF document


mwe_after.tex
Description: TeX document


mwe_before.pdf
Description: Adobe PDF document


mwe_before.tex
Description: TeX document


signature.asc
Description: PGP signature

Should child docs inherit trust for needauth converter?

[Scott Kostyshak]

I have a master document and several child documents that use knitr. If
I click on "Run", which is the prompt from the master, I am still
prompted for each child.

I'm conflicted by what I think is the ideal behavior. I'm also biased
since I find the multiple prompts annoying (but this is only temporary
and easily solved).

I suppose the way to think through it is the following: Is there an
example where you would want to trust the parent but not trust the
child?

Perhaps you get the prompt for the parent, and say "I looked through
this document and looked at the knitr chunks and know that none of the
code is malicious" so I trust the document, and then a prompt for the
child doc comes and you say "I did not know that the child doc used
knitr, I want to check it also for malicious code". That's the best
example I can come up with, but I'm not very convinced by it.

I suppose in cases of security, unless I can make a sound-proof argument
to get rid of the additional prompts, we should just keep them.

Any thoughts?

Scott


signature.asc
Description: PGP signature

Re: Bug #10295

[Scott Kostyshak]

On Tue, May 16, 2017 at 10:18:05PM -0400, Richard Heck wrote:
> Can anyone test the fix for this bug posted at
> 
> http://www.lyx.org/trac/ticket/10295
> 
> It'd be nice to have a decent version for beta1.

I can't reproduce the bug. Can anyone reproduce and then check that
Richard's patch makes it go away?

Scott


signature.asc
Description: PGP signature

Re: Different LaTeX output when exporting than when previewing

[Scott Kostyshak]

On Wed, Nov 02, 2016 at 09:23:23PM -0400, Scott Kostyshak wrote:
> On Wed, Nov 02, 2016 at 09:43:05PM +0100, Jürgen Spitzmüller wrote:
> 
> > I would like to investigate, but if we cannot reproduce, there is not
> > much we can do.
> 
> OK, I don't have an idea either.

I can reproduce with the following:

To use the below, "lyx" is the binary from current master for me.

# cd to the git repository
cd lib/doc/es
testFile="EmbeddedObjects"
lyx -E luatex "${testFile}_CL.tex" "${testFile}.lyx"
lyx -x "command-sequence buffer-export luatex" "${testFile}.lyx"
# exit LyX.
diff "${testFile}_CL.tex" "${testFile}.tex"

If I do the above several times, I eventually get:
3c3
<
\documentclass[12pt,english,ngerman,spanish,bibliography=totoc,index=totoc,BCOR7.5mm,titlepage,captions=tableheading,dvipsnames,table]{scrbook}
---
> \documentclass[12pt,ngerman,english,spanish,bibliography=totoc,index=totoc,BCOR7.5mm,titlepage,captions=tableheading,dvipsnames,table]{scrbook}
--

Can anyone else reproduce if they do the above a few times?

Scott


signature.asc
Description: PGP signature

Re: #10119: Shortcut Control-M

[Scott Kostyshak]

On Mon, May 29, 2017 at 08:19:55AM +0200, Luca Brandolini wrote:
> It seems that in Mac OSX Italian keyboard 'Ctrl-m' is mapped to ‘?’.

Do you mean this is independent of LyX? That is, do you think that the
issue is LyX's fault or is it a more general issue on Mac OS?

> I have a modified layout of the Italian keyboard in which Ctrl-m is mapped to 
> ‘U+D’. With this layout LyX works correctly.

Good to know.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Add an external template for minted

[Kornel Benko]

Am Montag, 29. Mai 2017 um 13:22:59, schrieb Kornel Benko 
> Am Montag, 29. Mai 2017 um 11:38:25, schrieb Enrico Forestieri 
> 
> > On Mon, May 29, 2017 at 12:59:43AM +0200, Kornel Benko wrote:
> > > 
> > > Do we have to install something first?
> > 
> > Please, have a look at the note inset in the example file.
> > 
> 
> I did, and all seemed to be installed.
> But the message about  'external template MintedSource not installed'.
> is disturbing.
> 
> Reconfiguring lyx.
> 
> Now this message disappeared and the remaining errors are
>   
>   ! Package minted Error: You must have `pygmentize' installed to use 
> this package
> 
> Interesting, I have it installed. Do I miss a conversion entry?

Ehm, my mistake. I inserted "-shel-escape" instead of "-shell-escape" in the 
converter.

Kornel

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

Re: [LyX/master] Add an external template for minted

[Kornel Benko]

Am Montag, 29. Mai 2017 um 11:38:25, schrieb Enrico Forestieri 
> On Mon, May 29, 2017 at 12:59:43AM +0200, Kornel Benko wrote:
> > 
> > Do we have to install something first?
> 
> Please, have a look at the note inset in the example file.
> 

I did, and all seemed to be installed.
But the message about  'external template MintedSource not installed'.
is disturbing.

Reconfiguring lyx.

Now this message disappeared and the remaining errors are

! Package minted Error: You must have `pygmentize' installed to use 
this package

Interesting, I have it installed. Do I miss a conversion entry?

Kornel

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

Re: [LyX/master] Add an external template for minted

[Enrico Forestieri]

On Mon, May 29, 2017 at 12:59:43AM +0200, Kornel Benko wrote:
> 
> Do we have to install something first?

Please, have a look at the note inset in the example file.

-- 
Enrico

Re: #10119: Shortcut Control-M

[Luca Brandolini]

It seems that in Mac OSX Italian keyboard 'Ctrl-m' is mapped to ‘?’.  I have a 
modified layout of the Italian keyboard in which Ctrl-m is mapped to ‘U+D’. 
With this layout LyX works correctly.

> Il giorno 28 mag 2017, alle ore 00:23, LyX Ticket Tracker  ha 
> scritto:
> 
> #10119: Shortcut Control-M
> -+-
> Reporter:  luca.brandolini  |   Owner:  lasgouttes
> Type:  defect   |  Status:  new
> Priority:  normal   |   Milestone:  2.2.x
> Component:  keyboard | Version:  2.2.3
> Severity:  normal   |  Resolution:
> Keywords:  os=macos |
> -+-
> 
> Comment (by forenr):
> 
> Replying to [comment:25 skostysh]:
>> Enrico, have you ever seen this behavior with an Italian keyboard? I'm
> guessing no since you don't use Mac OS, but thought I would check.
> 
> No, sorry. It works fine with an Italian keyboard on both Windows and
> Linux. But MacOS is a different beast.
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor