unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: [Feature Discuss] Nested buffer
Date: Tue, 24 Jul 2018 09:16:05 +0200	[thread overview]
Message-ID: <87pnzdt87e.fsf@telefonica.net> (raw)
In-Reply-To: CANr+fmz+07Kf8x-fJe7xmEfzJGPH8SgNd79vFn1zreDxQo7_Pg@mail.gmail.com

Harry Fei <tiziyuanfang@gmail.com> writes:

>    - Case 1: Collect multiple narrowed-indirect-buffers to edit together.
>    - Sometimes, when I am working on a large project repository (Maybe
>       something like Chromium and AOSP), there are some codes highly related to
>       each other which spread in multiple files. So I want to collect them
>       together into a host buffer (embed narrow indirect buffer) when I read
>       those code. After I understand the logic, I want to edit those
> code in this
>       host buffer directly(the content sync back to the origin buffer). Even
>       more, I can use other editor functions, eg. string replace.

Something like this would be very convenient.

In my case, often I have to work on some feature that touches certain
areas of several source files and, at the same time, create and edit
several test cases, each on one file. Having everything on the same
buffer will save lots of buffer switching, while at the same time
providing a compact "work area" that eases reading and editing.




  reply	other threads:[~2018-07-24  7:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 16:03 [Feature Discuss] Nested buffer fei xiaobo
2018-07-23 19:51 ` Stefan Monnier
2018-07-24  3:33   ` Harry Fei
2018-07-24  7:16     ` Óscar Fuentes [this message]
2018-07-24 14:33       ` Eli Zaretskii
2018-07-24 14:54         ` Ihor Radchenko
2018-07-24 15:08           ` Eli Zaretskii
2018-07-25  4:41           ` Van L
2018-07-24 14:59         ` Óscar Fuentes
2018-07-24 15:03           ` Óscar Fuentes
2018-07-24 15:14           ` Eli Zaretskii
2018-07-25  2:31       ` Stefan Monnier
2018-07-23 20:11 ` Brett Gilio
2018-07-23 20:31   ` Clément Pit-Claudel
2018-07-23 23:15     ` Phil Sainty
2018-07-24  1:24       ` Drew Adams
2018-07-24 15:22         ` Drew Adams
2018-07-24 16:54       ` Alan Mackenzie
2018-07-25  2:28     ` 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=87pnzdt87e.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).