From 08/05/2010 to 09/03/2010
09/02/2010
09/01/2010
- 11:06 PM Bug #476 (Closed): User can specify due: dates that are before wait: dates
- Now generates warnings.
- 10:48 PM Bug #485 (Assigned): inconsistency using partial strings: recur vs proj
- Ooh, this is a tricky one. The problem here is that recurrence periods are stored in original form ("monthly") and not expanded to a number of seconds, because that is not what you want to read on the 'long' report. Then the filter is specif...
08/31/2010
- 10:46 AM Bug #469: Recurring Tasks Broken for My Date Format
- Paul, excellent. I shall follow your instructions, and stop re-creating my recurring tasks when I don't see them right away ;)
- 09:28 AM Bug #485: inconsistency using partial strings: recur vs proj
- if i ask for monthly, i get results. if i ask for month, i get none. I can partially write project names, it seems not recurrences... Unclear if this is a true bug. ...
- 09:10 AM Bug #469: Recurring Tasks Broken for My Date Format
- Thanks for the additional data. When I take the lines searched from your pending file, and put them in my own test file (line numbers removed), I get this: ...
- 07:39 AM Bug #469: Recurring Tasks Broken for My Date Format
- Paul, re your comment #5, here is what I see when I explore the pending.data file. (I have tried not to delete or add any more recurring tasks, but I have marked at least one weekly status as done.) ...
- 01:26 AM Bug #469: Recurring Tasks Broken for My Date Format
- Regarding trace.txt, what you are seeing is correct behavior, if not expected behavior. Taskwarrior tries to limit the amount of future recurring tasks it generates to all overdue tasks, and one task into the future. This is controlled by rc.r...
- 01:13 AM Bug #469: Recurring Tasks Broken for My Date Format
- I've been looking at the recurrence code, and fixed one bug. I don't think it is related to this though. I also don't think your (unusual) date format is to blame. I've also been looking closely at the data provided. There are oddities. Fir...
- 12:06 AM Bug #483: Color.due.today depends on Midnight due time?
- Nice bug! Here's the problem, or a big part of it - the definitions of due and overdue: overdue: a task is overdue if its due date/time is before the current date/time, ie before 'right now'. For example: ...
08/30/2010
- 11:36 PM Bug #461 (Closed): due:today doesn't work as a filter - due.is:today does
- 08:47 PM Feature #351: milestones; a measure of success
- for sorting and reporting goodness, meta.#stepnumber.proj.foo="step title" stepnumber (integer) could affect the coefficient, and used with step-breaks could give projects yet another dimension. ...
- 08:03 PM Feature #484: task cost < filter >
- by hook or by crook, but flexible costing would be a desirable feature. You're probably right Fredde, as I can see this function being highly customized and connected to unforeseen things, so non-core makes sense. That would be transparent to ...
- 06:49 PM Feature #484: task cost < filter >
- I don't know. But I see this as a perfect example for a hook function and would not add this to the core.
- 05:57 PM Feature #484: task cost < filter >
- Looks like I need to sanction "." as well.
- 05:52 PM Feature #351: milestones; a measure of success
- if we like project and tag metadata, milestones could easily piggyback, using syntax suggested for PTM ;-) Milestones can be thought of as steps, and steps can be numbered, and the third new tag character is looming, so why not think of that sp...
- 01:46 PM Feature #484: task cost < filter >
- Using the recently sanctioned "$" symbol with tags, as in % task add proj:foo +$220.25 due:now make life more complicated for Paul % task add get catfood +$23 +@shopping we could add an exciting new Project Management feature with a ne...
- 08:43 AM Bug #483 (Assigned): Color.due.today depends on Midnight due time?
- Thanks for the screenshots and detailed writeup.
- 08:22 AM Bug #483: Color.due.today depends on Midnight due time?
- Background: I'm using @dateformat=Y-M-D.H:N@ as my date format. When I create a due item, I add in the time, usually 16:00, i.e., the end of my work day. I've also got settings for colouring my due items, e.g., ...
08/29/2010
- 12:58 PM Feature #481 (Closed): colors should follow rc order
- 11:15 AM Feature #481: colors should follow rc order
- Excellent points. The format will now be: ...
- 04:39 AM Feature #481: colors should follow rc order
- There is a lot of redundant information in the precedence declaration: color.*. I think we could make it more general and move the color string to the left hand side of the equals sign: ...
- 12:58 AM Feature #481: colors should follow rc order
- if the priority rules are grouped like that, then color.pri.any should serve as well, there ca be only one, as in rule.precedence=color.due.today,color.active,color.blocked,color.due.overdue,color.due,\ color.keyword.*,color.project.*,color...
08/28/2010
- 11:16 PM Feature #481: colors should follow rc order
- This is almost implemented, as is color.project.none. I want to take David's suggested precedence as is, as the default. But we need to make a big change. If task remembers the order in which the color rules appear, it still doesn't account f...
- 07:26 PM Feature #481: colors should follow rc order
- and then moved blocked higher still, because if something is due AND blocked, blocked is the more important information, and it will still be sorted within other due items.
- 04:00 PM Feature #481: colors should follow rc order
- i tweaked "blocked" a bit higher
- 11:11 AM Feature #481: colors should follow rc order
- Paul Beckingham wrote: > This can be changed easily, but is hard-coded. and this is why the order should be user-configurable ;) > Note that there is no "color.project.none", and your list is incomplete. I knew that, and I knew that,too I also...
- 08:09 AM Feature #481: colors should follow rc order
- I added: http://tasktools.org/gitweb/gitweb.cgi?p=rfc.git;a=blob_plain;f=rfc23-color-rules.txt;hb=HEAD
- 07:48 AM Feature #481: colors should follow rc order
- The color rule precedence is currently: ...
- 12:36 AM Feature #481: colors should follow rc order
- Until such time as color rules are sequenced by listing order, is it an easy thing re-jig the order ? I think the order of precedence should be something like color.due.today= color.active= color.overdue= color.due= user.defined.rules= (?) col...
08/27/2010
- 10:46 PM Feature #482: due:now
- Actually, that one was done in -28 days. Beat that!
- 10:36 PM Feature #482: due:now
- Let no one say that the taskwarrior developers aren't responsive.. feature request to completion; four minutes!
- 10:28 PM Feature #482 (Closed): due:now
- Fixed in 1.9.3 on 7/30/2010.
- 10:25 PM Feature #481: colors should follow rc order
- Feature request, not a bug. We *want* it to be controlled by order, but it isn't. Yet.
- 10:25 PM Feature #482: due:now
- how come due:today works, but not due:now "now" is not a valid date (m). ? but it should be a valid date AND time feature ? bug ? oversight ?
- 10:18 PM Feature #481: colors should follow rc order
- A given task may be subject to many conflicting color rules, which one will display ? It is supposed to be determined by the order in which the colors are listed in .taskrc, but changing that order doesn't work for me. (task 1.9.2, including d...
08/26/2010
- 12:30 AM Feature #473: project and tag metadata
- Paul Beckingham wrote: > We just need to standardize on what metadata is supported. Maybe we could leave the method loose and arbitrary, "supporting" anything that will parse, but reserve a few terms that taskwarrior will use internally. m...
08/24/2010
- 09:04 PM Bug #450 (Rejected): Instances of recurring tasks appearing inconsistently
- I've changed my mind, and no longer think this is a bug. Here is what task is doing: Whenever task detects a gap, it generates all the recurring tasks to fill that gap. Task considers the entry date/time of the task, and all the recurring da...
- 07:06 PM Bug #480 (Closed): @ Symbol in context not returning
- Now #, $ and @ are allowed/supported in tags.
- 05:44 PM Bug #480: @ Symbol in context not returning
- Good eye. Since the @ character is very frequently used as an indicator for "contexts" in the GTD world (and tags are the best way to represent contexts in Taskwarrior) I think we should allow it in tag names. Common GTD contexts are @home, @work,...
08/23/2010
- 11:52 PM Bug #480: @ Symbol in context not returning
- Found it - a tag is defined as non-space, non-punctuation, and '@' is considered punctuation by the ispunct(3) function. Having found it, need to decide what to do about it, because it is not a straightforward fix.
- 10:38 PM Feature #473 (Assigned): project and tag metadata
- I get it now. I like it. Thanks. Here is how I think it could improve taskwarrior: * The "projects" report could show title * The "tags" report could show description * The "summary" report could show project title * Listing breaks coul...
- 10:12 PM Feature #473: project and tag metadata
- Paul Beckingham wrote: > Taskwarrior stores tasks. Projects are attributes of tasks, and not first-class data items themselves. Absolutely right, taskwarrior sees a Projects as an optional attribute of a task, and that's not likely to change, an...
- 06:06 PM Feature #457: New 'expire' attribute representing the absolute last day a task could be completed
- I too would be fine with the deletion, but really like Davids thought of adding an annotation. Also, I agree with Fredde in that an expiry date is independent of a due date -- they may be used together, but shouldn't be required as such.
- 05:56 PM Syntax festival
- Read more in the forum at http://taskwarrior.org/boards/6/topics/show/682
- 04:33 PM Bug #450: Instances of recurring tasks appearing inconsistently
- Sorry, 'm' is an alias for './task rc:minimal.rc' -- I tried to replace all of those with 'task' for clarity but obviously goofed.
- 04:01 PM Feature #413 (Assigned): Show more info in confirmation dialogs
- 04:01 PM Bug #447 (Assigned): Trouble Editing Task Due Date
- 03:58 PM Bug #450: Instances of recurring tasks appearing inconsistently
- This is a bug. I think recurring tasks are generated by the handleRecurrence call, that generates all the missing tasks starting from "now" and ending at "tomorrow" or "when recurrence.limit is exceeded", whichever comes last. It's a simple fi...
- 03:48 PM Bug #467 (Assigned): Recurring tasks don't honour wait values
- 03:44 PM Feature #473: project and tag metadata
- Taskwarrior stores tasks. Projects are attributes of tasks, and not first-class data items themselves. In the case of projects, the optional data is retained, and can be used in a filter and a sort field. Now until #471 came along, there was no...
- 03:25 PM Bug #476: User can specify due: dates that are before wait: dates
- David, do you think if we relax the hiding of waiting tasks, that it then creates a need for a stricter version of wait as well? Waiting was added as a way to get tasks out of the reports, for example with an annual recurring task, you may not wa...
- 03:22 PM Bug #476 (Assigned): User can specify due: dates that are before wait: dates
- I agree with Cory and David, in that I don't like to see task enforcing the notion that wait < due, but should certainly generate a warning.
- 03:18 PM Bug #475 (Assigned): annotate just a number cause an error
- 03:16 PM Bug #480 (Assigned): @ Symbol in context not returning
- 03:15 PM Feature #477: create and exchange website banners
- Wouldn't we need a real logo?
- 03:03 PM Feature #479 (Assigned): task calendar < filter >
- I wonder why I never added filters. Hmm.
- 09:50 AM Bug #480: @ Symbol in context not returning
- Super SoBBie wrote: > ok so if I put a +PC in my report I get those. It appears that it is not recognizing the @ at all. If you notice, I also changed a few to tags to know I have the following tags returning, "PC" "@PC" "PC-Work" "@PC-Work" ...
- 09:14 AM Bug #480: @ Symbol in context not returning
- Something else that I found a little odd is the following: ...
- 07:43 AM Bug #480: @ Symbol in context not returning
- Confirmed -- I thought it might have been the parser misunderstanding the '-' character in your example, but a @task add +@tag Foo; task ls +@tag@ also fails.
08/22/2010
- 11:27 PM Bug #480: @ Symbol in context not returning
- Good Morning. I have just run into a very strange thing. For some reason when I create a task with the tag +@PC-Home it creates it fine, but when I try to list all tasks for +@PC-Home it does not return anything. I am currently trying to make a...
- 12:23 PM Wikipedia article
- Check it out at http://en.wikipedia.org/wiki/Taskwarrior
- 12:14 PM Feature #479: task calendar < filter >
- I use *task cal* all the time, to keep the topmost tasks in focus, and it occurs to me that the ability to view a calendar report specific to < filter > would be great. example; % task cal proj:baz pri:l
- 11:25 AM Feature #448: Create recurrences based on end dates in addition to due dates
- This is functionality that has great interest to me as well. I have about an equal split of tasks of the "normal kind" and those that are preventive maintenance. Oil changes are definitely preventive and as stated above need to essentially be re...
08/21/2010
08/20/2010
- 11:58 PM Feature #471 (Closed): Enhancements to the project: attribute - feedback on completion
- Note that this feature requires that the pending.data and completed.data files are read on all commands that modify project (commands that *do* modify project, not commands that *can*), and consequently "task add", which was once the fastest comma...
- 11:15 AM Feature #478: themed info reports
- Let's extend the theming to *task info*, as I think it will be just as useful there, and can still be rendered colorless (if desired) with an rc override.
- 10:50 AM Feature #477: create and exchange website banners
- Looking at the Overview page, it occurs to me that our website could/should support banners, as shout-outs to the supporters and to the supporting Free Software projects. This will help us clean up the landing page while spicing up the site in gen...
- 10:20 AM Bug #476: User can specify due: dates that are before wait: dates
- the wait:< date > feature is necessary and powerful but has the potential for confusion. firstly, the status:waiting is scheduled for removal, and will leave the wait function resting on the wait: < value > attribute, so that it _will_ be possibl...
- 08:46 AM Bug #476: User can specify due: dates that are before wait: dates
- Cory, w/r/t your first point, some points for discussion. I guess some of the options are: 0) leave as is 1) prevent user from creating task when wait is after due. I agree that this is harsh. 2) throw a text warning stating that the...
- 08:08 AM Bug #476: User can specify due: dates that are before wait: dates
- Hi Charles, You bring up two issues in this ticket: 1) Users can create a task that has a due date before a wait date. I personally don't like *preventing* users from doing things, but it definitely deserves discussion. 2) User can't comp...
- 04:21 AM Bug #476: User can specify due: dates that are before wait: dates
- ahh, and it seems that you can not mark "done" a pending/waiting task but you can delete it. not sure that i understand the thinking behind this. but i also acknowledge that this is a really weird corner case.
- 04:08 AM Bug #476: User can specify due: dates that are before wait: dates
- maybe this is a bug? I am assuming that task should catch the fact that a due date should be after the wait date... or is this a bad assumption? tcyun@macos ~/tcy-script/tbird-logtool $ t add due:tom "backwards" wait:2010/08/30 Created ta...
- 12:24 AM Bug #469: Recurring Tasks Broken for My Date Format
- Michelle, we have had several bug reports of misbehaving recurring tasks, so something is clearly amiss under certain circumstances. We even have a pending.data file that contains some kind of problem that causes this, but we've never been able t...
08/19/2010
- 11:07 PM Feature #474: task info <filter>
- (changed from bug to feature request)
- 06:55 PM Feature #474: task info <filter>
- Functioning as designed. You may want this on the Great New Parser Syntax Wishlist, because that conversation is coming up soon.
- 06:53 PM Bug #475: annotate just a number cause an error
- That's a bug that we'll be fixing with an improved parser. For now, the workaround is this: ...
- 05:17 PM Bug #475: annotate just a number cause an error
- I want to annotate only a telephone number to a task and get an error message: ...
- 04:48 PM Feature #474: task info <filter>
- Well, according to the man page ...
- 04:25 PM Feature #471: Enhancements to the project: attribute - feedback on completion
- 1) I think it should be "remaining" as you directly see what is interesting: how many tasks are left todo and you don't need to compute that yourself as with "completed. Regarding the fraction: what about "2 of 5 tasks remaining". Fractions confus...
- 02:37 PM Feature #474: task info <filter>
- Currently, *task info ID(s)* produces a full display of task information (or a series of such displays) in a very useful way. I think that it might be more useful still if task info < filter > as in task info proj:foo due:eom could...
- 12:37 PM Feature #473: project and tag metadata
- Creating a project is easy, just make a task and give it a project, but is that all you need to work with a project ? If you are a GTD-head, the answer a a clear "No"; a project should have a full description, established purpose and principals, ...
- 10:29 AM Feature #472: grouping
- Tasks can be related by projects and tags, but these connections fall short when attempting to relate on a larger scope, as in (GTD) Areas of Responsibility, 5 Year Goals or Life Goals. I'm proposing a new feature that will allow arbitrary groupin...
- 08:23 AM Feature #471: Enhancements to the project: attribute - feedback on completion
- I agree with everything you pointed out, Fredde. 1) Regarding the 'remaining' part of the project status display, I think it's a good time to start thinking about how configuration fits into the style/format defined in rfc14. This sounds like ...
- 02:22 AM Feature #471: Enhancements to the project: attribute - feedback on completion
- I would like to see the @remaining@ part as well. There could be a config variable that turns the feature off, sets it to sparse only displaying the percentage or full showing both percentage and total numbers. I think 2 cases needs some specia...
08/18/2010
- 08:55 PM Feature #351 (Assigned): milestones; a measure of success
- 08:54 PM Feature #471 (Assigned): Enhancements to the project: attribute - feedback on completion
- 08:50 PM Feature #471: Enhancements to the project: attribute - feedback on completion
- Here's what we were thinking: ...
- 12:20 PM Feature #471: Enhancements to the project: attribute - feedback on completion
- In 1.9.2, projects aren't used for much. We've got the cute @task summary@ report, but that's pretty much it. For the most part, the project: attribute is less flexible and no more useful than tags. There are a number of fairly easy project-re...
- 09:18 AM Bug #469: Recurring Tasks Broken for My Date Format
- When I was testing this, I added a few new "testing" tasks, recurring daily. When I couldn't get them to show up in the "recur" command, I would create another one. Now, every morning I'm noticing a whack of "testing" tasks, so they seem to be...
08/17/2010
- 11:19 PM Bug #470 (Closed): task rc.color.alternate:none fails
- 11:07 PM Bug #470: task rc.color.alternate:none fails
- More than fails - uses a strange color. "none" is an allowable color definition, and task doesn't seem to support it. This is also a vitapi bug.
- 08:24 PM Welcome Cory and Johannes
- Taskwarrior welcomes Cory and Johannes to the core development team. Cory and Johannes are already bringing you better design, better support and more significant releases. Thanks guys.
08/16/2010
- 08:46 AM Bug #469 (Assigned): Recurring Tasks Broken for My Date Format
- Thanks Michelle, for that trace.txt - it will help us reproduce this.
- 08:32 AM Bug #469: Recurring Tasks Broken for My Date Format
- I'm back at my normal computer, and tried changing my dateformat back to Y-M-D. But I'm still having trouble with recurring tasks disappearing. I'm attaching both my .taskrc config and a trace showing me creating a daily task, marking it done fo...
08/15/2010
- 02:56 PM Feature #448: Create recurrences based on end dates in addition to due dates
- Paul, at some point there was a discussion about these type of recurrances, IIRC. But I don't know if we did that via email or on IRC. would be useful for you, Cory, if we could dig it up.
- 02:20 PM New development movie
- It can be watched at http://www.youtube.com/watch?v=TLwBXGKm6gM. The movie was done with the help of "gource":http://code.google.com/p/gource, which is a nice tool for visualizing the git log, apache log or other log files. The music comes from "c...
- 12:21 PM Feature #448: Create recurrences based on end dates in addition to due dates
- Paul Beckingham wrote: > I think you've found a new species of recurrence. > > It is similar to the current species, but the subsequent task is only scheduled when the first is dismissed. RFC? Agreed, I'm working on rfc32-recurrences.txt w...
- 08:55 AM Feature #448: Create recurrences based on end dates in addition to due dates
- I think you've found a new species of recurrence. It is similar to the current species, but the subsequent task is only scheduled when the first is dismissed. RFC?
- 08:49 AM Feature #448: Create recurrences based on end dates in addition to due dates
- I'm finding that more and more of my obligations are best modeled using this period-dependent (versus due date dependent) type of recurrence: * Check backup tapes * Get a haircut * Water plants * Bathe the dog * Call mom * Mow the lawn * ...
08/14/2010
- 11:46 AM Bug #469: Recurring Tasks Broken for My Date Format
- Using the newest version, I've noticed a distressing tendency for my recurring tasks to fail. By fail, I mean, I mark that task as done but the next one does not show up. I wonder if it has something to do with my date format, with is currentl...
08/13/2010
- Burndown chart mockup
- 02:55 PM Feature #468: Eliminate the gap in functionality between pending and completed tasks
- There are a number of very useful commands that cannot be run on tasks with status:completed. Duplicate, annotate, edit, add/remove attributes and tags, etc. From the end user's perspective, there's no obvious reason for this -- all the user can ...
- 08:11 AM Bug #467: Recurring tasks don't honour wait values
- There's a bit of overlap between wait and the upcoming interval functionality, so this may require some discussion. A task set as recurring and waiting shows up in reports as though the wait: value had not been set. Consider: ...
- 12:43 AM Bug #466 (Closed): wrong error message when sort key missing +/-
08/12/2010
- Taskwarrior is sponsored by LinuxCaffe
- 08:27 PM Bug #466 (Assigned): wrong error message when sort key missing +/-
- Good catch.
- 07:21 PM Bug #466: wrong error message when sort key missing +/-
- task-1.9.2 will complain that a 'Sort column is not part of the report' when, in fact, it is, but is simply missing the requisite +/- following the sort key name.
08/11/2010
- 07:11 PM Feature #462: url support
- It would be nice to something similar as the _.ssh/config_ file. The corresponding values could be config variables in .taskrc
- 07:08 PM Feature #465: Merge filter
- Some kind of matching to merge single tasks or particular projects, e.g.: ...
- 07:07 PM Feature #464: Merge Rollback
- Restore the state of a single task after a merge operation.
- 07:05 PM Feature #463: Content merging
- Merge command: Should be possible not only to substitute full tasks, but also to merge the _contents_ of tasks to resolve conflicts. E.g. merge project from the left side with tags from the right side.
- 06:56 PM Feature #462: url support
- ...as with git, e.g.: ...
- 03:21 AM task on the Nokia N900
- Read http://taskwarrior.org/boards/1/topics/show/483#message-643 for more information. And scroll further down as user zeltak has a tip on how to share the task files between the PC and the N900. We will now try to get task into the Maemo repos...
08/10/2010
- 10:13 PM Bug #460 (Closed): There should be a way to turn off header and footer info
- 08:22 AM Bug #461: due:today doesn't work as a filter - due.is:today does
- The first gives a terrible error: ...
08/09/2010
- 04:55 PM task, cygwin, mintty and colors
- You will not just get 256 colors, but also a proper terminal. mintty is part of cygwin and available in the _shells_ category. It is based on the terminal emulation from PuTTY. It's project homepage is at http://code.google.com/p/mintty
- 04:47 PM task in Debian and Ubuntu
- This means that task is included in 8 major distributions.
- 08:56 AM Feature #457: New 'expire' attribute representing the absolute last day a task could be completed
- While the specter of a resurrected "retired" status is a bit chilling, there's the semantic disconnect of marking an expired task "deleted" or "done", and neither of these things really happened. Perhaps annotations are our friend here, and being ...
- 08:18 AM Feature #457: New 'expire' attribute representing the absolute last day a task could be completed
- Paul Beckingham wrote: > what happens to the task? Deleted? A status:retired was promised (halfheartedly) for 2.0.0 in this Forum thread: "Task retirement home.":http://taskwarrior.org/boards/6/topics/show/159 I'm entirely content with expir...
- 08:01 AM Feature #456: Additional recurrence functionality: 1st and 3rd Tuesdays (for example)
- Federico Hernandez wrote: > but I guess the first example wiil (at least currently) produce the wrong result as "tuesday" means the next tuesday which could be the second one if you run the command between the first and second tuesday of a month....
- 08:00 AM Bug #460: There should be a way to turn off header and footer info
- ...
08/08/2010
- 09:20 PM Feature #456: Additional recurrence functionality: 1st and 3rd Tuesdays (for example)
- Hmm. I see your point. ...
- 09:00 PM Feature #456: Additional recurrence functionality: 1st and 3rd Tuesdays (for example)
- I'm thinking the due: field shouldn't behave any differently than for any other type of task. Consider this vanilla recurring task: ...
- 08:31 PM Feature #456: Additional recurrence functionality: 1st and 3rd Tuesdays (for example)
- The n'th occurrence of a weekday in year y and month m can be calculated with ...
- 08:28 PM Feature #456: Additional recurrence functionality: 1st and 3rd Tuesdays (for example)
- Cory, I would like you to think about syntax for this. how would you like to enter these values? task add recur:1st3rdTuesday Recycling pick up Theoretically a task like this would not require a due date - it is implicitly given in recur:...
- 08:19 PM Bug #458: Relative date values should require user is unambiguous
- I see the point in just using 'm': it is shorter. And there weren't minutes in task before. Now I still would prefer to keep m for the month and either use mi, M or mm for the minutes or even 0m30m, omitting years, days and hours plus seconds f...
- 07:31 PM Feature #457: New 'expire' attribute representing the absolute last day a task could be completed
- I could live with having it deleted. Others would like to have it "archived" - for statistics or just completeness purposes (but then we don't have archived as a status). Another thing is that an expire date should be allowed without a due date...
- 06:47 PM Feature #457: New 'expire' attribute representing the absolute last day a task could be completed
- So what happens to this task: ...
- 06:06 PM Bug #440 (Closed): Parser recognizes an attempt to simultaneously subst and append, but doesn't d...
- Hmm. The code didn't even try to apply the substitution on both append and prepend.
- 09:03 AM Bug #442: "task edit" fails on Cygwin when using a Windows editor
- Another way would be to have a configuration variable that the user can set and tell task to generate files with the correct line endings for the wanted editor. That variable could also be useful for other "exports" where a task generated file sho...
08/07/2010
- 09:39 PM Feature #421 (Closed): Data synch
- 09:38 PM Bug #442: "task edit" fails on Cygwin when using a Windows editor
- Following a suggestion by Dirk, the edit command now performs a "chdir" to the data location as known to task, then calls the editor with just a file name, not a path so that any editor can pick up the file from the current directory. This works,...
08/06/2010
- 07:07 PM Bug #361 (Assigned): task command cannot have upper-case characters
- 06:57 PM Bug #459: Error when using limit:n where n < lines on screen and < results
- If your terminal has 24 lines, the task command results in 10 lines, if you use "limit:page", then task will say something like: ...
08/05/2010
- 05:12 PM Bug #458: Relative date values should require user is unambiguous
- I see, so it's just the 'm'? Would simply taking that one out work for you? As for "sennight", that was me, and it's a clue as to what book I was reading at the time.
- 08:19 AM Bug #458: Relative date values should require user is unambiguous
- I should have been more clear -- I think it's perfectly appropriate to allow all of your examples to resolve to "years" -- "yearly", "years", "yrs" and "y" are all different commands, but unambiguously resolve to the same period. "m" is the specif...
- 07:30 AM Bug #458: Relative date values should require user is unambiguous
- Just a note: Taking one example, "yearly", I wanted to be able to accept words that make sense. In this case "yearly", "years", "yrs" are common ways of entering a number of years. In addition, I wanted the ultimate abbreviation to work - "y". ...
- 07:02 AM Bug #458 (Assigned): Relative date values should require user is unambiguous
- I will comment when sitting in front of a real keyboard.
Also available in: Atom