From 10/27/2009 to 11/25/2009
11/25/2009
- 11:06 PM Bug #160: shrink name display
- Is this issue still valid? If it is, what about one of below styles? 1. David Patrick => David P. Jin-young Heo => Jin-young H. 2. David Patrick => D. Patrick Jin-young Heo => J. Heo 3. David Patrick => D. P. Jin-young Heo ...
- 10:53 PM Bug #134: css trainwreck on resize web page width
- Do you mean that reducing side space of each main menu tab (Overview, Activities ....)?
- 10:51 PM Bug #113: css: re-order main menu tabs; alphabetical
- Done. The forum is another name of board. The menu ordering is determined by "menu.push" sequences in ~/public_html/redmine/lib/redmine.rb (from line 108 ~ 150)
- 09:59 PM Bug #113: css: re-order main menu tabs; alphabetical
- Re-ordering was completed except "Forum". Forum doesn't follow a common menu rule like other menus. I'm searching where it's generated.
- 09:37 PM Bug #180: remove redmine references to "other projects"
- Sorry too late. Anyway the top menu and select box has been removed. !! IMPORTANT !! This modifying is temporal fix for only our source of redmine on taskwarrior.org server. If someone upgrades or changes it with another version (new versio...
11/24/2009
- 11:40 PM Bug #320 (Closed): color reference system needed
- 10:32 AM Visualizing task development
- Take a look at the video that visualizes the development of task 2.0.0 at http://www.youtube.com/watch?v=AqGZNne-q70
11/20/2009
- 07:35 PM Bug #320: color reference system needed
- David, this is going to make your day. The colortest script you are running generates output like: 16: 00/00/00 17: 00/00/5f 18: 00/00/87 19: 00/00/af 20: 00/00/d7 21: 00/00/ff etc That number in the first column (16, 17, 18, 19, 20, ...
- 10:52 AM Bug #320: color reference system needed
- On my system (ubuntu) colortest creates such a list, is there any chance that the numbers on the left might correspond to the taskwarrior color numbers ? djp@orange:~ $ colortest ************************** *XTERM 256Color Test Chart ***********...
11/19/2009
- 12:10 AM Bug #320: color reference system needed
- although 256 colors are now possible, it seems the color numbering system is unique. We need some method of cross referencing to a known color scheme, where sample tables exist, or we need task to generate its own reference table, something lik...
11/18/2009
- 03:57 PM Bug #319: Removing tag from multiple tasks at once causes incorrect change summary
- Experienced in version v1.8.3. Removing an existing tag from multiple tasks causes the 'No changes were made' message to be displayed for each task, even though an action was performed. Here the tags are added: ...
- 02:48 PM Feature #318: timestamp for status changes
- Cory Donnelly wrote: > For all statuses, when status is changed, an associated date value should be set (statusdate:"1258403641" perhaps?) I think that with the combination of existing task and history data, and minor enhancements of existing repo...
- 11:45 AM Feature #318: timestamp for status changes
- Interestingly, we already have this information in the undo log. How would you like to see it presented? Just on the "info" report? Somewhere else?
- 11:29 AM Feature #318: timestamp for status changes
- (was: All statuses should store an associated date value) Currently in v1.8.3, completing a task causes the task to be moved to completed.data, status is set to "completed", and an end value (end:"1258403641" for example) is added. This could ...
- 11:22 AM Bug #317 (Assigned): Output produced by `task completed` shouldn't use due-related colouring
- Good point, Cory. If a task is completed, due date is meaningless. Thanks.
- 11:18 AM Bug #317: Output produced by `task completed` shouldn't use due-related colouring
- For completed tasks, colouring them according to color.overdue and color.due no longer really makes sense. Since `task completed` is just a regular report specified within .taskrc this might be more trouble than it's worth to address -- I can't...
- 09:51 AM Bug #222 (Assigned): make test data set available
- 09:51 AM Bug #222: make test data set available
- Ah, I see. That makes a lot of sense. A sandbox.
- 09:43 AM Bug #222: make test data set available
- I was referring not so much to your battery of software tests, as I was to a sample.data file that was packed with imaginary examples of tasks, using every feature, for a whole imaginary family; something for new users and experimenters to play with.
- 12:44 AM Bug #211: usage of "update" missing from help output
- Ah. Yes. When you do either of the following: ...
- 12:20 AM Bug #211: usage of "update" missing from help output
- Paul Beckingham wrote: > Please elaborate. in an IRC discussion, if I recall correctly, you described a seemingly undocumented command "update". (existing usage, as opposed to a future, expanded implementation) did I imagine that ? if s...
11/17/2009
- 11:18 PM Bug #222 (Rejected): make test data set available
- All unit tests generate their own data immediately prior to running the test, then clean up after. Therefore I don't think this is important.
- 11:16 PM Bug #211: usage of "update" missing from help output
- Please elaborate.
- 11:12 PM Feature #239 (Closed): i8 - stats panel
- 11:11 PM Feature #238 (Closed): i7 - keys panel
- No asynchronous message posting. Not needed.
- 11:08 PM Bug #315 (Assigned): Unexpected behaviour - marking task as done releases task ID
- You're right, this is not consistent with intended behavior. It is also inconsistent with this simple test: ...
- 10:57 PM Bug #316 (Closed): timesheet report oddly sorted
- It happened 20090922. Hmm.
- 10:50 PM Bug #316: timesheet report oddly sorted
- The timesheet report is broken - all the group headings appear first, then the data. When did this happen?
- 10:50 PM Bug #315: Unexpected behaviour - marking task as done releases task ID
- Consider: ...
- 06:31 PM Task 1.8.4 is released
- See the *"task 1.8.4":http://taskwarrior.org/wiki/taskwarrior/V184* page for details.
11/16/2009
- 11:02 PM Bug #312 (Closed): Applying changes to one task affects another
- No fix because this is intended functionality. Added warning when modifying a recurring task that all instances of the recurring task may be modified. Further identified all recurring tasks when asking the "Are you sure?" question.
- 10:44 PM Bug #312: Applying changes to one task affects another
- After puzzling over this one I realized that the two tasks are related. 78 is the parent task of 79. This can be seen with: task info 78-79 This is therefore functioning as designed - edits to a recurring task are propagated to other i...
- 10:27 PM Bug #208: 'task recurring' not listing all recurring tasks
- Cory's sample pending.data file does indeed exhibit the bug. Task 40 in the sample file does not have the parent:xxxx attribute, and as such doesn't qualify as a recurring task. Whether or not the filtering logic for selecting recurring tasks is...
- 10:02 PM Bug #313 (Closed): Edit command fails when data.location includes directories containing spaces
- Nice patch. Thank you.
- 09:56 PM Feature #298 (Assigned): Configurable recurring task count
- 09:55 PM Bug #306 (Assigned): add tags to annotations
- 09:53 PM Bug #311 (Assigned): tab completion knows about 'waiting', not 'wait'
- 09:53 PM Bug #314 (Assigned): tab completion knows about 'recurring', not 'recur'
- 09:52 PM Bug #313 (Assigned): Edit command fails when data.location includes directories containing spaces
- 09:51 PM Bug #312 (Assigned): Applying changes to one task affects another
- 01:55 PM New preview movie
- It shows change highlighting and multi-user access. You may need to watch on high quality because the text is small. http://www.youtube.com/watch?v=9CyCxvhvFMo
- 11:16 AM Bug #314: tab completion knows about 'recurring', not 'recur'
- See Bug #311 for waiting/wait.
- 11:11 AM Bug #313: Edit command fails when data.location includes directories containing spaces
- Experienced under v1.8.3 running on cygwin, likely elsewhere as well. Trivial patch attached.
- 08:58 AM Bug #312: Applying changes to one task affects another
- Please disregard the inconsistency in the description of task 79 in the above output of `t strangeness 79` -- in testing bug #208 I mangled this output. In the lines beginning 'Task [78|79],' the descriptions of both tasks were reported correctly ...
11/15/2009
- 10:39 PM Bug #312: Applying changes to one task affects another
- I experience this issue under v1.8.3. Updating the description (specified by task ID) causes the description to be updated for another task as well. May be related to Bug #208. Most data in the attached database were initially imported from to...
- 10:30 PM Bug #208: 'task recurring' not listing all recurring tasks
- I'm currently experiencing this issue under v1.8.3. See the attached database. ...
- 06:23 PM Bug #311: tab completion knows about 'waiting', not 'wait'
- Admittedly one is a report name, and the other an attribute, but I think the tab completion might be making an assumption about argument order. Reported by Cory Donnelly.
11/12/2009
- 12:33 PM Feature #307: taskrc.vim
- John Florian wrote: > I'm leaning towards the first route. How can I get a complete list of valid keywords? If you know any really good programmers who are intimate with the inner workings of task, and who ALSO happen to live in the Boston area...
- 11:17 AM Feature #307: taskrc.vim
- I'm leaning towards the first route. How can I get a complete list of valid keywords? Would just having task create a brand-new default ~/.taskrc be sufficient? Even this route will have to be somewhat dynamic to handle "report.ANYTHING_HERE....
- 09:20 AM Feature #307: taskrc.vim
- John Florian wrote: > Are we talking about highlighting of ~/.taskrc itself ? yes When I edit mine vim uses syntax=conf by default probably because of the comment style. For me this is pretty normal as most conf files all look the same and I...
- 09:15 AM Feature #310: 'task add' with external editor
- 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 typin...
- 08:55 AM Feature #310 (In progress): 'task add' with external editor
- Good idea, leading to a much cleaner error message.
- 08:40 AM Feature #307: taskrc.vim
- Are we talking about highlighting of ~/.taskrc itself or something else? When I edit mine vim uses syntax=conf by default probably because of the comment style. For me this is pretty normal as most conf files all look the same and I really only ...
- 08:27 AM Feature #310: 'task add' with external editor
- 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. ...
11/08/2009
- 08:37 PM Feature #53: Incorporate a pager
- Paul Beckingham wrote: > I'm still confused by: > > color.pager.bg=nicecolor I'm sorry, I should have prefaced it with suggestion that the above line might be a new .taskrc setting, not a new function. > > The output from task is gen...
- 04:30 PM Feature #53: Incorporate a pager
- I'm still confused by: color.pager.bg=nicecolor The output from task is generally already colored by various rules. Does this new color: a) add a background color to whatever task is already using, for all output? b) replace whateve...
- 04:12 PM Feature #53: Incorporate a pager
- Paul Beckingham wrote: > Need some clarification here. The original request from Bruce was to use a pager for long output, or in other words, when there is more than a screenful of output. The pager in this case is any piece of software that doe...
- 02:10 PM Feature #53: Incorporate a pager
- Need some clarification here. The original request from Bruce was to use a pager for long output, or in other words, when there is more than a screenful of output. The pager in this case is any piece of software that does what "less" and "more" ...
11/07/2009
- 06:55 PM Feature #53: Incorporate a pager
- the pager means another color option; color.pager.bg=nicecolor
- 04:06 PM Feature #309: xterm title output
- if we're uxing task with an xterm window (and you know we are) I think it would be swell to have some data passed to the xterm window title (like vim does it) so that wherever you are in the data output, you could see the name of the application l...
- 01:25 PM Feature #53: Incorporate a pager
- The upcoming version of "ledger-cli":http://wiki.github.com/jwiegley/ledger (which is going to be flat-out awesome) has moved to a pager for output, and it is very likeable. An interesting adjunct to the pager might be the option to allow a re-d...
- 12:04 PM Bug #308: task shell needs tab completion, history and color
- Another thing that would make the shell super-fine, is color. If each key-stroke is evaluated (and I think it is) then having color added as soon as the input string matches (even before hitting <enter>) would not just be sassy, it would be usefu...
- 11:27 AM Bug #308: task shell needs tab completion, history and color
- right now, task shell, which promises to deliver faster data entry, loses the tab-completion, and thereby some of it's promise. Maintaining a history list, to be scrolled through with the up-and-down arrows, would also be a boon. Answering promp...
11/06/2009
- 11:56 AM Feature #61: File attachments
- question; should the _note:something_ field be a reference to an external file or to a data field within a task data file ? answer; either Very simply, (in concept) if the string that follows the "note:" is parse-able as a file reference, then...
11/05/2009
- 09:57 AM Feature #193: pcal plug-in
- The main challenges here revolve around the conversion of recurrent dates and date ranges. the .calendar format that pcal (and a surprising number of other things) use, is quite different, and recurrent date tasks will require a new parameter (sta...
- 12:37 AM Feature #307 (Assigned): taskrc.vim
- John is really good at making these...
11/04/2009
- 09:00 PM Feature #307: taskrc.vim
- the syntax highlighting file. should happen, at some point
10/31/2009
- 02:49 PM Bug #306: add tags to annotations
- I just ran this test: task add foo task annotate 1 bar +baz The annotation ("bar") is added, but the tag ("+baz") is not. Task should probably warn about that.
- 01:11 PM Bug #306: add tags to annotations
- I think that +tags within annotations is like a can of worms within another can of worms; messy and hard to open. The good news is that you can do what you are asking for (sort of) with existing functionality. If you had to organize a skating par...
10/29/2009
- 10:28 AM Bug #306: add tags to annotations
- It may be useful to be able to tag annotation. I'm not sure yet for the actual use case, but i could imagine to attache one or more tags to an annotation, like FAIL, PASS, POSTPONE, TODO. I'm coming with this because i have a task, which is kind...
Also available in: Atom