List projects/contexts of other .txt files

[pursvir]

I wonder if there is some alternative for "lsc" and "lsprj" for manually specified .txt file.
Pretty needed feature, in my opinion, if user splits their tasks into several .txt files (e.g. inbox.txt, todo.txt, someday.txt) and wants to keep it consistent, especially if there are thousands of tasks.

[inkarkat]

You can do

$ TODO_FILE=/path/to/other.txt todo.sh lsc

Splitting tasks into separate todo files is not recommended, but if you go that route, I'd recommend to set up separate aliases for each file:

alias todoinbox='TODO_FILE=/path/to/inbox.txt todo.sh'
alias todosomeday='TODO_FILE=/path/to/someday.txt todo.sh'

You can then do $ todoinbox lsc and so on.

If you need to override more than the file location, I'd recommend to use separate configuration files (you can source the common todo.cfg in each) and pass a dedicated config file in each alias:

alias todoinbox='todo.sh -d ~/.todo/inbox-config'

[pursvir]

Thank you!

[pursvir]

I've been playing around with these solutions a bit. Overriding env variable in Shell command (and in Shell aliases) has no effect. It acts properly only if I edit TODO_FILE variable in todo.cfg (or use Shell aliases that route to specified todo.cfg). In other words, todo.cfg variables have higher priority than Shell commands overrides. Is it a bug?

[inkarkat]

Oh, you're right! I have modified my own config to allow this, but I think the ability to override should be part of the default config; just submitted #460.
To adapt your config, simply replace

export TODO_FILE="$TODO_DIR/todo.txt"

with

: ${TODO_FILE:="${TODO_DIR}/todo.txt"}
export TODO_FILE

[pursvir]

Now it always works as intended. Thank you!