all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: arthur miller <arthur.miller@live.com>
To: Gregory Heytings <ghe@sdf.org>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Sv: Opening multiple files in a single buffer?
Date: Mon, 15 Jun 2020 06:58:04 +0000	[thread overview]
Message-ID: <VI1PR06MB45269DED914DF98CA78E3710969C0@VI1PR06MB4526.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <alpine.NEB.2.22.394.2006142153450.9148@sdf.lonestar.org>

That sounds great!
________________________________
Från: help-gnu-emacs <help-gnu-emacs-bounces+arthur.miller=live.com@gnu.org> för Gregory Heytings <ghe@sdf.org>
Skickat: den 14 juni 2020 22:14
Till: help-gnu-emacs@gnu.org <help-gnu-emacs@gnu.org>
Ämne: Re: Opening multiple files in a single buffer?


>
> Wonder how fast it would work with emacs src directory by opening all .h
> anc .c files, some of which are 5k+ lines of code. If that is the case
> for refactorisation and similar.
>

I just tried this.  With "cat *.h *.c > all.c" in the Emacs src directory,
the resulting file is 11 MB, for about 370K source lines.  Opening and
using that file, with c-mode, font-lock-mode, transient-mark-mode,
hl-line-mode and display-line-numbers-mode (and a few others), works
without any visible problems.  I tried e.g. to insert some code at random
places, to kill the second half ot the buffer and to yank it as its first
part, to query-replace-regexp the 1652 occurrences of "E\([^ ]*\)s " with
"Es\1 ", to narrow-to-region/widen, ...  The Emacs process did not use
more than 120 MB.

Gregory



  reply	other threads:[~2020-06-15  6:58 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
2020-06-14  7:45               ` Arthur Miller
2020-06-14 20:14                 ` Gregory Heytings
2020-06-15  6:58                   ` arthur miller [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=VI1PR06MB45269DED914DF98CA78E3710969C0@VI1PR06MB4526.eurprd06.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=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.
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.