aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLibravatar Alexander Foremny <aforemny@posteo.de>2023-10-09 13:50:04 +0200
committerLibravatar Alexander Foremny <aforemny@posteo.de>2023-10-09 13:52:47 +0200
commit688eed82928f5106d196df20b9fda468ee4b2038 (patch)
tree1854892d8d715baa66844b518cebd727f41a568c
parentb87674a9ad1aece973da49197182a08ac65cd2df (diff)
add 'edit issues' issue
-rw-r--r--app/Main.hs11
1 files changed, 11 insertions, 0 deletions
diff --git a/app/Main.hs b/app/Main.hs
index 771fd68..402d153 100644
--- a/app/Main.hs
+++ b/app/Main.hs
@@ -6,6 +6,17 @@
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE PartialTypeSignatures #-}
+-- TODO Edit issues.
+--
+-- I would like to edit issues from the command line.
+--
+-- `anissue edit @id` should bring up the issue inside `$EDITOR`, updating the issue with any changes made within `$EDITOR`.
+--
+-- Comment markers should be stripped, and the file format should be Markdown. Issue markers could be stripped.
+--
+-- 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).
--
-- Currently it is not possible to filter for an issue satisfying one filter or another. We could add the following syntax allowing it: