RFC: Gemini link numbering #133
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#133
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently the gemini module does not do what gopher does: provide a left hand gutter for link numbers. Should we add a gutter on the left hand side for gemini? It is a minor code update to do so... but I am not sure what the merits and flaws of doing so are.
I am leaning toward adding this in. If only for consistency with how gopher is displayed in Bombadillo.
It has the additional bonus that any link lines that are part of ascii art (not recommended, but definitely possible) will align properly with the art the comes before and/or after them. I'll work something up and get a PR together.
So, this has proved to be trickier than initially thought. I'm going to keep playing with it, but wanted to update that I had been working on it.
It has taken forever (sorry!) but I think I have a working version of the numbering gutter working for gemini. Any that want to check it out can see the code in PR #188 . The branch is listed and can be pulled. If this seems good we'll move it into a release branch and close this issue. Otherwise I'll comment here with an update.
This was merged into a release branch with #188
Gopher's link numbering was also modified as a part of that PR. I will keep this open until the release is done.