[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 23.0.60; Assuming errstring unibyte is incorrect and leads to Emacs
From: |
Kenichi Handa |
Subject: |
Re: 23.0.60; Assuming errstring unibyte is incorrect and leads to Emacs crashes |
Date: |
Thu, 28 Aug 2008 09:40:01 +0900 |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
In article <address@hidden>, Eli Zaretskii <address@hidden> writes:
> > From: Kenichi Handa <address@hidden>
> > Date: Wed, 27 Aug 2008 10:13:06 +0900
> > Cc: address@hidden, address@hidden
> >
> > + if (! EQ (Faref (errstring, make_number (1)), make_number ('/')))
> > + {
> > + int c;
> > +
> > + str = (char *) SDATA (errstring);
> > + c = STRING_CHAR (str, 0);
> > + Faset (errstring, 0, make_number (DOWNCASE (c)));
> > + }
> Can we explain in a comment what is special about a slash as the
> second character of the error message?
We should, but I don't know the reason. By grepping
ChangeLog files, I found this item:
1991-02-21 Richard Stallman (address@hidden)
* fileio.c (report_file_error): Don't downcase "I/O".
Is this the reason?
---
Kenichi Handa
address@hidden