From: markus schnalke <meillo@marmaro.de>
To: tuhs@tuhs.org
Subject: Re: [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c)
Date: Sun, 31 May 2020 15:01:48 +0200 [thread overview]
Message-ID: <1jfNb2-7JV-00@marmaro.de> (raw)
In-Reply-To: <CAC20D2Pm9_u8BiExe+ELjt0jb4qnB-d-bUFbNCvpXJnDma68yQ@mail.gmail.com>
Hoi.
[2020-05-28 09:46] Clem Cole <clemc@ccc.com>
>
> [...] until
> I finally switched from mh (actually the hm version) to the Gmail interface as
> my MUI client.
Would you be so kind to explain a bit about the hm version of MH.
Ten years ago I wanted to improve nmh, because I found it bad that it took
me months to configure it in so many ways to get it usable for modern
emailing. Even at that point I hadn't found some of its cool features, which
all were deactivated by default. I argued but couldn't convince the nmh
community. Later I used my master's thesis as the opportunity to create an
experimental version of nmh, to convince by demonstration.
Have a look at my master's thesis, if you like:
http://marmaro.de/docs/master/
Actually it became a fork, now named mmh. The project's still active.
Especially Philipp Takacs has done a lot, among that replacing m_getfld(),
a highly optimized mail reading function. See the pre-mmh version of it
for an entertaining read:
http://git.marmaro.de/?p=mmh;a=blob;f=docs/m_getfld.c.humor;h=46449095d
This is our replacement:
http://git.marmaro.de/?p=mmh;a=blob;f=sbr/m_getfld2.c;h=b9a618d16
I'm much interested in any MH background. Shockingly I cannot recall having
read about hm before ...
meillo
next prev parent reply other threads:[~2020-05-31 13:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 12:34 [TUHS] fmt(1): history, POSIX, -t, -c markus schnalke
2020-05-28 13:08 ` Rob Pike
2020-05-28 13:30 ` Clem Cole
2020-05-28 13:47 ` Clem Cole
2020-05-28 16:08 ` Mary Ann Horton
2020-05-28 18:00 ` Clem Cole
2020-05-28 18:35 ` Richard Salz
2020-05-28 18:51 ` Clem Cole
2020-05-29 0:18 ` Greg 'groggy' Lehey
2020-05-29 5:10 ` Michael Stiller via TUHS
2020-05-29 5:19 ` Greg 'groggy' Lehey
2020-05-29 13:39 ` Clem Cole
2020-05-29 15:43 ` Warner Losh
2020-05-29 16:12 ` Clem Cole
2020-05-29 17:14 ` Mary Ann Horton
2020-05-28 13:46 ` Clem Cole
2020-05-31 13:01 ` markus schnalke [this message]
2020-05-31 14:53 ` [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c) Clem Cole
2020-05-31 16:25 ` Richard Salz
2020-05-31 16:50 ` Larry McVoy
2020-05-31 17:09 ` Ralph Corderoy
2020-05-31 17:25 ` Jon Steinhart
2020-05-31 17:28 ` [TUHS] mh/hm, mmh Mary Ann Horton
2020-05-31 18:56 ` Eric Allman
2020-05-31 19:49 ` Clem Cole
2020-05-31 21:31 ` Mary Ann Horton
2020-06-01 6:32 ` Caipenghui
2020-06-01 7:14 ` markus schnalke
2020-05-31 12:35 ` [TUHS] fmt(1): history, POSIX, -t, -c markus schnalke
2020-06-03 0:43 [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c) Bakul Shah
2020-06-03 0:49 ` Clem Cole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1jfNb2-7JV-00@marmaro.de \
--to=meillo@marmaro.de \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).