goyo.vim
nvim-treesitter
goyo.vim | nvim-treesitter | |
---|---|---|
41 | 300 | |
4,435 | 9,537 | |
- | 3.3% | |
0.9 | 9.9 | |
about 1 year ago | 4 days ago | |
Vim Script | Scheme | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
goyo.vim
- Ensō: write now, edit later
-
Ask HN: Did anyone write a book in Nano?
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/
-
is it possible to read books in vim?
Maybe https://github.com/junegunn/goyo.vim could be useful then.
-
Help with plugin: Goyo
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!
- [Vim] Vous cherchez un moyen d'ajouter un rembourrage de tout le côté de la fenêtre.
-
An application that serves as a notepad that overlays the screen?
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.
-
SQLite WASM in the Browser Backed by the Origin Private File System
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
-
UPDATE: no-neck-pain.nvim - Dead simple plugin to center the currently focused buffer to the middle of the screen.
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.
-
BlindVim, my first simple plugin.
This feels real similar in concept to limelight and goyo. Nice! 👍🏻
nvim-treesitter
-
JetBrains' unremovable AI assistant meets irresistible outcry
I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.
These two plugins are the bare minimum in my view.
https://github.com/nvim-treesitter/nvim-treesitter
Treesitter gives you much better syntax highlighting based on a parser for a given language.
https://github.com/neovim/nvim-lspconfig
This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:
https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...
For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.
pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server
Best of luck! Happy hacking.
-
Help needed with Treesitter sql injection
It was changed in https://github.com/nvim-treesitter/nvim-treesitter/commit/78b54eb
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
- Problem with highlighting when attempting to create own treesitter parser
-
neorg problem, all other plugins deactivate when added to init.lua
vim.opt.rtp:prepend(lazypath) require('lazy').setup({ { "nvim-neorg/neorg", build = ":Neorg sync-parsers", opts = { load = { ["core.defaults"] = {}, -- Loads default behaviour ["core.concealer"] = {}, -- Adds pretty icons to your documents ["core.dirman"] = { -- Manages Neorg workspaces config = { workspaces = { notes = "~/notes", }, defaultworkspace = "notes", }, }, }, }, dependencies = { { "nvim-lua/plenary.nvim", }, { -- YOU ALMOST CERTAINLY WANT A MORE ROBUST nvim-treesitter SETUP -- see https://github.com/nvim-treesitter/nvim-treesitter "nvim-treesitter/nvim-treesitter", opts = { auto_install = true, highlight = { enable = true, additional_vim_regex_highlighting = false, }, }, config = function(,opts) require('nvim-treesitter.configs').setup(opts) end }, { "folke/tokyonight.nvim", config=function(,) vim.cmd.colorscheme "tokyonight-storm" end,}, }, }, }) require 'plugins' ```
-
Getting Treesitter to work for Windows 10
Change the compiler to use 'llvm' and install visual studio build tools command line stuff - at least that is what worked for me without problems. If you are using c++ then I would assume you have visual studio installed already. If you need more info follow the treesitter windows support
-
Just come back up out of the rabbit hole - TS unsets syntax variable by design!
After a lot of time spent yesterday I took a fresh look today and then thought to myself - what if this is what TS does by design? A few clicks later and I found this https://github.com/nvim-treesitter/nvim-treesitter/issues/1327
- What is this color scheme
-
nvim-treesitter erroring on Windows 11 Pro
I've followed the official guide for nvim-treesitter support on Windows, but I'm having problems making it work. I keep getting a compilation error for any parser I try to install using TSInstall. If instead I use TSInstallSync I don't get errors but the parser is not correctly installed. My setup uses lazyvim and I installed LLVM using winget to have a C compiler.
-
Neovim can't find C compiler
I have read that gcc in windows doesn't always provide the necessary support for treesitter. I have seen ppl prefer clang over gcc in Windows. Please see also Windows support in treesitter's repo. Unfortunately I cannot help further as I don't use Windows for coding, but hope you can deduce something to solve your problem from the above link (if you haven't already read through it).
What are some alternatives?
zen-mode.nvim - 🧘 Distraction-free coding for Neovim
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vim-pencil - Rethinking Vim as a tool for writing
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-easy-align - :sunflower: A Vim alignment plugin
vim-polyglot - A solid language pack for Vim.
vim-startify - :link: The fancy start screen for Vim.
vim-python-pep8-indent - A nicer Python indentation style for vim.
indent-blankline.nvim - Indent guides for Neovim
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
nvim-lua-setup
tree-sitter - An incremental parsing system for programming tools