From: Xue Fuqiao <xfq.free@gmail.com>
Date: Mon, 14 Oct 2013 22:20:52 +0000 (+0800)
Subject: Comment
X-Git-Tag: emacs-24.3.90~173^2^2~42^2~45^2~387^2~1268
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=c463be09eb74597309dc4014ac7f96d0b05ce01c;p=emacs.git

Comment
---

diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index 99cbb4d3458..ae24439c41f 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -611,6 +611,9 @@ program signals a Lisp error and then handles it with
 @code{condition-case}, the user won't see the error message; it could
 show the message to the user by reporting it as a warning.)
 
+@c FIXME: Why use ‘(bytecomp)’ instead of ‘'bytecomp’ or simply
+@c ‘bytecomp’ here?  The parens are part of ‘warning-type-format’ but
+@c not part of the warning type. --xfq
 @cindex warning type
   Each warning has a @dfn{warning type} to classify it.  The type is a
 list of symbols.  The first symbol should be the custom group that you