From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: 60528@debbugs.gnu.org
Subject: bug#60528: uri->string swallows mandatory slashes
Date: Tue, 03 Jan 2023 21:00:48 +0100 [thread overview]
Message-ID: <4d95ebf7d53d8604fef2ffc8a4ff60dae8ead27f.camel@gmail.com> (raw)
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 "file:///home")
$1 = #<<uri> scheme: file userinfo: #f host: #f port: #f path: "/home"
query: #f fragment: #f>
scheme@(guile-user)> (uri->string $1)
$2 = "file:/home"
scheme@(guile-user)> (uri->string (build-uri 'file #:host "" #:path
"/home"))
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Throw to key `uri-error' with args `("Expected valid host: ~s" (""))'.
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
Cheers
next reply other threads:[~2023-01-03 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 20:00 Liliana Marie Prikler [this message]
2023-01-04 8:11 ` bug#60528: uri->string swallows mandatory slashes tomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d95ebf7d53d8604fef2ffc8a4ff60dae8ead27f.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=60528@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).