From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH] gdbserver: Add .dir-locals.el file
Date: Mon, 02 Mar 2020 09:53:00 -0000 [thread overview]
Message-ID: <20200302095303.4474-1-andrew.burgess@embecosm.com> (raw)
Add a .dir-locals.el file into the gdbserver directory so that we get
the GNU style when editing these files in Emacs.
I copied this file over from the gdb/ directory and the only change I
made was to remove (mode . c++) from the c-mode settings. The reason
for this is that all C++ files in the gdbserver/ directory now have
the .cc suffix, and we don't (currently) have any .c files in there. I
assume that if did add a .c file in the future, it really would be C,
not C++, so forcing c++-mode seems like the wrong thing to do.
The copyright date in the new file is left as for gdb/.dir-locals.el,
as the new file is an exact copy with one line removed.
gdbserver/ChangeLog:
* .dir-locals.el: New file.
---
gdbserver/.dir-locals.el | 36 ++++++++++++++++++++++++++++++++++++
gdbserver/ChangeLog | 4 ++++
2 files changed, 40 insertions(+)
create mode 100644 gdbserver/.dir-locals.el
diff --git a/gdbserver/.dir-locals.el b/gdbserver/.dir-locals.el
new file mode 100644
index 00000000000..28a6df0de07
--- /dev/null
+++ b/gdbserver/.dir-locals.el
@@ -0,0 +1,36 @@
+;; Emacs settings.
+;; Copyright (C) 2012-2020 Free Software Foundation, Inc.
+
+;; This program is free software; you can redistribute it and/or modify
+;; it under the terms of the GNU General Public License as published by
+;; the Free Software Foundation; either version 3 of the License, or
+;; (at your option) any later version.
+
+;; This program is distributed in the hope that it will be useful,
+;; but WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+;; GNU General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+(
+ (tcl-mode . ((tcl-indent-level . 4)
+ (tcl-continued-indent-level . 4)
+ (indent-tabs-mode . t)))
+ (nil . ((bug-reference-url-format . "http://sourceware.org/bugzilla/show_bug.cgi?id=%s")))
+ (c-mode . ((c-file-style . "GNU")
+ (indent-tabs-mode . t)
+ (tab-width . 8)
+ (c-basic-offset . 2)
+ (eval . (c-set-offset 'innamespace 0))
+ ))
+ (c++-mode . ((eval . (when (fboundp 'c-toggle-comment-style)
+ (c-toggle-comment-style 1)))
+ (indent-tabs-mode . t)
+ (tab-width . 8)
+ (c-file-style . "GNU")
+ (c-basic-offset . 2)
+ (eval . (c-set-offset 'innamespace 0))
+ ))
+)
next reply other threads:[~2020-03-02 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 9:53 Andrew Burgess [this message]
2020-03-02 10:17 ` Aktemur, Tankut Baris
2020-03-02 12:31 ` [PATCHv2] " Andrew Burgess
2020-03-02 14:06 ` Pedro Alves
2020-03-02 17:08 ` Andrew Burgess
2020-03-02 17:34 ` Pedro Alves
2020-03-02 17:58 ` Eli Zaretskii
2020-03-02 18:13 ` Pedro Alves
2020-03-02 19:19 ` Eli Zaretskii
2020-03-05 15:12 ` Andrew Burgess
2020-03-05 15:26 ` Eli Zaretskii
2020-03-05 16:00 ` Pedro Alves
2020-03-02 10:19 ` [PATCH] " Aktemur, Tankut Baris
2020-03-02 12:02 ` Andrew Burgess
2020-03-02 14:05 ` Pedro Alves
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=20200302095303.4474-1-andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.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.
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).