From: Oleh Krehel <ohwoeowho@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: master 1be349c 1/2: * lisp/emacs-lisp/package.el: Define custom faces
Date: Mon, 07 Sep 2015 11:48:03 +0200 [thread overview]
Message-ID: <87zj0y4l2k.fsf@gmail.com> (raw)
In-Reply-To: <87vbboo6mb.fsf@gnu.org> ("Johan \=\?utf-8\?Q\?Bockg\=C3\=A5rd\=22's\?\= message of "Sun, 06 Sep 2015 00:15:24 +0200")
Johan Bockgård <bojohan@gnu.org> writes:
> Artur Malabarba <bruce.connor.am@gmail.com> writes:
>
>>> The convention is to not end face names with "-face".
>>
>> Cool. I prefer to not end the names with `-face', but I was just
>> following the lead of the font-lock faces.
>
> The font-lock face are different for historical reasons.
>
>> For reference, is this convention stated anywhere? I couldn't find it
>> in (info "(elisp) Defining Faces").
>
> It says right there:
>
> -- Macro: defface face spec doc [keyword value]…
> This macro declares FACE as a named face whose default face spec is
> given by SPEC. You should not quote the symbol FACE, and it should
> not end in ‘-face’ (that would be redundant).
Is it actually a good idea not end with "-face"? I do it for all my
packages. And the reason is a very good one: I get completion
(completion-at-point, apropos, git-grep, CEDET tags, whatever) for faces
with "package-prefix.*-face". It's useful to distinguish the face
symbols from the variable symbols.
Oleh
next prev parent reply other threads:[~2015-09-07 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150806102825.25477.3457@vcs.savannah.gnu.org>
[not found] ` <E1ZNIPS-0006dx-Nh@vcs.savannah.gnu.org>
2015-09-05 21:44 ` master 1be349c 1/2: * lisp/emacs-lisp/package.el: Define custom faces Johan Bockgård
2015-09-05 22:09 ` Artur Malabarba
2015-09-05 22:15 ` Johan Bockgård
2015-09-06 13:05 ` Artur Malabarba
2015-09-07 9:48 ` Oleh Krehel [this message]
2015-09-10 11:31 ` Alexis
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=87zj0y4l2k.fsf@gmail.com \
--to=ohwoeowho@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.