wodny

Because this issue is still open I would like to suggest some further changes in a paragraph next to the one mentioned. There is a [discussion](https://users.rust-lang.org/t/why-can-lifetimes-not-be-inferred/25645/18) at the user's forum...

@levb I've looked at the history and it seems that the set of characters for matching without using `\b` is the same since the beginning, i.e. d0760cfb3bd49895ce37e99d589181972088be30 (went through all...

> @wodny Appreciate the contribution and understand the intent. I'll need to look into the history carefully. The custom delimiter set (as opposed to `WordMatch=true`) has a long history of...

@levb @iomodo So I came to a conclusion that the more complex regex isn't pretty. Modifying the code to apply only the first matching pattern/template to a piece of text...

> > I wonder if the best solution would just be to make the entire prefix (and suffix) user-customizable, with a meaningful (`\b`?) default. It can be added as an...

> I wonder if the best solution would just be to make the entire prefix (and suffix) user-customizable, with a meaningful (`\b`?) default. It can be added as an extra...

It would be great to have a `htmx:beforeOnLoad` analog and a possibility to reject an update from a WebSocket. For now I've created a wrapper class that overrides `addEventListener()` and...

Also an optional tree view with RFCs from the "Updated by" section in a subtree might be useful.

This problem goes beyond custom code not reaching the client during application shutdown. I observe the same problem (aiohttp 3.8.1) when calling `WebSocketResponse.close()` during normal application operation, eg. when I...

I've used the following workaround on a server that is wrong in guessing content encoding via `mimetypes.guess_type()`: ```python async def on_response_prepare(request, response): if not response.compression: response.headers.popall("Content-Encoding", None) return response app.on_response_prepare.append(on_response_prepare)...