Keith David Bershatsky e...@lawlist.com writes:
Yes, `(setq-default cache-long-scans nil)` does indeed fix the
problem.
Great. As I said I must give up here, because I don't know what to do at
this point ; but I can dig further if someone tells me what I'm looking
for, or what is to be done.
Date: Tue, 31 Dec 2013 09:37:15 -0800
From: Keith David Bershatsky e...@lawlist.com
Cc: 16...@debbugs.gnu.org
So my recommendation would be that the Emacs team return the default value of
`cache-long-scans` to `nil`
Unlikely to happen.
or, fix it somehow so that it doesn't interfere
Yes, the issue has indeed been resolved in the latest version of Emacs Trunk
that I built today. I used my example to conduct the test, and it works now
with `cache-long-scans` enabled.
Great job -- thank you Eli, and thanks again Nicolas!
Keith
Date: Wed, 01 Jan 2014 17:30:12 -0800
From: Keith David Bershatsky e...@lawlist.com
Cc: theonewiththeevill...@yahoo.fr, 16...@debbugs.gnu.org
Yes, the issue has indeed been resolved in the latest version of Emacs Trunk
that I built today. I used my example to conduct the test, and it
Le 28/12/2013 21:44, Keith David Bershatsky a écrit :
This example demonstrates the problem caused when `org-capture`
damages the line numbers in the `org-agenda-files`, making it
impossible to go to the bottom of the buffer with (goto-char
(point-max)) -- consequently, re-search-backward
Nicolas Richard theonewiththeevill...@yahoo.fr writes:
I'll bisect this (I tested 24.3, it works there) and post the result
bisection is done.
# first bad commit: [f56f1e3993fd79240e03666cf8390f489b4a2435] Switch
cache-long-scans to t by default.
and indeed, running
emacs -Q --batch --eval
Nicolas:
Yes, `(setq-default cache-long-scans nil)` does indeed fix the problem. In a
version of Emacs Trunk built on October 5, 2013, the default value for
`cache-long-scans` is `nil`. In the recent version of Emacs Trunk built on
December 23, 2013, the default value for `cache-long-scans`
Nicolas:
This example demonstrates the problem caused when `org-capture` damages the
line numbers in the `org-agenda-files`, making it impossible to go to the
bottom of the buffer with (goto-char (point-max)) -- consequently,
re-search-backward fails -- other functions fail also, e.g.,
