jekyll-garden VS vim-sensible

Since Obsidian and Jekyll both use Markdown, you can create a Jekyll project, open it as an Obsidian vault. You could then use Jekyll to run it as a web server on your own machine. (It also works nicely with Github Pages for public websites, since that has built-in Jekyll support.)

There's also a third-party Jekyll theme specifically for this purpose (https://github.com/Jekyll-Garden/jekyll-garden.github.io).

The github repo I'm using: Jekyll-Garden/jekyll-garden.github.io

I use github pages to host this for free. If you want more instructions on how to install you can follow these instructions from this repository: https://github.com/Jekyll-Garden/jekyll-garden.github.io . That being said, this repository fairly bare-bones in terms of Obsidian support and I've had to make custom modifications to it (e.g. doesn't support aliasing). The only reason I use it is due to a search feature that I like from it and github pages support.

#1: What are digital gardens? Let's share them. 🌿 #2: Everything I Know (X-Post HN) | 8 comments #3: Jekyll Garden : A Jekyll theme to publish Digital Garden from Obsidian | 0 comments

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.