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: Thu, 04 Oct 2012 16:00:37 +0200 [thread overview]
Message-ID: <87obkinxq2.fsf@kanis.fr> (raw)
In-Reply-To: <83lifn8fjs.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 03 Oct 2012 22:29:59 +0200")
Eli Zaretskii <eliz@gnu.org> wrote:
>> > 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?
>
> They can always ask here, like you did (or google and find the
> answer). Not every little factoid needs to be in the docs.
Fair enough. Now that I have set extra pure size to an obscene amount I
will never see the warning anymore.
--
Ivan Kanis
http://ivan.kanis.fr
If a man should conquer in battle a thousand and a thousand more, and
another man should conquer himself, his would be the greater victory,
because the greatest of victories is the victory over oneself.
-- Pali Tripitaka
prev parent reply other threads:[~2012-10-04 14:00 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
2012-10-03 20:29 ` Eli Zaretskii
2012-10-04 14:00 ` Ivan Kanis [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obkinxq2.fsf@kanis.fr \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.