From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: Xemacs 21.5.32 & org-8.03 almost
Date: Sun, 09 Jun 2013 21:45:28 +0200 [thread overview]
Message-ID: <87sj0r83vr.fsf@mat.ucm.es> (raw)
In-Reply-To: 87a9mzazsi.fsf@Rainer.invalid
>> "Achim" == Achim Gratz <Stromeko@nexgo.de> writes:
> Uwe Brauer writes:
>> (I had this issue for example in Ulf icalendar.el). I thought of
>> wrapping (if (featurep 'xemacs) around the relevant code, till I
>> found out that there is already a org-compat, so I
>> added (require 'org-compat) and then the problem disappeared.
>>
>> - However I now receive:
>>
>> Cannot open load file: "org-version.el"
> This would indicate you didn't create the autoload files.
Strange I am sure I run make autoload.
I did it again and now this file is generated. *However*
now even with
(require 'org-compat)
I obtain
,----
|
| (1) (initialization/error) An error has occurred while loading /home/oub/.emacs:
|
| Wrong number of arguments: (lambda (obsolete-name current-name when
| &optional docstring) "$ad-doc: define-obsolete-function-alias$" (let
| (ad-return-value) (setq ad-return-value
| (ad-Orig-define-obsolete-function-alias obsolete-name current-name))
| ad-return-value)), 2
`----
The strange this is that C-h f define-obsolete-function-alias tells me
that the function is advised and points to org-compat but it seems not
to work.
I can of course just wrap the xemacs featurep and delete the docstring
in these functions but I thought org-compat would make this not
necessary.
Uwe
next prev parent reply other threads:[~2013-06-09 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 18:20 Xemacs 21.5.32 & org-8.03 almost Uwe Brauer
2013-06-09 18:45 ` Achim Gratz
2013-06-09 19:45 ` Uwe Brauer [this message]
2013-06-09 20:14 ` Achim Gratz
2013-06-09 20:36 ` Uwe Brauer
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=87sj0r83vr.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
/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).