On Sat, Jul 20, 2024 at 09:18:53PM +0200, Maxime Devos wrote: [...]
> Also, AFAIK that %3a encoding isn’t necessary (and neither recognised(^)) in > Guile – I don’t think Guile does any percent encoding(*). I think naming the > file “srfi/:1.scm” would work fine, although it’s not something I’ve tried > before. (There might be a problem with Makefile if ‘make’ doesn’t like the :, > but I have some ideas for simple ways around that.) For civilised file systems, yes. Windows will balk at the colon. (Windows balks at lots of funny things in file names: the colon, I somewhat expect, from DOS inheritance, but AFAIR, "+" is also a no-go). I guess that's where this funky URL encoding was intended to fix. Cheers -- t
signature.asc
Description: PGP signature
