xdgdirs 1.0

xdgdirs 1.0

[Thien-Thi Nguyen]

[-- 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 --]

Re: xdgdirs 1.0

[Andy Wingo]

Just a bunch of random things.  No opinion about module names, etc :)

On Thu 05 Sep 2013 12:42, Thien-Thi Nguyen <ttn@gnu.org> writes:

> (define mentioned?
>   (let ((cl (command-line)))
>     (lambda (opt)
>       (member opt cl))))

You could do this as (cute member <> (command-line)), having imported
srfi-26.

> (cond ((mentioned? "--help")
>        (use-modules (ice-9 documentation))
>        (fso "~A~%" (file-commentary (car (command-line))))
>        (exit #t)))

Here I think "when" is much more readable.  Also, you can use
"(current-file-name)" for a more reliable way to get the current file
name.

> (cond ((mentioned? "--version")
>        (fso "xdgdirs ~A~%~A~%" VERSION COPYRIGHT)
>        (fso "~A ~A~%~A~%~A~%"
>             "License GPLv3+: GNU GPL version 3 or later"
>             "<http://gnu.org/licenses/gpl.html>"
>             "This is free software: you are free to change and redistribute it."
>             "There is NO WARRANTY, to the extent permitted by law.")
>        (exit #t)))

You can use (ice-9 command-line)'s version-etc.

Regards,

Andy
-- 
http://wingolog.org/

Re: xdgdirs 1.0

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

() Andy Wingo <wingo@pobox.com>
() Sat, 07 Sep 2013 10:36:38 +0200

   > (define mentioned? ...)

   You could do this as (cute member <> (command-line)),
   having imported srfi-26.

   > (cond ((mentioned? "--help") ...)

   Here I think "when" is much more readable.  Also, you can use
   "(current-file-name)" for a more reliable way to get the current
   file name.

   > (cond ((mentioned? "--version") ...)

   You can use (ice-9 command-line)'s version-etc.

Thanks for the tips.  I'll try to keep these in mind.

-- 
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 --]