unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <ghe@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Overlay behavior change
Date: Wed, 08 Jul 2020 19:25:40 +0300	[thread overview]
Message-ID: <83a70aq8hn.fsf@gnu.org> (raw)
In-Reply-To: <alpine.NEB.2.21.2007081710210394.7785@sdf.lonestar.org> (emacs-devel@gnu.org)

> Date: Wed, 8 Jul 2020 17:12:23 +0200 (CEST)
> From: Gregory Heytings via "Emacs development discussions." <emacs-devel@gnu.org>
> 
> What I would have liked to see is something that is neither the previous 
> nor the current default behavior.  This idea will probably not be 
> considered (let's name it the attribute ":visualblock t"), but here it is:
> 
> 1. calculate the overlay as it would have been displayed by Emacs 21 to 
> 26.
> 
> 2. remove all pixel columns on the right *and on the left* of the overlay 
> which have no "content" (that is, no characters on the right, whitespace 
> characters on the left).
> 
> This way the block (of code) would really be displayed on the screen as a 
> block, even a deeply nested one.  The above "algorithm" would work with 
> fixed and variable-width fonts, but could of course be made more efficient 
> for fixed-width fonts.

Feel free to submit a feature-request bug report about this.



      reply	other threads:[~2020-07-08 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08  8:14 Overlay behavior change Gregory Heytings via Emacs development discussions.
2020-07-08  8:48 ` Eli Zaretskii
2020-07-08  9:14   ` Gregory Heytings via Emacs development discussions.
2020-07-08 14:26     ` Eli Zaretskii
2020-07-08 15:12       ` Gregory Heytings via Emacs development discussions.
2020-07-08 16:25         ` Eli Zaretskii [this message]

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=83a70aq8hn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ghe@sdf.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 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).