From: E Sabof <esabof@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14636@debbugs.gnu.org
Subject: bug#14636: 24.3.50.1; window-line-height doesn't seem to work, unless the point is at the end-of-buffer
Date: Sun, 16 Jun 2013 18:19:06 +0100 [thread overview]
Message-ID: <CAEp6Dya=rHPOtQL0yLLFx7T_XX+Q=cTh_-7P+pn-+9o0kVO0JA@mail.gmail.com> (raw)
In-Reply-To: <83ehc2t2sp.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
> I have also tried
> >
> > (progn (pos-visible-in-window-p)
> > (window-line-height))
> >
> > but it didn't seem to make any difference.
>
> Why should it? Calling pos-visible-in-window-p does not guarantee
> that the window will be up-to-date, it just gives you the same
> information without requiring that the display be up-to-date. Its
> disadvantage is that it is slower.
>
You might be confusing posn-at-point (which returns the height of the
character amoung other things), with pos-visible-in-window-p, which returns
t or nil.
In any case, the height of the character can be different from the height
of the line, so they are not equivalent. So either a) the documentation is
incomplete and misleading, or b) there is a bug in the implementation
(which I think is more likely, given the arbitrary circumstances under
which this function does and doesn't work).
[-- Attachment #2: Type: text/html, Size: 1449 bytes --]
next prev parent reply other threads:[~2013-06-16 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 15:24 bug#14636: 24.3.50.1; window-line-height doesn't seem to work, unless the point is at the end-of-buffer E Sabof
2013-06-16 16:35 ` Eli Zaretskii
2013-06-16 16:44 ` E Sabof
2013-06-16 16:53 ` Eli Zaretskii
2013-06-16 17:19 ` E Sabof [this message]
2013-06-16 17:32 ` 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='CAEp6Dya=rHPOtQL0yLLFx7T_XX+Q=cTh_-7P+pn-+9o0kVO0JA@mail.gmail.com' \
--to=esabof@gmail.com \
--cc=14636@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).