From: Xue Fuqiao <xfq.free@gmail.com>
To: Thien-Thi Nguyen <ttn@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Changes in revision 114466
Date: Mon, 30 Sep 2013 12:55:47 +0800 [thread overview]
Message-ID: <CAAF+z6H3we=w_BeLc53nWEor8CH9ZO7Aca8NGRaa1a2QinOc9Q@mail.gmail.com> (raw)
In-Reply-To: <87ioxk3x9z.fsf@zigzag.favinet>
On Sun, Sep 29, 2013 at 3:24 PM, Thien-Thi Nguyen <ttn@gnu.org> wrote:
> () Eli Zaretskii <eliz@gnu.org>
> () Sun, 29 Sep 2013 05:36:08 +0300
>
> > >> +@c FIXME: Document these functions:
> > >> +@c `bool-vector-exclusive-or'
> > >> +@c `bool-vector-union'
> > >> +@c `bool-vector-intersection'
> > >> +@c `bool-vector-set-difference'
> > >> +@c `bool-vector-not'
> > >> +@c `bool-vector-subset'
> > >> +@c `bool-vector-count-matches'
> > >> +@c `bool-vector-count-matches-at'
>
> Nothing to be sorry about, and thank you.
>
> If the names of these functions were produced by some scanning program,
> this is a good opportunity to add that code to the repo (under admin/).
>
> If they were produced by hand, then i guess the zeroth step would be to
> write a program that likewise produces them.
>
> The overall meta-goals are to make doc coverage easy to determine for
> everyone, and to render the selection criteria (for surely, some things
> do not warrant "full" documentation) explicit and consequently subject
> to refinement.
>
> With this in place, the overall goal of improving the doc coverage is
> most easily realizable, not just once, but also as an ongoing basis, as
> Emacs gains new features over time.
Agreed. The name of these functions were produced by hand. To make doc
coverage, the only solution that I see is scanning the Emacs repo for
keywords like these:
(def\\(var\\|const\\|custom\\)
(def\\(un\\|subst\\|macro\\|advice\\)
(def\\(type\\|struct\\|class\\|ine-condition\\)
DEFUN ("
maybe also for defgroup, defmath, defalias, cl-{defun, defmacro,
defsubst}, ...
although `defadvice' should not be used for Lisp code in Emacs proper.
But I see one problem: not every {functions, variables, ...} needs
documenting. E.g., some functions/variables use two hyphens to separate
prefix. These functions/variables usually don't needs documenting.
IMO every user option and every command needs documentation.
--
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/
next prev parent reply other threads:[~2013-09-30 4:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.53349.1380335551.10747.emacs-diffs@gnu.org>
2013-09-28 7:46 ` Changes in revision 114466 Eli Zaretskii
2013-09-28 22:30 ` Xue Fuqiao
2013-09-29 2:36 ` Eli Zaretskii
2013-09-29 7:24 ` Thien-Thi Nguyen
2013-09-30 4:55 ` Xue Fuqiao [this message]
2013-09-30 5:21 ` Drew Adams
2013-09-30 10:29 ` Stephen Berman
2013-09-30 15:05 ` Drew Adams
2013-09-30 15:52 ` Thien-Thi Nguyen
2013-10-01 2:11 ` Stephen J. Turnbull
2013-09-30 15:42 ` Eli Zaretskii
2013-09-30 11:47 ` Andreas Röhler
2013-09-30 15:38 ` Eli Zaretskii
[not found] ` <<83k3hye2uq.fsf@gnu.org>
2013-09-30 16:38 ` Drew Adams
2013-10-01 3:40 ` Xue Fuqiao
2013-10-01 4:57 ` Stephen J. Turnbull
2013-10-01 5:15 ` Drew Adams
2013-10-01 5:27 ` Drew Adams
2013-10-01 6:11 ` Stephen J. Turnbull
2013-10-01 7:44 ` Drew Adams
2013-10-01 8:29 ` Stephen J. Turnbull
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAF+z6H3we=w_BeLc53nWEor8CH9ZO7Aca8NGRaa1a2QinOc9Q@mail.gmail.com' \
--to=xfq.free@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ttn@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).