bboard hyperpithole gate
(DIR) Menu
(DIR) Section <GOPHER>
(DIR) Forward
(DIR) Backward
Thread[.post]: 4.12
TACKER: peteyboy (Pete)
SUBJECT: .. Editing for readability
DATE: 01-Jul-26 18:40:44
HOST: ryo
sjlawson funny, I've been running into the same issue. Specifically, if you
edit files after they've been fold(1)ed, you can end up with a weird
stairstep effect which you don't want.
'fmt' solves this by re-linking the line below if it fits.
However, I found in my use case is that 'fmt' is file-wide and so it will
slurp up say, bullets, and other text you DON'T want folded like that.
This makes things like:
* one
* two
* three
suddenly
* one * two * three
:<
I am trying to make text files to be served by the nex:// protocol
[ SCROLL (F)ORWARD, (B)ACKWARD - (Q)UIT ] FORWARD
This makes things like:
* one
* two
* three
suddenly
* one * two * three
:<
I am trying to make text files to be served by the nex:// protocol
(nightfall express protocol, see http://nightfall.city for details), and
struggling with how text files look on GUI browsers, specifically Lagrange.
My current solution, as a 'nano' user, is I can open files with the --fill
# flag-- I am using 'fill 50'--and then manually ctl-j to justify
paragraphs that I edit. This saves my bullet points and weird text
formatting I want to preserve.
(I like nex in that its basically the same as gopher but with a sane index
syntax replacing gophermap menu syntax; it doesn't do everything that
gopher menus do, but I am just serving up text content)
(I probably should just give in and use gemini, but I'm attracted to how
simple nex is, I wrote my own client and use zilog's server made with socat
and shell)
<GOPHER.4.12/19>(75)[ <ENTER> follow thread, (R)EPLY, (F)LAG or (Q)UIT ]