From: Nick Dokos <nicholas.dokos@hp.com>
To: Dave Abrahams <dave@boostpro.com>
Cc: emacs-orgmode@gnu.org, nicholas.dokos@hp.com,
Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Bug: void-function org-list-struct-fix-item-end [7.7 (release_7.7.396.g25c21)]
Date: Wed, 05 Oct 2011 14:06:48 -0400 [thread overview]
Message-ID: <27148.1317838008@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Dave Abrahams <dave@boostpro.com> of "Wed, 05 Oct 2011 13:31:24 EDT." <m2vcs31h1v.fsf@pluto.luannocracy.com>
Dave Abrahams <dave@boostpro.com> wrote:
> > I can't reproduce it.
>
> Me neither. But it happened, and I figured I'd better report it.
>
> >> Package: Org-mode version 7.7 (release_7.7.396.g25c21)
> >
> > This release doesn't exist yet. Latest is about
> > (release_7.7.349.g3d835).
> >
> > Could you make sure your Org is clean first, and then try to reproduce
> > the problem?
>
> Wouldn't make any difference, since I can't reproduce it at all.
>
> > Note: the function your Org can't find has been introduced quite
> > recently.
>
> It went away when I did `M-x load-library org-list' so I'm guessing
> there's some code path that fails to (require org-list) when needed.
>
More likely it was an artifact of how exactly you upgraded.
A possible scenario: after you pull, you do (load-library "org.el")
which picks up the new version of org.el. Now org.el requires org-list
but that does not mean that the new version of org-list gets loaded: all
that require does is check if the feature is a member of some list
(which it is, since you were using the feature before the pull). The new
org.el uses the org-list-struct-fix-item-end function, but the function
is not defined, since the old org-list.el is still in force. When you
(load-library "org-list.el") you get the new org-list.el with the
definition of the new function and everything is consistent. Also when
you restart, you get new versions of everything and everything is
consistent.
If you compile org, that creates even more ways that things can get
inconsistent.
Moral of the story: after you pull (and possibly ``make clean; make''),
do M-x org-reload, rather than loading individual files. Even so, if you
see strange things happening, restart your emacs -- or, at the very
least, start a new ``emacs -q -l minimal.emacs'' and test the
strangeness there: chances are that it won't happen, so you'd know you
are in some twisted maze like the one described above.
Nick
next prev parent reply other threads:[~2011-10-05 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 16:57 Bug: void-function org-list-struct-fix-item-end [7.7 (release_7.7.396.g25c21)] Dave Abrahams
2011-10-05 17:13 ` Nicolas Goaziou
2011-10-05 17:31 ` Dave Abrahams
2011-10-05 18:06 ` Nick Dokos [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-05 16:56 Dave Abrahams
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27148.1317838008@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=dave@boostpro.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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/org-mode.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).