From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: bug#15888: 24.3.50; Eval-after-load eval'ed twice Date: Sun, 17 Nov 2013 09:59:08 +0100 Message-ID: <87txfbieub.fsf@gmail.com> References: <868uws6lgt.fsf@somewhere.org> <86ob5mxktp.fsf@somewhere.org> <4jppq1ha35.fsf__32040.8881329515$1384535048$gmane$org@fencepost.gnu.org> <87txfdy2cu.fsf@alphaville.bos.redhat.com> <87mwl5jz3q.fsf@gmail.com> <87wqk7hgly.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59341) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VhyC0-0003sn-9c for emacs-orgmode@gnu.org; Sun, 17 Nov 2013 03:59:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VhyBu-0000uE-FH for emacs-orgmode@gnu.org; Sun, 17 Nov 2013 03:58:56 -0500 Received: from mail-ee0-x231.google.com ([2a00:1450:4013:c00::231]:52931) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VhyBu-0000u6-7k for emacs-orgmode@gnu.org; Sun, 17 Nov 2013 03:58:50 -0500 Received: by mail-ee0-f49.google.com with SMTP id b47so160747eek.8 for ; Sun, 17 Nov 2013 00:58:49 -0800 (PST) In-Reply-To: <87wqk7hgly.fsf@gmail.com> (Nick Dokos's message of "Sat, 16 Nov 2013 22:06:17 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nick Dokos Cc: emacs-orgmode@gnu.org Hello, Nick Dokos writes: > I started emacs with > > emacs -Q -L ~/src/emacs/org/org-mode/lisp -l double-load.el > > where double-load.el looks like this: > > > (defun foobar () > (message "LOADED") (sit-for 3) (message "")) > > (setq org-load-hook (function foobar)) > > and edebugged foobar. Then I did a C-x C-f foo.org. It stopped twice > at foobar and I got backtraces (this is with the version that includes > the change you suggested above). The first time it stopped, the backtrace > looked like this: Thank you. The problem should now be fixed. Though, at some point, we will need a clear loading scheme. We're still on thin ice. Regards, -- Nicolas Goaziou