Ellie Huxtable

Something like what @dcarosone could be done pretty easily and would make a good workaround Supporting actual + proper deletion might prove a little more tricky. The issue lies in...

Thanks for that @bvergnaud! Really nice workaround > None of this is as neat as a proper handling of commands prepended by space(s), nor does it solve the use case...

Working on it, but it involves some larger changes around how sync works :)

> Should the import process ignore lines beginning with the history comment character? (Is this configurable or always #? no idea!) I think in an ideal world, we would parse...

> On enum value naming, perhaps `return-original` instead of `returnoriginal` would be better etc...? I think this would definitely read better!

I'd be happy to increase the max size of this field, as I doubt you'll be the only one running into this problem! Perhaps 16,384? We'd need to create another...

Need some thinking around proper validation here, we can't just ignore insertions because then remote/local have different history + won't sync very well For now I've partly mitigated this in...

> First of all, the server should never crash on invalid/malformed/whatever input, that’s DoS vulnerability. The server doesn't actually crash on a long entry, but the handler does error out....

I'd be happy to get this one out, but I think it would also make a pretty good first issue for someone. Happy to help out + provide guidance if...

could you try deleting them via the `sqlite3` CLI? like ``` delete from history where command = 'the command you want to delete'; ```