minpac VS goyo.vim

PS: As you get proficient with Vim, you'll probably want to extend it with plugins, so you should look into package managers when you'll be a decent Vimmer; I use minpac but there are plenty of others. But for now, focus on learning Vim; you don't want to install a plugin to do something that Vim can do out of the box.

It’s been such a long time since I’ve used it. Don’t know how it compares, but minpac is super simple and uses vim’s native package system (the latter can also be used on its own) https://github.com/k-takata/minpac

There are package managers that are built on top of Vim's package system, the one I use is minpac which has a list of other plugin managers using Vim's package system in its README.

Options: - packloadall command family and maybe git submodules - minpac which is a thin utility around the above - vim-plug - old but still popular for it does the job - packer.nvim is a popular choice for lua configs, never got to using it myself - paq-nvim is another often mentioned lua solution - dozens of other solutions

I'm not sure about vim-plug, but I use minpac which does use vim's native plugin location. The selling point is that the installs and updates are managed via the plugin's commands. As part of my dotfiles, the install command is run.

I went back to using minpac. It uses vim's package feature, but doesn't have to compile anything. I like that I don't have to load it unless I download something.

minpac: Plugin manager.

vim.opt.runtimepath:remove(vim.fn.expand('~/.config/nvim')) vim.opt.packpath:remove(vim.fn.expand('~/.local/share/nvim/site')) vim.opt.runtimepath:append(vim.fn.expand('/tmp/nvim-config')) vim.opt.packpath:append(vim.fn.expand('/tmp/nvim-config')) -- Install minpac local install_path = '/tmp/nvim-config/pack/minpac/opt/minpac' local install_plugins = false if vim.fn.empty(vim.fn.glob(install_path)) > 0 then vim.cmd('!git clone https://github.com/k-takata/minpac ' .. install_path) install_plugins = true end function PackInit() vim.cmd('packadd minpac') vim.call('minpac#init', {dir = '/tmp/nvim-config'}) local Plug = vim.fn['minpac#add'] -- Plugin manager Plug('k-takata/minpac', {type = 'opt'}) -- Colorscheme Plug 'mjlbach/onedark.nvim' -- LSP Support Plug 'neovim/nvim-lspconfig' Plug 'williamboman/nvim-lsp-installer' -- Autocompletion Plug 'hrsh7th/nvim-cmp' Plug 'hrsh7th/cmp-buffer' Plug 'hrsh7th/cmp-path' Plug 'saadparwaiz1/cmp_luasnip' Plug 'hrsh7th/cmp-nvim-lsp' Plug 'hrsh7th/cmp-nvim-lua' -- Snippets Plug 'L3MON4D3/LuaSnip' Plug 'rafamadriz/friendly-snippets' -- lsp stuff Plug 'VonHeikemen/lsp-zero.nvim' end pcall(vim.cmd, 'colorscheme onedark') vim.cmd [[ command! PackUpdate lua PackInit(); vim.call('minpac#update') command! PackClean lua PackInit(); vim.call('minpac#clean') command! PackStatus lua PackInit(); vim.call('minpac#status') ]] if install_plugins then vim.cmd('PackUpdate') end local ok, lsp = pcall(require, 'lsp-zero') if ok then lsp.preset('recommended') lsp.setup() end

k-takata/minpac, the plugin manager that stays out my way. It can live as an optional plugin, it's not loaded unless I update or install something.

I like minpac, it's a good plugin manager. It does what I want. Exactly what I want. Problem is it's written in vimscript, which is something I'm trying to avoid right now. I have no good reason to avoid vimscript... I just don't want to write any. By now I have read enough about lua and the neovim api to create a wrapper that would make minpac a little bit more "lua friendly".

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! 👍🏻