On Wed, 17 Nov 2010, MItchell Church wrote:
On Wed, Nov 17, 2010 at 5:36 PM, Aurélien Aptel wrote:
On Wed, Nov 17, 2010 at 10:10 PM, MItchell Church wrote:
Is anyone else having trouble getting st to accept font changes?
I've tried numerous strings using xfontsel, many of which work fine
in
Sorry for being vague. I was under the impression I could use xfontsel to
create an X font name that could then be plugged into config.def.h. I tried
several fonts including inconsolata, terminus, and dejavu but none of the
strings produced by xfontsel are working. St recompiles successfully, bu
I've committed&pushed your patch.
If someone has a problem with a curse app make sure TERM is set to xterm.
Also, drawing is a bit slower now that it support utf8.
On Wed, Nov 17, 2010 at 10:10 PM, MItchell Church
wrote:
> Is anyone else having trouble getting st to accept font changes? I've tried
> numerous strings using xfontsel, many of which work fine in other terminal
> programs. Is st support for this limited at the moment? Thanks.
Could you be mor
On Wed, Nov 17, 2010 at 2:54 PM, Damian Okrasa wrote:
> changed FONT and BOLDFONT, more fonts are selected
> fixed bug in ttyread, does ncurses apps work correctly?
It's much better now. Curses apps still have the same problem, but
changing TERM back to xterm made them work correctly (which is go
Is anyone else having trouble getting st to accept font changes? I've tried
numerous strings using xfontsel, many of which work fine in other terminal
programs. Is st support for this limited at the moment? Thanks.
changed FONT and BOLDFONT, more fonts are selected
fixed bug in ttyread, does ncurses apps work correctly?
st-utf8.diff
Description: Binary data
