Hi steffen,
> For other use cases i would have no problem with a single global
> .ini-style configuration file and a per-user one with the same syntax.
Aside, I dislike Microsoft's INI files that have appeared in Unix. :-)
They're not line based, but have context, making them more awkward to
sea
Hello and good morning Ralph,
Ralph Corderoy wrote:
|> For other use cases i would have no problem with a single global
|> .ini-style configuration file and a per-user one with the same syntax.
|
|Aside, I dislike Microsoft's INI files that have appeared in Unix. :-)
|They're not line based
P.S.:
i wrote:
|Werner LEMBERG wrote:
||Do you actually know the kpathsea library? Without this library, TeX
||file management would be a nightmare. And kpathsea works on all major
||platforms and is very mature.
My "all too hardwired and restricted, and then scattered at the
same time" di
Gurus,
My document, file 'oops' attached, uses
.S 12 24
to get double line spacing.
The command
groff -mm oops
bombs when going to the second page.
oops:48: fatal error: input stack limit exceeded (probable infinite loop)
Changing the above to
.S 12 18
avoids the