Justin SearlsHow do people write prose in code editors, with vim movements, and insist on softwrap? Drives me up a fucking wall not being able to navigate up and down reliably with j and k. #TeamHardWrap80cs
samir, actually the xkcd top hat guy@searls I use `nnoremap j gj` (and similar for “k”).
https://stackoverflow.com/questions/9713967/how-can-i-intuitively-move-cursor-in-vimnot-by-line
jasonkarns@searls couldn’t tell you. I’m also #teamhardwrap
Neal Lindsay@jasonkarns @searls When I'm in Vim I write my prose in Markdown with one sentence per line. Soft wrap is on, but almost never causes a wrap. This keeps me more aware of sentence length.
Git commits get hard wrapped though.
Todd A. Jacobs | Rubyist@searls I wrap at 56-120 chars per line depending on purpose. For #prosewriting, though, I've seen a lot of folks advocate for #softwrapping long lines but #hardwrapping at sentence boundaries.
The argument is similar to trailing commas in #RubyLang Hash or Array elements: it makes rearranging sentences easier, and probably isn't a huge navigation hardship for short, declarative sentences.
That's never felt natural to me though. So, #TeamHardWrap for me too!
@todd_a_jacobs @searls another scenario where editors should work in syntax, but save/commit AST.
(Presume AST for prose is 1 sentence/line)
Noel Rappin@searls I don't write prose in a code editor, the affordances are wrong, I write prose in ia or Ulysses that are designed for writing prose.
I also don't like writing prose in a monospaced font.