aboutsummaryrefslogtreecommitdiffstats
path: root/app
diff options
context:
space:
mode:
authorLibravatar Fabian Kirchner <kirchner@posteo.de>2023-10-15 10:55:39 +0200
committerLibravatar Fabian Kirchner <kirchner@posteo.de>2023-10-15 10:55:39 +0200
commite2f4e9fc842fe41cdaa3cf53375ab59b6c10b80d (patch)
tree03c00784b4f3a89e7ad08ea9947a29be31ff4263 /app
parent225c2ff039137fcd3aa82343367f76d9d49f254c (diff)
minor issue adjustments
Diffstat (limited to 'app')
-rw-r--r--app/Main.hs8
1 files changed, 4 insertions, 4 deletions
diff --git a/app/Main.hs b/app/Main.hs
index b535335..1540178 100644
--- a/app/Main.hs
+++ b/app/Main.hs
@@ -6,7 +6,7 @@
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE PartialTypeSignatures #-}
--- TODO Edit issues.
+-- TODO Edit issues from command line
--
-- I would like to edit issues from the command line.
--
@@ -17,14 +17,14 @@
-- I am personally anticipating that this is used most frequently in response to `anissue show @id`. So, maybe `anissue show @id --edit` should be a synonym?
-- Rationale: the latter is typing `<UP> --edit<CR>`. The former, after show, is typing `<UP><ESC>^wcwedit<CR>`, the former obviously being more palatable.
--- TODO Tag improvements (OR-filtering).
+-- TODO Tag improvements (OR-filtering)
--
-- Currently it is not possible to filter for an issue satisfying one filter or another. We could add the following syntax allowing it:
--
-- `--filter '(@assigned aforemny) OR (@due 2023-10-4)'`
-- @topic tags
--- TODO Tag improvements (globbing).
+-- TODO Tag improvements (globbing)
--
-- I would like to filter `--filter '@assigned *@posteo.de'`.
-- @topic tags
@@ -42,7 +42,7 @@
-- Issues having a `@priority` tag whose value is not an integer should be regarded not matching the filter.
-- @topic tags
--- TODO Tag improvements (dates).
+-- TODO Tag improvements (dates)
--
-- I would like anissue to support due dates when filtering. Let's for a first implementation add the following filter syntax:
--