Re: Adding a Local Layout for a \newcommand

[Dr Eberhard Lisse]

Even Cooler :-)-O

That will help me for a number of things.

And, I can move the luacode from the preamble into the layout if I
really wanted to :-)-O

greetings, el

On 25/04/2017 06:28, Guenter Milde wrote:
> On 2017-04-22, Dr Eberhard Lisse wrote:
>> Thanks.
> 
>> It did help to come up with:
> 
>> in the Preamble:
> 
>> \newcommand\LMP[1]{#1}
> 
> 
>> In Settings->Local Layout:
> 
>> Format 60
>> Style EDD
>>CopyStyle Date
>>LabelFont
>>Series Bold
>>Color Red
>>EndFont
>>LatexName renewcommand
>>LatexParam {\LMP}
>>LabelString "LMP:"
>> End
> 
>> which does exactly what I want, and with the look I wanted.
> 
> To have it all in one place, you can move the preamble definition into
> the Style
> 
> Style EDD
>CopyStyle Date
>LabelFont
>Series Bold
>Color Red
>EndFont
>LatexName renewcommand
>LatexParam {\LMP}
>LabelString "LMP:"
>Preamble
>  \newcommand\LMP[1]{#1}
>EndPreamble
> End
> 
> Günter
> 
> 

Re: Index does not print

[Richard Heck]

On 04/24/2017 11:41 PM, Karthik Tayur wrote:
> Replacing all special characters (Insert>Symbols) in the document
> allows me to print the indices. I had inserted the pilcrow symbol in
> the document. When resolving a problem with conversion I replaced all
> the symbols in my document with text.
> Any idea why this works? Are special symbols not allowed in footnote
> spaces?

If you could produce a small file, as small as possible, that
illustrates the problem, it would make it easier to investigate. The
reason it should be small is so we can be sure where the problem really is.

Richard


>
>
> On 25 April 2017 at 03:42, Karthik Tayur  > wrote:
>
> Hello,
> I have been using LyX for some time now. It has been great.
> Previously the multiple index function worked well.
> Today, while I was able to insert indices, they wouldn't print.
> Only disabling the multiple index option under Settings in a fresh
> document allows printing of the singular index.
> Any suggestions as to how I might go about solving this problem? I
> suspect that the files needed for \printindex simply don't
> compile, as the logs seem to suggest.
>
> System Details: Arch Linux with KDE, LyX 2.2.2
>
> Regards
>
>

texlive in Debian

[Wolfgang Engelmann]

I am frequently reminded by the Debian system to install texlive, which 
is, however, of 2014, whereas I am using the one of 2016.


If I click the various texlive packages away (a bit cumbersome, around 
14 or so packages) I am told that it is needed for removing a security 
risk.


What should I do? I would rather like to stick to the 2015 version. Does 
this version give me the security? Or should I install the 2016 version? 
Or wait for the 2017 version?


Thanks for help.

Wolfgang