Version bump.

[elpher.git] / ISSUES.org

diff --git a/ISSUES.org b/ISSUES.org
index 5f45081..3ebb22d 100644 (file)
--- a/ISSUES.org
+++ b/ISSUES.org
@@ -41,11 +41,10 @@ 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.
 
 The last few will be made infinitely easier if we factor the
 gopher "getter" code differently.
 

-

 ** OPEN Add history browsing
 ** OPEN Add history browsing

-
+   

 * Bugs
 * Bugs

-
+  

 * Completed improvements
   
 ** CLOSED Turn on lexical scoping
 * Completed improvements
   
 ** CLOSED Turn on lexical scoping


@@ -115,6 +114,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
 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
   
 
 * Closed issues
   


@@ -146,3 +162,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.
 
 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.