bug#72154: test-error does not work

foo actual-error: + (bar) result: PASS According to feedback from mastodon it is not really implemented. That does not seem to be documented. Maybe it would be better to just not export it? Or it should throw 'not-implemented instead of just passing? Have a nice day, Tomas -- There are

bug#72153: Test name is evaluated twice

: PASS That does not seem to be allowed by SRFI-64. I do not believe this is limited to test-assert, I managed to reproduce with test-equal as well. Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

bug#71980: [3.0.10] posix.test uses depcrecated tmpnam

t; -(with-error-to-port port > - (lambda () > -(system* "sh" "-c" "echo bong >&2" > +(system* "sh" "-c" "echo bong >&2")) > >

bug#71800: [PATCH 1/2] doc: Document #:hide.

* doc/ref/api-modules.texi (Using Guile Modules): Document #:hide. --- doc/ref/api-modules.texi | 29 ++--- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi index 9f2bba02d..efe739a25 100644 ---

bug#71800: [PATCH 2/2] doc: Fix implication of omitting optional arguments.

According to the previous wording, omitting all optional arguments led to empty interface. That however was not the case and was only a documentation bug (as confirmed by wingo on IRC). So let us fix that. * doc/ref/api-modules.texi (Using Guile Modules): Fix implication of omitting optional

bug#71800: [PATCH 0/2] Improve documentation about using modules.

Document the #:hide argument. Correct text for implication of leaving all optional arguments out. Tomas Volf (2): doc: Document #:hide. doc: Fix implication of omitting optional arguments. doc/ref/api-modules.texi | 29 ++--- 1 file changed, 18 insertions(+), 11

bug#71798: [PATCH 1/2] doc: Document #:hide.

* doc/ref/api-modules.texi (Using Guile Modules): Document #:hide. --- doc/ref/api-modules.texi | 29 ++--- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi index 9f2bba02d..efe739a25 100644 ---

bug#71799: [PATCH 2/2] doc: Fix implication of omitting optional arguments.

According to the previous wording, omitting all optional arguments led to empty interface. That however was not the case and was only a documentation bug (as confirmed by wingo on IRC). So let us fix that. * doc/ref/api-modules.texi (Using Guile Modules): Fix implication of omitting optional

bug#71796: [PATCH] Do not depend on tmpnam in posix.test.

`tmpnam' is a deprecated procedure that can be excluded during a configure (`--disable-tmpnam'). There currently was a single test relying on it, and therefore failing is such configuration. This commit switches to mkstemp instead. * test-suite/tests/posix.test ("system*"): Use mkstemp instead

bug#71262: [PATCH] Try to install C.UTF-8 locale before falling back to C.

If user does not have LANG or LC_ALL set (as does often happen in various sandboxes) glibc will just install C locale. That is fine (and permissible by POSIX), however in Guile's context it is of a mixed usefulness due to the absence of UTF-8 support. This commit changes the locale

bug#71047: [PATCH] doc: Recommend alist-copy instead of list-copy.

The current recommendation of `list-copy' is not right and does not lead to preserving the original list: scheme@(guile-user)> (define x (list (cons 'a 1) (cons 'b 2))) scheme@(guile-user)> (define y (list-copy x)) scheme@(guile-user)> (assq-set! y 'b 3) $1 = ((a . 1) (b . 3))

bug#68504: [PATCH v3] Add copy-on-write support to scm_copy_file.

uto case: CoW ---fail--> copy_file_range ---fail--> current copy ---fail--> FAIL For 'never case: copy_file_range ---fail--> current copy ---fail--> FAIL Is that an accurate summary? Or did you mean only as a fallback for the CoW, so only for 'auto, but not for the '

bug#69730: Segfault in (spawn) when passed wrong port

uot;/dev/null")), I would not expect invalid value in an interpreted language to cause a segfault. If the value is indeed invalid, it should throw an error. Original report: https://emacs.ch/@kakafarm/112075808549752692 Have a nice day, Tomas Volf -- There are only two hard things in Comput

bug#69438: basename faulty with nul and suffix

On Tue, Feb 27, 2024 at 08:14:58PM +, Zefram via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: > Trying out the basename function in Guile 3.0.9: > > scheme@(guile-user)> (basename "foo/bar") > $1 = "bar" > scheme@(guile-user)> (basename "foo/bar" "r") > $2 = "ba" >

bug#68504: [PATCH] Add copy-on-write support to scm_copy_file.

time to actually form an opinion based on facts. Have a nice day, Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

bug#68504: [PATCH v3] Add copy-on-write support to scm_copy_file.

On modern file-systems (BTRFS, ZFS) it is possible to copy a file using copy-on-write method. For large files it has the advantage of being much faster and saving disk space (since identical extents are not duplicated). This feature is stable and for example coreutils' `cp' does use it

bug#68504: [PATCH v2] Add copy-on-write support to scm_copy_file.

On modern file-systems (BTRFS, ZFS) it is possible to copy a file using copy-on-write method. For large files it has the advantage of being much faster and saving disk space (since identical extents are not duplicated). This feature is stable and for example coreutils' `cp' does use it

bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file.

WDYT? Modified as agreed on irc. I am not convinced on the -P, but I defer to your judgment on this. Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

bug#68505: [PATCH v3] Add more detailed instructions into the HACKING file.

Until now, the ./meta/guile was not mentioned anywhere, and therefore it was not obvious how to run the locally compiled Guile without installing it. While modifying the file, I took the liberty to also mention a bit about compiling Guile using Guix. Finally, the header lines where cleaned up,

bug#68507: [PATCH] doc: Fix example in list-transduce example.

While the `.' might be correct from a grammatical point of view (I do not know), it turns the example into invalid scheme code, which is not ideal. New users (like me) might try to copy the whole line and wonder why it does not work (like I did). So delete it. * doc/ref/srfi-modules.texi

bug#68506: [PATCH v3] doc: Extend documentation for (ice-9 match)

Extend the documentation for (ice-9 match) module with explanations of some of the patterns and also provide more examples for them. That should make it more useful for people trying to use the module for the first time just based on the documentation. * doc/ref/match.texi (Pattern Matching):

bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file.

Until now, the ./meta/guile was not mentioned anywhere, and therefore it was not obvious how to run the locally compiled Guile without installing it. While modifying the file, I took the liberty to also mention a bit about compiling Guile using Guix. Finally, the header lines where cleaned up,

bug#68504: [PATCH] Add copy-on-write support to scm_copy_file.

On modern file-systems (BTRFS, ZFS) it is possible to copy a file using copy-on-write method. For large files it has the advantage of being much faster and saving disk space (since identical extents are not duplicated). This feature is stable and for example coreutils' `cp' does use it

bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros., bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros., control message for bug #66531

Mike Gran writes: Hello, > I haven't forgotten about this. My linux devel box died. > > Maybe someone else can make the push, otherwise, I'll be back in business in > a couple weeks. Just a polite ping regarding this patch. Thank you and have a nice day, Tomas Volf

bug#68350: Segmentation fault using list-head with negative k

lloda writes: > I think this is another dupe of https://debbugs.gnu.org/58154. Highly possible. Like Ricardo I cannot reproduce this with a local build I made from the tip of the repo. (I saw the same segfault using list-ref with the debian 3.0.8 version FWIW.) -- Tomas

bug#68350: Segmentation fault using list-head with negative k

8-2 all Documentation for Guile 3.0 ii guile-3.0-libs:amd643.0.8-2 amd64Core Guile libraries Thanks for all the work -- Tomas

bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros.

on the radar. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros.

er from here, that would be great. :) > > Mike Gran Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros.

Both macros were missing a quote for the procedure call, causing the actual return value to be compiled into the ftw.go, instead of the procedure call. Snippet from disassembly of ftw.go does confirm that: 55(make-immediate 2 3990) ;; 997at ice-9/ftw.scm:319:46

bug#66135: Unable to download Guile tar file

ou know. Thank you for the details! You may try the "-S" options to wget: this will print the HTTP headers, which might help in identifying the problem. If I do that, this is what I see: | tomas@trotzki:/tmp$ wget -S https://ftp.gnu.org/gnu/guile/guile-3.0.9.tar.gz | --202

bug#66135: Unable to download Guile tar file

It worked for me too. On Sat, Sep 23, 2023 at 09:19:54AM +0530, ahmad khizir wrote: > Not working for me, i can share the screenshot. Perhaps better if you describe what you are trying (how are you downloading, perhaps whether you are in a company or country which might enforce network

bug#63196: Further on this error message

On Mon, May 01, 2023 at 10:44:18AM +0800, Christopher Lam wrote: > The source seems to be sxpath.scm -- see "yikes" error which triggers when > n is -2 -4 -6 etc. I don't know how to build guile from sources and cannot > debug further. > > > (define (node-pos n) > (lambda (nodeset) > (cond

bug#62053: Guile compiler is unable to compile tiny program

to disable. > ;;; compiling /home/amaya/tmp/guile-compiler-bug.scm > ;;; WARNING: compilation of /home/amaya/tmp/guile-compiler-bug.scm failed: > ;;; not found 22 >   > Compiler reports confusing message here: `not found 22’.    Bizarre. Can confirm tomas@trotzki:~/foo$ vim buggy.scm to

bug#60528: uri->string swallows mandatory slashes

On Tue, Jan 03, 2023 at 09:00:48PM +0100, Liliana Marie Prikler wrote: > Hi folks, > > Below some unexpected behaviour observed in Guile 3.0.8, but it also > dates back to 2.2.7 and possibly earlier versions. > > scheme@(guile-user)> ,use (web uri) > scheme@(guile-user)> (string->uri

bug#60522: make-vector takes 100% cpu if called without argument in the REPL

On Tue, Jan 03, 2023 at 05:57:19PM +0100, Sascha Ziemann wrote: > The following throws an error: > guile -c '(make-vector)' > > But the evaluation of '(make-vector)' in the REPL generats just a warning: > > ;;; :1:0: warning: possibly wrong number of arguments to `make-vector' > > and seems to

bug#59874: Segfault from string-ref with negative 'k'

e repositories. Hi, this is Debian GNU/Linux, x86_64, but a self-compiled Guile: | tomas@trotzki:~$ guile | GNU Guile 3.0.8.57-bc3b1 | Copyright (C) 1995-2022 Free Software Foundation, Inc. | | Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'. | This program is free software,

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

On Sun, Nov 20, 2022 at 06:24:57PM +0100, Ludovic Courtès wrote: > Hi, > > Andrew Whatson skribis: > > > Forcibly closing file descriptors like this shouldn't be necessary if > > the application has properly opened descriptors with the FD_CLOEXEC > > flag. It would be good to get input from

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

On Fri, Nov 18, 2022 at 02:49:05PM +1000, Andrew Whatson wrote: > Hi Nate, > > Thanks for reporting this! I'm able to reproduce on my systems, and > have identified the culprit: [250k calls to close()] Well spotted. Here [1] is a good discussion on the problem. Spoiler alert: there is no

bug#59221: (file-exists? #f) raises an exception

On Sun, Nov 13, 2022 at 02:15:43AM +, jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: > November 12, 2022 12:58 PM, "Jean Abou Samra" wrote: > > >> Le 12 nov. 2022 à 18:50, Joshua Branson via Bug reports for GUILE, GNU's > >> Ubiquitous Extension > >>

bug#51133: [PATCH 1/1] Tolerate http response line without reason phrase

On Tue, Oct 12, 2021 at 10:26:22AM +0200, Alexey Abramov via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: > Hi, > > I agree that it is not a complient http response, According to The Book [1] ;-) there should be at least one space (SP) (as far as I understand this is really

bug#49693: Bad address of FSF in module/language/elisp/compile-tree-il.scm

Hi, There is a bad address specified in the license of module/language/elisp/compile-tree-il.scm file in version 3.0.7. I am attaching a patch to fix this. commit 5a888dc8cba740718d302e4e759b28bc19a9d06c Author: Tomas Korbar Date: Thu Jul 22 13:02:56 2021 +0200 Fix address of FSF diff

bug#49638: Guile 3.0.7 can not be compiled on Fedora rawhide

Hi Guys, I am trying to package guile 3.0.7 into Fedora but I encountered a problem. In sources, there is a header lib/libc-config.h and then there is preprocessor condition for presence of __attribute_maybe_unused__ macro. This macro is newly defined in the latest version of glibc which we have

bug#46447: segfault with bugnum

On Thu, Feb 11, 2021 at 09:54:38PM +0100, Ricardo Wurmus wrote: > This program sometimes causes Guile 3.0.5 to segfault: > > (define a (expt 2 (expt 3 (expt 4 2 > (display (remainder a 10)) > (display "\n") > > And sometimes this program doesn’t terminate. Here’s an example >

bug#46014: (define (thunk) (lambda (x) x)) should be a compile error?

On Fri, Jan 22, 2021 at 09:47:24AM -0500, jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: > Ricardo Wurmus writes: > > > Hi Joshua, > > > >> When I look at > >> > >> #+BEGIN_SRC scheme > >> (define (thunk) > >>(lambda (x) > >> x)) > >> #+END_SRC > > > >

bug#45923: Hot to intall Guile without Make

On Sun, Jan 17, 2021 at 09:18:59PM +0100, Dr. Arne Babenhauserheide wrote: > > paul.eb...@mail.de writes: > > > is there a way to install Guile or Make on Manjaro without an internet > > connection and without having already installed one of them? > > You’ll need to build and install make once

bug#45923: Hot to intall Guile without Make

On Sat, Jan 16, 2021 at 11:42:18PM +0100, paul.eb...@mail.de wrote: > Hello everyone, I'm very sorry, if this is the wrong mail adress > for my problem, but I couldn't find another to seek for help. I > just thought that you are probably the expert for my question and > are maybe willing to

bug#43364: Possible bug with output redirection

On Sat, Sep 12, 2020 at 10:59:23PM +0200, pinoaffe wrote: > Dear guilers, > > When using with-output-to-string, the output of external processes > started using system* and the like is not redirected to the temporary > port. As far as I can tell, it just redirects things written/displayed > from

bug#43326: [3.0.x] Regression: Compilation error involving strings

On Fri, Sep 11, 2020 at 03:31:24PM +0700, Erik Dominikus wrote: > Dear author(s) of the Guile 3.0.x compiler, > > Background: I would like to report a problem that I found while trying > to write a simple web server with get-string-n, sxml simple, and web > server. > > I have traced and reduced

bug#42012: Reference Manual and Docstring on number->string

On Tue, Jun 23, 2020 at 12:51:23AM +0200, Sebastian Miele wrote: > Guile 3.0.3. The reference manual and the docstring of number->string > say: "If N is inexact, a radix of 10 will be used." But that is not what > happens, e.g., > > (let ((x 4.0)) (and (inexact? x) (number->string x 3))) > >

bug#41320: sxml attributes of some elements are in reverse order

On Sat, May 16, 2020 at 02:27:15PM +0200, Jan Synacek wrote: [...] > > just imagine another XML processor in the middle changing > > attribute order. It would be spec compliant. What now? [...] > In the middle of the first processor reading the file? No, I was thinking much simpler than that.

bug#41320: sxml attributes of some elements are in reverse order

On Sat, May 16, 2020 at 12:29:54PM +0200, Jan Synacek wrote: > Consider the following code snippet running on Guile-3.0.2: [...] > [...] > (event (@ (number 2) (name KeyPress)) > Attributes 'number' and 'name' are in reverse compared to the original > xml. On the other hand, 'type' and

bug#40855: integer-length 0 should be 1

On Sat, Apr 25, 2020 at 11:15:40PM +0200, Bengt Richter wrote: > I'm hoping this is the right place to report this bug :) > > To reproduce, guile -c '(format #t "~s\n" (integer-length 0))' > Expected result if correct: 1 > Observed result: 0 > > The following is to support the opinion that 1 is

bug#40008: Backtraces can contain very long strings

On Tue, Mar 10, 2020 at 11:05:24AM +0100, Jan Synacek wrote: > I have the following backtrace: > > Backtrace: > In ice-9/boot-9.scm: > 1736:10 9 (with-exception-handler _ _ #:unwind? _ # _) > In unknown file: >8 (apply-smob/0 #) > In ice-9/boot-9.scm: > 718:2 7

bug#38486: Compiler does not terminate

. FWIW, I just tried with guile 2.9.5 and the compile terminates: tomas@trotzki:~$ guile /tmp/zack.scm ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0 ;;; or pass the --no-auto-compile argument to disable. ;;; compiling /tmp/zack.scm ;;; compiled /home/tomas/.cache/guil

bug#38398: non-obvious SCM_EOF_VAL rationale

On Wed, Nov 27, 2019 at 12:05:34PM +, Zefram via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: [...] > But please don't get sidetracked. This wasn't a feature request for > "#eof" [...] To be fair, you contributed strongly to this side-tracking. By waving a big red

bug#38235: string-foldcase bug for trailing sigma

On Sat, Nov 16, 2019 at 09:41:05PM +0100, Andy Wingo wrote: > Given the following example, using (rnrs unicode): > > (string-foldcase "ΜΈΛΟΣ") Good catch. I think there's even a worse example: dotless and dotted I [1]. Here it seems even impossible to do up- and downcase correctly without

bug#36251: Regex library doesn't recognize ']' in a character class

On Tue, Jun 18, 2019 at 07:08:06AM -0400, Mark H Weaver wrote: > Hi, > > Abdulrahman Semrie writes: > > > I am using the pattern [\\[\\]a-zA-Z]+ to match a string with left or > > right bracket in it [...] > It turns out that there are several flavors of regular expressions in > common use,

bug#36251: Regex library doesn't recognize ']' in a character class

On Sun, Jun 16, 2019 at 08:16:29PM +0300, Abdulrahman Semrie wrote: > > I am using the pattern [\\[\\]a-zA-Z]+ to match a string with left or right > bracket in it. However, the string-match function doesn’t match the ‘]’ > character. To demonstrate with an example, try the following funciton:

bug#20339: Taking a step back (was: sxml simple: sxml->xml mishandles namespaces?)

Hi, after mulling over it for a while, I think it's time to take a step back and think a bit about where we'd like to go with this. Note that I'm ignoring technical details (the fact that the SXML, and thus the XML serialization now has namespace declarations everywhere down the path instead of

bug#20339: sxml simple: sxml->xml mishandles namespaces?

;sxml' ;;; note: source file ./sxml/simple.scm ;;; newer than compiled /usr/local/lib/guile/2.2/ccache/sxml/simple.go ;;; found fresh local cache at /home/tomas/.cache/guile/ccache/2.2-LE-8-3.A/home/tomas/guile/sxml-fix/sxml/simple.scm.go (*TOP* (*PI* xml "version=\&q

bug#34457: GNU Guile: Error in docstring of proc reverse-list->string

On Tue, Feb 12, 2019 at 03:34:06PM +0400, Андрей wrote: > Good day! > > The docstring of `reverse-list->string` proc says: > ``` > scheme@(guile-user)> (help reverse-list->string ) > `reverse-list->string' is a procedure in the (guile) module. > > - Scheme Procedure: reverse-list->string chrs >

bug#20339: sxml simple: sxml->xml mishandles namespaces?

On Mon, Feb 04, 2019 at 09:44:02PM +0100, Ricardo Wurmus wrote: > Hello! > > I just looked at this again and I think I came with something useful. > Here’s some context: [...] > Attached is a patch that does the requested things. The parser > procedures like FINISH-ELEMENT have access to all

bug#29684: exception printers - request for improvement

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jul 03, 2018 at 04:31:23PM -0300, David Pirotte wrote: > Hi Ludovic, > > > > It is perfectly fine, on the opposite side, to ask advanced scheme users > > > (who > > > would want to, but I really don't see the point) configure guile s the >

bug#26221: (define function nil should work in 2.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Mar 23, 2017 at 07:59:04PM +, Joshua Branson wrote: > > I can confirm this bug. Eshell accepts (defun hello nil (print “Hello")) > And (hello) works properly. > > M-x guiler > > ,languages elisp > > (defun hello nil (print

bug#26151: date-year-day screws up leap days prior to AD 1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Mar 18, 2017 at 01:10:58AM +, Zefram wrote: [...] > Where did you get the idea to use a non-linear year numbering? What's > your opinion of SRFI-19's (lack of) text on this matter? You should > consider the possibility of changing your

bug#24659: 'mkdir' procedure is neither thread-safe nor safe (2.0.12)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 10, 2016 at 06:39:47PM +0200, Ludovic Courtès wrote: > Hello! [...] > Furthermore, AFAICS, the above logic is redundant with what the kernel > does anyway. That is, in a single-threaded program, > > mask = umask (0); > umask

bug#20339: sxml simple: sxml->xml mishandles namespaces?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jul 14, 2016 at 12:10:17PM +0200, Andy Wingo wrote: > Hi :) > > On Wed 13 Jul 2016 15:24, to...@tuxteam.de writes: > > > Referring to Oleg Kiseliov's paper [1], there are actually three > > things involved: > > This summary is helpful,

bug#20339: sxml simple: sxml->xml mishandles namespaces?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Jul 13, 2016 at 03:24:03PM +0200, to...@tuxteam.de wrote: [...] > What is missing? From my point of view: > > - At xml->sxml time, the user doesn't know which namespaces >are in the xml. So it would be nice if the XML parser >could

bug#20339: sxml simple: sxml->xml mishandles namespaces?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 23, 2016 at 09:32:16PM +0200, Andy Wingo wrote: > See thread here as well: > http://thread.gmane.org/gmane.lisp.guile.devel/17709 > > I like Ricardo's patch but have some comments here: >

bug#23739: Unexpected behavior of 'add-to-load-path'.

/guile/site" "/usr/share/guile")) > --8<---cut here---end--->8--- I can confirm half of it :-) I mean: the double entry "foo" for %load-path in your first result above doesn't happen for me. Could that be a typo? As for the str

bug#18592: FFI should have portable access to ‘errno’

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 05, 2016 at 10:24:35AM +0800, Chaos Eternal wrote: > On Tue, Jan 5, 2016 at 3:14 AM, Nala Ginrut wrote: > > Hi Mark! > > Thanks for all the advices. > > > > Here's the new patch according to your advices. > >

bug#21855: eq?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 07, 2015 at 01:58:48PM +0100, Atticus wrote: > So I wanted to try out gnu guix and thus make myself more familiar with > guile first. While running some tests I encountered a problem/bug with eq?: > > $ guile -v > guile (GNU Guile) 2.1.1

bug#21373: compile for development version from git fails on OpenBSD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Aug 28, 2015 at 09:47:51PM -0400, Jamil Egdemir wrote: Hi Guys, I just pulled the latest from the git repo and the build failed on OpenBSD 5.6 (output from dmesg is all the way at the bottom if that helps): $ git clone

bug#20339: sxml simple: sxml-xml mishandles namespaces?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Apr 23, 2015 at 09:04:46AM +0200, Ricardo Wurmus wrote: to...@tuxteam.de writes: What's yet missing (as far as I can read off the diff) is a way to dream up an abbreviation when it's not in the namespaces alist. True. Ideally,

bug#20339: [PATCH] sxml-xml and namespaces: updated patch

Hi, I've embellished my proposed patch a bit: - use values resp. call-with-values instead of passing around lists. This was one thing I didn't like about my first patch candidate: the namespace -- ns abbreviation lookup had two things to return, for noe the abbreviation, and

bug#20339: sxml simple: sxml-xml mishandles namespaces?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I posted more details on guile-devel. Perhaps this was the wrong list? When transforming SXML to XML, namespaces don't seem to be handled properly: #!/usr/bin/guile -s !# (use-modules (sxml simple)) ;; An XML with two namespaces

Re: AG, that im living

Banned CD! Government don't want me to sell it. See Now # woody incurred precipitate jar confiscate anemone cheyenne nebula signify melon nonce beloit hackney innermost send gainful admission deane susan downgrade carla babylon filamentary applicable conglomerate brownell floppy apology greet

Re: Strange behaviour of array?

surprised it's not fixed in 1.6.0, but maybe it's because I never sent the patch in... Thanks a zillion. I'll try this out when out of crunch mode. I'll keep you informed Regards -- tomas ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org