On 02/07/2018 12:01 PM, racoon wrote:
> On 24.01.2018 21:22, Richard Heck wrote:
>> On 01/23/2018 03:49 AM, Jean-Marc Lasgouttes wrote:
>>>
>>> Now that I think about it, the advantage of using a special syntax is
>>> that there is not need to specify the file name, which makes the code
>>> safer.
On 24.01.2018 21:22, Richard Heck wrote:
On 01/23/2018 03:49 AM, Jean-Marc Lasgouttes wrote:
Now that I think about it, the advantage of using a special syntax is
that there is not need to specify the file name, which makes the code
safer.
Idead of syntax:
Input
Input *
InputParent
On 01/23/2018 03:49 AM, Jean-Marc Lasgouttes wrote:
>
> Now that I think about it, the advantage of using a special syntax is
> that there is not need to specify the file name, which makes the code
> safer.
>
> Idead of syntax:
> Input
> Input *
> InputParent
I had a similar thought: someth
On 23.01.2018 11:50, Jean-Marc Lasgouttes wrote:
When is it useful to extend an extension in the same user directory? I
do not see the point...
For example, you might have a module locally installed in the user dir
which you want to extend. This is not strictly speaking an extension of
an ext
Le 23/01/2018 à 10:02, racoon a écrit :
On 23.01.2018 10:41, Jean-Marc Lasgouttes wrote:
Le 23/01/2018 à 09:35, racoon a écrit :
Yes, that would work for my case. However, it will fail if I want to
extend an extension since it will not search my user directory.
Let's say in the user directory
On 23.01.2018 11:02, racoon wrote:
On 23.01.2018 10:41, Jean-Marc Lasgouttes wrote:
Le 23/01/2018 à 09:35, racoon a écrit :
Yes, that would work for my case. However, it will fail if I want to
extend an extension since it will not search my user directory.
Let's say in the user directory ther
On 23.01.2018 10:41, Jean-Marc Lasgouttes wrote:
Le 23/01/2018 à 09:35, racoon a écrit :
Yes, that would work for my case. However, it will fail if I want to
extend an extension since it will not search my user directory.
Let's say in the user directory there is
1. user_dir/foo.layout.ext
wh
Le 23/01/2018 à 06:11, Richard Heck a écrit :
My sense, from our previous discussion, is that this would work in the
cases racoon had in mind. But I'm not sure why this wouldn't scale. We
could of course look also for *.ext.ext.
OK, imagine that we have support for a site directory (and I think
Le 23/01/2018 à 09:35, racoon a écrit :
Yes, that would work for my case. However, it will fail if I want to
extend an extension since it will not search my user directory.
Let's say in the user directory there is
1. user_dir/foo.layout.ext
which extends an extension
Actually, what I propos
On 23.01.2018 07:11, Richard Heck wrote:
On 01/22/2018 04:23 AM, Jean-Marc Lasgouttes wrote:
Le 22/01/2018 à 10:10, racoon a écrit :
So LyX should load the library's stdinset.inc first and then load the
code that extends it next.
Richard, who ran into similar problems as I did, suggested that
On 22.01.2018 11:23, Jean-Marc Lasgouttes wrote:
Le 22/01/2018 à 10:10, racoon a écrit :
So LyX should load the library's stdinset.inc first and then load the
code that extends it next.
Richard, who ran into similar problems as I did, suggested that LyX
could be enhanced by automatically look
On 01/22/2018 04:23 AM, Jean-Marc Lasgouttes wrote:
> Le 22/01/2018 à 10:10, racoon a écrit :
>> So LyX should load the library's stdinset.inc first and then load the
>> code that extends it next.
>>
>> Richard, who ran into similar problems as I did, suggested that LyX
>> could be enhanced by auto
Le 22/01/2018 à 10:10, racoon a écrit :
So LyX should load the library's stdinset.inc first and then load the
code that extends it next.
Richard, who ran into similar problems as I did, suggested that LyX
could be enhanced by automatically looking for and loading an .ext file,
e.g. stdinset.i
13 matches
Mail list logo
