From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Comments on display.texi
Date: Tue, 28 Sep 2004 14:58:41 +0200 [thread overview]
Message-ID: <m3zn3a7doe.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1CBwsq-0000A7-6U@fencepost.gnu.org> (Richard Stallman's message of "Mon, 27 Sep 2004 10:53:44 -0400")
Richard Stallman <rms@gnu.org> writes:
> But even faces have a limit of 21^2-1, so emacs is not without
> arbitrary limits.
>
> So there must be some limit -- which ? 2^32-1 ?
>
> A limit of 2^21 would be ok, if it is painful to overcome.
Actually, the 2^21 limit on faces is because we want to reduce
memory usage for glyphs.
Each glyph struct contains a face id as well as a number of 1-bit
boolean fields. There are 11 such 1-bit fields, so to keep these
together with the face id in 32 bits, the face id is 32-11 = 21 bits
wide.
Re. number of bitmaps:
I still have problems envisioning anybody using more than a few
bitmaps in any mode (ok, a mode which shows line numbers in
the fringe would probably use a couple of 100s).
Currently, the only package using bitmaps is gdb-ui -- and it uses
just ONE.
IMO, for 21.4 a limit of 4095 would be more than adequate.
define-fringe-bitmap should signal an error if there are no free
bitmap slots.
There are several places in the code which uses a static allocation
based on the max number of bitmaps. Of course they can be made
dynamic, but that would be unnecessary, we could agree on a limit of
4095 for 21.4. WDYT?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-09-28 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 0:19 Comments on display.texi Kim F. Storm
2004-09-26 18:20 ` Richard Stallman
2004-09-26 20:38 ` Kim F. Storm
2004-09-27 14:53 ` Richard Stallman
2004-09-28 12:40 ` Kim F. Storm
2004-09-27 14:53 ` Richard Stallman
2004-09-28 12:58 ` Kim F. Storm [this message]
2004-09-28 22:48 ` Richard Stallman
2004-09-29 14:39 ` Kim F. Storm
2004-09-29 14:56 ` David Kastrup
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=m3zn3a7doe.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).