unofficial mirror of bug-gnu-emacs@gnu.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 09:27:41 +0300	[thread overview]
Message-ID: <834l058d2a.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkF87Kdy4bUQ2Owv0oyZS2fAs=kkgMWcnLPyPvJL==JLA@mail.gmail.com> (message from Stefan Kangas on Fri, 18 Oct 2019 23:07:10 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 18 Oct 2019 23:07:10 +0200
> 
> 1. Remove section on how to enable the default behaviour of having the
> region highlighted, which is probably not a frequently asked question.

OK.

> 2. Remove information on large files in ancient versions of Emacs that
> would only confuse new users.  This leaves in only the information on
> the relatively recent versions of Emacs.

IMO, this section should first tell that Emacs has an inherent fixed
limitation on the size of buffers, as that is not something people
assume nowadays.  It should cite the limitation separately for 32-bit
builds, 32-bit builds --with-wide-int, and 64-bit builds.  Then it
should say that this limitation also imposes size limit on visiting
files, but the file-size limit is roughly about half the buffer limit,
due to decoding and other stuff.  I would also mention visiting
compressed archives, because the size limitation might be hit half-way
through decompression.

Thanks.





  reply	other threads:[~2019-10-19  6:27 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 [this message]
2019-10-19 12:58   ` Stefan Kangas
2019-10-19 14:20     ` Eli Zaretskii
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

  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=834l058d2a.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 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).