Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On 16 August 2010 02:49, anonymous wrote: > I don't think this should be written in shell scripting language: it > is not too easy to calculate what date it will be tomorrow without > libc and it should be very fast. I wanted to do some date manipulation in rc awhile back and ended up writing som

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Wed, 18 Aug 2010 01:27:22 +0200 Alexander Teinum wrote: > How many of these small tools are there? moreutils rock. they really fill some gaps. niche, but still. Dieter

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Wed, 18 Aug 2010 01:27:22 +0200 Alexander Teinum wrote: > How many of these small tools are there? Before this gets out of hand > – scream along with me: > > “IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, > INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTI

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

How many of these small tools are there? Before this gets out of hand – scream along with me: “IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS …”

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Wed, 18 Aug 2010 01:11:09 +0200 Alexander Teinum wrote: > The downside is that it’s hard to remove lots of items that are > grepped. If you want to do that, and you don’t need to identify the > items by their date, then you can do that manually in vim by deleting > the lines. # pacman -S more

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

flo does not store any ids in the items file. Items get their id once they are listed in the order that they are sorted. Since they’re sorted, it’s safe to remove ids between range 5–7 like this: for i in {0..2}; do flo -r 5; done Changing items in a range is not safe, since an item might be sort

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Wed, 18 Aug 2010 01:38:26 +0300 (AST) Nikhilesh S wrote: > On Tue, 17 Aug 2010, Alexander Teinum wrote: > > > It might be obvious, but there’s one thing that I have found that is > > nice about changing ids, and that’s when you’re removing items in a > > row. Count how many items you want to

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Tue, 17 Aug 2010, Alexander Teinum wrote: It might be obvious, but there’s one thing that I have found that is nice about changing ids, and that’s when you’re removing items in a row. Count how many items you want to remove, and then remove the first id three times. Type command, enter, arro

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

It might be obvious, but there’s one thing that I have found that is nice about changing ids, and that’s when you’re removing items in a row. Count how many items you want to remove, and then remove the first id three times. Type command, enter, arrow up, enter, arrow up, enter.

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Tue, Aug 17, 2010 at 2:56 PM, Nikhilesh S wrote: > On Tue, 17 Aug 2010, Suraj Kurapati wrote: > >> uuidgen(1) for the win. > > I don't see why they should be univrsally unique - just unique within > the input file should do. All that is required is adding an additional > integer 'id' field to t

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

$ flo do something … $ flo -c 1b4e28ba-2fa1-11d2-883f-b9a761bde3fb -w "do something else" … I’ll think about it.

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Tue, Aug 17, 2010 at 10:19 AM, Alexander Teinum wrote: > On Tue, Aug 17, 2010 at 6:50 PM, Andreas Wagner > wrote: >> I would like a system for managing a task dependency graph > > Yeah, I did think about having some sort of dependency graph today. > it requires [...] that the items must have

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

* Andreas Wagner [2010-08-17 18:51]: > I would like a system for managing a task dependency graph, it is > easier for many people to complete vague tasks when they are broken > down. Having many small tasks without a dependency graph of some sort > would be cumbersome. You might find pyGTD useful

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Tue, Aug 17, 2010 at 6:50 PM, Andreas Wagner wrote: > I would like a system for managing a task dependency graph, it is > easier for many people to complete vague tasks when they are broken > down. Having many small tasks without a dependency graph of some sort > would be cumbersome. Yeah, I d

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

I would like a system for managing a task dependency graph, it is easier for many people to complete vague tasks when they are broken down. Having many small tasks without a dependency graph of some sort would be cumbersome. The user could specify (a) task(s) that depends on another task or an uno

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

You could also be interested in http://todotxt.com/ (although I don't really know it, neither have I taken a look at flo) -- - yiyus || JGL . 4l77.com

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

> Don't have time right now, hence that task management application ? ;-) $ f check out david’s app Ids are updated. On Tue, Aug 17, 2010 at 5:32 PM, Nikhilesh S wrote: > I made a flo-git package for AUR then when I was about to submit I found > that there was already flo-git in AUR. This would

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

I made a flo-git package for AUR then when I was about to submit I found that there was already flo-git in AUR. This would have been my first package. ;_;

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On 10-08-17 02:57 AM, Alexander Teinum wrote: I don’t have time to try it out right now, but I see how an interactive interface might be practical. Don't have time right now, hence that task management application ? ;-) taskwarrior is also purely cli at the moment, but working towards adding

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

/^s/s/$/g/ ? 2010/8/17, Szabolcs Nagy : > * Alexander Teinum [2010-08-17 09:01:00 +0200]: >> s/ISO 6801 date/ISO 6801 week/ > s/6801/8601/ > > -- Do YOU trust google?

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

Damn right! Alexander

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

* Alexander Teinum [2010-08-17 09:01:00 +0200]: > s/ISO 6801 date/ISO 6801 week/ s/6801/8601/

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

s/ISO 6801 date/ISO 6801 week/

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

> Sounds intriguing, and I'm going to check it out, but I have to admit to > being the "Designer" of a competing bit of software at > http://taskwarrior.org I don’t have time to try it out right now, but I see how an interactive interface might be practical. Mine is more like a pure command line a

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On 10-08-14 08:18 AM, Alexander Teinum wrote: I have been working on a program that makes it easy to keep myself, and perhaps others, in check. It’s inspired by suckless. I now consider it stable enough to share it with you. Sounds intriguing, and I'm going to check it out, but I have to admit

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

Or fp as in [f]lo gre[p]. It’s two characters, one doesn’t have to type the same character twice, and it alternates between the hands when typing fp d0 for instance. At least for those that use qwerty. :) Alexander

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

> In bourne-like shells, fg is absolutely necessary to manage job control. > How do you put your jobs back into foreground? I haven’t used Ctrl+Z and fg, but I probably should! I usually have lots of terminals in dwm that I alt+j/k between, and then I send the active one to the left. I would neve

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

\fg %jid ? Dne 16.8.2010 12:43 "Moritz Wilhelmy" napsal/a: In bourne-like shells, fg is absolutely necessary to manage job control. How do you put your jobs back into foreground?

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

In bourne-like shells, fg is absolutely necessary to manage job control. How do you put your jobs back into foreground?

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

alias fg='flo | grep ' # add tagged item f :w meeting,d114-d11430 # list items of a tag fg :w # display today’s events fg d0 # display tomorrow’s events fg d1 Simplicity is so sweet. Alexander

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

> Tagging is easy to do with grep: you can add tags right into items > description text (like "[work] [university]" or ":w:u:") and then use > grep like "flo | grep :u:".  So you don't need one file for each tag. You’re right! I’ve removed tag support. flo just got one millisecond faster! It is h

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sun, Aug 15, 2010 at 10:04:18PM +0200, Alexander Teinum wrote: > I realize that there are ways to do this that are closer to the Unix > way of thinking. Editor of choice for adding and editing. Instead of > tagging items, one would should have one file for university and > another one for work i

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Mon, 16 Aug 2010 00:08:06 +0200 Alexander Teinum wrote: > > For timestamps that must be both human-readable and machine-readable, I > > just told you: -MM-DDThh:mm:ss-tz:tz (the fractional-second > > timezone should be optional).  (That paragraph wasn't entirely a > > joke.) > > Sorry, I

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

> For timestamps that must be both human-readable and machine-readable, I > just told you: -MM-DDThh:mm:ss-tz:tz (the fractional-second > timezone should be optional).  (That paragraph wasn't entirely a > joke.) Sorry, I misinterpreted what you wrote (“last standard that we’ll ever need” – the

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sun, Aug 15, 2010 at 02:14:51PM -0700, Robert Ransom wrote: On Sun, 15 Aug 2010 16:45:13 -0400 Kris Maglione wrote: On Sat, Aug 14, 2010 at 03:29:35PM -0700, Suraj Kurapati wrote: >On Sat, Aug 14, 2010 at 5:18 AM, Alexander Teinum wrote: >> http://github.com/alexanderte/flo > >Congratulatio

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sun, 15 Aug 2010 16:45:13 -0400 Kris Maglione wrote: > On Sat, Aug 14, 2010 at 03:29:35PM -0700, Suraj Kurapati wrote: > >On Sat, Aug 14, 2010 at 5:18 AM, Alexander Teinum wrote: > >> http://github.com/alexanderte/flo > > > >Congratulations on choosing the ISC license for your project. Too >

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sun, 15 Aug 2010 22:49:55 +0200 Alexander Teinum wrote: > Robert, what do you (and others here) think are the nicest date and > time formats? Just curious. For timestamps that must be both human-readable and machine-readable, I just told you: -MM-DDThh:mm:ss-tz:tz (the fractional-second t

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

Robert, what do you (and others here) think are the nicest date and time formats? Just curious. Alexander

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sat, Aug 14, 2010 at 03:29:35PM -0700, Suraj Kurapati wrote: On Sat, Aug 14, 2010 at 5:18 AM, Alexander Teinum wrote: http://github.com/alexanderte/flo Congratulations on choosing the ISC license for your project. Too many projects still use MIT/X these days when ISC is clearly more suckl

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sun, 15 Aug 2010 22:04:18 +0200 Alexander Teinum wrote: > > The nice thing about standards is that there are so many of them to choose > > from. > > I was thinking about that exact sentence while writing the sentence > that you quoted. We need more quotes about standards to choose from… > an

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

What I like about at your script and the Plan 9 one is that they don’t have a year specified. I don’t need that information unless I’m going to add an event for 2012, or if I still have an event from 2009. Huh… I’ll remove it from flo’s output I realize that there are ways to do this that are clos

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sun, 15 Aug 2010 19:38:19 +0200 Alexander Teinum wrote: > Right before I went back to $HOME, I realized that it was unnecessary > to include the dot-prefix. I decided to not follow that standard, but > if I did, I think $XDG_DATA_HOME would be a better place to put the > file. $XDG_DATA_HOME

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

What I would really like to see is a some kind of `when` clone with cron-like syntax written in C. I have just written very simple prototype of it in rc: #!/usr/bin/env rc date=`{date} month=$date(2) day=$date(3) while (line=`{read}) { if ({~ $line(1) '*' || ~ $line(1

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

Thanks for the feedback. Right before I went back to $HOME, I realized that it was unnecessary to include the dot-prefix. I decided to not follow that standard, but if I did, I think $XDG_DATA_HOME would be a better place to put the file. I will keep it as it is now, but I wish that there was one

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sat, Aug 14, 2010 at 03:29:35PM -0700, Suraj Kurapati wrote: > Congratulations on choosing the ISC license for your project. Too > many projects still use MIT/X these days when ISC is clearly more > suckless IMHO: because it has less LOL (lines of license ;-) Cheers. "License: ISC" don't mean

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

If you use $XDG_CONFIG_HOME, don't use dot in the name of config file. Look into your $XDG_CONFIG_HOME for examples. Looks like you have removed support for XDG_CONFIG_HOME. I don't like dotfiles and my XDG_CONFIG_HOME is set to $HOME/lib (and XDG_CACHE_HOME is set to $HOME/var). Directory names

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

Another similar program: http://www.lightandmatter.com/when/when.html

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

WTFPL has less LOL

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sat, Aug 14, 2010 at 5:18 AM, Alexander Teinum wrote: > http://github.com/alexanderte/flo Congratulations on choosing the ISC license for your project. Too many projects still use MIT/X these days when ISC is clearly more suckless IMHO: because it has less LOL (lines of license ;-) Cheers.

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

> s/i\.e\./e.g./ > > Ah, I see. Thanks. Alexander

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

On Sat, 14 Aug 2010 15:59:51 +0200 Alexander Teinum wrote: > The syntax is as short as it possibly can be – you type in the > information that you have available, and flo figures out if it’s an > event, a to-do, or a deadline. When you change an item, the to-do > might become i.e. an event. s/i\

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

> What's the difference to remind(1)? I haven’t used remind before, but I just got it from the Arch Linux package manager. Judging remind from its man-page, I’d say that flo is much simpler; which is a good or bad thing depending on what you need. flo only uses one file, and that’s ~/.flo. Taggin

Re: [dev] flo - a command line program for organizing events, to-dos, and deadlines

What's the difference to remind(1)?

[dev] flo - a command line program for organizing events, to-dos, and deadlines

I have been working on a program that makes it easy to keep myself, and perhaps others, in check. It’s inspired by suckless. I now consider it stable enough to share it with you. flo accepts a syntax like “.tag what,from-to”. All fields except what are optional. The program usually starts between