Maybe the package manager decided to add a shell script to the package
called "tlf". This shell script will then call the binary and create the
appropriate directories before starting the tlf binary. This would explain
the odd behaviour you are seeing.
73 de Joop PG4I
Op do 20 feb. 2020 om 03:52
Hi. Thanks for responding. The AUR has version 1.4.0. Neither solution
worked. No matter what it reads the default logcfg. file. Interestingly,
installing directly from source solved the problem. I use the first
method to have a separate logcfg.dat. Perfect, thanks! Perhaps the
package maintainer w
Hi Austin,
I had a look at the Arch repository. From there I think you have
a tlf-1.3.0 version.
You have two ways to solve your problem:
1. Drop the space between '-f' and the filename, e.g.
$ tlf -fqrpfoxhunt.dat
2. Use a separate directory, name the config file there just
'logcfg.dat' and c
I installed TLF from the Arch User Repository. The first time I ran it,
it created ~/tlf, and copied a working file structure into it, including
rules, a logcfg.dat, and other files. I successfully edited the
logcfg.dat and began using it, but I can't seem to figure out how to use
another log file.
