From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: absurd
Date: Mon, 10 Jun 2013 22:37:24 +0200 [thread overview]
Message-ID: <87k3m14s8r.fsf@mat.ucm.es> (raw)
In-Reply-To: 87zjux51zo.fsf@Rainer.invalid
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
>> "Achim" == Achim Gratz <Stromeko@nexgo.de> writes:
> Uwe Brauer writes:
>> Now the make process is getting absurd.
> What does that problem have to do with make?
Because I can byte compile it manually, in dired via Shift-B!
That I consider as bizarre, byte compiling works, but via make it does
not.
>> For example I put in org-agenda.el
>>
>> (if (featurep 'xemacs)
>> (define-obsolete-variable-alias 'org-agenda-menu-two-column
>> 'org-agenda-menu-two-columns)
>> (define-obsolete-variable-alias 'org-agenda-menu-two-column
>> 'org-agenda-menu-two-columns "24.3"))
> That cannot work since the byte-compiler necessarily sees both branches
> of the if clause.
I don't understand:
(defun my-test-if ()
(interactive)
(if (featurep 'xemacs)
(message "Xemacs")
(message "GNUS")))
when executed in Xemacs returns Xemacs, when executed in GNU emacs returns
GNUS.
In any case I removed the ifs leaving
(define-obsolete-variable-alias 'org-agenda-menu-two-column
'org-agenda-menu-two-columns)
And again make failed with the same error message!
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5556 bytes --]
next prev parent reply other threads:[~2013-06-10 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 11:01 absurd (was: Xemacs 21.5.32 & org-8.03 almost) Uwe Brauer
2013-06-10 17:06 ` absurd Achim Gratz
2013-06-10 18:49 ` absurd Achim Gratz
2013-06-10 20:40 ` absurd Uwe Brauer
2013-06-10 20:50 ` absurd Achim Gratz
2013-06-10 20:59 ` absurd Uwe Brauer
2013-06-10 20:45 ` absurd Uwe Brauer
2013-06-10 20:37 ` Uwe Brauer [this message]
2013-06-10 20:55 ` absurd Achim Gratz
2013-06-10 21:26 ` absurd 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=87k3m14s8r.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).