Refresh v Reload

What is the difference between reloading a graph by Ctrl + r and refreshing it from the menu? I see that the menu for Refresh says “import changes from local files”; if that’s uniqe to Refresh, what does Reload do?

1 Like

Refreshing the graph basically imports the changes without reloading the app. What reloading does is basically what logseq does on startup. If you close and reopen the app, that’s pretty much the same effect as reloading. Reloading can be useful when fixing errors or when weird stuff is happening but takes time to startup the graph again. Reloading includes what refreshing does but anyways refreshing is rarely required because logseq does much of the functionality on its own anyways.

Is it safe to say you should reload after modifying config.edn to pick up the changes? Or is a refresh sufficient?

Refresh is usualyl sufficient especially for default queries. But it’s generally a good idea to reload when editing like settings.

Is there any shortcut to refresh?
Till the vim motion feature comes, I am opening md files in vim and then refreshing logseq to import changes from local files.
So, binding refresh to a key would make this process more easier.

2 Likes

Does Refresh pick up new files created somewhere else, or should you use Reload for that?