Subject: Re: bug#22757: 25.1.50; `face-at-point` and `faces--attribute-at-point` -- add argument WINDOW-OR-BUFFER

From: Eli Zaretskii <[email-masked]>
Date: Sun, 21 Feb 2016 22:54:07 +0200

> Date: Sun, 21 Feb 2016 10:05:33 -0800
> From: Keith David Bershatsky <[email-masked]>
> 
> As a feature request, please consider adding an additional argument to `face-at-point` and `faces--attribute-at-point` to support WINDOW-OR-BUFFER with `get-char-property`; and, add that to the sections of code in said functions containing `get-char-property`.  The doc-strings would need to be updated to explain the difference.  The default would be BUFFER.
> 
> It is sometimes useful to be able to obtain a face of an overlay that is associated with a particular window -- e.g., an active region that may be different in each window.  The current functions do not have the ability to test for that occurrence because the third argument of `get-char-property` is always `nil`.

Why can't you call get-char-property directly?  face-at-point is
nothing more than a thin wrapper around get-char-property, and most of
the wrapper code is about stuff you don't care about AFAIU from your
description.

Is there something I'm missing?

Thanks.