blindFS
g:task_report_command should include user-defined reports
Now g:task_report_command contains only predefined reports. Ideally it should contain everything task report returns, including the user-defined reports from .taskrc.
task report returns many undesired commands, I'll just allow users to specify their own g:task_report_command. For example, If you want to add the command my-command,
just put let g:task_report_command = ['my-command'] in your vimrc.
That's just what I was doing via autocmd and +=. I still believe that the user could wish to see her own custom .taskrc-defined reports there automatically.
Well, automation is good, but using task report to get it is not a good approach, in my perspective.
I want to keep the init process simple and fast.
Perhaps parsing .taskrc? I'm concerned with the current solution in this way: the user has to retype dozens of the existing reports in her .vimrc. Maybe there should be an option to extend the list of reports, not overwrite? As to the init process, you still need to call task next before anything is shown.
Currently, it is not overwrite already, you don't have to put 'next, long, all, ....' in your g:task_report_command, just your personal reports. But you need to put that line before Bundle 'xxx/vim-taskwarrior' if you use vundle or sth like that, while neobundle will allow you to put it anywhere.
As for the init process, I mean the init process of vim instance, not the TW buffer. Generally speaking, plugin/*.vim files will be sourced each time vim starts.