From: Perry Smith <pedz@easesoftware.com>
To: Gregory Heytings <ghe@sdf.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Opening multiple files in a single buffer?
Date: Sat, 13 Jun 2020 14:45:39 -0500 [thread overview]
Message-ID: <53D2E172-0D7E-4440-84C7-8650B3AA7FCB@easesoftware.com> (raw)
In-Reply-To: <alpine.NEB.2.22.394.2006132121550.24604@sdf.lonestar.org>
> On Jun 13, 2020, at 2:22 PM, Gregory Heytings <ghe@sdf.org> wrote:
>
>
>>
>>> Another application would be to open all the code files in a directory into a single buffer, and do replace-string or query-replace on all of them, to rename variables, for example.
>>
>> We have a special Dired command to do such renaming.
>>
>
> Indeed, but that's not the point. As I said what I'm proposing is a way to do some things more easily (for some users). Everything that could be done with such a feature can already be done in other ways. I don't use the menu-bar, the tool-bar, customize, or the menus on the mode-line. But I do not consider that they are useless. All these features make it possible to do things more easily (for some users), that can already be done in other ways.
Before you decide to dive into this, I would suggest doing a test run by writing a simple script to cat the files together with a separator and edit that file with something like search and replace or bounce around in various places making edits. I have vague memories that when buffers get extremely big, emacs slows down considerably but my memories are not clear enough to recall the exact circumstances. Perhaps one of the emacs maintainers can jump in and comment. Is emacs going to be more efficient with several “small” buffers rather than one extremely large buffer. Some of the people commenting are wanting to load up an entire project into a single buffer. As I recall, that is going to be very unfriendly to use.
next prev parent reply other threads:[~2020-06-13 19:45 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 [this message]
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 ` 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=53D2E172-0D7E-4440-84C7-8650B3AA7FCB@easesoftware.com \
--to=pedz@easesoftware.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.
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).