On Thu May 25, 2023 at 2:53 AM CDT, Robin Jarry wrote:
> Bence Ferdinandy, May 25, 2023 at 07:46:
> > On Thu May 25, 2023 at 06:41, Tristan Partin wrote:
> > > I guess the only other problem I have with ProtonMail is that the emails
> > > display out of order. Like I have emails from 2021 near the top.
> > > Wondering if I need to enable some of the sort UI options...
> >
> > Yeah, :sort -r date is probably what you are looking for
>
> You may also try:
>
>     [ui]
>     force-client-threads = true

I guess the only other problem I have with ProtonMail is that the emails
display out of order. Like I have emails from 2021 near the top.
Wondering if I need to enable some of the sort UI options...

-- 
Tristan Partin
https://tristan.partin.io

Build failure seems unrelated.

-- 
Tristan Partin
https://tristan.partin.io

Based on information from the mailing list and my own experience, I can
confirm that these example settings work.
---
 providers/protonmail.md | 34 ++++++++++++++++++++--------------
 1 file changed, 20 insertions(+), 14 deletions(-)

diff --git a/providers/protonmail.md b/providers/protonmail.md
index cd32095..9cf66bb 100644
--- a/providers/protonmail.md
+++ b/providers/protonmail.md
@@ -5,29 +5,35 @@ title: "aerc-wiki: Providers/ProtonMail"
 # ProtonMail
 
 Using ProtonMail with aerc is not trivial, as you will likely
[message trimmed]

I will put something together.

-- 
Tristan Partin
https://tristan.partin.io

Drew,

Thanks for the post. I would be interested in learning a little bit
more about how to combine a chroot with qemu-user in order to setup a
cross-compilation environment, whether that is a pointer to the docs or
another blog post that talks about how you use it for Hare development.

Thanks,

Tristan Partin

https://json.schemastore.org/sourcehut-build-0.65.0.json

Not sure where it is maintained, but someone on this
list was involved with it.

pathuf supports constructing a path up to PATH_MAX.
---
 include/platform/pathbuf.h | 15 +++++++++++
 src/platform/meson.build   |  1 +
 src/platform/pathbuf.c     | 53 +++++++++++++++++++++++++++++++++++++
 tests/unit/meson.build     |  1 +
 tests/unit/pathbuf.c       | 54 ++++++++++++++++++++++++++++++++++++++
 5 files changed, 124 insertions(+)
 create mode 100644 include/platform/pathbuf.h
 create mode 100644 src/platform/pathbuf.c
 create mode 100644 tests/unit/pathbuf.c

diff --git a/include/platform/pathbuf.h b/include/platform/pathbuf.h
new file mode 100644
[message trimmed]

Owen,

I am so stupid! I never saw this email in my inbox. I have been
iterating on my website quite a bit recently, and finally got enough
blogs down to realize the mistake I made here. Ended up fixing other
pagination issues as well.

I ended up finding your blog. Cool that your site looks a lot like
mine. I made quite a few changes around how it is configured, so if
you wanted to pull updates from the source html files, it should be
much easier now.

Maybe at some point I will actually get a real Hugo theme going.

This really has nothing to do with my non-existsent obsession about
a status badge.

Say my pipeline publishes something to PyPI. I should be able to
take the release from PyPI, see what git tag was associated with it,
and look up the pipeline associated with that release easily. In the
case of the alpine build I presented in my last email, because of the
resubmit, people would not easily be able to associate the tag with
the specific build pipeline that published the Python package. That
pipeline would just be orphaned forever.