urghh the urge to install #guix on my #nixos and play with the #guile lang and the hoot framework..
https://youtube.com/shorts/QlqtTKB_ccA?si=mV8KZBIwmSSpZcbv
WWE Stars Take Over Street Fighter: Cody Rhodes and Roman Reigns Revealed!
.
.
.
Linktr.ee/562AlexD
#StreetFighter
#WWE
#CodyRhodes
#RomanReigns
#MovieNews
#Gaming
#Wrestling
#Hollywood
#ActionMovies
#Crossover
#Guile
#Akuma
#Entertainment
#MovieCast
#Film2026
Street Fighter ficha al actor perfecto para Guile (y no, no es Van Damme). El reparto de esta película es bastante épico y va aumentando #StreetFighter #Guile #CodyRhodes 🎮 https://www.cinemascomics.com/street-fighter-ficha-actor-perfecto-guile/
Did you notice, that Guile moved to Codeberg?
Street Fighter II: Turbo/Hyper Fighting Japanese Commercial (1992)
#レトロゲーム #ゲーム #Gaming #StreetFighter #RetroGaming #SFC #Games #VideoGames #Guile #FightingGames #Capcom #FGC #SNES #90s #StreetFighter2 #Nintendo #RetroGames #SuperFamicom #Commercial #Advertising #Marketing #GameDev #IndieDev
If I want to provide a "thing" that defines few bindings in a current module, can I write it as a procedure instead of a syntax-case macro? This:
(define (define-stuff)
(let ((m (current-module)))
(module-define! m 'foo 1)
(module-define! m 'bar 2)))
seems to work, however I am getting "possibly unbound variable" warnings (but the code seems to work). Is there a way around that? Or do I need use the syntax-case approach (with-syntax, and regular define)?
I have few #macports patches starting a #guile ecosystem. Since I will not be using macos anymore, I will no longer work towards getting them upstream. However, if your are interested, let me know and I will share the patches so that *you* can upstream them.
Port group:
guile
New ports:
guile-colorized
guile-json
guile-ssh
guile-gcrypt
guile-sqlite3
guile-zlib
guile-scheme-bytestructures
guile-git
guile-srfi-197
guile-wolfsden
guile-lib
Updates:
guile-gnutls 4.0.1
With the idea of promoting the usage of #guix and my favourite #programming language #guile #scheme I created a small project which is still in early stages, but I think with some more #love and #effort can be quite something.
https://jointhefreeworld.org/guile-show-hub/
The Guile ShowHub! Promoting all Guile projects out there! By reading from #foss Guix project source code we can tap into a plethora of information, and leverage the #homoiconicity of #lisp to directly analyze the source code and extract info.
#GuileEmacs is stalled again?
Also found this email in the projects mailing list from an individual showing their concerns https://lists.hcoop.net/pipermail/guile-emacs-devel/2025-May/000007.html
@baleine and I have been messing around with Guile's Stack Traces and now they are freaking awesome.
I've just packed wayland-scm in #Guix. Sane multischeme (#guile, #chicken,
#gauche) #bindings for #wayland by Mal https://codeberg.org/kfu
See: https://codeberg.org/shegeley/wayland-scm/src/branch/guix
I was able to launch 'empty-window.scm' example. See 'make -f example.Makefile'.
I didn not yet tried it on other complex interfaces (from wlroots). It
might need few more changes to work with them.
Also see my post on existing wayland bindings in Lisps:
https://grigory.tech/posts/wayland-lisps.html
@MishaVelthuis At the end of the day, your goals will dictate which tools to use..#NixOS and its own language have a bigger community at the moment..but there is nothing better than hacking in #Guile if you love #emacs and the #GNU project.
scheme@(guile-user)> 1234
$1 = 1234
scheme@(guile-user)> 12_34
$2 = 1234
scheme@(guile-user)> 123_456_789
$3 = 123456789
Hm, I wonder whether this would be accepted into #guile . Any opinions?
About a year ago, I wrote a #guile #scheme UUID library (https://codeberg.org/elb/guile-uuid) as part of a personal project that is currently stalled, but I went ahead and released the UUID library as #OpenSource / #FreeSoftware because it seemed individually useful. A few months ago, a kind third-party individual started the process of packaging it for #Guix (which I use!). Today he had the packaging PR merged on @Codeberg (where my project is also hosted). This is why I love FLOSS!
@MinervasRefuge Fear of Macros is nice. I went through it on the stream and adapted to guile specifics: https://youtu.be/Ag4movPnGa8?list=PLZmotIJq3yOJzhA0T6Y6EH2gxMfIm5pVQ
Also, take a look at syntax-rules primer: http://www.phyast.pitt.edu/~micheles/syntax-rules.pdf
And Writing Powerful Macros: https://mnieper.github.io/scheme-macros/README.html
I sat down the other day to re-look through David Thompson guile-bstructs
library, as a learning exercise.
I re-learnt a few things I didn't know before. Like how far it's possible to push syntax-rules/case
. I've never quite seen anything like it before.
I've said it before, but scheme syntax-rule
related stuff isn't the most intuitive thing. Fear of Macros is still the best explanation I've read; but doesn't show off the capability quite like that library does.
I took a look at differences between args-fold (as shipped with Guile) and getopt_long: https://wolfsden.cz/blog/post/parsing-differences-between-guile-s-srfi-37-and-getopt-long.html
In related news, I just need to write a documentation and my own args-fold, (almost) fully compatible with getopt_long, will be done.