emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: var `date' lacks a prefix warnings
Date: Fri, 27 Apr 2012 16:45:51 +0200	[thread overview]
Message-ID: <87zk9xs068.fsf@gnu.org> (raw)
In-Reply-To: <m2lilhs4v7.fsf@btinternet.com> (Martyn Jago's message of "Fri, 27 Apr 2012 14:04:28 +0100")

Hi Martyn,

Martyn Jago <martyn.jago@btinternet.com> writes:

> Regarding the remaining Org-mode `lacks a prefix' warnings and
> particularly in light of the recent message on emacs.devel [1] would it
> not be sufficient to simply alias date and entry locally:
> (defvaralias 'org--date 'date)
> (defvaralias 'org--entry 'entry)
> Presumably this would be backwardly-compatible, and given a subsequent
> name change in diary-lib.el a very simple integration test could catch
> that very quickly.

We first need to fix Calendar so that it doesn't use ̀date' and `entry'
as the name for dynamically variables that are passed around.

Then preparing a patch for Org would be great.

I'll ping Glenn on the emacs-devel mailing list about this.

> p.s. I should point out that my personal view is that a serious well
> maintained Emacs library such as Org-mode should have a zero warning
> policy for official releases.

We are close to zero.  If you have time to work on some warning,
could you have a look into the one for `buffer-substring-filters'?
Also the one for "name" should be fixed.  With these two, and when
the problems from calendar are fixed, we will be closer to zero.



  reply	other threads:[~2012-04-27 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 13:04 var `date' lacks a prefix warnings Martyn Jago
2012-04-27 14:45 ` Bastien [this message]
2012-04-27 20:35   ` Martyn Jago
2012-04-27 18:53 ` Achim Gratz
2012-04-27 20:17   ` Martyn Jago

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=87zk9xs068.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=martyn.jago@btinternet.com \


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