| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
one place and make things clearer to the uninitiated. Here's my
current understanding:
.
|-- libbe (the guts of BE)
|-- becommands (plugins for all "be *" commands)
|-- doc (documentation, currently just the man page)
|-- interfaces (non-commandline interface implementations)
| |-- web
| | |-- Bugs-Everywhere-Web (in Turbogears)
| |-- gui
| | |-- beg (in Tkinter)
| | `-- wxbe (in WX)
| |-- email
| `-- xml (xml <-> whatever conversion)
`-- misc (random odds and ends)
`-- completion (shell completion scripts)
Note that I haven't attempted to use the web or gui interfaces in a
while, so I'm not sure how well they're holding vs the core
development.
|
| |
|
|
|
|
|
|
| |
Oops. I seem to have removed it in my Thu 2008-11-27 19:35:55 -0500
commit. Luckily, the version I removed was still sitting right were
it belongs as
/etc/bash_completion.d/be
Now it will be back in the tree.
|
| |
|
|
| |
The code is a bit uglier now, but it's a good deal faster :).
|
| | |
|
|
|
I'm still working on a clean implementation though...
|
