aboutsummaryrefslogtreecommitdiffhomepage
path: root/doc
diff options
context:
space:
mode:
authorRobin Haberkorn <robin.haberkorn@googlemail.com>2024-09-19 12:53:14 +0200
committerRobin Haberkorn <robin.haberkorn@googlemail.com>2024-09-19 12:53:14 +0200
commitfcf962edded2d6a7cb638909587167261e4f2bb0 (patch)
tree9e29f3b39d5dcacae0b57be770a2d44fa862ecc9 /doc
parent5b3906f9255f43018c2bd9683cedddf3df37fa61 (diff)
downloadsciteco-fcf962edded2d6a7cb638909587167261e4f2bb0.tar.gz
Ctrl+^ is no longer translated to a single caret in string building (refs #20)
* Ctrl+^ (30) and Caret+caret (^^) were both translated to a single caret. While there might be some reason to keep this behavior for double-caret, it is certainly pointless for Ctrl+^. * That gives you an easy way to insert Ctrl+^ (code 30) into documents with <I>. Perviously, you either had to insert a double-caret, typing 4 carets in a row, or you had to use <EI> or 30I$. * The special handling of double-caret could perhaps be abolished altogether, as we also have ^Q^ to escape plain carets. The double-caret syntax is very archaic from the time that there was no proper ^Q as far as I recall correctly.
Diffstat (limited to 'doc')
-rw-r--r--doc/sciteco.7.template4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template
index 8486203..52fa742 100644
--- a/doc/sciteco.7.template
+++ b/doc/sciteco.7.template
@@ -1653,7 +1653,9 @@ stages:
.IP 1. 4
Carets followed by characters are translated to control codes,
so \(lq^a\(rq and \(lq^A\(rq are equivalent to CTRL+A (code 1).
-A double caret \(lq^^\(rq is translated to a single caret.
+\# FIXME: Should we change the double-caret behavior?
+A double caret \(lq^^\(rq is translated to a single caret,
+but Ctrl+caret (code 30) is not translated at all.
This caret-handling is independent of the caret-handling in
command names.
.IP 2.