| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
9a942b1d-a3b5-441d-8aef-b844700e1efa
Aaron says it's already implemented in the Bugs-Everywhere-Web, and
$ be show `be list --status all --uuids` | grep -A5 -B5 XYZ
works pretty well for me on the command line.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The new setting is currently only used when creating new bugs with
becommand/new.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If bug_A had no comments (and so, no comment directory), changing
comment settings before saving raised missing directory errors.
save_settings had previously assumed the
.be/bugs/XYZ/comments/
directory existed, which wasn't true for comment-less bugs. Now it
checks, and creates the directory if necessary.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I also disabled interspersed options and arguments in
cmdutils.CmdOptionParser. See
http://docs.python.org/library/optparse.html
Now
$ be severity xyz --complete
returns available severities. It had previously returned
--help --complete
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Per-tree severity levels working.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I adjusted the YAML format following
http://pyyaml.org/ticket/11
Unicode support
To remove '!!python/unicode' escapes and allow unicode in the output.
We can always have unicode in the output because the output is encoded
(as per the BugFile.encoding setting) before being sent to the outside
world.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
becommands/severity gets the configured settings appropriately.
Todo:
adjust setting-validation to compare against the current values.
setup becommands/severity to --complete severities.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
They currently have no effect, but you can see them with
$ be set
There's a lot of information in this one 'settings' variable. I think
set will have to be specialized to handle arrays smoothly...
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes e2f6514c-5f9f-4734-a537-daf3fbe7e9a0
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
settings_object.SavedSettingsObject encapsulates some of the common
settings functionality in the BE BugDir, Bug, and Comment classes.
It's a bit awkward due to the nature of scoping in python subclasses,
but it's better than reproducing this code in each of the above classes.
Now I need to move Bug and Comment over to *this* system ;).
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Also some typo corrections and some reworking of bug/bugdir to better
support the lazier loading.
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | | |
libbe/bug has been moved over to the new system.
comment and bugdir still to go.
|
| | | |
|
| | |
| | |
| | |
| | | |
The code is a bit uglier now, but it's a good deal faster :).
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now most of the bug-id arguments support Bash completion. Since there
will hopefully be lots of bugs in the database, I decided to filter
the list of available bugs. Currently, we just auto-complete active
bugs for most commands, with the exceptions of open (obviously) and
status (which needs to work on all types of bugs).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
All the other commands currently use default_complete(), which has no
effect other than catching the --complete option and effectively
aborting execution.
This closes 8e1bbda4-35b6-4579-849d-117b1596ee99
|
| | | |
|
| | |
| | |
| | |
| | | |
I'm still working on a clean implementation though...
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A'la ditz
http://gitorious.org/projects/ditz
See also this good intro to bash completion
http://www.debian-administration.org/articles/317
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I borrowed most of the code for this.
get_encoding() is from Trac
http://trac.edgewall.org/browser/trunk/trac/util/datefmt.py
format_datetime()
Trac has a BSD license
http://trac.edgewall.org/wiki/TracLicense
I don't know if such a small snippet requires us to "reproduce the
above copyright" or where we need to reproduce it if it is needed.
The stdout/stdin replacement code follows
http://wiki.python.org/moin/ShellRedirectionFails
Because of the stdout replacement, the doctests executes now need an
optional 'test' argument to turn off replacement during the doctests,
otherwise doctest flips out (since it had set up stdout to catch
output, and then we clobbered it's setup).
References:
http://wiki.python.org/moin/Unicode
http://www.amk.ca/python/howto/unicode
http://www.python.org/dev/peps/pep-0100/
I also split libbe/editor.py off from libbe.utility.py and started
explaining the motivation for the BugDir init flags in it's docstring.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The situation really calls for a global encoding setting rather than
lots of hardcoded "utf-8"s. See bug
f7ccd916-b5c7-4890-a2e3-8c8ace17ae3a
|
| | | |
|
| | | |
|
| |/
|/|
| |
| |
| | |
Kindof a cludgy check, but there's currently no simpler way to find
valid entries for a given setting name (that I can think of).
|
| |
| |
| |
| | |
I tried to stick to CAPS for argument placeholders.
|
| |
| |
| |
| |
| | |
Also emptied becommands/__init__.py. I didn't understand the plugin
interface when I wrote it.
|
| |
| |
| |
| | |
It's been fixed for a while
|