summaryrefslogtreecommitdiff
path: root/usr.bin/learn/lib/eqn/L12.1d
diff options
context:
space:
mode:
authorIan Darwin <ian@cvs.openbsd.org>1998-09-28 16:01:53 +0000
committerIan Darwin <ian@cvs.openbsd.org>1998-09-28 16:01:53 +0000
commit5c33bfa47b213f93498fe8c5dc17f90f4d116c06 (patch)
tree0dcf528168e800bebf68c46bb8296b34b3342caa /usr.bin/learn/lib/eqn/L12.1d
parent8d70bdbdf6fd88bf88b9a384cfaafb6668c804ec (diff)
import BTL learn(1) lessons/eqn
Diffstat (limited to 'usr.bin/learn/lib/eqn/L12.1d')
-rw-r--r--usr.bin/learn/lib/eqn/L12.1d21
1 files changed, 21 insertions, 0 deletions
diff --git a/usr.bin/learn/lib/eqn/L12.1d b/usr.bin/learn/lib/eqn/L12.1d
new file mode 100644
index 00000000000..32f1d480e8c
--- /dev/null
+++ b/usr.bin/learn/lib/eqn/L12.1d
@@ -0,0 +1,21 @@
+#print
+.LP
+The "right" part of a left-right construction can be
+omitted if it is not used; just leave that part out.
+The main thing to watch out for is that now you will
+need braces to enclose the entire construction, "left" and all -
+otherwise neqn will not know where to stop in
+figuring out how high the thing is.
+
+For example, will
+ left "{" a + b over c over d
+produce the same output as
+ { left "{" a } + b over c over d
+Answer yes or no after experimenting.
+#copyin
+#user
+#uncopyin
+#match no
+#log
+#next
+12.1e 10