lentil 1.0.0.1 → 1.0.1.0

raw patch · 6 files changed

+20/−10 lines, 6 files

Files

• changes.txt +8/−0
• doc/usr/page.rst +3/−3
• lentil.cabal +1/−1
• src/Lentil/Parse/Issue.hs +6/−4
• src/Main.hs +1/−1
• test/Lentil/Parse/IssueSpec.hs +1/−1

@@ -1,3 +1,11 @@+1.0.1.0+-------++- Released Fri 02 Sep 2016 19:04:13 CEST+- Removed "Feature" flagword (too many false positives on repos+  like the Linux kernel).+  I plan to readd it as an option.+ 1.0.0.1 ------- 

@@ -102,7 +102,7 @@ ------------  lentil parses basic ``TODO`` issues. The precise syntax is: keyword (one-of ``todo``, ``fixme``, ``xxx``, ``feature``), optional semicolon, followed+of ``todo``, ``fixme``, ``xxx``), optional semicolon, followed by a space, followed by free-form text (text can be multiline). In so many words, it is quite liberal in what it accepts: @@ -135,8 +135,8 @@  Tags are single words which are useful to catalogue and identify issues. Use them aplenty as they will make slicing and dicing your issue-base a breeze.-Since the semantic of ``FIXME``, ``XXX`` and ``Feature`` is specific (in-respect to the usual ``TODO``), they are automatically added as a tag.+Since the semantic of ``FIXME`` and ``XXX`` is specific (in respect to+the usual ``TODO``), they are automatically added as a tag.  As now lentil parses: 

@@ -1,5 +1,5 @@ name:                lentil-version:             1.0.0.1+version:             1.0.1.0 synopsis:            frugal issue tracker description:         minumum effort, cohesive issue tracker based on                      ubiquitous @TODO@s and @FIXME@s conventions.

@@ -30,17 +30,19 @@ -- TODO: "feature" flagword could (in theory) clash with a free-text comment --       (if it is present in the middle of a sentence at the beginning --       of a line). Consider alternatives (as: making new words---       configurable in .lentil dotfile [design] [u:2] [bug]+--       configurable in .lentil dotfile. After checking the linux+--       kernel, it definitely is. Erase it and possibly make it+--       an option [design] [u:3] [bug]  -- issue flagword-data FlagWord = Todo | Fixme | Xxx | Feature deriving (Enum, Eq)+data FlagWord = Todo | Fixme | Xxx deriving (Enum, Eq)   instance Show FlagWord where   show Todo    = "todo"   show Fixme   = "fixme"   show Xxx     = "xxx"-  show Feature = "feature"+  -- show Feature = "feature"  -- top-level constant to evaluate once flagWords :: [String]@@ -51,7 +53,7 @@     "todo"    -> Todo     "fixme"   -> Fixme     "xxx"     -> Xxx-    "feature" -> Feature+    -- "feature" -> Feature     e         -> error ("unrecognised flag word: " ++ e)  

@@ -28,7 +28,7 @@                                    short 'v'      <>                                    help "show version and copyright info" )     where-          versionCopy = "\nlentil - frugal issue tracker, version 1.0.0.1\n\+          versionCopy = "\nlentil - frugal issue tracker, version 1.0.1.0\n\                         \(C) 2015-2016 Francesco Ariis - http://www.ariis.it\n\                         \released under the GNU General Public License v3\n" 

@@ -60,7 +60,7 @@        do sp incipit "\n TODO: "  `shouldBe` Just Todo           sp incipit "\n FIXME: "  `shouldBe` Just Fixme           sp incipit "\nXXX: "  `shouldBe` Just Xxx-          sp incipit "\n Feature: "  `shouldBe` Just Feature+          -- sp incipit "\n Feature: "  `shouldBe` Just Feature     it "doesn't work without previous newline" $       sp incipit "\nTODO:some"  `shouldBe` Nothing     it "doesn't work with longer matches (todoodle)" $