From: plugd <plugd@thelambdalab.xyz>
Date: Fri, 23 Jul 2021 08:12:52 +0000 (+0200)
Subject: Updated issues file.
X-Git-Tag: v3.0.0~12
X-Git-Url: https://thelambdalab.xyz/gitweb/index.cgi?a=commitdiff_plain;h=68f5ca8daafe10f14c241e586617e2f669cf9310;p=elpher.git

Updated issues file.
---

diff --git a/ISSUES.org b/ISSUES.org
index 1c8088f..58fbe01 100644
--- a/ISSUES.org
+++ b/ISSUES.org
@@ -4,6 +4,16 @@
    
 * Open Bugs
 
+** OPEN Sanitize certificate names
+   :LOGBOOK:
+   - State "OPEN"       from              [2020-06-22 Mon 10:32]
+   :END:
+   
+Currently things will break in undefined ways if a name is specified
+that contains path separators and probably other characters that I
+haven't thought of.  This is dangerously unacceptable and needs to be
+fixed right away.
+
 * Closed Bugs
   
 ** CLOSED Org mode faces are not present in recent emacs versions
@@ -87,46 +97,7 @@ this can happen:
 
 ** OPEN Replace support for user-specified starting pages
 This used to be available, but was removed during a refactor.
-
-** OPEN Allow for grouping of bookmarks
-To support this I'd like to add a bookmark page specific
-set of keybindings.  Currently all bindings available on
-the bookmark page are available everywhere else.  But
-expanding and collapsing bookmark groups sounds like it
-might need more specific bindings.
-
-*** Priority bump <2020-05-31 Sun>
-
-As bookmark lists grow, some sort of grouping is becoming more and more
-important.  Furthermore, with this in place it would become feasible
-(and I really suspect almost trivial) to implement an update-checking
-system for chosen groups of bookmarks.
-
-For instance, we could prefetch content for each of the addresses within
-a chosen group, indicating which had been changed since the last fetch.
-(We could just store hashes of earlier content to detect changes.)
-
-The difficult thing to decide is how the UI for the new bookmark page
-will work.  It already has its own renderer, and we could easily stop
-using the gopher directory line renderer in favour of something more
-amenable to displaying the group information.  Thus we're very free to
-do whatever we like once we also have a special key map in place as well.
-
-I guess I need to look into what native widgets Emacs has for displaying
-collapsable hierarchies.
-
-** OPEN Add history browsing
-   
-** OPEN Sanitize certificate names
-   :LOGBOOK:
-   - State "OPEN"       from              [2020-06-22 Mon 10:32]
-   :END:
    
-Currently things will break in undefined ways if a name is specified
-that contains path separators and probably other characters that I
-haven't thought of.  This is dangerously unacceptable and needs to be
-fixed right away.
-
 ** OPEN Make installing existing certificates easier
    :LOGBOOK:
    - State "OPEN"       from "CLOSED"     [2020-06-22 Mon 10:34]
@@ -242,3 +213,41 @@ Here is the checklist of features required before release:
   
 The last few will be made infinitely easier if we factor the
 gopher "getter" code differently.
+
+
+** INVALID Allow for grouping of bookmarks
+:LOGBOOK:
+- State "INVALID"    from              [2021-07-23 Fri 10:10] \\
+  Since switching to Emacs native bookmarks, this is no longer our concern.
+:END:
+To support this I'd like to add a bookmark page specific
+set of keybindings.  Currently all bindings available on
+the bookmark page are available everywhere else.  But
+expanding and collapsing bookmark groups sounds like it
+might need more specific bindings.
+
+*** Priority bump <2020-05-31 Sun>
+
+As bookmark lists grow, some sort of grouping is becoming more and more
+important.  Furthermore, with this in place it would become feasible
+(and I really suspect almost trivial) to implement an update-checking
+system for chosen groups of bookmarks.
+
+For instance, we could prefetch content for each of the addresses within
+a chosen group, indicating which had been changed since the last fetch.
+(We could just store hashes of earlier content to detect changes.)
+
+The difficult thing to decide is how the UI for the new bookmark page
+will work.  It already has its own renderer, and we could easily stop
+using the gopher directory line renderer in favour of something more
+amenable to displaying the group information.  Thus we're very free to
+do whatever we like once we also have a special key map in place as well.
+
+I guess I need to look into what native widgets Emacs has for displaying
+collapsable hierarchies.
+
+
+** CLOSED Add history browsing
+:LOGBOOK:
+- State "CLOSED"     from "OPEN"       [2021-07-23 Fri 10:09]
+:END: