The eddie package

[ Tags: bsd3, cli-tool, program ] [ Propose Tags ]

A tool to let you use short haskell expressions to filter files at the command line.

[Skip to Readme]


Versions 0.1, 0.2, 0.5, 0.5.1, 1.0.0
Dependencies base (>=4.2.0 && <5), bifunctors (>=4.2), classy-prelude (>=0.12), hint (>=, optparse-applicative (>=0.11), safe (>=0.3.8) [details]
License BSD3
Copyright (c) 2014 Mike Meyer
Author Mike Meyer
Category CLI tool
Home page
Source repository head: SourceRepo {repoKind = RepoHead, repoType = Just (OtherRepoType "fs"), repoLocation = Just "", repoModule = Nothing, repoBranch = Nothing, repoTag = Nothing, repoSubdir = Nothing}
this: SourceRepo {repoKind = RepoThis, repoType = Just (OtherRepoType "fs"), repoLocation = Just "", repoModule = Nothing, repoBranch = Nothing, repoTag = Just "1.0.0", repoSubdir = Nothing}
Uploaded Wed May 27 21:26:37 UTC 2015 by MikeMeyer
Distributions NixOS:1.0.0
Executables eddie
Downloads 1160 total (11 in the last 30 days)
Rating 0.0 (0 ratings) [clear rating]
  • λ
  • λ
  • λ
Status Docs not available [build log]
Last success reported on 2015-11-12 [all 7 reports]
Hackage Matrix CI


Maintainer's Corner

For package maintainers and hackage trustees

Readme for eddie-1.0.0

[back to package description]

What is eddie?

A command line tool for running Haskell functions over text files.

It is also useful for prototyping Haskell text processing functions that you will later copy into a program.

Why is eddie?

This project actually started in response to a code bounty for a clojure shell scripting tool. That resulted in a specification for the requested program that had all the features of eddie, and then some. However, clojure code embedded on the command line looks clumsy, so the project was shelved.

In haskell, functional expression are much simpler and more elegant. In particular, in looking for haskell command line tools, I found, which convinced me that the original design would be not merely usable, but elegant if the expressions were done in haskell. Hence, eddie.

Why not ghc -e?

Eddie adds features to make using it for shell scripting easier:

  • When given file arguments, eddie feeds them to your function.
  • Eddie can easily add modules to the namespace you use.
  • Eddie has options for processing things a line or file at a time.
  • Eddie uses either Text or ByteStrings by default, not lists of characters.

More information

The best place to start is the manual. That's available in the source tree in both man format in eddie.1, and in html in eddie.html. The latter is also available online.


Install or build with cabal as usual.


Testing is done with the haskell shelltestrunner package (which can be installed with cabal). Run shelltest tests in the source directory to run the tests with the currently installed eddie. Use shelltest tests -w eddie.hs to run them using the current source. Use shelltest tests -w dist/build/eddie/eddie to run them with the compiled binary.


The documenation is built with pandoc from Use the -s flag, and convert from pandoc's markdown to your chosen format.