Updated link to gemini gopher page in README.

[elpher.git] / ISSUES.org

diff --git a/ISSUES.org b/ISSUES.org
index 68a8a00..2b637c0 100644 (file)
--- a/ISSUES.org
+++ b/ISSUES.org
@@ -3,11 +3,17 @@
 
 * Enhancements
 
-** OPEN Allow multiple elpher buffers
+** OPEN Allow multiple elpher buffers [33%]
 
    Shouldn't be too hard, just need elpher-current-node to be
 buffer-local and allow various buffer-switching procedures to
 do something sensible.
+
+Here are the things that need to be implemented before
+this can happen:
+- [X] shift history out of node tree and into separate stack
+- [ ] make history stack variables buffer-local
+- [ ] have elpher-with-clean-buffer select appropriate buffer 
    
 ** OPEN Remove "redraw" command
 This is only necessary for returning from displaying the raw
@@ -42,16 +48,6 @@ gopher "getter" code differently.
 
 * Bugs
 
-** OPEN History loops <2019-11-08 Fri>
-
-Occasionally elpher gets stuck in a "history loop" where a
-node is its own grandparent.  Obviously this sucks, as history
-is elpher's main mechanism for making gopherspace exploration
-painless.
-
-I suspect the problem is in either ~elpher-visit-node~ or
-~elpher-visit-parent~.
-
 * Completed improvements
   
 ** CLOSED Turn on lexical scoping
@@ -113,7 +109,7 @@ This also means that non-gopher URLs will be explicitly represented
 as such: no more abusing the "h" type for these.
 
 * Closed issues
-
+  
 ** CLOSED Org mode faces are not present in recent emacs versions
 Even 26.1 doesn't seem to have these.  This means that, for many
 users, elpher doesn't show any difference between any of the
@@ -128,3 +124,17 @@ Update: changed all default faces to inherit from font-lock and basic faces.
    
 Need a way to allow people to rescue their old bookmark files
 following this update.
+
+** CLOSED History loops <2019-11-08 Fri>
+
+Occasionally elpher gets stuck in a "history loop" where a
+node is its own grandparent.  Obviously this sucks, as history
+is elpher's main mechanism for making gopherspace exploration
+painless.
+
+I suspect the problem is in either ~elpher-visit-node~ or
+~elpher-visit-parent~.
+
+Follow-up: this has been fixed by the new stack-based history system
+in 2.5.
+