From: Daniel Moch <daniel@danielmoch.com>
To: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Nail: embrace, extend, extinguish
Date: Tue, 29 Dec 2020 05:46:12 -0500 [thread overview]
Message-ID: <87642E8697B6D1A0A459086FAC32B644@ranger.org> (raw)
In-Reply-To: <44AACD2185ABA9EE63E0A87C0979A034@eigenstate.org>
Quoth ori@eigenstate.org:
> Nail was designed from the start as a replacemnt
> for Acme mail. I think it's ready.
>
> The default view will chagne -- it's compact and
> threaded, but those who want the old appearance can
> get it:
>
> Nail -T -f'%F %{WWW DD MM hh:mm}\n%s'
>
> Are there any objectons our outstanding bugs that
> need to be fixed before this goes in?
Two comments, one question.
First, the question: How are you going to handle the manual? 9front
already has a mail(1). (I'm assuming Nail becomes Mail when it gets
merged.)
Now the comments:
- The manual doesn't document the format specification you mention
above for the default view. In fact, the above example *seems* to
link the format string to the -f flag, but the manual says -f is
used to specify the maildir (which I believe matches Mail). I
basically can't make sense of what's going on there.
- The font set I use (which are all provided in the base system)
doesn't support the glyph you're using to indicate new messages. I
wouldn't consider this a blocker, but I think that needs to get
resolved at some point, either by patching the glyph into all
system-provided fonts, or by using one already there. In my opinion
the system will feel pretty janky if the base font set doesn't
support the base utilities.
That's all I have at the moment. I'm looking forward to seeing Nail
get merged. The threading alone is a great value-add, and the code
seems a lot cleaner too. Thanks for taking this on!
--
Daniel Moch
https://djmo.ch
next prev parent reply other threads:[~2020-12-29 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 3:42 ori
2020-12-29 10:45 ` julien
2020-12-29 15:55 ` ori
2020-12-30 14:03 ` Shawn Nock
2020-12-30 17:20 ` ori
2020-12-31 4:49 ` ori
2020-12-29 10:46 ` Daniel Moch [this message]
2020-12-29 11:17 ` telephil9
2020-12-29 21:09 ` Lyndon Nerenberg
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=87642E8697B6D1A0A459086FAC32B644@ranger.org \
--to=daniel@danielmoch.com \
--cc=9front@9front.org \
--cc=ori@eigenstate.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).