Heirarchical structure to email imports
mikeboers says:
Howdy!
I think the email imports (now with with smart add functionality) would be much more beneficial to me (and hopefully others) if there was a short and easy way to group multiple tasks under the same group of tags/dates/etc, as well as adding notes to said tasks easily.
For example (using "[tab]" instead of spaces, because they don't show up here.):
Subject: Inbox
To: [my rtm inbox]
#@home ^today
[tab] Fix the clogged sink.
[tab] Install new curtain hardware.
[tab][tab] The current drywall anchors I have won't do. Need to use the special concrete toggles.
This will result in two tasks due today tagged @home. The second one will have a note with it.
Does this sound like it might be useful to anyone?
Mike
I think the email imports (now with with smart add functionality) would be much more beneficial to me (and hopefully others) if there was a short and easy way to group multiple tasks under the same group of tags/dates/etc, as well as adding notes to said tasks easily.
For example (using "[tab]" instead of spaces, because they don't show up here.):
Subject: Inbox
To: [my rtm inbox]
#@home ^today
[tab] Fix the clogged sink.
[tab] Install new curtain hardware.
[tab][tab] The current drywall anchors I have won't do. Need to use the special concrete toggles.
This will result in two tasks due today tagged @home. The second one will have a note with it.
Does this sound like it might be useful to anyone?
Mike
enkerli says:
Yes, quite a bit. I'm looking for ways to import outlines and this would be a useful way.
mediaarts says:
I love this idea. I don't understand the third level with the task `The current drywall anchors ...`.
To my knowledge there is no way to associate tasks with other tasks so why use a tertiary level when the secondary would do?
I liken this type of markup to that of HAML or SASS where children are taking on the attributes of their parents. Under this scheme, we could theoretically add another tag and utilize the third level.
e.g.:
#@home ^today
[tab] Fix the clogged sink.
[tab] Install new curtain hardware.
[tab][tab] #maintenance
[tab][tab][tab] The current drywall anchors I have won't do. Need to use the special concrete toggles.
In this case the task `The current drywall anchors ...` would have the tags `@home` and be due today as well as the additional tag `maintenance`.
To my knowledge there is no way to associate tasks with other tasks so why use a tertiary level when the secondary would do?
I liken this type of markup to that of HAML or SASS where children are taking on the attributes of their parents. Under this scheme, we could theoretically add another tag and utilize the third level.
e.g.:
#@home ^today
[tab] Fix the clogged sink.
[tab] Install new curtain hardware.
[tab][tab] #maintenance
[tab][tab][tab] The current drywall anchors I have won't do. Need to use the special concrete toggles.
In this case the task `The current drywall anchors ...` would have the tags `@home` and be due today as well as the additional tag `maintenance`.
Log in
to post a reply.