Kenny Meyer <knny.m...@gmail.com> wrote:
> According to this discussion on the mailing list,
> http://comments.gmane.org/gmane.emacs.orgmode/48571 , this is a known
> bug.
>
> I fixed this by loading "org-compat" after requiring org-mode from
> git, just like Sebastian said.
>
I don't think it's a bug in org: if you start with a clean copy of the
repo (make clean; make) and have your load-path pointing there, you
should not see any problems.
IIUC, Michael Bach's problem (a fairly common one, btw) was that he was
mixing different installations: he was picking up a recent org-capture
that was using org-pop-to-buffer-same-window, but an older org-compat
that did not include the definition of that function.
You have to make sure that all of the pieces come from the same place,
but there is still a gotcha in the sense that an old .elc file will
be picked up by emacs in preference to a new .el file (possibly with
a warning, but who looks at warnings?)
Hence assuming you are using git to keep up to date:
make clean
make
C-h v load-path RET
[make sure that your load path points at your git directory *first*]
M-x org-reload RET
[or perhaps safer: restart emacs]
And use M-x locate-library to make sure that emacs agrees with you about
where things are picked up from.
Nick
> --
> Kenny Meyer
>
>
>
> On Thu, Dec 1, 2011 at 12:05 PM, Nick Dokos <nicholas.do...@hp.com> wrote:
> > Nick Dokos <nicholas.do...@hp.com> wrote:
> >
> >> Kenny Meyer <knny.m...@gmail.com> wrote:
> >>
> >> > I am getting the same message here upon calling various org-functions
> >> > (e.g.: org-drill, org-submit-bug-report), since I have compiled
> >> > org-mode from git, but I am not sure where exactly the error was
> >> > introduced.
> >> >
> >> > > Explicitly Loading `org-compat' does cure this problem...
> >> > Requiring org-compat does not fix that here.
> >> > Can you tell me where exactly you loaded org-compat?
> >> >
> >> > Org-mode version 7.7 (release_7.7.617.gb1f2)
> >> > GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.2.0) of
> >> > 2011-09-29
> >> >
> >> > --
> >> > Kenny Meyer
> >> >
> >>
> >> IIRC, the cure for macro problems like this is to
> >>
> >
> > Sorry - I thought it was a macro but it isn't. Nevertheless,
> > the note below still stands.
> >
> > Nick
> >
> >> make clean
> >> make
> >>
> >> (alternatively, make clean and just use uncompiled code). There might be
> >> something missing to cause it, but I don't think so in this case: I
> >> tried a minimal .emacs with the same version as above (Org-mode version
> >> 7.7 (release_7.7.617.gb1f2) and I can start, goto the active clock and
> >> stop it with no errors.
> >>
> >> Nick
> >>
> >>
> >> >
> >> >
> >> > On Thu, Dec 1, 2011 at 9:51 AM, Sebastien Vauban
> >> > <wxhgmqzgw...@spammotel.com> wrote:
> >> > > Hello,
> >> > >
> >> > > In conditions which I consider unchanged (I speak of my emacs config
> >> > > file),
> >> > > with the latest Org-mode version, I now have the message:
> >> > >
> >> > > let*: Symbol's function definition is void:
> >> > > org-pop-to-buffer-same-window
> >> > >
> >> > > when doing, for example, `C-c C-x C-j' to jump on the currently
> >> > > clocked item.
> >> > >
> >> > > Explicitly Loading `org-compat' does cure this problem... But we must
> >> > > miss a
> >> > > `require' somewhere, but where? In `org.el' itself?
> >> > >
> >> > > Best regards,
> >> > > Seb
> >> > >
> >> > > --
> >> > > Sebastien Vauban
> >> > >
> >> > >
> >> >
> >>
>
