Thanks for both ideas, I appreciate it. Of course, I should have thought of Google Search by myself, I use it all the time. But I blanked in the face of a new kind of quandary.

And the formatting correction is very helpful, thanks for that as well.

Rol

I use taskpaper for tasks, but Reminders for recurring tasks. I am intrigued by the idea of using pythonista to load recurring tasks due today into taskpaper every morning.

I have found this pythonista script

import reminders
todo = reminders.get_reminders(completed=False)
print('TODO List')
print('=========')
for r in todo:
    print('[ ] ' + r.title)
done = reminders.get_reminders(completed=True)
print('DONE')
print('====')
for r in done:
    print('[x] ' + r.title)

Which seems like a good starting point, but a) I don't know pythonista, and I don't understand the data structure of Reminders.

So even when I changed the line

print('[ ] ' + r.title)

To

print('[ ] ' + r.title + ' ' + r.due_date)

it gives me incomprehensible error messages.

I am very willing to learn how to do this, but can anybody one help with these questions?

• Is this a good idea, and has anyone done it already?
• what is the data structure for a Reminder?
• how can I filter on items due by tonight at midnight?

Rol

Builds on the Archive @done in the Editorial Workflow Directory.

This workflow appends @done tasks in a TaskPaper document to the top of a separate CompletedTasks.taskpaper file in Dropbox. Attaches the date that the new archived tasks were added.

It then returns to the original file.

http://www.editorial-workflows.com/workflow/5810637028458496/dMt1PRVgU-8

There is a sister workflow, Select Archive, that selects the archived tasks at the bottom of the original file In case you wish to delete them. However, it leaves the deletion step itself to the user as a safety precaution.

http://www.editorial-workflows.com/workflow/5882227254624256/9u-FUc2loSs

This is without question a dumb question, but I am still stymied. Can anyone tell me what is wrong?

This little workflow works perfectly.

http://www.editorial-workflows.com/workflow/5882227254624256/9u-FUc2loSs

But when the same steps are included at the end of a longer workflow, the longer workflow opens the document, selects the entire document, but then fails to find the archive: line. It leaves the entire document selected, but greyed out, not blue. I think that means something, not sure what.

Any insights?

Thanks.
Rol

I solved the problem by find/replace tab with # before doing the find/replace \s+, and after I got rid of excess space, I reverse the fine/replace.

It's a good solution, and if there are 2 or more tabs, it correctly replaces them.

I understand the problem differently now. Here is an example:

Taskpaper File --
Project:
Task 1 @later

There is a tab in front of Task 1

1. Extend selection both ways start/end of line
2. Find/Replace @later with (null)
3. Find/Replace regular expression \s+ output (1 space)
4. Replace Selected Text with Input @now

Extra spaces can accumulate over time, so line 3 cleans that up. But line 3 is also replacing the tab with 1 single space, which is unfavorable behavior!

There must be a way to fix this.

I create workflows to set tags as priorities. When I change a priority, I EXTEND to capture the whole line, then remove the old priority, then Replace what is left with the new priority at the end.

But the tasks are initially indented by 1 tab character, and when the line is replaced, it is no longer indented. I am sure there is a simple fix for this, but I don't know what it is.

Can anyone help?