From: Chong Yidong <cyd@stupidchicken.com>
Cc: bob@rattlesnake.com, emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: overflow pure space
Date: Wed, 05 Jul 2006 14:44:48 -0400 [thread overview]
Message-ID: <87sllfj3hb.fsf@stupidchicken.com> (raw)
In-Reply-To: <uac7nrjbe.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Jul 2006 21:35:33 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > Warning (initialization): Building Emacs overflowed pure space.
>> > (See the node Pure Storage in the Lisp manual for details.)
>> >
>> > Did someone do something that caused this in the GTK+ version but not
>> > in others?
>>
>> I saw this too, and have checked in a patch to increment puresize.
>
> I'm not sure that was wise. There's some mystery going on with
> puresize; unfortunately I didn't have enough time to finish
> investigating it based on Reiner's reports. Perhaps someone could
> pick up where I left off and find out the reason(s) for these
> disparities. The relevant thread is "Re: PURESIZE increased (again)".
FWIW, I think the puresize overflow came from the following change.
2006-07-04 Kenichi Handa <handa@m17n.org>
* international/mule-cmds.el (set-language-info): If LANG-ENV is
the current one, don't call set-language-environment, but call one
of set-language-environment-XXX to make INFO effective now.
(set-language-environment): Call set-language-environment-XXX
functions instead of doing the various setups directly.
(set-language-environment-coding-systems): Delete argument eol-type.
(set-language-environment-input-method)
(set-language-environment-nonascii-translation)
(set-language-environment-charset)
(set-language-environment-fontset)
(set-language-environment-unibyte): New functions.
next prev parent reply other threads:[~2006-07-05 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 15:04 overflow pure space Robert J. Chassell
2006-07-05 15:42 ` Chong Yidong
2006-07-05 18:35 ` Eli Zaretskii
2006-07-05 18:44 ` Chong Yidong [this message]
2006-07-06 3:32 ` Eli Zaretskii
2006-07-06 11:01 ` YAMAMOTO Mitsuharu
2006-07-06 11:40 ` Evil Boris
2006-07-05 17:45 ` Jan Djärv
2006-07-05 20:02 ` Miles Bader
2006-07-05 21:52 ` Robert J. Chassell
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=87sllfj3hb.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).