Code cleanup and formatting. For the formatting, I used rustfmt. For the cleanup, I do it by hand. Also, you might wanna check lib.rs line 13. Basically, instead of making the TODO file in the current directory, it creates it in $HOME/TODO

Ok so I'm not sure if this is me just being dumb but the numbering seems to be wrong? I added 3 todos and instead of them being numbered 1 2 3 they were numbered 1 3 5

It would be awesome if this could run on macos!

From what I can tell, the current build panics at line 25 of lib.rs if ran on mac. I tried changing the match statement to include 'macos', but only ran into further errors.

Hello,

First, thank you for your work. I found a bug when using done feature.

➜ todo list
1 lol
2 lil

➜  todo done 2
thread 'main' panicked at 'Couldn't open the todofile: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/lib.rs:235:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Hey there!

I saw a post on r/linux or r/rust some days ago and have been using it since, thank you so much! With the new mac support PR (I think) the TODO file path has been changed from the current directory to the HOME directory (at least on my pc, which in hindsight after looking at the code was the intended behavior all along).

Anyhow, I like to have my TODO's split across multiple categories/projects, which was nicely possible with the "local folder TODO file" behavior. Would it be possible to add something like a flag to point to a file to use as TODO file?

I figured I would open an issue first to talk about the best way to do this (e.g. by a -f flag or having an optional argument before the action that denotes the file).

todo version: 2.3.1

Steps to reproduce:

while in /home/username/:

todo add "something"
cd Documents
todo done 1

output:

thread 'main' panicked at 'Couldn't open the todofile: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/lib.rs:226:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

~As far as I understand, todo creates a file in my home directory by default and when called from another directory it cannot access it.~ By some weird reason todo list works fine It seems a little bit weird, since I remember seeing TODO files in other directories.

So, I assume that the creation process is somehow wrong.

If any extra information / logs needed, then please be kind to provide some instructions on getting them.

changed up the name of the list file so it will appear hidden on UNIX systems. Also replaced all mentions of the file name in the code with a constant to make editing the name easier.

My current workflow is that i create a todo list in the morning and slowly but surely check off the assignments which is done, i don't remove them because i like to see how i'm doing 😅. However because of this i have to go through at the end of the day and delete every entry in the list. Thus i implemented a simple and intuitive reset command which does exacly that.

This pull request accidentally became a few features so if you only want a couple of features here let me know and I'll put in a pull request of just those instead. Feedback is of course welcome

Firstly, this replaces the code that checks for OS with the directories crate which does the same thing but with support for more OS's and includes a function to get the config directory which may be useful later.

I also replaced the home variable in the Todo struct to be todo_path as a PathBuf. This means you don't have to convert the String to a Path and join TODO on the end. I figure this won't cause any problems because that's the only use of home. This also fixes the issue where running a few functions (such as done) outside the home directory fails

I also ran rustfmt and fixed a lot of clippy lints. For example .len() < 1 becomes .is_empty() to convey meaning.

And finally I collapsed all the else blocks that happened after if statements containing process::exit(1) since anything after that can't be reached anyway and it reduces indentation which makes the code a bit easier to follow

It would be pretty handy to add priority indicators to the app. For instance, we could divide priorities as:

1. Low
2. Normal
3. Urgent

and the color code them so that when list() is called, there's a clear visual distinction between them. A basic idea would be create an enum for the types.

I might do a pull request soon :)

I think it would be cool if, when launching the Todo command, it would look for a todo list inside the current folder, without the hustle of having to specify the 'TODO_PATH=' every time. Then, if the current folder does not have a list in itself, go and search for the home path one. Another thing would be to add an option (like "home") to skip the lookup of the current folder.

Allow a method for organizing todos via f.x. boards similar to Taskbook. This would use @labels to create so called boards which can then be queried with todo list @boardname to only show tasks belonging to the queried board. Calling todo list on its own would list all boards e.g.

@work
- task A
- task B

@personal
- task C
- task D

@projectname
- task E
- task F

User can opt into saving their todo in the form of markdown.

Currently

todo saves todos in a TODO file.

Request

Save todo in an opt in markdown file.

Eg.

# TODO

1. Foo
2. Bar

This allows cross device sync, eg with nextcloud. Ease of bulk editing using text editors. This can benifit users already using markdown for mangaing their todo.

A config file can be saved at $HOME with destination file/folder preferences.

It would be nice if todo can take tasks from stdin.

Usage Add tasks echo banana orange | todo add or cat my_issues.txt | todo add

Mark done tasks start with 'today': todo raw todo | grep '^today' | todo done

Possibilities would be endless.

Nice tool, btw!