arara: load a local batch script or transform the batch script to an own rule
My question is similar to the one here, however it has a little different focus. I am working under Windows using MikTeX 2.9.
I do have several latex
projects which are part of a tool documentation. Each project may create multiple glossaries
files depending of the number of sub-glossaries used in each document.
document.acn
document.glo
document.syg1
document.syg2
...
Instead of calling makeindex
individually on each glossaries
file with
makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
makeindex -s %maintexname%.ist -t %maintexname%.slg2 -o %maintexname%.syi2 %maintexname%.syg2
...
I wrote a batch script create_glossaries.cmd
that applies makeindex
to all acn
, glo
and sygi
files in the main folder of the latex
project, for acronyms, glossaries and symbols respectively. Thus, I don't really have to know which glossaries
files are created explicitely and I can use the same batch script for all my documents.
Now I want to switch to build automation with arara
. I basically got it working to use pdflatex and biber to compile my document. But I am struggeling to include the creation of the glossaries. I could of course input the individual makeindex
commands for each glossaries
file with
% arara: makeindex: { style: %maintexname%.ist }
However, this lacks the generality of the approach and I would have to specify each glossaries
file for each project. If possible, I'd like to work around that.
So my first solution approach would be to call the batch script from within arara
. However, I did not really get how to call a batch script, here called create_glossaries.cmd
from a arara
rule. How is that possible?
To be platform independent and use the same approach on all operating system supported by arara
my second question is: How can I extend a rule that does the same as my script, so find each base glossaries
file and translate it to the proper output using makeindex
?
And a question related: How can I deliver a possible new arara
rule in my main tex
document folder instead of in the arara
rules path? Background is that the documents are part of a SVN repository, such that I do not know the absolute path where a collaborator checks the latex
file out to.
Batch script for makeindex
This is the file create_glossaries.cmd
::-----------------------------------------------------------------------------
::
:: Purpose: Create all glossaries for a tex document
::
:: Conventions:
::
:: - Acronyms: - Input file extension: acn*
:: - Output file extension: acr*
:: - Log file extension: alg*
::
:: - Glossary: - Input file extension: glo*
:: - Output file extension: gls*
:: - Log file extension: glg*
::
:: - Symbols : - Input file extension: syg*
:: - Output file extension: syi*
:: - Log file extension: slg*
::
:: Remarks: - This script has to be physically present in the tex directory.
:: A symbolic link does not work.
::
:: Author: Martin Raedel, DLR-FA-STM, WiMi, 10.02.2016
::-----------------------------------------------------------------------------
::
:: @echo off verhindert Ausgabe Befehlszeilen bis Stapelverarbeitung beendet
@echo off
::
::-----------------------------------------------------------------------------
:: set variables - no spaces between variable name and = allowed
::-----------------------------------------------------------------------------
::
:: manual mode:
::set maintexname=Mixed-Dimensional-Coupling
::
:: automatic mode:
set glo_num=2
::
set glo_input_list[0]=acn
set glo_input_list[1]=glo
set glo_input_list[2]=syg
::
set glo_output_list[0]=acr
set glo_output_list[1]=gls
set glo_output_list[2]=syi
::
set glo_log_list[0]=alg
set glo_log_list[1]=glg
set glo_log_list[2]=slg
::
::-----------------------------------------------------------------------------
:: create glossaries
::-----------------------------------------------------------------------------
::
:: Acronyms:
::
::makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
::
:: Glossar:
::
::makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
::
:: Symbols:
:: manual:
::makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
:: with automatic symbol input file search
setlocal EnableDelayedExpansion
::
FOR /L %%i IN (0, 1, %glo_num%) DO (
set inputextension=!glo_input_list[%%i]!
set outputextension=!glo_output_list[%%i]!
set logextension=!glo_log_list[%%i]!
::echo "inputextension: !inputextension!"
FOR %%f IN (*.!inputextension!*) DO (
::echo %%f
set fullfilename=%%f
set filename=%%~nf
set fileextensionwithdot=%%~xf
set fileextension=!fileextensionwithdot:~1!
::echo "fullfilename: !fullfilename! | fileextension: !fileextension! | !fileextension:~3,1!"
IF DEFINED fileextension IF "!fileextension:~3,1!"=="" (
::echo 3 or less characters
makeindex -s !filename!.ist -t !filename!.!logextension! -o !filename!.!outputextension! !filename!!fileextensionwithdot! >nul 2>&1
) ELSE (
::echo more than 3 characters
set index=!fileextension:~3,1!
::echo !index!
makeindex -s !filename!.ist -t !filename!.!logextension!!index! -o !filename!.!outputextension!!index! !filename!!fileextensionwithdot!>nul 2>&1
)
)
)
::
endlocal
Solution to idea 1?!
I managed to get the first approach, calling the batch script from an own arara
rule, working. I added this araraconfig.yaml
to the main directory of my project.
!config
paths:
- '.'
to find my own rule-file create_glossaries.yaml
!config
identifier: create_glossaries
name: create_glossaries
commands:
- name: Create glossaries
command: <arara> cmd /c create_glossaries.cmd
arguments:
- identifier: name
flag: <arara> @{parameters.name}
default: "create_glossaries"
Where the argument is not used, but the file does not work without it.
automation scripts arara
add a comment |
My question is similar to the one here, however it has a little different focus. I am working under Windows using MikTeX 2.9.
I do have several latex
projects which are part of a tool documentation. Each project may create multiple glossaries
files depending of the number of sub-glossaries used in each document.
document.acn
document.glo
document.syg1
document.syg2
...
Instead of calling makeindex
individually on each glossaries
file with
makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
makeindex -s %maintexname%.ist -t %maintexname%.slg2 -o %maintexname%.syi2 %maintexname%.syg2
...
I wrote a batch script create_glossaries.cmd
that applies makeindex
to all acn
, glo
and sygi
files in the main folder of the latex
project, for acronyms, glossaries and symbols respectively. Thus, I don't really have to know which glossaries
files are created explicitely and I can use the same batch script for all my documents.
Now I want to switch to build automation with arara
. I basically got it working to use pdflatex and biber to compile my document. But I am struggeling to include the creation of the glossaries. I could of course input the individual makeindex
commands for each glossaries
file with
% arara: makeindex: { style: %maintexname%.ist }
However, this lacks the generality of the approach and I would have to specify each glossaries
file for each project. If possible, I'd like to work around that.
So my first solution approach would be to call the batch script from within arara
. However, I did not really get how to call a batch script, here called create_glossaries.cmd
from a arara
rule. How is that possible?
To be platform independent and use the same approach on all operating system supported by arara
my second question is: How can I extend a rule that does the same as my script, so find each base glossaries
file and translate it to the proper output using makeindex
?
And a question related: How can I deliver a possible new arara
rule in my main tex
document folder instead of in the arara
rules path? Background is that the documents are part of a SVN repository, such that I do not know the absolute path where a collaborator checks the latex
file out to.
Batch script for makeindex
This is the file create_glossaries.cmd
::-----------------------------------------------------------------------------
::
:: Purpose: Create all glossaries for a tex document
::
:: Conventions:
::
:: - Acronyms: - Input file extension: acn*
:: - Output file extension: acr*
:: - Log file extension: alg*
::
:: - Glossary: - Input file extension: glo*
:: - Output file extension: gls*
:: - Log file extension: glg*
::
:: - Symbols : - Input file extension: syg*
:: - Output file extension: syi*
:: - Log file extension: slg*
::
:: Remarks: - This script has to be physically present in the tex directory.
:: A symbolic link does not work.
::
:: Author: Martin Raedel, DLR-FA-STM, WiMi, 10.02.2016
::-----------------------------------------------------------------------------
::
:: @echo off verhindert Ausgabe Befehlszeilen bis Stapelverarbeitung beendet
@echo off
::
::-----------------------------------------------------------------------------
:: set variables - no spaces between variable name and = allowed
::-----------------------------------------------------------------------------
::
:: manual mode:
::set maintexname=Mixed-Dimensional-Coupling
::
:: automatic mode:
set glo_num=2
::
set glo_input_list[0]=acn
set glo_input_list[1]=glo
set glo_input_list[2]=syg
::
set glo_output_list[0]=acr
set glo_output_list[1]=gls
set glo_output_list[2]=syi
::
set glo_log_list[0]=alg
set glo_log_list[1]=glg
set glo_log_list[2]=slg
::
::-----------------------------------------------------------------------------
:: create glossaries
::-----------------------------------------------------------------------------
::
:: Acronyms:
::
::makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
::
:: Glossar:
::
::makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
::
:: Symbols:
:: manual:
::makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
:: with automatic symbol input file search
setlocal EnableDelayedExpansion
::
FOR /L %%i IN (0, 1, %glo_num%) DO (
set inputextension=!glo_input_list[%%i]!
set outputextension=!glo_output_list[%%i]!
set logextension=!glo_log_list[%%i]!
::echo "inputextension: !inputextension!"
FOR %%f IN (*.!inputextension!*) DO (
::echo %%f
set fullfilename=%%f
set filename=%%~nf
set fileextensionwithdot=%%~xf
set fileextension=!fileextensionwithdot:~1!
::echo "fullfilename: !fullfilename! | fileextension: !fileextension! | !fileextension:~3,1!"
IF DEFINED fileextension IF "!fileextension:~3,1!"=="" (
::echo 3 or less characters
makeindex -s !filename!.ist -t !filename!.!logextension! -o !filename!.!outputextension! !filename!!fileextensionwithdot! >nul 2>&1
) ELSE (
::echo more than 3 characters
set index=!fileextension:~3,1!
::echo !index!
makeindex -s !filename!.ist -t !filename!.!logextension!!index! -o !filename!.!outputextension!!index! !filename!!fileextensionwithdot!>nul 2>&1
)
)
)
::
endlocal
Solution to idea 1?!
I managed to get the first approach, calling the batch script from an own arara
rule, working. I added this araraconfig.yaml
to the main directory of my project.
!config
paths:
- '.'
to find my own rule-file create_glossaries.yaml
!config
identifier: create_glossaries
name: create_glossaries
commands:
- name: Create glossaries
command: <arara> cmd /c create_glossaries.cmd
arguments:
- identifier: name
flag: <arara> @{parameters.name}
default: "create_glossaries"
Where the argument is not used, but the file does not work without it.
automation scripts arara
Hi! I am in a bit of a hurry, I will take a closer look at your question later on.:)
– Paulo Cereda
Mar 17 at 20:34
I am really looking forward to it. Thanks for the great tool. Should I open an issue on Github?
– krtek
Mar 17 at 20:50
add a comment |
My question is similar to the one here, however it has a little different focus. I am working under Windows using MikTeX 2.9.
I do have several latex
projects which are part of a tool documentation. Each project may create multiple glossaries
files depending of the number of sub-glossaries used in each document.
document.acn
document.glo
document.syg1
document.syg2
...
Instead of calling makeindex
individually on each glossaries
file with
makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
makeindex -s %maintexname%.ist -t %maintexname%.slg2 -o %maintexname%.syi2 %maintexname%.syg2
...
I wrote a batch script create_glossaries.cmd
that applies makeindex
to all acn
, glo
and sygi
files in the main folder of the latex
project, for acronyms, glossaries and symbols respectively. Thus, I don't really have to know which glossaries
files are created explicitely and I can use the same batch script for all my documents.
Now I want to switch to build automation with arara
. I basically got it working to use pdflatex and biber to compile my document. But I am struggeling to include the creation of the glossaries. I could of course input the individual makeindex
commands for each glossaries
file with
% arara: makeindex: { style: %maintexname%.ist }
However, this lacks the generality of the approach and I would have to specify each glossaries
file for each project. If possible, I'd like to work around that.
So my first solution approach would be to call the batch script from within arara
. However, I did not really get how to call a batch script, here called create_glossaries.cmd
from a arara
rule. How is that possible?
To be platform independent and use the same approach on all operating system supported by arara
my second question is: How can I extend a rule that does the same as my script, so find each base glossaries
file and translate it to the proper output using makeindex
?
And a question related: How can I deliver a possible new arara
rule in my main tex
document folder instead of in the arara
rules path? Background is that the documents are part of a SVN repository, such that I do not know the absolute path where a collaborator checks the latex
file out to.
Batch script for makeindex
This is the file create_glossaries.cmd
::-----------------------------------------------------------------------------
::
:: Purpose: Create all glossaries for a tex document
::
:: Conventions:
::
:: - Acronyms: - Input file extension: acn*
:: - Output file extension: acr*
:: - Log file extension: alg*
::
:: - Glossary: - Input file extension: glo*
:: - Output file extension: gls*
:: - Log file extension: glg*
::
:: - Symbols : - Input file extension: syg*
:: - Output file extension: syi*
:: - Log file extension: slg*
::
:: Remarks: - This script has to be physically present in the tex directory.
:: A symbolic link does not work.
::
:: Author: Martin Raedel, DLR-FA-STM, WiMi, 10.02.2016
::-----------------------------------------------------------------------------
::
:: @echo off verhindert Ausgabe Befehlszeilen bis Stapelverarbeitung beendet
@echo off
::
::-----------------------------------------------------------------------------
:: set variables - no spaces between variable name and = allowed
::-----------------------------------------------------------------------------
::
:: manual mode:
::set maintexname=Mixed-Dimensional-Coupling
::
:: automatic mode:
set glo_num=2
::
set glo_input_list[0]=acn
set glo_input_list[1]=glo
set glo_input_list[2]=syg
::
set glo_output_list[0]=acr
set glo_output_list[1]=gls
set glo_output_list[2]=syi
::
set glo_log_list[0]=alg
set glo_log_list[1]=glg
set glo_log_list[2]=slg
::
::-----------------------------------------------------------------------------
:: create glossaries
::-----------------------------------------------------------------------------
::
:: Acronyms:
::
::makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
::
:: Glossar:
::
::makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
::
:: Symbols:
:: manual:
::makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
:: with automatic symbol input file search
setlocal EnableDelayedExpansion
::
FOR /L %%i IN (0, 1, %glo_num%) DO (
set inputextension=!glo_input_list[%%i]!
set outputextension=!glo_output_list[%%i]!
set logextension=!glo_log_list[%%i]!
::echo "inputextension: !inputextension!"
FOR %%f IN (*.!inputextension!*) DO (
::echo %%f
set fullfilename=%%f
set filename=%%~nf
set fileextensionwithdot=%%~xf
set fileextension=!fileextensionwithdot:~1!
::echo "fullfilename: !fullfilename! | fileextension: !fileextension! | !fileextension:~3,1!"
IF DEFINED fileextension IF "!fileextension:~3,1!"=="" (
::echo 3 or less characters
makeindex -s !filename!.ist -t !filename!.!logextension! -o !filename!.!outputextension! !filename!!fileextensionwithdot! >nul 2>&1
) ELSE (
::echo more than 3 characters
set index=!fileextension:~3,1!
::echo !index!
makeindex -s !filename!.ist -t !filename!.!logextension!!index! -o !filename!.!outputextension!!index! !filename!!fileextensionwithdot!>nul 2>&1
)
)
)
::
endlocal
Solution to idea 1?!
I managed to get the first approach, calling the batch script from an own arara
rule, working. I added this araraconfig.yaml
to the main directory of my project.
!config
paths:
- '.'
to find my own rule-file create_glossaries.yaml
!config
identifier: create_glossaries
name: create_glossaries
commands:
- name: Create glossaries
command: <arara> cmd /c create_glossaries.cmd
arguments:
- identifier: name
flag: <arara> @{parameters.name}
default: "create_glossaries"
Where the argument is not used, but the file does not work without it.
automation scripts arara
My question is similar to the one here, however it has a little different focus. I am working under Windows using MikTeX 2.9.
I do have several latex
projects which are part of a tool documentation. Each project may create multiple glossaries
files depending of the number of sub-glossaries used in each document.
document.acn
document.glo
document.syg1
document.syg2
...
Instead of calling makeindex
individually on each glossaries
file with
makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
makeindex -s %maintexname%.ist -t %maintexname%.slg2 -o %maintexname%.syi2 %maintexname%.syg2
...
I wrote a batch script create_glossaries.cmd
that applies makeindex
to all acn
, glo
and sygi
files in the main folder of the latex
project, for acronyms, glossaries and symbols respectively. Thus, I don't really have to know which glossaries
files are created explicitely and I can use the same batch script for all my documents.
Now I want to switch to build automation with arara
. I basically got it working to use pdflatex and biber to compile my document. But I am struggeling to include the creation of the glossaries. I could of course input the individual makeindex
commands for each glossaries
file with
% arara: makeindex: { style: %maintexname%.ist }
However, this lacks the generality of the approach and I would have to specify each glossaries
file for each project. If possible, I'd like to work around that.
So my first solution approach would be to call the batch script from within arara
. However, I did not really get how to call a batch script, here called create_glossaries.cmd
from a arara
rule. How is that possible?
To be platform independent and use the same approach on all operating system supported by arara
my second question is: How can I extend a rule that does the same as my script, so find each base glossaries
file and translate it to the proper output using makeindex
?
And a question related: How can I deliver a possible new arara
rule in my main tex
document folder instead of in the arara
rules path? Background is that the documents are part of a SVN repository, such that I do not know the absolute path where a collaborator checks the latex
file out to.
Batch script for makeindex
This is the file create_glossaries.cmd
::-----------------------------------------------------------------------------
::
:: Purpose: Create all glossaries for a tex document
::
:: Conventions:
::
:: - Acronyms: - Input file extension: acn*
:: - Output file extension: acr*
:: - Log file extension: alg*
::
:: - Glossary: - Input file extension: glo*
:: - Output file extension: gls*
:: - Log file extension: glg*
::
:: - Symbols : - Input file extension: syg*
:: - Output file extension: syi*
:: - Log file extension: slg*
::
:: Remarks: - This script has to be physically present in the tex directory.
:: A symbolic link does not work.
::
:: Author: Martin Raedel, DLR-FA-STM, WiMi, 10.02.2016
::-----------------------------------------------------------------------------
::
:: @echo off verhindert Ausgabe Befehlszeilen bis Stapelverarbeitung beendet
@echo off
::
::-----------------------------------------------------------------------------
:: set variables - no spaces between variable name and = allowed
::-----------------------------------------------------------------------------
::
:: manual mode:
::set maintexname=Mixed-Dimensional-Coupling
::
:: automatic mode:
set glo_num=2
::
set glo_input_list[0]=acn
set glo_input_list[1]=glo
set glo_input_list[2]=syg
::
set glo_output_list[0]=acr
set glo_output_list[1]=gls
set glo_output_list[2]=syi
::
set glo_log_list[0]=alg
set glo_log_list[1]=glg
set glo_log_list[2]=slg
::
::-----------------------------------------------------------------------------
:: create glossaries
::-----------------------------------------------------------------------------
::
:: Acronyms:
::
::makeindex -s %maintexname%.ist -t %maintexname%.alg -o %maintexname%.acr %maintexname%.acn
::
:: Glossar:
::
::makeindex -s %maintexname%.ist -t %maintexname%.glg -o %maintexname%.gls %maintexname%.glo
::
:: Symbols:
:: manual:
::makeindex -s %maintexname%.ist -t %maintexname%.slg1 -o %maintexname%.syi1 %maintexname%.syg1
:: with automatic symbol input file search
setlocal EnableDelayedExpansion
::
FOR /L %%i IN (0, 1, %glo_num%) DO (
set inputextension=!glo_input_list[%%i]!
set outputextension=!glo_output_list[%%i]!
set logextension=!glo_log_list[%%i]!
::echo "inputextension: !inputextension!"
FOR %%f IN (*.!inputextension!*) DO (
::echo %%f
set fullfilename=%%f
set filename=%%~nf
set fileextensionwithdot=%%~xf
set fileextension=!fileextensionwithdot:~1!
::echo "fullfilename: !fullfilename! | fileextension: !fileextension! | !fileextension:~3,1!"
IF DEFINED fileextension IF "!fileextension:~3,1!"=="" (
::echo 3 or less characters
makeindex -s !filename!.ist -t !filename!.!logextension! -o !filename!.!outputextension! !filename!!fileextensionwithdot! >nul 2>&1
) ELSE (
::echo more than 3 characters
set index=!fileextension:~3,1!
::echo !index!
makeindex -s !filename!.ist -t !filename!.!logextension!!index! -o !filename!.!outputextension!!index! !filename!!fileextensionwithdot!>nul 2>&1
)
)
)
::
endlocal
Solution to idea 1?!
I managed to get the first approach, calling the batch script from an own arara
rule, working. I added this araraconfig.yaml
to the main directory of my project.
!config
paths:
- '.'
to find my own rule-file create_glossaries.yaml
!config
identifier: create_glossaries
name: create_glossaries
commands:
- name: Create glossaries
command: <arara> cmd /c create_glossaries.cmd
arguments:
- identifier: name
flag: <arara> @{parameters.name}
default: "create_glossaries"
Where the argument is not used, but the file does not work without it.
automation scripts arara
automation scripts arara
edited Mar 17 at 16:44
krtek
asked Mar 17 at 14:18
krtekkrtek
905820
905820
Hi! I am in a bit of a hurry, I will take a closer look at your question later on.:)
– Paulo Cereda
Mar 17 at 20:34
I am really looking forward to it. Thanks for the great tool. Should I open an issue on Github?
– krtek
Mar 17 at 20:50
add a comment |
Hi! I am in a bit of a hurry, I will take a closer look at your question later on.:)
– Paulo Cereda
Mar 17 at 20:34
I am really looking forward to it. Thanks for the great tool. Should I open an issue on Github?
– krtek
Mar 17 at 20:50
Hi! I am in a bit of a hurry, I will take a closer look at your question later on.
:)
– Paulo Cereda
Mar 17 at 20:34
Hi! I am in a bit of a hurry, I will take a closer look at your question later on.
:)
– Paulo Cereda
Mar 17 at 20:34
I am really looking forward to it. Thanks for the great tool. Should I open an issue on Github?
– krtek
Mar 17 at 20:50
I am really looking forward to it. Thanks for the great tool. Should I open an issue on Github?
– krtek
Mar 17 at 20:50
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479931%2farara-load-a-local-batch-script-or-transform-the-batch-script-to-an-own-rule%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479931%2farara-load-a-local-batch-script-or-transform-the-batch-script-to-an-own-rule%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hi! I am in a bit of a hurry, I will take a closer look at your question later on.
:)
– Paulo Cereda
Mar 17 at 20:34
I am really looking forward to it. Thanks for the great tool. Should I open an issue on Github?
– krtek
Mar 17 at 20:50