unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: [Feature Discuss] Nested buffer
Date: Tue, 24 Jul 2018 18:14:16 +0300	[thread overview]
Message-ID: <83r2jsvf7b.fsf@gnu.org> (raw)
In-Reply-To: <87h8kou1c0.fsf@telefonica.net> (message from Óscar Fuentes on Tue, 24 Jul 2018 16:59:11 +0200)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Tue, 24 Jul 2018 16:59:11 +0200
> 
> > 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.

Not nowadays.

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

I just create a new frame for that, and use that frame only for such
special situations.  All the other buffers live on other frames, so
popping buffers don't bother me.

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

If you say so.  Volunteers are welcome to come up with patches that
implement this cleanly.



  parent reply	other threads:[~2018-07-24 15:14 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
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 [this message]
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=83r2jsvf7b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).