On 2/9/2019 12:15 AM, Alan Braslau wrote:
On Fri, 8 Feb 2019 23:26:21 +0100
Hans Hagen wrote:
On 2/8/2019 10:22 PM, Marco Patzer wrote:
What is a bad name for context? Does it have any consequences if badly named
files are used? Just being curious.
Bad names are names that can result i a
On Fri, 8 Feb 2019 23:26:21 +0100
Hans Hagen wrote:
> On 2/8/2019 10:22 PM, Marco Patzer wrote:
>
> > What is a bad name for context? Does it have any consequences if
> > badly named files are used? Just being curious.
> Bad names are names that can result i a miss when looked up on a case
>
On Fri, 8 Feb 2019 23:26:21 +0100
Hans Hagen wrote:
> On 2/8/2019 10:22 PM, Marco Patzer wrote:
>
> > What is a bad name for context? Does it have any consequences if badly named
> > files are used? Just being curious.
> Bad names are names that can result i a miss when looked up on a case
>
On 2/8/2019 10:22 PM, Marco Patzer wrote:
What is a bad name for context? Does it have any consequences if badly named
files are used? Just being curious.
Bad names are names that can result i a miss when looked up on a case
sensitive system. When you have a workflow where images come from
Hi!
I was wondering what context considers a “bad” file name and what consequences
that might have. From workflows-mkiv.pdf:
“Bad names are reported and suitable action can be taken”
Indeed, every run context tells me how many files are badly named:
mkiv lua stats > graphics processing
