Gentle Formatting of the To-Do Record

I lately met the mission in todo.txt format, which makes it potential to make use of lists of things from the checklist. motion in plain textual content to create and handle your initiatives. I just like the simplicity of the concept, however a number of parts have prevented me from adopting it wholeheartedly.

First, I believe it's actually ugly. It's exhausting to investigate, particularly when there’s a lot to do. I do know that the concept is that it’s an intermediate illustration, however that this illustration is visually cumbersome.

Second, there are lacking notes. Freehand notes are an vital a part of activity administration, so it 's price noting the cellphone variety of the automotive' s location when you might want to put your tires on. winter.

Third, it will depend on the order, with a left-to-right disposition that actually doesn’t work for me.

Fourth, I don’t suppose that the (A) – (Z) precedence format is especially readable.

Though I like Annotations + Undertaking and @Context, I’ve the impression that todo.txt is just some steps from an intermediate type far more versatile and readable.

So I began eager about the best way to make this idea extra versatile. On the one hand, I believe the instance tries to make the mission and context "fluids" in a method that they don’t essentially should be. Sure, you may need to interview to see "what are all of the initiatives I'm engaged on?" And "what contexts do I work in?" To distinguish them, however I don’t suppose they want them to be embedded textual content to do.

The next is a really barely thought out retelling that I pulled completely out of nowhere. I didn’t spend numerous time on it and I'm positive there are higher methods to transform it to assist man-readable and barely annotated lists of duties. I begin this query as a place to begin in case one in every of you want to deepen this dialogue. It's a design train for me, an train that allowed me to tug a few of these ideas out of my head and throw them right into a weblog. So, take this for what it’s.

Think about that markup seems extra like this, relying on whether or not you're annotating mission or context values. A part of me rejects the notion of each kinds of markings, however I recognize the truth that you may need to interview "present me all my initiatives" and "present me all my backgrounds," and I'll be comfortable to see you. acknowledge the worth:

@ (tag) or + (tag)
@ (key: worth) or + (key: worth)
@ (precedence) or + (precedence)

A precedence could be so simple as a quantity, which individuals would deal with higher than "A", "B", "C", and so on. I believe a sample of (Zero-9) + would additionally permit: Straightforward differentiation within the evaluation between a tag (arbitrary textual content) and a precedence. Priorities vary from Zero (highest precedence) to any arbitrary quantity (lowest precedence). I doubt that individuals use greater than two or three precedence ranges (low, medium, excessive) in the event that they use them.

Provided that dates are important for the completion of deadlines, you’ll be able to withdraw them with NLP or be extra specific: @date (due date: 2019-05-02). The distinctive key phrase would let you analyze a date with extra versatile keys and stop an explosion of key phrases that you simply may encounter when making an attempt to design particular eventualities like @due (2019-05- 02), @checkin (subsequent Tuesday), and so on.

Relative dates would require a creation date. In case you use an editor quite than the uncooked format, you’ll be able to inject it as @date (created on: 2019-05-02). The second time you do that, nevertheless, you’re shifting away from the concept of ​​a easy, human-readable annotation that can be utilized by a software.

In my head, a greater system wouldn’t be monotonous. The addition of empty areas between parts vastly will increase the vertical house. Due to this fact, an indentation impressed by Python can keep away from the next issues:
Rendezvous for snow tires
Name and speak to Judy at 505-555-1212 # feedback are all the time glorious
She says to contact them not less than one Thursday earlier than the weekend you need. # Not proud of handbook line breaks right here
convey the automotive.
@ (house) + (winterizing) + (2) @ (earlier than: 2019-12-01)
Put the squeegee within the automotive
@ (automotive) + (wintering) @ (made) # bah me!
Get flu shot for Bob and Francis
Have them already for Fred and Mary
@ (household) + (well being) + (season) + (Costco) + (1) + (buying) # C is a buying, even when it isn’t d & # 39; purchase one thing

It's exhausting, clearly, however I believe it's a bit extra readable than the present formatting and slightly extra versatile:

If I work with an editor, I would favor that the performed parts be mechanically moved down or probably deleted or added to a different "performed.txt" checklist.

As well as, upon getting the ability to mark and categorize utterly, a well-constructed software ought to let you reap the benefits of every of those to show the related parts in a extra structured method. The format is easy however it isn’t needed that you simply current the marked data.

No matter it’s, these are my ideas. I see a mission with good bones that misses numerous human elements. What sort of change would you make to show this strategy right into a extra usable and common strategy? Or would you simply say that "plain textual content isn’t actually applicable right here" and as an alternative use OmniFocus or Issues? I’m curious to know what you suppose.

Replace : Readers Point out: