On Wed, May 06, 2020 at 11:10:34PM +0100, Chris Green wrote: > On Wed, May 06, 2020 at 03:25:52PM -0400, Thomas Dickey wrote: > > On Thu, May 07, 2020 at 01:11:30AM +1000, Brendan O'Dea wrote: > > > There is quite a bit of difference in how traditional X11 bitmap fonts > > > and freetype fonts are selected and rendered > > > (https://utcc.utoronto.ca/~cks/space/blog/unix/XFontTypes gives a > > > reasonable summation) but the main thing is that from the API level > > > they are not interchangeable. XTerm has specific code to handle > > > rendering of fonts selected via -fn (server bitmap) vs -fa (client > > > rendered scalable). I don't believe that xvile has handling for the > > > latter, so is limited to traditional server provided bitmap fonts. > > > > agreed - the APIs are very different. There was no _technical_ reason > > that they had to be incompatible... > > > > Having both in xterm makes it complicated. If/when I find time to > > do TrueType for xvile, it'll be one or the other at configure/make > > time. > > > That would be OK, what will distributions/repositories do though?
s/will/would/ (this is an item from a long to-do list) Assuming that I had done the work, and it worked well enough, I'd probably change the configure-default to the preferred version :-) Most packagers would use whatever I set that to... > > > However, I mostly use vile in xterm, and after _that_, winvile. > > > I mostly use vile in a terminal, it's just that *occasionally* (such > as marking rectangular areas with the mouse) xvile is very handy. -- Thomas E. Dickey <[email protected]> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
