summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorArun Isaac2022-07-06 16:28:32 +0530
committerArun Isaac2022-07-06 16:28:32 +0530
commit35a6deec5c455a9d58db49f5ce8cf2150a202939 (patch)
tree910a9d042fe38f6e5bbc96e54728158cf1b46e14 /issues
parent360e4a0e496cf541fdf65aa12271f0fa4fcf3f5e (diff)
downloadgn-gemtext-35a6deec5c455a9d58db49f5ce8cf2150a202939.tar.gz
Close tissue linter issue.
Diffstat (limited to 'issues')
-rw-r--r--issues/gnbug/add-linter.gmi6
1 files changed, 6 insertions, 0 deletions
diff --git a/issues/gnbug/add-linter.gmi b/issues/gnbug/add-linter.gmi
index 3d2d5bd..355475a 100644
--- a/issues/gnbug/add-linter.gmi
+++ b/issues/gnbug/add-linter.gmi
@@ -47,3 +47,9 @@ and each instance of the issue tracker can have some config file that defines, a
The tags could be parsed into a hashmap or an associative list, or any other similarly useful datatype, from which the values would be read for display.
Tissue could determine what the context is (CLI, web, etc) and using the config, figure out what tags to display and how
+
+## Closing
+
+We don't have tag restrictions for now. And, tag restrictions probably go against the "unstructured and unrestrictive" aesthetic that we are aiming for. In the web UI, we can color tags using the provided CSS classes. In the CLI, we have a fixed blue color for all tags. Short of supporting full-fledged CLI color theming, it might be counterproductive to allow changing colors of specific tags in the CLI. If filtering based on tags is the objective, we now also have a powerful xapian-powered search interface.
+
+* closed