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

Rename appname/idname to appName/idName in help files to maintain parity with code.

Browse Source
This commit is contained in:
Kris Maglione
2010-09-24 07:49:17 -04:00
parent 4fe44a403a
commit 2169301157
33 changed files with 172 additions and 172 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -5,20 +5,20 @@
<document
name="eval"
title="&dactyl.appname; Expression Evaluation"
title="&dactyl.appName; Expression Evaluation"
xmlns="&xmlns.dactyl;"
xmlns:html="&xmlns.html;">
<h1 tag="expression expr eval javascript">Expression evaluation</h1>
<toc start="2"/>
<p>
Much of the power of &dactyl.appname; lies in its scriptable expression
evaluation. &dactyl.appname; understands two kinds of expressions: ex
Much of the power of &dactyl.appName; lies in its scriptable expression
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
straightforward, but allows for any number of complex actions to be
executed, with full access to all of the internals of &dactyl.appname; and
executed, with full access to all of the internals of &dactyl.appName; and
&dactyl.host;. Both expression evaluation methods support sophisticated
expression completion, including option lists and descriptions thereof,
along with paren matching and syntax error highlighting.