Hi all, while I was reading this awesome documentation of logseq, I was thinking that would it be a good idea to put the nested namespace into a separate corresponding nested subdirectory?
For example, when I create a page called book/1984 it would make 2 pages: book & book/1984, and the files would be saved into book.md and book.1984.md. However, would it be better if it would be stored in book.md and book/1984.md, i.e. creating a folder called book?
I am worried that as my pages expand, searching through the large pool of pages md files would be cumbersome, especially when I sync the md with my phone. Thanks!
8 Likes
I’d be concerned that this might make refactoring namespaces difficult. I’d like flexible namespaces used to create note trees that can be easily refactored like they can be in Dendron. I’m not sure if putting them in sub-directories would make this process cumbersome or slow.
Why would it make it slower? The file name handling code would barely change, surely? Do you have a use-case that explains how it would make refactoring difficult?
Also, I accidentally noticed that you can already move pages to a subdirectory of the pages/ dir (or create them there), and Logseq deals with it happily. It does NOT treat those subdirectories as namespaces though, it just treats the file as if it was in the parent directory. Renaming the page to be in a name-space does the usual namespace___pagename.md, but it leaves the page in the subdirectory, which is at least nice for browsing while editing content with vim.
1 Like