Thank you for your completely unsubstantiated and useless opinion.
On 8 March 2013 17:37, pancake <panc...@youterm.com> wrote:
> Antialiased fonts on terminals is the worst invention since transparents
> backgrounds.
>
> On Mar 8, 2013, at 6:43, Christoph Lohmann <2...@r-36.net> wrote:
>
>> Greetings.
>>
>> On Fri, 08 Mar 2013 06:43:57 +0100 "Galos, David"
>> <galos...@students.rowan.edu> wrote:
>>>> you know what sucks about this patch? there is no command line flag to
>>>> disable aa. whats up.
>>>
>>> It never occurred to me that anyone would want aa fonts. This patch
>>> just prevents FcFontMatch or its family from ever messing aa if it is
>>> specified in the user pattern.
>>
>> I’m using AA fonts – all the time. They look non‐edgy and really, I just
>> got used to them because I manually enforced aa due to this fontconfig
>> crap deactivating it in surf, so websites looked edgy. But there’s the
>> whole problem. Here st is adding a workaround for something fontconfig
>> and xft should do on their own. If I specify antialias=false, then the
>> font really should be antialiased. There shouldn’t be any reason for do‐
>> ing this manual hack, which is just a hack to work around a misdesign in
>> fontconfig and xft.
>>
>> Anyone here has the abilities or skills to send patches to xft or font‐
>> config to fix this mess?
>>
>> I don’t have a good gut feeling by adding such a flag to vanilla st be‐
>> cause someone stupid from that X* crap pile projects was unable to pro‐
>> duce something useful and flexible how it should be.
>>
>>
>> Sincerely,
>>
>> Christoph Lohmann
>>
>>
>
