From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: (pos-visible-in-window-p t nil t) returns wrong position/is suboptimally documented.
Date: Sun, 27 Sep 2015 14:06:35 +0300 [thread overview]
Message-ID: <8337y0f7es.fsf@gnu.org> (raw)
In-Reply-To: <20150927104041.GA2401@acm.fritz.box>
> Date: Sun, 27 Sep 2015 10:40:41 +0000
> From: Alan Mackenzie <acm@muc.de>
>
> Which is correct? The function or the documentation?
The function. This has always worked like that.
next prev parent reply other threads:[~2015-09-27 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 10:40 (pos-visible-in-window-p t nil t) returns wrong position/is suboptimally documented Alan Mackenzie
2015-09-27 11:06 ` Eli Zaretskii [this message]
2015-09-30 7:21 ` Eli Zaretskii
2015-09-30 8:56 ` Alan Mackenzie
2015-09-30 9:32 ` Eli Zaretskii
2015-09-30 10:22 ` Alan Mackenzie
2015-09-30 13:52 ` Eli Zaretskii
2015-09-30 14:05 ` Alan Mackenzie
2015-10-01 7:36 ` 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=8337y0f7es.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--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).