On Sun, Sep 03, 2017 at 10:06:35AM -0700, Eric Pruitt wrote:
> On Sun, Sep 03, 2017 at 06:31:44PM +0200, Hadrien Lacour wrote:
> > I see, thanks. Don't know why I thought it was like this. Well, I'll try it
> > but fontconfig is indeed a big pain in the ass (editing XML is never fun).
>
> If you do
On Sun, Sep 03, 2017 at 06:31:44PM +0200, Hadrien Lacour wrote:
> I see, thanks. Don't know why I thought it was like this. Well, I'll try it
> but fontconfig is indeed a big pain in the ass (editing XML is never fun).
If you don't mind running an older revision of st (or porting my changes
to a n
On Sun, Sep 03, 2017 at 06:24:13PM +0200, Quentin Rameau wrote:
> > Hello,
>
> Hello Hadrien,
>
> > I'm trying view Japanese text but I don't manage to. Here's what I do
> > with urxvt (it works):
> > $ urxvt -fn "xft:xos4 Terminus:size=12,xft:Misc Fixed:size=11"
> >
> > with st (it doesn't; I get
> Hello,
Hello Hadrien,
> I'm trying view Japanese text but I don't manage to. Here's what I do
> with urxvt (it works):
> $ urxvt -fn "xft:xos4 Terminus:size=12,xft:Misc Fixed:size=11"
>
> with st (it doesn't; I get blank spaces or squares):
> $ st -f "xos4 Terminus:size=12,Misc Fixed Wide:size
Hello,
I'm trying view Japanese text but I don't manage to. Here's what I do with
urxvt (it works):
$ urxvt -fn "xft:xos4 Terminus:size=12,xft:Misc Fixed:size=11"
with st (it doesn't; I get blank spaces or squares):
$ st -f "xos4 Terminus:size=12,Misc Fixed Wide:size=11"
Am I doing something wro
On 07/01/2013, Raphael Proust wrote:
> Real difference is du handles hard links (i.e. shows actual disk usage
> (as one would expect) by counting hard-linked files only once) while
> ls list files (as one would expect) (and optionally gives some
> information about them). Which wins.
Ah, yes, I m
On Sun, Jan 6, 2013 at 2:02 PM, Strake wrote:
> On 06/01/2013, pancake wrote:
>> Didnt checked, but i guess that ls -s show size in bytes and du in block
>> bytes, which depends on filesystem.
>
> Nope. Both show size in blocks [1].
>
> It seems proper to do so in ls alone, with a flag of whether
On 01/06/2013 05:51 AM, Christoph Lohmann wrote:
Does freetype appear in the ldd(1) output? Does it appear when you leave
out ‐lfreetype?
Yes, even without -lfreetype. I think one of the other shared libraries
is pulling it in.
I renamed my libfreetype.a to libfreetype.a.bak and the bloati
On 06/01/2013, pancake wrote:
> Didnt checked, but i guess that ls -s show size in bytes and du in block
> bytes, which depends on filesystem.
Nope. Both show size in blocks [1].
It seems proper to do so in ls alone, with a flag of whether to add
sizes of all files below; thus we could drop du.
Greetings.
On Sun, 06 Jan 2013 14:51:43 +0100 Charlie Kester wrote:
> Interesting. I get much a much bigger executable with the latest git.
>
> So I dug a little deeper and the problem seems to occur when pkg-config
> adds -lfreetype to the linker flags.
>
> Omitting that linker flag gets me
Didnt checked, but i guess that ls -s show size in bytes and du in block bytes,
which depends on filesystem.
ls -s : file size
du : disk used
On Jan 6, 2013, at 13:02, markus schnalke wrote:
> [2013-01-05 18:55] Christoph Lohmann <2...@r-36.net>
>>
>>% ls -hs st-0.3/st
>>126K st
>
>
[2013-01-05 18:55] Christoph Lohmann <2...@r-36.net>
>
> % ls -hs st-0.3/st
> 126K st
I wondered why 20h did not use `du -h st-0.3/st' instead.
Then I wondered why ls(1) has `-s' at all.
Even in 1st Edition Unix, ls(1) has `-s' although du(1) is available.
http://man.cat-v.o
> >That’s only partially true. The array is adding 48k, which another patch
> >series will reduce. Most of the additional memory usage is due to the
> >font handling. So the inability of font handling in X.org/Fontconfig is
> >the reason why too much has to be done over and over again. Yet ano
On 01/05/2013 09:55 AM, Christoph Lohmann wrote:
Greetings.
On Sat, 05 Jan 2013 18:55:12 +0100 Charlie Kester wrote:
Of course, some growth is expected as new features are added, but going
from 38k to 618k is hard to swallow.
On my system:
% ls -hs st-0.3/st
126K st
On Jan 5, 2013 1:21 PM, "Christoph Lohmann" <2...@r-36.net> wrote:
>
> What are the list's opinions?
>
Extract the keys to another header, categorize keys somehow, add defines in
config.mk to include/exclude different category keys. Or document defines
in readme. Possible categories: EXTENDED_FN,
Greetings.
On Sat, 05 Jan 2013 18:55:12 +0100 Charlie Kester wrote:
> Of course, some growth is expected as new features are added, but going
> from 38k to 618k is hard to swallow.
On my system:
% ls -hs st-0.3/st
126K st
% strip st-0.3/st && ls -hs st-0.3/st
48
On 01/05/2013 07:33 AM, Charlie Kester wrote:
On 01/05/2013 06:57 AM, Christoph Lohmann wrote:
Greetings.
On Sat, 05 Jan 2013 15:57:21 +0100 Charlie
Kester wrote:
On 12/29/2012 12:20 AM, Kai Hendry wrote:
Initially I was worried that the newer version was somehow slower to
the version I was r
On 01/05/2013 06:57 AM, Christoph Lohmann wrote:
Greetings.
On Sat, 05 Jan 2013 15:57:21 +0100 Charlie Kester wrote:
On 12/29/2012 12:20 AM, Kai Hendry wrote:
Initially I was worried that the newer version was somehow slower to
the version I was running before.
Not slower, but definitely bi
Greetings.
On Sat, 05 Jan 2013 15:57:21 +0100 Charlie Kester wrote:
> On 12/29/2012 12:20 AM, Kai Hendry wrote:
> > Initially I was worried that the newer version was somehow slower to
> > the version I was running before.
>
> Not slower, but definitely bigger. The stripped executable is now 16
On 12/29/2012 12:20 AM, Kai Hendry wrote:
Initially I was worried that the newer version was somehow slower to
the version I was running before.
Not slower, but definitely bigger. The stripped executable is now 16x
the size of that from the 0.3 release -- thanks, no doubt, to these font
cach
Greetings.
On Sat, 29 Dec 2012 15:05:00 +0100 p37si...@lavabit.com wrote:
> On Sat, Dec 29, 2012 at 04:20:11PM +0800, Kai Hendry wrote:
> > So I just compared a little before the font code change and I couldn't
> > really see a difference tbh.
>
> You can see the difference when you copy and past
On Sat, Dec 29, 2012 at 04:20:11PM +0800, Kai Hendry wrote:
> So I just compared a little before the font code change and I couldn't
> really see a difference tbh.
You can see the difference when you copy and paste characters that are
not in your font. For example: "⊥" is not present in Terminus.
Initially I was worried that the newer version was somehow slower to
the version I was running before. I can't tell the version I was
running before, hence the silly patch.
So I just compared a little before the font code change and I couldn't
really see a difference tbh.
http://s.natalian.org/201
Greetings comrades,
please check out the git of st. Now there is a huge fallback code with
yet another font cache. Some memory regressions are fixed too, which al‐
lows unlimited zoom. Wide character drawing is not correct now, but al‐
samixer correctly displays all the line drawing.
Please re
24 matches
Mail list logo
