goyo.vim | fs | |
---|---|---|
41 | 7 | |
4,435 | 208 | |
- | 3.8% | |
0.9 | 6.8 | |
about 1 year ago | 3 months ago | |
Vim Script | HTML | |
MIT License | GNU General Public License v3.0 or later |
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! 👍🏻
fs
-
persistent storage API on Firefox temporary extension
You can use File System Standard https://fs.spec.whatwg.org/ to write data for that origin (Firefox doesn't implement File System Access API, nonetheless a File object can still be written to local disk using File API).
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
Both Firefox and Chromium (Chrome) have implemented WHATWG File System Standard.
-
SQLite WASM in the Browser Backed by the Origin Private File System
Can you just slow down for a moment and focus on what you said?
> We're literally in the discussion about File System API that is:
> - not on any standards track
As others have pointed out the standard is here:
https://fs.spec.whatwg.org/
> - considered harmful by other browser vendors
It is literally being drafted in conjunction by all the major browsers.
> - shipped by default in Chrome
So what? I for one am thankful that Chromium enables features earlier than other browsers. If you don't want the Chromium implementation then don't use it.
-
Show HN: I built a WASI playground for running CLI binaries in the browser
Score another point for memfs, the in-memory node.js fe impl.
WHATWG recently took up File System Access spec as their FS spec. It both looks semi promising, but they seem to only care about & are only building specs for specifically emscripten wasm users. Only sync apis, only usable from dedicated workers... there's some hopes for more latter but feels super weird to see the web finally get fs access & have it be fast... but for it to be extremely odd shaped hand tailored to a very narrow class of use.
https://fs.spec.whatwg.org/
- Learn Postgres at the Playground
What are some alternatives?
zen-mode.nvim - 🧘 Distraction-free coding for Neovim
node-postgres - PostgreSQL client for node.js.
vim-pencil - Rethinking Vim as a tool for writing
file-system-access - Expose the file system on the user’s device, so Web apps can interoperate with the user’s native applications.
vim-easy-align - :sunflower: A Vim alignment plugin
v86 - x86 PC emulator and x86-to-wasm JIT, running in the browser
vim-startify - :link: The fancy start screen for Vim.
runno - Browser-based runtime for programming languages and WASI binaries.
indent-blankline.nvim - Indent guides for Neovim
datasette-lite - Datasette running in your browser using WebAssembly and Pyodide
nvim-lua-setup
standards-positions