laydown --help
thread 'main' panicked at 'Failed to deserialize content from laydown.ron: missing field `history`', /home/x667421/.cargo/registry/src/github.com-1ecc6299db9ec823/laydown-1.5.0/src/data_file.rs:52:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

laydown --version
thread 'main' panicked at 'Failed to deserialize content from laydown.ron: missing field `history`', /home/x667421/.cargo/registry/src/github.com-1ecc6299db9ec823/laydown-1.5.0/src/data_file.rs:52:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

laydown edit
thread 'main' panicked at 'Failed to deserialize content from laydown.ron: missing field `history`', /home/x667421/.cargo/registry/src/github.com-1ecc6299db9ec823/laydown-1.5.0/src/data_file.rs:52:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

All this command (and maybe others, I can't access help...) shouldn't break when laydown.ron is not possible to deserialize. I mean they should not attempt to deserialize it.

laydown archive currently overwrites existing archive files without a warning. This made me lose todays archive by my own stupidity. This commit will prevent that this will happen to others.

Me again. This will prevent running laydown archive twice from overwriting the archive of the day.

I see that the default editor is configured to be vi. I like to use vim and kakoune, but they are not easy or even intuitive editors. If someone did not configure it's EDITOR env variable I think that nano is much more easy to use (not as easy to move lines from DO to DID) and is also installed everywhere.

It does not affect me, but any new linux/BSD user. Not sure how it will work on windows 🤔 (if laydown work there).

laydown
thread 'main' panicked at 'Failed to deserialize content from laydown.ron: missing field `history`', /home/x667421/.cargo/registry/src/github.com-1ecc6299db9ec823/laydown-1.5.0/src/data_file.rs:52:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Rust crates usually try to follow https://semver.org/ meaning that no break should happen if there is not a new major version. history field could be optional (only when reading?) and you won't need to tag a version 2.0 this way.

I just started using this tool a few days ago and was pretty surprised that the archive command doesn't also clear the laydown. Maybe that's just me though. Would you be open to a PR that changes this behavior?

If you like the current behavior better, just close this. This is an awesome tool nonetheless. :tada:

Close #23. You are right, I can do a PR for something like this. Even more now that I read a bit the code to detail for #23.

I think in the mean time you got another PR for this :sweat_smile: but I wanted to finish mine anyway. At the minimum to ~~un~~rust me ^^

This should be a working fix for old files (https://github.com/badjr13/laydown/issues/23) but is also kind of hacky. I feel like there should be a more robust way to update the schema for past files, which would actually be a fun thing to code probably

cheers

Print configuration directory with: laydown config-dir

Example usage/output:

manos % cargo run -- config-dir
    Finished dev [unoptimized + debuginfo] target(s) in 0.00s
     Running `target/aarch64-apple-darwin/debug/laydown config-dir`
/Users/manos/Library/Application Support/laydown

If my env does not have $EDITOR set, it currently panics with:

No $EDITOR environment variable found.: NotPresent'

A "sane default" would make sense, if possible

If I start a task (and I log it as "doing" in laydown) and complete it during the day, I would like to be able to move it from "doing" to "did".

If I find time, I might try to come up with a pull request.

It's a common convention in many CLI tools to use the $EDITOR environment variable as a path to the user's preferred text editor. Notable examples include git and sudoedit. It's be a fairly straightforward change:

let default_editor = std::env::var("EDITOR").as_deref().unwrap_or("vi");