emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Byte compiler warnings
Date: Sat, 22 Oct 2011 16:15:41 +0200	[thread overview]
Message-ID: <87ty712jua.fsf@Rainer.invalid> (raw)

Recently the byte compiler has become increasingly dissatisfied with the
orgmode code again... :-)

Emacs24 complains about these:

In org-agenda-get-blocks:
org-agenda.el:5434:42:Warning: assignment to free variable `category-pos'
org-agenda.el:5434:20:Warning: reference to free variable `category-pos'

That actually has been there for a while.

In org-edit-src-code:
org-src.el:295:14:Warning: reference to free variable `eq'

That's most likely a bug involving a comparison, in any case if "eq" really is a variable it
surely needs a different name.

In org-babel-get-lob-one-liner-matches:
ob.el:191:21:Warning: reference to free variable

That one is a bit older IIRC.

In org-babel-execute:shen:
ob-shen.el:68:32:Warning: reference to free variable `result-params'
ob-shen.el:72:19:Warning: reference to free variable `result'

I guess Eric knows what to do with this.

In end of data:
org.el:20874:1:Warning: the function `cdlatex-compute-tables' is not known to
    be defined.

I don't know if a package needs to be required or the function declared.

Emacs23 additionally complains about:

In org-mode:
org.el:4870:9:Warning: assignment to free variable `bidi-paragraph-direction'

In end of data:
org.el:20874:1:Warning: the function `format-spec' might not be defined at

It looks like these functions don't exist in Emacs23 and need to be
protected via version-dependent wrappers.

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

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:

             reply	other threads:[~2011-10-22 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22 14:15 Achim Gratz [this message]
2011-10-22 14:31 ` Byte compiler warnings Bastien
2011-10-22 14:59   ` Achim Gratz
2011-10-23 20:46     ` Bastien
2011-10-24 23:46 ` Andrei Jirnyi
2011-10-28 15:27   ` Bastien

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:

  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=87ty712jua.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).