Parv wrote:
It works for me now, too. When I was testing every (sic)
combination last night, I wasn't always using xterm. Sometimes I
used xfterm4 (the XFCE wrapper for xterm) and it DOES barf whether
I escape, quote or whatever.
If you don't mind ... Does the xterm start w/ the given font stri
in message <[EMAIL PROTECTED]>,
wrote Michael A. Smith thusly...
>
> It works for me now, too. When I was testing every (sic)
> combination last night, I wasn't always using xterm. Sometimes I
> used xfterm4 (the XFCE wrapper for xterm) and it DOES barf whether
> I escape, quote or whatever.
If yo
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.
Please ignore my previous reply to epilogue's reply.
After providing the
On Thu, 24 Jun 2004 15:17:58 -0400
Parv <[EMAIL PROTECTED]> wrote:
> in message <[EMAIL PROTECTED]>,
> wrote [EMAIL PROTECTED] thusly...
> >
> > On Thu, 24 Jun 2004 14:07:09 -0400
> > Parv <[EMAIL PROTECTED]> wrote:
> >
> > > i tried w/ xterms included in 4.3.0 and locally compiled version
> > >
in message <[EMAIL PROTECTED]>,
wrote [EMAIL PROTECTED] thusly...
>
> On Thu, 24 Jun 2004 14:07:09 -0400
> Parv <[EMAIL PROTECTED]> 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 \
> >
in message <[EMAIL PROTECTED]>,
wrote [EMAIL PROTECTED] thusly...
>
> On Thu, 24 Jun 2004 14:07:09 -0400
> Parv <[EMAIL PROTECTED]> 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 \
> >
On Thu, 24 Jun 2004 14:07:09 -0400
Parv <[EMAIL PROTECTED]> wrote:
> in message <[EMAIL PROTECTED]>,
> 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-chart
in message <[EMAIL PROTECTED]>,
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 sa
Robert Huff [Thu, Jun 24, 2004 at 09:05:49AM -0400]:
>
> Michael A. Smith writes:
>
> > 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-
Michael A. Smith writes:
> 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-*-*-*-*-*-*-*-*-*"
As far as I know, a correct fo
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 spac
On Wed, 23 Jun 2004, Michael A. Smith wrote:
I'm trying to set the xterm font from the command line using the -fn option.
$ xterm -fn fontname
What I can't seem to find is the exact fontname of any font on my system
(FreeBSD 5.2.1R). I've tried many combinations of my fonts: lowercase mixed
case,
I'm trying to set the xterm font from the command line using the -fn option.
$ xterm -fn fontname
What I can't seem to find is the exact fontname of any font on my system
(FreeBSD 5.2.1R). I've tried many combinations of my fonts: lowercase
mixed case, spaces, hyphes, underscores, etc... and it c
13 matches
Mail list logo
