ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: output file name query
Date: Sat, 23 May 2020 23:52:53 +0200	[thread overview]
Message-ID: <CDEF511E-0371-464F-A01E-BBBC09D3EA61@fiee.net> (raw)
In-Reply-To: <3d068487-61c5-3d3c-d57f-e21dc060c42f@gmail.com>


> Am 23.05.2020 um 14:43 schrieb Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
> 
>>> 1. Drop the weird (sorry Hraban) naming system and use myfilename for your product.
>> I force nobody to use that.
> No and everybody has to find a system which fits best for him, prefixes can be useful (e.g. to avoid component and style files with the same name) but aren't necessary.

Usually my project and environment have the same name, but different prefix (in my weird nomenclature).

>>> 2. Use the result option on the command line, e.g. "context --result=myfilename prd_filename.tex".
>> But that still produces a "prd_filename.*" first and then renames it, making it impossible to keep a "prd_filename.pdf". Or did that change recently?
>> 
>> My workflows are adapted to that behaviour: "prd_*.pdf" is just the temporary version, none of those leaves my computer, but only nicely named PDFs (usually MyProductName_yyyy-mm-dd.pdf).
> Having a simple name doesn't mean it's the final name of the document.

Of course. But in most of my projects I have several products (e.g. magazine issues, books of a series), and with a prefix I can keep all the products together and list them like `ls prd_*.tex`.
Not only my contextproject.py but also my call scripts relay on my naming scheme. And since I use it in my main projects, I use it everywhere (if I use the project structure at all).

>> That contradicts the mode approach. It would be nice if we could set (or can we?) the result from within the product, depending on a mode – since the product is renamed only later anyway, that could be viable.
> This addition is easy because already reads the first line of the document for special setting (e.g. the engine) but anything which is set in the document requires more work because you don't know the new name *before* LuaTeX or LuaMetaTeX create the PDF.

You don’t need to know the name before ConTeXt creates the PDF, because it uses the original filename and only renames the files (pdf, tuc, log) afterwards. Or misunderstood I something?

Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2020-05-23 21:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 12:33 Alan Bowen
2020-05-22 13:09 ` Wolfgang Schuster
2020-05-22 15:39   ` Henning Hraban Ramm
2020-05-22 20:08     ` Rik Kabel
2020-05-23 12:43     ` Wolfgang Schuster
2020-05-23 13:46       ` Gerben Wierda
2020-05-23 19:46         ` Wolfgang Schuster
2020-05-23 21:52       ` Henning Hraban Ramm [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CDEF511E-0371-464F-A01E-BBBC09D3EA61@fiee.net \
    --to=texml@fiee.net \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).