gryf/pentadactyl-pm
1
0
Fork 0
mirror of https://github.com/gryf/pentadactyl-pm.git synced 2026-01-07 13:54:11 +01:00
Code Issues Projects Releases Wiki Activity

Normalise the use of "Ex command" in the help files.

Browse Source 
--HG--
extra : rebase_source : cff38cc5048c648485bca80031910c1712280b35
This commit is contained in:
Doug Kearns
2010-09-30 15:30:23 +10:00
parent 251e6ccef1
commit d7bf145acf
4 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
common/locale/en-US/eval.xml
View File

@@ -13,7 +13,7 @@
<p>
Much of the power of &dactyl.appName; lies in its scriptable expression
evaluation. &dactyl.appName; understands two kinds of expressions: ex
evaluation. &dactyl.appName; understands two kinds of expressions: Ex
commands, and JavaScript. Ex commands are simple, easy to type, and
readily accessible from the <t>command-line</t>. They form a core part of
the user interface. JavaScript, on the other hand, is much less
@@ -74,7 +74,7 @@
<spec>:exe<oa>cute</oa> <a>expr</a></spec>
<description>
<p>
Execute the ex command string that results from the evaluation of
Execute the Ex command string that results from the evaluation of
the JavaScript expression <a>expr</a>. For example,
</p>
<code><ex>:execute "open " + content.location.host</ex></code>