Date: Thu, 24 Jun 2004 15:09:45 -0400 From: Parv <parv@pair.com> To: epilogue@allstream.net Cc: "Michael A. Smith" <msmith@code-fu.com> Subject: Re: setting xterm font from the command line Message-ID: <20040624190945.GA2180@moo.holy.cow> In-Reply-To: <20040624145011.71cbd047@localhost> References: <40DA34AA.20906@code-fu.com> <20040623221647.V88483@wonkity.com> <40DABF4C.3070901@code-fu.com> <20040624180709.GA622@moo.holy.cow> <20040624145011.71cbd047@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <20040624145011.71cbd047@localhost>, wrote epilogue@allstream.net thusly... > > On Thu, 24 Jun 2004 14:07:09 -0400 > Parv <parv@pair.com> wrote: > > > i tried w/ xterms included in 4.3.0 and locally compiled version > > (patch 187) w/o any problems; the exact command was... > > > > xterm -fn \ > > '-bitstream-bitstream vera sans mono-*-r-normal-*-16-*-*-*-*-*-*-*' > > > > i just tried it myself. in order for it to work, you *must* escape the > fontname whitespace. > > xterm -fn -bitstream-bitstream\ vera\ sans\mono-*-yada,yada. > > also, if you're using the ' ' on either end of the fontname (as > you've shown above), drop them. Ah but the single quotes are there to avoid expansion of '*' via shell besides aboding the need to quote the spaces as shown above. And epilogue(?), yes, your proposed syntax does cause xterm not to find the desired Bitstream font; default font, fixed, is used instead (when the command is being executed in bash 2.05b). - Parv --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040624190945.GA2180>