Re: Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity

Op 01-09-2023 om 11:33 schreef Vili Aapro: Dear all, for Geiser (specifically, `geiser-edit-symbol-at-point') compatibility, we would like the Guile procedure `program-source' always to return absolute paths; for this, we would need compiler co-operation. Specifically, it would be desirable

Re: Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity

On Mon, 25 Sep 2023 11:26:31 +0200 Maxime Devos wrote: > Sounds like a very bad idea. The absolute file name would be somewhere > in the build directory, which very likely doesn't exist anymore on a > typical installation. Yes, you are right. > I suppose that whatever code > is responsible

Re: Replacing Guile test-suite with SRFI-64?

Op 25-09-2023 om 01:32 schreef Mike Gran: A benefit of SRFI-64 is that the SRFI-64 implementation has tests whereas (IIRC) Guile's custom thing doesn't. OK two separate issues. 1. Mike G's gripes about SRFI-64. 2. Updating over 65,000 lines of test code These aren't separate issues -- if SRFI

Re: Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity

Op 25-09-2023 om 11:36 schreef Vili Aapro: On Mon, 25 Sep 2023 11:26:31 +0200 Maxime Devos wrote: Sounds like a very bad idea. The absolute file name would be somewhere in the build directory, which very likely doesn't exist anymore on a typical installation. Yes, you are right. I suppo

Re: [PATCH v2 4/4] load: Display modules depth in output when using %load-verbosely.

Op 10-09-2023 om 16:46 schreef Maxim Cournoyer: - (force-output) +(define (%load-announce file depth) + (when %load-verbosely +(with-output-to-port (current-warning-port) + (lambda () +(let* ((pad-count (- 3 (string-length (number->string depth +

Re: Inconsistency with expressions between definitions

Hi again! I am not sure about letrec*, but this should really raise an error in r6rs. You cannot reference a variable before it is assigned. I said it "would work in racket" because I believe it uses the same algorithm for deciding when and how and where and how and when things are bound in l

Re: Inconsistency with expressions between definitions

Linus Björnstam writes: > are bound in letrec*. This should also be the case in chez, but chez > displays an error. Given I have found the chez is never wrong with > regards to R6RS we can say that guiles behaviour is not conformant > with r6rs. … > What I am saying is: congrats, you found a bug

[PATCH v4 3/4] guix.scm: Update guile package native inputs.

* guix.scm (guile) [native-inputs]: Replace texlive-base with texlive-scheme-basic. Add git:send-email. --- (no changes since v1) .guix/modules/guile-package.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.guix/modules/guile-package.scm b/.guix/modules/guile-package.s

[PATCH v4 0/4] Add module depth information to %load-verbosely output

This change was made to support investigating cyclic module dependencies that sometimes happen in GNU Guix and are difficult to comprehend/debug. For more context, see: . Changes in v4: - Remove with-output-to-port in %load-announce and adjust doc Changes in v3

[PATCH v4 2/4] .dir-locals: Set c-basic-offset to 2 for c-mode.

* .dir-locals.el (c-mode): Set c-basic-offset to 2. --- (no changes since v1) .dir-locals.el | 1 + 1 file changed, 1 insertion(+) diff --git a/.dir-locals.el b/.dir-locals.el index 908670479..f63bdc8a3 100644 --- a/.dir-locals.el +++ b/.dir-locals.el @@ -3,6 +3,7 @@ ((nil . ((fill

[PATCH v4 1/4] (ice-9 boot-9): Fix typo.

* module/ice-9/boot-9.scm (module-use-interfaces!): Fix typo in doc string. --- (no changes since v1) module/ice-9/boot-9.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/module/ice-9/boot-9.scm b/module/ice-9/boot-9.scm index a5f2eea9b..897d8d01c 100644 --- a/module/ice-9

[PATCH v4 4/4] load: Display modules depth in output when using %load-verbosely.

* NEWS: Update news. * THANKS: Add myself. * doc/guile-api.alist (%load-announce, %load-hook): Add DEPTH argument. * doc/ref/api-evaluation.texi (Loading): Document new DEPTH argument for the primitive-load, primitive-load-path and %load-hook procedures. Update %load-hook example. Document %load-

[PATCH] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

* module/web/uri.scm (remove-dot-segments): Implement algorithm 5.2.4. (merge-paths): Implement algorithm 5.2.3. (resolve-relative-reference): Implement algorithm 5.2.2. (module): Export resolve-relative-reference. * NEWS: Reference it here. --- Dear Guile developers, When you request https://exam

Re: [PATCH] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

Op 25-09-2023 om 18:48 schreef Vivien Kraus: * module/web/uri.scm (remove-dot-segments): Implement algorithm 5.2.4. (merge-paths): Implement algorithm 5.2.3. (resolve-relative-reference): Implement algorithm 5.2.2. (module): Export resolve-relative-reference. * NEWS: Reference it here. --- Dear

[PATCH v2] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

* module/web/uri.scm (remove-dot-segments): Implement algorithm 5.2.4. (merge-paths): Implement algorithm 5.2.3. (resolve-relative-reference): Implement algorithm 5.2.2. (module): Export resolve-relative-reference. * NEWS: Reference it here. * doc/ref/web.texi (URIs): Document it here. (Subtypes of