From: Pieter Praet <pieter@praet.org>
To: Carl Worth <cworth@cworth.org>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] fix sum moar typos
In-Reply-To: <8762nwdtfw.fsf@yoom.home.cworth.org>
References: <1307202852-4398-1-git-send-email-pieter@praet.org>
	<1308600861-22684-1-git-send-email-pieter@praet.org>
	<8762nwdtfw.fsf@yoom.home.cworth.org>
User-Agent: Notmuch/0.5-243-g5a76944 (http://notmuchmail.org) Emacs/23.1.50.1
	(x86_64-pc-linux-gnu)
Date: Fri, 24 Jun 2011 22:04:13 +0200
Message-ID: <87liwrgfnm.fsf@praet.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list

On Thu, 23 Jun 2011 16:22:27 -0700, Carl Worth <cworth@cworth.org> wrote:
Non-text part: multipart/signed
> On Mon, 20 Jun 2011 22:14:21 +0200, Pieter Praet <pieter@praet.org> wrote:
> > Various typo fixes in docs, docstrings, comments, etc...
> >=20
> > Signed-off-by: Pieter Praet <pieter@praet.org>
>=20
> Thanks for these fixes, Pieter!

My pleasure.

> I've pushed these all out now. I split the original commit up into 6
> commits that each touch different kinds of text, (non-code text files,
> comments within source files, error messages within source files, etc.)
>=20
> The idea there is that these different kinds of text have different
> potential impacts on the correctness of the code. So some release
> manager might be willing to include one kind of change, but not another,
> for example.

Agreed.

> Also, it made things a bit easier to read. There were two incorrect typo
> fixes in the original commit which I fixed:
>=20
> > -    "\tSeveral notmuch commands accept a comman syntax for search\n"
> > +    "\tSeveral notmuch commands accept a command syntax for search\n"
>=20
> This is now "common syntax".
>=20
> > -    # Remember stdout and stderr file descriptios and redirect test
> > +    # Remember stdout and stderr file descriptions and redirect test
>=20
> This is now "file descriptors".
>=20
> And one change where I left the original text unchanged:
>=20
> >   * A non-NULL return value is guaranteed to be a valid string pointer
> >   * pointing to the characters "new/" or "cur/", (but not
> > - * NUL-terminated).
> > + * NULL-terminated).
>=20
> This comment uses "NULL" to describe a NULL pointer and "NUL" to
> describe the ASCII character '\0'. (I know that "NUL" is a really
> annoying historically misspelled abbreviation, but it is in standard
> usage I believe---see ASCII(7) for example.)

Prime examples of "or even made some new ones" [1] :D

> Meanwhile, I was almost tempted to leave this misspelling unchanged:
>=20
> > -	 (error "%s is a file. Can't creat maildir." path))
> > +	 (error "%s is a file. Can't create maildir." path))
>=20
> Since that's also a classic historically misspelled abbreviation. ;-)
>=20
> Oh, and let me just thank you for being so thorough! There were several
> fixes you made that could obviously not be caught by an automated spell
> checker:
>=20
> > ---part=3Did", (David Edmonson wants to rewrite some of "notmuch show" =
to
> > +--part=3Did", (David Edmondson wants to rewrite some of "notmuch show"=
 to
> ...
> >  (defun notmuch-user-other-email ()
> > -  "Return the user.primary_email value (as a list) from the notmuch co=
nfiguration."
> > +  "Return the user.other_email value (as a list) from the notmuch conf=
iguration."
> ...
> >  (defcustom notmuch-after-tag-hook nil
> > -  "Hooks that are run before tags of a message are modified.
> > +  "Hooks that are run after tags of a message are modified.
> ...
> > -The debian packaging exists in the top-level "debian" directory within
> > +The Debian packaging exists in the top-level "debian" directory within
>=20
> Those all demonstrate a particular eye for detail=E2=80=94well done! For a
> couple of those, I almost gave them their own commits.
>=20
> In passing, let me point out the most amusing typo I saw in the patch:
>=20
> > -} /* Appleasing Emacs */
> > +} /* Appeasing Emacs */
>=20
> I almost hate to see that go, because I like the pleasing portmanteau
> sound of "appleasing". Please applease me and leave this pleasing typo?
>=20
> Admittedly, that's not in code that's originally mine, so I can't say it
> wasn't intentional either.
>=20
> Finally, *many* of the typos and misspellings were originally mine. It's
> certainly embarrassing to see so many (and so many repeats). It was also
> embarrassing to see how many misspellings I committed while typing the
> commit messages, (fortunately I rebased many away).

Let's turn that around:

Comments and commit messages are (understandably) a mere afterthought
for most coders, including myself, and are thus often very terse or
even nonexistent, which automatically translates to less typos (y=3Dkx).

You however, seem to be incredibly disciplined in this respect,
so statistically speaking, you're destined to become typo-king,
and you have every reason to be *proud* of it. :D

The only thing you could possibly have to be embarrassed about,
is insufficient laziness (which, for programmers, is considered a
virtue) ;)

> And now I'm starting to get paranoid about this message. Am I really
> brave enough to type words like "embarrassing", "misspelling", and
> "committed" here?
>=20
> Thanks again,
>=20
> -Carl
Non-text part: application/pgp-signature


Peace

--=20
Pieter


[1] id:"1307202852-4398-1-git-send-email-pieter@praet.org"