all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 37818@debbugs.gnu.org
Subject: bug#37818: [PATCH] Various FAQ updates
Date: Sat, 19 Oct 2019 17:20:03 +0300	[thread overview]
Message-ID: <838spg7r70.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkGFp6RZTCDHR3p-UqqC3K3iDr0KXoLMpzj2rgsWg+L1Q@mail.gmail.com> (message from Stefan Kangas on Sat, 19 Oct 2019 14:58:53 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 19 Oct 2019 14:58:53 +0200
> Cc: 37818@debbugs.gnu.org
> 
> Thanks.  I've attached a revised patch here according to your
> comments.

I have some, see below.

> I'm not sure what the file size limit is for
> --with-wide-int on 32-bit builds or 64-bit builds, so that still needs
> adding.  Could someone please give the exact numbers or tell me where
> I can find them?

See below.

> +Emacs has an inherent fixed limitation on the size of buffers.

I'd suggest to say that the limitation is more strict that the maximum
size of objects supported by programs with the same architecture,
because otherwise this sentence might be misunderstood.

>                                                                  The
> +maximum buffer size on 32-bit machines is 512 MBytes beginning with
> +version 23.2.  If Emacs was built using the @code{--with-wide-int}
> +flag, the maximum buffer size on 32-bit machines is ***FIXME***
> +MBytes.

The number here is 2GB.

> +This limitation imposes a size limit on visiting files, which is
> +roughly half the buffer limit due to things like decoding of multibyte
> +characters.  When visiting compressed archives, the file size
> +limitation will be smaller than that due to decompression.
> +
> +Unless you want to visit unusually large files, this should only be an
> +issue on 32-bit machines.  Emacs compiled on a 64-bit machine can
> +handle much larger buffers.

The limit value for 64-bit builds is that of most-positive-fixnum.





  reply	other threads:[~2019-10-19 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 21:07 bug#37818: [PATCH] Various FAQ updates Stefan Kangas
2019-10-19  6:27 ` Eli Zaretskii
2019-10-19 12:58   ` Stefan Kangas
2019-10-19 14:20     ` Eli Zaretskii [this message]
2019-10-20 13:53       ` Stefan Kangas
2019-10-20 14:48         ` Eli Zaretskii
2019-10-23 23:11           ` Stefan Kangas
2019-10-19  8:35 ` Lars Ingebrigtsen
2019-10-19 12:59   ` Stefan Kangas
2019-10-23 23:10     ` Stefan Kangas

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=838spg7r70.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37818@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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.