Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

218 lines
7.7 KiB

;;; protobuf-mode.el --- major mode for editing protocol buffers. -*- lexical-binding: t; -*-
;; Author: Alexandre Vassalotti <alexandre@peadrop.com>
;; Created: 23-Apr-2009
;; Version: 0.3
;; Keywords: google protobuf languages
;; Redistribution and use in source and binary forms, with or without
;; modification, are permitted provided that the following conditions are
;; met:
;;
;; * Redistributions of source code must retain the above copyright
;; notice, this list of conditions and the following disclaimer.
;; * Redistributions in binary form must reproduce the above
;; copyright notice, this list of conditions and the following disclaimer
;; in the documentation and/or other materials provided with the
;; distribution.
;; * Neither the name of Google Inc. nor the names of its
;; contributors may be used to endorse or promote products derived from
;; this software without specific prior written permission.
;;
;; THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
;; "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
;; LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
;; A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
;; OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
;; SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
;; LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
;; DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
;; THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
;; (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
;; OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
;;; Commentary:
;; Installation:
;; - Put `protobuf-mode.el' in your Emacs load-path.
;; - Add this line to your .emacs file:
;; (require 'protobuf-mode)
;;
;; You can customize this mode just like any mode derived from CC Mode. If
;; you want to add customizations specific to protobuf-mode, you can use the
;; `protobuf-mode-hook'. For example, the following would make protocol-mode
;; use 2-space indentation:
;;
;; (defconst my-protobuf-style
;; '((c-basic-offset . 2)
;; (indent-tabs-mode . nil)))
;;
;; (add-hook 'protobuf-mode-hook
;; (lambda () (c-add-style "my-style" my-protobuf-style t)))
;;
;; Refer to the documentation of CC Mode for more information about
;; customization details and how to use this mode.
;;
;; TODO:
;; - Make highlighting for enum values work properly.
;; - Fix the parser to recognize extensions as identifiers and not
;; as casts.
;; - Improve the parsing of option assignment lists. For example:
;; optional int32 foo = 1 [(my_field_option) = 4.5];
;; - Add support for fully-qualified identifiers (e.g., with a leading ".").
;;; Code:
(require 'cc-mode)
(eval-when-compile
(and (= emacs-major-version 24)
(>= emacs-minor-version 4)
(require 'cl-lib))
(require 'cc-langs)
(require 'cc-fonts))
;; This mode does not inherit properties from other modes. So, we do not use
;; the usual `c-add-language' function.
(eval-and-compile
(put 'protobuf-mode 'c-mode-prefix "protobuf-"))
;; The following code uses of the `c-lang-defconst' macro define syntactic
;; features of protocol buffer language. Refer to the documentation in the
;; cc-langs.el file for information about the meaning of the -kwds variables.
(c-lang-defconst c-primitive-type-kwds
protobuf '("double" "float" "int32" "int64" "uint32" "uint64" "sint32"
"sint64" "fixed32" "fixed64" "sfixed32" "sfixed64" "bool"
"string" "bytes" "group"))
(c-lang-defconst c-modifier-kwds
protobuf '("required" "optional" "repeated" "oneof"))
(c-lang-defconst c-class-decl-kwds
protobuf '("message" "enum" "service"))
(c-lang-defconst c-constant-kwds
protobuf '("true" "false"))
(c-lang-defconst c-other-decl-kwds
protobuf '("package" "import" "syntax" "edition"))
(c-lang-defconst c-other-kwds
protobuf '("default" "max"))
(c-lang-defconst c-identifier-ops
;; Handle extended identifiers like google.protobuf.MessageOptions
protobuf '((left-assoc ".")))
;; The following keywords do not fit well in keyword classes defined by
;; cc-mode. So, we approximate as best we can.
(c-lang-defconst c-type-list-kwds
protobuf '("extensions" "to" "reserved"))
(c-lang-defconst c-typeless-decl-kwds
protobuf '("extend" "rpc" "stream" "option" "returns"))
;; Here we remove default syntax for loops, if-statements and other C
;; syntactic features that are not supported by the protocol buffer language.
(c-lang-defconst c-brace-list-decl-kwds
;; Remove syntax for C-style enumerations.
protobuf nil)
(c-lang-defconst c-block-stmt-1-kwds
;; Remove syntax for "do" and "else" keywords.
protobuf nil)
(c-lang-defconst c-block-stmt-2-kwds
;; Remove syntax for "for", "if", "switch" and "while" keywords.
protobuf nil)
(c-lang-defconst c-simple-stmt-kwds
;; Remove syntax for "break", "continue", "goto" and "return" keywords.
protobuf nil)
(c-lang-defconst c-paren-stmt-kwds
;; Remove special case for the "(;;)" in for-loops.
protobuf nil)
(c-lang-defconst c-label-kwds
;; Remove case label syntax for the "case" and "default" keywords.
protobuf nil)
(c-lang-defconst c-before-label-kwds
;; Remove special case for the label in a goto statement.
protobuf nil)
(c-lang-defconst c-cpp-matchers
;; Disable all the C preprocessor syntax.
protobuf nil)
(c-lang-defconst c-decl-prefix-re
;; Same as for C, except it does not match "(". This is needed for disabling
;; the syntax for casts.
protobuf "\\([\{\};,]+\\)")
;; Add support for variable levels of syntax highlighting.
(defconst protobuf-font-lock-keywords-1 (c-lang-const c-matchers-1 protobuf)
"Minimal highlighting for protobuf-mode.")
(defconst protobuf-font-lock-keywords-2 (c-lang-const c-matchers-2 protobuf)
"Fast normal highlighting for protobuf-mode.")
(defconst protobuf-font-lock-keywords-3 (c-lang-const c-matchers-3 protobuf)
"Accurate normal highlighting for protobuf-mode.")
(defvar protobuf-font-lock-keywords protobuf-font-lock-keywords-3
"Default expressions to highlight in protobuf-mode.")
;; Our syntax table is auto-generated from the keyword classes we defined
;; previously with the `c-lang-const' macro.
(defvar protobuf-mode-syntax-table nil
"Syntax table used in protobuf-mode buffers.")
(or protobuf-mode-syntax-table
(setq protobuf-mode-syntax-table
(funcall (c-lang-const c-make-mode-syntax-table protobuf))))
(defvar protobuf-mode-abbrev-table nil
"Abbreviation table used in protobuf-mode buffers.")
(defvar protobuf-mode-map nil
"Keymap used in protobuf-mode buffers.")
(or protobuf-mode-map
(setq protobuf-mode-map (c-make-inherited-keymap)))
(easy-menu-define protobuf-menu protobuf-mode-map
"Protocol Buffers Mode Commands"
(cons "Protocol Buffers" (c-lang-const c-mode-menu protobuf)))
;;;###autoload (add-to-list 'auto-mode-alist '("\\.proto\\'" . protobuf-mode))
;;;###autoload
[editors/emacs] Fix protobuf-mode definition (#9572) Fix a few issues with the Emacs mode definition. First, in 1ab7789f3 (2021-10-13, Emacs: Protobuf mode should be derived from prog-mode) we made `protobuf-mode' a derived mode of `prog-mode' using the `define-derived-mode' macro[1]. However, the definition body was not updated accordingly. So in this commit, we: - Remove the superfluous `(interactive)' form; - Remove the unnecessary call of `kill-all-local-variables', which is already handled by `define-derived-mode' and could cause a few issues, for example, it prevents `prog-mode-hook' from being run; - Remove forms that set `major-mode' and `mode-name', which are automatically set to the first and third arguments respectively; - Remove forms that set key map, syntax table, and abbrev table, which are already handled automatically; - Do not run `protobuf-mode-hook' explicitly in the body. It is already arranged to be run after the body. Second, the call to `c-make-emacs-variables-local' is removed. It is called inside `c-init-language-vars' already. Calling it again should do no harm now, but to be future-proof it might be better to just remove it. Finally, we move the `c-update-modeline' form to the :after-hook argument to ensure it is run at the very end, so that the mode line will reflect all user customizations done in various mode hooks. Similarly, we run `c-mode-common-hook' also at the very end to leave a place for user customizations (for example, set `imenu-generic-expression' in `c-mode-common-hook'). [1] https://www.gnu.org/software/emacs/manual/html_node/elisp/Derived-Modes.html Re: https://github.com/protocolbuffers/protobuf/issues/7316 Re: https://github.com/protocolbuffers/protobuf/pull/9076
3 years ago
(define-derived-mode protobuf-mode prog-mode "Protocol-Buffers"
"Major mode for editing Protocol Buffers description language.
The hook `c-mode-common-hook' is run with no argument at mode
initialization, then `protobuf-mode-hook'.
Key bindings:
\\{protobuf-mode-map}"
[editors/emacs] Fix protobuf-mode definition (#9572) Fix a few issues with the Emacs mode definition. First, in 1ab7789f3 (2021-10-13, Emacs: Protobuf mode should be derived from prog-mode) we made `protobuf-mode' a derived mode of `prog-mode' using the `define-derived-mode' macro[1]. However, the definition body was not updated accordingly. So in this commit, we: - Remove the superfluous `(interactive)' form; - Remove the unnecessary call of `kill-all-local-variables', which is already handled by `define-derived-mode' and could cause a few issues, for example, it prevents `prog-mode-hook' from being run; - Remove forms that set `major-mode' and `mode-name', which are automatically set to the first and third arguments respectively; - Remove forms that set key map, syntax table, and abbrev table, which are already handled automatically; - Do not run `protobuf-mode-hook' explicitly in the body. It is already arranged to be run after the body. Second, the call to `c-make-emacs-variables-local' is removed. It is called inside `c-init-language-vars' already. Calling it again should do no harm now, but to be future-proof it might be better to just remove it. Finally, we move the `c-update-modeline' form to the :after-hook argument to ensure it is run at the very end, so that the mode line will reflect all user customizations done in various mode hooks. Similarly, we run `c-mode-common-hook' also at the very end to leave a place for user customizations (for example, set `imenu-generic-expression' in `c-mode-common-hook'). [1] https://www.gnu.org/software/emacs/manual/html_node/elisp/Derived-Modes.html Re: https://github.com/protocolbuffers/protobuf/issues/7316 Re: https://github.com/protocolbuffers/protobuf/pull/9076
3 years ago
:after-hook (c-update-modeline)
(setq abbrev-mode t)
(c-initialize-cc-mode t)
(c-init-language-vars protobuf-mode)
(c-common-init 'protobuf-mode)
(setq imenu-generic-expression
'(("Message" "^[[:space:]]*message[[:space:]]+\\([[:alnum:]]+\\)" 1)
("Enum" "^[[:space:]]*enum[[:space:]]+\\([[:alnum:]]+\\)" 1)
[editors/emacs] Fix protobuf-mode definition (#9572) Fix a few issues with the Emacs mode definition. First, in 1ab7789f3 (2021-10-13, Emacs: Protobuf mode should be derived from prog-mode) we made `protobuf-mode' a derived mode of `prog-mode' using the `define-derived-mode' macro[1]. However, the definition body was not updated accordingly. So in this commit, we: - Remove the superfluous `(interactive)' form; - Remove the unnecessary call of `kill-all-local-variables', which is already handled by `define-derived-mode' and could cause a few issues, for example, it prevents `prog-mode-hook' from being run; - Remove forms that set `major-mode' and `mode-name', which are automatically set to the first and third arguments respectively; - Remove forms that set key map, syntax table, and abbrev table, which are already handled automatically; - Do not run `protobuf-mode-hook' explicitly in the body. It is already arranged to be run after the body. Second, the call to `c-make-emacs-variables-local' is removed. It is called inside `c-init-language-vars' already. Calling it again should do no harm now, but to be future-proof it might be better to just remove it. Finally, we move the `c-update-modeline' form to the :after-hook argument to ensure it is run at the very end, so that the mode line will reflect all user customizations done in various mode hooks. Similarly, we run `c-mode-common-hook' also at the very end to leave a place for user customizations (for example, set `imenu-generic-expression' in `c-mode-common-hook'). [1] https://www.gnu.org/software/emacs/manual/html_node/elisp/Derived-Modes.html Re: https://github.com/protocolbuffers/protobuf/issues/7316 Re: https://github.com/protocolbuffers/protobuf/pull/9076
3 years ago
("Service" "^[[:space:]]*service[[:space:]]+\\([[:alnum:]]+\\)" 1)))
(c-run-mode-hooks 'c-mode-common-hook))
(provide 'protobuf-mode)
;;; protobuf-mode.el ends here