Bastien writes:
> Nicolas Richard writes:
>
>> Bastien writes:
>>> PS: The change about throwing an error when recentering a window
>>> that does not display the current buffer breaks ~37 tests in Org
>>> master branch, even with this fix. I need to digg this further.
>>
>> For me, fixing also
> From: Stefan Monnier
> Cc: Bastien , theonewiththeevill...@yahoo.fr,
> 17...@debbugs.gnu.org, dogriffi...@gmail.com
> Date: Wed, 11 Jun 2014 14:15:08 -0400
>
> > Say thanks to Stefan for flagging all those bugs ;-)
>
> Now that I think about it, I should make `car' signal an error every
> 100
> Say thanks to Stefan for flagging all those bugs ;-)
Now that I think about it, I should make `car' signal an error every
100th call, as well. Would flag many bugs (with some false positives,
of course, but what's a few false positives among friends?)!
Stefan
> From: Bastien
> Date: Wed, 11 Jun 2014 17:50:02 +0200
> Cc: 17...@debbugs.gnu.org, David Griffiths
>
> PS: The change about throwing an error when recentering a window
> that does not display the current buffer breaks ~37 tests in Org
> master branch, even with this fix. I need to digg this f
Nicolas Richard writes:
> Bastien writes:
>> PS: The change about throwing an error when recentering a window
>> that does not display the current buffer breaks ~37 tests in Org
>> master branch, even with this fix. I need to digg this further.
>
> For me, fixing also org-fix-ellipsis-at-bol ma
Bastien writes:
> PS: The change about throwing an error when recentering a window
> that does not display the current buffer breaks ~37 tests in Org
> master branch, even with this fix. I need to digg this further.
For me, fixing also org-fix-ellipsis-at-bol made all tests run as
expected.
--
Nicolas Richard writes:
> David Griffiths writes:
>> Debugger entered--Lisp error: (error "`recenter'ing a window that does
>> not display current-buffer.")
>> recenter((4))
>> org-overview()
>
> So that's a duplicate of #17724. It is fixed in org-mode (upstream) master
> branch. The easy fix is
