- [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
-server response. If I can provide a better way of doing that
-then we can get rid of redraw entirely.
** OPEN Replace support for user-specified starting pages
This used to be available, but was removed during a refactor.
The last few will be made infinitely easier if we factor the
gopher "getter" code differently.
-* Bugs
+** OPEN Add history browsing
+
+** OPEN 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.
+
+* Bugs
+
* Completed improvements
** CLOSED Turn on lexical scoping
This also means that non-gopher URLs will be explicitly represented
as such: no more abusing the "h" type for these.
+** INVALID Remove "redraw" command
+This is only necessary for returning from displaying the raw
+server response. If I can provide a better way of doing that
+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 issues
** CLOSED Org mode faces are not present in recent emacs versions
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.