Hi Stuart,
On Tue, Apr 15, 2025 at 08:29:34PM +0100, Stuart Henderson wrote:
> > I see that FreeBSD's netsurf port (same netsurf version as ours) uses a
> > plain (updated) port of https://github.com/JuliaStrings/utf8proc rather
> > than netsurf's outdated fork of that same library.
> >
> > Here'
On 2025/04/15 20:26, Stuart Henderson wrote:
> cc'ing netsurf maintainer (in case you didn't read the earlier thread,
> neovim wants libutf8proc, Laurent has proposed a diff that builds a
> static library as part of neovim build, but this doesn't seem a good
> idea overall)
>
> On 2025/04/15 15:49
cc'ing netsurf maintainer (in case you didn't read the earlier thread,
neovim wants libutf8proc, Laurent has proposed a diff that builds a
static library as part of neovim build, but this doesn't seem a good
idea overall)
On 2025/04/15 15:49, Laurent Cheylus wrote:
> Hi Edd,
>
> - Mail origin
Hi Edd,
- Mail original -
> On Thu, Apr 03, 2025 at 05:12:38PM +0100, Stuart Henderson wrote:
> > You still need to be careful even if it's statically linked. In
> > particular you need to make sure that it can't accidentally pick up
> > anything from /usr/local/{include,lib} if present at
On Mon, Apr 14, 2025 at 10:18:35PM +0100, Edd Barrett wrote:
Hello Edd,
>> You still need to be careful even if it's statically linked. In
>> particular you need to make sure that it can't accidentally pick up
>> anything from /usr/local/{include,lib} if present at build time.
>> Especially consi
Morning,
On Mon, Apr 14, 2025 at 10:18:35PM +0100, Edd Barrett wrote:
> On Thu, Apr 03, 2025 at 05:12:38PM +0100, Stuart Henderson wrote:
> > You still need to be careful even if it's statically linked. In
> > particular you need to make sure that it can't accidentally pick up
> > anything from /u
On Thu, Apr 03, 2025 at 05:12:38PM +0100, Stuart Henderson wrote:
> You still need to be careful even if it's statically linked. In
> particular you need to make sure that it can't accidentally pick up
> anything from /usr/local/{include,lib} if present at build time.
> Especially considering what
On 2025/04/03 17:23, Laurent Cheylus wrote:
> Hi Stuart,
>
> On Thu, 3 Apr 2025 15:00:13 +0100, Stuart Henderson wrote:
>
> > On 2025/03/28 10:51, Laurent Cheylus wrote:
> >> - utf8proc library (https://github.com/JuliaStrings/utf8proc) needed to
> >> build neovim 0.11
> >> * download v2.10.0 v
Hi Stuart,
On Thu, 3 Apr 2025 15:00:13 +0100, Stuart Henderson wrote:
> On 2025/03/28 10:51, Laurent Cheylus wrote:
>> - utf8proc library (https://github.com/JuliaStrings/utf8proc) needed to
>> build neovim 0.11
>> * download v2.10.0 via DIST_TUPLE * build it with cmake and install
>> {includ
On Thu, Apr 03, 2025 at 03:00:13PM +0100, Stuart Henderson wrote:
> > * set UTF8PROC_LIBRARY and UTF8PROC_INCLUDE_DIR vars for configure
>
> there might be a problem between this and www/netsurf/libutf8proc
In addition to this, I think we should hold off the neovim+treesitter update
until after
On 2025/03/28 10:51, Laurent Cheylus wrote:
> - utf8proc library (https://github.com/JuliaStrings/utf8proc) needed to build
> neovim 0.11
> * download v2.10.0 via DIST_TUPLE
> * build it with cmake and install {include,lib} in ${STATIC_DEPS_INST}
> * set UTF8PROC_LIBRARY and UTF8PROC_INCLUDE
On Thu, Apr 03, 2025 at 07:53:13AM +, Laurent Cheylus wrote:
Hello Laurent,
>>> update for editors/neovim to the latest version 0.11.0
>> I've realised one minor problem: there is a missing dependency on
>> libutf8proc. Apart from that, this has worked well on two machines.
> utf8proc v2.10.0
Hi Laurence,
On Wed, 2 Apr 2025 08:44:07 +0100, Laurence Tratt wrote:
> On Fri, Mar 28, 2025 at 10:51:37AM +0100, Laurent Cheylus wrote:
>> update for editors/neovim to the latest version 0.11.0
>
> I've realised one minor problem: there is a missing dependency on
> libutf8proc. Apart from that,
On Fri, Mar 28, 2025 at 10:51:37AM +0100, Laurent Cheylus wrote:
Hello Laurent,
> update for editors/neovim to the latest version 0.11.0
I've realised one minor problem: there is a missing dependency on
libutf8proc. Apart from that, this has worked well on two machines.
Laurie
On Fri, Mar 28, 2025 at 10:51:37AM +0100, Laurent Cheylus wrote:
> update for editors/neovim to the latest version 0.11.0
Diff looks good to me. I'll be testing this during my workday tomorrow.
--
Best Regards
Edd Barrett
https://www.theunixzoo.co.uk
On Fri, Mar 28, 2025 at 10:51:37AM +0100, Laurent Cheylus wrote:
Hello Laurent,
> [cc edd@ as maintainer]
>
> update for editors/neovim to the latest version 0.11.0
After applying the treesitter update, this works well! My old config worked
as expected; updating it for some of the new features a
Hi ports@
[cc edd@ as maintainer]
update for editors/neovim to the latest version 0.11.0
**What's New in Neovim 0.11**
https://gpanders.com/blog/whats-new-in-neovim-0-11/
- update Makefile and distinfo for depends (according to
https://github.com/neovim/neovim/blob/v0.11.0/cmake.deps/deps.txt
17 matches
Mail list logo
