[Twisted-Python] Re: In Defense of Taps

Moshe Zadka m at moshez.org
Fri Feb 14 15:57:49 EST 2003


On Fri, 14 Feb 2003, Jp Calderone <exarkun at intarweb.us> wrote:

> The biggest problem I have is the amount of time it takes to backtrack from
> the end of a long command to somewhere in the middle to change an option,
> and this strikes me as a bash problem, not a Twisted one (one that
> lengthening the "twistd" invocation command would only exacerbate.

I'll go even further: frequently, the tap code is fairly "shallow": it
either works or doesn't, but has no subtle bugs. Thus, once you've
gotten the tap to work, the cycle is

mktap
twistd
debug, vi, blah
kill, run twistd (with same tap!)
debug, vi, blah
kill, run twistd (with same tap!)
rinse lather repeat

Oh, also, a comment about bash: if you're insane like me, you may want
to consider running bash in vi-mode. Then editing something in the middle
of a command can be easily done by word-jumping with b, w and e.
It is rumoured the common (EMACS mode) also has something like
that.
-- 
Moshe Zadka -- http://moshez.org/
Buffy: I don't like you hanging out with someone that... short.
Riley: Yeah, a lot of young people nowadays are experimenting with shortness.




More information about the Twisted-Python mailing list