Michał Siedlaczek

I don't have anything to bring to discussion regarding `Expects`/`Ensures` at the moment, but regarding `span`, wouldn't it make sense to have safe-by-default access but also have an "unsafe" part...

I agree with @MikeGitb, it's clear to me that the goal is to have safe access by default. > As for providing alternatives like at or unsafe_at, why should I...

> I don't actually think there is a big question about what a contract is. e.g. the terms wide an narrow contracts are well established. The big discussion is around...

I fully agree with @MikeGitb and @BjarneStroustrup, if the intent is to have safe access with runtime bound check, then `span` shouldn't use contracts for that. A somewhat separate issue...

@wgmayer0 what exactly do you mean by "automatically" and "any and all"? Here's what I got in my mailcap: ``` text/html; qutebrowser %s; needsterminal; nametemplate=%s.html ``` and in my `neomutrc`:...

@wgmayer0 not sure if that helps but I also have a separate binding: ``` macro index,pager B "html" ``` It's not exactly what you want but it's something. It works...

Unfortunately, I have no idea. Maybe @flatcap or @dcpurton can tell if my macro can be tweaked this way.

@flatcap this is my first attempt at making this work. Looks to be working, but let me know if this is the right direction. I'll try to add some tests...

> Note: I've made the Pull Request into a "draft" while you develop -- it reduces the load on GitHub Thanks, need to remember this for the next time.

Added some changes. I was wondering, would it be correct to check for new (and not notified) messages using `Email`s `received` value? Say, we would store time of last notification,...