(read1): Fix next_char matching.

1 files changed, 5 insertions, 5 deletions

diff --git a/src/lread.c b/src/lread.c
index db83623e054..e87dba53128 100644
--- a/src/lread.c
+++ b/src/lread.c
@@ -2374,7 +2374,7 @@ read1 (readcharfun, pch, first_in_list)
               c = 0;
             else if (c == (CHAR_CTL | '?'))
               c = 127;
-            
+
             if (c & CHAR_SHIFT)
               {
                 /* Shift modifier is valid only with [A-Za-z].  */
@@ -2459,9 +2459,9 @@ read1 (readcharfun, pch, first_in_list)
 
         if (next_char <= 040
             || (next_char < 0200
-                && index ("\"';([#?", next_char)
-                || (!first_in_list && next_char == '`')
-                || (new_backquote_flag && next_char == ',')))
+                && (index ("\"';([#?", next_char)
+                    || (!first_in_list && next_char == '`')
+                    || (new_backquote_flag && next_char == ','))))
           {
             *pch = c;
             return Qnil;
@@ -3681,7 +3681,7 @@ init_lread ()
   /* When Emacs is invoked over network shares on NT, PATH_LOADSEARCH is
      almost never correct, thereby causing a warning to be printed out that
      confuses users.  Since PATH_LOADSEARCH is always overridden by the
-     EMACSLOADPATH environment variable below, disable the warning on NT.  
+     EMACSLOADPATH environment variable below, disable the warning on NT.
      Also, when using the "self-contained" option for Carbon Emacs for MacOSX,
      the "standard" paths may not exist and would be overridden by
      EMACSLOADPATH as on NT.  Since this depends on how the executable