auto-fill non-op, fill-paragraph error

auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

The last several weeks or so I've noticed that auto-fill isn't working
and when I try to invoke fill-paragraph I receive the following error:

org-element-map: Symbol's function definition is void: org-element--parse-objects

I've been tied up in the middle of a system migration at work, so I'd
figured that the problem would surface elsewhere and eventually go away
but now maybe it's something I'm doing?

Also, fill-paragraph works fine in gnus. That's about all I know.

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Hi Edward,

Edward DeMeulle <ed@demeulle.org> writes:

> org-element-map: Symbol's function definition is void:
> org-element--parse-objects

Please let us know what version of Org you are using.

Errors in this area have been showing up in some versions,
but AFAIK they have been fixed.

-- 
 Bastien

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

I'm on 7.9.1. I've been pulling from the repository every once in a
while.

Re: auto-fill non-op, fill-paragraph error

[modeless]

Edward DeMeulle <ed <at> demeulle.org> writes:

> 
> I'm on 7.9.1. I've been pulling from the repository every once in a
> while.

Hi,

I'm as well facing the org-fill-paragraph problems in 7.9.1. I'm on the [maint] 
branch.

Kind regards,
Jörn

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Hi,

modeless <modeless@modeless.de> writes:

> I'm as well facing the org-fill-paragraph problems in 7.9.1. I'm on the [maint] 
> branch.

What is the value returned by

M-x org-version RET

?

-- 
 Bastien

Re: auto-fill non-op, fill-paragraph error

[Jörn Gersdorf]

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

Hi Bastien,

thank you - the bug is resolved as of release_7.9.1-337-g4512f8.

Best regards,
Jörn

On Tue, Sep 25, 2012 at 3:32 PM, Bastien <bzg@gnu.org> wrote:

> Hi Jörn,
>
> Jörn Gersdorf <modeless@modeless.de> writes:
>
> > No problem, I see that it's quite interesting after the "@" ;-) since
> > I'm running emacs under cygwin
> >
> > Org-mode version 7.9.1 (release_7.9.1-62-gb61ff1 @ /c/Documents and
> > Settings/myself/My Documents/.emacs.d/vendor/org-mode/lisp/)
>
> Okay -- it's now 337 commits *after* 7.9.1 so maybe this has been fixed
> since commit 62 after 7.9.1.
>
> ("release_7.9.1-62-gb61ff1" say you are on commit 62 after 7.9.1.)
>
> Please pull again and let us know.
>
> Also please reply to the whole mailing list, this can be useful to
> others.
>
> Thanks,
>
> --
>  Bastien
>

[-- Attachment #2: Type: text/html, Size: 1361 bytes --]

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

Unfortunately, I am still experiencing the problem with
release_7.9.1-382-g1a1d06-git. Is there any information I can provide to
help?

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Hi Edward,

Edward DeMeulle <ed@demeulle.org> writes:

> Unfortunately, I am still experiencing the problem with
> release_7.9.1-382-g1a1d06-git. Is there any information I can provide to
> help?

Please do C-u M-x org-version RET -- this will insert the complete
Org version in your email (assuming you are using Gnus.)

Chances are that you didn't compile Org correctly.

See http://orgmode.org/worg/dev/org-build-system.html for details.

Best,

-- 
 Bastien

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

Org-mode version 7.9.1 (release_7.9.1-382-g1a1d06-git @/home/ewd/.emacs.d/org-mode/lisp/)

I'd been simply running it from sources but will try compiling it.

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

I ran 'make up2' and received the following (I'm still on emacs23)

...
Compiling /home/ewd/.emacs.d/org-mode/lisp/org.el...

In org-store-link:
org.el:8999:23:Warning: `org-link-to-org-use-id' is an obsolete variable (as
    of Emacs 24.3); use `org-id-link-to-org-use-id' instead.
org.el:9001:32:Warning: `org-link-to-org-use-id' is an obsolete variable (as
    of Emacs 24.3); use `org-id-link-to-org-use-id' instead.
org.el:9002:37:Warning: `org-link-to-org-use-id' is an obsolete variable (as
    of Emacs 24.3); use `org-id-link-to-org-use-id' instead.
org.el:9005:24:Warning: `org-link-to-org-use-id' is an obsolete variable (as
    of Emacs 24.3); use `org-id-link-to-org-use-id' instead.

In org-deadline-close:
org.el:16039:12:Warning: `org-days-to-time' is an obsolete function (as of
    Emacs 24.3); use `org-time-stamp-to-now' instead.
Wrote /home/ewd/.emacs.d/org-mode/lisp/org.elc
Done (Total of 110 files compiled, 2 skipped)
make[2]: Leaving directory `/home/ewd/.emacs.d/org-mode/lisp'
make[1]: Leaving directory `/home/ewd/.emacs.d/org-mode/lisp'
install -m 755 -d /tmp/tmp-orgtest
TMPDIR=/tmp/tmp-orgtest emacs -batch -Q  --eval '(add-to-list '"'"'load-path "./lisp")' --eval '(add-to-list '"'"'load-path "./testing")'  -l org-install.el -l testing/org-test.el --eval '(require '"'"'ob-awk)' --eval '(require '"'"'ob-C)' --eval '(require '"'"'ob-fortran)' --eval '(require '"'"'ob-maxima)' --eval '(require '"'"'ob-lilypond)' --eval '(require '"'"'ob-octave)' --eval '(require '"'"'ob-python)' --eval '(require '"'"'ob-sh)'  --eval '(setq org-confirm-babel-evaluate nil)' -f org-test-run-batch-tests
Cannot open load file: ert
make: *** [test] Error 255

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Edward DeMeulle <ed@demeulle.org> writes:

> I ran 'make up2' and received the following (I'm still on emacs23)

Please use `make update2'

`make up2' runs the test suite but you don't have the ert package
installed. 

-- 
 Bastien

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

Ok. Ran 'make update2', which completed w/o errors. Still running into error:

org-fill-paragraph: Symbol's function definition is void: org-element--parse-objects

Org-mode version 7.9.1 (release_7.9.1-396-g5ba6bd @ /home/ewd/.emacs.d/org-mode/lisp/)

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Edward DeMeulle <ed@demeulle.org> writes:

> org-fill-paragraph: Symbol's function definition is void:
> org-element--parse-objects
>
> Org-mode version 7.9.1 (release_7.9.1-396-g5ba6bd @
> /home/ewd/.emacs.d/org-mode/lisp/)

Can you give the output of

C-h f org-element-parse-buffer RET

C-h f org-fill-paragraph RET

?

-- 
 Bastien

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

org-element-parse-buffer is a Lisp function in `org-element.el'.

(org-element-parse-buffer &optional GRANULARITY VISIBLE-ONLY)

Recursively parse the buffer and return structure.
If narrowing is in effect, only parse the visible part of the
buffer.

Optional argument GRANULARITY determines the depth of the
recursion.  It can be set to the following symbols:

`headline'          Only parse headlines.
`greater-element'   Don't recurse into greater elements excepted
		    headlines and sections.  Thus, elements
		    parsed are the top-level ones.
`element'           Parse everything but objects and plain text.
`object'            Parse the complete buffer (default).

When VISIBLE-ONLY is non-nil, don't parse contents of hidden
elements.

Assume buffer is in Org mode.

--- 

org-fill-paragraph is an interactive compiled Lisp function in
`org.el'.

(org-fill-paragraph &optional JUSTIFY)

Fill element at point, when applicable.

This function only applies to comment blocks, comments, example
blocks and paragraphs.  Also, as a special case, re-align table
when point is at one.

If JUSTIFY is non-nil (interactively, with prefix argument),
justify as well.  If `sentence-end-double-space' is non-nil, then
period followed by one space does not end a sentence, so don't
break a line there.  The variable `fill-column' controls the
width for filling.

For convenience, when point is at a plain list, an item or
a footnote definition, try to fill the first paragraph within.

[back]

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Hi Edward,

Edward DeMeulle <ed@demeulle.org> writes:

> org-element-parse-buffer is a Lisp function in `org-element.el'.
>
> org-fill-paragraph is an interactive compiled Lisp function in
> `org.el'.

Sorry, I should have mentioned that I interested in the absolute 
path org-element.el and org.el here.  Could you send this?

But it's already good that the first function is defined.

-- 
 Bastien

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

locate shows org-element.el here:
/home/ewd/.emacs.d/org-mode/contrib/lisp/org-element.el
/home/ewd/.emacs.d/org-mode/lisp/org-element.el
/home/ewd/.emacs.d/org-mode/lisp/org-element.elc
/usr/share/emacs/site-lisp/org/org-element.el
/usr/share/emacs/site-lisp/org/org-element.elc

org.el:
/home/ewd/.emacs.d/org-mode/lisp/org.el
/home/ewd/.emacs.d/org-mode/lisp/org.elc
/usr/share/emacs/23.3/lisp/org/org.elc
/usr/share/emacs/site-lisp/org/org.el
/usr/share/emacs/site-lisp/org/org.elc

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Edward DeMeulle <ed@demeulle.org> writes:

> locate shows org-element.el here:
> /home/ewd/.emacs.d/org-mode/contrib/lisp/org-element.el

This tells that you have two Org installs conflicting with
each other.  Since Org 7.9, org-element.el is not part of
contrib/ anymore, it is part of Org's core.

I suggest you delete .emacs.d/org-mode/ and reinstall Org.

HTH,

-- 
 Bastien

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

I thought that might be the case as I was posting it. Will do. Thanks.

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

Whacking the org-mode directory and re-cloning the repository did
it. Thanks again.

Re: auto-fill non-op, fill-paragraph error

[Achim Gratz]

Bastien writes:
> This tells that you have two Org installs conflicting with
> each other.  Since Org 7.9, org-element.el is not part of
> contrib/ anymore, it is part of Org's core.

It also tells you that it is not a good idea to keep …/org/contrib in
load-path before …/org.  Maybe the manual and Worg should be checked for
bad advice in that direction?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

Achim Gratz <Stromeko@nexgo.de> writes:
> It also tells you that it is not a good idea to keep …/org/contrib in
> load-path before …/org.  Maybe the manual and Worg should be checked for
> bad advice in that direction?

My init is set as follows:
(add-to-list 'load-path "~/.emacs.d/org-mode/lisp") 
(add-to-list 'load-path "~/.emacs.d/org-mode/contrib/lisp") 

isn't that the way it should be?

-ED-

Re: auto-fill non-op, fill-paragraph error

[Nick Dokos]

Edward DeMeulle <ed@demeulle.org> wrote:

> Achim Gratz <Stromeko@nexgo.de> writes:
> > It also tells you that it is not a good idea to keep …/org/contrib in
> > load-path before …/org.  Maybe the manual and Worg should be checked for
> > bad advice in that direction?
> 
> My init is set as follows:
> (add-to-list 'load-path "~/.emacs.d/org-mode/lisp") 
> (add-to-list 'load-path "~/.emacs.d/org-mode/contrib/lisp") 
> 
> isn't that the way it should be?
> 

No - C-h f add-to-list RET says:

,----
| add-to-list is a compiled Lisp function in `subr.el'.
| 
| (add-to-list LIST-VAR ELEMENT &optional APPEND COMPARE-FN)
| 
| Add ELEMENT to the value of LIST-VAR if it isn't there yet.
| The test for presence of ELEMENT is done with `equal',
| or with COMPARE-FN if that's non-nil.
| If ELEMENT is added, it is added at the beginning of the list,
| unless the optional argument APPEND is non-nil, in which case
| ELEMENT is added at the end.
`----

So you can either reverse the order, or you can say

  (add-to-list 'load-path "~/.emacs.d/org-mode/contrib/lisp" t) 

which will add it to the end of the list.

The two methods are not equivalent, mind you, but in either case the org
lisp directory will be found before the org contrib lisp directory.

And check with C-h v load-path RET afterwards to make sure that
things are as they should be.

Nick

Re: auto-fill non-op, fill-paragraph error

[Edward DeMeulle]

Nick Dokos <nicholas.dokos@hp.com> writes:
> So you can either reverse the order, or you can say
>
>   (add-to-list 'load-path "~/.emacs.d/org-mode/contrib/lisp" t) 
>
> which will add it to the end of the list.
>
> The two methods are not equivalent, mind you, but in either case the org
> lisp directory will be found before the org contrib lisp directory.

I understand. I didn't realize that add-to-list is stacking entries but
it does make sense that you'd want new entries to override previous
ones and I do see the distinction between the two options (reversing the
stacking order vs putting one at the other end of the list). Thank you
for the explanation.

Re: auto-fill non-op, fill-paragraph error

[Bastien]

Achim Gratz <Stromeko@nexgo.de> writes:

> Maybe the manual and Worg should be checked for
> bad advice in that direction?

Yes.  I updated the manual but did not check Worg yet.
If someone can have a go, great.

-- 
 Bastien