Thanks for this tool. I'd love to have syntax highlighting for task creation dates and the priorities as well.

Example:
(A) 2015-02-06 Finish summaries of chapters +book @work due:2015-02-08

Probably need some tests set up to check the behaviour. There's a system built into Atom, I think. At least they have tests in the Atom development tutorial!

Can you provide a example of usage? I have no idea how to use this. Its nothing colored.

[Enter steps to reproduce:]

1. ...
2. ...

Atom: 1.32.0 x64
Electron: 2.0.9
OS: Microsoft Windows 10 Education
Thrown From: language-todotxt package 1.1.5

Stack Trace

Failed to activate the language-todotxt package

At letter.toLowerCase is not a function

TypeError: letter.toLowerCase is not a function
    at _loop (/packages/language-todotxt/lib/language-todotxt.js:47:44)
    at Object.activate (/packages/language-todotxt/lib/language-todotxt.js:45:24)
    at Package.activateNow (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:3029631)
    at measure (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:3029043)
    at Package.measure (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:3026674)
    at activationPromise.activationPromise.Promise (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:3028903)
    at new Promise (<anonymous>)
    at Package.activate (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:3028846)
    at PackageManager.activatePackage (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:378471)
    at ~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:912430
    at r (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:11:907036)
    at o (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:14:1037411)
    at t.bufferStream (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:14:1037565)
    at Socket.e.on (~/AppData/Local/atom/app-1.32.0/resources/app/static/<embedded>:14:1036167)
    at emitOne (events.js:121:20)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:554:12)

Commands

     -2:09.0 intentions:highlight (input.hidden-input)
     -2:08.7.0 core:save (input.hidden-input)
     -2:02.4.0 intentions:highlight (input.hidden-input)
     -2:01.2.0 core:undo (input.hidden-input)
  2x -1:58.8.0 core:redo (input.hidden-input)

Non-Core Packages

atom-beautify 0.33.4 
atom-clock 0.1.16 
atom-python-run 0.9.7 
atom-python-virtualenv 1.0.2 
autocomplete-java 1.2.7 
autocomplete-python 1.10.12 
busy-signal 1.4.3 
git-control 0.9.0 
git-log 0.4.1 
git-plus 8.1.0 
git-time-machine 2.1.0 
gpp-compiler 3.0.7 
Hydrogen 2.6.0 
ide-java 0.8.3 
ide-python 1.0.0 
intentions 1.1.5 
language-kickstart 0.2.0 
language-puppet 0.23.0 
language-todotxt 1.1.5 
linter 2.2.0 
linter-gcc 0.7.1 
linter-javac 1.9.4 
linter-ui-default 1.7.1 
linter-vagrant-validate 1.1.0 
print-code 0.7.1 
python-debugger 0.2.0 
python-indent 1.1.6 
python-tools 0.6.9 
script 3.18.1 
split-diff 1.5.3 
todo-show 2.3.2 
tree-view-git-status 1.5.2 
vagrant 0.1.0 

Duplicate the functionality of the tmTodo feature here:

https://github.com/sideshowcoder/tmTodoTXT/blob/master/Commands/Create%20like%20current.tmCommand

It seems to create a new task with the same priority, project and context as the one on the current line.

Change a (D) to an (E) or an (M) to an (N). Decreasing the priority of a (Z) or an unprioritised task is a no-op.

todo.txt format is made to be sorted. We should have a note about using this module. https://atom.io/packages/sort-lines

At least on the dark ui theme, the start date is the same color as the priority. It'd be nice to see a little more contrast.

The project regexp is pretty forgiving. We should be more stringent, only matching + with a space before and word after.

We should include the build status icon on the README page. Depends on #25.

Like "todo-txt do", marks a task as done:

• Add an "x " at the beginning of the line
• Add the completion date
• Change priority "(A)" to "pri:A" and move it to the end of the line

I am not certain if this is possible. Any txt file I create is set as a TodoTXT file instead of Plain Text. Can language-todotxt only recognize todo.txt?

"@" matches as a context. Should be some content to it.

Our syntax highlighting is kind of a mess. I'd like to get it so we have the following elements available for styling:

• x ... done task appears as a comment
• creation date
• completion date
• (A) priority
• +Project
• @Context
• description plain text
• due:yyyy-mm-dd due date
• t:yyyy-mm-dd start date
• key:value key-value metadata pairs

I can see adding other special handling for well-known key-value pairs, but for now this should probably work well.

done.txt is useful, but most of the functionality in the next version (like adding new tasks) won't be useful for it. To be conservative, we should not load for it.

I use . as a date separator I've forked and modified the code to meet my needs. Do you think there is a big enough audience to add this to the options and allow user to select the data separator?

Show only lines with a particular context; hide others.

https://gitter.im/todotxt/language-todotxt

Based on https://github.com/atom/ci and https://github.com/atom/ci/blob/ddf83c3dccebc3510d6d4518b7f1a1b5d8b614a8/appveyor.yml

It'd be great to have syntax highlighting for key:value metadata. We have it for due: and t: but other metadata could probably use some highlighting.

When tagged versions of the package pass the unit tests on Travis, we should automatically push them to apm so they get distributed.

Show only tasks for a given project; hide the others (somehow).

We should test the build on Travis.

Show only lines with a particular priority

Would you consider adding commands like these as well, as a complement to syntax highlighting? https://github.com/sideshowcoder/tmTodoTXT/tree/master/Commands

Contexts and projects come up with the same color right now. It'd be great to have different colors so you can see the difference.

With this package installed, I'm not able to open a Markdown preview. Has anyone else had this problem?

I'm not sure if this is the right place to report this.

• Atom 1.10.2
• language-todotxt 0.6.1
• OSX 10.11.6

Let me know if there's anything I can do to help resolve this issue.

http://todotxt.org/images/todotxt_logo_2012.png

A way to quickly change a (B) to an (A) or a (W) to a (V). Trying to increase the priority of an (A) or an unprioritised task is a no-op.

Function to add a letter priority to a line, or change the current priority.

Email addresses like [email protected] will match as a context for "@example.com". There should probably be a check for a word boundary (\b) before the ampersand.

Should have myself and @gerane in the copyright notices.

Dear @gerane,

Thank you for creating this package. I would like to have TODO syntax highlighting, too.

Thus, I installed the package but I don't see any highlighting. See this example:

Could you please provide me with a screenshot so that I can see how it is supposed to look like?

Thankfully,

Robert

I didn't update the changelog before releasing 1.0.0!

I'm working on adding autocomplete suggestions for projects and contexts, so when you type "+", you get a list of all the projects that it finds in the file, and similarly for "@". If that's something you're interested in adding, I can submit a pull request.

Add a new line with the creation date at the beginning of the line, and the cursor placed one space after the date:

2017-08-14 |

We should have a special entity type for create date. It should be
colored like a date by default.

Duplicate the "Set Task Date" feature from tmTodo.

https://github.com/sideshowcoder/tmTodoTXT/blob/master/Commands/Set%20Task%20Date.tmCommand

It seems to add a "t:" where is today.

The README needs:

• todo.txt logo
• link to todotxt.org
• link to LICENSE
• link to CODE_OF_CONDUCT

There's a new organization managing the todotxt/todo.txt-cli and other apps. It'd be great to move this repo there and get more group maintenance.

It's better to move it than fork it since the issues will all move along with it.

@karbassi manages the organization and could help with the move. I would be happy to help maintain the codebase after the move.

@gerane we would also need to figure out how to manage the push to the Atom package manager.

Function to archive completed items in todo.txt to done.txt in same directory, similar to behaviour of "todo-txt archive". Ideally, it'd have a keystroke associated with it.

Having additional functionality besides the syntax colorisation requires a main module.