vim-sensible VS goyo.vim

That’s a good question. The built in tutorial is actually really good, you can launch it with “vimtutor” on the command line. It doesn’t give you everything, but its instructions and text to try things out on in the editor itself, which I find a good way to learn. It isn’t particularly programming focused either.

For getting used to the motions especially https://vim-adventures.com can be a fun way, in its game format.

For getting started I’d say don’t worry about plugins much, but get https://github.com/tpope/vim-sensible at least so the defaults meant for vi don’t get in the way. The only other thing you might want is a format syntax if your preferred note syntax isn’t highlighted well by default or something. Polyglot can be good to stave that off but really I’d say learn on a really lean config, and get used to using :help or similar. It’s the best way to learn the parts that work everywhere.

it's modified from tpope's https://github.com/tpope/vim-sensible, and https://github.com/mhinz/vim-galore#tips-1.

I didn't realise vim Vs vi purist was a thing.

I'm aware that for a while vim has had some backwards compatibility setting that people recommended turning off to get more modern defaults.

And that Tim Pope had a plugin that took you one step beyond that:

https://github.com/tpope/vim-sensible

> Think of sensible.vim as one step above 'nocompatible' mode: a universal set of defaults that (hopefully) everyone can agree on.

And that neovim took the opportunity to make an updated set of defaults:

https://neovim.io/doc/user/vim_diff.html#nvim-defaults

tpope/vim-sensible, because the Vim defaults aren't for everyone.

A while back I did a public Neovim options survey (here are the results). One of the goals was to gather a commonly used option values to create a "crowd-sourced" moderate version of tpope/vim-sensible. Well, this is it.

opps.. forgot to mention timpopes : https://github.com/tpope/vim-sensible settings :D

You don’t want any modern conveniences? Not even stuff from here[0]?

[0]: https://github.com/tpope/vim-sensible/blob/master/plugin/sen...

If you use vim-sensible, which you should, you can reset the highlight with ctrl+l.

Check out sensible.vim for lots of settings you might want to turn on.

What I plan to do with results: - The summary of results will be released in some way, shape, or form after survey is closed (at least two weeks from now when there is a 24 hours without new entries). It will be announced in this sub. - Possibly use the most commonly set non-default settings to power a Neovim variant, crowd-sourced version of tpope/vim-sensible.

I wrote a manuscript in vim a couple Novembers ago, for NaNoWrimo. I used a couple plugins, primarily Goyo [1] to add some margins, but otherwise, yeah, plain vim.

I don't think it was really any more productive than my current workflow in Obsidian. Vim keybindings are more useful for editing than for writing (and for editing code in particular, where the changes you're making are much more structured). Also, while the extra features afforded by Obsidian don't really make a difference during the writing process, I find they're really useful for outlines and other preliminary work, which is something of a point against a vim-only workflow unless you want to use vimwiki [2] or something.

Granted, Obsidian is still a markdown-based tool, so there's still some level of minimalism going on there, but by that point we're really discussing markup vs word processors, which is its own conversation—and to my mind, a much more important one. I much prefer working in markup than in a rich text editor, because plain text is easy to edit and process through the terminal, and because it lets me separate style choices from content.

I find that the markdown live preview that editors like Obsidian and Typora provide (and which vim doesn't) is a really nice compromise between a slick composing experience and the technical affordances of markup. Between that and Obsidian's hypertext features, I think I'll stick with Obsidian for the foreseeable future.

[1]: https://github.com/junegunn/goyo.vim

[2]: https://vimwiki.github.io/

Maybe https://github.com/junegunn/goyo.vim could be useful then.

Goyo is a distraction free plugin for vim/NeoVim. https://github.com/junegunn/goyo.vim. Typically used for people wanting to write inside of NeoVim. There isn’t a real purpose for me to use it other than I like the aesthetic looks. Thanks for replying!

Maybe not of use, but what about just one of your editors + the terminal? Using vim with the goyo extension similarly without the overlay. I write my notes with markdown.

I haven't maintained a Vim config in a few years now (more of an Emacs man now), but I do remember using Goyo in college. Looking back at it, I think it might scratch your itch as far as Vim plugins go, it even allows you to resize the area on the fly.

https://github.com/junegunn/goyo.vim

I went from https://github.com/junegunn/goyo.vim to https://github.com/folke/zen-mode.nvim and now this

Can't see https://github.com/junegunn/goyo.vim mentioned anywhere in this thread.

This feels real similar in concept to limelight and goyo. Nice! 👍🏻