about summary refs log tree commit diff
Commit message (Collapse)AuthorAge
...
* Rename unscoop -C to -cJune McEnroe2020-01-04
| | | | For consistency with scoop.
* Expand scoop(1) documentationJune McEnroe2020-01-04
|
* Improve litterbox(1) documentationJune McEnroe2020-01-03
|
* Add install and uninstall targetsJune McEnroe2020-01-01
|
* Assert that SQL query fits in bufferJune McEnroe2020-01-01
|
* Don't special case user being * in queriesJune McEnroe2020-01-01
| | | | | | It's a side-effect of imports that shouldn't surface elsewhere. Would be nice to have unscoop figure out how it can eliminate using * in more places.
* Factor out hashing functionJune McEnroe2020-01-01
|
* Add option for custom where expression to scoopJune McEnroe2020-01-01
|
* Document ENVIRONMENT in scoop(1)June McEnroe2020-01-01
|
* Add before and after optionsJune McEnroe2019-12-31
|
* Add scoop IRC output formatJune McEnroe2019-12-31
|
* Add scoop output format optionJune McEnroe2019-12-31
|
* Refactor scoop formatters and group colored outputJune McEnroe2019-12-31
|
* Add strftime format string optionJune McEnroe2019-12-31
|
* Refactor binding in scoopJune McEnroe2019-12-31
|
* Add option to group events by contextJune McEnroe2019-12-31
|
* Add missing includeJune McEnroe2019-12-31
|
* Use standout mode for highlightingJune McEnroe2019-12-31
|
* Rewrite scoop(1) argument descriptionsJune McEnroe2019-12-31
|
* Color both nicks in a changeJune McEnroe2019-12-31
|
* Implement nick-colored outputJune McEnroe2019-12-31
|
* Only enable highlighting on terminal outputJune McEnroe2019-12-31
|
* Set up pager pipeJune McEnroe2019-12-31
|
* Normalize date inputJune McEnroe2019-12-30
| | | | Mostly this just allows the use of 'now'.
* Add initial rough version of scoopJune McEnroe2019-12-30
|
* Join with USING wherever possibleJune McEnroe2019-12-30
|
* Add -D flag to prospective scoop manualJune McEnroe2019-12-30
|
* Order results by ID in outer query in litterboxJune McEnroe2019-12-30
|
* Use X macro for Type enumJune McEnroe2019-12-30
|
* Remove scoop -ABCJune McEnroe2019-12-30
| | | | | | I can almost get these to work with an inner and outer SQL query, but when contexts starts overlapping it becomes a disaster, so I'm leavin it out at least for now.
* Add limit option for litterbox's search query interfaceJune McEnroe2019-12-30
|
* Add prospective scoop manual pageJune McEnroe2019-12-30
|
* Send fts5 errors in response to queriesJune McEnroe2019-12-28
|
* Don't insert self-messagesJune McEnroe2019-12-28
| | | | | Even with NOTICEs litterbox would sometimes receive its own responses, which would create duplicates in the database, essentially.
* Run PRAGMA optimize in dbCloseJune McEnroe2019-12-28
|
* Call tls_close and dbClose in atexitJune McEnroe2019-12-28
|
* Move querySearch code aroundJune McEnroe2019-12-27
|
* Add nick coloring to search query resultsJune McEnroe2019-12-27
|
* Reply to search queries with NOTICEJune McEnroe2019-12-27
| | | | | When connected to pounce, it's possible to receive some of its own PMs, so it should respond with what can't be commands.
* Add search query interfaceJune McEnroe2019-12-27
|
* Use bsearch to find handlerJune McEnroe2019-12-26
| | | | | | | | | The code is a bit cleaner this way I think, and performance would be better if the list of handlers ever got very long, and it was sorted anyway. However, I would prefer if there were a way to enforce the list being sorted at compile-time.
* Handle ERRORJune McEnroe2019-12-26
|
* Make sure context exists in handleReplyTopicJune McEnroe2019-12-26
|
* Inline queries, move stuff aroundJune McEnroe2019-12-25
| | | | | | No idea now why I wanted to have network bound all the time. Ended up creating a copy of the string for each statement instead of just having one like this.
* Treat topics like motdsJune McEnroe2019-12-25
| | | | | It's more like a cache of existing topics. events is still meant to record actual topic events.
* Insert MOTDs into the databaseJune McEnroe2019-12-25
|
* Insert existing topics into the databaseJune McEnroe2019-12-25
| | | | | | | Not sure how to handle the 333 reply that contains the user who set the topic and the timestamp of when it was set, since they're two separate messages that aren't really easily correlated since there's no guarantee that you're even going to get a 333 at all.
* Handle SIGINT and SIGTERMJune McEnroe2019-12-25
|
* Only send JOIN if there are channels to joinJune McEnroe2019-12-25
|
* Broadcast nick to user and host if they're unsetJune McEnroe2019-12-25
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-27 19:34:56 +0000