switching from neuron to emanote

[zoranbosnjak]

Hi,
I am trying to switch from neuron to emanote, for the ~/zettelkasten folder. Some beginner questions about the transition:

I am used to neuron new to quickly create new note (random .md) file with timestamp in the header. I like the idea of random filenames with a proper document title, but the emanote examples suggest to use subject-related-filename.md instead. So, what's wrong with random filenames and why there is no emanote new command? Is there any other suggested way to create zettelkasten like notes?

I've started with empty ~/notes folder, started up emanote server and copyed over some ~/zettelkasten/*md files. The html rendering was OK, but the links from one note to the other does not work the way it was, that is <1234...> is not pointing to the 1234....md file. I've checked the migrating from neuron guide, but this is not mentioned. So, how do I fix the inter-node links?

I have around 500 files, I am running the server with emanote run --port=8080 and the response on the web page is very slow (it gets slower as I add more files). I this run command just for test? Do I suppose to generate and view static pages instead? I've used statically generated pages with neuron.

Thanks for your answers.

[srid]

For the links, you want to replace <1234> with [[1234]] (see wikilinks).

Regarding the filenames, emanote doesn't enforce any particular convention, so you can use 1234.md if you want.

Yea, the run command runs the live server which can be slow over time (see #411 and #66), but the static pages (generated using gen) will obviously be faster. We should resolve the performance issues with the live server; it is mainly to do with the JavaScript library we are using -- morphdom.

[srid]

We should resolve the performance issues with the live server

srid/ema#166

[zoranbosnjak]

Thanks. I just need a few more suggestions, how to actually replace my old workflow. In particular:

Any suggestion how to replace neuron new command? A custom script? Keeping neuron installed just for this purpose would be silly, I guess. May I suggest to introduce additional command, like emanote new - new issue?

I was using neuron -d path rib -w in a background, but emanote gen does not have -w euqivalent. What are your suggestion to monitor filesystem changes and regenerate?

[srid]

@zoranbosnjak

Regarding the live server performance, could you try out #567 and let me know if that improves it on your notebook (of 500+ files)? You can run the command in the PR description.

As for neuron new replacement, you may look into zk (see here). zk interoperates with Emanote, and it too is available through Nix (nix run nixpkgs#zk). I think emanote new would be outside the scope of this project.

What are your suggestion to monitor filesystem changes and regenerate?

You can use something like https://github.com/eradman/entr and rerun emanote gen when files change. But do also try out the live server with the PR above.

[zoranbosnjak]

@srid, thanks.
I have tested live server performance with version 1.3.20.0 and it works fine with 500 files. I will have a look at zk and entr projects to resolve the remaining problems.