Small style change. Persisted changes across the document.
This commit is contained in:
parent
8fe7ba6d29
commit
6104fe4181
39
README.md
39
README.md
|
@ -1,27 +1,28 @@
|
|||
<code>mp_suggest</code> is a simple little organizational tool for MP3
|
||||
<code>mp\_suggest</code> is a simple little organizational tool for MP3
|
||||
collections. I wrote it a few years ago to help me organize my own
|
||||
collection, and when the Hy Programming Language came out, I decided it
|
||||
was time for a minor exercise. Rewriting mp\_suggest in Hy was a
|
||||
perfect opportunity.
|
||||
was time for a minor exercise. Rewriting <code>mp\_suggest</code> in Hy
|
||||
was a perfect opportunity.
|
||||
|
||||
<code>mp\_suggest</code> does *not* alter your MP3 files; instead, it
|
||||
prints to stdout a simple Bash script that invokes the command-line
|
||||
program id3v2; you can capture that script and run it by hand, or pipe
|
||||
the output of <code>mp\_suggest</code> through <code>sed</code> to make
|
||||
changes on the fly, or just run the output straight into Bash with a
|
||||
unix pipe.
|
||||
prints to stdout a simple <code>bash</code> script that invokes the
|
||||
command-line program id3v2; you can capture that script and run it by
|
||||
hand, or pipe the output of <code>mp\_suggest</code> through
|
||||
<code>sed</code> to make changes on the fly, or just run the output
|
||||
straight into <code>bash</code> with a unix pipe.
|
||||
|
||||
Writing mp_suggest was an interesting exercise in returning to Lisp
|
||||
after all these years. I find that I really enjoyed it (although,
|
||||
honestly, Hy's debugging facilities leave a lot to be desired). The
|
||||
style used inside mp_suggest is most definitely not Lispy; looking
|
||||
through it, with its persistent use of cheap anonymous functions and
|
||||
closures and its function-level metaprogramming, I guess the best
|
||||
language I could compare it to is Coffeescript. I like Coffeescript a
|
||||
lot, but I don't get many opportunities to use it professionally, but
|
||||
the sensibilities of Coffeescript (especially Reginald Braithwaite's
|
||||
Ristrettology and his other books on functional programming) heavily
|
||||
influenced the design decisions I made in mp_suggest.
|
||||
Writing <code>mp\_suggest</code> was an interesting exercise in
|
||||
returning to Lisp after all these years. I find that I really enjoyed
|
||||
it (although, honestly, Hy's debugging facilities leave a lot to be
|
||||
desired). The style used inside <code>mp\_suggest</code> is most
|
||||
definitely not Lispy; looking through it, with its persistent use of
|
||||
cheap anonymous functions and closures and its function-level
|
||||
metaprogramming, I guess the best language I could compare it to is
|
||||
Coffeescript. I like Coffeescript a lot, but I don't get many
|
||||
opportunities to use it professionally, but the sensibilities of
|
||||
Coffeescript (especially Reginald Braithwaite's Ristrettology and his
|
||||
other books on functional programming) heavily influenced the design
|
||||
decisions I made in <code>mp_suggest</code>.
|
||||
|
||||
* Licensing
|
||||
|
||||
|
|
Loading…
Reference in New Issue