From: Paul Menzel <paulepanter@users.sourceforge.net>
To: ntg-context@ntg.nl
Subject: [t-vim] [PATCH] vim-README.md: Correct some typos
Date: Wed, 02 Nov 2011 20:29:21 +0100 [thread overview]
Message-ID: <1320262161.3560.19.camel@mattotaupa> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1417 bytes --]
Date: Wed, 2 Nov 2011 20:06:35 +0100
Subject: [PATCH] vim-README.md: Correct some typos
---
You can use `git am <pathtosavedmboxfile>` to apply the patch.
diff --git a/vim-README.md b/vim-README.md
index 557cf8f..5853aa2 100644
--- a/vim-README.md
+++ b/vim-README.md
@@ -4,9 +4,9 @@ The vim module
This module highlights code snippets using vim as a syntax
highlighter. Such a task may appear pointless at first glance. After all,
ConTeXt provides excellent syntax highlighting features for TeX, Metapost, XML,
-and a few other langauges. And in MkIV, you can specify the grammer to parse a
+and a few other languages. And in MkIV, you can specify the grammar to parse a
language, and get syntax highlighting for a new language. But writing such
-grammers is difficult. More importantly, why reinvent the wheel? Most
+grammars is difficult. More importantly, why reinvent the wheel? Most
editors, and many other syntax highlighting programs, already syntax highlight
many programming languages. Why not just leverage these external programs to
generate syntax highlighting? This module does exactly that.
@@ -188,7 +188,7 @@ The default color scheme is `pscolor`.
Line numbering
---------------
-To eanble line numbering for a particular snippet, use:
+To enable line numbering for a particular snippet, use:
\start<vimtyping>[numbering=yes]
...
--
1.7.7.1
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2011-11-02 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 19:29 Paul Menzel [this message]
2011-11-02 19:33 ` Paul Menzel
2011-11-02 19:39 ` Aditya Mahajan
2011-11-02 21:50 ` [t-vim] [PATCH] vim.txt: " Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1320262161.3560.19.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).