; Fix typos
This commit is contained in:
parent
58a483960d
commit
f5c3585e4d
3 changed files with 5 additions and 6 deletions
|
@ -847,7 +847,7 @@ Binding,,, elisp, The Emacs Lisp Reference Manual}) to be active.
|
|||
@findex flymake-proc-legacy-flymake
|
||||
The backend @code{flymake-proc-legacy-flymake} was originally designed
|
||||
to be extended for supporting new syntax check tools and error message
|
||||
patterns. It is also controlled by its own set of customization variables
|
||||
patterns. It is also controlled by its own set of customization variables.
|
||||
|
||||
@node Proc customization variables
|
||||
@section Customization variables for the Proc backend
|
||||
|
|
|
@ -54,9 +54,8 @@
|
|||
;; (question mark) if no backends were even configured.
|
||||
;;
|
||||
;; For programmers interested in writing a new Flymake backend, the
|
||||
;; docstring of `flymake-diagnostic-functions', the Flymake manual,
|
||||
;; and the code of existing backends are probably a good starting
|
||||
;; point.
|
||||
;; docstring of `flymake-diagnostic-functions', the Flymake manual, and the
|
||||
;; code of existing backends are probably good starting points.
|
||||
;;
|
||||
;; The user wishing to customize the appearance of error types should
|
||||
;; set properties on the symbols associated with each diagnostic type.
|
||||
|
|
|
@ -282,7 +282,7 @@ Accepts keyword arguments:
|
|||
key in the repeat map, but will not set the
|
||||
`repeat-map' property of the bound command.
|
||||
:continue BINDINGS - Within the scope of `:repeat-map' forces the
|
||||
same behaviour as if no special keyword had
|
||||
same behavior as if no special keyword had
|
||||
been used (that is, the command is bound, and
|
||||
it's `repeat-map' property set)
|
||||
:filter FORM - optional form to determine when bindings apply
|
||||
|
@ -429,7 +429,7 @@ Accepts keyword arguments:
|
|||
key in the repeat map, but will not set the
|
||||
`repeat-map' property of the bound command.
|
||||
:continue BINDINGS - Within the scope of `:repeat-map' forces the
|
||||
same behaviour as if no special keyword had
|
||||
same behavior as if no special keyword had
|
||||
been used (that is, the command is bound, and
|
||||
it's `repeat-map' property set)
|
||||
:filter FORM - optional form to determine when bindings apply
|
||||
|
|
Loading…
Add table
Reference in a new issue