unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: dim1212k@gmail.com, adam@alphapapa.net, casouri@gmail.com,
	emacs-devel@gnu.org
Subject: Re: Request for pointers and advice: displaying several buffers inside a single window
Date: Sat, 11 Apr 2020 10:34:08 +0300	[thread overview]
Message-ID: <831roumq6n.fsf@gnu.org> (raw)
In-Reply-To: <87h7xrxhh5.fsf@localhost> (message from Ihor Radchenko on Sat, 11 Apr 2020 03:34:30 +0800)

> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: casouri@gmail.com, dim1212k@gmail.com, adam@alphapapa.net,
>  emacs-devel@gnu.org
> Date: Sat, 11 Apr 2020 03:34:30 +0800
> 
> > And what do you suggest to do with the gap?
> 
> This is where the buffer text is stored internally right?

That's not the definition I'd use.  The gap is a way of making text
insertion less expensive.  If you insert characters one by one, each
insertion needs to move the characters after the insertion point,
which is expensive.  Having the gap allows us to perform this movement
only after relatively large amounts of text were inserted; for smaller
insertions we just make the gap smaller.

> I think a
> "segment" may as well refer to a substring from the gap. In the simplest
> case the list of "segments" would contain a single element referring to
> the whole gap. Then, if one adds another "segment", the list will hold 3
> elements: (<segment from beginning of the gap to pos> <added segment>
> <segment referring to the remaining part of the gap>).

My question was how you handle insertion in a segment?  Move the gap
to the segment, or have a separate gap for each segment?



  reply	other threads:[~2020-04-11  7:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 11:54 Request for pointers and advice: displaying several buffers inside a single window Dmitrii Korobeinikov
2020-04-03 13:07 ` Eli Zaretskii
2020-04-04 22:44   ` Dmitrii Korobeinikov
2020-04-05 14:08     ` Adam Porter
2020-04-05 22:55   ` Dmitrii Korobeinikov
2020-04-10 14:45     ` Yuan Fu
2020-04-10 15:35       ` Ihor Radchenko
2020-04-10 16:43         ` Eli Zaretskii
2020-04-10 17:46           ` Ihor Radchenko
2020-04-10 18:07             ` Eli Zaretskii
2020-04-10 18:37               ` Ihor Radchenko
2020-04-10 19:01                 ` Drew Adams
2020-04-10 19:19                   ` Ihor Radchenko
2020-04-10 20:29                     ` Drew Adams
2020-04-11  8:11                       ` Ihor Radchenko
2020-04-11 17:23                         ` Drew Adams
2020-04-12  2:42                           ` Richard Stallman
2020-04-12  5:09                             ` Drew Adams
2020-04-12  5:15                               ` Drew Adams
2020-04-13  2:21                               ` Richard Stallman
2020-04-13  5:23                                 ` Drew Adams
2020-04-12 23:54                             ` Juri Linkov
2020-04-13  5:23                               ` Drew Adams
2020-04-12 14:25                           ` Ihor Radchenko
2020-04-12 16:38                             ` Drew Adams
2020-04-10 19:12                 ` Eli Zaretskii
2020-04-10 19:25                   ` Ihor Radchenko
2020-04-10 19:34                   ` Ihor Radchenko
2020-04-11  7:34                     ` Eli Zaretskii [this message]
2020-04-11  8:35                       ` Ihor Radchenko
2020-04-11  9:25                         ` Eli Zaretskii
2020-04-10 19:09         ` Dmitrii Korobeinikov
2020-04-11  0:05           ` chad
2020-04-11  8:22             ` Eli Zaretskii
2020-04-11  7:30           ` Eli Zaretskii
2020-04-11  7:56             ` Dmitrii Korobeinikov
2020-04-11  8:26               ` Eli Zaretskii
2020-04-11 10:01                 ` Dmitrii Korobeinikov
2020-04-03 18:30 ` [SPAM UNSURE] " Stephen Leake
2020-04-05 13:18   ` Robert Pluim
2020-04-05 20:35     ` Dmitrii Korobeinikov

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=831roumq6n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=adam@alphapapa.net \
    --cc=casouri@gmail.com \
    --cc=dim1212k@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=yantar92@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 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).