summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorPjotr Prins2022-02-02 05:02:39 -0600
committerGitHub2022-02-02 05:02:39 -0600
commit0dfd2f44154b7676daaefaaa032da0dd835d8ccc (patch)
treed2b6d1293224f16e29f02049b9e053be62511340 /issues
parenta42c4e123c8f94c05443789af0296f4c1c6fa636 (diff)
downloadgn-gemtext-0dfd2f44154b7676daaefaaa032da0dd835d8ccc.tar.gz
Update recent-first-sort.gmi
Add note on sorting gemtext with gn-bug
Diffstat (limited to 'issues')
-rw-r--r--issues/gnbug/recent-first-sort.gmi4
1 files changed, 4 insertions, 0 deletions
diff --git a/issues/gnbug/recent-first-sort.gmi b/issues/gnbug/recent-first-sort.gmi
index bdd7df4..229554a 100644
--- a/issues/gnbug/recent-first-sort.gmi
+++ b/issues/gnbug/recent-first-sort.gmi
@@ -3,3 +3,7 @@
Add a command-line option --sort=(newest-first|oldest-first) to gnbug that determines the order the issues are listed. oldest-first is useful for command-line usage where you don't want to scroll up to see the most recent issue. newest-first is useful when generating gemtext/web pages where you don't want to scroll down to see the most recent issue.
* assigned: bonfacem
+
+# INFO
+
+It seems to me that the default is newest-first for gemtext and oldest-first for terminal output. No need for a switch.