Re: Question about test failure on Hydra

[Tino Calancha <tino.calancha@gmail.com>]

Tino Calancha <tino.calancha@gmail.com> writes:

> On Tue, 1 Aug 2017, Stephen Berman wrote:
>
>> On Tue, 01 Aug 2017 13:39:50 +0900 Tino Calancha <tino.calancha@gmail.com> wrote:
>>
>>> Stephen Berman <stephen.berman@gmx.net> writes:
>>>
>>>> On Mon, 31 Jul 2017 06:26:55 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>>>>
>>>> (dired test-dir) reverts an existing Dired buffer, because of setting
>>>> dired-auto-revert-buffer to t.  (When I step through the code, it is
>>>> after reverting that point moves to the subdirectory line, which the
>>>> should make "sanity check" true (and does, both when I step through the
>>>> code and just run the test in any way).  When I comment out the
>>>> dired-auto-revert-buffer line, then point stays at point-min, which
>>>> makes the sanity check fail (dired-file-name-at-point returns nil),
>>> When i comment out i see the point in point-max, and the test fails
>>> same as you but: (dired-file-name-at-point returns nil)
>>
>>>> though not in the way Hydra reports (it shows point being on the ".."
>>>> entry).)
>>> If somehow, we have in such Dired buffer the point at ".." _before_
>>> call `dired-revert', then _after_ revert the point is preserved:
>>
>> Yes, but the question is, how does point get there in Hydra?
I got the answer: because the Dired header line changed its size.
*) Before revert, it looks like:
"  total used in directory 8 available 37449484"
**) After revert, it changed to something like:
"  total used in directory 12 available 37449480"
;; 1 char longer: that mess up the saved position.
(See http://debbugs.gnu.org/27968).
> That's 1 million dollard question
I want my million bucks in a bag in the usual place; please, in small
bills.  No cops.