Feature #310
'task add' with external editor
| Status: | Closed | Start: | 11/12/2009 | |
| Priority: | Normal | Due date: | ||
| To: | Paul Beckingham | % Done: | 100% |
|
| Category: | core | Spent time: | 0.10 hours | |
| Target version: | 2.0.x - Katana | Estimated time: | 0.10 hours | |
Description
I was going to suggest that this error message could be improved a bit:
$ task add
A task must have a uuid, entry date and description in order to be valid.
Perhaps, as:
$ task add
A task must have a description in order to be valid.
Reason being that the user cannot (to my knowledge) dictate either the uuid or the entry date. However, that got me thinking the message might be apropos if the user had just used something like 'task edit'. Why not have 'task add' work like 'task edit' where only the uuid and entry date are populated? This might be more comfortable for a user wanting a form to fill out.
I don't want to distract from 2.0 development, but just in case this is super trivial, I thought I should bring it up.
History
Updated by Paul Beckingham 119 days ago
- Status changed from New to In progress
- To changed from David Patrick to Paul Beckingham
- Target version set to 2.0.x - Katana
- % Done changed from 0 to 100
- Estimated time set to 0.10
Good idea, leading to a much cleaner error message.
Updated by David Patrick 119 days ago
I don't think
$~ task add
should generate an error message at all, I think is should invoke the (to be enhanced) shell mode.
Any command such as the one above, lacking in parameters, is a candidate for shell-mode, and would be the same as typing
$~ task shell add
djp
Updated by Federico Hernandez 95 days ago
- Status changed from In progress to Closed