From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.help Subject: Re: Help debugging a backtrace Date: Sun, 01 May 2016 19:05:07 +0000 Message-ID: References: <87wpniyiy6.fsf@gmail.com> <87mvoccdht.fsf@web.de> <87r3dl3ljs.fsf@web.de> <87mvo93lbf.fsf@web.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1462129571 27068 80.91.229.3 (1 May 2016 19:06:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 1 May 2016 19:06:11 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Michael Heerdegen , Bruce Connor Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun May 01 21:06:10 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1awwgz-00059v-Rj for geh-help-gnu-emacs@m.gmane.org; Sun, 01 May 2016 21:06:09 +0200 Original-Received: from localhost ([::1]:34034 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1awwgw-0008IY-3J for geh-help-gnu-emacs@m.gmane.org; Sun, 01 May 2016 15:06:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57102) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1awwgf-00085D-Av for help-gnu-emacs@gnu.org; Sun, 01 May 2016 15:05:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1awwgT-0000lH-Be for help-gnu-emacs@gnu.org; Sun, 01 May 2016 15:05:43 -0400 Original-Received: from mail-oi0-x22c.google.com ([2607:f8b0:4003:c06::22c]:36301) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1awwgS-0000iQ-1p for help-gnu-emacs@gnu.org; Sun, 01 May 2016 15:05:37 -0400 Original-Received: by mail-oi0-x22c.google.com with SMTP id x201so169879603oif.3 for ; Sun, 01 May 2016 12:05:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xsCs5pYi5jxcAasCyEJ4GVj+3+/Ctpl2LgtI6EU9LxA=; b=BwraJ1Xba/8jiEIMPLr5gIOFBDlXNb7lixguYOX12ggOQH5hGzmVGKaLwSA1n6N/sm RU2FwzDBOzUOCoy8CbPdlk3JwhyJik0BNdm+gDCjjoVFtvbIIsIc79XbI80kp6165WHC iTaHMtxxgTEobJz/U5zdBVGw9GNKTjsn0MqcUMGM21pSowULcByNn/jVuhyE8aDOYkr+ hsfFVeicyj9mr5i0ZROdt+7H+DPem9QAFrexeVwUyV+xivEUJpCOUOzADF1Ky8CT28Ah yUU7Ks6E38QhNoMN8edncTPCfsA1JRVzOgDVt8r1r3pmW93y96Ug2g2qf7L0LSjhvHNr J6rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xsCs5pYi5jxcAasCyEJ4GVj+3+/Ctpl2LgtI6EU9LxA=; b=FeqGQxxgWV02ACvCPLgCAX1T/AuqdCLJoDdSLIVGglt/MmU+kThI9YidQVAJOiMoPJ pOHwT4JsBEVkGFuAqrH1fuOQHZA37YTR93jo6cFNhw7TYXClUuB3axL2PkB8Bvx8/84m iv9K9sSaycV8gGIbhGtHfpOrj0nPvt3xE/ekMwMRugUIFYd+oUReruab2372WhB0xoXO BfMJ/8k8uPOfDQx8Womeamn+mWvEfWQMpJ9dgXF37Qv5867FK8ZM0pl8BhKQkWWoI2i6 fYIa+ThaezI26g6DKOgxNPuRpJkO3bwp3aS3eKfPBY4YZ4y5LzimjgPozYNXyI6VtmuB xOyg== X-Gm-Message-State: AOPr4FUZRL4sBdqF7K9su7tyCjyVbSWOxGkvHBqFS16oSxeiKg1O6rNNu3cWgXC6kd7ihuWyhy1wK5jHyTnF+A== X-Received: by 10.157.6.80 with SMTP id 74mr13423836otn.164.1462129517968; Sun, 01 May 2016 12:05:17 -0700 (PDT) In-Reply-To: <87mvo93lbf.fsf@web.de> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c06::22c X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:109850 Archived-At: Hi Michael, I have made some progress on the debug and have come to some strange conclusions that might help you or anyone else familiar with package.el and on how packages are loaded at emacs startup from the elpa/ dir. Conclusion: - This happens ONLY on my phone build as I earlier stated using the exact same config I use on my RHEL 6.6 machine ( https://github.com/kaushalmodi/.emacs.d ). - I prefer to put all package related stuff in a separate file. So this issue is seen only if I do (package-initialize) in a separate file (not in init.el). - The issue is "gone" if I move (package-initialize) to init.el - The issue is not seen with an empty elpa/. None of my packages directly require finder-inf. But one of them probably does so indirectly (it's probably requiring some package, which then requires finder-inf? Not sure ..). Here is my installed package list: https://gist.github.com/kaushalmodi/e0de9d8dc2fff37b617f5ca0a52e6d0f - The issue is not seen with "emacs -Q -l my-init.el", but it is seen with "emacs" (even when init.el is the exact same as my-init.el. Also there is no default.el or site-start.el.). Huh! My understanding is that results of both "emacs -Q -l init.el" and "emacs" should be the same in absence of default.el or site-start.el or any site-wide .el. With that, if I set the below as my init.el and do "emacs", I do NOT see the issue because (package-initialize) is happening in the init.el. ===== ~/.emacs.d/init.el ===== (package-initialize) ===== BUT if I set the below as my init.el (move the (package-initialize) out of init.el), then I see the ((require . finder-inf)) problem: ===== ~/.emacs.d/init.el ===== ;; (package-initialize) ; Do NOT delete this comment ;; In emacs 25+, the `package-initialize' call is auto-added to the top of ;; init.el unless the user already has a commented or uncommented ;; `(package-initialize)' line present in their init.el. ;; I call this function in my-package-setup.el and so am keeping the ;; commented out version here so that package.el does not add it again. (load (locate-user-emacs-file "my-package-setup.el") nil :nomessage) ===== ===== ~/.emacs.d/my-package-setup.el ===== (package-initialize) ; Do not delete this line (provide 'my-package-setup) ===== Note that I have the exact same elpa/ dir with the above linked list of installed packages in both cases. @Artur It would be great if you have time to recreate this issue on your phone. See if you can recreate this issue with just the init.el and my-package-setup.el approach above with your elpa/ dir intact without any modification. In the mean while, I will try to narrow down to the package(s) in my elpa/ that probably cause this problem. Thanks! Kaushal -- -- Kaushal Modi