#Bring back the "parent" property
14 messages · Page 1 of 1 (latest)
I think an example of some workflow and its issues would be useful here. We have "parent" property for regular nodes. But somehow it does not help in you workflow, right?
parent property was renamed as extends. I did not go away. It was just renamed
Does not work for normal pages, right?
What I want is to be able to add a person as a child of a company page without going to the library page, finding it there, moving it, etc
Just go to the person page where i am already, cntrl shift p, and set parent to something different
I can get the idea wrong, but try this please:
- On a person's page, click the page title.
- Press cmd+shift+m (or cmd+k and type "move to").
- Choose the new parent
Does it do what you were looking for?
It seems like it should! Did not know about this command.
My problem is that the search function (not the normal one, the one form the library page) does not work for me. It always returns empty. But that is a separate issue
See? Always empty
That's weird, especially since I also have a "logseq" page in my library. I don't have much experience with the search, so I can't say anything useful.
The only thing I would try is to use the "parent/child" syntax to add items to the library, rather than using the library UI.
That is useful for non-existing pages, but you cannot add an existing page with that right?
wait
My search in "move to" looks slightly different. It does not say that it searches only among nodes. Library items are nodes too, so I don't know why it matters, but maybe that will help with the search issue.