From fcf962edded2d6a7cb638909587167261e4f2bb0 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Thu, 19 Sep 2024 12:53:14 +0200 Subject: 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 . Perviously, you either had to insert a double-caret, typing 4 carets in a row, or you had to use 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. --- doc/sciteco.7.template | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'doc') 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. -- cgit v1.2.3