booki
but in C, 'cause why not?
many previous iterations here and here
Differences between (current state) cbooki and the (current iteration) Python version:
| Feature | Current Version | cbooki |
|---|---|---|
add |
works | works |
discover |
works | doesn't exist |
| sorting | by author last name | by order in file |
| styling | title underlined | no styling |
--show |
only at end of command | anywhere in command |
| lists | anywhere in file | on string fields |
search |
by author, title, on | on any field |
accents in search |
must be explicit | diacritic-insensitive |
| editing | preserves file order | edits brought to bottom of file |
Things that work:
- [x]
searchwith arbitrary query items - [x] multiple
searchquery items - [x]
--showto print out ~~most~~ all attributes
Things that don't work:
- [ ]
searchwith more than 5 query items - [x] searching for a single author in a multi-author item
- [x] ~~printing any array thing~~ support for
on,author,language, andtranslator - [x] ~~
^or$in string searching~~ should work - [ ] sorting in any way
Things that might change:
- [ ]
--showmight want to limit by field - [x] now parsing manually ~~currently uses tomlc99, which is great but might be overkill for this~~
- [x] ~~maybe prefixed
<or>for numeric searches~~ prefixes are+for greater and~for less - [x] ~~format strings~~ with
--formatsupports names of fields in surrounding%characters, i.e. the default is%title% by %author% - [ ] discover endpoint
- [ ] how much lives on the stack vs the heap
