mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	Harry Wei <harryxiyou@gmail.com>,
	Alex Shi <alex.shi@linux.alibaba.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] coding-style.rst: Add fallthrough as an emacs keyword
Date: Sat, 14 Mar 2020 14:13:59 -0700	[thread overview]
Message-ID: <7a2977ea9baacd1580ff80689f2c8f20d45b069d.camel@perches.com> (raw)

fallthrough was added as a pseudo-keyword by commit 294f69e662d1
("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use")

Add fallthrough as a keyword to the example .emacs content
so emacs can colorize or highlight the uses.

Signed-off-by: Joe Perches <joe@perches.com>
---

I've no idea how to remove the infinite monkeys jibe from the chinese translation

 Documentation/process/coding-style.rst                    | 9 +++++----
 Documentation/translations/it_IT/process/coding-style.rst | 9 +++++----
 Documentation/translations/zh_CN/process/coding-style.rst | 5 ++++-
 3 files changed, 14 insertions(+), 9 deletions(-)

diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index acb2f1b..3260cd 100644
--- a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -577,9 +577,7 @@ item, explaining its use.
 That's OK, we all do.  You've probably been told by your long-time Unix
 user helper that ``GNU emacs`` automatically formats the C sources for
 you, and you've noticed that yes, it does do that, but the defaults it
-uses are less than desirable (in fact, they are worse than random
-typing - an infinite number of monkeys typing into GNU emacs would never
-make a good program).
+uses are less than desirable.
 
 So, you can either get rid of GNU emacs, or change it to use saner
 values.  To do the latter, you can stick the following in your .emacs file:
@@ -631,7 +629,10 @@ values.  To do the latter, you can stick the following in your .emacs file:
 
   (dir-locals-set-directory-class
    (expand-file-name "~/src/linux-trees")
-   'linux-kernel)
+   'linux-kernel
+   (font-lock-add-keywords 'c-mode
+			   '(("\\<\\(fallthrough\\)\\>" . font-lock-keyword-face)))
+  )
 
 This will make emacs go better with the kernel coding style for C
 files below ``~/src/linux-trees``.
diff --git a/Documentation/translations/it_IT/process/coding-style.rst b/Documentation/translations/it_IT/process/coding-style.rst
index 8725f2b..67364f 100644
--- a/Documentation/translations/it_IT/process/coding-style.rst
+++ b/Documentation/translations/it_IT/process/coding-style.rst
@@ -584,9 +584,7 @@ commento per spiegarne l'uso.
 Va bene, li facciamo tutti.  Probabilmente vi è stato detto dal vostro
 aiutante Unix di fiducia che ``GNU emacs`` formatta automaticamente il
 codice C per conto vostro, e avete notato che sì, in effetti lo fa, ma che
-i modi predefiniti non sono proprio allettanti (infatti, sono peggio che
-premere tasti a caso - un numero infinito di scimmie che scrivono in
-GNU emacs non faranno mai un buon programma).
+i modi predefiniti non sono proprio allettanti.
 
 Quindi, potete sbarazzarvi di GNU emacs, o riconfigurarlo con valori più
 sensati.  Per fare quest'ultima cosa, potete appiccicare il codice che
@@ -639,7 +637,10 @@ segue nel vostro file .emacs:
 
   (dir-locals-set-directory-class
    (expand-file-name "~/src/linux-trees")
-   'linux-kernel)
+   'linux-kernel
+   (font-lock-add-keywords 'c-mode
+			   '(("\\<\\(fallthrough\\)\\>" . font-lock-keyword-face)))
+  )
 
 Questo farà funzionare meglio emacs con lo stile del kernel per i file che
 si trovano nella cartella ``~/src/linux-trees``.
diff --git a/Documentation/translations/zh_CN/process/coding-style.rst b/Documentation/translations/zh_CN/process/coding-style.rst
index eae10bc..6c9443 100644
--- a/Documentation/translations/zh_CN/process/coding-style.rst
+++ b/Documentation/translations/zh_CN/process/coding-style.rst
@@ -558,7 +558,10 @@ Documentation/doc-guide/ 和 scripts/kernel-doc 以获得详细信息。
 
   (dir-locals-set-directory-class
    (expand-file-name "~/src/linux-trees")
-   'linux-kernel)
+   'linux-kernel
+   (font-lock-add-keywords 'c-mode
+			   '(("\\<\\(fallthrough\\)\\>" . font-lock-keyword-face)))
+  )
 
 这会让 emacs 在 ``~/src/linux-trees`` 下的 C 源文件获得更好的内核代码风格。
 



             reply	other threads:[~2020-03-15  2:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 21:13 Joe Perches [this message]
2020-03-15  2:12 ` Matthew Wilcox
2020-03-15  4:26   ` Joe Perches
2020-03-20 23:31 ` Jonathan Corbet
2020-03-20 23:45   ` Joe Perches

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=7a2977ea9baacd1580ff80689f2c8f20d45b069d.camel@perches.com \
    --to=joe@perches.com \
    --cc=alex.shi@linux.alibaba.com \
    --cc=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --cc=harryxiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®