From: Phillip Lord <phillip.lord@russet.org.uk>
To: Ken Brown <kbrown@cornell.edu>
Cc: 23446@debbugs.gnu.org
Subject: bug#23446: 25.0.93; cursor-sensor-inhibit
Date: Wed, 04 May 2016 23:50:22 +0100 [thread overview]
Message-ID: <87eg9h4evl.fsf@russet.org.uk> (raw)
In-Reply-To: <ed2795aa-703c-f250-5976-a11bf9339d2d@cornell.edu> (Ken Brown's message of "Wed, 4 May 2016 18:00:06 -0400")
Ken Brown <kbrown@cornell.edu> writes:
> On 5/4/2016 5:21 PM, Phillip Lord wrote:
>> Ken Brown <kbrown@cornell.edu> writes:
>>>>> On 5/4/2016 8:58 AM, Phillip Lord wrote:
>> So, this looks like up a failure during updating rather than anything
>> else.
>
> No, what happened is that the autoloads files got out of date and needed to be
> regenerated by 'make -C lisp autoloads', as I said in my first reply. This
> happens from time to time and is documented in INSTALL.REPO. It works
> perfectly well in an out-of-source build. If you delete your build directory,
> however, then you've thrown away your Makefile, and it's too late.
>
> The only reason you aren't bitten by this more often is that Glenn
> periodically updates the autoloads. See, for example, his commit 3cade20.
Yes, I checked the autoload commits and cursor-sensor-inhibit has been
added to ldefs-boot.el in that commit. I couldn't work out why that
would cause this form of error though (it should prevent it).
The actual cause is b755d988b498b19bd which added the autoload cookie,
and 16e5e8e4ea4a which removed the a (setq cursor-sensor-inhibit nil)
form. So, yes, autoloads out of date, and me being confused about my
build state.
Will close.
Phil
next prev parent reply other threads:[~2016-05-04 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 12:58 bug#23446: 25.0.93; cursor-sensor-inhibit Phillip Lord
2016-05-04 13:45 ` Ken Brown
2016-05-04 16:37 ` Phillip Lord
2016-05-04 18:14 ` Ken Brown
2016-05-04 21:21 ` Phillip Lord
2016-05-04 22:00 ` Ken Brown
2016-05-04 22:50 ` Phillip Lord [this message]
2016-05-04 22:10 ` Glenn Morris
2016-05-04 22:51 ` Phillip Lord
2016-05-05 7:07 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg9h4evl.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=23446@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).