tilde.club/~brennen/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

73 lines
2.5 KiB

9 years ago
  1. On Fri, Jan 30, 2015 at 12:57 PM, Eric Weir wrote:
  2. > Wondering if there are any poets here who use vim in writing
  3. > poetry, either in the messy creative phase or the later
  4. > refining, polishing, and editing phase. If so, I’d be
  5. > interested in knowing how you use vim, how you find vim
  6. > helpful, and whether there are any plugins that you have found
  7. > especially helpful.
  8. I use vim for most of what I don't write inside a browser, which
  9. includes a lot of poetry and prose.
  10. I'm not sure if I draw much of a distinction between the things
  11. that make a good code editor and the things that make a good
  12. literary text editor. I can certainly imagine that distinction,
  13. but I think if you like plain text, filter scripts, the
  14. coreutils, renderable markup languages, that sort of thing, then
  15. it all kind of fits together.
  16. I'm slowly writing a book partly about using the GNU/Linux CLI
  17. for literary things:
  18. https://p1k3.com/userland-book/
  19. ...which doesn't (yet, anyway) touch on vim, but it's sort of the
  20. environment I have in mind.
  21. As to the editor specifically, I do a lot of pretty intensive
  22. rewriting, rearranging lines or stanzas, replacing words, and
  23. experimenting with line breaks and spacing. Vim's pretty good at
  24. quickly slicing and dicing text.
  25. I use this binding a lot for chopping lines up:
  26. " split lines under the cursor (modeled on, maybe, emacs?)
  27. map K i<CR><Esc>g;
  28. As far as plugins go, NERD tree makes the whole editor a lot more
  29. useful for working with a collection of files, and I tend to
  30. organize projects as flatfiles in a directory, or blog entries in
  31. a tree of directories named after dates.
  32. Lastly, I have some simple tools for producing markup from a
  33. source format. So, for example, the last poem I wrote looks like
  34. this in source:
  35. <h1>monday, january 5</h1>
  36. <freeverse>
  37. driving down 36 to see you
  38. i grasp at the scene around me
  39. trying to fix in mind for you
  40. some list or hierarchy
  41. of attributes and aspects:
  42. snow on the hills
  43. snow on the plains
  44. the moon on the snow
  45. sundown on the clouds
  46. the haze over the city lights
  47. electricity vivid and gleaming
  48. within the field of some
  49. greater radiance
  50. </freeverse>
  51. ...where the stuff inside <freeverse> gets translated to regular
  52. HTML with linebreaks in the right places. It's a small thing,
  53. but it's a lot easier to stay in the flow of writing without
  54. having to worry about markup boilerplate. For print output in
  55. the past I've switched this up to generate LaTeX directly, but I
  56. think next time I produce something in book form I'll see what I
  57. can get done with Pandoc.
  58. -- bpb