Support reflowed text for gemini #103
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#103
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?
Blocked until consensus is reached by the gemini working group re: how to handle this
At present we are wrapping gemini text. The spec is in flux currently but looks to be rallying around reflowing text and adding syntax to have unflowed lines (whose behavior is still up in the air).
This should NOT get solved until things get settled on. However, I wanted to open this issue in preparation as I had some ideas about how to handle it without disrupting other content:
client.go
as the raw result. This will allow our regular wrapping to function.Doing things that way will make it so that we do not have to alter any structs or change how wrapping works. It should all just get handled in the gemini module and the result should be wrapable.
Are unflowed lines the equivalent of
Yes :) Right now the default is unflowed (but wrapped). There is no consensus currently regarding how to mark flowed vs unflowed lines nor which should be the default for the protocol. The web flows by default and gopher does not flow by default. I have argued in favor of unflowed by default, but with the ability to do something like this:
Note: the
.FLOW
&.UNFLOW
is for communicating the conceptual purpose and not a recommendation for what marker to use.We'll see what people think and what gets adopted.
The gemini spec has dropped the proposal for reflowed text in favor of wrapped text and an instruction to just use long lines if you want text treated as a flow group.
This story is being closed in recognition of that.