From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Unable to compile using Emacs 23 in Windows Date: Fri, 28 Aug 2009 14:57:12 +0200 Message-ID: References: <877hwpwbwd.fsf@gmail.com> <87my5lxoob.fsf@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh117-0007hb-Uf for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:57:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh112-0007cd-VB for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:57:21 -0400 Received: from [199.232.76.173] (port=38772 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh112-0007cP-OJ for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:57:16 -0400 Received: from mail-ew0-f217.google.com ([209.85.219.217]:48398) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mh111-0000fn-Rw for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:57:16 -0400 Received: by ewy17 with SMTP id 17so1397954ewy.2 for ; Fri, 28 Aug 2009 05:57:15 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Paul Mead Cc: emacs-orgmode@gnu.org On Aug 28, 2009, at 2:36 PM, Paul Mead wrote: > Carsten Dominik writes: > >> >> >> Hi Paul, >> >> did you interrupt the compilation here? >> >> The fact that there are a number of compilation *warnings* is no >> problem at all, >> I do clean these up only occasionally, for a release. In between >> releases, >> the can be present and usually pose no problem. >> >> The messages about goto-line are from a new policy in Emacs, >> apparently this >> is no longer a function that should be called from Lisp programs.... >> >> - Carsten > > Hi Carsten > > yes, I interrupted the compilation as it was stuck there. > > Pulling the next version seemed to cure the problem. > > I was able to byte-compile the files from dired with no problems, I > don't know if that makes it more or less clear? Not clearer, I don't know how it could get stuck. Anyway, good that it is solved, apparently.... - Carsten