Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!oliveb!amdahl!kim
From: kim@uts.amdahl.com (Kim DeVaughn)
Newsgroups: comp.sys.amiga.tech
Subject: Re: FastFonts (was Re: Windows/Fonts)
Message-ID: <00NxT30HU01010GlRRY@amdahl.uts.amdahl.com>
Date: 28 Jan 89 00:32:01 GMT
References: <6080.AA6080@heimat> <3281@amiga.UUCP>
Distribution: usa
Organization: Amdahl Corporation,  Sunnyvale, CA 94086
Lines: 44

In article <3281@amiga.UUCP>, jimm@amiga.UUCP (Jim Mackraz) writes:
> )>So, I went to the trouble to "fix" the font, and finally did get FF to
> )>load it when I typed in the command from the CLI.
> )
> ) Ok, so FF does work as I posted.
> )
> )>Put the command in the s-s, and .... didn't work (this was the STOCK s-s,
> )>except for the font name, and there were no assign/path/etc. dependencies).
> 
> I know, I know!
> 
> FF parses its command parameters real simply: if you have
> a comment on the same line, it will screw up parsing the font name.
> 
> Try putting the FF command on a line by itself, with no trailing blanks,
> in your Startup-sequence.  That might do it.

Hmmmmm ... that could well be it.  My recollection is a little fuzzy,
as I was doing this right after 1.3 was released, but I think I did
have a comment on the line.  Have to check on this, as I *suspect* that
BlitzFonts will bust under 1.4 ...


So lesee ... I now know of at least 3 "anomalous" situations under 1.3:

  1 - the FF anomaly described above

  2 - case sensitivity in some (all ?) of the Mountlist entries

  3 - newcon/newshell "from" startup files containing embedded tab chars
      will bust the alias command

Any other ones known that people should guard against?

Thanks jimm!

/kim

-- 
UUCP:  kim@amdahl.amdahl.com
  or:  {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim
DDD:   408-746-8462
USPS:  Amdahl Corp.  M/S 249,  1250 E. Arques Av,  Sunnyvale, CA 94086
BIX:   kdevaughn     GEnie:   K.DEVAUGHN     CIS:   76535,25