From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18285@debbugs.gnu.org
Subject: bug#18285: 24.3.92; A combination of `display' on text and `invisible' and `before/after-string' leads to the before/after string being displayed twice
Date: Sat, 23 Aug 2014 00:01:59 +0400 [thread overview]
Message-ID: <53F7A1B7.2080607@yandex.ru> (raw)
In-Reply-To: <83sikomz1a.fsf@gnu.org>
On 08/22/2014 05:31 PM, Eli Zaretskii wrote:
> If that's what people want, it's an easy change.
Can't say for all people, but it seems like a good idea to me.
> But the question is,
> won't that cause overlay strings not to be displayed in some cases?
The reverse, maybe? Making `invisible' inactive means something might
become visible, right? But I'd have to see some examples.
>> If `display' takes priority over `invisible', I would expect
>>
>> (let ((pt (point)))
>> (insert (propertize "a" 'display "bbb"))
>> (let ((o (make-overlay pt (point))))
>> (overlay-put o 'after-string "foo\nbar")))
>>
>> and
>>
>> (let ((pt (point)))
>> (insert (propertize "a" 'display "bbb"))
>> (let ((o (make-overlay pt (point))))
>> (overlay-put o 'invisible t)
>> (overlay-put o 'after-string "foo\nbar")))
>>
>> to be rendered the same.
>
> The question is what would you expect from the second example, if it
> used before-string there? Should the before-string be displayed or
> shouldn't it? Since invisible makes the beginning of the overlay
> disappear, under your suggestion it won't be displayed.
I think I'm suggesting the reverse, no? And anyway, with the current
logic, both examples render the `before-string' if I use it there just
fine. I see no reason for that that to change.
next prev parent reply other threads:[~2014-08-22 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 22:35 bug#18285: 24.3.92; A combination of `display' on text and `invisible' and `before/after-string' leads to the before/after string being displayed twice Dmitry
[not found] ` <handler.18285.B.140831493931056.ack@debbugs.gnu.org>
2014-08-18 1:06 ` bug#18285: Acknowledgement (24.3.92; A combination of `display' on text and `invisible' and `before/after-string' leads to the before/after string being displayed twice) Dmitry Gutov
2014-08-18 15:07 ` bug#18285: 24.3.92; A combination of `display' on text and `invisible' and `before/after-string' leads to the before/after string being displayed twice Eli Zaretskii
2014-08-21 14:07 ` Dmitry Gutov
2014-08-21 14:57 ` Eli Zaretskii
2014-08-21 15:40 ` Dmitry Gutov
2014-08-21 16:06 ` Eli Zaretskii
2014-08-22 0:58 ` Dmitry Gutov
2014-08-22 6:41 ` Eli Zaretskii
2014-08-22 11:41 ` Dmitry Gutov
2014-08-22 13:31 ` Eli Zaretskii
2014-08-22 20:01 ` Dmitry Gutov [this message]
2014-08-22 20:55 ` Eli Zaretskii
2014-08-24 1:28 ` Dmitry Gutov
2014-08-24 2:44 ` Eli Zaretskii
2014-08-23 23:21 ` Dmitry Gutov
2014-08-24 2:40 ` Eli Zaretskii
2014-08-24 2:48 ` Dmitry Gutov
2022-04-18 11:39 ` Lars Ingebrigtsen
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=53F7A1B7.2080607@yandex.ru \
--to=dgutov@yandex.ru \
--cc=18285@debbugs.gnu.org \
--cc=eliz@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.