From: James Thomas <jimjoe@gmx.net>
To: Vladimir Kazanov <vekazanov@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Buffers with buffers (transclusion)
Date: Thu, 17 Oct 2024 19:39:12 +0530 [thread overview]
Message-ID: <86ttdau8hj.fsf@gmx.net> (raw)
In-Reply-To: <CAAs=0-0Try3Z9ekYS_nBN31dJhGOh57t+Orsf=oibb1tM8mjLA@mail.gmail.com> (Vladimir Kazanov's message of "Thu, 17 Oct 2024 09:38:06 +0100")
Vladimir Kazanov wrote:
> Eli, James,
>
>> Yes, that's exactly the kind of thoughts I had when reading the
>> description. Why do we need to display text from different sources in
>> the same buffer, when we already have side-by-side display in adjacent
>> windows? If the problem is the decoration which set windows apart, it
>> is a minor issue to begin with, and we can make the separating
>> decorations less prominent.
>
> True, having a bunch of stacked windows, or side by side windows,
> works to an extent, and this is how I do it now. There are downsides
> to this approach.
>
> Firstly, all of the editing always happens in one of the windows, not
> across windows: search/replace, occur, grep. Having things in one
> buffer makes these things as easy as editing a single small file.
There are things like multi-isearch/occur already, no?
> Also, the number of windows that can be comfortably used in this
> manner is limited. 2? 3? 4? Doing this within a single window is just
> simpler.
Isn't 2 or 3 enough? AFAIU, one at the bottom to phase-in the succeeding
buffer, and the obverse of that. Of course, depending on buffer content.
Regards,
James
next prev parent reply other threads:[~2024-10-17 14:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 13:53 Buffers with buffers (transclusion) Vladimir Kazanov
2024-10-15 14:45 ` Eli Zaretskii
2024-10-15 15:01 ` Vladimir Kazanov
2024-10-16 22:44 ` James Thomas
2024-10-17 6:27 ` Eli Zaretskii
2024-10-17 8:38 ` Vladimir Kazanov
2024-10-17 11:00 ` Eli Zaretskii
2024-10-17 11:38 ` Vladimir Kazanov
2024-10-17 12:59 ` Eli Zaretskii
2024-10-17 13:24 ` Vladimir Kazanov
2024-10-17 15:15 ` Eli Zaretskii
2024-10-17 14:36 ` Suhail Singh
2024-10-17 15:19 ` Eli Zaretskii
2024-10-17 16:28 ` Suhail Singh
2024-10-17 17:18 ` Eli Zaretskii
2024-10-18 9:25 ` Vladimir Kazanov
2024-10-17 14:09 ` James Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 17:57 Christopher Howard
2024-10-16 10:48 ` Vladimir Kazanov
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=86ttdau8hj.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=vekazanov@gmail.com \
/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.