You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked existing issues and there are no existing ones with the same request.
Feature description
I'm new to the GTD workflow and I've been playing around with it for just a few hours. I feel like a nice convenience would be the ability to quickly move a task to a different file in your workspace after processing it in your inbox.
This could be part of the :Neorg gtd edit interface or a whole new interface on its own (e.g. :Neorg gtd move) that allows you to pick a file in your workspace to move the task the current cursor is on.
Like I said, I'm new to GTD so I welcome any input or advice on this and whether this feature is worth the effort of implementing. Is the general practice just to copy and paste a task and any contexts associated with it to the relevant file after you process it in the inbox?
Help
Yes, but I don't know how to start. I would need guidance
Implementation help
No response
The text was updated successfully, but these errors were encountered:
Issues
Feature description
I'm new to the GTD workflow and I've been playing around with it for just a few hours. I feel like a nice convenience would be the ability to quickly move a task to a different file in your workspace after processing it in your inbox.
This could be part of the
:Neorg gtd edit
interface or a whole new interface on its own (e.g.:Neorg gtd move
) that allows you to pick a file in your workspace to move the task the current cursor is on.Like I said, I'm new to GTD so I welcome any input or advice on this and whether this feature is worth the effort of implementing. Is the general practice just to copy and paste a task and any contexts associated with it to the relevant file after you process it in the inbox?
Help
Yes, but I don't know how to start. I would need guidance
Implementation help
No response
The text was updated successfully, but these errors were encountered: