From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Philipp Stephani
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Wed, 14 Sep 2016 18:43:13 +0000
> Cc: 21730@debbugs.gnu.org, mwd@md5i.com
>
>=C2=A0 Since the problem that caused the patch to be reverted was with<= br class=3D"gmail_msg"> >=C2=A0 narrowing, why not simply use
>
>=C2=A0 (=3D point (with-current-buffer (window-buffer window) (point-mi= n)))
>
>=C2=A0 instead of
>
>=C2=A0 (=3D point 1)
>
>=C2=A0 ?
>
> This has the same issues as described above. There's more code in = cursor-sensor--detect that assumes (eq
> (current-buffer) (window-buffer window)), e.g. the form (get-char-prop= erty point 'cursor-sensor-functions).
> Therefore (=3D point (with-current-buffer (window-buffer window) (poin= t-min))) must be the same as (bobp).
> Another mystery is the stack trace entry "run-hook-with-args(curs= or-sensor--detect #<window 224 on
> *Group*>)". How can cursor-sensor--detect be the first argumen= t to run-hook-with-args? Shouldn't it always
> be pre-redisplay-functions?
If we want to dig deeper, I think we should first understand why bop
doesn't work.=C2=A0 Is it indeed because the window's buffer is not= the
current buffer when the hook is called?