summaryrefslogtreecommitdiff
path: root/usr.bin/learn/lib/eqn/L12.1b
diff options
context:
space:
mode:
Diffstat (limited to 'usr.bin/learn/lib/eqn/L12.1b')
-rw-r--r--usr.bin/learn/lib/eqn/L12.1b29
1 files changed, 29 insertions, 0 deletions
diff --git a/usr.bin/learn/lib/eqn/L12.1b b/usr.bin/learn/lib/eqn/L12.1b
new file mode 100644
index 00000000000..6886309a61b
--- /dev/null
+++ b/usr.bin/learn/lib/eqn/L12.1b
@@ -0,0 +1,29 @@
+#print
+Bars are not the only characters you can put
+around an equation.
+If you say
+ left ( thing right )
+you will get large parentheses around "thing".
+You can also use [ and ] for large square brackets
+and { and } for large braces.
+
+The main problem is that on your terminal there is
+no good way for neqn to draw large braces
+or brackets or parens. So neqn replaces all of these
+with bars.
+Use the right character anyway, though - things do
+work properly on the typesetter. And who knows, some day
+neqn may get improved as well.
+
+With the current version of neqn, does the input
+ left { a over b right }
+produce the same output as
+ left [ a over b right ]
+Answer yes or no.
+#copyin
+#user
+#uncopyin
+#match yes
+#log
+#next
+12.1c 10