Re: How to extend a standard layouts

[Joel Kulesza]

On Sat, Jan 20, 2018 at 9:30 AM, racoon  wrote:

> By default LyX loads standard layouts and insets. Is there a way to extend
> them without overwriting the default .inc file and without using a module?
>

Would putting your changes into the Document's Local Layout (and optionally
saving as document defaults) be satisfactory?

Re: Skim as PDF-file-viewer on Mac

[Sehr Extrem]

Hello Scott,

sorry for answering late.
I still use LyX 2.2.3 and it works fine for me to use Skim 1.4.29 as 
file-viewer, nonetheless one or two commands »Skim.app« in the command-line. I 
think it works, because I just changed the general habit for my mac, so that 
every PDF now is opened with Skim. Not a very consequent solution, though, but 
it works for me…

Best
Jess



On 20. Jan. 2018, 18:19 +0100, racoon , wrote:
> On 25.06.2017 16:52, jezZiFeR wrote:
> > Hello,
> >
> > I would like to use Skim on Mac (10.12.5) as a PDF-file-viewer for
> > LuaTeX-Output, but it does not work for me.
> >
> >
> >
> > • In Lyx LyX Version 2.2.3 I have entered the following:
> >
> > Prefs / Output / General / PDF-Command:
> > /Applications/Skim.app/Skim.app/Contents/SharedSupport/displayline $$n
> > $$o $$t
>
> At least one problem is that there seems to be a "Skim.app" too many in
> the PDF-Command.
>
> Daniel
>

How to extend a standard layouts

[racoon]

By default LyX loads standard layouts and insets. Is there a way to 
extend them without overwriting the default .inc file and without using 
a module?


Let's say I want to extend the standard Note style.

I don't want to use a module since I want to make a non-optional change 
to the Note inset. For example, I want to use another font size for all 
LyX notes.


If I understood correctly, I can just put a copy of the stdinset.inc 
file from the library to the user directory. But this will have the 
unwelcome effect to overwrite whatever is in the stdinset.inc in the 
library directory. So, to avoid unwanted consequences, I will have to 
update my user stdinset.inc every time the library stdinset.inc changes, 
for example, in a new version of LyX.


So I would rather like to *extend* the current library file by just the 
font-size changes by


InsetLayout Note:Note
CopyStyle Note
Font
SizeSmall
EndFont
End

So LyX should load the library's stdinset.inc first and then load the 
code that extends it next.


Is there currently a way to do this?

Daniel

Re: Skim as PDF-file-viewer on Mac

[racoon]

On 25.06.2017 16:52, jezZiFeR wrote:

Hello,

I would like to use Skim on Mac (10.12.5) as a PDF-file-viewer for 
LuaTeX-Output, but it does not work for me.




• In Lyx LyX Version 2.2.3 I have entered the following:

Prefs / Output / General / PDF-Command:
/Applications/Skim.app/Skim.app/Contents/SharedSupport/displayline $$n 
$$o $$t


At least one problem is that there seems to be a "Skim.app" too many in 
the PDF-Command.


Daniel

LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Scott Kostyshak]

I have a paper where I set the language to "English (USA)". I am not
normally so patriotic, but I do this to get the conventional quoting
used in USA journals where punctuation in the references are inside the
quotation marks, e.g., <<"This is a Title.">> instead of <<"This is a
Title".>>. I could instead set the language of Biblatex directly so the
following issue would not matter, but I am stubborn.

Most of my other .lyx files use the language "English", and so whenever
I paste from one of those .lyx files into my "English (USA)" .lyx file,
the pasted text is (correctly) marked with a blue line because it is a
different language, "English". I then just need to select the text I
just pasted in and change it from "English" to "English (USA)." I do
this maneuver enough times that I find it annoying.

Does anyone else run into this annoyance, e.g., with other forms of
English, French, German, etc? If not, then I don't think we should
change anything.

If others do find this annoying, perhaps we can think of an improvement.
The ideal behavior for me would be that whenever I paste text that is in
language "mylanguage (x)" into a document that has language "mylanguage
(y)" and no other language, the text would be pasted as
"mylanguage (y)". However, thinking about what the LyX behavior should
be, I don't know what to suggest. On the one hand, I don't think we
should change the default behavior since it is correct to treat
"mylanguage (x)" and "mylanguage (y)" as different languages.
On the other, I don't think this is a big enough issue that we should
have a preference for it. So I don't know what to suggest.

Thoughts?

Scott



signature.asc
Description: PGP signature

Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Richard Heck]

On 01/20/2018 05:39 PM, Scott Kostyshak wrote:
> I have a paper where I set the language to "English (USA)". I am not
> normally so patriotic, but I do this to get the conventional quoting
> used in USA journals where punctuation in the references are inside the
> quotation marks, e.g., <<"This is a Title.">> instead of <<"This is a
> Title".>>. I could instead set the language of Biblatex directly so the
> following issue would not matter, but I am stubborn.
>
> Most of my other .lyx files use the language "English", and so whenever
> I paste from one of those .lyx files into my "English (USA)" .lyx file,
> the pasted text is (correctly) marked with a blue line because it is a
> different language, "English". I then just need to select the text I
> just pasted in and change it from "English" to "English (USA)." I do
> this maneuver enough times that I find it annoying.
>
> Does anyone else run into this annoyance, e.g., with other forms of
> English, French, German, etc? If not, then I don't think we should
> change anything.
>
> If others do find this annoying, perhaps we can think of an improvement.
> The ideal behavior for me would be that whenever I paste text that is in
> language "mylanguage (x)" into a document that has language "mylanguage
> (y)" and no other language, the text would be pasted as
> "mylanguage (y)". However, thinking about what the LyX behavior should
> be, I don't know what to suggest. On the one hand, I don't think we
> should change the default behavior since it is correct to treat
> "mylanguage (x)" and "mylanguage (y)" as different languages.
> On the other, I don't think this is a big enough issue that we should
> have a preference for it. So I don't know what to suggest.
>
> Thoughts?

Maybe another form of "paste special" that would just ignore the
language? That would probably take care of most of the use cases here.

Richard

Re: How to extend a standard layouts

[racoon]

On 20.01.2018 19:22, Joel Kulesza wrote:
On Sat, Jan 20, 2018 at 9:30 AM, racoon > wrote:


By default LyX loads standard layouts and insets. Is there a way to
extend them without overwriting the default .inc file and without
using a module?


Would putting your changes into the Document's Local Layout (and 
optionally saving as document defaults) be satisfactory?


Thanks. Right that is an option. But that is not ideal either. It would, 
for example, mean that I have to add it to all files I already created.

Re: How to extend a standard layouts

[Joel Kulesza]

On Sat, Jan 20, 2018 at 2:58 PM, racoon  wrote:

> On 20.01.2018 19:22, Joel Kulesza wrote:
>
>> On Sat, Jan 20, 2018 at 9:30 AM, racoon  xraco...@gmx.de>> wrote:
>>
>> By default LyX loads standard layouts and insets. Is there a way to
>> extend them without overwriting the default .inc file and without
>> using a module?
>>
>>
>> Would putting your changes into the Document's Local Layout (and
>> optionally saving as document defaults) be satisfactory?
>>
>
> Thanks. Right that is an option. But that is not ideal either. It would,
> for example, mean that I have to add it to all files I already created.
>

That's true.  However, the way I'd approach it (probably via module
inclusion) is to batch-edit the .lyx files from the command line to update
the already existing ones retroactively.

Re: How to extend a standard layouts

[Richard Heck]

On 01/20/2018 11:30 AM, racoon wrote:
> By default LyX loads standard layouts and insets. Is there a way to
> extend them without overwriting the default .inc file and without
> using a module?
>
> Let's say I want to extend the standard Note style.
>
> I don't want to use a module since I want to make a non-optional
> change to the Note inset. For example, I want to use another font size
> for all LyX notes.
>
> If I understood correctly, I can just put a copy of the stdinset.inc
> file from the library to the user directory. But this will have the
> unwelcome effect to overwrite whatever is in the stdinset.inc in the
> library directory. So, to avoid unwanted consequences, I will have to
> update my user stdinset.inc every time the library stdinset.inc
> changes, for example, in a new version of LyX.

I have run into this problem, too. Some form of it will arise any time
you want to emend or amend a layout file.

I wonder if a longer-term solution is required, then. Might there be
some way we could have 'extensions' of this kind? Maybe they could be
named things like stdinsets.inc.ext and they would always be loaded
after the corresponding other file was.

Richard

Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Scott Kostyshak]

On Sun, Jan 21, 2018 at 12:32:41AM +, Rich Shepard wrote:
> On Sat, 20 Jan 2018, Scott Kostyshak wrote:
> 
> > If others do find this annoying, perhaps we can think of an improvement.
> > The ideal behavior for me would be that whenever I paste text that is in
> > language "mylanguage (x)" into a document that has language "mylanguage
> > (y)" and no other language, the text would be pasted as "mylanguage (y)".
> > However, thinking about what the LyX behavior should be, I don't know what
> > to suggest. On the one hand, I don't think we should change the default
> > behavior since it is correct to treat "mylanguage (x)" and "mylanguage
> > (y)" as different languages. On the other, I don't think this is a big
> > enough issue that we should have a preference for it. So I don't know what
> > to suggest.
> > 
> > Thoughts?
> 
> Scott,
> 
>   I stick with 'English (USA)' and don't have this issue. However, I offer
> the suggestion of a separate tool that can be invoked as desired by the
> user. It could be a script that pops up when lyx detects two flavors of a
> common language in a document, presents the two flavors, asks the user which
> is the flavor of the day (or ignore the differences as a third option), then
> modify the .lyx file and reload the working document.
> 
>   This does not force behavior on everyone and might be easier to implement
> and maintain.

Thanks for the idea, Rich. That could be interesting. Maybe a little
difficult to implement since we don't have a similar mechanism yet.

Scott


signature.asc
Description: PGP signature

Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Scott Kostyshak]

On Sat, Jan 20, 2018 at 10:55:28PM +, Richard Heck wrote:

> Maybe another form of "paste special" that would just ignore the
> language? That would probably take care of most of the use cases here.

Yeah that could work.

Scott


signature.asc
Description: PGP signature

Re: Skim as PDF-file-viewer on Mac

[Scott Kostyshak]

On Sat, Jan 20, 2018 at 07:19:08PM +, Sehr Extrem wrote:
> Hello Scott,
> 
> sorry for answering late.
> I still use LyX 2.2.3 and it works fine for me to use Skim 1.4.29 as 
> file-viewer, nonetheless one or two commands »Skim.app« in the command-line. 
> I think it works, because I just changed the general habit for my mac, so 
> that every PDF now is opened with Skim. Not a very consequent solution, 
> though, but it works for me…

Thanks for the response, Jess!

Scott


signature.asc
Description: PGP signature

Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Rich Shepard]

On Sat, 20 Jan 2018, Scott Kostyshak wrote:


If others do find this annoying, perhaps we can think of an improvement.
The ideal behavior for me would be that whenever I paste text that is in
language "mylanguage (x)" into a document that has language "mylanguage
(y)" and no other language, the text would be pasted as "mylanguage (y)".
However, thinking about what the LyX behavior should be, I don't know what
to suggest. On the one hand, I don't think we should change the default
behavior since it is correct to treat "mylanguage (x)" and "mylanguage
(y)" as different languages. On the other, I don't think this is a big
enough issue that we should have a preference for it. So I don't know what
to suggest.

Thoughts?


Scott,

  I stick with 'English (USA)' and don't have this issue. However, I offer
the suggestion of a separate tool that can be invoked as desired by the
user. It could be a script that pops up when lyx detects two flavors of a
common language in a document, presents the two flavors, asks the user which
is the flavor of the day (or ignore the differences as a third option), then
modify the .lyx file and reload the working document.

  This does not force behavior on everyone and might be easier to implement
and maintain.

Regards,

Rich