Currently, when you move a note to another project from the note command menu, the note disappears and you stay in the current project. This could make sense if you were invoking outside of the note perhaps, but I think better behavior if you are invoking from within the note would be to follow the note to the correct project. Bear in mind that because in Agenda notes are firstly tied to date, it may be less common than in other apps that you are starting a new note from within the right project
Makes sense to discriminate between following and non-following based on the way the move was triggered, we’ll have a look if this is possible.
I wonder if this is planned for future releases.
Just to clarify my use case:
I am in note B, which is currently under Project PA, and I need to move B to Project PB.
I type this in the note B: \move(PB)
I would have expected to remain in Note B (now under project PB). However, after typing the \move command, Agenda is showing me the other notes sitting on Project PA, and I have to manually go to PB to find note B.
I doubt this is the intended behavior
Thanks!
I agree w/ @javi. Keeping focus on the project the note is moved from is verifying a negative. Instead of the note moving to PB it may have gone to grandmas’ house.
*exception would be if it was moved to the trash??
Thanks for the report, we’ll take a look if this can be improved.