Re: mumi issue tracker interface for Guile
"Dr. Arne Babenhauserheide" <[email protected]> Sun, 06 Apr 2025 19:31:34 +0200
| Newsgroups | gmane.lisp.guile.devel,gmane.lisp.guile.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Maxim, Hi Arun, Maxim Cournoyer <[email protected]> writes: >> Arun Isaac <[email protected]> writes: >>> https://issues.guix.gnu.org/guile . I hope the Guile project can benefit >> In general for mumi I tried to use it, but failed at the initial steps: >> if I do not have it set up yet (nothing set up), what do I need to do to >> use it for Guile? > $ mumi search submitter:arne is:open > --8<---------------cut here---------------start------------->8--- > mumi search submitter:arne is:open My first step felt a bit strange: $ cd path/to/guile && LANG=C guix shell mumi -- mumi search submitter:arne is:open Backtrace: 4 (primitive-load "/gnu/store/3kxdvvql3q9fq0jr4i93gjxd2hvi06k4-mumi-0.13.0/bin/.mumi-real") In mumi/client.scm: 87:13 3 (search _) 71:16 2 (client-config mumi-scheme) In ice-9/ports.scm: 450:11 1 (call-with-input-file "path/to/guile/.mumi/config" #<procedure read (#:optional port)> #:binary _ #:encoding _ #:guess-encoding _) In unknown file: 0 (open-file "path/to/guile/.mumi/config" "r" #:encoding #f #:guess-encoding #f) ERROR: In procedure open-file: In procedure open-file: No such file or directory: "path/to/guile/.mumi/config" First need to create a config: $ mkdir .mumi && echo '((debbugs-host . "debbugs.gnu.org") (patch-email-address . "[email protected]") (mumi-host . "issues.guix.gnu.org"))' > .mumi/config $ LANG=C guix shell mumi -- mumi search submitter:arne is:open 72208 [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi opened 9 months ago by Dr. Arne Babenhauserheide, last updated 5 months ago … ^ works now. > 1. Applying a patch series locally $ mumi current 72208 72208 [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi opened 9 months ago by Dr. Arne Babenhauserheide, last updated 5 months ago $ mumi am Applying: doc: tour: note the top-level modules ice-9, scheme, and srfi This has a strange result: commit 5ec4503bcdd4abfeccac146d0cd118119d1fdd53 Author: Dr. Arne Babenhauserheide <[email protected]> doc: tour: note the top-level modules ice-9, scheme, and srfi --=-=-= Content-Type: text/plain Hi, the attached patch is a companion to the thread "The Guile junk drawer and a C plea" in guile-devel. Its goal is to ensure that newcomers learn early about the main module prefixes provided by Guile: (scheme ...), (srfi ...), and (ice-9 ...). From 929f5075be5d21c552e91931aca4a68fde348e21 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide <[email protected]> Date: Sat, 20 Jul 2024 15:03:15 +0200 Subject: [PATCH] doc: reference ice-9, scheme, and srfi * doc/ref/tour.texi (Using Modules): reference ice-9, scheme, and srfi. Looks like it pulled in too much from the email? > 2. Send a multiple messages series $ git format-patch --cover-letter HEAD^ -o my-patches my-patches/0000-cover-letter.patch my-patches/0001-doc-tour-note-the-top-level-modules-ice-9-scheme-and.patch (it feels like it may be nice not to venture into git here and instead do something like mumi create-patches HEAD^ ⇒ mumi-patches-72208/ and then $ mumi send-email ) I’m a bit afraid of calling mumi send-email, because I have no feeling for what it will do. Will it honor the current issue? I guess that yes. > Happy hacking! Thank you! And thank you for the explanation! Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de
signature.asc
(application/pgp-signature, 1.1 KB)
-----BEGIN PGP SIGNATURE----- iQJEBAEBCAAuFiEE801qEjXQSQPNItXAE++NRSQDw+sFAmfyunYQHGFybmVfYmFi QHdlYi5kZQAKCRAT741FJAPD631zD/0WXgRUP8vuiYrr8uDm8U/XwncvggjBDX69 D4kHA7t5VyKBEOVd1xh29yVQaV51YLNinIVlgfeW74zrb+twxAaMuFmCHO86CSmW 0kugXA1otVXlWfXlq8hNmloidZeIFskIX8wRMsRklXuA5nTfLAm0sNaezGnlAaIp M53LBqD8+7BmOu9ijqJAekbjuoNda4XJWIybiXvtQqpKtYkOzhHJ2qXEyoD4ZohX o1uhv1393wAQaPXddlbHechFuRX//F6VD7/B+ZoOhVZL/0gaBC8AXzMWODxUzsrl nQHQ5Ntz/cxM+yyBef19DOGhIJATbWoUd2P+RylE8xDfXEXkv53QfP/kcjRUp/Sw C+KUkIS2mjVF35Y05/0Df6q1OM5BSrd1qADe1VJYw2OwfZ6jPa6N117YSEyEhXQd tFkq5n2LCdSVSwYtGP3xpih3ekXjIaKXU7BFZ0SuUR5utsJI21Gf8Uq8IiABWsBS vjocjjhIt0WjXq7htnJs+6cM9Y6rlXl0mEEJXOpKCgnFJI0R3tu0hty2GxL8FQbQ 3eWdcQS9pvIchI6Q+At6s689Ztl6JP7gEea63LLWlCgFGJ6kpDQVvbRBhXOSeFWc pVhu6ZwWXAM0o47g5SHmu2bRuwoCFd3b13lqsj9Lvg5HzhcNtfVLp2KbTn9CzShe yNzFEkqyaYjEBAEBCAAuFiEE3Si95tmHXKvOSosd3M8NswvBBUgFAmfyunYQHGFy bmVfYmFiQHdlYi5kZQAKCRDczw2zC8EFSAs4A/4vJiaVDfe2uL6A05vWfU81Cg3H JAYGeny3/f10EfOgoZlgNwVoY1HGLBll/RgnC2tgokaKnh/v1Eti44vyN7OE6p+1 eAqKeCFOprp57kes+F8AoOUOSlWhYH+fpGe4tHH0U7pyG4N7ryijICcGqKtWGc9X QfBBzgCqEosfxc0RTQ== =vQzj -----END PGP SIGNATURE-----