From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: checkdoc: spam.el
Date: Sat, 03 Jan 2004 22:21:17 -0500 [thread overview]
Message-ID: <4npte0o0uq.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <v9znd6hx28.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 02 Jan 2004 22:15:11 +0100")
On Fri, 02 Jan 2004, 4.uce.03.r.s@nurfuerspam.de wrote:
> I have run `M-x checkdoc RET' on `spam.el' and fixed some issues
> checkdoc complained about. Additionally, I removed trailing
> whitespace. Unless there are objections, I'm going to commit the
> changes. The attached patch was produced with `-w' (Ignore all
> white space) for better legibility.
>
> Beyond my changes, there are still lot of doc-strings with "First
> line is not a complete sentence" and undocumented functions. Maybe
> someone could look into this (after my commit).
I wish I had known about checkdoc before. Thanks for looking at
spam.el. I can clean it up more after the release.
Ted
prev parent reply other threads:[~2004-01-04 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 21:15 Reiner Steib
2004-01-04 3:21 ` Ted Zlatanov [this message]
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=4npte0o0uq.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).