From: Bastien <bzg@altern.org>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Compilation warnings and a test failure
Date: Thu, 20 Dec 2012 01:33:23 +0100 [thread overview]
Message-ID: <878v8th8a4.fsf@bzg.ath.cx> (raw)
In-Reply-To: <5589.1355935596@alphaville> (Nick Dokos's message of "Wed, 19 Dec 2012 11:46:36 -0500")
Hi Nick,
Nick Dokos <nicholas.dokos@hp.com> writes:
> | In org-get-location:
> | org.el:6989:10:Warning: `special-display-function' is an obsolete variable (as
> | of 24.3); use `display-buffer-alist' instead.
> | org.el:6988:10:Warning: `special-display-regexps' is an obsolete variable (as
> | of 24.3); use `display-buffer-alist' instead.
> | org.el:6987:10:Warning: `special-display-buffer-names' is an obsolete variable
> | (as of 24.3); use `display-buffer-alist' instead.
These are not trivial to fix. If someone wants to have a look,
please go ahead.
> | In org-shiftcontrolup:
> | org.el:19234:11:Warning: org-clock-timestamps-up called with 1 argument, but
> | accepts only 0
> |
> | In org-shiftcontroldown:
> | org.el:19244:11:Warning: org-clock-timestamps-down called with 1 argument, but
> | accepts only 0
Fixed, thanks.
> | In org-switch-to-buffer-other-window:
> | org.el:20957:23:Warning: `special-display-function' is an obsolete variable
> | (as of 24.3); use `display-buffer-alist' instead.
> | org.el:20956:52:Warning: `special-display-regexps' is an obsolete variable (as
> | of 24.3); use `display-buffer-alist' instead.
> | org.el:20956:23:Warning: `special-display-buffer-names' is an obsolete
> | variable (as of 24.3); use `display-buffer-alist' instead.
> | Wrote /home/nick/src/emacs/org/org-mode/lisp/org.elc
Same as above.
> and a test failure:
Fixed too, thanks!
--
Bastien
next prev parent reply other threads:[~2012-12-20 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 16:46 Compilation warnings and a test failure Nick Dokos
2012-12-20 0:33 ` Bastien [this message]
2012-12-20 9:23 ` Achim Gratz
2012-12-20 10:41 ` 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:
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=878v8th8a4.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).