unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, emacs-devel <emacs-devel@gnu.org>
Subject: Layered display API (was: bug#18195: 24.3.92; window-screen-lines is not accurate)
Date: Wed, 06 Aug 2014 16:40:37 +0400	[thread overview]
Message-ID: <53E22245.4070307@yandex.ru> (raw)
In-Reply-To: <83k36mpbxg.fsf@gnu.org>

On 08/06/2014 06:52 AM, Eli Zaretskii wrote:

 >> That sounds great, but I don't even know where to start. What we're
 >> trying to emulate, though, is multi-layered display. That sounds
 >> somewhat different from a "text layout API" to me.
 >
 > I don't mind how it is called and what is the correct abstraction.  I
 > do know that we need some abstraction and APIs to support it.  If you
 > already know what the correct abstraction is, then you are in a good
 > position to formulate the requirements.

I don't know much of the other use cases (only in-buffer calltips come 
to mind).

Basically, we'd like to be able to display a rectangle with propertized 
text inside, at an arbitrary position (I would say pixel coordinates, 
but that might not work well in terminal), so that it would be displayed 
above the buffer contents.

This would solve two issues we currently have:

1. If the buffer ends (shortly) after the current line, we're forced to 
pad it with a newline, and then carefully undo that and restore the 
buffer modification status.

2. If the buffer is already heavily using the `display' text property, 
or other similar ones, our tooltip positioning also breaks or works 
unexpectedly. Example: the `report-emacs-bug' buffer 
(https://github.com/company-mode/company-mode/issues/136).

Somewhat relatedely, I'd love to be able to sanely display smooth 
graphics spanning multiple lines in the fringe (or in the area that 
would replace it), to indicate the buffer lines that changed from the 
last VCS commit, without conflict with flymake-style warning/error 
indicators. Code folding packages might also use it to indicate the 
bounds of the function or block at point. Maybe even support buttons?

Here's an illustration from a proprietary editor: 
http://wiki.jetbrains.net/i/images/6/68/Git_general_branches_updated_code.png



       reply	other threads:[~2014-08-06 12:40 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           ` Dmitry Gutov [this message]
2014-08-06 17:19             ` Layered display API (was: bug#18195: 24.3.92; window-screen-lines is not accurate) 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
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=53E22245.4070307@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --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).