From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs opens only first 16384 bytes of file?!
Date: Sun, 12 Feb 2023 08:11:04 +0100 [thread overview]
Message-ID: <Y+iRCPK6oVeNvdTC@tuxteam.de> (raw)
In-Reply-To: <83ilg7ifpe.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On Sun, Feb 12, 2023 at 08:02:37AM +0200, Eli Zaretskii wrote:
> > From: Christoph Groth <christoph@grothesque.org>
> > Date: Sat, 11 Feb 2023 22:16:52 +0100
> >
> > I just noticed something that made me doubt my own sanity: With Emacs
> > 27.1 (from Debian stable running Debian’s Linux kernel
> > 6.0.0-0.deb11.6-amd64) the command
> >
> > emacs -q -nw /proc/cpuinfo
> >
> > reproducibly opens cpuinfo only up to a portion of line 272, while the
> > entire file is 560 lines long on that machine. I checked on a different
> > machine (with same Emacs), and I see the same behavior.
> >
> > C-u C-x = tells that the file is read up to position 16384 (= 2^14).
> >
> > Running M-x revert-buffer loads the whole file...
> >
> > Is/was this a known issue? I could not find anything on the web.
>
> Please report this as a bug.
I think the bug is already there (#9800) [1]
[1] https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-02/msg00459.html
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-02-12 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 21:16 Emacs opens only first 16384 bytes of file?! Christoph Groth
2023-02-12 3:55 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-02-12 4:55 ` Óscar Fuentes
2023-02-12 5:56 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-02-12 9:58 ` Christoph Groth
2023-02-12 11:45 ` Eli Zaretskii
2023-02-12 6:02 ` Eli Zaretskii
2023-02-12 7:11 ` tomas [this message]
2023-02-12 7:33 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2023-02-13 7:59 Christoph Groth
2023-02-13 13:06 ` Eli Zaretskii
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=Y+iRCPK6oVeNvdTC@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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.
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).