From 12/16/2009 to 01/14/2010

01/14/2010

07:46 AM Feature #366: task command environment variable
Each time a task query is issued, the TASK_COMMAND environment variable should be set. The actual command used to create a listing is essential to describe what the list does (and more importantly) does not contain. For reports that are printed, a... David Patrick

01/13/2010

05:32 PM Feature #283 (Closed): Annotations display options
Federico Hernandez
03:24 PM Feature #283 (In progress): Annotations display options
Federico Hernandez

01/12/2010

09:51 PM Feature #296: Setting configuration variables in .taskrc
Paul Beckingham wrote: > Any thoughts? I hadn't seen that in git since I've typically just edited the file directly, but the pattern makes sense. If we were using a "set" keyword or the like, I'd say go with the antonym (e.g., "unset"), but I... John Florian
06:04 PM Feature #365: Partial completion indicator
Completion is like pregnancy, in this case, it is or it isn't. There's status:pending and status:completed and nothing in between. I think you were onto something when you suggested that a partially completed task should be deemed started, but I ... David Patrick
08:53 AM Task 1.8.5 re-packaged for OSX 10.6
Task 1.8.5 has a new OSX 10.6 (Snow Leopard) package that properly installs the man pages, various documents, shell completion scripts, and Vim scripts. Prior OSX packages contained only the task program itself, a license and and a README. This... Paul Beckingham
08:44 AM Feature #365: Partial completion indicator
We could display partial completion dates alongside annotations: ... Cory Donnelly
08:36 AM Feature #365: Partial completion indicator
I have a few monumental tasks which don't lend themselves well to being reinterpreted as projects. Consider: ... Cory Donnelly

01/11/2010

11:14 PM Feature #296: Setting configuration variables in .taskrc
I think the following might be a better way, and more closely copies git: To set < name > equal to < value >: $ task config < name > < value > Are you sure? Y/n To set < name > to blank (ie not the default value): $ task config < n... Paul Beckingham
08:49 PM Feature #254 (Closed): Support two dateformats
Federico Hernandez
08:48 PM Feature #295 (Closed): Secondary dateformat for reports
Federico Hernandez

01/10/2010

07:38 PM Feature #295 (In progress): Secondary dateformat for reports
Federico Hernandez
07:38 PM Feature #254 (In progress): Support two dateformats
Federico Hernandez

01/09/2010

03:52 PM Bug #364 (Closed): Minor typos on overview page
Cory Donnelly
03:42 PM Bug #364: Minor typos on overview page
Cory, if you have ideas or want to experiment with things like this, please do. Paul Beckingham
09:48 AM Bug #364 (Assigned): Minor typos on overview page
It seems only fair to assign this to Cory, who clearly has an eye for it. Paul Beckingham
09:06 AM Bug #364: Minor typos on overview page
- 'corresponfing' should be 'corresponding' - 'more videos' should be capitalized - there are a few sentences missing punctuation Now that I look more closely at it, the Overview page could use a bit of work in general. It's the default page... Cory Donnelly

01/08/2010

09:16 AM Feature #363: iCal export format
iCal is a universal export format that really needs to be supported. Paul Beckingham

01/07/2010

06:27 PM Feature #294 (Closed): task cal verbosity
Done.Using @calendar.details@ and @calendar.details.report@ as configuration variables. Federico Hernandez

01/01/2010

12:14 PM Bug #362: Wiki: typo on Getting Started page: lincurse8
Cory Donnelly wrote: > I could have sworn that I didn't have edit rights over the wiki before now. Developer: Cory Donnelly :) David Patrick

12/31/2009

11:38 AM Bug #362: Wiki: typo on Getting Started page: lincurse8
I could have sworn that I didn't have edit rights over the wiki before now. Either someone is messing with me or I need to pay more attention. :) Thanks for making the change, Paul. Cory Donnelly
11:05 AM Bug #362 (Closed): Wiki: typo on Getting Started page: lincurse8
Done. Good suggestion. Thanks Cory. Don't forget it's a a Wiki, so feel free to edit/rearrange as you wish. Paul Beckingham
10:40 AM Bug #362: Wiki: typo on Getting Started page: lincurse8
Currently, the Getting Started page instructs the user to install the "lincurse8" package. The correct name for this package is "libncurses8". Rather than having two places describe the required cygwin environment for building from source, it ... Cory Donnelly

12/30/2009

12:00 PM Bug #361: task command cannot have upper-case characters
Task is lowering the case on all commands, just to do a caseless comparison. This is silly. Paul Beckingham

12/28/2009

08:55 AM Bug #360 (Assigned): Huh? "You cannot remove the recurrence from a recurring task. "
Oh that's definitely a bug, and, it makes no sense. Oops. Paul Beckingham
08:41 AM Bug #360: Huh? "You cannot remove the recurrence from a recurring task. "
I had a few tasks that weren't assigned to a project and since I try to always have one associated, I went to clean them up and encountered this oddity: ... John Florian

12/27/2009

01:52 PM Bug #350 (Closed): deleting multiple tasks uses wrong confirmation dialog
Paul Beckingham
01:51 PM Feature #352 (Closed): rc file should support includes
Syntax is: ... Paul Beckingham
11:30 AM Task on the Sharp Netwalker
ArchiMark has got task running on the Sharp Netwalker. This tiny handheld device is running Ubuntu, so this is a full-featured device, and capable of running task well. ArchiMark, I wonder if you can get DropBox on the Netwalker, and share those... Paul Beckingham
11:24 AM netwalker-task.jpg
Sharp Netwalker running task Paul Beckingham
11:24 AM netwalker.jpg
Sharp Netwalker Paul Beckingham

12/23/2009

11:51 AM Feature #359: Cross referencing task IDs
Paul Beckingham wrote: > I love the idea of connected tasks. This feature keeps cropping up, and is highly desirable. There are problems though - while everyone agrees that task hierarchies, linkage, and dependencies are all things we want, no ... David Patrick
11:08 AM Feature #359: Cross referencing task IDs
I love the idea of connected tasks. This feature keeps cropping up, and is highly desirable. There are problems though - while everyone agrees that task hierarchies, linkage, and dependencies are all things we want, no one has yet been able to p... Paul Beckingham

12/21/2009

03:31 PM Feature #359: Cross referencing task IDs
this is directly analogous to RedMine's Related Issue links (look up) How about this ? if an annotation is a single numeric entry, and that entry matches an active task, then those tasks are related. or even, following the redmine example above, ... David Patrick
02:47 PM Feature #359: Cross referencing task IDs
It would be useful if it were possible to do something like: ... John Florian

12/20/2009

09:11 PM Feature #357: task ls/list/long/etc. should match contents of projects too
I'm really, really hoping Santa brings us 1). Cory Donnelly
08:21 PM Feature #357: task ls/list/long/etc. should match contents of projects too
That's quite an elegant home-brew dependency handling scheme, cool! Dependencies (feature #169) are several stops down the track from here, and it'll be fun to share our work-arounds till then (mid 2012 ?) unless there is some breakthrough ... David Patrick
05:44 PM Feature #357: task ls/list/long/etc. should match contents of projects too
David Patrick wrote: > As a side note to Corey, who likes to pile information into the proj:text; > I think the upcoming note:fileref|string will do a better job of holding that additional information. > (and should IT be included in said sea... Cory Donnelly
05:44 PM Bug #358 (Rejected): .taskrc case sensitive - see steps to reproduce
David Patrick
05:27 PM Bug #358: .taskrc case sensitive - see steps to reproduce
It took David's comment for the ramifications to sink in -- I'm with you guys. Please feel free to reject. Cory Donnelly

12/19/2009

02:43 PM Feature #357: task ls/list/long/etc. should match contents of projects too
FWIW, I'm ok with not being able to do a case-sensitive search for all lowercase terms, but I do like Dvaid's proposal for the three options -- I'd most likely have mine set to case-sensitive=no. I'd rather find too much than not enough for the s... John Florian
01:34 PM Bug #358: .taskrc case sensitive - see steps to reproduce
Paul Beckingham wrote: > This is why I'm thinking it is not a bug. > > That said, it would be easy to add case-insensitivity and allow the case you are presenting. If the above doesn't sway you, I'll be happy to put this in 1.9. imho too, it's ... David Patrick
01:14 PM Feature #357: task ls/list/long/etc. should match contents of projects too
yes Ideal scenario; case sensitivity is user configurable, with three options case-sensitive=yes case-sensitive=no case-sensitive=smartcase In my experience, the occasion to search for specifically _lower_ case, is rare, but hey, that's just me... David Patrick
10:05 AM Bug #358: .taskrc case sensitive - see steps to reproduce
Hi Cory, I understand the problem. Here's my position: all custom report definitions need to be lower case, to match the column names that are available. The column labels, however, are comma-delimited free text, and really need bear no relatio... Paul Beckingham
09:00 AM Feature #357: task ls/list/long/etc. should match contents of projects too
David, are you okay with the fact that it would then be impossible to perform a case-sensitive search for a lowercase word? Paul Beckingham
01:18 AM Feature #357: task ls/list/long/etc. should match contents of projects too
I'm with ya John, case sensitivity is a sensitive issue, and a bit hazardous for the forgetful and inconsistent amongst us. Smart-case (as I just noted in your issue #176) is case insensitive _unless_ mixed-case is used, like "This". David Patrick
01:13 AM Feature #176: search with user-controlled case-sensitivity
this is more commonly known as "smart-case" David Patrick

12/18/2009

11:07 PM Bug #358: .taskrc case sensitive - see steps to reproduce
Hi Paul, I think my choice of example was poor -- here it is again, project+ vs. Project+ in report.testcase.sort: ... Cory Donnelly
07:23 PM Feature #357: task ls/list/long/etc. should match contents of projects too
I agree that qualified searches must be treated differently than unqualified. I too really like the idea of widening the scope for unqualified searches. I also think this might be a good time to bring up the importance of being able to do case... John Florian
05:39 PM Bug #358: .taskrc case sensitive - see steps to reproduce
Not a bug, I'm afraid. These entries are column names: * report.foo.columns * report.foo.sort And this entry is labels: * report.foo.labels For example, the label could be: * report.foo.labels=...,Description of the task It just ha... Paul Beckingham
02:44 PM Bug #358: .taskrc case sensitive - see steps to reproduce
I noticed it in report.cmd.sort, it might be elsewhere as well: ... Cory Donnelly

12/17/2009

10:37 AM Feature #357: task ls/list/long/etc. should match contents of projects too
Paul Beckingham wrote: > I'm warming to this one. I think I'd like to see: > To match on: > * description > * annotations > * projects I'm all for allowing an unqualified search to find these things, so long as s query with $ task list desc:fo... David Patrick

12/16/2009

11:24 PM Feature #357: task ls/list/long/etc. should match contents of projects too
I'm warming to this one. I think I'd like to see: ... Paul Beckingham
04:00 PM Feature #357: task ls/list/long/etc. should match contents of projects too
This has happened to me a few times -- I've had to `task ls | grep foo` in order to find a particular task: ... Cory Donnelly
« Previous
Next »
 

Also available in: Atom