From 16993f82867e04826929c4440440eba8588168d8 Mon Sep 17 00:00:00 2001
From: ayin <ayin>
Date: Wed, 17 Oct 2007 13:53:42 +0000
Subject: [PATCH] Update resource syntax doc to reflect the removal of rxvt own
 parsing.

---
 doc/rxvt.1.pod | 13 ++-----------
 1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/doc/rxvt.1.pod b/doc/rxvt.1.pod
index 7d513afa..c3a0f189 100644
--- a/doc/rxvt.1.pod
+++ b/doc/rxvt.1.pod
@@ -1085,17 +1085,8 @@ omitting the prefix B<XK_>. Alternatively you can specify I<key> by its hex
 keysym value (B<0x0000 - 0xFFFF>). Note that the lookup of I<sym>s is not
 performed in an exact manner; however, the closest match is assured.
 
-I<string> may contain escape values (C<\a>: bell, C<\b>: backspace,
-C<\e>, C<\E>: escape, C<\n>: newline, C<\r>: carriage return, C<\t>: tab,
-C<\000>: octal number) or verbatim control characters (C<^?>: delete,
-C<^@>: null, C<^A> ...) and may be enclosed with double quotes so that it
-can start or end with whitespace. B<This feature is deprecated and will
-be removed>.
-
-Please note that you need to double the C<\> in resource files, as
-Xlib itself does its own de-escaping (you can use C<\033> instead of
-C<\e> (and so on), which will work with both Xt and @@RXVT_NAME@@'s own
-processing).
+I<string> may contain escape values (C<\n>: newline, C<\000>: octal
+number), see RESOURCES in C<man 7 X> for futher details.
 
 You can define a range of keysyms in one shot by providing a I<string>
 with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where the delimiter `/'
-- 
2.34.1