This is a Python-based application to manage events and tasks, using flat text files to store data
Displayed items can be grouped by date, context, keyword or project and can be filtered in a number of ways.
A display of busy and free times is also supported as is a reckoning view of time spent that is suitable for client billing.
Alarms are supported for events and repetition for both events and tasks in a powerful and flexible manner.
More documentation can be found on Duke University's project page.
- Differences between stored information:
- Event: A reminder of something that will happen on a particular day (or days) and, perhaps, at a particular time. An event cannot be begun or finished either early or late. Events may or may not require our participation.
- Task: A reminder of something that needs to be done. It may or may not have a due date, and if it does, it might be begun and even finished before the due date. It might also be finished and even begun after the due date.
- Action: A record of the time-consuming action required to complete a task or participate in an event. Actions are not reminders, they are instead records of how time was actually spent.
- General Features:
- Quickly enter an event or task using a simple format.
- Enter dates and times using fuzzy parsing.
- Easily specify tasks and events that repeat in complex ways, e.g., the first Tuesday after a Monday in November every four years (Presidential election day). See Repetition examples.
- View events and tasks sorted by date, project, context or keywords.
- Limit the display to events, tasks and/or actions whose titles, notes, projects, contexts and/or keywords match (regex) search string(s).
- Export the events, tasks and/or actions which satisfy the other list view criteria in iCalendar format.
- See schedules of busy and free times for a range of dates. Limit displayed free times to certain hours each day, .e.g., 8:00a-5:00p, and to periods of at least a minimum number of minutes in duration and with a minimum number of 'slack' minutes on either end.
- Make records of expenditures of your time using the built-in timer and then use date, context and keywords to categorize them. Use this simply to track your time or to bill clients.
- Use reckonings (time reports) to see how your time has been used. These reports can make use of dates, contexts, keywords and descriptions to provide a myriad of possible levels of detail and groupings.
- Calculate dates from the command line or using the GUI.
- Specify a list of minutes prior to an event at which to trigger early warning alerts.
- Have alerts make spoken announcements and/or pop up displays using your platform tools, e.g., growl on OS X or notify-send on Linux.
- View the queue of coming alerts for the current day.
- Specify a number of days prior to the due date to be reminded to begin a task.
- Display tasks in customizable colors which depend upon their due dates.
- Keep complete records of the dates when tasks were completed.
- Dates and calendars use locale settings and thus should appear in your native language. Other settings determine the first day of the week and the words and phrases used in displays and alerts.
- Pop up a twelve month planning calendar.
- View sun and moon data (from the US Naval Observatory) for a location specified in your ~/.etm/etmrc for a (fuzzy parsed) date.
- View local weather conditions and forecast (from yahoo weather) for a location specified in your ~/.etm/etmrc.
In a hurry? Add it to your Download Basket!
What's New in version 889
- Fixed bug in dealing with leading whitespace in @n entries.
- Fixed but in clearing undo for finish and unfinish.