From 06/29/2009 to 07/28/2009
07/28/2009
- 11:25 PM Bug #248: export of single-quotes and double-quotes in description collide
- Both single-quotes and double-quotes get encoded as as " during an export. Only one of these can be correct because upon importing, they'll both be decoded as either or single-quotes or double-quotes. A combination is not possible.
- 08:45 PM Feature #247: provide infinite width reporting
- It would also be really slick if the user could set rc.defaultwidth=0 (or some magic value) to indicate infinite width (i.e., no word wrapping at all). This would make pasting into other documents having full formatting capabilities much smoother...
- 08:44 PM Bug #246: redirected task output ignores rc.defaultwidth
- Width seems to be forced to 80 characters when task output is redirected to a pipe or file.
- 08:05 PM Bug #245: export of due-dates are surrounded by single-quotes which remain through import
- The single-quotes remain around the due date upon import which results in those dates being misreported.
- 08:02 PM Bug #244: export does not include annotations
- 02:06 PM Bug #243 (Closed): v1.8 wiki page need update
- 01:00 PM Bug #243: v1.8 wiki page need update
- the way we should handle versions, is to create pages for the incremental versions, too (ie. v181 should be created, rather than changing v18) the roadmap should then show only the patch page, with links to the changelog, which should be made of a...
- 10:12 AM Bug #243: v1.8 wiki page need update
- http://taskwarrior.org/wiki/taskwarrior/V18 still refers to beta3, and this page should look more like (in fact, BE) the 1.8 changelog, which should then be {include}d in the changelog page.
07/27/2009
- 08:33 PM Bug #242: Reported ID of just added task can be incorrect
- Not sure how to reproduce exactly -- maybe related to having deleted a task, but I've seen this several times now: $ task add foo Created task 159 $ task info 159 Task 159 not found
- 06:32 PM Feature #188: GIT plug-in
- look at "Cil":/boards/8/topics/show/200#message-204
- 02:57 PM Bug #241: bash completion with bash 4
- It appears that the real problem may have been with bash 3.x. According to the bash man page, the env. variable COMP_WORDBREAKS provides a list of characters that are to delimit words. In both Fedora 10 and 11 this does contain the colon (:) cha...
- 02:15 PM Bug #241: bash completion with bash 4
- bash completion with bash version 4 (as it comes with Fedora 11) is not working for project completion. tag and rc.<attribute> completion works though.
07/26/2009
- 04:20 PM Bug #231 (Closed): time_t/int collision on 32-bit system
- 04:18 PM Bug #231 (In progress): time_t/int collision on 32-bit system
- Fixed in task 1.8.1. Patch offered by Pietro Cerutti applied. Although this patch was applied to the task 1.8.1 branch, it may never be released as 1.8.1. The reasoning behind this decision is: a) Pietro, although affected by this problem,...
- 03:51 PM Feature #240: Dynamic "stats" report
- The interactive equivalent to "task stats" is a dynamic screen that updates in real time.
- 03:49 PM Feature #239: i8 - stats panel
- Intermediate prototype that introduces a live, threaded stats panel. This will maintain accurate stats when 2.0 is running interactively, and a CLI 2.0 changes the stats.
- 03:47 PM Feature #238: i7 - keys panel
- Intermediate prototype that introduces a working keys panel that properly captures input. Also introduces asynchronous message posting between panels.
- 03:45 PM Feature #237: i6 - title panel
- Intermediate prototype that introduces a working, complete title panel. Incrementally improving the prototype.
- 03:44 PM Feature #236: i5 - live clock panel
- Intermediate prototype that introduces a live clock panel, and panel initialize/terminate control, to minimize resources.
- 03:41 PM Feature #235: i4 - dynamic layout, automatic resize
- Intermediate prototype to allow CLI specification of layout, with automatic resize recalc. This will allow us to evaluate layout designs with resizing.
- 03:39 PM Feature #234: i3 - single layout, automatic resize
- Intermediate prototype to determine best method for handling terminal resize via ncurses. We're looking for good behavior on all platforms.
- 03:38 PM Feature #233: i2 - layout design
- Intermediate prototype that allows colored panels to be placed and rendered, allowing us to design layouts for task screens.
- 03:37 PM Feature #232: i1 - keyboard test
- Intermediate prototype for testing keyboard configurations on all platforms.
07/24/2009
- 03:22 AM Bug #231: time_t/int collision on 32-bit system
- I suggest to remove the int() operator at all, and cast to an integer type in the caller, when required, e.g., for printf.
07/23/2009
- 05:21 PM Bug #231: time_t/int collision on 32-bit system
- Added by Pietro Cerutti about 7 hours ago On 32-bit platforms, time_t is often defined as int. class Duration defines two overloaded operators, 43 operator int (); 44 operator time_t (); which are implemented as 54 ////////////...
07/22/2009
- 11:27 PM Feature #230: make 'task N' same as 'task N info'
- yeah, like it a lot; natural, useful
- 09:00 PM Feature #230: make 'task N' same as 'task N info'
- This is a great idea.
- 05:19 PM Feature #230: make 'task N' same as 'task N info'
- As of 1.8.0, the following usage has little benefit: ...
- using 256colors2.pl (found in files section)
- week calendar mock-up
- report.io mock-up
- taskwarrior 2.0 mock-up
- work-week mock-up
07/21/2009
- 10:52 PM Feature #141: write f1 help text
- John Florian wrote: > DocBook is exactly what I was thinking, which is a form of SGML and happily, my favorite outline editor (vimoutliner) features a docbook export plug-in !
- 10:50 PM Bug #180: remove redmine references to "other projects"
- yup, and the reference to Project, at the top left.
- 10:50 PM Bug #179: wiki/gallery image thumbnails
- sure ! I think we should break it up into three galleries; interface, website and videos. The ideal scenario is that the Gallery page has three divisions (columns ? rows ?) and that the latest (5 ? 6 ?) images are represented as thumbnails. cli...
- 10:45 PM Bug #179: wiki/gallery image thumbnails
- David, could you be a little more specific?
- 10:41 PM Bug #180: remove redmine references to "other projects"
- Do you mean that remove the box?
- 07:37 PM Task 1.8.0 is released!
- Task 1.8.0 is released, with many new features, and a more robust foundation for future versions. Check out the new attribute modifiers, the improved tab completion scripts, the new reports, and more. Don't forget to take a look at the demo movi...
- 09:29 AM Feature #210: shell mode extension and enhancement
- shell-mode-style input will also be used extensively in interactive mode. for example, while in the interactive shell, if you hit (a)dd, the prompt-bar should display a shell-mode input prompt, like ...
07/20/2009
- 02:35 PM Feature #141: write f1 help text
- David Patrick wrote: > John Florian wrote: > > What would be really slick is to have the "master" help in something like SGML and then render that into navigable help from within task as well as plain text and HTML and .... > so.. you''re sugge...
- 01:39 PM Feature #141: write f1 help text
- John Florian wrote: > What would be really slick is to have the "master" help in something like SGML and then render that into navigable help from within task as well as plain text and HTML and .... so.. you''re suggesting as base format.. sgml ? ...
- 10:45 AM Feature #141: write f1 help text
- David Patrick wrote: > John Florian wrote: > > I think vim's first help page (:help) is nice in that it explains how to navigate the help. > That is the perfect place to start. > question; is that help file helpless without vim ? Yes and n...
07/19/2009
- 10:43 PM Feature #141: write f1 help text
- John Florian wrote: > I think vim's first help page (:help) is nice in that it explains how to navigate the help. That is the perfect place to start. question; is that help file helpless without vim ?
- a perl color palette display thingy
- 08:00 PM Feature #141: write f1 help text
- David Patrick wrote: > does anyone have an example of the "ideal" f1 help screen ? I think vim's first help page (:help) is nice in that it explains how to navigate the help.
- 04:57 PM Feature #141: write f1 help text
- does anyone have an example of the "ideal" f1 help screen ? can we use multiple pages, or links within a page ? how context sensitive should f1 be ? then how many contexts are there ?
- 04:37 PM Feature #224: .taskrc folding
- I'm learning about vim folding, for real, and found a nice bit of reference; http://tuxtraining.com/2009/04/10/how-to-use-folds-in-vim
- 02:14 PM Feature #226: Support terminal window resize
- Well, vim and top both automatically redraw and resize on terminal resize. I can only assume this is done via the SIGWINCH signal, but I guess we could verify that in the source.
- 02:04 PM Feature #226: Support terminal window resize
- Paul Beckingham wrote: > Do all terminal programs support SIGWINCH? I don't know -- there as so many. It may be best to assume they do until we hear otherwise at which point we "blacklist" it which causes TW to fall back to no automatic adjus...
- 12:25 PM Feature #229: Logging
- Add an optional logging capability, enabled with: rc.logging:on which captures various interactive related events (key presses) and debug messages that would otherwise go to stdout, but in the interactive case cannot, and must therefore ...
- 12:21 PM Feature #228: How to: Terminal setup for color
- How to document describing how to set up a terminal to allow color, satisfy ncurses and run task interactively. This should include things like: export TERM=xterm-color
- 12:17 PM Feature #227: New code to determine color availability
- The current implementation can override ncurses' ability to use color, which is wrong. Integrate the has_color call.
- 12:15 PM Feature #226: Support terminal window resize
- When a terminal window is resized, task must resize, re-apportion and repaint. Do all terminal programs support SIGWINCH?
- 12:13 PM Feature #225: Extend color support to include ncurses
- The current task color system needs to be integrated with ncurses.
07/18/2009
- 08:40 PM Bug #208 (Assigned): 'task recurring' not listing all recurring tasks
- Cannot replicate. Hopefully we'll get a reproducible case.
- 05:56 PM Feature #99: redmine plug-in
- it seems that vimwiki (http://code.google.com/p/vimwiki/) uses syntax that is nearly identical to Redmine's markdown wiki style ! what good luck ! I'll be poking away at the vim usage, but it looks like a good target.
- 03:19 PM Feature #224: .taskrc folding
- If vim keybinding are implemented for the hide/show/level actions, I would encourage the use of those already established by vimoutliner. Some users (at least one) will be using task and vimoutliner in concert.
- 03:16 PM Feature #224: .taskrc folding
- The configuration file .taskrc is where all the setting will go and as more and more features come on board, requiring more and more settings, and as it gets bigger and bigger, it would be handy to have the vim syntax file include a folding option.
- 10:56 AM Feature #223: cut and paste
- using xclip interactive key-bindings; (if possible) Ctrl-x, c and v CLI usage; pipe to and from xclip
- 12:47 AM Bug #206 (Closed): start and complete attributes not working/documented
07/17/2009
- 08:49 AM Bug #219 (Closed): task timesheet through pipe uses escape sequences
- Silly mistake. Sorry.
- 08:44 AM Bug #222: make test data set available
- we should have a full featured, sanitized sample data set to play with.
- 08:43 AM Bug #219 (In progress): task timesheet through pipe uses escape sequences
- Better, but still broken. The section for started tasks still exhibits this behavior.
- 12:49 AM Bug #206: start and complete attributes not working/documented
- Perhaps "live" isn't the right word. Gasping perhaps.
- 12:46 AM Bug #206: start and complete attributes not working/documented
- oops, didn't think start.before and start.after were "live", but why wouldn't they be ?
- 12:32 AM Bug #206 (In progress): start and complete attributes not working/documented
- This isn't a mix of commands and modifiers - it's just a report with a filter. John's right - this is sorely broken, and should be working. I'm in the middle of fixing this one.
- 12:19 AM Bug #206 (Rejected): start and complete attributes not working/documented
- commands and modifiers as described do not yes exist, therefor it's not broken
- 12:17 AM Bug #206: start and complete attributes not working/documented
- I would suggest trying; task list due.after:6/1/2009 and task all status:completed due.after:6/28/2009 your examples above are outside of the current implementation.
07/16/2009
- 10:17 PM Bug #219 (Closed): task timesheet through pipe uses escape sequences
- 09:59 PM Bug #213 (Closed): Ctrl-D in "shell" command hangs
- The Ctrl-D closed std::cin. It just needed to be detected.
- 10:40 AM Feature #151: apply journal.txt vim syntax highlighting and folding
- for folding key-bindings, please use those established by vimoutliner.
- callsheet script by djp, generates callsheet from palm data
- "callsheet" generated from palm data
07/15/2009
- 11:52 PM Feature #42: Purge command to remove deleted tasks
- suggested options (in development) purge [attrs] [#|date] (so you could purge data from one proj:, for example) purge completed [attrs] [#|date] (don't recycle ID#s, or purge retired) purge ID [attrs] [#|date] (recycle a...
- 02:49 PM Feature #221: journal
- Somewhere between log-file and personal diary, the journal will become an essential tool. From the command line, you will be able to jump right into editing the journal with your fave text editor, just by entering "task -j" (same as "task journal...
- 02:31 PM Feature #220: review script
- Straight-on task-doing, starting with the most important/urget things first, is what taskwarrior is about, along with the massive stress reduction that comes from knowing you're not forgetting anything, HOWEVER, if all of your focus is at the top ...
- 02:22 PM Bug #219: task timesheet through pipe uses escape sequences
- All other reports have nice looking column headings, but 'task timesheet' does not.
- 02:15 PM Feature #218: context support
- One of the pillars of the GTD task management school-of-thought, is "contexts". The thinking is that now matter geared up and rarin' ta go you may be, you can really only perform (some) tasks within a definable context. That is to say that if you ...
- 01:47 PM Feature #217: routine
- the "routine" functionality is an extension of "contexts", and will require time-of-day handling. It will serve multiple functions, from automatically assigning due:dates based on context, to automated avoidance of scheduling conflicts, to present...
- 01:34 PM Feature #216: User-defined Exclusions
- A good task management system will let you track EVERYTHING, from the most important/urgent tasks, to the piddlingly trivial. The problem is that the least important things clutter and cloud the big picture. With UDE, users will be able to define ...
- 01:20 PM Feature #215: goal-setting script
- We all know how important it is to set goals for yourself, but for many people it's the hardest thing. Happily, methods have been established to make this easier, without re-inventing the process, and this action script will ask all the right qu...
- 01:12 PM Feature #214: HipsterPDA plug-in
- to facilitate the creation of index-card-sized organizer
- 08:44 AM Bug #213: Ctrl-D in "shell" command hangs
- Reproduce with the following: task shell task> ^D Thanks to Ian Mortimer.
07/14/2009
- 10:51 AM Feature #210: shell mode extension and enhancement
- John Florian wrote: > I think we'd want an rc option that enabled/disabled this feature though. perhaps autoshell=on/off and a CLI override (noautoshell) so that you can stay in autoshell mode and your scripts can still behave nicely.
- 10:44 AM Bug #211: usage of "update" missing from help output
- although I'm not sure of it's status. Usage of "update" for compound commands is not yet implemented. (?)
- 09:41 AM Feature #210: shell mode extension and enhancement
- That's clever. I think we'd want an rc option that enabled/disabled this feature though. I can envision a day when I'll have other scripts creating tasks for me and I wouldn't want a scripting error to freeze because it was blocked on input. ...
- 12:05 AM Feature #210: shell mode extension and enhancement
- if I type task add I get an error message "Cannot add a task that is blank, or contains <CR> or <LF> characters." Considering the stealthy new shell mode, wouldn't it be swell if what actually happened was that task went into "shell add...
07/13/2009
- 08:32 PM Bug #207 (Closed): weekly recurrence requires quantity vs. monthly which does not
- 08:31 PM Bug #207: weekly recurrence requires quantity vs. monthly which does not
- Paul Beckingham wrote: > The "w" is ambiguous, and could be "weekly" or "weekdays". Doh! I should have checked my work better and I'd forgotten about weekdays. > But the real problem is that "m" is not "1m", but coincidentally works. I gu...
- 08:08 PM Bug #207 (Rejected): weekly recurrence requires quantity vs. monthly which does not
- That's because "m" is the minimum unique string required to identify "monthly" from a list of durations which contains no other durations that begin with the letter "m". The "w" is ambiguous, and could be "weekly" or "weekdays". But the real...
- all about inky
- 04:53 PM Bug #209: 'task edit' of recurring task not working correct
- First, I: ...
- 02:21 PM Bug #208: 'task recurring' not listing all recurring tasks
- ...
- 02:12 PM Bug #207: weekly recurrence requires quantity vs. monthly which does not
- An inconsistency exists (in 1.8.0beta3) which may trip up a newer task user: ...
- 10:01 AM Beta 3 of task 1.8.0 now available
- A new version of the beta release of task 1.8.0 is available for download from the [[V18]] page.
- 10:00 AM Bug #206: start and complete attributes not working/documented
- Sorry if beta3 fixes this as I haven't been able to pull that yet, but: Neither 'task help' nor 'man task' document start and complete as valid attributes. Also, I'm unable to make 'task list start.after:6/1/2009' work. It shows tasks, but ...
- 08:40 AM Support #190 (Rejected): conky how-to
- Duplicate of #82
- 08:39 AM Feature #199 (Closed): bash completion of rc setting overrides
- Available as of beta3
- 08:32 AM Feature #204 (Closed): offer completed projects for bash completion
- complete.all.projects=yes/no complete.all.tags=yes/no
07/12/2009
- 07:20 PM Feature #204: offer completed projects for bash completion
- Paul Beckingham wrote: > This is a trivial change, and can be implemented in 7 lines of code, and that include tags as well as projects. Classify it as a bug, and it can go in 1.8.0. Otherwise, how about 2.0.0? if it's really so trivial then...
- 07:05 PM Feature #204: offer completed projects for bash completion
- This is a trivial change, and can be implemented in 7 lines of code, and that include tags as well as projects. Classify it as a bug, and it can go in 1.8.0. Otherwise, how about 2.0.0?
- 06:40 PM Bug #205 (Closed): problems with batch operations
- 06:11 PM Bug #205: problems with batch operations
- Same bug also affects "append" command.
- 04:56 PM Bug #205: problems with batch operations
- Reproduced, added bug.bulk.t unit tests. Now to fix it.
- 03:52 PM Bug #205 (In progress): problems with batch operations
- Yikes. What bothers me most is that task 100 wasn't even part of your command. I'm trying to reproduce this bug.
- 03:25 PM Bug #203 (Closed): list tasks without a project
- Fixed. Projects are a special case, such that: task ls pro:ta will match project "task". This is the mechanism that allows subprojects to work. The bug is that a blank project was essentially being compared like this: if (! str...
- 12:38 PM Bug #203 (In progress): list tasks without a project
07/11/2009
- 05:55 PM Feature #204: offer completed projects for bash completion
- David Patrick wrote: > tags might be similarly recycled. Very good point!
- 03:56 PM Bug #205: problems with batch operations
- ...
- 03:37 PM Bug #203: list tasks without a project
- I just went back and learned more about the attribute modifiers and realized that I can: @task list pro.none:@ It probably would be best to resolve the inconsistency though.
- 03:25 PM Feature #204: offer completed projects for bash completion
- tags might be similarly recycled.
- 02:41 PM Feature #204: offer completed projects for bash completion
- Once all tasks for a given project are done, the project disappears from the bash completion list. It may be useful (hint: rc option) to also allow bash completion of projects from completed.data, at least until a purge is performed.
- 01:02 PM Bug #203: list tasks without a project
- While it is possible to list tasks without a priority via: @task list pri:@ It is not possible to use a consistent approach and list tasks without a project via: @task list pro:@
- 12:01 PM Bug #181 (Closed): csv <-> pipe separated values script
- seems that openoffice.org will happily eat and regurgitate "pipe separated values". stand by for buffed up tables.
07/10/2009
- 06:17 PM Bug #200 (Closed): man page missing documentation of wait attribute
- Fixed and pushed.
- 05:10 PM Bug #200 (In progress): man page missing documentation of wait attribute
- Yes. It is a miss.
- 12:03 PM Feature #202: establish sync protocol
- consider http://www.opensync.org/
- 09:36 AM Feature #201: wait dates relative to due date
- absolutely; a positive date reference means "wait from now until <value>", while a negative date reference should mean "wait until <value> before due date". (no due date= error) this will be VERY handy. Of course, wait:yesterday still won't make s...
- 09:27 AM Feature #201: wait dates relative to due date
- It might be useful to do something like: task add due:12/20/2009 wait:-1m recur:y "Buy Christmas presents"
- 09:25 AM Bug #200: man page missing documentation of wait attribute
- Under the section ATTRIBUTES AND METADATA there is no description of the wait attribute.
- 09:18 AM Feature #198 (Assigned): lazy dates
- Good idea. I'm currently researching relative date entries - have done this a couple of years ago for scheduling problems - and I think this fits as well into this category. Will write it down.
- 09:15 AM Feature #199: bash completion of rc setting overrides
- If task had something like a _rc command, it should be possible to have bash complete the setting names.
- 09:12 AM Feature #198: lazy dates
- It would be convenient if the user could omit the year in a date entry and task would assume the current year in such cases.
- 08:26 AM Support #192 (Closed): how-to; vim syntax highlighting set-up
- David Patrick wrote: > John Florian wrote:> > > Methinks the "add News" thingy is invisible! Permissions perhaps? > try now, thou newest of administrators. That did the trick.
07/09/2009
- 11:53 PM Support #192: how-to; vim syntax highlighting set-up
- John Florian wrote:> > Methinks the "add News" thingy is invisible! Permissions perhaps? try now, thou newest of administrators.
- 11:50 PM Support #192: how-to; vim syntax highlighting set-up
- Paul Beckingham wrote: > 3. Click on the "add News" thingy at the top right of the page Methinks the "add News" thingy is invisible! Permissions perhaps?
- 11:25 PM Support #192: how-to; vim syntax highlighting set-up
- Adding News: 1. Log in 2. Click on the "News" tab 3. Click on the "add News" thingy at the top right of the page 4. Scratch your head over what text should go into each of the three fields 5. Look at the other news items for guidance. Lear...
- 11:08 PM Bug #196 (Closed): task next not fully honoring next= setting in rc
- 10:26 PM Feature #197: parser upgrade
- to new EBNF, recursive, backtracking, LALR Parser
- 10:17 PM Bug #194 (Closed): Expired wait: not switching to pending
- 10:00 PM Bug #195 (Closed): date problems with 2-digit year
- 08:06 PM Feature #58 (Closed): Windows binary distribution
- packaged in cygwin enough ?
- 04:03 PM Bug #196: task next not fully honoring next= setting in rc
- I should mention this was with the default 'task next' report configuration, included here for completeness: # task next report.next.description=Lists all tasks matching the specified criteria report.next.columns=id,project,priority,due,activ...
- 04:01 PM Bug #196: task next not fully honoring next= setting in rc
- I've removed the task descriptions to protect the innocent. However, notice the aos.deploy project for just one example: $ task next rc.next:100 ID Project Pri Due Active Age 42 M 7/10/2009 3 wks 35 pi...
- 03:41 PM Bug #195: date problems with 2-digit year
- I had my dateformat configured for a 2-digit year and mistakenly set a due date using a 4-digit year. I don't recall getting an error for that and the year essentially got interpreted as 2020. Further more, I tried to fix this using 'task edit...
- 09:06 AM Bug #194: Expired wait: not switching to pending
- T. Charles Yun reports: task add foo wait:yesterday task add bar wait:tomorrow task list shows nothing, and should show "foo" as pending.
07/08/2009
- 10:51 PM Bug #171 (Closed): task done has repetitive output
- Thanks John. That extra message should have been only displayed in the case of a bulk change.
- 08:49 PM Feature #193: pcal plug-in
- Pcal and lcal are calendar-generation programs which produce nice-looking PostScript output http://pcal.sourceforge.net/
- 08:02 PM Vim syntax highlighting
- The the [[Configure_VIM_for_Syntax_Highlighting_of_Task_Data|wiki page]] for instructions on how to enable this functionality in your vim.
- 07:09 PM Support #192: how-to; vim syntax highlighting set-up
- The wiki has been updated with a new page. I haven't seen how the News page is updated so if someone wants to tackle that bit we should be all set.
- 12:41 PM Support #192: how-to; vim syntax highlighting set-up
- David Patrick wrote: > would that README be suitable for posting in the how-to section ? Not exactly as is. It references a tarball that I sent out containing just the vim related stuff. I can update it (later today) and place under the wiki...
- 12:32 PM Support #192: how-to; vim syntax highlighting set-up
- Federico Hernandez wrote: > You will find a scripts dir containing a vim dir with all the files and a README written by John on how to install them. would that README be suitable for posting in the how-to section ? .. or should there be a READ...
- 11:45 AM Support #192: how-to; vim syntax highlighting set-up
- The corresponding vim files are installed in /usr/share/doc/task or /usr/local/share/doc/task-<version> depending if you install by package or tarball without using the ./configure --prefix option. You will find a scripts dir containing a vim d...
- 11:26 AM Support #192: how-to; vim syntax highlighting set-up
- where are the files and what is the user supposed to do with them ?
- 08:57 AM Bug #191: Going into 'cal' mode when called using full path
- Verified that 1.8.0ß2 fixes this. Thanks, Paul.
- 08:51 AM Bug #191 (Closed): Going into 'cal' mode when called using full path
- That's awful. Sorry Eric. Priority set to Immediate because this prevents Eric from using task. String search was not anchored to end of string. New tarball uploaded.
- 08:33 AM Task 1.8.0 in beta
- We have been working hard to bring about some big improvements in task. Some of those changes you won't see, because they are internal, like the doubling in size of the test suite, helping us keep the code quality high, or the more modular design...
- 08:14 AM Bug #191: Going into 'cal' mode when called using full path
- Task 1.8.0ß is outputting like it's in 'cal' mode when it is run using the full path. See below: ---BEGIN PASTED TEXT--- $ task [task list] ID Project Pri Due Active Age Description -- --------------------- --- ---...
- 12:05 AM Support #190: conky how-to
- write a how-to describing how to set up conky to display selected task info
07/07/2009
- 05:12 PM Bug #189: "stop" annotates start and stop times
- To enable time-tracking, "stop" should move start-time and stop-time to a task annotation. It should be easy to report from, and write to, and might be similar to having entered $ task 55 ann:start_2010-01-04_19:32:22---stop_2010-01-04_21:19...
- 02:31 PM Feature #188: GIT plug-in
- another version control system
- 02:27 PM Feature #187: scripted execution
- see discription of [[execute]] "action scripts", to act on tasks "verbs" and "nouns" and using new attributes "time:" and "action:"
- 02:10 PM Feature #186: network monitoring plug-in
- keep track of machines on the network and view a range of near real-time statistics
- 02:07 PM Feature #185: nanoblogger plug-in
- to allow seamless blogging using nanoblogger.
- 02:04 PM Feature #184: address book export
- all (or selected) contact data exported to pdf and ready to print a good-looking address book.
- 02:03 PM Feature #183: call-sheet export
- modeled after the call-sheet that is used in the movie business, featuring a clear layout of everything that happens that day (scheduled tasks, Next actions, sunrise/set, weather forecasts etc.) I will follow this up with examples. example "cal...
- 01:59 PM Feature #182: telephony plug-in
- to enable speedy completion of "calls", with auto dialer, (crazy warning) and maybe even touch-tone menus to have (festival) speach synth output of task or contact data. Think about it, forget a phone number ? if you could call your own ans...
- 01:56 PM Bug #181: csv <-> pipe separated values script
- for moving wiki tables out to spreadsheet, and back
- 01:46 PM Bug #180: remove redmine references to "other projects"
- in the very top right hand side "Projects" and the "Jump to a project..." box
- 01:40 PM Bug #179: wiki/gallery image thumbnails
- in three groups; interface, website and videos
- 01:36 PM Feature #178: multimedia plug-in
- With the integration of a console multi-media application (and there are several good ones) taskwarriors will be able to enjoy tunes without leaving the application, or even starting X. Sound support will also allow task to have an audio-theme, ...
- 01:12 PM Feature #177: units plug-in
- the linux CLI application "units" is amazing, but could be even better with an interactive interface.
- 12:58 PM Feature #176: search with user-controlled case-sensitivity
- Personally, I favour "upper-case sensitivity" where searches in all lower-case are case insensitive, but the use of any upper-case character in a search string forces the search to be case-sensitive.
- 12:51 PM Feature #176: search with user-controlled case-sensitivity
- In task 1.7.1 keyword searches were case-insensitive. In task 1.8.0 they became case-sensitive. Both are equally useful depending on the circumstances. The user should have a choice in which method is used. Example tasks where one might want...
- 12:25 PM Feature #175: taskOS
- a minimal live linux distribution that packages the complete taskwarrior environment, including all available plug-ins and enhancements, suitable for carrying around on a USB key.
- 12:15 PM Feature #174: console games plug-in
- Yes, task-doing is serious business and we are trying to craft an environment free of distraction, but there are many productivity applications lurking under the "games" category (like gtypist, goal-setting apps and speed-reading tutors) and game-...
- 12:05 PM Feature #173: scurvy plug-in
- scurvy is a perl-based, vim-centric screenplay writing application. It features lightweight mark-up, sane import/export and flawlwss pdf screenplay output. The interactivisation would add key, bindings, screenplay elements as attributes, real-time...
- 12:00 PM Feature #172: bc plug-in
- basic calculator interactive. While bc is a champion of console calculators, it would benefit from an interactive shell and the use of a bc.data file. The advantage is that free-form notes could be interspersed with live calculations and the whole...
- 10:53 AM Bug #171: task done has repetitive output
- task 49 done Task 49 "Eat a pizza" Completed 49 "Eat a pizza" Marked 1 task as done Seems like we could drop: Task 49 "Eat a pizza"
- 01:31 AM Feature #170: sc plug-in
- the spreadsheet calculator, with an interactive shell, would become indispensable.
- 01:28 AM Feature #169: dependency support
- allowing hierarchies of dependent tasks, as well as dependencies to contacts. see and ignore; rambling and mostly-wrong wiki page : [[dependencies]] see and consider; "task-linking with special tags forum discussion":http://taskwarrior.org/b...
- 01:24 AM Feature #168: screen solution
- a screen session tailored for taskwarriors. screen (the console window manager) is more than handy, and most experienced *nix users consider it a must-have. Unfortunately, for newer users, the initial set-up can be daunting, with a gazillion op...
- 01:22 AM Feature #167: contacts support
- with full set of contact related attributes, contact related interactive display, mixed task/ contact listings and a "contact" alias for the CLI. see: [[contacts]]
- 01:07 AM Feature #166: encryption plug-in
- that makes it easy to secure your data.
- 12:58 AM Feature #165: ledger integration
- Tight integration will ledger (http://wiki.github.com/jwiegley/ledger) exposing all features to the interactive shell and allowing cross referencing ledger entries with tasks and contacts. While this is deep integration, we should do it without fo...
- 12:54 AM Feature #164: user-defined attributes
- where users can create their own attributes and define data types and constraints. These new attribute will be usable just like the built-in ones. see: [[User-defined_attributes]]
- 12:51 AM Feature #163: time of day support
- with new time:attribute
- 12:40 AM Feature #162: email plug-in; alpine or sup
- allowing use of contact data, easy emailing from within task, sending of tasks to delegates, and receipt of tasks via email.
- 12:34 AM Feature #161: 256 color plug-in
- for terminals that will support it. This should never move to "core" as task should never require a 256 color terminal.
- 12:26 AM Bug #160: shrink name display
- full names in issue listings just eats too much real-estate. If there's a way to use initials instead, even if it means changing developer user-names, let's do it.
07/06/2009
- 06:54 PM Bug #159 (Closed): deleting all of recurring task leaves some
- Fixed. Code was iterating over a filtered set of tasks, not the full set.
- 05:21 PM Feature #152 (Rejected): add "purge" command
- duplicate of #42
- 05:20 PM Feature #42: Purge command to remove deleted tasks
- task purge [attrs] [#|date] (note that [date] refers to the period from the beginning-of-time to [date]) to purge from files completed.data retired.data archive.data default action to move all [or as selected by # or date specifier] completed and...
- 01:03 PM Bug #159: deleting all of recurring task leaves some
- I had accidentally created a (near) duplicate recurring task: $ task list oil ID Project Pri Due Active Age Description 82 6/29/2009 1 wk replac...
07/05/2009
- 03:20 PM Feature #105: Support for pipes
- Federico Hernandez wrote: > I beg to differ. and differ you may, let's kick it around in the "forums":http://taskwarrior.org/boards/6/topics/show/171
- 11:22 AM Feature #105 (New): Support for pipes
- I beg to differ. Pipes are not "commands" and has nothing to do with update. They are just a means to get information into task and out of task. For example: ...
- 12:53 AM Feature #105 (Rejected): Support for pipes
- the new command structure (using update) will obsolete this issue.
- 12:50 AM Feature #158: regex support
- whatever that entails
- 12:10 AM Support #23 (Closed): Handle one-way file upgrade for 1.8.0
- The following is the official 1.8.0 -> 1.7.1 downgrade capability: % task-1.8.0 export > data.csv % task-1.7.1 import data.csv
07/04/2009
- 07:55 PM Support #107: upload man page output to wiki
- Will be completed together with the release of 1.8.0.
- 07:54 PM Feature #157: Naked reports
- Naked reports that is reports without headers or footers - just the naked, bare information - could be useful to have. As input into formatting scripts and without having to filter away this information. Could be perhaps done via an option in task...
- 02:38 PM Feature #57 (Closed): Command aliases
- 01:46 PM Feature #143: Need canonical names in command table
- Not needed until 2.0.0.
- 12:23 PM Feature #7 (Closed): Unit test: fontunderline
- 08:52 AM Feature #156 (Assigned): diff style output for the task undo command
- ;-)
- 12:21 AM Feature #156: diff style output for the task undo command
- well I've done the onerous part, version assignment and all, now back to you for the implementation part.
07/03/2009
- 11:35 PM Feature #51 (Closed): Unit Test verify .taskrc created when missing
- 06:43 PM Feature #156: diff style output for the task undo command
- task currently presents the information about the effects of an undo in "side-by-side" style. It would be nice to have task present this information as well in a "diff" style. From an email exchange with Paul: *Fredde:* Something like a "dif...
- 02:05 PM Bug #155 (Closed): reports forced to 80 columns
- 02:01 PM Bug #155: reports forced to 80 columns
- Mr. Florian was severely under-caffeinated and simply needed to install Fedora's ncurses-devel package before running configure and make. All is better now.
- 01:53 PM Bug #155: reports forced to 80 columns
- Paul Beckingham wrote: > 3. Could you rerun commands with: > > task rc.debug:on <your original command> > > and tell me what task says about "Context::getWidth ..."? Survey says: Context::getWidth: no ncurses, using width of 8...
- 12:32 PM Bug #155: reports forced to 80 columns
- Paul Beckingham wrote: > John, I need some more details: > > 1. Please pull and rebuild 1.8.0 code. Tried and failed with: ...
- 11:41 AM Bug #149 (Closed): bash_completion does not do projects
07/02/2009
- 11:07 PM Bug #155 (In progress): reports forced to 80 columns
- John, I need some more details: 1. Please pull and rebuild 1.8.0 code. 2. What command(s) did you run to determine this? 3. Could you rerun commands with: task rc.debug:on <your original command> and tell me what task says about...
- 10:56 PM Bug #154 (Closed): waiting for file lock is too silent
- 06:36 PM Bug #146 (Closed): write vim color profiles for pending.data and completed.data
- 06:36 PM Bug #146: write vim color profiles for pending.data and completed.data
- > Here's an updated tarball that now provides color highlighting for 'task 1 edit', cleaned up support files for the already supported {pending,complete}.data files, an installation README and GPL licensing for all. Downloaded and will be pushe...
- 06:06 PM Cygwin package
- task has been packaged for cygwin 1.5 and can now be installed using the setup program of cygwin. The package has started to propagate through cygwin's mirror network. We are also working on a package for cygwin 1.7 beta.
- 05:45 PM Bug #146: write vim color profiles for pending.data and completed.data
- Here's an updated tarball that now provides color highlighting for 'task 1 edit', cleaned up support files for the already supported {pending,complete}.data files, an installation README and GPL licensing for all. I'm thinking this is good shap...
- 04:42 PM Bug #155: reports forced to 80 columns
- task doesn't appear to be querying the terminal for the max number of columns anymore. Stretched xterms are being used inefficiently.
- 04:11 PM Bug #154: waiting for file lock is too silent
- If you 'task 1 edit' and then elsewhere attempt to do anything, even a 'task list' the commands blocked waiting for a lock would be much more friendly if they informed the user of the situation. As is, they just sit there and the user must realiz...
07/01/2009
- 11:58 PM Feature #33 (Closed): Allow retired and deferred task states
- 'retired' status deferred for now.
- 07:34 PM Bug #146: write vim color profiles for pending.data and completed.data
- Done.
- 07:09 PM Bug #146: write vim color profiles for pending.data and completed.data
- John, I will change "task edit" to use the .task file extension in it's temporary file name.
- 06:46 PM Bug #146: write vim color profiles for pending.data and completed.data
- Paul Beckingham wrote: > I'd be happy to modify the file for "task <id> edit" in any way. Shebang-like identifier, file >"extension", or whatever. Name it. > > But as for the pending.data, completed.data, undo.data and unmentioned upcoming a...
- 01:22 AM Support #23: Handle one-way file upgrade for 1.8.0
- The following commands should work, as a way to recover from the forced format upgrade: % task-1.8.0 export > file.csv % rm ~/.task/pending.data ~/.task/completed.data ~/.task/undo.data % task-1.7.1 import file.csv It should work, but it c...
- 01:12 AM Bug #153: description replacement broken
- Reassigning to 2.0.0 when the new command line format is to be implemented: task <id or filter> <command> <modifications> In the meantime, the workaround is: task 55 -- implement recurring tasks for season change and freeze protec...
- 01:05 AM Feature #8 (Closed): Undo stack
06/30/2009
- 09:32 PM Bug #146: write vim color profiles for pending.data and completed.data
- I'd be happy to modify the file for "task <id> edit" in any way. Shebang-like identifier, file "extension", or whatever. Name it. But as for the pending.data, completed.data, undo.data and unmentioned upcoming additional files, I'd rather not...
- 08:56 PM Bug #146: write vim color profiles for pending.data and completed.data
- John Florian wrote: > That's an interesting approach, but I think it's a bit naughty for one package to go diddling around in another package's config data like that. Well if .vimrc has to be modified, that would be naughty, but if it's just a...
- 08:23 PM Bug #146: write vim color profiles for pending.data and completed.data
- David Patrick wrote: >rather than point to an alternate vimrc, I imagine generating a new task.vim file each time the >task colors have changed. the command "task color vim" generates a new task.vim and plunks it in >the (derived or user specifie...
- 04:42 PM Bug #149: bash_completion does not do projects
- THX for the patch, John. Great work. I will apply and push it in the next few days.
06/29/2009
- 11:39 PM Bug #149: bash_completion does not do projects
- Federico, here's a patch that allows completion of project names so long as you've typed at least "pro:". Of course, it's happy if you've given "project:" or anything in between. In addition, I've also made tags more friendly as I found that I c...
Also available in: Atom