<commit_before>if nothing next then show deferred
---
query sort order is all wrong
---
infer a status ... next is things that are today, deferred is things that are after today
show this on the search screen and the board
---
use ^ for status and something else for date, maybe @, maybe nothing, maybe the date is part of the status
---
have a max items setting, default to 10 and then do ... to encourage faster processing
---
flag as red things that are past today
---
show a summary of stats - using the colours and counts
---
moan if something is next and it is nexted again (don't change the date, enforce a defer)
---
make defer better
---
support ; when adding (how do we handle tags? apply to all?)
---
ref : tag ...
---
will want expert mode add and next +/
will want expert mode add and done +!
might want expert mode /d, /w, /m, /y or even d, w, m, y were it's automatically 1, but could be /d 2 etc
---
http://lifedev.net/2007/02/gtd-cheatsheet-the-workflow/
http://lifedev.net/2007/02/gtd-cheatsheet-the-collection/
http://lifedev.net/2007/02/gtd-cheatsheet-processing-your-stuff/
---
(unsorted)
red for things that are past due date
orange for collected
yellow for next
grey for things we don't need to worry about yet (incubated backlog) i.e. someday maybe
how about delegated - maybe they should be highlighted blue or yellow/orange - could also have a due date
 - important to highlight what we are waiting on
do we allow reference items? - could also be grey<commit_msg>change priorities<commit_after>flag as red things that are past today
---
infer a status ... next is things that are today, deferred is things that are after today
show this on the search screen and the board
---
show only next on the board ... if nothing in next then show deferred
---
use ^ for status and something else for date, maybe @, maybe nothing, maybe the date is part of the status
---
query sort order is all wrong
---
have a max items setting, default to 10 and then do ... to encourage faster processing
---
show a summary of stats - using the colours and counts
---
moan if something is next and it is nexted again (don't change the date, enforce a defer)
---
make defer better
---
support ; when adding (how do we handle tags? apply to all?)
---
: tag (although search covers it for now)
---
will want expert mode add and next +/
will want expert mode add and done +!
might want expert mode /d, /w, /m, /y or even d, w, m, y were it's automatically 1, but could be /d 2 etc
---
http://lifedev.net/2007/02/gtd-cheatsheet-the-workflow/
http://lifedev.net/2007/02/gtd-cheatsheet-the-collection/
http://lifedev.net/2007/02/gtd-cheatsheet-processing-your-stuff/
---
(unsorted)
red for things that are past due date
orange for collected
yellow for next
grey for things we don't need to worry about yet (incubated backlog) i.e. someday maybe
how about delegated - maybe they should be highlighted blue or yellow/orange - could also have a due date
 - important to highlight what we are waiting on
do we allow reference items? - could also be grey
{'fraction_non_alphanumeric': 0.08801313628899836, 'fraction_numerical': 0.01444991789819376, 'mean_word_length': 3.3022598870056497, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2003372', 'n_tokens_mistral': 910, 'n_tokens_neox': 843, 'n_words': 466}