unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Gregory Heytings <ghe@sdf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Opening multiple files in a single buffer?
Date: Mon, 15 Jun 2020 14:24:29 +0000	[thread overview]
Message-ID: <alpine.NEB.2.22.394.2006151550300.18619@sdf.lonestar.org> (raw)
In-Reply-To: <87a714ze85.fsf@fastmail.fm>


>
> I can't tell you how feasible it would be, but unless you want to 
> implement it yourself, you'll probably have to do some more convincing 
> in order to get someone to implement it for you. As you said yourself, 
> the potential use cases for such a multi-file buffer are easily covered 
> by other means.
>

Are covered: yes.  Are easily covered: no.  If you take the tool-bar, 
everything it offers is (very!) easily covered by other means.  Yet it 
exists, because it makes these things easier for some users.

>
> There is `multi-occur` for searching in multiple buffers, there are 
> front-ends to e.g., ripgrep (I use `counsel-rg` self) to search through 
> multiple files and with `wgrep` you can then edit those occurrences in 
> one go. (I use `multiple-cursors`, but you can also do a search and 
> replace in the multi-occur buffer.)
>

Yes, these tools exist.  Yet I'd bet that many users would find a 
multi-file buffer far easier to use than these tools.  Many users find it 
easier to use customize than to type Emacs LISP code by hand in their 
.emacs file.

Gregory



  reply	other threads:[~2020-06-15 14:24 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 [this message]
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                   ` 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.2006151550300.18619@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).