From: ynyaaa@gmail.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25824@debbugs.gnu.org
Subject: bug#25824: 25.1; bugs about display specfications
Date: Fri, 24 Feb 2017 15:01:19 +0900 [thread overview]
Message-ID: <87bmtsnn4g.fsf@gmail.com> (raw)
In-Reply-To: <834lzkucq5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 Feb 2017 17:51:46 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Only if the replacement comes from a before- or after-string (in which
> case the text won't be replaced, so you will have to hide it with some
> invisible property). Put the 'raise' display property on the overlay
> string, and you will have what you want.
Overlays are not editable with kill and yank,
so text properties are better.
> What the display engine does is reserve space above
> the baseline that is large enough for the enlarged font, and then draw
> the "X" with a negative offset relative to the baseline, by enlarging
> the 'descent' value of that particular glyph, which adds vertical
> space _below_ the line.
I wonder why the display engine does not take 'rase' into account
when reserving space above the baseline.
> Does the below do what you want? If not, perhaps I don't understand
> what you mean by "centered".
>
> (insert "A" (propertize "X" 'display '((raise -0.2) (height 2))))
It is enough for only one line.
With blank areas, emacs can display fewer lines.
For example in my environment, the form below displays 9 lines.
(insert (propertize "1\n2\n3\n4\n5\n6\n7\n8\n9\n"
'display '(height 5)))
And the form below displays 7 lines.
(insert (propertize "1\n2\n3\n4\n5\n6\n7\n8\n9\n"
'display '((raise -1.3) (height 5))))
next prev parent reply other threads:[~2017-02-24 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 4:17 bug#25824: 25.1; bugs about display specfications ynyaaa
2017-02-21 17:37 ` Eli Zaretskii
2017-02-23 2:53 ` ynyaaa
2017-02-23 15:51 ` Eli Zaretskii
2017-02-24 6:01 ` ynyaaa [this message]
2017-02-24 8:23 ` Eli Zaretskii
2017-03-04 16:00 ` Eli Zaretskii
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=87bmtsnn4g.fsf@gmail.com \
--to=ynyaaa@gmail.com \
--cc=25824@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 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).