From: Thien-Thi Nguyen <ttn@gnu.org>
To: guile-sources@gnu.org
Cc: guile-user@gnu.org
Subject: xdgdirs 1.0
Date: Thu, 05 Sep 2013 12:42:55 +0200 [thread overview]
Message-ID: <87hadzczww.fsf@zigzag.favinet> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]
Greetings earthlings,
I'm contemplating adding XDG basedirs support to GNU Alive and GNU
Serveez, so the obvious approach is classic modularity: write the
functionality once and somehow make it available. It's no big deal to
start w/ ‘define-module’, but then the questions begin:
- What is a good module name?
- What package does it belong to?
- Does the use case justify keeping all this code in memory?
- Is this really "write once"?
- What about Lisp programs?
- What about programs (in any language) that can ‘read’ sexps?
The functionality is basically using ‘getenv’ and ‘parse-path’ to
produce easily-serialized data (strings and lists of strings), amenable
to piping and other textual manipulations. So, why not a standalone
program?
As to the packaging, for a bit i mulled over a "XDG Utils" package with
only one program to start, but that would be succumbing to my bad habit
of overengineering things, so i'm glad to say that bit was short-lived.
Anyway, here it is:
[-- Attachment #1.2: xdgdirs --]
[-- Type: application/x-scheme, Size: 4386 bytes --]
[-- Attachment #1.3: Type: text/plain, Size: 442 bytes --]
Installation is simple:
# install xdgdirs /usr/local/bin
The program supports ‘--help’ and ‘--version’, which must suffice in
lieu of proper documentation, for now. Maybe some future release...
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2013-09-05 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 10:42 Thien-Thi Nguyen [this message]
2013-09-07 8:36 ` xdgdirs 1.0 Andy Wingo
2013-09-07 9:10 ` Thien-Thi Nguyen
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=87hadzczww.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=guile-sources@gnu.org \
--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).