From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Request for pointers and advice: displaying several buffers inside a single window Date: Sat, 11 Apr 2020 11:26:05 +0300 Message-ID: <83wo6ml97m.fsf@gnu.org> References: <83a73swwd7.fsf@gnu.org> <87wo6nxsjz.fsf@localhost> <83369amqdi.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="72341"; mail-complaints-to="usenet@ciao.gmane.io" Cc: adam@alphapapa.net, casouri@gmail.com, yantar92@gmail.com, emacs-devel@gnu.org To: Dmitrii Korobeinikov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 11 10:26:48 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jNBTU-000Ik9-8f for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Apr 2020 10:26:48 +0200 Original-Received: from localhost ([::1]:49850 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jNBTT-0002qF-B4 for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Apr 2020 04:26:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35314) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jNBT1-0002PC-D5 for emacs-devel@gnu.org; Sat, 11 Apr 2020 04:26:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:40769) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jNBT1-0005Vq-9c; Sat, 11 Apr 2020 04:26:19 -0400 Original-Received: from [176.228.60.248] (port=1482 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jNBT0-00055i-Fs; Sat, 11 Apr 2020 04:26:18 -0400 In-Reply-To: (message from Dmitrii Korobeinikov on Sat, 11 Apr 2020 13:56:07 +0600) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246826 Archived-At: > From: Dmitrii Korobeinikov > Date: Sat, 11 Apr 2020 13:56:07 +0600 > Cc: Ihor Radchenko , Yuan Fu , adam@alphapapa.net, > emacs-devel > > By "unified core interface", I meant something like an OOP-style > public interface done in a way so the users don't have to know about > the implementation and underlying data structures You will find that in buffer.h. Modify those interfaces, and you are done. > > > The good news is: I believe xdisp.c wouldn't have to be modified all > > > that much if the regions are enforced to start on different lines. > > > > How so? The display code accesses the buffer text directly, using > > BYTE_POS_ADDR. > > I didn't say it wouldn't have to be touched at all : ) xdisp.c has > only 8 occurences of BYTE_POS_ADDR, that doesn't appear too bad. Why does it matter how many times BYTE_POS_ADDR is used? If you change the implementation of BYTE_POS_ADDR, the replacement is a mechanical job, no matter if there are 8 places or 800 to make the change.