Russell Mull

We've experimented with various flavors of this. For awhile we used git appraise, which has a CLI along the lines described by OP. We found it basically unusable, to the...

I'm seeing the same problem, but minus the errors. I'm on Kubuntu 19.04 (KWin 5.15.4)

> After running the fuzzer for a little awhile, we run out of file handles. It seems like something in this library is leaking, but it's unclear where or why....

Sorry for the delay, it's over at https://github.com/tokahuke/yaque/pull/22

I was able to investigate the `recv_batch` situation a bit, and developed a repro: ```rust // test simple try_recv_batch uses. #[test] fn test_try_recv_batch_too_much_then_less_than_everything() { // Populate a queue: let mut...

Breaking execution with debug enabled gives: ```Debugger entered--Lisp error: (quit) sp-point-in-string() sp--do-action-p("(" navigate) sp--get-allowed-stringlike-list() sp--get-stringlike-regexp() sp-get-stringlike-expression(nil) sp-get-stringlike-or-textmode-expression(nil #("'" 0 1 (face font-lock-comment-face fontified t))) sp-get-expression(nil) sp-get-sexp() sp-get-enclosing-sexp(1) sp-up-sexp(-1 nil) sp-backward-up-sexp()...

I've noticed that `sp-kill-hybrid-sexp` does nearly the same thing as `evil-sp-delete-line`, so for the moment I've bound `D` to that. How is the behavior of the two supposed to differ?...

:-D I'm happy that it helped you! I'll leave this issue open so you can post a link to your own implementation when it's done ;)

Some emacs features this is like, to help future issue searchers land here: - Dynamic abbrevs, dabbrev, dabbrev-completion - Hippie expand, hippie-expand

For `rust-analyzer` specifically, I have been able to work around this by putting this in `${PROJECT_ROOT}/.zed/settings.json`: ```json { "lsp": { "rust-analyzer": { "initialization_options": { "linkedProjects": [ "relative/path/to/Cargo.toml", "relative/path/to/another/Cargo.toml" ] }...