From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: [Feature Discuss] Nested buffer Date: Tue, 24 Jul 2018 16:59:11 +0200 Message-ID: <87h8kou1c0.fsf@telefonica.net> References: <87pnzdt87e.fsf@telefonica.net> <83wotkvh42.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1532444271 32434 195.159.176.226 (24 Jul 2018 14:57:51 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 24 Jul 2018 14:57:51 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 24 16:57:47 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fhyl1-0008LM-HF for ged-emacs-devel@m.gmane.org; Tue, 24 Jul 2018 16:57:47 +0200 Original-Received: from localhost ([::1]:40985 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhyn8-0008B7-GS for ged-emacs-devel@m.gmane.org; Tue, 24 Jul 2018 10:59:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhyma-0008Ar-Eu for emacs-devel@gnu.org; Tue, 24 Jul 2018 10:59:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fhymX-0007LG-Dc for emacs-devel@gnu.org; Tue, 24 Jul 2018 10:59:24 -0400 Original-Received: from [195.159.176.226] (port=45760 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fhymX-0007Kr-5G for emacs-devel@gnu.org; Tue, 24 Jul 2018 10:59:21 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fhykN-0007ZT-Pv for emacs-devel@gnu.org; Tue, 24 Jul 2018 16:57:07 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 32 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:WfsxjGckgIelR0JlgJ61n9FA9ek= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:227769 Archived-At: Eli Zaretskii writes: >> 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. > > Any reason why several windows side by side couldn't serve the same > purpose? (You can disable the mode line if that gets in the way.) That is what I do when the number of affected areas is small, but... 1. The screen has limited space. 2. Arranging the windows takes time and is fragile (commands like `compile' and derivatives changes the layout, temporally or permanently; you are forced to use another frame for magit, gnus...). 3. Editing a single buffer is more natural and convenient. Things like "replace this with that" would be automatically narrowed to the contents of the virtual buffer. I see the OP's proposal as a method for achieving narrowing at the file level (Emacs already has buffer-level narrowing): pick some files, put them (or parts of them) on the same buffer, and proceed as if you were working on a mini-project written on a single file. My first impression about his proposal was kind of "meh", but the more I think about it, the more interesting it looks.