On Mon, May 12, 2014 at 4:45 AM, Jean-Marc Lasgouttes
wrote:
> 29/04/2014 19:29, Scott Kostyshak:
>
>> We do not parse looking for R commands in Systemcall::startscript as
>> we were doing for Python. The second patch should not change any
>> functionality, just organization (I will state this exp
29/04/2014 19:29, Scott Kostyshak:
We do not parse looking for R commands in Systemcall::startscript as
we were doing for Python. The second patch should not change any
functionality, just organization (I will state this explicitly in the
commit message). Just in case, I tested exporting the knit
On Mon, Apr 28, 2014 at 5:44 AM, Jean-Marc Lasgouttes
wrote:
> 28/04/2014 01:57, Scott Kostyshak:
>
> I am not sure that I understand the second patch: what are the changes in
> commandPrep wrt libScritpSearch exactly? How come that you did not need to
> change the documentation of the function?
28/04/2014 01:57, Scott Kostyshak:
Any other comments? If not I will commit the two patches to master
that are attached (they are the same as before except that I revert
the temporary fix at 731b8610 in one of them now).
I am not sure that I understand the second patch: what are the changes
in
On Fri, Feb 21, 2014 at 12:57 PM, Scott Kostyshak wrote:
> On Mon, Feb 3, 2014 at 6:42 AM, Jean-Marc Lasgouttes
> wrote:
>> 31/01/2014 07:02, Scott Kostyshak:
>
>> In any case, this is probably not usable to 2.1 (maybe backported later). I
>> understand this was the precise reason why you wanted
On Mon, Feb 3, 2014 at 6:42 AM, Jean-Marc Lasgouttes wrote:
> 31/01/2014 07:02, Scott Kostyshak:
> In any case, this is probably not usable to 2.1 (maybe backported later). I
> understand this was the precise reason why you wanted to do that. In this
> case, a solution maybe to, in parallel, rese
On Mon, Feb 3, 2014 at 6:42 AM, Jean-Marc Lasgouttes wrote:
> 31/01/2014 07:02, Scott Kostyshak:
>>
>> On Wed, Jan 29, 2014 at 3:37 AM, Scott Kostyshak wrote:
>>>
>>> Ah, right. OK then, I will make a patch for using libScriptSearch in
>>> SystemCall::startscript().
>>
>>
>> Attached is a patch.
31/01/2014 07:02, Scott Kostyshak:
On Wed, Jan 29, 2014 at 3:37 AM, Scott Kostyshak wrote:
Ah, right. OK then, I will make a patch for using libScriptSearch in
SystemCall::startscript().
Attached is a patch. Note that I also made the change in
ForkedCall::startScript. I'm not confident in thi
On Wed, Jan 29, 2014 at 3:37 AM, Scott Kostyshak wrote:
> On Wed, Jan 29, 2014 at 3:07 AM, Jean-Marc Lasgouttes
> wrote:
>> Le 29/01/14 06:01, Scott Kostyshak a écrit :
>>
>>> Makes sense. I was a little worried about performance from
>>> libScriptSearch but I guess it is not an issue compared to
On Wed, Jan 29, 2014 at 3:07 AM, Jean-Marc Lasgouttes
wrote:
> Le 29/01/14 06:01, Scott Kostyshak a écrit :
>
>> Makes sense. I was a little worried about performance from
>> libScriptSearch but I guess it is not an issue compared to the
>> overhead of running an external command anyway.
>>
>> Wha
Le 29/01/14 06:01, Scott Kostyshak a écrit :
Makes sense. I was a little worried about performance from
libScriptSearch but I guess it is not an issue compared to the
overhead of running an external command anyway.
What about the substitutions of the other converter variables? Should
they also a
On Tue, Jan 28, 2014 at 5:56 PM, Jean-Marc Lasgouttes
wrote:
> Le 25/01/14 19:18, Scott Kostyshak a écrit :
>
>> If latex=pdflatex is specified, the $$s is not substituted. The only
>> substitution is for $$i. This is not documented. I have a script that
>> I want to use to run pdflatex (and do ot
On Tue, Jan 28, 2014 at 6:01 PM, Jean-Marc Lasgouttes
wrote:
> Le 27/01/14 19:07, Scott Kostyshak a écrit :
>
>> Is there any reason not to make any of the other substitutions also? I
>> would like to either fix this for 2.1 or fix the Customization manual.
>
>
> I think there is no reason for not
Le 27/01/14 19:07, Scott Kostyshak a écrit :
Is there any reason not to make any of the other substitutions also? I
would like to either fix this for 2.1 or fix the Customization manual.
I think there is no reason for not doing it, but in this case it should
be done with a centralized method i
Le 25/01/14 19:18, Scott Kostyshak a écrit :
If latex=pdflatex is specified, the $$s is not substituted. The only
substitution is for $$i. This is not documented. I have a script that
I want to use to run pdflatex (and do other things like copy the log
file to a different directory). Because my s
On Sat, Jan 25, 2014 at 1:18 PM, Scott Kostyshak wrote:
> On Thu, Jan 23, 2014 at 12:14 PM, Scott Kostyshak wrote:
>> On Thu, Jan 23, 2014 at 11:32 AM, Jean-Marc Lasgouttes
>> wrote:
>>> Le 23/01/2014 17:22, Scott Kostyshak a écrit :
>>>
$$s is for the system directory. So to reach those sc
On Thu, Jan 23, 2014 at 12:14 PM, Scott Kostyshak wrote:
> On Thu, Jan 23, 2014 at 11:32 AM, Jean-Marc Lasgouttes
> wrote:
>> Le 23/01/2014 17:22, Scott Kostyshak a écrit :
>>
>>> $$s is for the system directory. So to reach those scripts one could
>>> do $$s/scripts/. I don't believe there is a
On Thu, Jan 23, 2014 at 11:32 AM, Jean-Marc Lasgouttes
wrote:
> Le 23/01/2014 17:22, Scott Kostyshak a écrit :
>
>> $$s is for the system directory. So to reach those scripts one could
>> do $$s/scripts/. I don't believe there is a variable for the user
>> scripts directory and it is this director
Le 23/01/2014 17:22, Scott Kostyshak a écrit :
$$s is for the system directory. So to reach those scripts one could
do $$s/scripts/. I don't believe there is a variable for the user
scripts directory and it is this directory that I understand the
Customization manual to suggest.
Actually, the f
On Thu, Jan 23, 2014 at 5:06 AM, Jean-Marc Lasgouttes
wrote:
> Le 23/01/2014 06:27, Scott Kostyshak a écrit :
>
>> I've always used the full paths to scripts in converters, but I
>> interpret the Customization manual to suggest that I only need to use
>> the base name:
>>
>> "Save it in your local
Le 23/01/2014 06:27, Scott Kostyshak a écrit :
I've always used the full paths to scripts in converters, but I
interpret the Customization manual to suggest that I only need to use
the base name:
"Save it in your local LyX directory—say,
/home/you/.lyx/scripts/pdfcopier.sh—and make it executable
I've always used the full paths to scripts in converters, but I
interpret the Customization manual to suggest that I only need to use
the base name:
"Save it in your local LyX directory—say,
/home/you/.lyx/scripts/pdfcopier.sh—and make it executable... enter
pdfcopier.sh $$i $$o into the Copier fi
22 matches
Mail list logo
