From: Kurt H Maier <khm@sciops.net>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Revived! The 10 Edition spell program!
Date: Tue, 24 Sep 2019 13:30:52 -0700 [thread overview]
Message-ID: <20190924203052.GB74746@wopr> (raw)
In-Reply-To: <20190924195835.GB21722@mcvoy.com>
On Tue, Sep 24, 2019 at 12:58:35PM -0700, Larry McVoy wrote:
>
> How is this better than spell(1) on Linux?
Assuming you're talking about GNU spell, it suffers from feature creep
(localization stuff, hard-coded markup filters, etc) which makes the
code less pleasant to work with. I'm not sure why my spellchecker needs
curses support, but GNU spell has it. Also I don't like having to worry
about licensing cruft when I e.g. copy a binary over to a system at
work. If I can do my work with 5% the source code, that's generally my
plan.
khm
next prev parent reply other threads:[~2019-09-24 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 17:10 arnold
2019-09-24 17:15 ` Clem Cole
2019-09-24 17:30 ` arnold
2019-09-24 19:42 ` Kurt H Maier
2019-09-24 19:58 ` Larry McVoy
2019-09-24 20:30 ` Kurt H Maier [this message]
2019-09-25 6:15 ` arnold
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=20190924203052.GB74746@wopr \
--to=khm@sciops.net \
--cc=lm@mcvoy.com \
--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).