Re: Maintenance and future of Guile

Ludovic Courtès writes: > If someone is interested, please get in touch with us! > > While Andy focuses on major improvements to the compiler and VM with a > long-term vision, I think it would be great to also have people on the > maintainer team focusing on more day-to-day operations: incrementa

Re: Maintenance and future of Guile

Taylan Kammer writes: > On 17.12.2021 16:48, Olivier Dion wrote: >>> Olivier Dion skribis: >>> I would also like to contribute in some meaningful way. In what way someone with none wizard knowledge of Scheme can contribute the most to the project? >>> >> On Fri, 17 Dec 2021, Ludo

Re: Maintenance and future of Guile

Tim Van den Langenbergh writes: > That sounds like a good idea, though I wonder what the best way to organise > it would be. > > IRC, Mattermost, and Rocket Chat seem like the most obvious options > for chat. I don't know what would be best for task management, maybe > some out-of-the-box kanban?

Re: Maintenance and future of Guile

"Dr. Arne Babenhauserheide" writes: > Olivier Dion via "Developers list for Guile, the GNU extensibility > library" writes: > >>> irc is good for me, and of course e-mail :) >>> >>> but for out-of-the-box task management tools, are we all emacs >>> and/or org-mode users >>> here? we could agree

Re: Goblins on Guile at FOSDEM: following along

Hi Christine! This is great! Unfortunately due to existing commitments I might miss it, will it be recorded? I'm actually planning to reach out to you as I'm doing an A/V video mapping installation in Singapore this summer that requires networked user interaction and figured it might be small eno

Re: Maintenance and future of Guile

Considering this conversation is coming back, I'd mention that I'd be happy to become a Guile "janitor" (as discussed earlier) with some guidance, as I've only been using Guile for a year and still learning the internals, but have some patch series fixing some old bugs I've found. I could also hel

[PATCH v1 5/6] docs/fixup: @cindex was in the wrong place

--- doc/ref/match.texi | 13 ++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/doc/ref/match.texi b/doc/ref/match.texi index 4f3dc86fc..5512103c4 100644 --- a/doc/ref/match.texi +++ b/doc/ref/match.texi @@ -23,11 +23,11 @@ The @code{(ice-9 match)} module provides a @dfn{

[PATCH v1 4/6] docs/match: match-let* unwrap example

[pdf] now builds, but there are some spacing issues I want to correct in the PDF, that will be introduced next. --- doc/ref/match.texi | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/doc/ref/match.texi b/doc/ref/match.texi index 567146a35..4f3dc86fc 100644 --

[PATCH v1 1/6] docs/match: add pattern matching examples

Hello all, This commit introduces a set of (long overdue) examples to the documentation on pattern matching discussed in the Guix Days presentation which can be found here: https://xana.lepiller.eu/guix-days-2022/guix-days-2022-documentation.mp4 As discussed in the Guix Days presentation, and agr

[PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo

don't know how to fix this rn, but... --- doc/ref/match.texi | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/doc/ref/match.texi b/doc/ref/match.texi index 105150886..c5017e1a5 100644 --- a/doc/ref/match.texi +++ b/doc/ref/match.texi @@ -80,10 +80,10 @@ Patterns

[PATCH v1 6/6] docs/match:style reviewing with pdf, adding newlines

--- doc/ref/match.texi | 78 -- 1 file changed, 47 insertions(+), 31 deletions(-) diff --git a/doc/ref/match.texi b/doc/ref/match.texi index 5512103c4..38745e173 100644 --- a/doc/ref/match.texi +++ b/doc/ref/match.texi @@ -19,15 +19,15 @@ @cindex patte

[PATCH v1 3/6] docs/match: add reverse nested list example

--- doc/ref/match.texi | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/ref/match.texi b/doc/ref/match.texi index c5017e1a5..567146a35 100644 --- a/doc/ref/match.texi +++ b/doc/ref/match.texi @@ -112,6 +112,13 @@ extract the elements that make it up. @result{} ((

Re: [PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo

Thanks! The new latest edit is still preferred but I'll keep that in mind for the future. On Fri, Jan 27, 2023, 23:33 Maxime Devos wrote: > > > On 26-01-2023 19:57, Blake Shaw wrote: > > don't know how to fix this rn, but... > > You can escape @ with @@. > >

Re: [PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo

Because the result in the final commit is better. Sorry, I should have added this commit to fixup when I was rebasing. On Sat, Jan 28, 2023, 20:08 Maxime Devos wrote: > > > On 28-01-2023 10:14, Blake Shaw wrote: > > Thanks! The new latest edit is still preferred but I'll k

Re: [PATCH v1 1/6] docs/match: add pattern matching examples

Mastodon and discovered many guix have retreated there. Now let's get into the specifics of the current patch review where I'll show why I think your efforts aren't in earnest, and even appear malign: On Sun, Jan 29, 2023 at 3:30 PM Maxime Devos wrote: > > > On 29-01-202

[PATCH v2] docs/match: pattern matcher example makeover

All changes have been squashed into a single commit [V2 update] Before I was able to render only the pdf, but it was unclear how to render an individual texinfo page. Since then I discovered [makeinfo] in emacs which solves this problem. There is some conflict between PDF and Texinfo, and Guile c

[PATCH v3] docs/match: pattern matcher example makeover

[V3 update] @xref{sxml-match} had been commented out because it was interfering with emacs makeinfo. This ammends that change. Also adding `--` to breakup changelog into a more digestible format. Reviewing everything all else, everything appears fine. [V2 update] All changes have been squashed i

Re: [PATCH v3] docs/match: pattern matcher example makeover

David Pirotte writes: > Not at all - and quite annoying. imo. > So i'd 'vote' not to use them anywhere in the guile reference manual take the following functions in both styles: (let unwrap ((peel '(unnest arbitrary nestings))) (match-let* (((core ...)) peel) ((wrappe

Re: [PATCH v3] docs/match: pattern matcher example makeover

Arun Isaac writes: > Hi Blake, > >> Well, these conventions can be found throughout the gamut of scheme >> literature going back to the 80s, and some of the largest scheme >> projects, such as Chez, Racket, etc. employ them. So if you're >> getting into Scheme, you'll necessarily encounter them

[PATCH v2] docs/match: pattern matcher example makeover

[v4 update] style: revert bracketed/Indiana style conventions in for matching I'd rather not bikeshed over this, so reverting the style changes as per the mailing list discussion: https://lists.gnu.org/archive/html/guile-devel/2023-02/msg1.html [V3 update] @xref{sxml-match} had been commented

[PATCH v4] docs/match: pattern matcher example makeover

Sorry, this is meant to be V4*, I've updated the subject accordingly Blake Shaw writes: > [v4 update] > style: revert bracketed/Indiana style conventions in for matching > I'd rather not bikeshed over this, so reverting the style changes > as per the mailing li

Re: [PATCH v3] docs/match: pattern matcher example makeover

Josselin Poiret writes: > Hi Blake and David, > > We were talking about this very node of the documentation yesterday with > Ludovic and zimoun, so here are my two cents. Rewriting this > introduction is a very good idea, the current one is pretty hard to get > into for novices. > > David Pirot

Re: possible bug in export

I would just chime in that this has caused me some trouble in the past, where an unbound variable is exported by a module. Damien Mattei writes: > hello, > i noticed that when defining a module and exporting a procedure not defined > this does not cause > an error in Guile ( at the opposite

Re: What's to be considered on-topic for Guile mailing lists? (Re: The message chain with an happy ending)

I'm sorry, I'm the one supposed to be working on a rehaul of the documentation, but the review process has slowed this down. I started integrating everyones suggestions for the revamped map section after it was proposed in January and its almost done but not complete, and but I've been so busy t