Michael Davis

I force-pushed a version without the formatting changes (no hard-wrapping at 80 and no changes to table layout) following up on https://github.com/helix-editor/helix/pull/5545#issuecomment-1399323148. You can compare the changes [here](https://github.com/helix-editor/helix/compare/07cbc5475c1018ef1e4982650995d34bc335eea5..3901d60911d9a5caef2718ce02f84dc7200a9c7a). I also...

Ah no worries, I think I still have the branch locally so I might be able to force-push it back or it might work to drop the merge commits. When...

Ok it looks like this only needed a revert of the merge commit in 7c84042 so no need to `git reset --hard` for this change, you should only need to...

Hmm, we may want to abandon the 80-column formatting change. I like 80 columns but it causes a bunch of formatting churn with the existing docs. It will matter much...

The problem is with bundling content changes with auto-formatting changes - switching to different auto-formatting settings won't really make a difference. I could go through the #5543 changes and rewrite...

Yep it would just be rewritten commit(s) on your branch in that PR. You would still be the author on the commits too. I'll rebase the changes on master so...

Being able to share queries would be really nice! I'm not sure how to accomplish it though because they queries tend to be implementation-specific. Indentation is a good example: the...

> We are now in the process of (incrementally) moving things that work well into core -- which is a chance for changing things, so this is now a good...

Yeah I think it would be preferrable to use libc directly. Pulling in nix for a handful of small functions doesn't seem worth it.

Ah, I had actually already started on a PR to Erlang/OTP. I will submit what I have upstream and they can take it over or supersede it if they'd like...