On Fri, Jan 29, 2021 at 11:31:31AM +0100, Laslo Hunhold wrote:
> On Thu, 28 Jan 2021 16:06:28 -0300
> Pedro Lucas Porcellis <porcellis_AT_eletrotupi.com> wrote:
>
> > ---
> > README.md | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/README.md b/README.md
> > index 6ece4c0..d3a815f 100644
> > --- a/README.md
> > +++ b/README.md
> > _AT_@ -18,7 +18,7 @@ Programs you can use lchat as a front end for:
> > Requirements
> > ------------
> >
> > - * libutf
> > + * [libutf](https://git.suckless.org/sbase)
> > * tail(1)
> > * grep(1)
> >
> > --
> > 2.30.0
> >
> >
>
> I don't know if that's really correct, given sbase does not install the
> library on the system. Instead, sbase just has a local copy, compiles
> it as a static library (.a) and links it into each binary statically.
> It would make more sense to do the same for lchat, but I'd rather check
> and see what really is needed.
You are right. I also thought about that, before committing the diff.
But, I have the same advice in config.mk. So, the advice is correct for
the moment. But, I also would prefer to install a libutf with your
distros package manager. (e.g. pkg_add libutf).
> From what I can tell, reading the slackline-source, one could easily
> port it to libgrapheme, for example, because the utf.h-requirement is
> only necessary for "Rune"-handling (i.e. Codepoints). By porting lchat
> to libgrapheme you would get grapheme-cluster-support for free on top
> of that.
Thats on my TODO list :-)
Thanks,
Jan
Received on Fri Jan 29 2021 - 17:37:34 CET