From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: RFC: add .dir-locals.el
Date: Fri, 13 Apr 2012 13:51:00 -0000 [thread overview]
Message-ID: <4F882F09.5040008@codesourcery.com> (raw)
In-Reply-To: <83pqbb3j8c.fsf@gnu.org>
On 04/13/2012 08:32 PM, Eli Zaretskii wrote:
> Can you show the actual warnings that state the names of the variables
> and the values they are being set to? (Sorry, I cannot easily check
> this myself where I'm typing this.)
"The local variables list in /home/yao/SourceCode/gnu/gdb/gdb
contains variables that are risk (**).
Do you want to apply it? You can type
y -- to apply the local variables list.
n -- to ignore the local variables list.
(bug-reference-url-format .
"http://sourceware.org/bugzilla/show_bug.cgi?id=%s")
(c-file-style . "GNU")
(indent-tabs-mode . t)
** (eval : (progn (font-lock-add-keywords nil
'(("\\<\\(\\(xasprintf\\|abort\\|vasprintf\\|strerror\\|strdup\\|asprintf\\|sprintf\\)[
]*\(\\)" 1 font-lock-warning-face t))) (font-lock-add-keywords nil
'(("\\<include[
]*\\(<\\(stat\\|dirent\\|wait\\|sys/wait\\|assert\\)\\.h>\\)" 1
font-lock-warning-face t)))))"
--
Yao (é½å°§)
next prev parent reply other threads:[~2012-04-13 13:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 18:52 Tom Tromey
2012-03-26 19:06 ` Joel Brobecker
2012-03-26 19:33 ` Tom Tromey
2012-03-28 17:35 ` Tom Tromey
2012-04-11 23:59 ` Yao Qi
2012-04-12 0:44 ` Joel Brobecker
2012-04-12 16:01 ` Tom Tromey
2012-04-12 16:25 ` Tom Tromey
2012-04-12 19:21 ` Eli Zaretskii
2012-04-12 20:15 ` Tom Tromey
2012-04-13 9:08 ` Eli Zaretskii
2012-04-13 14:05 ` Tom Tromey
2012-04-13 15:22 ` Eli Zaretskii
2012-04-13 15:37 ` Eli Zaretskii
2012-04-13 9:45 ` Yao Qi
2012-04-13 12:48 ` Eli Zaretskii
2012-04-13 13:51 ` Yao Qi [this message]
2012-04-13 14:45 ` Pedro Alves
2012-04-13 14:58 ` Tom Tromey
2012-04-13 15:20 ` Eli Zaretskii
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=4F882F09.5040008@codesourcery.com \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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