In its absence you can always open the "index.html" file directly to access the site. Perhaps a neuron open command can be provided that does this (using xdg-open on linux and openon Mac).
I generally am against site generators and similar stuff to have their own http server, I like to use mine. but with neuron the process was so easy and smooth that I like it the way it is.
When you iterate over your zettels in an editor and use "rib -wS" it might be nice to have the browser live reload changes. I use https://livejs.com/ in a similar project and that works q...
Does anyone find the HTTP server to be all that critical to their workflow? I'm considering removing it.
In its absence you can always open the "index.html" file directly to access the site. Perhaps a
neuron opencommand can be provided that does this (usingxdg-openon linux andopenon Mac).Or, it can be disabled by default, with CLI option to run it if anybody wants it.
Alright, the new command is:
neuron -d ./guide rib -wSLet's keep HTTP server, but
neuron openis addedI generally am against site generators and similar stuff to have their own http server, I like to use mine. but with neuron the process was so easy and smooth that I like it the way it is.
(my experience is always with javascript/npm apps, so it's always unpleasant
the HTTP server is useful to implement scroll-sync UX like this: https://github.com/iamcco/markdown-preview.nvim#--markdown-preview-for-neovim--
cf. https://github.com/srid/neuron/issues/200