From: Gregory Heytings <ghe@sdf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Opening multiple files in a single buffer?
Date: Sun, 14 Jun 2020 07:12:22 +0000 [thread overview]
Message-ID: <alpine.NEB.2.22.394.2006140904280.1059@sdf.lonestar.org> (raw)
In-Reply-To: <VI1PR06MB4526FF72F71920AA4247D616969F0@VI1PR06MB4526.eurprd06.prod.outlook.com>
>
>> That's not correct. On my laptop, I can easily edit a 100 (one
>> hundred) MB text file, Emacs is almost as reactive as with a 1 KB text
>> file. Of course some operations take more time, e.g. a
>> query-replace-regexp on the whole buffer, but from what I see (on my
>> laptop it takes about four seconds, with a regexp) I doubt that it
>> takes more time than hundred query-replace-regexp in a 1 MB file, or
>> for that matter than doing this with dired on hundred 1 MB files.
>>
> I think it depends on content in those files as well as of size.
>
> Try to edit some of those two files: https://github.com/amno1/Plato ,
> possibly Plato.org. Don't just display them, but try to actually put
> some text note in it or add/remove some whitespace or whatever. Jump to
> some paragraph and insert a new line and see how long it takes. Then try
> to do same in Atom text editor.
>
> My Emacs takes quite some time even to add a white space char while Atom
> has not problems whatsoever. I run on 6700K i7 cpu + 32 gig 3000Mhz ram.
>
> I don't know what the problem is, if it is just my Emacs config or
> actually underlaying data structure (Gap buffer vs linked structure
> optimized for changes - their "Superstring").
>
These files work flawlessly on my laptop (under Org-mode), which has half
the memory of your computer. So this has nothing to do with Emacs per se.
I don't know what the problem on your computer is. I'd suggest to try to
open these files by opening with emacs -q. Then try to find what causes
the problem in your .emacs file.
Anyway, all this has nothing to do with the proposed feature. The fact
that it will not work under some circumstances is obvious and is not a
problem. Of course every feature has a limit, I mean, even opening files
does not work anymore above some limit.
Gregory
next prev parent reply other threads:[~2020-06-14 7:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 14:31 Opening multiple files in a single buffer? Gregory Heytings
2020-06-13 15:20 ` Douglas Lewan
2020-06-13 16:53 ` Gregory Heytings
2020-06-13 15:21 ` tomas
2020-06-13 15:36 ` Douglas Lewan
2020-06-13 15:53 ` tomas
2020-06-13 15:49 ` Jakub Jankiewicz
2020-06-13 16:43 ` Stefan Monnier
2020-06-14 11:11 ` Michael Albinus
2020-06-15 8:26 ` Gregory Heytings
2020-06-15 9:33 ` tomas
2020-06-15 9:52 ` Gregory Heytings
2020-06-15 10:58 ` tomas
2020-06-15 12:48 ` Joost Kremers
2020-06-15 14:24 ` Gregory Heytings
2020-06-15 14:41 ` Stefan Monnier
2020-06-15 12:21 ` Sergey Organov
2020-06-15 15:26 ` Gregory Heytings
2020-06-15 15:31 ` Perry Smith
2020-06-13 18:10 ` Dan Hitt
2020-06-13 18:41 ` Jakub Jankiewicz
2020-06-13 18:41 ` Eli Zaretskii
2020-06-13 19:22 ` Gregory Heytings
2020-06-13 19:45 ` Perry Smith
2020-06-13 20:42 ` Gregory Heytings
2020-06-14 5:29 ` Arthur Miller
2020-06-14 7:12 ` Gregory Heytings [this message]
2020-06-14 7:45 ` Arthur Miller
2020-06-14 20:14 ` Gregory Heytings
2020-06-15 6:58 ` Sv: " arthur miller
2020-06-13 19:31 ` Stefan Monnier
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=alpine.NEB.2.22.394.2006140904280.1059@sdf.lonestar.org \
--to=ghe@sdf.org \
--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).