From: Eli Zaretskii <eliz@gnu.org>
To: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
Cc: user.emacs@gmail.com, emacs-devel@gnu.org
Subject: Re: bug#7517: 24.0.50; repeated crash under Mac OS X
Date: Mon, 03 Jan 2011 00:08:50 +0200 [thread overview]
Message-ID: <83sjxbnekt.fsf@gnu.org> (raw)
In-Reply-To: <19744.58213.935000.469856@gargle.gargle.HOWL>
> Date: Sun, 2 Jan 2011 20:43:17 +0000
> From: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
> Cc: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>,
> user.emacs@gmail.com,
> emacs-devel@gnu.org
>
> > The only subtlety here is that iso-8859-8-i is a coding-system-alias
> > of iso-8859-8. Does that help to resolve the issue?
>
> I have now given up on using the mime-charset property to search for
> coding systems because of the too many aliases going on. However, it
> seems that all the coding systems have aliases that correspond to MIME
> charset names. So, I am using that to find the right coding system.
Why, doesn't
(coding-system-get FOO :mime-charset)
work for you, or isn't TRT in this case?
> However, OP reports that the frame title says "bad coding" or some
> such incantation, even though the buffer name shows up correctly
> inside Emacs. Perhaps it is a problem in the interface between Emacs
> and the OS?
No, that's our way to defend ourselves against buffer names that are
unibyte strings, to avoid a crash that was the trigger for this bug.
If the unibyte buffer name is now solved, the "bad coding" text will
never show up.
next prev parent reply other threads:[~2011-01-02 22:08 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin-OjWynp7GOEPnSTKxf2PXH1+t6LWbmQBwCCFD@mail.gmail.com>
[not found] ` <87tyic1uzh.fsf@stupidchicken.com>
[not found] ` <AANLkTinQHfFXazEbf+qxtz5+MfKcaXQLN18nPnyQMj8X@mail.gmail.com>
[not found] ` <AANLkTi=eou59qi2vgMZpWpcWy5xJfgkCKbYr-_LcqYDH@mail.gmail.com>
2010-12-29 4:29 ` bug#7517: 24.0.50; repeated crash under Mac OS X Chong Yidong
2010-12-29 11:59 ` Jan Djärv
2010-12-29 12:21 ` Jan Djärv
2010-12-29 15:41 ` Stefan Monnier
2010-12-29 16:06 ` emacs user
2010-12-30 11:35 ` Jan Djärv
2010-12-30 14:20 ` emacs user
2010-12-30 22:02 ` Jan Djärv
2010-12-31 6:11 ` emacs user
2010-12-31 6:12 ` emacs user
2010-12-31 8:18 ` Eli Zaretskii
2010-12-31 11:16 ` emacs user
2010-12-31 10:49 ` Jan Djärv
2010-12-31 11:23 ` Jan Djärv
2010-12-31 11:26 ` emacs user
2010-12-31 12:53 ` Eli Zaretskii
2010-12-31 13:06 ` emacs user
2010-12-31 13:18 ` Jan Djärv
2010-12-31 13:10 ` Jan Djärv
2010-12-31 13:19 ` Eli Zaretskii
2010-12-31 14:22 ` Jan Djärv
2010-12-31 16:07 ` Eli Zaretskii
2010-12-31 16:09 ` emacs user
2010-12-31 18:57 ` Jan Djärv
2011-01-01 3:55 ` Stephen J. Turnbull
2010-12-31 16:56 ` Stefan Monnier
2010-12-31 17:42 ` emacs user
2010-12-31 22:30 ` Jan Djärv
2010-12-31 23:07 ` Stefan Monnier
2011-01-01 11:57 ` Eli Zaretskii
2011-01-01 12:46 ` emacs user
2011-01-01 15:40 ` Eli Zaretskii
2011-01-01 17:02 ` Uday S Reddy
2011-01-01 18:08 ` Eli Zaretskii
2011-01-01 18:34 ` Jan D.
2011-01-02 14:02 ` Chong Yidong
2011-01-03 21:34 ` Jan Djärv
2011-01-01 17:22 ` Stefan Monnier
2011-01-01 18:07 ` Eli Zaretskii
2011-01-01 12:00 ` Eli Zaretskii
2011-01-01 17:11 ` Stefan Monnier
2011-01-01 18:06 ` Eli Zaretskii
[not found] ` <8362u8pkg6.fsf__47242.3368752517$1293906238$gmane$org@gnu.org>
2011-01-01 22:43 ` Uday S Reddy
2011-01-02 4:03 ` Eli Zaretskii
2011-01-02 20:43 ` Uday S Reddy
2011-01-02 22:06 ` Jan Djärv
2011-01-03 4:59 ` Uday S Reddy
2011-01-03 8:10 ` emacs user
2011-01-02 22:08 ` Eli Zaretskii [this message]
2011-01-03 4:50 ` Uday S Reddy
2011-01-03 13:10 ` Eli Zaretskii
2011-01-03 21:07 ` Jan Djärv
2011-01-03 0:27 ` Stefan Monnier
2010-12-31 12:52 ` Eli Zaretskii
2010-12-31 13:16 ` Eli Zaretskii
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=83sjxbnekt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=u.s.reddy@cs.bham.ac.uk \
--cc=user.emacs@gmail.com \
/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).