| 03:59 | <Domenic> | uh... I will need to run this against the entire html spec... not sure cut and paste field is going to work |
| 10:05 | <annevk> | Domenic: were you going to take on the hgroup thing? I don't think I'll get to it before somewhere next week, but there's a small chance I have enough time later today to give it a go. |
| 10:06 | annevk | wonders if Ms2ger 💉💉💉 was trolling above |
| 10:15 | <jgraham> | Random bikeshed feature request (there must be a better place for these): in the output it would be really nice if e.g. clicking on a <var> highlighted other instances of the same variable in the same algorithm. |
| 10:17 | <Ms2ger 💉💉💉> | jgraham: it does |
| 10:17 | <Ms2ger 💉💉💉> | But you may need to be inside a <div algorithm> |
| 10:18 | <annevk> | (the place for non-existing feature requests is on GitHub) |
| 10:19 | <evilpie> | I really like this highlighting, I wished it worked on https://w3c.github.io/webappsec-csp/ |
| 10:19 | <jgraham> | OK, then fetch spec request: I wish fetch was updated to work with this feature :p |
| 10:20 | <Ms2ger 💉💉💉> | OK, then fetch spec request: I wish fetch was updated to work with this feature :p |
| 10:21 | <jgraham> | Yep, I can of course file a GitHub issue. Although apparently moaning here was effective in that it quickly identified the source of the problem. |
| 10:28 | <Domenic> | Domenic: were you going to take on the |
| 10:28 | <Domenic> | I won't work on it for at least another 16 hours. |
| 14:15 | <wanderview> | Cut and paste is what I use |
| 14:16 | <wanderview> | Or are the rules for wrapping written out somewhere so I can do them as I go? I'm thinking, how to properly split element across boundary, etc. It does not seem obvious where splits are allowed or not. |
| 15:47 | <Dominic Farolino> | I think we just split wherever the latest space character is before 100 lines |
| 15:48 | <Dominic Farolino> | FWIW we've been working to port the great rewrapper to a tool that you can run on the spec file itself. It will (soon) only impact the diff of your current branch: https://github.com/domfarolino/specfmt |
| 16:16 | <annevk> | Dominic Farolino: will that work for Bikeshed and Wattsi? |
| 16:17 | <annevk> | Dominic Farolino: seems like it might, wow, thank you so much for tackling that. I hope it works well as that would indeed help contributors (and reviewers!) quite a bit. |
| 16:19 | <annevk> | Jake Archibald: ^^ |
| 16:20 | <Jake Archibald> | ohhhh very nice! |
| 16:20 | <Dominic Farolino> | Yeah it doesn't discriminate on any kind of file type really, but for right now at least it is basically just the rewrapper in non-website form + some "automatically find the spec file to format in this directory" logic. I'm now working on making it only apply to the changes in your current branch |
| 16:21 | <Dominic Farolino> | And later ideally it would do more than just rewrapping, but not sure how far we want to go with that heh |
| 16:22 | <Jake Archibald> | Dominic Farolino: it'd be great if it could support annevk-style wrapping, where it never wraps in the middle of terms (like definitions or references), so ctrl+f still finds stuff |
| 16:25 | <annevk> | Yeah honestly that is very nice, having to \s+ everywhere is somewhat tiresome and something one easily forgets |
| 16:31 | <annevk> | Dominic Farolino: if we can get to the point where we can enforce it in CI (or make it do fixups) that would be the best. Would essentially remove an entire category of review feedback and churn. |
| 17:02 | <Dominic Farolino> | I do personally prefer annevk-style rewrapping, but IIRC there is some disagreement around that more generally. I guess even if we use it from here on out, we'd still have to use \s+ for all the old lines that we aren't changing....unless we go back and do those. |
| 17:02 | <Dominic Farolino> | Something like a "CI" mode sounds like a very good idea |
| 17:13 | <annevk> | Dominic Farolino: at least for my specs I'd want this to apply to the whole file as some kind of Meta reformat commit and then enforce the tooling for all commits |
| 17:24 | <Dominic Farolino> | Makes sense, that could be configurable |
| 18:51 | <wanderview> | this future automated world sounds very nice, thanks for working on it! |
| 18:52 | <wanderview> | for now, though, it sounds like I can split at any space character, except in the middle of a span or dfn because we want to ctrl-f terms? |
| 20:27 | <annevk> | wanderview: for HTML you make the longest possible string and split on the first space before 100 columns |
| 20:27 | <annevk> | (or at 100 columns, I suppose) |
| 20:28 | <wanderview> | even if its in the middle of a span reference? |
| 20:28 | <annevk> | wanderview: yeah HTML is one of the specs where you need to litter your searches with \s+ |
| 20:28 | <wanderview> | ok, thanks |
| 20:28 | <wanderview> | I've been searching for the concept-document-foo tags instead |
| 20:28 | <annevk> | wanderview: it's documented at https://github.com/whatwg/html/blob/main/CONTRIBUTING.md#source-formatting |
| 20:28 | <annevk> | wanderview: that works if there's a data-x, but that isn't always the case |
| 20:29 | <wanderview> | thanks again |