setting xterm font from the command line

epilogue at allstream.net epilogue at allstream.net
Thu Jun 24 11:50:37 PDT 2004


On Thu, 24 Jun 2004 14:07:09 -0400
Parv <parv at pair.com> wrote:

> in message <40DABF4C.3070901 at code-fu.com>,
> wrote Michael A. Smith thusly...
> >
> > Warren Block wrote:
> > >Use xfontsel to choose the font and then specify the exact same thing 
> > >that it shows:
> > >
> > >xterm -fn '-bitstream-charter-*-r-normal-*-*-*-*-*-*-*-*-*'
> > 
> > xfontsel works great and works fine for the sample string above 
> > (Bitstream Charter), but xterm barfs on font strings that have spaces, 
> > for example:
> > 
> > "-bitstream-bitstream vera sans mono-*-r-normal-*-*-*-*-*-*-*-*-*"
> > 
> > I've tried every combination of single quotes, double quotes and 
> > backslashes before the spaces without success. I get back an error like
> > this:
> > 
> > xterm:  bad command line option "vera"
> 
> Just a data point ... 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.

after doing this, are you getting any error messages?


cheers,
epi


> 
> Is "bitstream vera sans mono" font listed in xfontsel(1)'s list or
> xlsfonts(1)'s output?
> 
> 
>   - Parv
> 
> -- 
> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
> 


More information about the freebsd-questions mailing list