On 16 August 2010 02:49, anonymous ya6io...@lavabit.com 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
On Wed, 18 Aug 2010 01:27:22 +0200
Alexander Teinum atei...@gmail.com wrote:
How many of these small tools are there?
moreutils rock. they really fill some gaps. niche, but still.
Dieter
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
s/ISO 6801 date/ISO 6801 week/
Damn right!
Alexander
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
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. ;_;
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 s.nikhil...@gmail.com wrote:
I made a flo-git package for AUR then when I was about to submit I found
that there was already flo-git
On Tue, Aug 17, 2010 at 6:50 PM, Andreas Wagner
andreasbwag...@gmail.com 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
* Andreas Wagner andreasbwag...@gmail.com [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
On Tue, Aug 17, 2010 at 10:19 AM, Alexander Teinum atei...@gmail.com wrote:
On Tue, Aug 17, 2010 at 6:50 PM, Andreas Wagner andreasbwag...@gmail.com
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
$ flo do something
…
$ flo -c 1b4e28ba-2fa1-11d2-883f-b9a761bde3fb -w do something else
…
I’ll think about it.
On Tue, Aug 17, 2010 at 2:56 PM, Nikhilesh S s.nikhil...@gmail.com 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
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.
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,
On Wed, 18 Aug 2010 01:38:26 +0300 (AST)
Nikhilesh S s.nikhil...@gmail.com 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
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
On Wed, 18 Aug 2010 01:27:22 +0200
Alexander Teinum atei...@gmail.com 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
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 harder
\fg %jid ?
Dne 16.8.2010 12:43 Moritz Wilhelmy c...@wzff.de napsal/a:
In bourne-like shells, fg is absolutely necessary to manage job control.
How do you put your jobs back into foreground?
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
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
Another similar program: http://www.lightandmatter.com/when/when.html
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
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
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) '*' || ~
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
On Sun, 15 Aug 2010 22:04:18 +0200
Alexander Teinum atei...@gmail.com 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
On Sat, Aug 14, 2010 at 03:29:35PM -0700, Suraj Kurapati wrote:
On Sat, Aug 14, 2010 at 5:18 AM, Alexander Teinum atei...@gmail.com 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
Robert, what do you (and others here) think are the nicest date and
time formats? Just curious.
Alexander
On Sun, 15 Aug 2010 22:49:55 +0200
Alexander Teinum atei...@gmail.com 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
On Sun, 15 Aug 2010 16:45:13 -0400
Kris Maglione maglion...@gmail.com 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 atei...@gmail.com wrote:
http://github.com/alexanderte/flo
Congratulations on choosing the ISC
On Sun, Aug 15, 2010 at 02:14:51PM -0700, Robert Ransom wrote:
On Sun, 15 Aug 2010 16:45:13 -0400
Kris Maglione maglion...@gmail.com 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 atei...@gmail.com 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 misinterpreted what you wrote (“last standard that we’ll ever
need” – the
On Mon, 16 Aug 2010 00:08:06 +0200
Alexander Teinum atei...@gmail.com 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.)
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
What's the difference to remind(1)?
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.
On Sat, 14 Aug 2010 15:59:51 +0200
Alexander Teinum atei...@gmail.com 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.
On Sat, Aug 14, 2010 at 5:18 AM, Alexander Teinum atei...@gmail.com 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
WTFPL has less LOL
41 matches
Mail list logo
