From: Amirouche Boubekki <amirouche@hypermove.net>
To: sph@posteo.eu
Cc: guile-user@gnu.org,
guile-user <guile-user-bounces+amirouche=hypermove.net@gnu.org>
Subject: Re: here is one way to implement file globbing
Date: Tue, 16 Oct 2018 17:12:25 +0200 [thread overview]
Message-ID: <bf52cad752b1c858cd43544c7c44c1a6@hypermove.net> (raw)
In-Reply-To: <92c495d8442433c77df97732730ae60c@posteo.de>
On 2018-10-16 01:12, tantalum wrote:
> im sure it is not the optimal way to do it, and currently it fails on
> file access errors and there might be bugs, but it has cool features
> and i just wanted to share.
[...]
> here is the code with reduced dependencies so that anybody with only
> guile should be able to run it:
> http://files.sph.mn/s/computer/guile-fsg.scm
>
> it is now part of sph-lib:
> https://github.com/sph-mn/sph-lib/blob/master/modules/sph/filesystem.scm
>
Thanks for sharing.
prev parent reply other threads:[~2018-10-16 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 23:12 here is one way to implement file globbing tantalum
2018-10-16 15:12 ` Amirouche Boubekki [this message]
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=bf52cad752b1c858cd43544c7c44c1a6@hypermove.net \
--to=amirouche@hypermove.net \
--cc=guile-user-bounces+amirouche=hypermove.net@gnu.org \
--cc=guile-user@gnu.org \
--cc=sph@posteo.eu \
/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).