summaryrefslogtreecommitdiff
path: root/man/flymake.texi
diff options
context:
space:
mode:
authorJuanma Barranquero <lekktu@gmail.com>2005-06-20 14:47:12 +0000
committerJuanma Barranquero <lekktu@gmail.com>2005-06-20 14:47:12 +0000
commit3d80e1a24fb6f8c2349139c91ac0e5281aff96f2 (patch)
tree5e53cc2e662a2a92d9d5a9afd1e21fa969c1f50c /man/flymake.texi
parent2345130a330ae7ba5c53655172f68e2d652bcfeb (diff)
downloademacs-3d80e1a24fb6f8c2349139c91ac0e5281aff96f2.tar.gz
Fix spellings.
Diffstat (limited to 'man/flymake.texi')
-rw-r--r--man/flymake.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/man/flymake.texi b/man/flymake.texi
index 9db7551b18c..bf224b28fde 100644
--- a/man/flymake.texi
+++ b/man/flymake.texi
@@ -292,7 +292,7 @@ check tools and error message patterns.
@section Customizable variables
@cindex Customizable variables
-This section summarises variables used for Flymake
+This section summarizes variables used for Flymake
configuration.
@table @code
@@ -378,7 +378,7 @@ first item with @code{filename-regexp} matching buffer filename is
selected. If no match is found, @code{flymake-mode} is switched off.
@item init-function
-@code{init-function} is required to initialise the syntax check,
+@code{init-function} is required to initialize the syntax check,
usually by creating a temporary copy of the buffer contents. The
function must return @code{(list cmd-name arg-list)}. If
@code{init-function} returns null, syntax check is aborted, by
@@ -639,7 +639,7 @@ and project include directories. The former is just the contents of the
and the way it can be obtained can vary greatly for different projects.
Therefore, a customizable variable
@code{flymake-get-project-include-dirs-function} is used to provide the
-way to implement the desired behaviour.
+way to implement the desired behavior.
The default implementation, @code{flymake-get-project-include-dirs-imp},
uses a @code{make} call. This requires a correct base directory, that is, a
@@ -658,7 +658,7 @@ of every syntax check attempt.
Flymake can be configured to use different tools for performing syntax
checks. For example, it can use direct compiler call to syntax check a perl
script or a call to @code{make} for a more complicated case of a
-@code{C/C++} source. The general idea is that simple files, like perl
+@code{C/C++} source. The general idea is that simple files, like perl
scripts and html pages, can be checked by directly invoking a
corresponding tool. Files that are usually more complex and generally
used as part of larger projects, might require non-trivial options to