f7160f3218
The various schemas included in QEMU use a JSON-based format which is, however, strictly speaking not valid JSON. As a consequence, when vim tries to apply syntax highlight rules for JSON (as guessed from the file name), the result is an unreadable mess which mostly consist of red markers pointing out supposed errors in, well, pretty much everything. Using Python syntax highlighting produces much better results, and in fact these files already start with specially-formatted comments that instruct Emacs to process them as if they were Python files. This commit adds the equivalent special comments for vim. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Message-Id: <20200729185024.121766-1-abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: John Snow <jsnow@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
31 lines
788 B
Python
31 lines
788 B
Python
# -*- Mode: Python -*-
|
|
# vim: filetype=python
|
|
|
|
##
|
|
# = QMP errors
|
|
##
|
|
|
|
##
|
|
# @QapiErrorClass:
|
|
#
|
|
# QEMU error classes
|
|
#
|
|
# @GenericError: this is used for errors that don't require a specific error
|
|
# class. This should be the default case for most errors
|
|
#
|
|
# @CommandNotFound: the requested command has not been found
|
|
#
|
|
# @DeviceNotActive: a device has failed to be become active
|
|
#
|
|
# @DeviceNotFound: the requested device has not been found
|
|
#
|
|
# @KVMMissingCap: the requested operation can't be fulfilled because a
|
|
# required KVM capability is missing
|
|
#
|
|
# Since: 1.2
|
|
##
|
|
{ 'enum': 'QapiErrorClass',
|
|
# Keep this in sync with ErrorClass in error.h
|
|
'data': [ 'GenericError', 'CommandNotFound',
|
|
'DeviceNotActive', 'DeviceNotFound', 'KVMMissingCap' ] }
|