From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: 23.0.60; Assuming errstring unibyte is incorrect and leads to Emacs crashes
Date: Thu, 28 Aug 2008 22:43:09 +0200 [thread overview]
Message-ID: <87abewyioy.fsf@escher.local.home> (raw)
In-Reply-To: uej4925bu.fsf@gnu.org
On Thu, 28 Aug 2008 06:20:37 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Kenichi Handa <handa@m17n.org>
>> CC: cyd@stupidchicken.com, dima@sphinx.net.ru, emacs-devel@gnu.org
>> Date: Thu, 28 Aug 2008 09:40:01 +0900
>>
>> > 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 (rms@mole.ai.mit.edu)
>>
>> * fileio.c (report_file_error): Don't downcase "I/O".
>>
>> Is this the reason?
>
> Yes, that's what I remembered as well. But if the reason is "I/O",
> why not test for that explicitly? Do certain locales translate "I/O"
> into a different string, which still has a slash as its second
> character?
"E/A" (for "Ein-/Ausgabe") is commonly used in German.
Steve Berman
next prev parent reply other threads:[~2008-08-28 20:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 17:28 23.0.60; Assuming errstring unibyte is incorrect and leads to Emacs crashes Chong Yidong
2008-08-27 1:13 ` Kenichi Handa
2008-08-27 3:20 ` Eli Zaretskii
2008-08-28 0:40 ` Kenichi Handa
2008-08-28 3:20 ` Eli Zaretskii
2008-08-28 5:53 ` Kenichi Handa
2008-08-28 9:23 ` Jason Rumney
2008-08-28 20:43 ` Stephen Berman [this message]
2008-08-31 18:36 ` Stefan Monnier
2008-09-01 6:11 ` Richard M. Stallman
2008-09-01 18:22 ` Stefan Monnier
2008-09-02 1:09 ` Richard M. Stallman
2008-09-02 19:56 ` Stefan Monnier
2008-09-03 2:41 ` Richard M. Stallman
2008-09-03 16:09 ` Stefan Monnier
2008-09-04 0:10 ` Richard M. Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87abewyioy.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).