From: Glenn Morris <rgm@gnu.org>
To: 1208@emacsbugs.donarmstrong.com
Subject: bug#1208: overlay after-string and adjacent overlays with same string
Date: Sun, 19 Oct 2008 17:30:00 -0400 [thread overview]
Message-ID: <18683.42712.498573.238665@fencepost.gnu.org> (raw)
In-Reply-To: <E1IjVDL-00018n-0P@fencepost.gnu.org>
tags 1208 wontfix
stop
> BUG #2: An overlay's display property and after-string property are
> not displayed if an immediately following overlay shares the same Lisp
> string as its display property. (Using two distinct display strings
> with identical contents works around the bug.)
Tagging as wontfix based on the previous discussion:
http://lists.gnu.org/archive/html/bug-gnu-emacs/2008-02/msg00179.html
This occurs because, as stated in the Emacs Lisp manual, all
consecutive characters that have the same Lisp object as their
`display' property are replaced as a single unit. In this case, it's
somewhat ambiguous what the behavior should be, but after looking at
the code I think the behavior you suggest would be much more difficult
to implement (and slower) than the current behavior.
Furthermore, you can trivially obtain the behavior you want by making
a copy of the string using copy-sequence, so that the two display
strings are different Lisp objects.
Therefore, let's leave this alone.
next prev parent reply other threads:[~2008-10-19 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18683.41584.520431.671377@fencepost.gnu.org>
2007-10-21 7:27 ` Two more overlay display bugs Richard Stallman
2008-10-19 21:20 ` bug#1200: marked as done (Two more overlay display bugs) Emacs bug Tracking System
2008-10-19 21:30 ` Glenn Morris [this message]
2008-10-19 21:40 ` Processed: Re: bug#1208: overlay after-string and adjacent overlays with same string Emacs bug Tracking System
2008-10-24 19:10 ` bug#1201: marked as done (Another overlay display bug) Emacs bug Tracking System
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=18683.42712.498573.238665@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=1208@emacsbugs.donarmstrong.com \
/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.