On 6/6/2016 9:21 AM, Procházka Lukáš Ing. wrote:
Hello Hans,
just to remind -
- would it be possible to use "--result=OutputFileName" as the name for
the output stream immediately?
not now (as it also relates to all kind of other name things like
preventing a file to load itself as graphic
Hello Hans,
just to remind -
- would it be possible to use "--result=OutputFileName" as the name for the
output stream immediately?
(See the history bellow.)
Best regards,
Lukas
On Sun, 10 Apr 2016 23:43:30 +0200, Hans Hagen wrote:
On 4/10/2016 9:49 PM, Lukáš Procházka
Hello,
On Sun, 10 Apr 2016 23:43:30 +0200, Hans Hagen wrote:
On 4/10/2016 9:49 PM, Lukáš Procházka wrote:
- the option "--jobname" is not listed when you type "context.exe" (=
help), so it seems like a "hidden" option;
it's not supported as engine flag
- Suggestion: would
On 4/10/2016 9:49 PM, Lukáš Procházka wrote:
- the option "--jobname" is not listed when you type "context.exe" (=
help), so it seems like a "hidden" option;
it's not supported as engine flag
- Suggestion: would it be possible to use "--result=OutputFileName" as
the name for the output
Hello,
On Sun, 10 Apr 2016 18:07:54 +0200, Aditya Mahajan wrote:
This should have worked, but for some reason it does not:
context --jobname=shadow main.tex
The output says:
system > files > jobname 'shadow', input './main', result 'shadow'
.
mkiv lua stats
On 4/10/2016 6:07 PM, Aditya Mahajan wrote:
On Sun, 10 Apr 2016, Lukáš Procházka wrote:
My way is to compile into a "shadow copy" which allow use to view the
document even during its compilation.
Once the compilation is done, I close the .pdf, I move the compiled
"shadow copy" to the
On Sun, 10 Apr 2016, Lukáš Procházka wrote:
My way is to compile into a "shadow copy" which allow use to view the
document even during its compilation.
Once the compilation is done, I close the .pdf, I move the compiled "shadow
copy" to the well-named .pdf and I open it in a viewer.
So I'm
On 4/9/2016 11:47 PM, Pablo Rodriguez wrote:
On 04/09/2016 10:11 PM, Lukáš Procházka wrote:
Hello,
is there a way to tell ConTeXt to generate a .pdf named othe
instead of the name derived from file to be compiled?
Hi Lukáš,
this wuld be the way to do it:
context source.tex
Hello,
thanks for the tip,
the issue here is that I'm not using AR but PdfXChange Viewer (and yes, there
is also at least SumetraPPDF and Foxit Reader).
I don't use --autopdf as it closes the .pdf as soon as the compilation is to
start.
My way is to compile into a "shadow copy" which allow
On 2016-04-09 Pablo Rodriguez wrote:
> On 04/09/2016 10:51 PM, Alan BRASLAU wrote:
> > On Sat, 9 Apr 2016 22:11:29 +0200 Lukáš Procházka wrote:
> >
> >> Let's have A.tex to be compiled and an existing A.pdf which
> >> cannot be written into, e.g. due to being open by a viewer.
> >
> > This is
On 04/09/2016 11:47 PM, Pablo Rodriguez wrote:
> On 04/09/2016 10:11 PM, Lukáš Procházka wrote:
>> Hello,
>>
>> is there a way to tell ConTeXt to generate a .pdf named othe
>> instead of the name derived from file to be compiled?
> [...]
> BTW, ---auto may achieve what you intend. I have never
On 04/09/2016 10:11 PM, Lukáš Procházka wrote:
> Hello,
>
> is there a way to tell ConTeXt to generate a .pdf named othe
> instead of the name derived from file to be compiled?
Hi Lukáš,
this wuld be the way to do it:
context source.tex --result=output
I’m not sure it may work with Adobe,
On 04/09/2016 10:51 PM, Alan BRASLAU wrote:
> On Sat, 9 Apr 2016 22:11:29 +0200 Lukáš Procházka wrote:
>
>> Let's have A.tex to be compiled and an existing A.pdf which cannot be
>> written into, e.g. due to being open by a viewer.
>
> This is only an issue for Windows users...
As far as I know,
On Sat, 9 Apr 2016 22:11:29 +0200
Lukáš Procházka wrote:
> Let's have A.tex to be compiled and an existing A.pdf which cannot be
> written into, e.g. due to being open by a viewer.
This is only an issue for Windows users...
Alan
14 matches
Mail list logo