From: Eli Zaretskii <eliz@gnu.org>
To: Bo Lin <bo@dreamsphere.org>
Cc: rudalics@gmx.at, dgutov@yandex.ru, emacs-devel@gnu.org
Subject: Re: Layered display API
Date: Thu, 14 Aug 2014 19:19:32 +0300 [thread overview]
Message-ID: <83zjf7gi23.fsf@gnu.org> (raw)
In-Reply-To: <87vbpv9hqj.fsf@dreamsphere.org>
> From: Bo Lin <bo@dreamsphere.org>
> Cc: rudalics@gmx.at, emacs-devel@gnu.org, dgutov@yandex.ru
> Date: Thu, 14 Aug 2014 12:08:20 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> >> > What I meant is this: if you need to display below the last line of
> >> >> > the buffer text, put the overlay at EOB, and include newlines in the
> >> >> > overlay string when you need to move to the next screen line. To
> >> >> > align text horizontally you could use spaces or align-to display
> >> >> > properties in the string.
> >> >>
> >> >> Yes, I might try this, as soon as there's some suggestion how to handle
> >> >> the problem of `line-prefix' in this multi-overlay approach.
> >> >
> >> > Find the longest prefix and align everything so that the left edge
> >> > keeps clear of that?
> >>
> >> Zero length overlays don't get displayed so this won't work when the
> >> buffer is empty.
> >
> > When a buffer is empty, there are no line prefixes, right? Or did I
> > misunderstand what you eman?
>
> I thought this was about avoid padding the buffer text with
> newlines?
Sorry, it wasn't clear, as the previous citations talked about both.
So turning to the padding the buffer: it's not about padding with
newlines, it's about including newlines in overlay string. After the
newline, the overlay string would have the text to be displayed beyond
the EOB.
next prev parent reply other threads:[~2014-08-14 16:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86tx5r7l1j.fsf@yandex.ru>
[not found] ` <53E097F7.5050407@gmx.at>
[not found] ` <53E0ABF9.7070506@yandex.ru>
[not found] ` <8338dbqcai.fsf@gnu.org>
[not found] ` <53E14AF4.6050804@yandex.ru>
[not found] ` <83k36mpbxg.fsf@gnu.org>
2014-08-06 12:40 ` Layered display API (was: bug#18195: 24.3.92; window-screen-lines is not accurate) Dmitry Gutov
2014-08-06 17:19 ` Eli Zaretskii
2014-08-06 18:20 ` Alp Aker
2014-08-06 18:39 ` Eli Zaretskii
2014-08-06 20:48 ` Layered display API Stefan Monnier
2014-08-07 2:45 ` Eli Zaretskii
2014-08-06 20:49 ` Dmitry Gutov
2014-08-07 15:39 ` Eli Zaretskii
2014-08-11 1:14 ` Dmitry Gutov
2014-08-11 15:01 ` Eli Zaretskii
2014-08-13 2:42 ` Dmitry Gutov
2014-08-13 12:46 ` Stefan Monnier
2014-08-13 15:29 ` Eli Zaretskii
2014-08-13 16:27 ` Dmitry Gutov
2014-08-13 17:07 ` Eli Zaretskii
2014-08-13 17:45 ` Stefan Monnier
2014-08-13 15:28 ` Eli Zaretskii
2014-08-14 2:35 ` Dmitry Gutov
2014-08-14 2:53 ` Eli Zaretskii
2014-08-14 13:12 ` Dmitry Gutov
2014-08-14 15:20 ` Eli Zaretskii
2014-08-15 1:20 ` Dmitry Gutov
2014-08-15 6:39 ` Eli Zaretskii
2014-08-15 23:03 ` Dmitry Gutov
2014-08-16 7:41 ` Eli Zaretskii
2014-08-16 9:17 ` Dmitry Gutov
2014-08-14 2:06 ` Bo Lin
2014-08-14 2:49 ` Eli Zaretskii
2014-08-14 16:08 ` Bo Lin
2014-08-14 16:19 ` Eli Zaretskii [this message]
2014-08-14 16:42 ` Bo Lin
2014-08-06 20:56 ` 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=83zjf7gi23.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bo@dreamsphere.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).