emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Christian Egli <christian.egli@sbs.ch>, emacs-orgmode@gnu.org
Subject: Re: Build error in git HEAD with org-bibtex.el
Date: Thu, 28 Apr 2011 11:47:44 -0400	[thread overview]
Message-ID: <87vcxyxtr3.fsf@fastmail.fm> (raw)
In-Reply-To: <87tydibdvi.fsf@gmail.com> (Eric Schulte's message of "Thu, 28 Apr 2011 09:21:37 -0600")

"Eric Schulte" <schulte.eric@gmail.com> writes:

> Matt Lundin <mdl@imapmail.org> writes:
>

[...]

>> And with bleeding edge emacs (compiled from the repos yesterday), I'm
>> getting an additional error:
>>
>> In toplevel form:
>> org-bibtex.el:114:1:Warning: global/dynamic var `description' lacks a prefix
>> org-bibtex.el:257:1:Error: Byte-compiling a redefinition of `get'
>> will not work - use `labels' instead
>> make: *** [lisp/org-bibtex.elc] Error 1
>>
>> Note: the description variable error has nothing to do with the recent
>> changes to org-bibtex.
>
> Yes, the org-mode source is littered with such un-prefixed dynamic
> variables, and I'm not sure how this will be addressed.  Personally I
> would prefer an option to tell the compiler not to complain, as adding
> org- to all of these variable names could make the source harder to
> read.  But, that said, I suppose there is a danger of conflict in common
> variable names between packages...

Thanks for explaining this. I believe I misspoke when I said it was an
error. I now see it is only a warning.

Best,
Matt

  reply	other threads:[~2011-04-28 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 11:34 Build error in git HEAD with org-bibtex.el Christian Egli
2011-04-28 12:53 ` Matt Lundin
2011-04-28 15:21   ` Eric Schulte
2011-04-28 15:47     ` Matt Lundin [this message]
2011-04-28 15:19 ` Eric Schulte

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=87vcxyxtr3.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=christian.egli@sbs.ch \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).