Added history bug to issues document.

[elpher.git] / ISSUES.org

diff --git a/ISSUES.org b/ISSUES.org
index 5f45081..650b1e3 100644 (file)
--- a/ISSUES.org
+++ b/ISSUES.org
@@ -41,11 +41,26 @@ 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.
 
-
 ** OPEN Add history browsing
-
+   
 * Bugs
+  
+** History inconsistency when restarting elpher <2020-05-26 Tue>
 
+To reproduce:
+1. open elpher and follow a few links until you're a handful of links below
+   the start page.
+2. kill the elpher buffer with C-x k
+3. Open elpher again, which will show the start page.
+4. Press 'u' to go up.  Elpher wiill respond stating that there is no previous page.
+5. Press 'u' again. Elpher will then jump to the page that was open when
+   the buffer was originally killed.
+
+Expected behaviour: elpher should be once again at the bottom of the history
+stack and should not remember the previous history.
+
+Observed behaviour: elpher _does_ remember the previous history.
+  
 * Completed improvements
   
 ** CLOSED Turn on lexical scoping
@@ -115,6 +130,23 @@ Actually, this command can be useful to correct rendering issues that
 occasionally pop up in termal windows.  Lets leave it for now.
 
 ** CLOSED Implement Finger support
+   
+** CLOSED Improve download performance
+   This is actually easy to fix - the major problem at the moment is
+   the braindead way the incrementally-retrieved data is recorded:
+   (setq result-string (concat result-string next-bit)).
+   This is O(N^2).  Yuck!
+   
+   Okay, replacing this really does improve things.  Large gemini
+   downloads now seem occur at rates I'd expect.
+   
+** CLOSED Download/rendering progress feedback
+   Particularly for large files or complicated pages, elpher can
+   take a few seconds or more to generate a response.  Thhis is
+   frustrating for users, who are left staring at a blinking
+   cursor.
+
+   A small amount of feedback could help with this.
 
 * Closed issues
   
@@ -146,3 +178,11 @@ I suspect the problem is in either ~elpher-visit-node~ or
 Follow-up: this has been fixed by the new stack-based history system
 in 2.5.
 
+
+** CLOSED Redirects do not rewrite current address
+
+This is a bug, as gemini://blah.com/hi may get redirected
+to gemini://blah.com/hi/, at which point link lines
+of the form "=> there" should be interpreted as pointing
+at gemini://blah.com/hi/there, while currently they are
+interpreted as pointing at gemini://blah.com/there.