From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: D-Bus integration into Emacs
Date: Thu, 06 Dec 2007 08:05:13 +0100 [thread overview]
Message-ID: <47579F29.3030903@swipnet.se> (raw)
In-Reply-To: <jer6i0oiw0.fsf@sykes.suse.de>
Andreas Schwab skrev:
> Jan Djärv <jan.h.d@swipnet.se> writes:
>
>> Andreas Schwab skrev:
>>> Jan Djärv <jan.h.d@swipnet.se> writes:
>>>
>>>> Andreas Schwab skrev:
>>>>> Jan Djärv <jan.h.d@swipnet.se> writes:
>>>>>
>>>>>> BTW, does anybody know why we have
>>>>>>
>>>>>> AC_INIT(src/lisp.h)
>>>>>>
>>>>>> at the begining of configure.in? The documentation says:
>>>>>>
>>>>>> AC_INIT (PACKAGE, VERSION, [BUG-REPORT], [TARNAME])
>>>>> See (autoconf)Obsolete Macros.
>>>>>
>>>> Thanks for the pointer. But it would be OK for us to change to the
>>>> non-obsolete version?
>>> Sure, we require a modern version of autoconf anyway.
>>>
>> OK, I did that.
>
> That means that the version number is now duplicated in configure.in,
It is too bad, I agree. But using obsolete macros is no good either, sooner
or later they are removed. Ideally we should generate lisp/version.el and
doc/emacs/emacs.texi from configure so the version number is only in
configure.in. But that would not be OK where configure is not used.
Suggestions anyone?
> and AC_CONFIG_SRCDIR is lost.
That is easily fixed.
Jan D.
next prev parent reply other threads:[~2007-12-06 7:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 22:19 D-Bus integration into Emacs Michael Albinus
2007-12-02 17:28 ` Michael Albinus
2007-12-02 20:45 ` Eli Zaretskii
2007-12-02 21:47 ` Jason Rumney
2007-12-03 8:37 ` Michael Albinus
2007-12-02 22:40 ` Christian Faulhammer
2007-12-03 2:32 ` Nick Roberts
2007-12-03 7:04 ` Christian Faulhammer
2007-12-03 7:36 ` Nick Roberts
2007-12-03 8:48 ` Christian Faulhammer
2007-12-03 8:59 ` Nick Roberts
2007-12-03 22:04 ` Andreas Schwab
2007-12-04 6:48 ` Christian Faulhammer
2007-12-04 16:55 ` Richard Stallman
2007-12-04 18:18 ` Ulrich Mueller
2007-12-04 20:17 ` Michael Albinus
2007-12-04 20:48 ` Ulrich Mueller
2007-12-04 21:03 ` Michael Albinus
2007-12-04 21:56 ` Magnus Henoch
2007-12-05 6:05 ` Richard Stallman
2007-12-03 8:51 ` Michael Albinus
2007-12-03 18:42 ` Richard Stallman
2007-12-03 21:11 ` Michael Albinus
2007-12-03 3:17 ` Magnus Henoch
2007-12-03 7:12 ` Jan Djärv
2007-12-03 9:37 ` Andreas Schwab
2007-12-04 7:36 ` Jan Djärv
2007-12-04 10:25 ` Andreas Schwab
2007-12-04 11:30 ` Jan Djärv
2007-12-05 22:51 ` Andreas Schwab
2007-12-06 7:05 ` Jan Djärv [this message]
2007-12-06 8:02 ` Glenn Morris
2007-12-06 8:08 ` Thien-Thi Nguyen
2007-12-06 10:01 ` Jan Djärv
2007-12-05 2:56 ` Richard Stallman
2007-12-03 21:41 ` Michael Albinus
2007-12-03 22:05 ` Magnus Henoch
2007-12-04 7:35 ` Jan Djärv
2007-12-03 23:43 ` Johan Bockgård
2007-12-04 21:42 ` Michael Albinus
2007-12-05 10:37 ` Johan Bockgård
-- strict thread matches above, loose matches on Subject: below --
2007-12-05 8:37 Michael Albinus
2007-12-05 14:55 ` Magnus Henoch
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47579F29.3030903@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.