Christian Moe <m...@christianmoe.com> writes:
For this particular use case, though, have you considered a different
approach, using entries and column view? That is:
Wow, this is really a great solution. I didn't know I could play with properties to build a table
template!
It's just a little bit verbose, but the row definitions can be collapsed.
Thank you!
An alternative to defining a STATUS property at all would be to define the
statuses as local TODO keywords, which gives you a quick way to look up
all unsent or unpaid invoices via the agenda view without having to
write match syntax.
I've tried overwriting locally `org-todo-keywords` but I didn't
understand how: do I need a custom lisp snippet like the following?
--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC emacs-lisp
(setq-local org-todo-keywords
'((sequence "TO_BE_SENT" "SENT" "TO_BE_PAID" "PAID")))
#+END_SRC
--8<---------------cut here---------------end--------------->8---
but how can I define the override as a PROPERTY?
And then how can I use the redefined sequence in the invoice entry PROPERTY (instead of the
`:Status:` property)?
Cheers,
