| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
The notes filter will return every game whose notes field is non-empty.
Useful for client-building and/or automation.
Run `vgstash init` after upgrading to recreate any missing (or new)
filters.
|
|
setup.py wasn't being included, preventing distros from easily building
it. Whoops.
|
|
To migrate, run these two commands:
sqlite3 /path/to/vgstash.db 'DROP VIEW backlog;'
vgstash init
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Before, vgstash.DB.list_games() would default to 'allgames' and silently
hide it when a filter wasn't found. This commit ensures that the vgstash
package and CLI both indicate when an invalid filter is passed to them:
* vgstash.DB.list_games() will return False on a failure to match;
* vgstash_cli uses Click's Choice object to enforce the constraint
|
|
|
|
|
|
Also tweaked the export command to report correctly.
|
|
The export command is like the import command; currently supporting YAML
output, but ready to be expanded as needed.
|
|
Currently the import command will only accept YAML files, but is ready
for expansion to other formats as needed.
|
|
|
|
The "notes" command will show the user what their notes for a particular
game are. The output can be piped anywhere the user wants, such as a
pager or a file.
If "notes" is passed with the "--edit" or "-e" flag, vgstash will open a
temporary file with the game's notes already inside and edit it using
the program pointed to by the EDITOR environment variable. When the
editor is closed (with a successful exit status), vgstash updates the
game's notes and exits.
The defaults for the testing environment ("cat" for non-interactive,
"vim" for interactive) may need tweaking on other operating systems.
Patches for these platforms are very welcome.
|
|
|
|
Two helper functions were also added to the vgstash package to ease
client workflows.
This commit marks the final core function necessary to manipulate a
vgstash DB on the command line.
|
|
Unlike the old version of vgstash, the new one does not accept row IDs
as arguments for removal. Instead, it accepts two mandatory arguments:
the title of the game, and the system it's on. This is in line with the
database itself, using the title and system as primary keys.
|
|
The sqlite database already uses a game's title and system as the
primary keys. Row IDs are redundant.
|
|
|
|
|
|
Also add the "--width" option to specify the maximum width of the table.
|
|
|
|
Add '--raw' option to the list command, in addition to proper note
expansion. Newline characters in notes are escaped to be friendly to
scripting. This option may be shortened to '-r' at the user's
convenience.
In raw output mode, the information is formatted in plain pipe-delimited
strings, one line per row:
title|system|ownership|progress|notes
ownership and progress are printed in their numeric form, consistent
with the OWNERSHIP and PROGRESS dictionaries in the vgstash package.
An empty notes field will result in a line ending with a pipe and no
whitespace following it.
|
|
|
|
Whoops.
|
|
This commit is huge, but contains everything needed for a "proper" build
system built on pytest + tox and a CLI built with click.
For now, this branch will contain all new vgstash development activity
until it reaches feature parity with master.
The CLI is installed to pip's PATH. Only the 'init', 'add', and 'list'
commands work, with only two filters. This is pre-alpha software, and is
therefore not stable yet.
|
|
It's time for a refactor to a module; the functionality and interface
are clashing.
|
|
|
|
This filter is used to get an idea of which games you're currently
playing through, so you can prioritize games to play when you're bored
and detect it when you've beaten a game but haven't marked it as such.
|
|
At present, user modification is needed to make these seamless. vgup()
may need to be axed in favor of telling the user to make an alias.
|
|
It used to point to a directory, which would then look for .vgstash.db.
This behavior was kind of backwards and I don't remember why I did it
that way. This change gives users more control over where they put their
DB.
Be sure to update your environment variable if you have it set!
|
|
Sourcing them in .bash_profile screws up login if they're set.
|
|
|
|
|
|
|
|
Loops and functions -- oh my, what a useful combination. :)
|
|
|
|
|
|
|
|
Also correct a typo.
|
