From: Eli Zaretskii <eliz@gnu.org>
To: dalanicolai <dalanicolai@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Redisplay issues with 'space' display properties on overlays
Date: Sat, 16 Apr 2022 22:02:43 +0300 [thread overview]
Message-ID: <83h76szwa4.fsf@gnu.org> (raw)
In-Reply-To: <CACJP=3=5kZUob1zBErkAK7rd=129PRDuhOdVf6uZshd+fxumog@mail.gmail.com> (message from dalanicolai on Sat, 16 Apr 2022 20:40:47 +0200)
> From: dalanicolai <dalanicolai@gmail.com>
> Date: Sat, 16 Apr 2022 20:40:47 +0200
> Cc: Emacs Devel <emacs-devel@gnu.org>
>
> 2. I would expect that a specified space (space display property for the 'gap'
> > overlays, i.e. the space between the pages) could be smaller than the default
> > 'line-pixel-height`. However, this does not seem possible by just setting a
> > smaller :height for the space display property, as the overlay will always have
> > a minimum height of the default 'line-pixel-height'
>
> Here is again my 'second question'. So after when you do `M-x papyrus-demo`
> (and scroll using the arrows) the 'gaps', which are the gray 'gaps' between the pages,
> have the height of the default `pixel-line-height`. Setting `papyrus-gap-height` larger
> will increase the gap size. However, setting `papyrus-gap-height` smaller will not
> decrease the gap size because it seems that the `line-pixel-height` is the minimum.
> I would expect the size could be smaller, so my question is why the minimum size is
> limited to be `line-pixel-height`...
I think this is because you have a newline after the overlay, and the
newline has the default height. Did you try to put a face with
smaller :height on the newline?
next prev parent reply other threads:[~2022-04-16 19:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 16:37 papyrus.el, improved/simplified/"final" implementation of continuous scroll dalanicolai
2022-04-16 16:46 ` Eli Zaretskii
2022-04-16 19:00 ` dalanicolai
2022-04-16 16:49 ` Redisplay issues with 'space' display properties on overlays Eli Zaretskii
2022-04-16 18:17 ` dalanicolai
2022-04-16 18:32 ` Eli Zaretskii
2022-04-16 18:40 ` dalanicolai
2022-04-16 19:02 ` Eli Zaretskii [this message]
2022-04-16 18:47 ` dalanicolai
2022-04-16 18:57 ` dalanicolai
2022-04-16 19:06 ` Eli Zaretskii
2022-04-16 19:16 ` dalanicolai
2022-04-16 19:18 ` Eli Zaretskii
2022-04-16 19:33 ` dalanicolai
2022-04-16 19:52 ` dalanicolai
2022-04-16 21:39 ` dalanicolai
2022-04-16 19:36 ` dalanicolai
2022-04-16 18:32 ` dalanicolai
2022-04-16 18:36 ` Eli Zaretskii
2022-04-16 18:38 ` Eli Zaretskii
2022-04-16 18:49 ` dalanicolai
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=83h76szwa4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dalanicolai@gmail.com \
--cc=emacs-devel@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).