From: Ivan Kanis <ivan.kanis@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: specifying pure space without editing puresize.h
Date: Wed, 03 Oct 2012 21:50:02 +0200 [thread overview]
Message-ID: <87haqbnxn9.fsf@googlemail.com> (raw)
In-Reply-To: <83a9w3a2nw.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 03 Oct 2012 19:25:23 +0200")
Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Ivan Kanis <ivan.kanis@googlemail.com>
>> Date: Wed, 03 Oct 2012 09:59:33 +0200
>> Cc: emacs-devel@gnu.org
>>
>> Óscar Fuentes <ofv@wanadoo.es> wrote:
>>
>> > This was posted two days ago:
>> >
>> > Achim Gratz <Stromeko@nexgo.de> writes:
>> >
>> >> Eli Zaretskii writes:
>> >>>> Warning (initialization): Building Emacs overflowed pure space.
>> >>>> (See the node Pure Storage in the Lisp manual for details.)
>> >>>
>> >>> Enlarge BASE_PURESIZE in puresize.h until the warning goes away.
>> >>
>> >> …or call configure with '-DSYSTEM_PURESIZE_EXTRA=some_number' added to
>> >> CFLAGS.
>> >
>>
>> May it should be documented in the relevant info node?
>
> What for? These are temporary situations that exist until the Emacs
> maintainers get their act together and enlarge the size of the pure
> storage. This happens once in a year or two, so I see nothing
> important enough to document here, no more than we should be
> documenting gazillions of other similar knobs in our headers.
I was looking for the information. Someone else might. Isn't what the
documentation is for?
--
Ivan Kanis
http://ivan.kanis.fr
Predictability: does the flap of a butterfly's wings in Brazil set off
a tornado in Texas?
-- Edward N. Lorenz
next prev parent reply other threads:[~2012-10-03 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 7:25 specifying pure space without editing puresize.h Ivan Kanis
2012-10-02 7:44 ` Stephen J. Turnbull
2012-10-02 12:36 ` Óscar Fuentes
2012-10-02 17:52 ` Ivan Kanis
2012-10-03 7:59 ` Ivan Kanis
2012-10-03 8:46 ` Achim Gratz
2012-10-03 17:31 ` Eli Zaretskii
2012-10-03 17:25 ` Eli Zaretskii
2012-10-03 19:50 ` Ivan Kanis [this message]
2012-10-03 20:29 ` Eli Zaretskii
2012-10-04 14:00 ` Ivan Kanis
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=87haqbnxn9.fsf@googlemail.com \
--to=ivan.kanis@googlemail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).