From: Brandon Invergo <brandon@invergo.net>
To: Guile User <guile-user@gnu.org>
Subject: [ANN] guile-file-names 0.2
Date: Thu, 16 May 2019 10:06:36 +0100 [thread overview]
Message-ID: <87a7fmkbtv.fsf@invergo.net> (raw)
Hello,
I'm happy to announce the release of guile-file-names 0.2.
The (file-names) module provides methods for manipulating file names.
Its design distinguishes between the human-friendly string format of
filenames ("/usr/bin/guile") and a more Scheme-friendly representation
to take out all the little nuisances of working with file names.
This release sees bugs fixed, under-the-hood improvements, and new
features added. See below for an excerpt from the NEWS file.
Download:
http://brandon.invergo.net/software/download/guile-file-names/guile-file-names-0.2.tar.gz
http://brandon.invergo.net/software/download/guile-file-names/guile-file-names-0.2.tar.gz.sig
guile-file-names-0.2.tar.gz sha256sum:
28d63bec3e484ae5c98431b77f0a1bcc50e2f351cf432b383009106a152c9dcf
If you use the library, please consider reporting any bugs you encounter
or feature requests you might have on the issue tracker on Gitlab:
https://gitlab.com/brandoninvergo/guile-file-names
Direct email to me is also fine, if you don't have a Gitlab account.
NEWS:
** Features
*** Native file-globbing sub-module
A new sub-module (file-names glob) has been added. This module
provides the <file-name> method glob, which is used to perform
"file-globbing." File-globbing is the method of finding multiple
files, e.g. at the shell, by matching wildcards
(e.g. "/usr/lib/*.so").
glob supports shell-style wildcards (*, ?, [] and **) as
well as full regular expressions.
*** string->file-name now takes optional keyword arguments
This allows you to override system- or parsed- defaults for the
volume, separator and case-sensitivity.
*** New <file-name> methods remove-prefix and remove-prefix!
These new methods convert an absolute file name to a relative one by
removing a leading directory prefix.
*** Specialized write and display methods for <file-name> objects
Running write or display on a <file-name> object now prints a
recognizable string representation of the file name rather than the
default cryptic GOOPS-object format:
#+BEGIN_EXAMPLE
scheme@(guile-user)> (use-modules (file-names))
scheme@(guile-user)> (define f (string->file-name "/usr/bin/guile"))
scheme@(guile-user)> (simple-format #t "~a\n" f)
#<<file-name> /usr/bin/guile>
#+END_EXAMPLE
** Bugs
*** Resolving an absolute file name
It is now an explicit error if there are double-dots at the root of
the file name (e.g. "/../foo/bar"). Also, a bug was fixed where
sequential double-dots ("../../../blah.txt") were not handled correctly.
*** file-name=? now behaves correctly for relative file names.
--
-brandon
next reply other threads:[~2019-05-16 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 9:06 Brandon Invergo [this message]
2019-05-16 20:01 ` [ANN] guile-file-names 0.2 Mark H Weaver
2019-05-16 20:06 ` Mark H Weaver
2019-05-17 8:36 ` Brandon Invergo
2019-05-22 22:03 ` exporting GOOPS generic functions, was: " Brandon Invergo
2019-05-25 1:21 ` Mark H Weaver
2019-05-25 2:14 ` Mark H Weaver
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=87a7fmkbtv.fsf@invergo.net \
--to=brandon@invergo.net \
--cc=guile-user@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).