Date: Thu, 24 Jun 2004 15:24:35 +0200 From: Michal Pasternak <michal@pasternak.w.lub.pl> To: Robert Huff <roberthuff@rcn.com> Cc: questions@freebsd.org Subject: Re: setting xterm font from the command line Message-ID: <20040624132435.GB42463@pasternak.w.lub.pl> In-Reply-To: <16602.53677.446980.723841@jerusalem.litteratus.org> References: <40DA34AA.20906@code-fu.com> <20040623221647.V88483@wonkity.com> <40DABF4C.3070901@code-fu.com> <16602.53677.446980.723841@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Huff [Thu, Jun 24, 2004 at 09:05:49AM -0400]: >=20 > Michael A. Smith writes: >=20 > > xfontsel works great and works fine for the sample string above=20 > > (Bitstream Charter), but xterm barfs on font strings that have spaces,= =20 > > for example: > > =20 > > "-bitstream-bitstream vera sans mono-*-r-normal-*-*-*-*-*-*-*-*-*" >=20 > As far as I know, a correct fontspec has no spaces. Try > replacing the ' 's with '-'s and see what happens. No, it can. Dash is a separator of given fields in font specification, so what you just said is totally wrong. --=20 m
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040624132435.GB42463>