From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
rms@gnu.org, galex-713@galex-713.eu, emacs-devel@gnu.org
Subject: Re: Future of display engine and lines
Date: Sun, 24 Oct 2021 13:17:10 +0000 [thread overview]
Message-ID: <YXVc1iqKIOBaZ4Am@ACM> (raw)
In-Reply-To: <87a6iybntc.fsf@gnus.org>
Hello, Lars.
On Sun, Oct 24, 2021 at 14:38:07 +0200, Lars Ingebrigtsen wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> > Perhaps I misunderstand what "multiple columns" mean, then. Doesn't
> > it mean that buffer text is displayed in separate rectangular
> > portions, like this:
> > aaaaaaaaaaaa bbbbbbbb ccccccc xxx xxxxxxxx xxxxxxxxxxxx
> > dddddddd eeeeeeee fffffff ggg yyyyyy yyyyyyyyy yyyyyyyy
> > hhhhhhhh iiiiiiiiii jjjj kkkk zzzzzzzzz zzzzzzzzzz zzzz
> > where buffer position of the first "xxx" follows the buffer position
> > of the last "kkkk"?
> Well, it depends. Perhaps these the next point after "xxx" is before
> "where". Or perhaps if you enter more text after "kkk", that box should
> get a scroll bar, or perhaps it should extend downwards.
> We're basically in the same design territory that HTML + CSS 3 covers,
> and It's Just Very Difficult. And as you say, the main problem isn't
> displaying the glyphs on the screen -- but it's defining the semantics
> about how the blocks interoperate, and making a command like `M-q' do
> something sensible within a block.
Err, aren't we talking about Follow Mode, here? Follow Mode has been
around for a year or two now, and works very well (apart from the fact
there are no standard key bindings to enable it in 1/2/3 columns, or
disable it). The semantics of the interoperating windows is indeed
somewhat involved, and unfortunately also somewhat slow, since
follow-mode is fighting the display engine over what goes where.
> Within the current Emacs structure, it would have to look like a bunch
> of buffers that we glue together as sub-panes inside one window, where
> your example ("xxx" follows "kkkk") would be as two sub-panes from one
> of these sub-buffers, and where the second sub-pane displays the text
> after line 3, with the layout in question.
> I mean... it'd be great, but I think we're basically talking about a
> different editor.
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-10-24 13:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 13:27 Future of display engine and lines Alexandre Garreau
2021-10-21 3:16 ` Lars Ingebrigtsen
2021-10-22 23:47 ` Richard Stallman
2021-10-23 7:10 ` Eli Zaretskii
2021-10-24 12:38 ` Lars Ingebrigtsen
2021-10-24 13:17 ` Alan Mackenzie [this message]
2021-10-25 2:18 ` Richard Stallman
2021-10-25 12:05 ` Eli Zaretskii
2021-10-25 12:20 ` Alexandre Garreau
2021-10-25 12:50 ` Eli Zaretskii
2021-10-25 13:01 ` Alexandre Garreau
2021-10-28 12:19 ` Richard Stallman
2021-10-28 12:19 ` Richard Stallman
2021-10-28 13:19 ` Eli Zaretskii
2021-10-28 15:03 ` Alexandre Garreau
2021-11-09 23:13 ` chad
2021-11-10 19:24 ` Eli Zaretskii
2021-11-13 4:08 ` Richard Stallman
2021-10-23 10:32 ` Alexandre Garreau
2021-10-21 22:43 ` Richard Stallman
2021-10-22 11:56 ` Alexandre Garreau
2021-10-22 12:45 ` Eli Zaretskii
2021-10-23 13:55 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YXVc1iqKIOBaZ4Am@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=galex-713@galex-713.eu \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.