I think I found a possible bug on st when inserting a unicode character.
Here are the steps for someone to try to reproduce it.
Take the heavy round-tipped rightwards arrow (U+279C) for example.
➔
Highlight to copy and middle-click to paste into st.
Now try to immediately write something. The chara
On Tue, 12 Apr 2016 11:09:55 -0300, Marc Collin wrote:
> Really a bug or something wrong only for me?
For me, it works fine. It may be a problem with your font.
Cheers,
Gabriel
--
Gabriel Pérez-Cerezo Flohr ['peɾeθ θe'ɾeθo floːɐ]
Encrypt your e-mails! — GPG Key: BB09BA34D353EC69
Plain-text ribb
Works here too. If I type something
right after the arrow, the latter cuts
a bit though, being still visible.
Mitt
No problem here. I am using st with:
static char font[] = "Liberation
Mono:pixelsize=15:antialias=true:autohint=true";
On 2016-04-12 at 11:09, Marc Collin wrote:
> Really a bug or something wrong only for me?
I haven't noticed until now, but I can reproduce the problem with
static char font[] = "Inconsolata for
Powerline:pixelsize=16:antialias=false:autohint=false";
Best regards,
Andreas
It's been a few weeks since I set up my set config.h and it's lost
now, but I'm almost sure I'm using the font Terminus, size 12,
antialias disabled.
On Tue, Apr 12, 2016 at 11:25 AM, Greg Reagle wrote:
> No problem here. I am using st with:
> static char font[] = "Liberation
> Mono:pixelsize=1
On Tue, 12 Apr 2016 16:33:58 +0200, Andreas Doll wrote:
>
> On 2016-04-12 at 11:09, Marc Collin wrote:
> > Really a bug or something wrong only for me?
>
> I haven't noticed until now, but I can reproduce the problem with
>
> static char font[] = "Inconsolata for
> Powerline:pixelsize=16:antia
I made a new test and came up with some more information that may help.
Inserting the arrow and then one single space makes the arrow head not show.
But if you go to another workspace on dwm and come back, st will
redraw and the arrow head will appear.
In similar way, inserting the arrow and giving
On Wed, 06 Apr 2016 18:45:57 -0500, Joshua Haase wrote:
> Marc André Tanner writes:
> > you do not have to prefix your sam command with `ggvG` because
> > in normal mode it will by default be applied to the whole file.
>
> Or you could use `:,` to mean the whole file (i. e. `:,y/\n/i/FOO`).
Or
I found the same last December and had a look into it, but my conclusion was
that it's a bug in the font/libc, so I didn't reported my findings here.
From my notes back then:
- st expects chars to have a fixed width (see [1]).
- It uses wcwidth(3) to get the length and reserves as much space on th
So this is not a st bug and not a libc bug.
Just a font bug?
I'll test a few fonts and check which doesn't work, then I'm emailing
the authors of the fonts.
How can we easily describe the problem so the font authors can fix it?
Thanks.
On Tue, Apr 12, 2016 at 3:46 PM, Jochen Sprickerhof
wrote:
Hi,
I usually compile suckless software with tcc,
but it fails at static linking, so I found myself
cloning scc.
I changed PREFIX in config.mk to /usr/local and
successfully installed it. First, what are cc1 and cc2?
Also, I couldn't find a man page. Compiling Hello World
with cc1 says it can't
* Marc Collin [2016-04-12 16:31]:
> So this is not a st bug and not a libc bug.
I think it's a libc bug as well, quoting man 3 wcwidth:
"The wcwidth() function returns the number of columns needed to
represent the wide character c. If c is a printable wide character, the
value is at least 0. If
On Tue, Apr 12, 2016 at 11:37:51PM +0200, Jochen Sprickerhof wrote:
> Not even sure here, I assume xft pulls in other (non monospace) fonts to
> display missing symbols.
Unfortunately not. Xft doesn't have native support for fallback fonts,
and you have to write the code yourself or use a higher-l
14 matches
Mail list logo
