On 7/8/2021 3:38 PM, Marco Patzer wrote:
On Thu, 8 Jul 2021 10:34:32 +0200
Hans Hagen wrote:
Now, to the issue of names like 10.11.12.13 ... here .13 is the
suffix, like it or not, so in principle we then get
10.11.12.log
10.11.12.tuc
10.11.12.pdf
It's not that I use files without (.tex, .m
On 7/8/2021 8:13 PM, Alan Braslau wrote:
(and for Hans, the VMS ";" version specification is a different
feature).
Sure, one being that one ran out of disk space (but there were enough
unused accounts with simple passwords to take care of backups) but it
would add an interesting challenge (pro
On Wed, 7 Jul 2021 21:57:27 +0200
Ulrike Fischer wrote:
> Am Wed, 7 Jul 2021 12:25:29 -0600 schrieb Alan Braslau:
>
> > Windows, I believe, does not take kindly to filenames containing
> > multiple dots.
> >
> > Therefore, Hans never uses such filenames and does not expect them,
> > either, so
On Thu, 8 Jul 2021 10:34:32 +0200
Hans Hagen wrote:
> Now, to the issue of names like 10.11.12.13 ... here .13 is the
> suffix, like it or not, so in principle we then get
>
> 10.11.12.log
> 10.11.12.tuc
> 10.11.12.pdf
It's not that I use files without (.tex, .mkiv, ...) suffixes, but
your 10.1
On 7/7/2021 8:25 PM, Alan Braslau wrote:
Windows, I believe, does not take kindly to filenames containing
multiple dots.
windowes is very kind to multiple dots but it (normally) sees the last
suffix as an indication of what file is it (other operating system needs
some 'open' command while wi
On 7/7/2021 10:13 PM, Marco Patzer wrote:
But maybe Hans can chime in and clarify.
I have to check it but syffixes and tex are kind of special. It has
nothing to do with operating systems (sorry for those who love to bash
windows for it). Personally I always use a suffix and don't look into
f
On Wed, 7 Jul 2021 12:25:29 -0600
Alan Braslau wrote:
Thank you for your reply.
> Windows, I believe, does not take kindly to filenames containing
> multiple dots.
Disclaimer: I don't use Windows, I know nothing about Windows. But I
downloaded a Windows 10 VM and fired it up, installed LMTX, cr
Am Wed, 7 Jul 2021 12:25:29 -0600 schrieb Alan Braslau:
> Windows, I believe, does not take kindly to filenames containing
> multiple dots.
>
> Therefore, Hans never uses such filenames and does not expect them,
> either, so I am not surprised that this yields unpredictable results.
>
> An unfor
Windows, I believe, does not take kindly to filenames containing
multiple dots.
Therefore, Hans never uses such filenames and does not expect them,
either, so I am not surprised that this yields unpredictable results.
An unfortunate side-effect of dealing with Windows.
Alan
On Tue, 6 Jul 2021
This is something that has caused me problems in the past, too.
On Tue, Jul 6, 2021 at 4:51 PM Marco Patzer wrote:
> On Thu, 28 May 2020 18:18:51 +0200
> Hans Hagen wrote:
>
> > > LMTX:
> > > 10.10.10.tex → 10.10 (not even a PDF suffix)
> > > 10.10.11.tex → 10.10 (file 10.10 is over
On Thu, 28 May 2020 18:18:51 +0200
Hans Hagen wrote:
> > LMTX:
> > 10.10.10.tex → 10.10 (not even a PDF suffix)
> > 10.10.11.tex → 10.10 (file 10.10 is over-written)
> > 11.10.11.tex → 11.10 (no suffix)
I've checked again with 2021.07.06 18:49 LMTX
10.10.10.tex → 10.10.pdf + 1
On 5/28/2020 8:31 PM, Marco Patzer wrote:
On Thu, 28 May 2020 18:18:51 +0200
Hans Hagen wrote:
MkIV (everything's predictable and fine):
10.10.10.tex → 10.10.10.pdf
10.10.11.tex → 10.10.11.pdf
11.10.11.tex → 11.10.11.pdf
LMTX:
10.10.10.tex → 10.10 (not even a PDF
On Thu, 28 May 2020 18:18:51 +0200
Hans Hagen wrote:
> > MkIV (everything's predictable and fine):
> > 10.10.10.tex → 10.10.10.pdf
> > 10.10.11.tex → 10.10.11.pdf
> > 11.10.11.tex → 11.10.11.pdf
> >
> > LMTX:
> > 10.10.10.tex → 10.10 (not even a PDF suffix)
> > 10.10.
On 5/28/2020 5:59 PM, Marco Patzer wrote:
On Thu, 28 May 2020 17:33:19 +0200
Hans Hagen wrote:
On 5/28/2020 2:49 PM, Marco Patzer wrote:
Hi!
LMTX and MkIV behave differently if dots are used in the file
name. Example:
printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context
foo.
On Thu, 28 May 2020 17:33:19 +0200
Hans Hagen wrote:
> On 5/28/2020 2:49 PM, Marco Patzer wrote:
> > Hi!
> >
> > LMTX and MkIV behave differently if dots are used in the file
> > name. Example:
> >
> >printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context
> > foo.10.tex
> >
> > M
On Thu, 28 May 2020 17:33:19 +0200
Hans Hagen wrote:
> On 5/28/2020 2:49 PM, Marco Patzer wrote:
> > Hi!
> >
> > LMTX and MkIV behave differently if dots are used in the file
> > name. Example:
> >
> >printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context
> > foo.10.tex
> >
> > M
On 5/28/2020 2:49 PM, Marco Patzer wrote:
Hi!
LMTX and MkIV behave differently if dots are used in the file
name. Example:
printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context foo.10.tex
MkIV: → foo.10.pdf
LMTX: → foo.pdf
Is this intentional?
consider it to be so
Hans
-
Hi!
LMTX and MkIV behave differently if dots are used in the file
name. Example:
printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context foo.10.tex
MkIV: → foo.10.pdf
LMTX: → foo.pdf
Is this intentional?
This is LuaMetaTeX, Version 2.06.05
current version: 2020.05.25 23:39
Marco
__
18 matches
Mail list logo
