summaryrefslogtreecommitdiff
path: root/src/print.c
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2015-09-16 16:23:55 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2015-09-16 16:26:07 -0700
commit032ce1c7d1afb23e6b1265d91c5a97e45de071ce (patch)
treedab9ca1e540c23aeb15ee9ef8fdc6b78e1929b6d /src/print.c
parent309d39b832ccd72f99cc726090ff03f7e146948d (diff)
downloademacs-032ce1c7d1afb23e6b1265d91c5a97e45de071ce.tar.gz
Omit unnecessary \ before paren in C docstrings
Although \( is needed in docstrings in Elisp code, it is not needed in docstrings in C code, since C function definitiions do not start with a parenthesis. The backslashes made the docstrings a bit harder to read and to format in columns. Also, some C docstrings had ( in column 1 and this did not appear to be causing any problems. So, simplify C docstrings by replacing \( with ( and \) with ).
Diffstat (limited to 'src/print.c')
-rw-r--r--src/print.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/print.c b/src/print.c
index 94f3fcd7db1..3c3dca77000 100644
--- a/src/print.c
+++ b/src/print.c
@@ -2198,7 +2198,7 @@ Also print formfeeds as `\\f'. */);
DEFVAR_BOOL ("print-escape-nonascii", print_escape_nonascii,
doc: /* Non-nil means print unibyte non-ASCII chars in strings as \\OOO.
-\(OOO is the octal representation of the character code.)
+(OOO is the octal representation of the character code.)
Only single-byte characters are affected, and only in `prin1'.
When the output goes in a multibyte buffer, this feature is
enabled regardless of the value of the variable. */);
@@ -2206,7 +2206,7 @@ enabled regardless of the value of the variable. */);
DEFVAR_BOOL ("print-escape-multibyte", print_escape_multibyte,
doc: /* Non-nil means print multibyte characters in strings as \\xXXXX.
-\(XXXX is the hex representation of the character code.)
+(XXXX is the hex representation of the character code.)
This affects only `prin1'. */);
print_escape_multibyte = 0;