Dnia 26-12-2008 Matt Wozniski <[email protected]> pisze:
> 
> diff --git a/doc/usr_44.txt b/doc/usr_44.txt
> index f5506b4..7aa324a 100644
> --- a/doc/usr_44.txt
> +++ b/doc/usr_44.txt
> @@ -503,9 +503,10 @@ For example, add keywords that are not used in C: >
> 
>  This works just like in any other syntax file.
> 
> -Now consider the Perl language.  It consists of two distinct parts: a
> -documentation section in POD format, and a program written in Perl itself.
> -The POD section starts with "=head" and ends with "=cut".
> +Now consider the Pere language.  There are two distinct types of files that
> +need Perl syntax highlighting: a documentation section in POD format, and
> +a program written in Perl itself.  The POD section starts with "=head" and
> +ends with "=cut".
>     You want to define the POD syntax in one file, and use it from the Perl
>  syntax file.  The ":syntax include" command reads in a syntax file and stores
>  the elements it defined in a syntax cluster.  For Perl, the statements are as

Typo: Perl, not Pere:


diff --git a/doc/usr_44.txt b/doc/usr_44.txt
index f5506b4..7aa324a 100644
--- a/doc/usr_44.txt
+++ b/doc/usr_44.txt
@@ -503,9 +503,10 @@ For example, add keywords that are not used in C: >

 This works just like in any other syntax file.

-Now consider the Perl language.  It consists of two distinct parts: a
-documentation section in POD format, and a program written in Perl itself.
-The POD section starts with "=head" and ends with "=cut".
+Now consider the Perl language.  There are two distinct types of files that
+need Perl syntax highlighting: a documentation section in POD format, and
+a program written in Perl itself.  The POD section starts with "=head" and
+ends with "=cut".
    You want to define the POD syntax in one file, and use it from the Perl
 syntax file.  The ":syntax include" command reads in a syntax file and stores
 the elements it defined in a syntax cluster.  For Perl, the statements are as

-- 
Cheers,
Lech

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui