From 12/08/2009 to 01/06/2010

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

12/14/2009

11:42 AM Bug #356 (Closed): Report not sorting correctly on completion date
Paul Beckingham
11:41 AM Bug #356: Report not sorting correctly on completion date
I actually happened to be looking at the koji page last Friday and it showed that task-1.8.5 was built successfully. Don't know why it hasn't made it into testing or updates though. John Florian
10:25 AM Bug #356: Report not sorting correctly on completion date
Regarding 1.8.5 and F10 we will have to see when and if 1.8.5 made it into F10. Build was submitted before cut-off date, but you never know with the build-queue list... I can't check right know as the build and update system has a planned-outage f... Federico Hernandez
09:56 AM Bug #356: Report not sorting correctly on completion date
On further review, it may be that the end date is being sorted on, but possibly as an alpha-string rather than a numerical date as I saw the following sequence for one project: 12/10/2009, 12/11/2009, 12/7/2009, 12/8/2009. Hope this helps. John Florian
09:51 AM Bug #356: Report not sorting correctly on completion date
I have the following report defined: ... John Florian

12/13/2009

11:09 PM Feature #193: pcal plug-in
> ... would it not be easiest from both user perspective and programmer perspective, > to have "include all these" and "exclude all these" lists? I think providing the user with a simple filtering mechanism is most important. Listing all high... Paul Beckingham
09:38 PM Feature #193: pcal plug-in
Paul Beckingham wrote: > This one: > Has no results because a task cannot have a project with two values. > No disjoint operations yet (see http://taskwarrior.org/issues/show/142). right, not yet, ok. > > filter=status:pending,proj:foo,bar >... David Patrick
05:02 PM Bug #355: Config::load called twice
It appears that Config::load is called twice, no matter what. Why did I do that? Paul Beckingham
12:07 PM Feature #19 (Closed): TDB support for multiple files
This was actually finished a while ago. Paul Beckingham
11:22 AM Feature #193: pcal plug-in
This one: filter=status:pending,proj:foo,proj:bar Has no results because a task cannot have a project with two values. Those filter elements are all ANDed together. No disjoint operations yet (see http://taskwarrior.org/issues/show/142). ... Paul Beckingham
09:44 AM Bug #354: Unit tests won't build without ncurses
The unit tests need to be built with autotools too. Currently they expect ncurses to be installed, which is not necessarily the case. This is not user-visible. Paul Beckingham

12/12/2009

06:11 PM Feature #193: pcal plug-in
well that's dandy! just the ticket! and, if I may ask, what of filter=status:pending,proj:foo,proj:bar because filter=status:pending,proj:foo,bar would not work (?) (comma separation collision ?) Or perhaps I'm confusing behavior at the cli ... David Patrick
05:10 PM Feature #193: pcal plug-in
filter=status:pending,proj.not:foo,pri.not:l That would give you a report of pending tasks that were not project foo and had either no priority, H or M. Paul Beckingham
04:53 PM Feature #193: pcal plug-in
Paul Beckingham wrote: > Sorry, it's the other way around. The filters filter in, not out. then how would "filter=status:pending,proj.not:foo,pri.not:l" behave ? > Guess it's more of a selector than a filter, huh? I think so. more like "includ... David Patrick
01:57 PM Feature #193: pcal plug-in
Sorry, it's the other way around. The filters filter in, not out. Guess it's more of a selector than a filter, huh? Paul Beckingham

12/11/2009

11:52 PM Feature #193: pcal plug-in
In futzing with pcal and the resulting printed calendars, I have a couple of potentially effective (and/or annoying) ideas, that may spawn new #features. They are both related to the report/export intended for pcal processing (but applicable anywh... David Patrick

12/09/2009

07:29 PM Support #353: Decision required on case sensitivity in confirmation dialogs
For me: * [no] as default makes most sense * as a rule I think case sensitivity is a bit of a pain * I don't see any pressing need to perform bulk undos, but if Paul/David feel frisky... :) Cory Donnelly
05:06 PM Support #353: Decision required on case sensitivity in confirmation dialogs
I am going to advocate for [no] as the default action for bulk changes. [OOPS! Fredde, I edited, instead of quoted your post.. .. you were saying ? That sounds like a good default, especially if I can change it to [all] and even more so if it we... Federico Hernandez
04:57 PM Support #353: Decision required on case sensitivity in confirmation dialogs
I wouldn't advocate case sensitivity in confirmation dialogs, that sounds annoying. I may have _seemed_ like I was pushing for it, as I drew my mock-up dialogs with a capitalized letter, but that was to indicate the default action on <enter>, not ... David Patrick
04:48 PM Support #353: Decision required on case sensitivity in confirmation dialogs
If you make a bulk change that affects three tasks, then you have three separate undo operations, because the undo is not also bulk. That might make a nice enhancement - to make either a single or batch undo. Would it be easy? No. No it woul... Paul Beckingham
04:36 PM Support #353: Decision required on case sensitivity in confirmation dialogs
I consider myself a unix guy and would not assume a default action for this confirmation dialog. A default answer for me is @[yes]@ or @yes/[no]/all/quit@. When using @rm -i@ the _-i_ is step one in the confirmation, _y_ is step two. Using @Yes... Federico Hernandez
04:00 PM Bug #347 (Closed): Confirmation dialog is lowercase for "all"
Federico Hernandez
03:29 PM Feature #352: rc file should support includes
agreed 100% and as I'm delighted to find, the .calendar format supports them, too. include.cal ~/.task/canadian.holidays.calendar include.cal ~/.task/usergroups.calendar or just include.cal ~/.task/MyCalendar and it #includes the rest it _w... David Patrick
02:22 PM Support #353: Decision required on case sensitivity in confirmation dialogs
It's come up a few times in the past week or so -- I misinterpreted a deliberately-implemented feature for a bug in Issue #346, Federico corrected me and submitted the inverse in Issue #347, and then David was confused in Issue #350. I think we... Cory Donnelly
11:54 AM Feature #352: rc file should support includes
The rc file should support include files, like this: ... Paul Beckingham
10:50 AM Feature #351: milestones; a measure of success
A project is just a multi-step task. In project management, milestones are used to indicate completion of important stages of a project. A milestone is not a task itself, but a marker to indicate progress. Milestones could be implemented a... David Patrick
08:58 AM Feature #337: productivity rewards
tcharles yun wrote: > i want to chime in that this is a great idea; i like it; i want it. and eventually, you shall have it! my question is how milestones are visualized during a simple `task list` scenario. There are two distinct thin... David Patrick

12/08/2009

08:51 PM Feature #343: Allow spaces in Projects
I want to say no, too, but I'm not sure how much of that is based on my own usage. (I would not use it) Should it be possible ? Is there a logical reason to want this ? Is there a technical reason not to do this ? I can not say.. David Patrick
08:18 PM Bug #350 (In progress): deleting multiple tasks uses wrong confirmation dialog
Federico Hernandez
08:13 PM Bug #350: deleting multiple tasks uses wrong confirmation dialog
bulk delete with confirmation; yes in the first example above, Proceed with change? (Yes/no/All/quit) only ONE (or none) options should ever be capitalized, indicating default action on <enter> David Patrick
07:47 PM Bug #350: deleting multiple tasks uses wrong confirmation dialog
I say yes, provided it needs confirmation. If we prevented bulk deletes, I don't think it would be too long before someone asked for it. Paul Beckingham
07:29 PM Bug #350: deleting multiple tasks uses wrong confirmation dialog
The question is should we permit bulk operations for the delete command? Federico Hernandez
07:24 PM Feature #193: pcal plug-in
an excellent .calendar, including undated tasks, could easily be generated by an external script (warning; psudo-code ahead) $ task export.calendar proj:foo,bar due.any: > FooANDBar.calendar # filtering out due.none: $ echo '$TOMORROW ... David Patrick
07:09 PM Feature #193: pcal plug-in
undated tasks in export.calendar problem partially solved; solution inherited! After closer inspection of pcal documentation, it seems that if a [description] does not have an associated date, then that date is inherited from the event above. Thi... David Patrick
07:02 PM Feature #343: Allow spaces in Projects
I want to say no, only single word tags. But I don't have a good reason. I need to defer on this. David? Paul Beckingham
06:34 PM Bug #347 (In progress): Confirmation dialog is lowercase for "all"
Federico Hernandez
06:34 PM Bug #350 (Assigned): deleting multiple tasks uses wrong confirmation dialog
Federico Hernandez
06:34 PM Bug #350: deleting multiple tasks uses wrong confirmation dialog
When changing multiple tasks a 'Yes/no/All/quit' confimation dialog is shown. For example: ... Federico Hernandez
06:22 PM Feature #337: productivity rewards
i want to chime in that this is a great idea; i like it; i want it. my question is how milestones are visualized during a simple `task list` scenario. specifically, what happens when one has tasks with different: due dates, project names, et... t charles yun
05:47 PM Feature #343: Allow spaces in Projects
would this thinking apply to tags as well? task add "woo hoo" +"i get to use spaces in tags too!" t charles yun
12:40 PM Bug #348: task done a little over zealous
I do generally use the form: ... John Florian
« Previous
Next »
 

Also available in: Atom