X-Git-Url: https://thelambdalab.xyz/gitweb/index.cgi?p=elpher.git;a=blobdiff_plain;f=ISSUES.org;h=3ebb22dfd586acf03d34c4cb5f5d12bfc630547f;hp=462478632c4e2bdc72efce37a66cdb27ca73ed72;hb=a4c54eb1a28d27902f9d99ee961545dbc68e2965;hpb=a29c98cf4d17b09060d923f2e9e2510563027c7a

diff --git a/ISSUES.org b/ISSUES.org
index 4624786..3ebb22d 100644
--- a/ISSUES.org
+++ b/ISSUES.org
@@ -41,12 +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.
 
-** OPEN Implement Finger support
-
 ** OPEN Add history browsing
-
+   
 * Bugs
-
+  
 * Completed improvements
   
 ** CLOSED Turn on lexical scoping
@@ -115,6 +113,25 @@ then we can get rid of redraw entirely.
 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
   
 ** CLOSED Org mode faces are not present in recent emacs versions
@@ -145,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.
 
+
+** 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.