unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Phil Sainty" <psainty@orcon.net.nz>,
	"Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: Emacs-devel <emacs-devel-bounces+psainty=orcon.net.nz@gnu.org>,
	emacs-devel@gnu.org
Subject: RE: [Feature Discuss] Nested buffer
Date: Mon, 23 Jul 2018 18:24:00 -0700 (PDT)	[thread overview]
Message-ID: <cd884131-9ee1-46bb-9b45-ae1cbbc522ec@default> (raw)
In-Reply-To: <19151eff43b77d7548828a8ed98c160e@webmail.orcon.net.nz>

> > I think anything that was covered by the islands proposals
> 
> This new suggestion sounds rather like narrowed indirect buffers
> (which we can do already), or perhaps an extension of that facility?

The new proposal sounds like nearly anything one might want
to imagine.  IOW, it sounds like nothing at all.  It needs
to be specified - nailed down quite a bit more, so people
can actually think about it, instead of just imagining stuff.



  reply	other threads:[~2018-07-24  1:24 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
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 [this message]
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=cd884131-9ee1-46bb-9b45-ae1cbbc522ec@default \
    --to=drew.adams@oracle.com \
    --cc=cpitclaudel@gmail.com \
    --cc=emacs-devel-bounces+psainty=orcon.net.nz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=psainty@orcon.net.nz \
    /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).