From: Oleh Krehel <ohwoeowho@gmail.com>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Adding a few more finder keywords
Date: Mon, 08 Jun 2015 16:56:20 +0200 [thread overview]
Message-ID: <87sia2l04r.fsf@gmail.com> (raw)
In-Reply-To: <CAAdUY-+HA-29KV0JQQvc8wRhA76qPhqxseo+aeS6YNArOuCwtA@mail.gmail.com> (Artur Malabarba's message of "Sat, 25 Apr 2015 17:59:33 +0100")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
> Note how the list contains:
> - 17 "theme" and 18 "themes".
> - 8 "package" and 4 "packages" (and many other instances of singular vs plural)
> - "mode-line", "modeline", "mode line", and even "stausline".
> - 4 "major" and 4 "major-mode"
>
> I think this situation can be improved if we extend the list of
> default keywords. So a new developer, writing his first package,
> doesn't have to decide between "theme" or "themes" (one of them will
> already be offerd to them in the defaults).
I've just added `checkdoc-package-keywords' that checks if the current
file's keywords are in `finder-known-keywords'. It's possible to make
`checkdoc-current-buffer' call `checkdoc-package-keywords'
automatically. I didn't make this the default, since
`finder-known-keywords' still doesn't contain such common keywords as
"org", "completion", "git" etc.
What remains to do now, is to extend `finder-known-keywords', and
possibly make `checkdoc-package-keywords-flag' default to t.
Oleh
next prev parent reply other threads:[~2015-06-08 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 16:59 Adding a few more finder keywords Artur Malabarba
2015-04-25 18:51 ` Drew Adams
2015-04-25 19:23 ` Artur Malabarba
2015-06-08 14:56 ` Oleh Krehel [this message]
2015-06-08 15:37 ` Drew Adams
2015-06-08 15:43 ` Oleh Krehel
2015-06-08 16:20 ` Drew Adams
2015-06-08 16:15 ` Artur Malabarba
2015-06-08 16:19 ` Artur Malabarba
2015-06-08 16:27 ` Drew Adams
2015-06-08 20:59 ` Stefan Monnier
2015-06-09 4:39 ` Stephen J. Turnbull
2015-06-09 6:52 ` Oleh Krehel
2015-06-09 8:02 ` Artur Malabarba
2015-06-09 8:54 ` Oleh Krehel
2015-06-09 14:22 ` Drew Adams
2015-06-09 14:47 ` Oleh Krehel
2015-06-09 16:05 ` Drew Adams
2015-06-09 16:47 ` Oleh Krehel
2015-06-09 17:19 ` Drew Adams
2015-06-09 16:08 ` 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=87sia2l04r.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@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).